Skip to content
This repository has been archived by the owner on May 24, 2024. It is now read-only.

1.1.2.3 diagram #10

Open
mmorozumi opened this issue Dec 3, 2015 · 3 comments
Open

1.1.2.3 diagram #10

mmorozumi opened this issue Dec 3, 2015 · 3 comments

Comments

@mmorozumi
Copy link

It is difficult to understand the 'Trusted' and 'untrusted'. I think 'known' and 'unknown' may be better.

@rmogull
Copy link
Collaborator

rmogull commented May 20, 2016

it isn't just known though- "known" could be nearly anyone, while "trusted" is known and approved. but Iwill leave this issue open for more feedback.

@rmogull rmogull closed this as completed May 20, 2016
@rmogull rmogull reopened this May 20, 2016
@daddydruid
Copy link

trusted is a great term and in common use wrt cloud assurance and architecture discussions. Possibly needs a definition for both trusted/untrusted added?

@pve
Copy link

pve commented May 23, 2016

In my training sessions i typically explain this as: the consumer controls who the (other) users are.
Private cloud IMHO is about isolation, as a consumer you require your provider to provision resources exclusive to you, and isolate you well enough from other tenants. The consumer decides whether or not the provisioning is exclusive enough. By extension, that means that the consumer should decide/control who the other users are on those resources.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants