The attached zip file contains the Turbonomic Service Now integration in the form of an XML update package to be loaded into Service Now, together with full installation and setup instructions
You can use Turbonomic Deploy to deploy workloads in your managed environment. With this application, you can use Turbonomic to calculate the best placement of new Virtual Machines (VMs) within your managed IT environment. You can deploy workloads immediately, or reserve space for the workloads to deploy them later.
Turbonomic Deploy sets up communication between your ServieNow deployment and one or more instances of Turbonomic. Your ServiceNow management system discovers entities in your environment such as datacenters, clusters, and VM templates.
Turbonomic also discovers these entities, as well as all the VMs in the datacenters. Turbonomic manages VMs in the context of the full datacenter, taking into account:
The physical hosts, storage (datastores, disk arrays, storage controllers), fabrics, virtual datacenters, and networks that provide resources to the VMs
The applications that are hosted by the VMs.
Turbonomic considers the full range of supply and demand in your environment to calculate the best placement of VMs in your environment.
When it’s time to deploy more VMs in your ServiceNow environment, you can use Turbonomic Deploy to calculate the best placement for those VMs, and then actually deploy the VMs to those locations.
If you want to set up a deployment for a later date, you can use Turbonomic Deploy to calculate the best placement, and then reserve the necessary resources to support that placement. Turbonomic deploys reserved VMs -- placeholders for the VMs you want to deploy. While the reservation is active, Turbonomic continually calculates the best placement for these reserved VMs, and moves them as necessary. Then, when it’s time to deploy, Turbonomic will deploy the actual VMs to the calculated locations.
Virtual Machine Support
Turbonomic Deploy supports deployment of workloads managed by VMware vServer versions 5.5 and 6.0.
Both Turbonomic and ServiceNow perform discovery — scanning your environment for the datacenters and their components that Turbonomic and ServiceNow will manage. Note that both management systems (Turbonomic and ServiceNow) should be configured to discover the same datacenters — This means that they both manage the same environment, including the same hosts, storage, and VMs.
As you perform administration tasks and manage reservations, you will use discovered components. For example, to deploy a set of VMs, you specify a VM template to use — You choose the template you want from a list of discovered VM templates.
This documentation assumes that discovery has been configured correctly by your ServiceNow administrator. Your ServiceNow administrator is responsible for:
Configuring discovery in Service Now
This includes installing and configuring the ServiceNow discovery plugin, and setting up periodic discovery of the managed datacenters. If you want to learn more about discovery in ServiceNow, see the documentation for your version. For example, for information about discovery in Geneva, see Discovery.
Discovery in Turbonomic
Turbonomic connects to VMware and Microsoft Hyper-V management systems to discover associated datacenters. Your administrator should have already configured the Turbonomic REST Hosts that you will use. Before you configure other REST Hosts, you should consult with your administrator to make sure that you use Turbonomic servers that are configured to discover the appropriate datacenters.
For information about Turbonomic target configuration and discovery, please see the Turbonomic Product Documentation.
User Interface Overview
Turbonomic Deploy includes a ServiceNow Update Set that deploys the integration logic, as well as forms that make up a graphical user interface (GUI) for the application. This GUI makes it easy for users to orchestrate VM deployments within the ServiceNow managed environment via Turbonomic Deploy.
Once the update set is installed, enter
Turbonomic in the ServiceNow Navigator search bar. This should display the Turbonomic Deploy menu. If the menu does not appear, contact your ServiceNow administrator to make sure you have access to Turbonomic Deploy.
This documentation describes:
When you want to deploy VMs in your environment, you create a reservation. You can deploy it immediately, or you can reserve the resources for those VMs to deploy them at a later date. This documentation describes how to create a reservation, and how to monitor its status.
To use Turbonomic Deploy, it must be properly installed and set up in your ServiceNow environment. Proper setup includes:
REST Hosts — The administrator sets up one or more connections between an instance of Turbonomic, and a ServiceNow MID Server. This is how you connect Turbonomic to your ServiceNow workflows.
- Constraints — A constraint is a profile that specifies a VM template, the datacenter you will deploy to, and optionally a cluster within that datacenter.
Settings — Parameters that specify polling intervals, reservation timeouts, and deployment timeouts
NOTE: This document does not describe installation — It assumes that you already have a correctly installed instance of Turbonomic Deploy.
We hope this documentation gives you all the information you require to successfully deploy VMs with the Turbonomic Deploy application. If you encounter problems, please contact your ServiceNow administrator. This administrator should have contact with Turbonomic Inc. — If necessary, the administrator can contact Turbonomic to resolve issues.
Turbonomic Deploy uses Intelligent Workload Management to calculate the best placement for new VMs, and then actually deploy them in your environment. The Reservations view gives you the tools to create and manage reservations — You can deploy the requested VMs now or in the future. To deploy VMs in this view, you will:
Create new reservations
Specify the VM Template to use, and how many VMs from the given template that you want to deploy. You also specify information such as when to reserve or deploy, and optional constraints on where to deploy.
View your reservations
You can come to the Reservations view to see the current status of your reservations.
Delete selected reservations
When you delete a pending reservation, that also cancels the reservation in Turbonomic. Note that you must delete pending reservations one-at-a-time.
Click Reservations in the Turbonomic Deploy Menu:
Create a Reservation
To create a reservation, you will provide information about the VMs you want to deploy, when to deploy them, and optional constraints on placement.
Provide a name that describes the reservation.
Note that the reservation name also serves as the name prefix for deployed VMs. For example, assume you deploy three VMs in a reservation named DevServers. The VM names will start with prefixes of DevServers1, DevServers2, and DevServers3.
Turbonomic REST Host
A Turbonomic REST Host establishes a connection between a specific instance of Turbonomic and a MID Server in your ServiceNow deployment. The Turbonomic instance will calculate the placement for your VMs. Your ServiceNow administrator should have already specified one or more REST Hosts that you can use. Click the Search icon () to choose from a list of predefined REST Hosts.
For more information, see REST Hosts.
Number of Virtual Machines
Give the number of VMs that you want to deploy. If your environment has the resources to support those VMs, then Turbonomic will reserve the space for them, and deploy them at the time you choose.
The date that you want Turbonomic to reserve the resources for your VMs. To enable this setting, disable the Deploy Now option.
When you have made a reservation, Turbonomic adds the reserved VMs to your environment and calculates their placement as though they are real VMs. It manages the placement of these reserved VMs along with the placement of actual workload in your environment.
Often you will set the Reservation Date to be today. However, you might know that your IT department will deploy more hardware resources to your environment at some time in the future. In that case, you might want to set the Reservation Date to a time after the hardware upgrade.
The date that you want Turbonomic to deploy your VMs. To enable this setting, disable the Deploy Now option.
While the reservation is active (Succeeded status, but not deployed), the reserved VMs are placeholders in your environment. At the deployment date, Turbonomic uses the reservation’s template to deploy actual VMs to your environment.
When this option is enabled, the reservation date and the deploy date are both set to today. When you click the Submit button, Turbonomic will calculate the placement for the VMs, and then deploy real VMs in your environment.
To set up a reservation that deploys in the future, disable this setting and provide values for Reservation Date and Deploy Date.
Either choose a discovered template, or choose a predefined custom constraint.
By default, the form takes a Virtual Machine Template. Click the Search icon () to choose from a list of discovered VM templates. In this mode, Turbonomic will choose where to place the VMs among all the datacenters and clusters that can host this template. This is often the best choice, because it leaves Turbonomic free to use all your resources in the best possible way.
Your ServiceNow administrator should have already defined any constraints that you need. For more information, see Constraints.
The VM Template
The datacenter to deploy to (optional)
The cluster to deploy to (optional)
After you have made the settings you want, click Submit to create the reservation.
When you navigate to the Reservations view, it shows you a history of the reservations you have made, including the reservation date, deployment date, and status. Note that you can delete entries from this listing, but until you delete it a reservation remains in the list.
Each record in the list includes the following fields:
The reservation name
Number of Virtual Machines
How many VMs you specified for this reservation
The date you want Turbonomic to reserve the resources to host your VMs.
The date you want Turbonomic to create the actual VMs.
The current status for the reservation. The status can be one of:
In Progress: Turbonomic is calculating the placement for your VMs and reserving the necessary resources.
Reservation Succeeded: Turbonomic reserved the resources and is waiting for the Deploy Date so it can deploy the real VMs.
Reservation Unfulfilled: The environment does not have enough resources to reserve space for all the VMs. Turbonomic continually tries to fulfill the reservation. At the deploy date, if the reservation is successful Turbonomic will deploy the workload. If the reservation is still unfulfilled, then Turbonomic cancels the reservation.
Deploying: Turbonomic is actively deploying the VMs in your environment.
Deployment Succeeded— Turbonomic successfully deployed the VMs in your reservation.
Error: The reservation or deployment failed. See the Details field for more information.
If the reservation shows an
Errorstatus, the details show more information about the error. Hover over the Details field to see a tooltip with the full explanation.
Turbonomic Reservation ID
An internal unique ID that Turbonomic uses to track the reservation. The ID appears after the reservation has succeeded.
NOTE: When you delete a reservation, make sure to delete it by clicking the Info button ( ) to display the reservation data, and then clicking Remove. Do not use the Actions on selected rows menu to delete selected reservations. When you delete a reservation, it’s important that Turbonomic Deploy can send a message to Turbonomic — In this way Turbonomic knows to delete the pending reservation from its management process.
Before users can define and execute these deployments and reservations, Turbonomic Deploy must be properly set up. You should perform these tasks only if you have an administrator-level understanding of your ServiceNow managed environment, and of your Turbonomic deployments. These administrative tasks include setting up the connection between ServiceNow and Turbonomic (the REST Host), as well as specifying VM templates that are valid for specific datacenters in your environment. If you don’t have this level of understanding, you should talk to your ServiceNow administrator.
Click REST Hosts in the Turbonomic Deploy Menu:
A Turbonomic REST Host establishes a connection between a specific instance of Turbonomic and a MID Server in your ServiceNow deployment. The Turbonomic server performs the calculations to deploy workloads in your environment. When you create a reservation or execute a deployment of workload, your ServiceNow system will use a Turbonomic REST Host to connect with the Turbonomic server, request analysis, and execute actions.
The Turbonomic instance must already be installed in the same environment as the corresponding MID server. Also, the Turbonomic must already be configured to manage the hypervisors that will host the workload you want to deploy.
NOTE: A REST Host can only have one instance of Turbonomic and one MID Server instance.
To define a REST Host, specify:
A name that identifies this REST Host to your users. You should provide a descriptive name that identifies the purpose or scope of this REST Host.
URL that identifies the domain of the Turbonomic server for this REST Host. Typically, you provide the IP address of the Turbonomic server. Click the padlock icon to open the Endpoint field for editing.
A MID Server that is deployed in your environment. The MID Server facilitates communication between your deployment of ServiceNow and the Turbonomic server. Click the search icon to open a list of available MID Servers.
NOTE: The search results dialog box for MID Servers includes a New button. Do not use New to create a MID Server entry — You should only use MID servers that have been successfully registered and are active in your ServiceNow cloud instance.
Credentials that give ServiceNow access to Turbonomic — ServiceNow can then request Turbonomic to calculate workload placement, create a reservation, and deploy workload. The credentials must be for an Turbonomic account that has administrator or automator privileges.
Authentication Type: Choose Basic
Username/Password: Provide credentials for an administrator or automator account in Turbonomic
Click Constraints in the Turbonomic Deploy Menu:
NOTE: This version of Turbonomic Deploy supports deployment of workloads managed by VMware vServer versions 5.5 and 6.0. Your constraints can include corresponding VM templates.
A constraint is a preset profile that you can use to deploy a certain type of workload. For example, assume that you always want to deploy the same kind of VM to host applications used by the HR department. You can specify a constraint named “HR” and then always use that constraint when you deploy VMs to HR.
Each constraint must contain a VM template. Optionally, a constraint can specify a certain datacenter or cluster — This limits the VM placement to the specified datacenter or cluster. For example, assume you want the same VM template for HR and Payroll deployments, but each department is limited to its own host cluster. You can specify two constraints that use the same template, but specify different cluster as appropriate.
It’s very important that you choose a datacenter that’s valid for the template, and a cluster that’s valid for the datacenter. If you choose invalid datacenters or clusters, any attempt to deploy with this constraint will fail.
To choose a valid datacenter, first chose a discovered template. After you choose the template the INFORMATION icon appears next to the Template field. Click that icon to see the template’s discovered data. The data includes a list of valid datacenters — When you choose the datacenter to use, make sure it’s a datacenter that’s listed in the discovered data for your template.
Similarly, you can see the datacenter information to determine which clusters are valid.
To create a new constraint, specify:
Provide a name that describes the purpose or scope of this constraint.
Virtual Machine Template
The template that describes the VMs that you will deploy via this constraint. Choose from the list of discovered templates.
If you do not specify a datacenter or cluster, Turbonomic can deploy the VMs to any datacenter that contains the template. Turbonomic will calculate the best VM locations among these datacenters, and deploy your workload there. This is often the best option, because it takes the fullest advantage of all the resources in your environment.
If you want to limit a deployment to a specific datacenter, choose from the list of discovered datacenters.
To deploy successfully, you must choose a datacenter that contains the template. View the template information to see which datacenters are valid.
If you want to limit a deployment to a specific cluster, choose from the list of discovered clusters.
To deploy successfully, you must choose a cluster that is contained by the datacenter. View the datacenter information to see which clusters are valid.
NOTE: Each search results dialog box for Templates, Datacenters, and Clusters includes a New button. Do not use New to create entries — You should only use items that have been discovered by ServiceNow.
Click Settings in the Turbonomic Deploy Menu:
Use these settings to specify polling and timeout intervals in seconds:
- Polling Interval
How often Turbonomic Deploy polls the specified REST Host(s). Polling checks the status of a reservation while it’s in a state of
in progress. The default is 10 seconds.
- Reservation Timeout
The maximum time to allow for a reservation to succeed. The default is one hour (3,600 seconds).
When you create a reservation, the REST Host performs calculations to determine the best placement for the given workload. This can take a significant amount of time, but it should not take longer than an hour. If the reservation is in the state of in progress for more than an hour, Turbonomic Deploy cancels the request and shows a Failed state for the reservation.
- Deployment Timeout
The maximum time to allow for a deployment to succeed. The default is one hour (3,600 seconds).
When you deploy workload, the REST Host interacts with the underlying hypervisors to deploy the VMs to the calculated hosts. This can take a significant amount of time, but it should not take longer than an hour. If the deployment is in the state of in progress for more than an hour, Turbonomic Deploy cancels the request and shows a Failed state for the deployment.