Change management integrations provide you the ability to manually generate change request tickets from Cloud Cost Management (CCM). CCM displays recommendations for idle resources and right sizing on the Cost Saving Opportunities page. From there, you can choose to manually submit a request to a change management system (CMS) directly from CCM.
Other than submitting the change request, Virtana Platform does not interact with the change management system. Any other actions involving the request must be done within the change management system itself.
Only one instance of a given change management system can be installed, but you can install multiple types of CMSs. For example, you can install both ServiceNow and Jira, but only one instance of each.
When you add the integration, you select the fields from the CMS that you want as Default Issue Settings in Virtana Platform when making a change request. You can then use policies to finely tune the field settings for various types of change requests.
See the Cloud Cost Management guide for more information about submitting change requests.
-
First, you must configure a web services user and add Virtana Platform to the application registry in ServiceNow. Then, copy the Client ID and Secret from ServiceNow.
-
Enter the ServiceNow credentials in the integration setup form in Virtana Platform and complete the form.
Related Topics
-
First, you must generate and copy a Jira API token.
-
Then, you must access the integration setup form in Virtana Platform, paste in the token, and complete the form.
Related Topics
Before you can add a ServiceNow integration in Virtana Platform, you must perform some configuration tasks in ServiceNow.
About This Task
You must create a non-interactive user account in ServiceNow that provides access to ServiceNow APIs through webservices. This user cannot log in directly to the ServiceNow system.
You must also add Virtana Platform to the ServiceNow Application Registry to establish OAuth access.
For further details, see the ServiceNow documentation.
-
Log in to the ServiceNow Service Management console as an administrator.
-
In the left navigation pane, search for "user admin" and select User Administration > Users from the results.
-
Complete the User form, selecting Web service access only and ensure Active is enabled.
-
Under the Roles tab, click the Edit button.
-
Add the itil and personalize_dictionary roles, then click Save.
These roles are needed to be able to access the ServiceNow Change Request fields from the Virtana UI, where they can be populated with default values for each created policy.
-
Search for "system oauth" and select System OAuth > Application Registry from the results.
-
Click New and then click Create an OAuth API endpoint for external clients from the popup list.
-
Complete the form and submit.
The new name appears in the registries table.
Note
The name must be unique and should identify the application for which you require OAuth access. For example, "Virtana".
You can use the default settings.
Details about the fields are available in the ServiceNow documentation, if you need them.
-
Click the name of the application you just registered.
Example: Virtana
The OAuth client application details opens.
-
Click the lock icon for the Client Secret.
The secret password displays below the field.
-
Copy and save the Name, Client ID, and Client Secret, then close the form.
You need to add this information to the integration configuration form in Virtana Platform.
-
You can log out of ServiceNow.
Now that you have the required information, you must add the values to Virtana Platform.
Next Steps
You can add a ServiceNow integration to Virtana Platform so that requests can be generated in ServiceNow by Cloud Cost Management (CCM).
About This Task
When configuring the ServiceNow integration, you must select the Default Issue Settings. The issue settings are selected from a list of fields used in your ServiceNow account. They are pulled into Virtana Platform from ServiceNow.
The Default Issue Settings are the fields that will be automatically assigned when change requests are enabled. You can customize the CMS settings per policy later, to satisfy specific use cases.
Prerequisites
You must configure ServiceNow with a web service access only user and an item in the Application Registry for Virtana so that CCM can connect to ServiceNow. See Configure ServiceNow for Integration with Virtana Platform.
Steps
-
In Virtana Platform, click the Settings sprocket.
-
In the left navigation pane, click Integrations > Change Management.
-
Click Connect to ServiceNow.
The Setup ServiceNow Integration form opens.
-
Enter the required information:
-
Your ServiceNow Domain in the format sample.servicenow.com
-
Username and Password for the user account that will access the ServiceNow APIs
-
OAuth Client ID and OAuth Secret
You can copy the ID and secret password from the Application Registry page in ServiceNow.
-
-
Click Test Connection.
A message indicates if connection is successful.
If connection is successful, the Default Issue Settings display.
-
Under Default Issue Settings click Add Fields to select the fields you want to include when generating ServiceNow change requests.
Select the fields you want filled in by default for all ServiceNow requests created through CCM.
The list of fields changes depending on the configuration of each customer's CMS.
-
Select or enter content for each field you added.
You must enter content for all required fields to complete the integration.
You can add a Jira integration to Virtana Platform so that change requests can be generated in Jira by Cloud Cost Management (CCM).
About This Task
When configuring the Jira integration, you must select the Default Issue Settings. The issue settings are selected from a list of fields used in your Jira account. They are pulled into Virtana Platform from Jira.
When configuring the Jira integration, the selections under Default Issue Settings change depending on the Project and Issue Type selected. Any required fields display automatically for each Project or Issue Type selected. You can add optional fields, as well. Optional fields can be deleted, but you cannot delete required fields.
The Default Issue Settings are the fields that will be automatically included in any change requests. You can customize the settings per policy later, to satisfy specific use cases.
Prerequisites
You must have a Jira account.
You must have administrator access to Virtana Platform.
Steps
-
Create a Jira API token using the API Token generator and copy the token.
-
In Virtana Platform, click the Settings sprocket.
-
In the left navigation pane, click Integrations > Change Management.
-
Click Connect to Jira.
The Setup Jira Integration form opens.
-
Enter the required information:
-
Your Jira Domain in the format companyID.atlassian.net
-
API Key for the user account that will access the Jira APIs
Paste in the field the token you copied from the Jira Token generator.
-
Email address
Specify the address of the user who created the API key.
-
-
Click Test Connection.
A message indicates if connection is successful.
If connection is successful, the Default Issue Settings display.
-
Select the Project and Issue Type to use when generating Jira change requests.
These are the fields you want filled in by default for all Jira requests created through CCM.
The list of issue types changes based on the project you select.
-
Click Add Fields to select any optional fields you want to add.
The list of fields changes depending on the configuration of each customer's CMS.
-
Select or enter content for each field you added.
You must enter content for all required fields to complete the integration.
Comments
0 comments
Article is closed for comments.