Cloud bursting with HP CloudSystem Matrix

infrastructure orchestration and Savvis

Technical white paper
July 2012
Contents
Overview ................................................................................................................................. 2
What is CloudSystem bursting? .................................................................................................. 2
Why burst with CloudSystem? .................................................................................................... 2
Hybrid cloud use cases .............................................................................................................. 2
CloudSystem Matrix bursting to Savvis ........................................................................................ 3
CloudSystem Matrix bursting to Savvis concepts and capabilities ................................................... 3
Inventory .............................................................................................................................. 3
Access ................................................................................................................................. 3
Allocation policy ................................................................................................................... 3
VM provisioning .................................................................................................................... 3
Networking .......................................................................................................................... 3
Software mapping ................................................................................................................. 3
API call translation ................................................................................................................. 4
Savvis bursting connector ....................................................................................................... 4
Prerequisites ............................................................................................................................. 4
Configuring Savvis for cloud bursting .............................................................................................. 5
Create a Savvis account ............................................................................................................ 5
Create one or more VPDCs using the SavvisStation portal .............................................................. 5
Create a VPN connection to Savvis ............................................................................................. 8
Upload a Client Provided Image (CPI) to Savvis ............................................................................ 9
Gather and record URIs of Client Provided Images ...................................................................... 11
Configuring Matrix infrastructure orchestration for cloud bursting ..................................................... 12
Edit hpio.properties ................................................................................................................. 12
Edit Savvis properties .............................................................................................................. 12
Enable Savvis log (optional) ..................................................................................................... 12
Create Savvis cloud pools ........................................................................................................ 12
Create a pool properties file for each pool ................................................................................. 13
Create an mxpassword entry for each pool ................................................................................ 13
Create a software mapping file for each pool ............................................................................ 13
Install the Savvis SSL certificate ................................................................................................. 14
Restart the infrastructure orchestration service ............................................................................. 16
Provisioning in Matrix infrastructure orchestration using Savvis ......................................................... 17
Access infrastructure orchestration designer ............................................................................... 17
Create a template ................................................................................................................... 17
Access infrastructure orchestration console ................................................................................. 18
Create a pool ......................................................................................................................... 18
Create a new service using the template .................................................................................... 19
Verify that the VM was created ................................................................................................. 20
Accessing the VM from infrastructure orchestration ...................................................................... 22
Disk scrubbing .................................................................................................................... 22
Savvis cloud support in infrastructure orchestration 7.0 ................................................................... 23
Supported operations .............................................................................................................. 23
Limitations .............................................................................................................................. 23
Limitations and known issues ........................................................................................................ 23
For more information ................................................................................................................... 25



Overview
What is CloudSystem bursting?
Public cloud bursting is a feature of HP CloudSystem Matrix that enables enterprises to provision public and private
infrastructure resources in a seamless way. Combined with CloudSystems powerful private cloud management
capabilities, the ability to burst beyond the private cloud environment, and to leverage infrastructure resources
offered by external cloud service providers, creates a virtually unlimited pool of hybrid cloud resources for
CloudSystem users to draw upon for cloud service delivery.

Why burst with CloudSystem?
As enterprises grow their portfolio of cloud services, CIOs are becoming strategic brokers to determine and optimize
service delivery options. Based on business needs, some cloud services are being sourced from a private cloud, some
from public clouds and others from hosted private clouds. As business needs change, resources must be added,
subtracted, reconfigured, and rebalanced across available channels dynamically. To optimize cloud service
deployments in these environments, CIOs need a cloud service delivery model that is flexible across hybrid delivery
channels and can be managed as an integrated technology environment.

HPs unique approach to bursting with CloudSystem ushers in the era of hybrid computing in a way that enables
enterprises to embrace both private and public clouds fully, and to make hybrid clouds fundamental to their IT
architecture and provisioning strategies.

For enterprises, the unmatched flexibility of hybrid clouds redefines the scope of what is possible by opening
access to a breadth and depth of resources and to new service delivery options that are simply not available
using either private or public clouds alone.

Of critical importance to IT, bursting to public clouds from CloudSystem brings public clouds into the sphere of IT
governance and control, and makes them manageable from the same environment used to manage private
clouds.

Cloud service designers benefit as well, by being able to leverage both private and public cloud infrastructure
resources from a single service design and provisioning environment

Hybrid cloud use cases
With hybrid cloud resources at their disposal, enterprises can go beyond thinking in terms of using private or public
clouds, and think instead of how to use private and public clouds effectively together. This holistic view enables
hybrid cloud to become a foundational element of IT strategy, touching everything from IT planning and operations,
to the design of individual services.

Some use case examples:

Growth as a risk management strategy, an enterprise may choose to experiment with the idea of expanding
into a new geography via a service provider first; if the trial is successful, the enterprise may choose to open a
datacenter in the new location and transition from using public to private resources at that time.

Elastic capacity to help contain costs, an enterprise may choose to use public cloud resources to augment
internal capacity as a way of handling fluctuating demand for IT resources. At times of higher demand, lower
priority services can be deployed to public cloud resources to ensure that private resources will be available for
higher priority workloads.

Technology operations to increase operational efficiency, an enterprise may plan to use different resources
for different phases of a projects lifecycle. For example, a software development team might routinely plan to
use public cloud resources for application development and testing, and to switch to using private resources for
production deployment.

Service optimization to maximize performance, a single service can be designed to use both public and
private cloud resources. For example, a two-tiered web application could be designed to run the web tier in a
public cloud, while keeping the database tier closer, running on internal resources only.


CloudSystem Matrix bursting to Savvis
Initially, HP CloudSystem Matrix 7.0 can burst to Savvis, an HP CloudAgile Service Provider partner and approved
HP CloudSystem bursting destination. Savvis is a managed hosting and cloud services provider capable of meeting
dynamic customer demand for outsourced IT and cloud services. Savvis is a global cloud provider, with datacenters
in the US east, US west, EMEA, and Asia. The company offers Savvis Symphony Virtual Private Data Center (VPDC)
solutions that feature multi-tiered security and a set of predefined service levels.

Over the coming months and years, look for an expanding ecosystem of bursting destinations that will include HP
Cloud Services, additional HP CloudAgile bursting partners, and other service providers.

CloudSystem Matrix bursting to Savvis concepts and capabilities
Inventory

Savvis resources appear to CloudSystem Matrix infrastructure orchestration as pools with unlimited capacity.
Cloud Resource pools do not have an upper capacity (unlike VM Hosts, which can run out of memory and disk
space). Consequently, if a logical server definition is valid for the cloud provider, it can always be provisioned to
the cloud.
Resources accessible via a Savvis account are represented as a Cloud Resource inside of Matrix. This Cloud
Resource can be added to a resource pool like any other VM Host or ESX Resource Pool.
A Savvis Cloud Resource comprises its own infrastructure orchestration pool.
CloudSystem can burst to any number of Savvis accounts
For a single Savvis account, there can be multiple VPDCs in Savvis and multiple Savvis cloud pools in Matrix
Savvis Cloud Resources can be inserted into any number of different server pools
A single server pool cannot include both internal cloud resources and Savvis Cloud Resources, and multiple
Savvis Cloud Resources cannot be included in one server pool
Access
Access to Savvis server pools is assignable to user groups, in the same way that access to internal server pools is
managed.
Savvis account credentials are associated with a Cloud Resource. The account used is determined by the Cloud
Resource selected during allocation.

Allocation policy
The user selects server pools and specifies the pool list order. Servers are provisioned to the first server pool that
can accommodate the needs of all servers in a group. If a Savvis pool can satisfy the needs of a server group
and is the first pool in the list, the server is provisioned to Savvis. If a Savvis pool is not the first pool in the list of
selected pools, Savvis is used only if previous pools are unable to accommodate the server group.

All servers in a server group are provisioned within the same cluster or the same Cloud Provider. Multiple server
groups can have some groups provisioned in the Matrix environment and others in an external cloud.

VM provisioning
Operating system image is deployed
Data disks are added
Servers are added to the Savvis network
Progress is monitored, and status reported as for on-premise

Networking
A logical server is limited by Savvis to connect to only one network.

Software mapping
Matches a CloudSystem software template to an analogous Savvis deployment image
Accommodates differences in the name, format, and content of images used by CloudSystem and Savvis. For
example, CloudSystem VM templates are mapped to corresponding images in the Open Virtualization Format
(OVF) that Savvis uses; HP servers employing hypervisors not supported by Savvis can be mapped to Savvis
images that rely on Savvis-supported hypervisors. This allows customers to deploy services to Savvis regardless of
whether the template was initially designed for on-premise deployment of ESX virtual machines or Hyper-V virtual
machines. (Note that VMware software is required to create the client provided OVF images that are uploaded
to Savvis.)

Is transparent to Matrix Self Service Portal users. The same service template used by Matrix to deploy servers
internally can also be used to deploy servers to Savvis.
Is performed through a properties file that is used by Matrix.

API call translation
The Savvis interface adapter translates calls passed through the CloudSystem bursting interface so that they can be
understood by the Savvis API.

Savvis bursting connector
HP CloudSystem communicates with the Savvis public cloud using the Savvis Bursting Connector. The connector
adapts CloudSystem bursting calls so that they can be properly understood and executed by Savvis. As illustrated in
the following figure, software mapping and API call translation are embedded in the Savvis bursting connector:

Figure 1: Cloudsystem Matrix bursting to Savvis


The Savvis Bursting Connector is unique to Savvis. Connectors to other service providers will not be implemented in
the same way.

Prerequisites
1. Install the Insight Management 7.0 DVD and select HP Matrix infrastructure orchestration.
2. Install (or verify installation of) a supported browser. See the HP Insight Management Support Matrix for
supported browsers.
3. Using Systems Insight Manager, discover the VMware vCenter Server and VM Hosts. (Microsoft SCVMM
discovery is not required.) In Systems Insight Manager, select Options > Discovery.

4. License and register the VM Hosts. In Systems Insight Manager, select Configure > Virtual Machine >
Register Virtual Machine Host.



5. Launch Matrix infrastructure orchestration. In Systems Insight Manager, select Tools > Infrastructure
orchestration.


6. Ensure that ESX software is available in the infrastructure orchestration console Software tab.



Configuring Savvis for cloud bursting
Create a Savvis account
Contact your Savvis account representative to create an account.

Create one or more VPDCs using the SavvisStation portal
Create a VPDC by performing the following steps.

1. Log into the SavvisStation portal at https://www.savvisstation.com/
2. Select the Symphony VPDC menu.
3. Click Create New VPDC.


NOTE: The following images may not exactly reflect the screens in the Savvis user interface. Refer to the
Symphony VPDC User Guide for the latest information.


Select a Billing Site, Service Profile and Location. (The service profile is also known as a provider profile,
which you add to the pool properties file described in Configuring Matrix infrastructure orchestration for cloud
bursting.)



Savvis has defined three service profiles to fit the application lifecycle. Each service profile configures the
infrastructure, including virtual compute services, bandwidth, storage, and security services.

Note: Some features of Savvis service profiles are not supported by Matrix. For example, the Premier tier offers more
than one VLAN at the Savvis level, but only one is supported with Matrix cloudbursting.

Savvis Service Profiles
Essential Balanced Premier
Online Support
Network with options
Affordable compute and SAN
storage (performance equivalent or
better than most other cloud
providers)
On/Off Network Security Options
99.9% SLA

24x7 online and phone support
More network options and higher
network priority
Performance compute and SAN
storage
Fully configurable firewalls* VPN
available
Load Balancing
99.99% SLA

24x7 online and proactive support
Most network options and highest
network priority
Highest performing compute and
SAN storage
Fully configurable firewalls* VPN
included
Load Balancing with more pools
99.99% SLA


* Changes to firewall settings are performed in the Savvis portal.

4. Configure the data center by dragging a virtual server from the product catalog on the right into the center tier.
Create only a single, small VM in the Savvis VPDC. This VM is required by Savvis when creating a
VPDC. (You cannot create an empty VPDC.) After it is created, power off the VM. The type of VM that is
configured in Savvis does not have any effect on the types of VMs that are provisioned by Matrix.



5. Optionally, customize resources by clicking a virtual server and selecting Configure.
6. Review the monthly price and credit balance, and check the checkbox to confirm the purchase.
7. Deploy the VPDC, which makes the servers in the VPDC available to infrastructure orchestration.



8. Obtain the VPDC ID. Select the View/Hide Columns link, then add VPDC ID as one of the displayed
columns. This identifier is required for the software mapping file for cloud pools.



Create a VPN connection to Savvis
Information about ordering VPN access can be found in the Symphony VPDC User Guide, available under the Help
menu in the Savvis portal, and from your Savvis representative. After an order is placed, a Savvis representative will
contact you to configure the VPN.
















VPN addresses are assigned by Savvis. You cannot specify the range or address block of the VPN.
A VPN is required to access a provisioned VM using remote desktop or SSH.

Upload a Client Provided Image (CPI) to Savvis
Savvis enables you to upload Open Virtualization Format (OVF) images to a selected VPDC site and use it as a
Custom vServer Template to build vServers in the VPDCs. These custom images are stored in an Image Library, which
is available across all of the VPDCs at that site.





1. In the Symphony VPDC: Overview page, click on the Upload New Image link in the upper left-hand corner of
screen under Shortcuts or under the My Tasks section.



2. On the Upload New Image screen, select the Billing Site/Department and Location from the pull down
menus.

IMPORTANT Using CloudSystem Matrix with Savvis requires client-provided images uploaded to Savvis. See
the Symphony VPDC User Guide for detailed client image preparation guidelines. It is the customers
responsibility to verify with Savvis the specific requirements for the images that can be deployed to Savvis.


IMPORTANT Network connectivity depends on the service profile of the VPDC created in Savvis.

If you create a VPDC with an Essential service profile, a VPN is not required; however, VMs created in Essential
VPDCs are available on the public internet. You can only access the VM over the public internet.

If you create a VPDC with a Balanced or Premier service profile, you must create a VPN connection to access
the VM. (You do not need a VPN connection to provision the VM.) Savvis DHCP servers serve IP addresses to
VMs in these VPDCs, and Matrix can find and display these IP addresses. The VMs are accessible via these IP
addresses only over the VPN connection.



3. Click Continue to launch a Java Web application that runs on the desktop. The Java Web Start technology
loads the Savvis transport client application automatically. This application will upload the Client Provided
Image. Once started, the Java application contacts the Upload Server.

The transport client application has been tested to work on Windows Vista. If you are using Windows 2003,
Windows 2008, or Windows 7, locate the downloaded .jnlp file and run it manually.



4. When the server has been contacted and the communication path established, browse and select files from the
desktop and click Add. You must browse to the files to upload, and the files must be located on the local system.
Select the .ovf and .vmdk files, and click Send.

Note: Use vmx7 as the VM type. If you generate the .ovf file on an ESX5 platform, it creates a vmx8 file, which
fails to import. If an .mf is generated, it is not needed and will not be uploaded.




5. When the files are successfully uploaded, a confirmation screen is displayed. Click Open to review information
in the file, or click OK.

After the upload image and conversion process is completed, the CPI is uploaded to the VPDC and saved as a
template in the Image Library. As a best practice, rename the image to match the name used in CloudSystem
Matrix.

Gather and record URIs of Client Provided Images
In the Savvis UI, find and note the following information. (You insert this information into the client image URI in the
Create a software mapping file for each pool step below.)

<CUSTOMER-BILLING-SITE> Displayed on the View VPDC Status screen, in the Billing Site column
<TEMPLATE-ID> Displayed in the right pane of the Savvis Image Library when the template is
selected
<VPDC-ID> Displayed when you select the View/Hide Columns link, then add VPDC
ID as one of the displayed columns

Configuring Matrix infrastructure orchestration for cloud
bursting
Edit hpio.properties
1. Open the properties file in the default location at:
C:\Program Files\HP\Matrix infrastructure orchestration\conf\hpio.properties

2. Add the following lines to enable cloud provisioning and to inform infrastructure orchestration that there is
external capacity available in the system. The value of cloud.max.concurrent.requests is always 1 because all
operations sent to Savvis are serialized.

Note: This setting controls concurrency across all cloud provisioning operations, including providers that may
support a higher concurrency setting.

cloud.capacity=true
cloud.max.concurrent.requests=1

3. (Optional) Add the following lines containing recommended timeout values for cloud operations, in minutes.
timeout.create.cloud.logicalserver=180
timeout.delete.cloud.logicalserver=60
timeout.start.cloud.logicalserver=30
timeout.stop.cloud.logicalserver=30
timeout.deactivate.cloud.logicalserver=30
timeout.resume.cloud.logicalserver=30
timeout.add.cloud.datadisk=60
Edit Savvis properties
If you selected an Essential service profile for your VPDC, manually limit the number of VMs in all VPDCs to which
Matrix provisions.

1. Create an empty file at C:\Program Files\HP\Matrix infrastructure orchestration\savvis-
config.properties
2. Add the following line:
savvis.vms.max=13

Enable Savvis log (optional)
1. Open the log properties file in the default location at:
C:\Program Files\HP\Matrix infrastructure orchestration\conf\log4j.properties
2. Add the following lines:
# Savvis Cloud
log4j.category.com.hp.hpio.cloud.savvis=DEBUG

Create Savvis cloud pools
Create an xml file to specify the pools that will be available in IO for provisioning. For each VPDC in Savvis, create
an identifier and name pair. (The identifier and name do not have any relationship to the VPDC name, and can be
any value as long as they are unique.) Modify the following example and save the file as C:\Program
Files\HP\Matrix infrastructure orchestration\conf\savvis-cloud-pools.xml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<CapacityPool xmlns="http://hp.com/2007/ess/sw/model/InfrastructureUtilitySchema">
<Id>Savvis-Cloud</Id>
<Resources xsi:type="CloudCapacityPool" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<!-- This Id maps to a property file with the same name
The Id is used to retrieve properties for this given CapacityPool.
For this pool, there would be a properties file named "savvis-cloud-1.properties"
in the <IO>\conf directory
-->

<Id>savvis-cloud-1</Id>
<Name>savvis-cloud-1</Name>
</Resources>
<Resources xsi:type="CloudCapacityPool" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Id>savvis-cloud-2</Id>
<Name>savvis-cloud-2</Name>
</Resources>
</CapacityPool>

Create a pool properties file for each pool
For each pool entered in savvis-cloud-pools.xml, create a properties file using the information from the example below
and save it in C:\Program Files\HP\Matrix infrastructure orchestration\conf\. Name the file
<pool-ID>.properties, where <pool-ID> is the pool ID entered in savvis-cloud-pools.xml.
provider.url=https://api.savvis.net/vpdc/v1.0
provider.profile=<SAVVIS_ACCOUNT_PROFILE>
provider.username=<SAVVIS_ACCOUNT_USERNAME>
proxy.host=<PROXY_FROM_BROWSER>
proxy.port=<PROXY_PORT_FROM_BROWSER>
proxy.username=<NOT_REQUIRED>
proxy.password=<NOT_REQUIRED>
For example, savvis-cloud-1.properties contains the following information:
provider.url=https://api.savvis.net/vpdc/v1.0
provider.profile=balanced
provider.username=firstname.lastname
proxy.host=
proxy.port=8088
proxy.username=
proxy.password=
Create an mxpassword entry for each pool
For each pool entered in savvis-cloud-pools.xml, create an entry in mxpassword. Open a command prompt
on the Central Management Server (CMS) and enter the following information, replacing savvis-cloud-1 with the
name of each pool ID in savvis-cloud-pools.xml.
mxpassword -a -x savvis-cloud-1=<SAVVIS-ACCOUNT-PASSWORD>
Create a software mapping file for each pool
As part of the bursting process, IO matches the software specified in the template, and matches it against software
defined in Savvis as mapped in the properties file. This provides a mapping from software X in CloudSystem Matrix
to software Y in Savvis.

The Matrix software that is selected is not important; it only matters that the software has a specific mapping to a
specific software item in Savvis that will be used to create the new VM. Generally, the software in Matrix and Savvis
are equivalent (for example, small_win2k8, large_win2k8, using the desired naming convention). The mapping
directs Matrix so that when a request for software X is targeted at the cloud, it creates a VM from software Y in the
cloud.

For each pool entered in savvis-cloud-pools.xml, create a properties file containing the mapping values for
your software. This file is used to identify the software that should be installed in the virtual machine in the Savvis
portal. Save the file in C:\Program Files\HP\Matrix infrastructure orchestration\conf\. Name
the file <pool-ID>-software.properties, where <pool-ID> is the pool ID entered in savvis-cloud-
pools.xml.
The first part of the mapping file (to the left of the equals sign) is the infrastructure orchestration software
location. This location is shown in the bottom details pane of the infrastructure orchestration console Software
tab. (If an ellipsis is displayed at the end of the location, hover your mouse to see the full location in yellow.
Special characters in the software location must be preceded by a \.)

In the following example, the infrastructure orchestration software location is:

vm\://192.168.200.11/vmfs/volumes/datastore1/WinTemplate/WinTemplate.vmtx




The second part of the mapping (to the right of the equals sign) contains the Savvis billing site, VPDC, and
template identifiers. This is the URI of the client provided image noted in the Gather and record URIs of Client
Provided Images section above.

https\://api.savvis.net/vpdc/v1.0/org/<CUSTOMER-BILLING-SITE>/vdc/
<VPDC-ID>/vAppTemplate/<TEMPLATE-ID>

For example, the file savvis-cloud-1-software.properties contains:

vm\://192.168.200.11/vmfs/volumes/datastore1/WinTemplate/WinTemplate.vmtx
=https\://api.savvis.net/vpdc/v1.0/org/606677.0/vdc/5159/vAppTemplate/732

Install the Savvis SSL certificate
The following example shows the certificate installation steps using Firefox. (If you are using Internet Explorer, select
Base-64 Encoded x.509 (.CER), which also can be imported safely with mxpassword.)

1. On the CMS, open a web browser and navigate to the following web address: https://api.savvis.net. The
SAVVIS APIs screen appears.


2. Click the savvis.net certificate to the left of the URL in the address bar. Click More Information in the screen
that appears.




3. Click View Certificate.



4. Click the Details tab, then click Export.




5. Browse to a location to save the certificate.



6. Open a command prompt and enter the command mxcert t f <filespec> to add the Savvis certificate
to the Systems Insight Manager keystore.




Restart the infrastructure orchestration service
On the CMS, open the Windows Services and restart the HP Matrix infrastructure orchestration Windows service.
(Restarting the service is required after enabling cloud provisioning in hpio.properties and adding the Savvis
certificate to the Systems Insight Manager keystore.)




Provisioning in Matrix infrastructure orchestration using Savvis
The following sections describe how to create a service inside the Cloud Provider using infrastructure orchestration.
Access infrastructure orchestration designer
To access HP Matrix infrastructure orchestration designer using a browser, navigate to https://<cms-ip-
address>:51443/hpio/designer/. (Clicking New or Edit on the Templates tab in the infrastructure
orchestration console also launches the designer.)

Create a template
Drag the following icons to the components frame to create a new template in the Designer.

One or more virtual server groups. Right click the server group to configure it. On the Software tab, select the
software mapped in the software.properties file.
A virtual network. You can select any network in Matrix. Savvis allows only a single network connection for any
VM, so the VM will reside on the only available network in Savvis.
One boot disk
Up to three private data disks (optional)




NOTE: There is no indication inside the designer that the software is mapped to Savvis software. The created template
can be used to provision in the cloud or on VM hosts.
Access infrastructure orchestration console
To access the infrastructure orchestration console using a browser, navigate to https://<cms-ip-
address>:50000/mxportal/home/MxPortalFrames.jsp

Launch the infrastructure orchestration console through Systems Insight Manager by selecting Tools >
Infrastructure orchestration.

Create a pool
1. Click the Servers tab. Create a pool containing cloud resources by clicking Create Pool. If you are not logged in
as Administrator, set user access to the newly created pool on the Users tab.


2. On the Create Pool screen:
a. Enter a new pool name.
b. Select a pool from the dropdown menu.
c. Select a cloud resource from the left table, and click the right arrow to move the resource to the new pool.
d. Click Save.





Create a new service using the template
1. Click the Templates tab. Select the template previously created and click Create Service.



2. On the Create Service screen:
a. Enter a service name.
b. Enter a hostname completion.
c. Click Options.
d. Select the cloud pool in the Available Server Pools table.
e. Click the right arrow to move the cloud pool to the Selected Server Pools table, and click Submit.
In this example, Public-Savvis is the only selected server pool. If more than one pool is selected, the order is
important. The VM is provisioned to the first (top) pool in the list. The VM is provisioned to second or subsequent pools
only if the previous pools do not have capacity for the VM.



Click the Requests tab to view the progress and status of the create service request.

Verify that the VM was created
1. Access the Savvis Station Portal at https://www.savisstation.com/login and login with your account
credentials.
2. In the Savvis portal, verify that the VM was properly created.
a. Select the Symphony VPDC tab at the top of the screen and the appropriate profile in the left margin.
b. Select the VPDC.
c. Verify that the VM exists and has a green checkmark. In this example, the newly created VM is named
vpn1.


3. In the Savvis portal, check the IP address of the VM. Right click on the VM and select View Properties.



4. Under Network Information, note the IP Address of the VM.



5. In the infrastructure orchestration console, verify that the service is running in the Savvis cloud. On the Services
tab, click Details to view the details of the service.


6. In the Resource Details tab, view the resource ID for the logical server and verify that it begins with
https://api.savvis.net.



7. In the NIC Details tab, view the IP address and verify that it matches the address of the VM in step 4.



Accessing the VM from infrastructure orchestration
With a VPN connection established, you can access the IP address of the VM as if it were an address within your
corporate network.

For Windows VMs, select the RDP link in the Service Details pane under Console Access.
For Linux VMs, access the VMs using SSH. This is the same method used to access VMs inside of Matrix.


Disk scrubbing
Matrix does not enforce disk scrubbing for VMs placed at cloud providers. Savvis scrubs disks when the entire VPDC
is deleted. Disks are not scrubbed when VMs are deleted. Sharing a VPDC among multiple tenants or users may
contain disks constructed with unscrubbed data.

For a single Savvis account, multiple VPDCs can be created in Savvis (and multiple Savvis cloud pools in Matrix). If
isolation is required or desired, create separate VPDCs (and Matrix cloud pools) for each tenant or user.

Savvis cloud support in infrastructure orchestration 7.0
Supported operations
Create Service
Delete Service
Power On Server
Power Off Server
Power Cycle Server
Add Server
Add Disk (up to three data disks)
Activate redirected to Power On VM request; does not behave the same as Matrix VMs
Deactivate redirects to Power Off VM request; does not behave the same as Matrix VMs
Limitations
Logical server (SAVVIS vServer) memory and number of CPUs (based on valid provider profile):
Balanced or Premier
Memory: 16 Gb or less
CPUs: 8 or fewer
Essential
Memory: 8 GB or less
CPUs: 2 or fewer





Logical servers are defined using VM template software. The following HP deployment servers/methods do not
support Savvis VMs: Insight Control server deployment, Server Automation (SA), and manual OS provisioning.
VPDC has fewer than 32 vServer options currently provisioned in the product catalog.
Server Load Balancing (SLB) pools, Source IP Perimeter Firewall (PFW) Filtering, and the Server Tier Firewall are not
supported through Matrix infrastructure orchestration. Changes to these settings are performed in the Savvis
portal.
Network: Only one NIC is attached to the logical server, and the network is configured with DHCP.
Boot disk size cannot be changed.
Data disk size is less than 500 GB.
Shared data disks are not supported
Storage tags cannot be defined
Linked clones are not supported

Limitations and known issues
Performance
It takes approximately 30 minutes (and varies according to the Savvis network support) for each simple provisioning
of one VM using one boot disk and one network.

Network
Savvis limits a VM to only one network connection.

No concurrent request handling
NOTE Savvis allows specific values for memory and the number of CPUs in a vServer (for example,
1, 2, 4, or 8 CPUs for a vServer in the Balanced profile). Matrix infrastructure orchestration allows
any value from 1 through 8 for the number of CPUs. IO maps the value in the IO template to the
smallest Savvis value that is greater than or equal to the value requested in the IO template for both
CPUs and amount of memory. The service details inside IO are updated to reflect the new value.

All operations sent to Savvis are serialized. Concurrent VM provisioning in the same service is limited; Savvis
currently supports only a single operation at the service level.

Generic messages
Errors that occur when submitting a request to Savvis are non-specific as to the cause. For example, Cloud provider
is not compatible with Logical Server requirements. Please refer to the Matrix OE infrastructure orchestration
documentation for further details.

No VM customization and login
Some values (such as IP addresses) are not customized inside Savvis. Automatic login for the created VMs is not
allowed.

Software mapping
Software deployed in the Savvis cloud requires manual setup before it is used by infrastructure orchestration.

Custom VM images created in IO must be uploaded to Savvis using the Savvis web portal.
After the software is uploaded to Savvis, a mapping file must be createdto map each IO image to the
corresponding Savvis image.

Software provisioning
Using SA to deploy application software onto a Savvis VM (subsequent to OS deployment by Savvis) is not
supported. Using different deployment engines to deploy software to the same VM is not supported.

Visibility and management of cloud based VMs
Cloud based VMs are visible only to infrastructure orchestration. These VMs are invisible to Insight Control virtual
machine management and Systems Insight Manager, and have no logical server associated in logical server
management.

Localization
Savvis support in infrastructure orchestration 7.0 is English only.





For more information
The latest versions of manuals and white papers for Matrix OE and related products can be downloaded from the HP
Web:
http://www.hp.com/go/matrixoe/docs

For more about HP CloudSystem bursting options, see:
http://www.hp.com/go/cloudsystem

For more information about HP Cloud Services, see:
www.hpcloud.com
www.hp.com/go/ScalingTheCloud


























Get connected
hp.com/go/getconnected



Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The
only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services.
Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or
omissions contained herein.

5900-2256, Created March 2012
Rev 3, July 2012