Cisco Cisco Intelligent Automation for Cloud 4.3.1 Installation Guide

Page of 130
84
Configuring Cisco IAC With the Wizard
Managing PODs
a.
Assign a name for this POD. 
b.
Assign a description for this POD. 
c.
Optional. Choose the UCS Manager that is to serve this POD. 
Note: 
Any physical devices acting as Edge Routers or Layer2 Aggregation Switches should also be selected for 
future extensions. 
Note: 
The VLAN Pool field must have a range of VLANs that Cisco IAC can use to create content extensions.
Note: 
There is a 1-to-1 mapping between UCS Managers and PODs. If the drop-down list is empty, all available UCS 
Managers have been associated with a POD. 
Note: 
UCS Fabric Inter-connects will also appear in the list for select under the Network POD. The UCS Manager as 
well as its Fabric Inter-connects should all be selected together.
3.
Click Submit Order.
4.
Click on the number in the Requisition Number field to display the details. 
5.
Click Close when the status says Completed
Note: 
Devices which you have discovered and then register are those devices which you want dynamically created 
VLANS (by Cisco IAC) to be propagated to. Therefore, register a device if you want Cisco IAC to configure the VLAN 
on it and choose them when creating the network POD.
Creating Compute PODs
Use the Create Compute POD form to register an installed compute POD (Point Of Delivery) and choose the cloud 
infrastructure platform elements that manage its resources.
Note: 
There is a 1-to-1 mapping between datacenters and PODs (one between DataCenter and Compute POD; refer to 
the object model). If the drop-down list is empty, all available datacenters have been associated with a POD.
Note: 
Multiple data centers are supported through multiple Compute PODs. Multiple Compute PODs can reference the 
same network POD.
1.
From the Wizard, choose Create Compute POD.
2.
On the Create Compute POD form:
a.
Enter a new short name and a full description for the Compute POD.
b.
Set the Process Orchestrator Location for the POD in the Location field.
Note: 
Location is optional; however, you can enter the same location you entered for the “PO Location” for Cisco 
Process Orchestrator field earlier. By doing so, the two locations can be mapped together, if you want. For 
information, see the section, 
 in this module, under the heading, 
c.
Choose your Cloud Infrastructure Type, such as VMware vCenter Server.
Note: 
There are other infrastructure types beyond VMware vCenter Server used in this example and therefore, the 
subfields that are displayed after you select that type will be different. The other types include: 
 
 Amazon EC2
 
 Cisco UCS Director
 
 Openstack Cloud Manager
 
 VMware vCloud Director