Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and Savvis

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.