Open Stack

I think the Service VM discussion resolved itself in a way that reduces the
problem to a form of NFV - there are standing issues using VMs for
services, orchestration is probably not a responsibility that lies in
Neutron, and as such the importance is in identifying the problems with the
plumbing features of Neutron that cause implementation difficulties.  The
end result will be that VMs implementing tenant services and implementing
NFV should be much the same, with the addition of offering a multitenant
interface to Openstack users on the tenant service VM case.

Geoff Arnold is dealing with the collating of information from people that
have made the attempt to implement service VMs.  The problem areas should
fall out of his effort.  I also suspect that the key points of NFV that
cause problems (for instance, dealing with VLANs and trunking) will
actually appear quite high up the service VM list as well.
-- 
Ian.



On 18 May 2014 20:01, Steve Gordon <sgordon at redhat.com> wrote:

> ----- Original Message -----
> > From: "Sumit Naiksatam" <sumitnaiksatam at gmail.com>
> >
> > Thanks for initiating this conversation. Unfortunately I was not able
> > to participate during the summit on account of overlapping sessions.
> > As has been identified in the wiki and etherpad, there seem to be
> > obvious/potential touch points with the advanced services' discussion
> > we are having in Neutron [1]. Our sub team, and I, will track and
> > participate in this NFV discussion. Needless to say, we are definitely
> > very keen to understand and accommodate the NFV requirements.
> >
> > Thanks,
> > ~Sumit.
> > [1] https://wiki.openstack.org/wiki/Neutron/AdvancedServices
>
> Yes, there are definitely touch points across a number of different
> existing projects and sub teams. The consensus seemed to be that while a
> lot of people in the community have been working in independent groups on
> advancing the support for NFV use cases in OpenStack we haven't necessarily
> been coordinating our efforts effectively. Hopefully having a cross-project
> sub team will allow us to do this.
>
> In the BoF sessions we started adding relevant *existing* blueprints on
> the wiki page, we probably need to come up with a more robust way to track
> these from launchpad :). Further proposals will no doubt need to be built
> out from use cases as we discuss them further:
>
>     https://wiki.openstack.org/wiki/Meetings/NFV
>
> Feel free to add any blueprints from the Advanced Services efforts that
> were missed!
>
> Thanks,
>
> Steve
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140519/815edf58/attachment.html>