[openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang

zengchen chenzeng765 at 163.com
Wed May 31 14:12:41 UTC 2017


Hi, Spyros:
    Recently, Rexray can supply volume for Docker by integrating Cinder. It is great!  However, comparing to Fuxi,  Rexray is a little heavier. Because Rexray must depend on Libstorage to communicate with Cinder. Fuxi-golang is just a new project which re-implements Fuxi in go language. From the standpoint of Fuxi, Fuxi-golang is just her 'sister'.


    By the way, you said you have been integrating Manila to Libstorage. But I don't see the relevant materials from the link[1]. Is the link wrong or do I miss something. Could you give more details about your work on integrating Manila?  Thanks very much!


Best Wishes!
zengchen
. 
[1] http://git.openstack.org/cgit/openstack/magnum/tree/magnum/drivers/common/templates/swarm/fragments/volume-service.sh?h=stable/ocata





At 2017-05-30 19:47:26, "Spyros Trigazis" <strigazi at gmail.com> wrote:

FYI, there is already a cinder volume driver for docker available, written
in golang, from rexray [1].

Our team recently contributed to libstorage [3], it could support manila too. Rexray
also supports the popular cloud providers.

Magnum's docker swarm cluster driver, already leverages rexray for cinder integration. [2]

Cheers,
Spyros 


[1] https://github.com/codedellemc/rexray/releases/tag/v0.9.0 
[2] https://github.com/codedellemc/libstorage/releases/tag/v0.6.0
[3] http://git.openstack.org/cgit/openstack/magnum/tree/magnum/drivers/common/templates/swarm/fragments/volume-service.sh?h=stable/ocata


On 27 May 2017 at 12:15, zengchen <chenzeng765 at 163.com> wrote:

Hi John & Ben:
 I have committed a patch[1] to add a new repository to Openstack. Please take a look at it. Thanks very much!


 [1]: https://review.openstack.org/#/c/468635


Best Wishes!
zengchen






在 2017-05-26 21:30:48,"John Griffith" <john.griffith8 at gmail.com> 写道:





On Thu, May 25, 2017 at 10:01 PM, zengchen <chenzeng765 at 163.com> wrote:



Hi john:
    I have seen your updates on the bp. I agree with your plan on how to develop the codes.
    However, there is one issue I have to remind you that at present, Fuxi not only can convert
 Cinder volume to Docker, but also Manila file. So, do you consider to involve Manila part of codes
 in the new Fuxi-golang?
Agreed, that's a really good and important point.  Yes, I believe Ben Swartzlander
 
is interested, we can check with him and make sure but I certainly hope that Manila would be interested.
Besides, IMO, It is better to create a repository for Fuxi-golang, because
 Fuxi is the project of Openstack,
Yeah, that seems fine; I just didn't know if there needed to be any more conversation with other folks on any of this before charing ahead on new repos etc.  Doesn't matter much to me though.
 


   Thanks very much!


Best Wishes!
zengchen





At 2017-05-25 22:47:29, "John Griffith" <john.griffith8 at gmail.com> wrote:





On Thu, May 25, 2017 at 5:50 AM, zengchen <chenzeng765 at 163.com> wrote:

Very sorry to foget attaching the link for bp of rewriting Fuxi with go language.
https://blueprints.launchpad.net/fuxi/+spec/convert-to-golang




At 2017-05-25 19:46:54, "zengchen" <chenzeng765 at 163.com> wrote:

Hi guys:
    hongbin had committed a bp of rewriting Fuxi with go language[1]. My question is where to commit codes for it.
We have two choice, 1. create a new repository, 2. create a new branch.  IMO, the first one is much better. Because
there are many differences in the layer of infrastructure, such as CI.  What's your opinion? Thanks very much
 
Best Wishes
zengchen

__________________________________________________________________________
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


Hi Zengchen,


For now I was thinking just use Github and PR's outside of the OpenStack projects to bootstrap things and see how far we can get.  I'll update the BP this morning with what I believe to be the key tasks to work through.


Thanks,
John



__________________________________________________________________________
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





__________________________________________________________________________
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



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170531/5571587c/attachment.html>


More information about the OpenStack-dev mailing list