Continue the multi-quarter Neutron project by creating a detailed migration plan for replacing the current nova-network service with a more modern Neutron stack. This plan should include reasonably detailed steps needed to plan the actual implementation including changes that will need to be made both inside and outside of the Cloud Services environment. It should also identify contributions needed from other Foundation teams so that we can start talking to those teams in preparation for actually implementing the plan.
== hardware status ==
Some of this is refresh and we need to rebuild and retire the existing, and some of this is additional hardware from the 16/17 budget for a second region testing.
=== These hosts can be used for the new Neutron deployment ===
* labtestcontrol2003
* labtestmetal2001
* labtestnet2002
* labtestservices2002
* labtestservices2003
* labtestneutron2001
* labtestneutron2002
* labtestvirt2003
=== in use ===
labtestpuppetmaster2001
- two clouds sharing a puppetmaster?
* labtestvirt2002.codfw.wmnet && labtestvirt2001.codfw.wmnet
** Compute node
** Runs nova-compute
** Has space for 4 or 5 smallish VMs
* labtestnet2001.codfw.wmnet
** Current network host and api server
** Runs nova-api
** Runs nova-network
* labtestcontrol2001.wikimedia.org
** Openstack controller node
** Runs keystone API and all keystone services
*: why can't we have shared keytone?
** Runs nova scheduler
** Runs nova conductor
** Hosts all OpenStack databases for labtest
** Hosts puppetmaster for all labtest VMs
* labtestservices2001.wikimedia.org
** Ldap/DNS server
** Runs pdns
** Runs all designate services
-- is there a way to have designate see tokens from multiple keystons as valid?
* labtestweb2001.wikimedia.org
** Web UI frontend for labtest
** Runs Horizon test instance
** Runs Wikitech test instance