UCSD Integration Work Flow Examples

[tasankar@cisco.com]

Introduction:

In this article, we are providing sample work flows for the private cloud management solution. In our topology, ACI is used for network. We have placed the BMA outside the UCS fabric  and connected through L3 switch. The UCS servers are connected to the leaves of the ACI. Storage devices are connected with the UCSM FI through MDS(s). We have used NetApp AF and VNX2 storage arrays in this topology. The idea is to give the WF to manage private cloud deployment using the existing UCSD tasks, starting from APIC tenant creation, Server reservation, Bare Metal Provisioning, Creating the Datacenter, Creating Cluster and adding the created host to the cluster. We have used the basic variations in the infra provisioning like SAN Boot and Local Boot. The topology of the setup is attached.

Toplogy:

UCSD INTEGRATION TOPOLOGY

Solution:

These set of work flows are provided to help the customer to understand and build their use cases. This can be extended as per the need of customer. All the functionalities are modularly grouped as a compound tasks and it can be reused and extended based on the customer need. We have used the Orchestration filtering mechanism to show/hide the relevant WF input fields during the work flow execution. 

Compatible UCS Director Versions:

UCS Director 6.6.X.X

Category:

Virtualization, Compute, Network and Storage

Components:

Cisco UCS Director

Cisco UCS Director Baremetal Agent

UCSM, ACI, MDS, VC, NETAPP/VNX

 Prerequisites:

All accounts are added into UCSD
BMA is added into UCSD
UCS Service Profile Template is created as per need the customer use caes

BareMetal Provisioning WF Prerequisites:

Need to provide these three user input values. Currently its configured as admin input. This need to be provided based on your environement. 

APIC_Tenant_Common_Identity
BMA_EPG
MGMT_EPG

1.      Master_Flow_Tenant_Creation_With_NetApp_FC_ADD_LUN_BMA_OS_Deployment

This workflow creates an ACI tenant and allocates compute resources. The workflow creates the server installed with VMware hypervisor and the VC environment for the tenant. The installation includes configuration of the VMware datacenter and cluster, and attachment of the new host. BMA is used to provision the OS on the local disk of the blade server. A NetApp LUN is mapped to the new host as an external datastore.

2.      Master_Flow_Tenant_Creation_With_NetApp_FC_ADD_LUN_Manual_OS_Deployment

This workflow creates an ACI tenant and allocates compute resources. Manual installation (KVM) is used to provision the OS on the local disk of the blade server. A NetApp LUN is mapped to the new host as an external datastore.

3.      Master_Flow_Tenant_Creation_With_NetApp_FC_SAN_Boot_Manual_OS_Deployment

This workflow creates an ACI tenant and allocates compute resources. Manual installation (KVM) is used to provision the OS on the external SAN using a UCS SAN boot policy. A NetApp LUN is mapped to the new host as an external datastore.

 4.      Master_Flow_Tenant_Creation_With_VNX_FC_ADD_LUN_BMA_OS_Deployment

This workflow creates an ACI tenant and allocates compute resources. The workflow creates the server installed with VMware hypervisor and the VC environment for the tenant. The installation includes configuration of the VMware datacenter and cluster, and attachment of the new host. BMA is used to provision the OS on the local disk of the blade server. A VNX5600 storage LUN is mapped to the new host as an external datastore. 

5.      Master_Flow_Tenant_Creation_With_VNX_FC_ADD_LUN_Manual_OS_Deployment

This workflow creates an ACI tenant and allocates compute resources. Manual installation (KVM) is used to provision the OS on the local disk of the blade server. A VNX5600 storage LUN is mapped to the new host as an external datastore.

6.      Master_Flow_Tenant_Creation_With_VNX_FC_SAN_Boot_BMA_OS_Deployment

This workflow creates an ACI tenant and allocates compute resources. The workflow creates the server installed with VMware hypervisor and the VC environment for the tenant. The installation includes configuration of the VMware datacenter and cluster, and attachment of the new host. BMA is used to provision the OS on the local disk of the blade server. A VNX5600 storage LUN is mapped to the new host as an external datastore using a UCS SAN boot policy. The client can input boot parameters.

7.      Master_Flow_Tenant_Creation_With_VNX_FC_SAN_Boot_Manual_OS_Deployment

This workflow creates an ACI tenant and allocates compute resources. Manual installation (KVM) isused to provision the OS on the external SAN using a UCS SAN boot policy. A VNX5600 storage LUN is mapped to the new host as an external datastore.

8.      Master_Flow_VDC_VMware_Task

This workflow creates a Cisco UCS Director VDC and allocates compute resources. The admin can create a VMware resource pool and attach it to the compute policy. The admin can also create the system, compute, network, and storage policies.