Updated Branches: refs/heads/4.2-forward a55c75bbd -> 2d08a322d
CLOUDSTACK-2121. DOC. New docs for affinity groups. Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/2d08a322 Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/2d08a322 Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/2d08a322 Branch: refs/heads/4.2-forward Commit: 2d08a322dd976e696783535a0f3d174483adf155 Parents: a55c75b Author: Jessica <[email protected]> Authored: Tue Aug 27 13:37:40 2013 -0700 Committer: Jessica <[email protected]> Committed: Tue Aug 27 13:37:40 2013 -0700 ---------------------------------------------------------------------- docs/en-US/accounts-users-domains.xml | 33 ++++++++++++++++++++++++++---- 1 file changed, 29 insertions(+), 4 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/cloudstack/blob/2d08a322/docs/en-US/accounts-users-domains.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/accounts-users-domains.xml b/docs/en-US/accounts-users-domains.xml index a3f5837..34372a7 100644 --- a/docs/en-US/accounts-users-domains.xml +++ b/docs/en-US/accounts-users-domains.xml @@ -46,8 +46,33 @@ <title>Root Administrator</title> <para>Root administrators have complete access to the system, including managing templates, service offerings, customer care administrators, and domains</para> </formalpara> - <para>The resources belong to the account, not individual users in that account. For example, - billing, resource limits, and so on are maintained by the account, not the users. A user can - operate on any resource in the account provided the user has privileges for that operation. - The privileges are determined by the role.</para> + <formalpara> + <title>Resource Ownership</title> + <para>Resources belong to the account, not individual users in that account. For example, + billing, resource limits, and so on are maintained by the account, not the users. A user can + operate on any resource in the account provided the user has privileges for that operation. + The privileges are determined by the role.</para> + </formalpara> + <section id="account-dedicated-resources"> + <title>Dedicating Resources to Accounts and Domains</title> + <para>You can dedicate infrastructure resources including zones, pods, clusters, or hosts to an account or domain. + </para> + <para>The root administrator can dedicate resources to a specific domain or account + that needs private infrastructure for additional security or performance guarantees. + A zone, pod, cluster, or host can be reserved by the root administrator for a specific domain or account. + Only users in that domain or its subdomain may use the infrastructure. + For example, only users in a given domain can create guests in a zone dedicated to that domain.</para> + <para>There are several types of dedication available:</para> + <itemizedlist> + <listitem> + <para>To explicitly dedicate a resource, use the explicit-dedicated type of Affinity Group. + For example, when creating a new VM, an end user can choose to place it on dedicated infrastructure. + See <xref linkend="affinity-groups"/>.</para></listitem> + <listitem><para>You can also use strict implicit dedication. + Strict Implicit dedication, when requested, means, a host will not be shared across multiple accounts â as an example, here is a reason: + for deployment of certain types of applications, such as desktops, due to licensing reasons, no host can be shared between different accounts.</para></listitem> + <listitem><para>You can also implicitly dedicate a resource with "preferred" implicit dedication. This means that the resource will be deployed + in dedicated infrastructure if possible. Otherwise, the resource can be deployed in shared infrastructure.</para></listitem> + </itemizedlist> + </section> </section>
