Ian and Daniel,

Thanks for the comments.

I have neutron spec here and planned to start from Neutron side to expose 
bridge name via port-binding API.

    https://review.openstack.org/#/c/131342/


Thanks,
Ryota

> -----Original Message-----
> From: Ian Wells [mailto:ijw.ubu...@cack.org.uk]
> Sent: Monday, December 15, 2014 8:08 PM
> To: Daniel P. Berrange; OpenStack Development Mailing List (not for usage
> questions)
> Subject: Re: [openstack-dev] [nova][neutron] bridge name generator for vif
> plugging
> 
> Let me write a spec and see what you both think.  I have a couple of things
> we could address here and while it's a bit late it wouldn't be a dramatic
> thing to fix and it might be acceptable.
> 
> 
> On 15 December 2014 at 11:28, Daniel P. Berrange <berra...@redhat.com>
> wrote:
> 
>       On Mon, Dec 15, 2014 at 11:15:56AM +0100, Ian Wells wrote:
>       > Hey Ryota,
>       >
>       > A better way of describing it would be that the bridge name is,
> at present,
>       > generated in *both* Nova *and* Neutron, and the VIF type semantics
> define
>       > how it's calculated.  I think you're right that in both cases
> it would make
>       > more sense for Neutron to tell Nova what the connection endpoint
> was going
>       > to be rather than have Nova calculate it independently.  I'm not
> sure that
>       > that necessarily requires two blueprints, and you don't have a
> spec there
>       > at the moment, which is a problem because the Neutron spec deadline
> is upon
>       > us, but the idea's a good one.  (You might get away without a
> Neutron spec,
>       > since the change to Neutron to add the information should be small
> and
>       > backward compatible, but that's not something I can make judgement
> on.)
> 
>       Yep, the fact that both Nova & Neutron calculat the bridge name
> is a
>       historical accident. Originally Nova did it, because nova-network
> was
>       the only solution. Then Neutron did it too, so it matched what Nova
>       was doing. Clearly if we had Neutron right from the start, then
> it
>       would have been Neutrons responsibility todo this. Nothing in Nova
>       cares what the names are from a functional POV - it just needs to
>       be told what to use.
> 
>       Regards,
>       Daniel
>       --
>       |: http://berrange.com      -o-
> http://www.flickr.com/photos/dberrange/ :|
>       |: http://libvirt.org              -o-
> http://virt-manager.org :|
>       |: http://autobuild.org       -o-
> http://search.cpan.org/~danberr/ :|
>       |: http://entangle-photo.org       -o-
> http://live.gnome.org/gtk-vnc :|
> 
> 
>       _______________________________________________
>       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

Reply via email to