Re: [openstack-dev] [Neutron] Network Tagging Blueprint

ctive, I have not been following closely the > discussion on VPC; I hope to find time to catch up. > However, I recall seeing a blueprint for using nova-api as endpoint for > network operations as well; is that still the current direction> > > Salvatore > > > On 21 March 20

[openstack-dev] [Neutron] Network Tagging Blueprint

weekend for those interested in the details. https://docs.google.com/document/d/1ZqW7qeyHTm9AQt28GUdfv46ui9mz09UQNvjXiewOAys/edit# Regards -- Vinay Bannai eBay Inc ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org

[openstack-dev] Network Tagging Blueprint

weekend for those interested in the details. https://docs.google.com/document/d/1ZqW7qeyHTm9AQt28GUdfv46ui9mz09UQNvjXiewOAys/edit# Regards -- Vinay Bannai Ebay Inc ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org

Re: [openstack-dev] [Neutron][ML2] Can I use a new plugin based on Ml2Plugin instead of Ml2Plugin as core_plugin

self._ensure_default_security_group(context, >>>>>>>> tenant_id) >>>>>>>> >>> result = super(Ml2Plugin, >>>>>>>> self).create_network(context, >>>>>>>> >>> network) >>>>>>>> >>> network_id = result['id'] >>>>>>>> >>> ... >>>>>>>> >>> mech_context = driver_context.NetworkContext(self, >>>>>>>> context, >>>>>>>> >>> result) >>>>>>>> >>> >>>>>>>> self.mechanism_manager.create_network_precommit(mech_context) >>>>>>>> >>> >>>>>>>> >>> Also need to include new extension in the >>>>>>>> _supported_extension_aliases. >>>>>>>> >>> >>>>>>>> >>> So to avoid changes in the existing code, I was going to create >>>>>>>> my own >>>>>>>> >>> plugin (which will be very similar to Ml2Plugin) and use it as >>>>>>>> core_plugin. >>>>>>>> >>> >>>>>>>> >>> Please advise the right solution implementing that. >>>>>>>> >>> >>>>>>>> >>> Regards, >>>>>>>> >>> Nader. >>>>>>>> >>> >>>>>>>> >>> >>>>>>>> >>> On Wed, Mar 5, 2014 at 11:49 PM, Aaron Rosen < >>>>>>>> aaronoro...@gmail.com> >>>>>>>> >>> wrote: >>>>>>>> >>>> >>>>>>>> >>>> Hi Nader, >>>>>>>> >>>> >>>>>>>> >>>> Devstack's default plugin is ML2. Usually you wouldn't >>>>>>>> 'inherit' one >>>>>>>> >>>> plugin in another. I'm guessing you probably wire a driver >>>>>>>> that ML2 can use >>>>>>>> >>>> though it's hard to tell from the information you've provided >>>>>>>> what you're >>>>>>>> >>>> trying to do. >>>>>>>> >>>> >>>>>>>> >>>> Best, >>>>>>>> >>>> >>>>>>>> >>>> Aaron >>>>>>>> >>>> >>>>>>>> >>>> >>>>>>>> >>>> On Wed, Mar 5, 2014 at 10:42 PM, Nader Lahouti < >>>>>>>> nader.laho...@gmail.com> >>>>>>>> >>>> wrote: >>>>>>>> >>>>> >>>>>>>> >>>>> Hi All, >>>>>>>> >>>>> >>>>>>>> >>>>> I have a question regarding ML2 plugin in neutron: >>>>>>>> >>>>> My understanding is that, 'Ml2Plugin' is the default >>>>>>>> core_plugin for >>>>>>>> >>>>> neutron ML2. We can use either the default plugin or our own >>>>>>>> plugin (i.e. >>>>>>>> >>>>> my_ml2_core_plugin that can be inherited from Ml2Plugin) and >>>>>>>> use it as >>>>>>>> >>>>> core_plugin. >>>>>>>> >>>>> >>>>>>>> >>>>> Is my understanding correct? >>>>>>>> >>>>> >>>>>>>> >>>>> >>>>>>>> >>>>> Regards, >>>>>>>> >>>>> Nader. >>>>>>>> >>>>> >>>>>>>> >>>>> ___ >>>>>>>> >>>>> 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 >>>>>>>> >>>> >>>>>>>> >>> >>>>>>>> >>> ___ 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 >>>>>>>> >>> >>>>>>>> >> >>>>>>>> >> >>>>>>>> >> ___ >>>>>>>> >> 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 >>>>>>>> > >>>>>>>> >>>>>>>> ___ >>>>>>>> OpenStack-dev mailing list >>>>>>>> OpenStack-dev@lists.openstack.org >>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> ___ >>>>>>> OpenStack-dev mailing >>>>>>> listOpenStack-dev@lists.openstack.orghttp://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 >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> ___ >>>>> 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 >>>> >>>> >>> >>> ___ >>> 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 >> >> > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Vinay Bannai Email: vban...@gmail.com Google Voice: 415 938 7576 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Support for multiple provider networks with same VLAN segmentation id

On Tue, Feb 11, 2014 at 12:32 PM, Aaron Rosen wrote: > I believe it would need to be like: > > network_vlan_ranges = physnet1:100:300, phynet2:100:300, phynet3:100:300 > > Additional comments inline: > > On Mon, Feb 10, 2014 at 8:49 PM, Vinay Bannai wrote: > >>

Re: [openstack-dev] [Neutron] Support for multiple provider networks with same VLAN segmentation id

ukura wrote: > On 02/09/2014 12:56 PM, Kyle Mestery wrote: > > On Feb 6, 2014, at 5:24 PM, Vinay Bannai wrote: > > > >> Hello Folks, > >> > >> We are running into a situation where we are not able to create > multiple provider networks with the same

[openstack-dev] [Neutron] Support for multiple provider networks with same VLAN segmentation id

/neutron/+spec/duplicate-providernet-vlans Thanks -- Vinay Bannai Email: vban...@gmail.com Google Voice: 415 938 7576 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev