[openstack-dev] [kuryr] kuryr-libnetwork split

Monty Taylor mordred at inaugust.com
Fri Jul 1 13:26:13 UTC 2016


On 07/01/2016 08:10 AM, Antoni Segura Puimedon wrote:
> Hi fellow kuryrs!
> 
> In order to proceed with the split of kuryr into a main lib and it's kuryr
> libnetwork component, we've cloned the contents of openstack/kuryr over to
> openstack/kuryr-libnetwork.
> 
> The idea is that after this, the patches that will go to openstack/kuryr
> will be to trim out the kuryr/kuryr-libnetwork specific parts and make a
> release of the common parts so that openstack/kuryr-libnetwork can start
> using it.
> 
> I propose that we use python namespaces and the current common code in
> kuryr is moved to:
> kuryr/lib/

Check with Doug Hellman about namespaces. We used to use them in some
oslo things and had to step away from them because of some pretty weird
and horrible breakage issues.

> 
> which openstack/kuryr-libnetwork would import like so:
> 
>     from kuryr.lib import binding
> 
> So, right now, patches in review that are for the Docker ipam or remote
> driver, should be moved to openstack/kuryr-libnetwork and soon we should
> make openstack/kuryr-libnetwork add kuryr-lib to the requirements.
> 
> Regards,
> 
> Toni
> 
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 




More information about the OpenStack-dev mailing list