Thanks Toni. On 5 Nov 2015 16:02, "Antoni Segura Puimedon" <[email protected]> wrote:
> > > On Thu, Nov 5, 2015 at 10:47 AM, Vikas Choudhary < > [email protected]> wrote: > >> ++ [Neutron] tag >> >> >> On Thu, Nov 5, 2015 at 10:40 AM, Vikas Choudhary < >> [email protected]> wrote: >> >>> Hi all, >>> >>> By network control plane i specifically mean here sharing network state >>> across docker daemons sitting on different hosts/nova_vms in multi-host >>> networking. >>> >>> libnetwork provides flexibility where vendors have a choice between >>> network control plane to be handled by libnetwork(libkv) or remote driver >>> itself OOB. Vendor can choose to "mute" libnetwork/libkv by advertising >>> remote driver capability as "local". >>> >>> "local" is our current default "capability" configuration in kuryr. >>> >>> I have following queries: >>> 1. Does it mean Kuryr is taking responsibility of sharing network state >>> across docker daemons? If yes, network created on one docker host should be >>> visible in "docker network ls" on other hosts. To achieve this, I guess >>> kuryr driver will need help of some distributed data-store like consul etc. >>> so that kuryr driver on other hosts could create network in docker on other >>> hosts. Is this correct? >>> >>> 2. Why we cannot set default scope as "Global" and let libkv do the >>> network state sync work? >>> >>> Thoughts? >>> >> > Hi Vikas, > > Thanks for raising this. As part of the current work on enabling > multi-node we should be moving the default to 'global'. > > >> >>> Regards >>> -Vikas Choudhary >>> >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> [email protected]?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
