Open Stack

Hello Everybody !!!

As we discussed in the meeting yesterday, I have submitted restructured
patches now in kuryr-lib and kuryr-libnetwork to address only dropping
non-relevant code and adding kuryr-lib as dependency to kuryr-libnetwork.

Please provide review comments so that i quickly reiterate over patches and
eventually we will be able to move our existing under review patches also
from kuryr to kuryr-libnetwork.

Since RPC support is also ready, will be submitting the same in both repos
as seperate patches(linked with dependency)

Here is the link for base patchsets:
Kuryr-libnetwork:  https://review.openstack.org/#/c/337350/
kuryr-lib: https://review.openstack.org/#/c/336784/



Regards
Vikas

On Fri, Jul 1, 2016 at 6:40 PM, Antoni Segura Puimedon <
toni+openstackml at midokura.com> 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/
>
>
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160705/0d032a4c/attachment.html>