Technical Guidelines & Validation Requirements

EXHIBIT A

 

TECHNICAL GUIDELINES & VALIDATION REQUIREMENTS

I. Technical Guidelines

 

• “Built-For” Requirements

 

1. Applications must run independently of OpenStack and Rackspace Private Cloud Software (RCPS), aka “Alamo,” inside of a virtual machine (VM) without having to modify neither the Alamo nor OpenStack configurations
2. Partners must only provide features at the top of the application software stack in their VM(s) and must only expect and rely on resources offered to a virtualized environment

• For example, cloud application deployment tools would qualify as would applications and platforms that run inside RPCS virtual machines such as databases and analytics tools, virtual appliances, application middleware, web applications, application monitoring tools.
• Cloud infrastructure management tools, custom file systems, infrastructure security and infrastructure monitoring tools would not qualify

 

• Technical Requirements

 

1. OS & Hypervisor
   1. Alamo installs Ubuntu 12.04 on all OpenStack nodes and exclusively uses the KVM hypervisor on all compute nodes

                                                  i.    Applications requiring nested virtualization must use QEMU with KVM full virtualization support disabled

1. Networking
   1. Applications must be capable of only interacting with a Flat DHCP network model made available by the host compute node

                                                  i.    Accessibility to configuration of floating IP’s, security groups and a DMZ is available via the API

                                                 ii.    Integrated support for extensive infrastructure network features such as network security, VLAN tagging of VM’s etc., is not available

1. Infrastructure
   1. The application cannot make usage of or require cluster management related tasks or resources to the Alamo OpenStack environment (i.e. custom drivers, third-party cluster storage, load-balancing, redundancy etc.)

 

II. Built-for Rackspace Private Cloud Validation and Testing

• Application Validation

Please follow the steps below to validate your application and document the process. Suggestions for documentation are noted in red. Our goal is to be able to quickly see the specifics of the validation with OpenStack and Rackspace Private Cloud (Alamo) that we can share with customers so they’ll know exactly how the product was tested and with which configuration it worked.

 

1. Install OpenStack using Rackspace’s Private Cloud Software (Alamo), our free & public ISO, onto a cluster located in your environment or datacenter
   1. ISO: http://www.rackspace.com/cloud/private/openstack_software/
   2. Install Guides: http://www.rackspace.com/knowledge_center/getting-started/rackspace-private-cloud
   3. Configure & install your application onto a VM, or set of VM’s, within the Alamo OpenStack environment by either
      1. Creating & uploading an existing ready-to-go custom VM or VMs in either the RAW or QCOW2 formats
      2. Or install your application, its software stack & dependencies to an existing image already available in the Alamo environment.
      3. Documentation:

                                          i.    Provide us with the number of VM’s required for your app to run

                                         ii.    Provide us with the quantity of CPU, RAM & Hard disk storage requirements for each VM instantiated as well as any performance metrics readily accessible

                                        iii.    Provide us with a general architectural layout of the VM’s if its not a flat layout

1. Configure the proper network configurations needed by the application using either OpenStack’s Horizon or via the API
   1. Documentation:

                                          i.    Provide us with the internal & external network requirements, as well as settings & configurations required by your application

1. Configure any external dependencies required by your application
   1. Documentation:

                                          i.    Provide us with any information regarding API calls or usage of resources outside of the Alamo environment

1. i.e. remote resources used via API, heartbeat / phone-home requirements etc.
2. Setup the proper authentication, authorization, service catalogs in Keystone if your application requires deployment capabilities
   1. Documentation:

                                          i.    Provide us with any specific usage of made to the OpenStack API for cluster deployment (instantiating, deleting VM’s, images etc.)

 

Once completed, documentation should be sent to rpcpartners@rackspace.com