Open Stack

Folks,

I think is correct to have "Service VMs" on a separate project because it
seems to me a very specific implementation (form factor) of a Service
Insertion use case.
However, there are few interesting services sessions proposed for the
summit intended to enhance all areas of the ³Networking Services² such as
DB, plugin and the agent side.

I strongly recommend to have all services-related sessions together and
finally to decide as a team, which path will be for Neutron on this area,
we should not be extending more and more the current framework that was
not designed (if it was ever designed) for the functionality that we are
giving it today. Let¹s consider a couple of already presented proposals on
this area:

https://wiki.openstack.org/wiki/Neutron/ServiceInsertion


I will update the wiki with the latest ideas on this area.. But please, as
a team we should start considering finally a ³Generic Services Insertion²
framework regardless of the backend technology and the service form factor
(bare metal, vm, etc.).

Cheers,

Edgar


On 4/21/14, 6:41 PM, "Kyle Mestery" <mestery at noironetworks.com> wrote:

>On Mon, Apr 21, 2014 at 4:20 PM, Doug Hellmann
><doug.hellmann at dreamhost.com> wrote:
>> On Mon, 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:
>>
>> How long do you anticipate the project needing to live on stackforge
>> before it can move to a place where we can introduce symmetric gating
>> with the projects that use it?
>>
>The patches for this (look at the BP here [1]) have been in review for
>a while now as WIP. I think it's reasonable to expect that moving this
>to stackforge would let the authors and others interested collaborate
>faster. I expect this would take a cycle on stackforge before we could
>talk about other projects using this. But honestly, that's a better
>question for Isaku and Bob.
>
>> Who is going to drive the development work?
>>
>For that, I'm thinking Isaku and Bob (copied above) would be the ones
>driving it. But anyone else who is interested should feel free to jump
>in as well.
>
>Thanks,
>Kyle
>
>[1] https://blueprints.launchpad.net/neutron/+spec/adv-services-in-vms
>
>> Doug
>>
>>>
>>> 1. There is nothing Neutron specific about service VMs.
>>> 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.
>>>
>>> I'm starting this email thread now to get people's feedback on this
>>> and see what comments other have. I've specifically copied Isaku and
>>> Bob, who both filed summit sessions on this and have done a lot of
>>> work in this area to date.
>>>
>>> Thanks,
>>> Kyle
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>_______________________________________________
>OpenStack-dev mailing list
>OpenStack-dev at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev