[openstack-dev] [Kuryr] Clarification of expanded mission statement

Fox, Kevin M Kevin.Fox at pnnl.gov
Fri Mar 18 20:12:29 UTC 2016

I'd assume a volume plugin for cinder support and/or a volume plugin for manila support?

Either would be useful.

From: Russell Bryant [rbryant at redhat.com]
Sent: Friday, March 18, 2016 4:59 AM
To: OpenStack Development Mailing List (not for usage questions); gal.sagie at gmail.com
Subject: [openstack-dev] [Kuryr] Clarification of expanded mission statement

The Kuryr project proposed an update to its mission statement and I agreed to start a ML thread seeking clarification on the update.


The change expands the current networking focus to also include storage integration.

I was interested to learn more about what work you expect to be doing.  On the networking side, it's clear to me: a libnetwork plugin, and now perhaps a CNI plugin.  What specific code do you expect to deliver as a part of your expanded scope?  Will that code be in Kuryr, or be in upstream projects?

If you don't know yet, that's fine.  I was just curious what you had in mind.  We don't really have OpenStack projects that are organizing around contributing to other upstreams, but I think this case is fine.

Russell Bryant
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160318/47b528d0/attachment.html>

More information about the OpenStack-dev mailing list