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

zengchen chenzeng765 at 163.com
Fri May 26 04:01:00 UTC 2017



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? Besides, IMO, It is better to create a repository for Fuxi-golang, because
 Fuxi is the project of Openstack,


   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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170526/73a92ef6/attachment.html>


More information about the OpenStack-dev mailing list