Cisco Cisco Intelligent Automation for Cloud 4.2 User Guide
64
Setting Up a Community VDC
Setting Up a Community VDC
3.
On the Add Cloud Administrator form, choose Choose Existing User from the Action drop-down list.
4.
Choose the nsAPI user.
5.
Click Submit Order.
Manually Adding the Site Administrator Role to an nsAPI User
You can manually add the Site Administrator role to an nsAPI user without directory service. Follow the steps below.
1.
Choose Organization Designer from the module drop-down list, choose the People tab.
2.
Choose the nsAPI user.
3.
Choose Roles, check the Site Administrator check box, then click Add.
Starting All Other Agents
1.
Choose Service Link from the module drop-down list, then click the Control Agents tab.
2.
While pressing and holding Shift, click the red icon next to the first agent in the list, then click the red icon of the
last agent in the list to choose all of the agents, then click Start Chosen.
last agent in the list to choose all of the agents, then click Start Chosen.
Note:
If a vertical scroll bar appears in the list, scroll down to choose the last agent on the page.
The red icons turn to green, indicating that they are now sending and receiving.
3.
If there are additional agents in the list, use the scroll arrow at the bottom of the list to display to them, then repeat
Step 2, above
Step 2, above
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” to create the 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.