Cisco Cisco Intelligent Automation for Cloud 4.3.2 User Guide
63
Setting Up the Infrastructure
Setting Up a Community VDC
Setting Up a Community VDC
A community VDC (virtual data center) can be used by server owners in any organization to provision virtual and physical
servers. A community VDC lives on a cluster in a POD and has datastores, resource pools, and community networks
resources associated with it.
servers. A community VDC lives on a cluster in a POD and has datastores, resource pools, and community networks
resources associated with it.
Multiple community VDCs can be created by the Cloud Provider for server owners to provision servers in. A virtual data
center has an associated size that determines limits for the number of virtual servers, physical servers, vCPUs, CPU MHz,
storage, and memory.
center has an associated size that determines limits for the number of virtual servers, physical servers, vCPUs, CPU MHz,
storage, and memory.
Limits are enforced by comparing the sum of the number of provisioned virtual and physical servers and the vCPUs,
memory, and storage for a server size against the limits defined for the virtual data center size.
memory, and storage for a server size against the limits defined for the virtual data center size.
A VMware resource pool is created for each virtual data center. This allows further control of resource utilization by
defining CPU and memory limits, as well as CPU and memory reservations in the VMware resource pool.
defining CPU and memory limits, as well as CPU and memory reservations in the VMware resource pool.
On the Create VDC service form (My Cloud > My VDCs), choose “Community VDC” as “Yes” to create the
Community VDC.
Community VDC.
Note:
f the Community VDC ordering is set to No for the chosen Tenant, then by default the Community VDC option
is set to No on the form.
Adding a Server Owner
Cisco Intelligent Automation for Cloud users consist of Server Owners, who are end users of an organization who order
and provision servers. There are two kinds of Server Owners:
and provision servers. There are two kinds of Server Owners:
Virtual and Physical Server Owner—Orders and provisions virtual machines and physical servers.
Defines/assigns/adds a SO after creating an organiation.
Defines/assigns/adds a SO after creating an organiation.
Virtual Server Owner—Orders and provisions virtual machines only.
Both users are created using the same form. To add users, complete the following steps:
1.
Choose Management > Tenant Management.
2.
Choose a Tenant.
3.
Choose the Organization where the server owner is located (within the tenant).
Note:
Server Owners can only be added to an Organization. Actions are allowed at the tenant level with regard to
Add User are adding TTA and/or TBA. Even where the TTA and the TBA are already defined, you cannot add a Server
Owner at the tenant level.
Owner at the tenant level.
4.
On the Tenant Management form, choose the Users tab.
5.
Click Add User.
6.
On the Add User form, choose the organization to which you want to add a new user as a Server Owner.
7.
Choose Create New User from the Action drop-down list. Provide the following:
a.
Enter the first and last name of the new Server Owner, a unique login identifier for the new Server Owner, and
the new Server Owner’s e-mail address.
the new Server Owner’s e-mail address.
b.
From the drop-down list, choose the time zone of the new Server Owner’s primary address.
c.
Enter, then re-enter the password for the new Server Owner.
8.
In the Roles field, click one of the following radio buttons to indicate the role to be assigned to the user: