[openstack-dev] [Neutron] VMware networking support
Hi, A few months back we started to work on a umbrella spec for Vmware networking support (https://review.openstack.org/#/c/105369). There are a number of different proposals for a number of different use cases. In addition to providing one another with an update of our progress we need to discuss the following challenges: * At the summit there was talk about splitting out vendor code from the neutron code base. The aforementioned specs are not being approved until we have decided what we as a community want/need. We need to understand how we can continue our efforts and not be blocked or hindered by this debate. * CI updates - in order to provide a new plugin we are required to provide CI (yes, this is written in stone and in some cases marble) * Additional support may be required in the following: * Nova - for example Neutron may be exposing extensions or functionality that requires Nova integrations * Devstack - In order to get CI up and running we need devatck support As a step forwards I would like to suggest that we meeting at #openstack-vmware channel on Tuesday at 15:00 UTC. Is this ok with everyone? Thanks Gary ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] VMware networking support
Fine for me :) On Thu, Nov 13, 2014 at 6:08 PM, Gary Kotton gkot...@vmware.com wrote: Hi, A few months back we started to work on a umbrella spec for Vmware networking support (https://review.openstack.org/#/c/105369). There are a number of different proposals for a number of different use cases. In addition to providing one another with an update of our progress we need to discuss the following challenges: - At the summit there was talk about splitting out vendor code from the neutron code base. The aforementioned specs are not being approved until we have decided what we as a community want/need. We need to understand how we can continue our efforts and not be blocked or hindered by this debate. - CI updates – in order to provide a new plugin we are required to provide CI (yes, this is written in stone and in some cases marble) - Additional support may be required in the following: - Nova – for example Neutron may be exposing extensions or functionality that requires Nova integrations - Devstack – In order to get CI up and running we need devatck support As a step forwards I would like to suggest that we meeting at #openstack-vmware channel on Tuesday at 15:00 UTC. Is this ok with everyone? Thanks Gary ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- *Regards,* *Romil * ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] VMware networking support
I chimed in on another thread, but I am reinstating my point just in case. On 13 November 2014 04:38, Gary Kotton gkot...@vmware.com wrote: Hi, A few months back we started to work on a umbrella spec for Vmware networking support (https://review.openstack.org/#/c/105369). There are a number of different proposals for a number of different use cases. In addition to providing one another with an update of our progress we need to discuss the following challenges: - At the summit there was talk about splitting out vendor code from the neutron code base. The aforementioned specs are not being approved until we have decided what we as a community want/need. We need to understand how we can continue our efforts and not be blocked or hindered by this debate. The proposal of allowing vendor plugin to be in full control of their own destiny will be submitted as any other blueprint and will be discussed as any other community effort. In my opinion, there is no need to be blocked on waiting whether the proposal go anywhere. Spec, code and CI being submitted will have minimal impact irrespective of any decision reached. So my suggestion is to keep your code current with trunk, and do your 3rd Party CI infrastructure homework, so that when we are ready to push the trigger there will be no further delay. - CI updates – in order to provide a new plugin we are required to provide CI (yes, this is written in stone and in some cases marble) - Additional support may be required in the following: - Nova – for example Neutron may be exposing extensions or functionality that requires Nova integrations - Devstack – In order to get CI up and running we need devatck support As a step forwards I would like to suggest that we meeting at #openstack-vmware channel on Tuesday at 15:00 UTC. Is this ok with everyone? Thanks Gary ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
