The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the following sections:
You can use a resource group to select the appropriate resources for a tenant based on the requirements of an application. Additional concepts, such as a service offering, tenant profile, application profile, and resource group, are all required. Using these resource group concepts, you can onboard tenants and deploy applications based on a dynamic selection of resources. You can share resources in a resource group across tenants or you can dedicate them to a specific tenant.
A resource group is a pool of resources. Each group can contain physical infrastructure resources, virtual infrastructure resources, or a combination of physical and virtual infrastructure resources. Resource groups enable you to onboard tenants into Cisco UCS Director with minimum intervention.
As an infrastructure administrator or system administrator, you can add physical or virtual accounts to a resource group one at a time. Also, you can assign a pod to a resource group where all the accounts in the pod are added to the resource group. For more information about assigning a pod to a resource group, see Adding a Pod to a Resource Group.
When an account is added to a resource group, the resource group by default announces all the capabilities and capacities for objects for that account as resource group entity capacities and capabilities. With Cisco UCS Director, you can selectively disable certain capacities or capabilities from the resource group.
You can configure the environment variable for each resource. These environment variables are used during provisioning of the tenant onboarding and application deployment.
Note | The listed environment variables are not required for every workflow. The subset of required environment variables depends on the use case and the specific workflow(s) being executed. |
Environment Variable |
Description |
Sample Value |
---|---|---|
Container Parent Folder |
The folder to which you want to add the newly created container. |
APIC |
IP Subnet Pool Policy |
The APIC container uses an IP subnet pool policy that is defined in Cisco UCS Director. Each tier inside the container gets a unique subnet address from the IP subnet pool policy. This environment variable is used for container provisioning. |
IP-Pool |
No environment variables are required for virtual storage.
Environment Variable |
Description |
Sample Value |
---|---|---|
VMM Domain for VMware |
VMware vCenter is configured ACI-vCenter with the Virtual Machine Manager (VMM) domain. When VMware vCenter is associated with Cisco APIC, a distributed virtual switch (DVS) with the same name is created in VMware vCenter. This environment variable is used for tenant onboarding. Choose VMM domain with Cisco AV switch to support AVS in VXLAN mode. Cisco UCS Director offers AVS support in both VLAN and VXLAN mode. The VM gets the VLAN ID or VXLAN ID from the pool assigned to the VMM domain. |
ACI-Bldg4-1-vCenter |
DV Switch |
Choose either DV switch or Cisco AV switch according to the requirement. The DV switch is available on the vCenter account and is used to connect the selected host during onboarding. The Cisco AV switch is used to support AVS in VXLAN mode. This environment variable is used for tenant onboarding. |
virt_switch |
Environment Variable |
Description |
Sample Value |
---|---|---|
Physical Domain for UCS |
The physical domain for Cisco UCS. This environment variable is used for bare metal provisioning. |
Phys |
VLAN Pool |
The VLAN pool from which you want to assign a VLAN ID for the account. |
ACI3-Eng-VLAN-Pool |
iSCSI PXE Boot Service Profile Template |
The template used for creating the host service profile on which you want to provision bare metal. This environment variable is used for bare metal provisioning on a NetApp storage system. |
DR_UCSM;org-root;org-root/l s-ACI-DR-Hosts |
Service Profile Template for Full Width Blade |
The service profile template is used to create a service profile. When a service profile is created, the software identifies and selects free servers from the server pool that is associated with the service profile template. This environment variable is used for the VNX tenant onboarding. |
VNX_UCSM;org-root/ls-PSC- FullBlade-Template |
Service Profile Template for Half Width Blade |
The service profile template is used to create a service profile. When a service profile is created, the software identifies and selects free servers from the server pool that is associated with the service profile template. This environment variable is used for the VNX tenant onboarding. |
VNX_UCSM;org-root/ls-PSC- HalfBlade-Template |
IQN Pool |
The IQN pool that contains the iSCSI Qualified Names (IQNs) used as initiator identifiers by iSCSI vNICs in a Cisco UCS domain. The IQN pool is used to create a service profile iSCSI boot policy. This environment variable is used for bare metal provisioning on a NetApp storage system. |
IQN_Pool |
Boot Policy |
Boot policy for the physical compute account. This environment variable is used for a VNX-type account. |
VNX_UCSM;org-root;org-root// boot-policy-SAN_NEW |
VLAN |
VLAN for the physical compute account. This environment variable is used for a VNX-type account. |
VNX_UCSM;fabric/lan/net-MGT -ACI-POOL |
Environment Variable |
Description |
Sample Value |
---|---|---|
Physical Domain for NetApp |
The physical domain that is used to connect the NetApp account to the APIC. This environment variable is used for tenant onboarding. |
topology/pod-1/paths-201/pathep- [eth1/36] |
NetApp Static Path |
The static path defines the port on the APIC where the NetApp cluster node is connected. This environment variable is used to add the static path to the endpoint group (EPG) during tenant onboarding. |
topology/pod-1/node-302/sys /cdp/inst/if-[eth1/47]adj-1 |
Vlan pool |
The VLAN pool that is used to create the cluster vServer. This environment variable is used for tenant onboarding. |
Vlan_pool |
SP Port |
The storage processor (SP) port for the physical storage account. This environment variable is used for VNX type account. |
VNX-POD;VNX_BLOCK;A- 0;50:06:01:60:88:60:1B:6A: 50:06:01:60:08:60:1B:6A ,VNX-POD;VNX_BLOCK;A- 1;50:06:01:60:88:60:1B:6A: 50:06:01:61:08:60:1B:6A |
Replication Storage Group |
The replication storage group for the physical storage account. This environment variable is used for VNX type account. |
|
NFS Vlan Pool |
This environment variable is used to define a VLAN pool. Individual VLANs are then assigned to a physical storage account dynamically from the pool. |
NetApp-vlan-pool |
SVM mgmt Vlan Pool |
The VLAN pool for management of Storage Virtual Machine (SVM). |
NetApp-vlan-pool |
iSCSI_A VLAN Pool |
The VLAN pool from which a VLAN is chosen as iSCSI_A VLAN. |
NetApp-vlan-pool |
iSCSI_B VLAN Pool |
The VLAN pool from which a VLAN is chosen as iSCSI_B VLAN. |
NetApp-vlan-pool |
APIC vPC Static Path for Node 1 |
The static path of virtual port channel (vPC) for node 1. |
topology/pod-1/path-101/pathep- [PGr-FAS-A] |
APIC vPC Static Path for Node 2 |
The static path of virtual port channel (vPC) for node 2. |
topology/pod-1/path-101/pathep- [PGr-FAS-B] |
NFS IP Subnet Pool Policy |
The subnet IP pool policy for NFS. |
ip_nfs_subnet_pool |
iSCSI_A IP Subnet Pool Policy |
The IP subnet pool policy to be used for the first iSCSI VLAN. |
NetApp_ISCSI_A_Subnet_pool |
iSCSI_B IP Subnet Pool Policy |
The IP subnet pool policy to be used for the second iSCSI VLAN. |
NetApp_ISCSI_B_Subnet_pool |
SVM mgmt IP Subnet Pool Policy |
The subnet IP pool policy for SVM management. |
netapp_svm_subnet_pool |
VMNet IP Subnet Pool Policy |
The subnet IP pool policy for VM network. |
VMNet_IP_Subnet_pool_policy |
APIC Vlan Pool for Node 1 |
The APIC VLAN pool from which the VLAN ID needs to be assigned for node 1. |
NetApp-Pool |
APIC Vlan Pool for Node 2 |
The APIC VLAN pool from which the VLAN ID needs to be assigned for node 2. |
NetApp-Pool |
Cluster Node 1 Identity |
The identity of the first Netapp C-mode account node. |
ACI2-CMODE-01 |
Cluster Node 2 Identity |
The identity of the second Netapp C-mode account node. |
ACI2-CMODE-02 |
Default Recovery Point |
The recovery point attached to the VNX account. |
RP |
Recovery Point Cluster Identity |
The identity of the recovery point attached to the VNX account. |
RP@1649417791 |
Environment Variable |
Description |
Sample Value |
---|---|---|
IP Pool |
The IP pool that is used to assign the IP addresses between the NetApp datastore and host vmkernel. This environment variable is used for tenant onboarding. |
IP_pool |
PXE Server IP Pool |
The IP pool of the Preboot eXecution Environment (PXE) server. This environment variable is used for bare metal provisioning. |
pxe_ip_new11 |
BMA EPG Entity |
The Cisco UCS Director Bare Metal Agent endpoint group (EPG) entity. This environment variable is used for bare metal provisioning. |
VNX_APIC185@common@BMA- AP@PSC_BMA |
Connected to FI A |
When configuring the physical setup for FlexPod, VSAN is created for the Fabric Interconnect (FI) A - NXOS switch 1 connection and FI B - NXOS switch 2 connection. In BMA provisioning, zoning is configured for FI A - NXOS controller. Choose this environment variable to specify whether a Cisco Nexus switch is connected to Cisco UCS FI A. This environment variable appears for the MDS switch. |
Yes |
Physical domain for LB |
The physical domain that you need to use for the load balancer service. |
Phy_LB_Domain |
Physical LB Path |
The physical path of the load balancer service. |
topology/pod-1/node-101/sys/cdp /inst/if-[eth1/12]/adj-1 |
DPC Static path 1 |
The static path of the first Direct Port Channel (DPC). |
topology/pod-1/paths-302/ pathep-[PC_Policy_1Gb] |
DPC Static path 2 |
The static path of the second DPC. |
topology/pod-1/paths-303/ pathep-[PC_Policy_1Gb] |
Path 1 to L3Out |
The first transit path from the ACI leaf to an external router. |
topology/pod-1/protpaths- 103-104/pathep-[ifs-n3k-b_PolGrp] |
Path 2 to L3Out |
The second transit path from the ACI leaf to an external router. |
topology/pod-1/protpaths- 103-104/pathep-[ifs-n3k-a_PolGrp] |
L2 Physical Domain |
The physical domain for Layer 2. This environment variable is used for configuring EPG transit. |
L2-2960 |
IP Subnet Pool Policy |
The pool policy to be used to get the IP addresses for sub-interfaces. |
Ipsubnetpoolpolicy |
L3 Vlan Pool |
The pool to be used to get the VLAN ID that is used to communicate between the external router and ACI fabric. This environment variable is used to configure the external routed network. |
L3out_Pool |
L2 Transit Vlan Pool |
The pool to be used to get the VLAN ID for the transit EPG. This environment variable is used for creating a transit EPG. |
L2out_Pool |
Node |
The leaf nodes of the APIC account. This environment variable is used for creating a transit EPG. |
topology/pod-1/node-302 |
Routed Sub-Interface Path |
The sub-interface routed path based on the leaf node selection. |
topology/pod-1/paths-303/pathep- [eth1/47], topology/pod-1/paths-303/pathep- [eth1/48], topology/pod-1/paths-302/pathep- [eth1/47] topology/pod-1/paths-302/pathep- [eth1/48] |
Nexus Switches |
The Nexus switches for the APIC account. |
192.0.232.166, 192.0.232.167 |
Loop Back IP Subnet Pool Policy |
The pool policy to be used to get the IP address for Loop Back. |
loop_back_ip_pool_policy |
L3 Domain |
The Layer 3 domain of the APIC account. This environment variable is used to configure the external routed network. |
Phy_L3out_domain |
Router IP Pool |
The IP pool to configure router ID for routers on an external Layer 3 network. This environment variable is used to configure the external routed network. |
IP_pool |
LB Cluster IP Pool |
The IP pool to provide the cluster management IP address for the load balancer device cluster. |
IP_pool |
SVI Path |
The interface connecting APIC to a router on an external Layer 3 network. This environment variable is used to configure the external routed network. |
topology/pod-1/protpaths-101-102 /pathep-[vpcPG_ec1acifwi001-2_DATA |
SVI IP Pool |
The subnet for configuring a switch virtual interface (SVI) on APIC leaves. This environment variable is used to configure the external routed network. |
IP_pool |
Note | The following environment variable are not supported in Cisco UCS Director Release 5.4: IP Subnet Pool Policy, iSCSI PXE Boot Service Profile Template, IQN Pool, Replication Storage Group, PXE Server IP Pool, BMA EPG Entity, Physical domain for LB, and Physical LB Path. |
Physical Compute—Cisco UCS Manager
EMC VNX Unified
VMware Account
APIC (Physical Network)
DPC Static Path 1 (for L2 configuration)
DPC Static Path 2 (for L2 configuration)
L2 Physical Domain (for L2 configuration)
IP Subnet Pool Policy (for L3 configuration)
L3 VLAN Pool (for L3 configuration)
Routed Sub-Interface Path (for L3 configuration)
Node (for L3 configuration)
Nexus Switches (for L3 configuration)
Loop Back IP Subnet Pool Policy (for L3 configuration)
APIC Account
NetApp
Vlan Pool
Physical Domain for NetApp
NFS Vlan Pool
SVM mgmt Vlan Pool
APIC vPC Static Path for Node 1
APIC vPC Static Path for Node 2
NFS IP Subnet Pool Policy
SVM mgmt IP Subnet Pool Policy
VMNet IP Subnet Pool Policy
APIC Vlan Pool for Node 1
APIC Vlan Pool for Node 2
Cluster Node 1 Identity
Cluster Node 2 Identity
iSCSI_A VLAN Pool
iSCSI_B VLAN Pool
iSCSI_A IP Subnet Pool Policy
iSCSI_B IP Subnet Pool Policy
VMware Account
You can define an environment variable that you want to use in the resource group and workflow. The type of the user-defined environment variable is custom.
Ensure that the IP subnet pool policy and VLAN pool policy are defined to use the policy in the environment. Also, you can add a policy in the Add Entry to Environment Variables dialog box when adding a resource group.
Step 1 | On the menu bar, choose . | ||||||||||||||||
Step 2 | Click the
Resource Groups tab.
| ||||||||||||||||
Step 3 | Click Add. | ||||||||||||||||
Step 4 | In the
Create
Resource Group dialog box, complete the following fields:
| ||||||||||||||||
Step 5 | Click Next. | ||||||||||||||||
Step 6 | (Optional)In the
Virtual
Compute screen, choose the virtual compute account and the
interested capabilities and capacities:
| ||||||||||||||||
Step 7 | Click Next. | ||||||||||||||||
Step 8 | In the
Virtual
Storage screen, choose the virtual compute account and the
interested capabilities and capacities.
| ||||||||||||||||
Step 9 | Click Next. | ||||||||||||||||
Step 10 | In the
Virtual
Network screen, choose the virtual network account and the
interested capabilities and capacities:
| ||||||||||||||||
Step 11 | Click Next. | ||||||||||||||||
Step 12 | (Optional)In the
Physical
Compute screen, choose the physical compute account and the
interested capabilities and capacities:
| ||||||||||||||||
Step 13 | Click Next. | ||||||||||||||||
Step 14 | (Optional)In the
Physical Storage screen, choose the physical storage
account and the interested capabilities and capacities:
| ||||||||||||||||
Step 15 | Click Next. | ||||||||||||||||
Step 16 | (Optional)In the
Physical Network screen, choose the physical network
account and the interested capabilities and capacities:
| ||||||||||||||||
Step 17 | Click Next. | ||||||||||||||||
Step 18 | In the
L4L7
Devices screen, choose the firewall specification and load balancer
specification:
| ||||||||||||||||
Step 19 | Click Submit. |
You can delete an account from a resource group only when the account is not associated with other resource group objects, such as a tenant profile.
Step 1 | On the menu bar, choose . | ||||||||||||||
Step 2 | Click the Resource Groups tab. | ||||||||||||||
Step 3 | Select a resource group from the table. | ||||||||||||||
Step 4 | Click Edit. | ||||||||||||||
Step 5 | In the
Edit
Resource Group dialog box, complete the following fields for the
resource group:
| ||||||||||||||
Step 6 | Click Next. | ||||||||||||||
Step 7 | (Optional)The Virtual Compute screen displays the virtual compute accounts added to the resource group. Choose an account and click the edit icon to edit the environment variable, capabilities, and capacities of the account. You can also add an account using the add icon and delete the account using the delete icon. | ||||||||||||||
Step 8 | Click Next. | ||||||||||||||
Step 9 | The Virtual Storage screen displays the virtual storage accounts added to the resource group. Choose an account and click the edit icon to edit the environment variable, capabilities, and capacities of the account. You can also add an account using the add icon and delete the account using the delete icon. | ||||||||||||||
Step 10 | Click Next. | ||||||||||||||
Step 11 | The Virtual Network screen displays the virtual network accounts added to the resource group. Choose an account and click the edit icon to edit the environment variable, capabilities, and capacities of the account. You can also add an account using the add icon and delete the account using the delete icon. | ||||||||||||||
Step 12 | Click Next. | ||||||||||||||
Step 13 | The Physical Compute screen displays the physical compute accounts added to the resource group. Choose an account and click the edit icon to edit the environment variable, capabilities, and capacities of the account. You can also add an account using the add icon and delete the account using the delete icon. | ||||||||||||||
Step 14 | Click Next. | ||||||||||||||
Step 15 | The Physical Storage screen displays the physical storage accounts added to the resource group. Choose an account and click the edit icon to edit the environment variable, capabilities, and capacities of the account. You can also add an account using the add icon and delete the account using the delete icon. | ||||||||||||||
Step 16 | Click Next. | ||||||||||||||
Step 17 | The Physical Network screen displays the physical network accounts added to the resource group. Choose an account and click the edit icon to edit the environment variable, capabilities, and capacities of the account. You can also add an account using the add icon and delete the account using the delete icon. | ||||||||||||||
Step 18 | Click Next. | ||||||||||||||
Step 19 | In the L4L7 Devices screen, edit the firewall specification and load balancer specification as required. | ||||||||||||||
Step 20 | Click Submit. |
Note | You can also add a multi-domain manager account to a resource group using the Add Pod to Resource Group option, provided that the multi-domain manager account is associated with a pod. |
Step 1 | On the menu bar, choose . | ||||||
Step 2 | Click the Resource Groups tab. | ||||||
Step 3 | Click Add Pod to Resource Group. | ||||||
Step 4 | In the
Resource
Group dialog box, complete the following fields:
| ||||||
Step 5 | Click Submit. |
Note | The Manage Tag dialog box displays tags according to the Taggable Entities that are assigned during creation. For more information on how to create a tag, see the Cisco UCS Director Administration Guide. |
The resources need to be grouped based on the resource capabilities. Use a tag to group the resources. You can create the tag library based on the resource type, capacity, quality, and capability of each resource, so as to group the resources in a proper pattern.
Step 1 | On the menu bar, choose . |
Step 2 | Click the Resource Groups tab. |
Step 3 | Choose a resource group. |
Step 4 | Click Manage Tag. |
Step 5 | In the
Manage
Tags dialog box, click the
+ icon to add a tag.
Alternatively, you can click Add Tags in the Resource Groups tab. |
Step 6 | In the
Manage
Tag dialog box, choose a tag and click the pencil icon to edit a
tag.
|
Step 7 | In the
Manage
Tag dialog box, choose a tag and click the
cross icon to delete a tag.
Alternatively, you can click Delete Tags in the Resource Groups tab. |
Step 8 | Click Submit. |
Step 9 | Click OK. |
Note | You cannot delete a resource group that is in use. |
A tenant is a customer who uses resources in Cisco UCS Director to deploy and manage their application.
When a customer wants to deploy an application in Cisco UCS Director, the customer is onboarded as a tenant and the infrastructure is provided to deploy the application, using the APIC use case workflows.
Note | If the disaster recovery support is enabled for the tenant, the resource groups of the primary site and the disaster recovery site are displayed. |
To view the resource entity, reserved resources, and resources available for use in tenant and container, choose the resource group and click View Details. The following tabs appear:
Resource Entity—Displays the details of the entity in the resource group. The details include name, type, component, resource group, tenant resource allocation type, application resource allocation type, container, and state of the resource entity.
Tenant Resource Limits—Displays availability of both virtual and physical resources in a tenant. The resources reserved during tenant onboarding are displayed along with the used and available resource values. The VDCs Limit column specifies the maximum number of containers that are reserved for the tenant. The Available Number of VDCs column represents the number of containers that are available for provisioning. The physical resource limits display the blades that are reserved as part of tenant onboarding, along with the number of blades used for bare metal provisioning.
Note | If a container is created without a resource limit, the value of the virtual resources is displayed as Not Set. |
Private Network—Displays the private networks created for the tenant. Choose a private network and click View Details to view the supernet and subnet pools of the private network. The Supernets tab lists the supernets available for the tiers. The Subnets tab displays the sub-network pool that is used for load balancer configuration during the container deployment.
The tenant-specific and container-specific resource limits assist in provisioning VMs and BMs.
A service offering defines the resources required to provision an application. Each service offering must include one or more service classes that represents the capacity and capability needed for the following resource layers:
Virtual Compute
Virtual Storage
Virtual Network
Physical Compute
Physical Storage
Physical Network
Layer 4 to Layer 7 Services
When you define a service offering, you can specify the usage of resource groups as one of the following:
Shared—The resources are shared among the applications or tenants.
Dedicated —The resources are dedicated to a single application or tenant.
Based on the capacity, capability, and resource tags defined in the service offering, the resource groups are filtered and the matching resource groups are selected for further processing in the tenant onboarding and application deployment.
If tag-based resource selection is required for any of the resources, ensure that the tags are created in the tag library and are associated with the respective object. So that, the tags are listed when you define resource tag for service class. For more information on how to create a tag, see the Cisco UCS Director Administration Guide.
Step 1 | On the menu bar, choose . | ||||||||||||||||||||||||
Step 2 | Click the
Service
Offering tab.
| ||||||||||||||||||||||||
Step 3 | Click Add. | ||||||||||||||||||||||||
Step 4 | In the
Add
Service Offering dialog box, complete the following fields:
| ||||||||||||||||||||||||
Step 5 | Click Next. | ||||||||||||||||||||||||
Step 6 | In the Service Class screen, click the + icon to define the service class that the service offering has to provide. | ||||||||||||||||||||||||
Step 7 | In the
Add Entry
to Service Class dialog box, complete the following fields:
| ||||||||||||||||||||||||
Step 8 | Click Submit. The service class information is added to the table. You can define multiple service classes for the service offering. | ||||||||||||||||||||||||
Step 9 | Click Submit. |
Ensure that the tags are created in the tag library and the tags are associated with the respective object. So that, the tags are listed when you define resource tag for service class. For more information on how to create a tag, see the Cisco UCS Director Administration Guide.
Step 1 | On the menu bar, choose . | ||||||||||||||||||||||
Step 2 | Click the Service Offering tab. | ||||||||||||||||||||||
Step 3 | Choose the service offering that you want to clone. | ||||||||||||||||||||||
Step 4 | Click Clone Service Offering. | ||||||||||||||||||||||
Step 5 | In the
Clone
Service Offering dialog box, complete the following fields:
| ||||||||||||||||||||||
Step 6 | Click Next. | ||||||||||||||||||||||
Step 7 | In the Service Class screen, click the + icon to define the service class that the service offering has to provide. | ||||||||||||||||||||||
Step 8 | In the
Add Entry
to Service Class dialog box, complete the following fields:
| ||||||||||||||||||||||
Step 9 | (Optional)Click the pencil icon to edit the values of an already configured service class. | ||||||||||||||||||||||
Step 10 | (Optional)Click the cross icon to delete an already configured service class from the service offering. | ||||||||||||||||||||||
Step 11 | Click Submit. |
Note | Do not edit the service offering that is mapped to a resource group and tenant profile. If you edit the service offering that is mapped to a resource group and tenant profile, the tenant that is onboarded using the service offering will be affected. |
Ensure that the tags are created in the tag library and the tags are associated with the respective object. So that, the tags are listed when you define resource tag for service class. For more information on how to create a tag, see the Cisco UCS Director Administration Guide.
Step 1 | On the menu bar, choose . | ||||||||||||||||||||||
Step 2 | Click the Service Offering tab. | ||||||||||||||||||||||
Step 3 | Choose the service offering that you want to edit. | ||||||||||||||||||||||
Step 4 | Click Edit. | ||||||||||||||||||||||
Step 5 | In the
Modify
Service Offering dialog box, complete the following fields:
| ||||||||||||||||||||||
Step 6 | Click Next. | ||||||||||||||||||||||
Step 7 | In the Service Class screen, click the + icon to define the service class that the service offering has to provide. | ||||||||||||||||||||||
Step 8 | In the
Add Entry
to Service Class dialog box, complete the following fields:
| ||||||||||||||||||||||
Step 9 | Click Submit. |
Note | You cannot delete a service offering that is in use. |
Tenant profiles represent the pairing of one or more service offerings with one or more resource groups. Each tenant profile defines the characteristic of infrastructure requirements and application requirements.
You can create a tenant profile to meet each possible combination of customer and application. You can associate a tenant profile with multiple service offerings and choose a resource group for each service offering. A tenant profile can be shared by more than one tenant.
The DR service is enabled.
The resource group is configured as primary.
The primary resource group is mapped with the secondary resource group.
The primary and secondary resource groups have same number of accounts.
The resources required for the tenant are available in both the primary and secondary resource groups.
For more information on how to enable DR service and set the resource group as primary or secondary, see Adding a Resource Group.
Step 1 | On the menu bar, choose . | ||||||||||||||
Step 2 | Click the
Tenant
Profile tab.
| ||||||||||||||
Step 3 | Click Add (+). | ||||||||||||||
Step 4 | In the
Add
Tenant Profile dialog box, complete the following fields:
| ||||||||||||||
Step 5 | Click Next. | ||||||||||||||
Step 6 | Click the
Add
(+) icon to choose a resource group for a specific service
offering. For each service offering selected for the tenant profile, you can
select the resource group.
The resource groups that match the specified requirement of the tenant profile are displayed.
| ||||||||||||||
Step 7 | Click Submit. |
While creating a tenant profile, you associate a tenant profile with multiple service offerings. The service offerings list is displayed based on the matching resource group availability. If you receive an error message instead of the service offerings list, take action according to the error message.
For example, on receiving the error message: Host is not mounted on UCS servers, check for the following:
Verify that Cisco UCS server is managed by Cisco UCS Director. To check the status of Cisco UCS servers, choose , choose the Cisco UCS Manager account, and click the UCS Discovered Servers tab.
Verify that the vCenter account and Cisco UCS Manager account are in the same resource group, and host in the vCenter account is mounted on the Cisco UCS Manager account.
Verify that the Cisco UCS Manager accounts that are available in Cisco UCS Director each have a unique IP address. If more than one account exists with the same IP address, remove one of the accounts that is not part of the resource group.
Step 1 | On the menu bar, choose . | ||||||||||||
Step 2 | Click the Tenant Profile tab. | ||||||||||||
Step 3 | Choose the tenant profile that you want to clone. | ||||||||||||
Step 4 | Click Clone. | ||||||||||||
Step 5 | In the
Clone
Tenant Profile dialog box, complete the following fields:
| ||||||||||||
Step 6 | Click Next. | ||||||||||||
Step 7 | Click the
+ icon to choose a resource group for a specific
service offering. For each service offering selected for the tenant profile,
you can select the resource group.
The resource groups that match the specified requirement of the tenant profile are displayed.
| ||||||||||||
Step 8 | Click Submit. |
Step 1 | On the menu bar, choose . | ||||||||||||
Step 2 | Click the Tenant Profile tab. | ||||||||||||
Step 3 | Choose the tenant profile that you want to edit. | ||||||||||||
Step 4 | Click Edit. | ||||||||||||
Step 5 | In the
Edit
Tenant Profile dialog box, complete the following fields:
| ||||||||||||
Step 6 | Click Next. | ||||||||||||
Step 7 | Click the
+ icon to choose a resource group for a specific
service offering. For each service offering selected for the tenant profile,
you can select the resource group.
The resource groups that match the specified requirement of the tenant profile are displayed.
| ||||||||||||
Step 8 | Click Submit. |
Note | You cannot delete a tenant profile that is in use. |