opendev/system-config
Code Issues Proposed changes

Update cloud provider reqs

Browse Source 
Based on what we've learned adding two more.

Change-Id: I060d2dbb9ad2b9be46be47dcc98d609f48523579
This commit is contained in:
James E. Blair 2015-11-11 15:11:18 -08:00
parent 6814292b38
commit 7df7983538
1 changed files with 17 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
doc/source/contribute-cloud.rst
View File

@ -43,16 +43,26 @@ If you have some capacity on an OpenStack cloud that you are able to
contribute to the project, it would be a big help. This is what we contribute to the project, it would be a big help. This is what we
need: need:
* Nova and Glance APIs * Nova and Glance APIs (with the ability to upload images)
* 8GB RAM, 8vCPU per test node (CPUs vary, the important thing is to
be able to run devstack and tempest in about 1 hour)
* Public IP addresses
* A single instance with 300GB of disk (via Cinder is okay) per cloud * A single instance with 300GB of disk (via Cinder is okay) per cloud
region for our region-local mirror region for our region-local mirror
Our current providers are each donating around 600 instances of the Each test instance requires:
above types. Since there's a bit of setup and maintenance involved in
adding a new provider, a minimum of 100 instances would be helpful. * 8GB RAM
* 8vCPU at 2.4GHz (or more or less vCPUs depending on speed)
* A public IP address (IPv4 and/or IPv6)
* 40GB of storage
In a setting where our instances will be segregated, our usage
patterns will cause us to be our own noisy neighbors at the worst
times, so it would be best to plan for little or no overcommitment.
In an unsegregrated public cloud setting, the distribution of our jobs
over a larger number of hypervisors will allow for more
overcommitment.
Since there's a bit of setup and maintenance involved in adding a new
provider, a minimum of 100 instances would be helpful.
Since we continuously use the OpenStack APIs and are familiar with how Since we continuously use the OpenStack APIs and are familiar with how
they should operate, we occasionally discover potential problems with they should operate, we occasionally discover potential problems with