Open Stack

On Apr 21, 2014, at 3:07 PM, Kyle Mestery <mestery at noironetworks.com> wrote:

> For the upcoming Summit there are 3 sessions filed around "Service
> VMs" in Neutron. After discussing this with a few different people,
> I'd like to propose the idea that the "Service VM" work be moved out
> of Neutron and into it's own project on stackforge. There are a few
> reasons for this:
> 
> 1. There is nothing Neutron specific about service VMs.

Agreed.  VMs are one of several options for implementing a service.  Managing the full lifecycle tends to touch on lots of OpenStack components and as Kyle wrote below there is nothing to specific to Neutron about them.

> 2. Service VMs can perform services for other OpenStack projects.
> 3. The code is quite large and may be better served being inside it's
> own project.
> 
> Moving the work out of Neutron and into it's own project would allow
> for separate velocity for this project, and for code to be shared for
> the Service VM work for things other than Neutron services.
> 
+1 to starting a separate project on stackforge for this work.

mark