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 consist of the following topics:
As a Site Administrator you can create a Service Administrator who is well aware of the UCS Director, CloudCenter and UCS PM applications. The Service Administrator role creates and manage UCSD, CloudCenter, and UCS PM integrations. This role is also responsible for creating and mapping custom templates for the UCSD services and CloudCenter applications.
The very first Service Administrator must be created by ordering the service Create Service Administrator from Service Catalog. Assign a person as Service Administrator from the Search for Recipient pop up and click Submit. This Service Administrator can then assign the same capabilities to others by ordering the Create Service Administrator service.
In case you have upgraded from previous version of Prime service Catalog and have already integrated with UCSD, then you must map the user who manages the integrations with the Service Administrator role.
Cisco Prime Service Catalog integrated with UCS Director provides single self-service ITaaS catalog for the self-service provisioning and lifecycle management of VMs in the private and hybrid cloud workloads. You can provide services such as provisioning virtual machines on a private cloud using UCS Director and perform the lifecycle operations on these public and private VMs. This section covers the infrastructure services such as virtual machines, fenced containers, Virtual Application Container Services (VACS), and APIC Container Catalog on UCS Director.
Note |
|
Note | Prime Service Catalog currently does not support the popup table input type for UCS Director advance catalog workflow. |
You receive an email notification when you create a VDC or a standard virtual machine. A VDC can be an APIC, fenced, or VACS container, and a virtual machine can be a standard virtual machine or a cloned virtual machine. You also get an email notification while adding a virtual machine to a Fenced and VACS container.
When you order a new VDC successfully, an email notification is sent out, which includes VDC service item details, VDC subscription data, and specific details of the VDCs such as name, display name, description, cloud name, and status of the VDC with its corresponding virtual machines. You can view the details of all the virtual machines of a particular VDC.
For information on VDC creation, see the "Virtual Data Centers" section in the Cisco Prime Service 11.1.1 User Guide.
Set the SMTP properties in the Administration module. These properties are, "Mail Server Address", "Mail Server Port", and "Support Email Address".
FTL files must adhere to the following guidelines:
FTL files are well formed. This includes naming the tags properly, ensuring that every opening tag has a closing tag, ensuring that at least one "to" address exists, in addition to the other precautions mentioned above.
FTL files must be placed in some custom template folder and the fully qualified path name to the folder must be specified in Administration > Settings > Path of the folder containing the FTL files. The path should navigate to the folder containing the FTL files and not the files itself. By default, these FTL files are available in the "RequestCenter.war/WEB-INF/classes/config/templates/ folder.
The FTL file path must be in Linux convention (which is a/b/c/d and not a\b\c\d) andmust mandatorily end with '/'.
For clustered environments, the URL ObjectCache.Application.URL must be hardcoded in the Newscale.properties file.
For clustered environments, each node must have the FTL files in the same folder, and this folder must exist in every node.
create_vdc_fen.ftl—For creating Fenced Container VDC
create_vdc_apic.ftl—For creating APIC Container VDC
create_vdc_vacs.ftl—For creating VACS Container VDC
add_vm_fen.ftl—For adding a VM of a Fenced container
add_vm_vacs.ftl—For adding a VM to a VACS container
vm_operation.ftl—For cloning a VM of a Fenced container and an APIC container, and creating a Standard VM.
You can view, modify, show, hide, or remove the FTL file according to your requirement, but do not change the naming convention of the FTL files, as mentioned above. You can view all the details that are included in the email notification.
Note | By default, the <from> field has ToBeFilled as the value. If you want to use the <from> field, edit this field with an appropriate and valid email address. If you do not want to use the <from> field, remove this field or comment it out in the FTL. If the FTL is used as is as provided out of the box, then it would result in an error, since ToBeFilled is not a valid email address. |
Apart from the customizations mentioned above, you can also add any static text inside of the FTL template. For this, no special tags need to be used. You can just mention the static text as is. The "subject" field of the email template can also be customized with a custom subject line for the email.
|
Steps |
Topics |
---|---|---|
Step 1 |
Integrate UCS Director with Prime Service Catalog. |
Integrating UCS Director (UCSD) or VACS with Prime Service Catalog |
Step 2 |
Discover the IaaS entities from UCS Director. |
|
Step 3 |
Set up automatic or manual synchronization with UCS Director. |
Managing UCSD or ICFB Synchronization |
Step 4 |
|
Based on the permissions, end users can now order the hybrid cloud services and perform lifecycle operations on the provisioned containers and virtual machines. For more information on ordering these services, and on the available lifecycle operations for the UCS Director entities, see Cisco Prime Service Catalog 12.0 User Guide.
Container templates, container catalogs, standard catalogs, and advance catalogs from UCS Director
Container catalog services and container template services from VACS. VACS template services includes a CSR Virtual Machine, VSG Virtual Machine, and application Virtual Machines.
If you are planning to connect to a UCS Director instance that is integrated with an LDAP, do the following in Prime Service Catalog :
Failing to map the above attributes may result in duplicate user accounts in Prime Service Catalog after the UCS Director import.
Step 1 | Login to Prime Service Catalog as the Service Admin user. | ||||
Step 2 | From the main
menu, choose
Advanced Configuration > Integrations
and click
New
Integrations.
| ||||
Step 3 | Select Cisco UCS Director. The client/server side validation happens, on successful creation it navigates to Manage Integrations page. | ||||
Step 4 | Enter the details to connect to the server where UCS Director is installed. For https connections, import the root CA certificate of the UCS Director server. Copy the content of the root CA certificate of the server and paste it in the text area. If the root certificate is a chain of certificates, paste the content one below the other. The connection would fail, in case the SSL certificate of the server becomes invalid or untrusted. You can skip the certificate validation by selecting the Skip Certificate Validation option. | ||||
Step 5 | Check Sync User with IaaS option to sync this user with IaaS. | ||||
Step 6 | Check
Enable
Poller if you want to configure automatic polling for the subsequent
connections with UCS Director connections.
| ||||
Step 7 | Click Create Integration. | ||||
Step 8 | Select the connection from the Integrations page to and choose Test Connectivity option from Manage Integration drop-down to authenticate the credentials. | ||||
Step 9 | After the
connection is successful, click
Import
all Objects
option from
Manage
Integration drop-down. . The system starts to discover the data from UCS
Director. For more information on data discovered from UCS Director, see
Cisco Prime Service Catalog
12.0 Designer Guide.
You can now set the timeout period for UCS Director synchronization initiated using the Connect and Import option. Set the ucsddata.killSession parameter in the newscale.properties file to set the timeout. The UCS Director synchronization will end after this set period is elapsed.
| ||||
Step 10 | On the
Discovered
Panel, you can:
Deleting a UCS Director connection As a Service Admin, you can delete a UCS Director connection by selecting the Remove option either from Integrations > Setting drop down or Manage Integrations page > Manage Integrations drop down. This option will delete the connection along with its imported entities such as virtual machines, VDCs, containers, templates, catalogs, and workflows. However, entities such as users, user groups, images, template definitions, and organization units will remain in Prime Service Catalog. |
If you are using Prime Service Catalog in the Cisco ONE Enterprise Cloud Suite, you must enable single Sign-on (SSO) when integrating Prime Service Catalog with UCS Director.
Caution | You cannot configure both LDAP and SAML configured for SSO login in Prime Service Catalog. If you wish to use LDAP SSO, the SAML SSO must be manually disabled, failing which will lead to incorrect login behavior. To disable SAML login, go to Administration > Settings > Customizations. From the Common section, turn off the Enable SAML setting and click Update. |
Prime Service Catalog and UCS Director use LDAP authentication to handle permissions for catalog items and service items. With LDAP integration, group permissions for the catalog items and virtual machines in UCS Director are synchronized with the service items and catalog items in Prime Service Catalog. For example, if a specific group owns a virtual machine in UCS Director, the users in that group can view the same virtual machine in Prime Service Catalog. In addition, if a specific group can access a catalog item in UCS Director, the users in that group can order the same catalog item from Prime Service Catalog.
Use the procedure below to enable the single sign-on:
Step 1 | Set up LDAP integration in Prime Service Catalog. For more information, see the Configuring LDAP integration section in Cisco Prime Service Catalog 12.0 Integration Guide. | ||
Step 2 | Set up LDAP
integration in UCS Director. For more information, see the
LDAP
Integration section in
Cisco UCS Director 5.3
Administration Guide.
| ||
Step 3 | Integrate UCS
Director with Prime Service Catalog. For instructions on integrating UCS
Director with Prime Service Catalog, see
Integrating UCS Director (UCSD) or VACS with Prime Service Catalog.
|
You can automatically discover UCS Director instances at scheduled intervals using the scheduler. Use the below procedure to configure the scheduler.
Step 1 | Edit the
following properties files. These files can be located in the
RequestCenter.war/WEB-INF/classes/config
directory.
| ||
Step 2 | In
UCSD
Scheduler
option.
page, select the
|
If Prime Service Catalog and UCS Director are integrated with LDAP, it is recommended to manually poll users information using the web interface whenever the user roles are changed in UCS Director. This is to ensure synchronization of the user’s RBAC permission to Prime Service Catalog services with the changes made in UCS Director.
You can manually import UCS Director instances using the UCS Director Integration page. When you perform this process, all entities including users and roles are synchronized.
This process is used in the following scenarios:
You can discover the reporting data for all VMs from the UCS Director at scheduled intervals, using the scheduler, automatically. You can also configure the number of days, months, weeks and beginner of the week for which the data needs to be imported and displayed in the Prime Service Catalog. Use the following procedure to configure the scheduler and the reporting data settings.
Based on the permissions granted to an end user, the discovered services from UCS Director becomes orderable in the Service Catalog module.
To understand the UCS Director groups and roles mapping to Prime Service Catalog groups and roles, see Prime Service Catalog Roles Mapping with UCSD and ICFB Roles and Users and User Groups Imported from UCSD and ICFB.
Depending on the UCS Director integration, you can discover standard catalogs, container catalogs, and container templates services for end-user provisioning and maintenance of VMs on private and public cloud. Using these services, end users can:
Order services created based on service container catalog, standard catalog, advanced catalog, and fenced container templates from UCS Director.
Discover the Services from UCS Director by integrating with the UCS Director instance. For more information on integrating UCS Director, see Integrating UCSD or ICFB with Prime Service Catalog.
Prime Service Catalog provides out-of-box templates using which you can map to the UCSD services. The template service defines the way the entities of UCSD appear as a service in Service Catalog module. In UCSD, templates can be mapped at catalogs or templates level.
Custom templates can be created based on the out-of-box UCSD templates provided by Prime Service Catalog and used for mapping to the UCSD services. For more information on creating custom templates see, Create Custom Templates in Cisco Prime Service Catalog Designer Guide.
To map a template:
Step 1 | Select the connection from the Integrations page, choose Manage Connection from the settings. |
Step 2 | Click Objects in the Discovered panel. |
Step 3 | Choose the Template or Catalog from the left hand side and for the selected entry, choose the custom template from the Select Base Template drop-down list. |
Step 4 | You can do one
of the following from the settings option:
|
Note | In a single pane of glass, where Prime Service Catalog, UCS Director are connected to LDAP:
|
When Prime Service Catalog connects to a UCS Director for the first time, Prime Service Catalog creates a:
Where <ID> is the 3-letter identifier of the UCS Director server. This group will be the parent group for all groups imported from this UCS Director server.
Where <ID> is the 3-letter identifier of the UCS Director server. There will be group for each group in the UCS Director. All such groups are grouped under the parent group. Users belonging to various groups in the UCS Director are imported to the respective groups in Prime Service Catalog.
All the imported users from the UCS Director are assigned an Organizational Unit (OU) in Prime Service Catalog.
During the subsequent connections, Prime Service Catalog checks for group membership changes and updates the records accordingly.
Note | For container templates, container catalogs, standard catalogs, and advance catalogs services created in Prime Service Catalog for UCS Director:
|
Prime Service Catalog creates the following system-defined roles for the UCS Director roles it discovers. The following table lists the mapping of the UCS Director to Prime Service Catalog system-defined roles.
UCS Director Roles |
Prime Service Catalog System Defined Roles |
Description |
---|---|---|
System Admin |
UCSD Sys Admin |
UCSD Sys Admin user can view the details of Containers, vDC's and VM's as service items in My Products and Services based on the Group permissions assigned to each of the UCS Director Service Item in Service Item Manager. Only users with this role can order Container Template Services. |
All Policy Admin |
||
Computing Admin |
||
Service End-User, Group Admin, Operation roles |
UCSD End User |
UCSD End User can view the details of Containers, vDC's and VM's as service items in My Stuff based on the Group permissions assigned to each of the UCS Director Service Item in Service Item Manager. Users with this role can order services based on the group to which user belongs and catalogs which are assigned to a group in UCS Director. |
All other roles |
UCSD Operator |
Users with this role can only view and use the self-service portal but cannot order the services. |
Note | In a single pane of glass, where Prime Service Catalog, UCS Director are connected to LDAP:
|
The new service will be displayed in the Service Catalog module based on the category you have selected.
Discover the Services from UCS Director by integrating with the UCS Director instance. For more information, see Integrating UCSD or ICFB with Prime Service Catalog.
Step 1 | Choose Advanced Configuration > Integrations and select the connection from the Integrations page. |
Step 2 | Click Manage Integration option from drop down and click on the Services tab in the Discovered panel double-click on the service. |
Step 3 | In the Details panel, do the following: |
Step 4 | Click Save. |
This feature enables service providers to use Cisco ONE Enterprise Cloud Suite to provide multi-tenant Infrastructure as a Service (IaaS) on ACI. The components required for this functionality are: Prime Service Catalog, UCS Director (in Managed Service Provider mode), and ACI.
The Tenant Management module in Prime Service Catalog provides infrastructure services to multiple tenants quickly and efficiently. Using this module, tenants can manage their own set of services, and offer these infrastructure services to their end users. A tenant can contain several organizations and each organization can contain several users.
The tenant workflow (for example: create, update, and delete tenants), VDC, and VM operations are executed through Advanced and Service Container Catalog workflow in UCS Director. Prime Service Catalog creates services for these advance and service container catalog workflows during the UCS Director discovery process. For this feature to work seamlessly, a site administrator must map these UCS Director discovered services to the Tenant Management workflow in Prime Service Catalog. For more information, see Setting Up Tenant Management Module and Mapping Tenant and VDC Workflows from UCSD.
For seamless multi-tenant IaaS operations, an administrator must ensure that multi-tenant IaaS-related objects are created and configured in UCS Director. An administrator need to configure only four of these multi-tenant IaaS workflows. Remaining workflow are pre-defined and configured during the installation process.
Note | Do not use hyphen in UCS Director Advance Catalog name. This is to avoid the synchronization issues after integrating with Prime Service Catalog. |
UCS Director Workflow |
UCS Director Advance or Service Container Catalog Fields |
---|---|
VNX Tenant Onboarding |
|
Update Tenant |
|
APIC Service Container catalog |
No specific fields to configure for APIC Service Container catalog. Make sure an APIC Service Container catalog is available in UCS Director for VDC workflows. |
Firewall Rule Action Configuration |
A site administrator must perform the following steps for seamless multi-tenant IaaS operations.
Step 1 | Integrate Prime Service Catalog with UCS Director and discover the infrastructure entities from UCS Director. For instructions, see Integrating UCS Director with Prime Service Catalog. |
Step 2 | Map the Advanced Catalog/Container Catalog services from UCS Director to the Prime Service Catalog workflow. For more information, see Mapping Tenant and VDC Workflows from UCSD. |
Step 3 | Invoke workflow for creating tenants in Prime Service Catalog. For more information, see Onboarding a Tenant. |
When Prime Service Catalog is integrated with UCS Director, the discovery process creates services based on UCS Director Advanced Catalogs and APIC service container catalog. The advance and the APIC service container catalogs in UCS Director are used for publishing workflow for creating, managing a tenant and creating a VDC respectively.
Note | Only four of the Prime Service Catalog tenant management workflows need mapping from an administrator. The remaining workflows are pre-defined and are configured during the installation process. For information on the workflows that needs mapping in Prime Service Catalog, see the table below . |
Integrate Prime Service Catalog with UCS Director instance that is in the Service Provider mode. For more information, see Integrating UCSD with Prime Service Catalog.
Step 1 | Discover the UCS Director entities in Prime Service Catalog. | ||
Step 2 | On the discovery page in Prime Service Catalog, select a workflow from the Manage Workflows section and click to open manage workflow page. , and select an advance or a service container catalog service from the Services drop down on the right-hand side. For information on which services to select in this drop down, see the table below. | ||
Step 3 | Based on the
type of advance or service container catalog service selected in the previous
step, select the values for the remaining workflow attributes and click
Save.
| ||
Step 4 | Navigate to
Tenant
Management module and invoke workflow for creating tenants. For VDC and
Firewall Rule Workflows, navigate to
Service
Catalog module
My Products
& Services >
Virtual Data
Centers to create VDC and add Firewall Rule.
The status of the service request is displayed as Completed, if the operation on UCS Director is successful.
|
Prime
Service Catalog Workflow
Create
Tenant
Advance
Catalog based on
VNX
Tenant Onboarding workflow
Manage
Tenant
Advance
Catalog based on
Update
Tenant workflow
Create VDC
Advance
Catalog based on any
APIC
Service Container Catalog
Create
Firewall
Advance
Catalog based on
Firewall Rule Action Configuration workflow
UCSD Advance/Service
Container Catalogs
As a site administrator, you can create a tenant administrator. A Tenant administrator can create and manage users, Organization Units (OUs), and VDCs. In addition, the tenant administrator can specify which tasks the users can perform on their virtual machines and services, and can place quotas on computing resources and virtual machines.
When you create a Tenant Admin, the Organization and Tenant User dashlets are automatically created and associated for that Tenant.
Note | These prerequisites are also applicable for creating a VDC. |
Add a UCS Director connection that is in the Manage Service Provider (MSP) mode. You can connect to a UCS Director instance in
and click New Integrations.Map the advance/service container catalog services with the Prime Service Catalog workflows. For more information, see Mapping Tenant and VDC Workflows from UCSD.
UCSD Agent must be up and running in the Service Link module.
Step 1 | Log in as Site Administrator. | ||
Step 2 | Go to Tenant Management. | ||
Step 3 | Click Add Tenant from the Tenant Management Dashboard. | ||
Step 4 | In the
Tenant
Information tab, enter details such as name of the tenant, address,
disaster recovery protection information, L2 VLAN ID, L2 IP Subnet, Tenant IP
Pool, and Resource Selection (For ND).
| ||
Step 5 | Specify the
reservation details for vDC in the
Quota
Management tab (based on the vDC template).
UCS Director uses this information for resource allocation and to provision that tenant. The Tenant Administrator can then create and manage OUs, vDC, and users for each of the associated Tenant. When the Tenant is in the Being provisioned status, the Tenant Admin icon will be disabled on Tenant Dashboard restricting the user (site admin) to view the User Management. An information icon 'i' is displayed in Status in the Tenant Dashboard and when clicked, displays an overlay of requisition, provisioning workflow summary, comments with date and timestamp. |
You can also search and edit only the quota/capacity details (and not any other details associated to a VDC) by navigating to
. The Tenant Administrator can navigate to Organization, Users, and VDCs from the User Dashboard.Note |
|
The following instructions are specific only to the customers who have access to the Tenant Management module.
To delete a tenant from the Tenant Management dashboard, make sure that you delete all the physical servers, VMs, VDCs, Organization users, or any service items associated with that tenant. Follow the steps in the same sequence as listed below.
There might be slight variations in steps depending on the database you are using.
Step 1 | (As a Tenant Administrator) Go to Service Item Manager > Manage Service Items, then click the delete icon to delete physical servers for the tenant. |
Step 2 | Go to My Products & Services > Virtual Data Center, then select the VDCs corresponding to the tenant. |
Step 3 | Delete the load balancer. To delete, select the Load Balancer from the Load Balancer tab and click the delete icon. |
Step 4 | Delete the Firewall rule. To delete, select the Firewall rule from the Firewall Rule tab and click the delete icon. |
Step 5 | Delete the VMs. To delete, click the Virtual Machines corresponding to the VDC. On the right of each VM, click the gear icon to delete it. |
Step 6 | Delete the VDCs. Click the delete icon on the existing VDC to delete it. |
Step 7 | (For Oracle only ) Go to the Administration > Utilities and purge all the requisitions for the specific users. |
Step 8 | Go to the
Organisation Designer module and do the following:
|
Step 9 | (As a Site Administrator) Go to the Tenant Management module and click the delete icon next to the tenant, which you want to delete. |
Cisco Prime Service Catalog offers a direct integration with Cisco CloudCenter. You can set up the connection from Prime Service Catalog to CloudCenter, resulting in the automated import of the application deployment workflows, ready to be published to the catalog.
CloudCenter lets users define cloud-agnostic blueprints of their multi-tier applications and then deploy them to private, public, or hybrid clouds based on cost and performance metrics provided by CloudCenter. CloudCenter can manage the lifecycle of an application with auto-aging policy and the ability to scale-out and scale-in individual tiers of a multi-tier app based on application performance.
|
Steps |
Topics |
---|---|---|
Step 1 |
Integrate CloudCenter with Prime Service Catalog. |
|
Step 2 |
Discover application profiles. |
|
Step 3 |
Configure search facets, permissions, and presentation for hybrid cloud provisioning services in Prime Service Catalog. |
Configuring Permissions and Presentation for CloudCenter Services |
Based on the permissions, end users can now deploy the application services.
Prerequisites
Step 1 | Login to Prime Service Catalog as the Service Administrator (or Site Administrator) user. |
Step 2 | From the main menu, choose New Integrations. and click |
Step 3 | Select Cisco CloudCenter. |
Step 4 | Enter the
details and click
Create
Integration to connect to the CloudCenter server.
|
Step 5 | Choose Test Connectivity option from Manage Integration drop-down to validate the credentials and the server details. |
Step 6 | After the connection is successful, click Import all Objects option from Manage Integration drop-down . The system starts to discover and import the published CloudCenter application profile . |
Step 7 | In the
Discovered
panel, you can:
|
You can delete a CloudCenter connection by choosing Remove option from Manage Integration or by choosing Remove option from Settings drop down in the Integrations page. This option will delete the connection along with its imported entities such as applications and activation profiles.
Security Assertion Markup Language (SAML) can be used with Prime Service Catalog to provide external authentication of users and a means of SSO (Single Sign-On).
As a prerequisite to integrate Prime Service Catalog with CloudCenter, you must enable and configure SAML SSO.
Perform the following procedure to enable single sign-on:
Step 1 | Enable SAML on Prime Service Catalog: |
Step 2 | Configure SAML support in Prime Service Catalog. For more information, see the Configuring SSO Using SAML section in Cisco Prime Service Catalog 12.0 Integration Guide. |
Step 3 | (Optional) Integrate CloudCenter with Prime Service Catalog. For more information, see Integrating CloudCenter with Prime Service Catalog. |
Based on the permissions granted to the user, the discovered application services become available in the Service Catalog module. Using the options described in the below procedure you can grant deploying permission of these services to OUs, users, groups or roles in prime Service Catalog, or customize the services by adding more presentation details, descriptions, categories, etc. However, the services are ready to be deployed as is without any additional definitional changes.
Discover the Application Profiles from CloudCenter by integrating with the CloudCenter. For more information on integrating, see Integrating CloudCenter with Prime Service Catalog.
Step 1 | Select the connection from the Integrations page and click Services in the Discovered panel or select Manage Integration option from Settings drop down and click Services in the Discovered panel. | ||
Step 2 | Select the service to be customized. | ||
Step 3 | In the
Details
panel, enter Service Name, Description, and add Categories. And click
Save.
| ||
Step 4 | In the Presentation panel, click Attach, to select an image to be associated with the service or select Image URL to enter the URL of the image. Default option selected is Image File . | ||
Step 5 | Select an image from the list of Select Image window and click Add . Cisco provides a number of images out-of-box that you can assign to the service. You can also upload an image to be used for the service. | ||
Step 6 | Enter a description for the service by selecting the Overview or Service Form options, and click Save . | ||
Step 7 | In the Facets panel, choose the required options and click Save. | ||
Step 8 | In the Permissions panel, do the following: | ||
Step 9 | Click Save. The new service will be displayed in the Service Catalog module based on the category you have selected. |
You can set a base template for the services for a chosen connection or the application profile. This template defines the way the application appears as a service in Service Catalog module.
The templates can be mapped at two levels:
Connection level: You can map the template when you add a new connection or modify the connection later to map a new template. On import all the applications associated with that connection inherit the template assigned at the connection level.
Note | Only those template will continue to inherit connection level template which were inheriting before connection level template is changed. |
Note | It is recommended to apply the custom templates at application profile level only in the case current template for that application profile is updated and you want the service to have those changes. |
To map templates at application profile level follow the below procedure:
With SAML support enabled, with the first login of the IDP user a corresponding Prime Service Catalog user is created. When a user joins or creates a Tenant for the first time, this user is pushed in to CloudCenter and is associated to the default Activation Profile.
As a Service Administrator you can add a connection to Performance Manager server. Data points for performance reports are generated in UCS Performance Manager. Prime Service Catalog imports these data points through an API call functionality. For each Performance Manager application profile, Prime Service Catalog automatically creates a service. You can view the performance report for a vDC for an hour, 6 hours, and 1 week. You can also customize the time interval for which you need the performance report. For more information on performance reports, see section Viewing Performance reports in Cisco Prime Service Catalog User Guide.
Ensure to have UCSD connection established and VMs created by UCSD user in Prime Service Catalog.
Step 1 | Login to Prime Service Catalog as the Service Administrator user. | ||
Step 2 | From the main menu, choose Advanced Configuration > Integrations and click New Integrations. | ||
Step 3 | Select Cisco UCS Performance Manager. | ||
Step 4 | Enter the details to connect to the server where UCS Performance Manager is installed. For https connections, import the root CA certificate of the UCS Performance Manger server. Copy the content of the root CA certificate of the server and paste it in the text area. If the root certificate is a chain of certificates, paste the content one below the other. The connection would fail, in case the SSL certificate of the server becomes invalid or untrusted. You can skip the certificate validation by selecting the Skip Certificate Validation option. | ||
Step 5 | Click Create Integration. | ||
Step 6 | Select the
connection from the Integrations page to and choose
Test
Connectivity
option from
Manage
Integration drop-down to authenticate the credentials.
|
As a Service Administrator, you can delete a UCS Performance Manager connection by selecting the Remove option either from Integrations > Setting drop down or Manage Integrations page > Manage Integrations drop down. This option will delete the connection along with its imported entities such as application and activation profiles, clouds, and deployment environments..