Jump to: navigation, search

Difference between revisions of "TripleO/TripleOCloud/Regions"

(What is it)
(What is it)
Line 3: Line 3:
  
 
Each region of this cloud contains:
 
Each region of this cloud contains:
* a bare metal cloud used by the TripleO admins team  
+
* a bare metal cloud used by the TripleO admins team to deploy things in the region
 
* a hypervisor based cloud (e.g. KVM) deployed on top of the bare metal cloud
 
* a hypervisor based cloud (e.g. KVM) deployed on top of the bare metal cloud
 
* one more more test environments for emulated bare metal testing deployed on top of the bare metal cloud
 
* one more more test environments for emulated bare metal testing deployed on top of the bare metal cloud

Revision as of 00:23, 8 November 2013

What is it

The TripleO cloud is a contributor run continuously deployed cloud, operated by the TripleO CD admins team, a team of trusted members of the TripleO community.

Each region of this cloud contains:

  • a bare metal cloud used by the TripleO admins team to deploy things in the region
  • a hypervisor based cloud (e.g. KVM) deployed on top of the bare metal cloud
  • one more more test environments for emulated bare metal testing deployed on top of the bare metal cloud

What is it for?

Primarily for testing the deployment and production readiness of OpenStack. A set of test environments for testing OpenStack deployment logic is deployed on the bare metal cloud using OpenStack's bare metal deployment facilities. These are then used to run 'check' tests with emulated baremetal. Secondly we deploy OpenStack to bare metal and then run tempest against the deployed cloud, validating Hypervisor configuration and the ability to deploy to bare metal on that hardware.

Finally, we permit active contributors to TripleO to use the cloud, because having users on the cloud finds issues :).

Contributing a region to the TripleOCloud

Regions are contributed by interested parties.

Location

Contributors should provide the machines in an operational environment of their own with their own DC operations staff available to correct hardware and network issues with the environment.

Hardware size

Each region has a minimum size of 10 machines, but their size varies substantially. For instance the first region we brought on line has ~50 machines. Each machine needs to be large enough to run a production OpenStack configuration - not necessarily scaled up. Right now we say 2-core and 8GB of RAM + 1TB of disk is the minimum node size for sensible use. We don't have a preferred config because - scaling out gate tests requires lots of small nodes to meet the concurrency of the gate pipeline, but running check tests requires large nodes that can handle many VMs effectively, as each test environment runs multiple VMs on one node.

Networking

We require a reasonable number of public IP addresses to permit openstack-infra's nodepool to spin up tests and drive them. The IPMI (or equivalent) network needs to be reachable from the machines in the rack, so that we can use Ironic/Nova baremetal to deploy to the same machines. This should be partitioned of from your own network.

10Gbps is preferred for the server LAN, but we can work with 1Gbps too.

There should be no other network services running in the rack as our Undercloud will be serving DHCP and net-booting the machines.

Sysops

The TripleO CD admins team will do all system operations other than hardware interventions - that's something your local team needs to provide.