Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang
Hi all: The repository of Fuxi-golang has been set up! We can submit bugs and bps[1] through launchpad now. To Antoni Segura, this patch[2] will need your +1 to be merged. So could you please take a look at it. Thanks very much! [1] https://launchpad.net/fuxi-golang [2] https://review.openstack.org/#/c/470111/ Best Wishes zengchen At 2017-05-31 23:55:15, "Hongbin Lu" wrote: Please find my replies inline. Best regards, Hongbin From: Spyros Trigazis [mailto:strig...@gmail.com] Sent: May-30-17 9:56 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang On 30 May 2017 at 15:26, Hongbin Lu wrote: Please consider leveraging Fuxi instead. Is there a missing functionality from rexray? [Hongbin Lu] From my understanding, Rexray targets on the overcloud use cases and assumes that containers are running on top of nova instances. You mentioned Magnum is leveraging Rexray for Cinder integration. Actually, I am the core reviewer who reviewed and approved those Rexray patches. From what I observed, the functionalities provided by Rexray are minimal. What it was doing is simply calling Cinder API to search an existing volume, attach the volume to the Nova instance, and let docker to bind-mount the volume to the container. At the time I was testing it, it seems to have some mystery bugs that prevented me to get the cluster to work. It was packaged by a large container image, which might take more than 5 minutes to pull down. With that said, Rexray might be a choice for someone who are looking for cross cloud-providers solution. Fuxi will focus on OpenStack and targets on both overcloud and undercloud use cases. That means Fuxi can work with Nova+Cinder or a standalone Cinder. As John pointed out in another reply, another benefit of Fuxi is to resolve the fragmentation problem of existing solutions. Those are the differentiators of Fuxi. Kuryr/Fuxi team is working very hard to deliver the docker network/storage plugins. I wish you will work with us to get them integrated with Magnum-provisioned cluster. Patches are welcome to support fuxi as an *option* instead of rexray, so users can choose. Currently, COE clusters provisioned by Magnum is far away from enterprise-ready. I think the Magnum project will be better off if it can adopt Kuryr/Fuxi which will give you a better OpenStack integration. Best regards, Hongbin fuxi feature request: Add authentication using a trustee and a trustID. [Hongbin Lu] I believe this is already supported. Cheers, Spyros From: Spyros Trigazis [mailto:strig...@gmail.com] Sent: May-30-17 7:47 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang 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 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" 写道: On Thu, May 25, 2017 at 10:01 PM, zengchen 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" wrote: On Thu, May 25, 2017 at 5:50 AM, zengchen wrote: Very sorry to foget attaching the
Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang
Hi Hongbin. Regarding your comments below, some quick clarifications for people less familiar with Magnum. 1. Rexray / Cinder integration - Magnum uses an alpine based rexray image, compressed size is 33MB (the download size), so pretty good - Deploying a full Magnum cluster of 128 nodes takes less than 5 minutes in our production environment. The issue you mention only exists in the upstream builds and is valid for all container images, and is due to nodes in infra having a combination of non-nested virtualization and/or slow connectivity (there were several attempts to fix this) - Not sure about mystery bugs, but the ones we found were fixed by Mathieu: https://github.com/codedellemc/libstorage/pull/243 2. Enterprise ready Certainly this means different things for different people, at CERN we run ~80 clusters in our production service covering many use cases. Magnum currently lacks the ability to properly upgrade the COE version for running clusters, which is a problem for long lived services (which are not the majority of our use cases today). This is the main focus on the currently cycle. Hope this adds some relevant information. Cheers, Ricardo On Wed, May 31, 2017 at 5:55 PM, Hongbin Lu wrote: > Please find my replies inline. > > > > Best regards, > > Hongbin > > > > From: Spyros Trigazis [mailto:strig...@gmail.com] > Sent: May-30-17 9:56 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for > Fuxi-golang > > > > > > > > On 30 May 2017 at 15:26, Hongbin Lu wrote: > > Please consider leveraging Fuxi instead. > > > > Is there a missing functionality from rexray? > > > > [Hongbin Lu] From my understanding, Rexray targets on the overcloud use > cases and assumes that containers are running on top of nova instances. You > mentioned Magnum is leveraging Rexray for Cinder integration. Actually, I am > the core reviewer who reviewed and approved those Rexray patches. From what > I observed, the functionalities provided by Rexray are minimal. What it was > doing is simply calling Cinder API to search an existing volume, attach the > volume to the Nova instance, and let docker to bind-mount the volume to the > container. At the time I was testing it, it seems to have some mystery bugs > that prevented me to get the cluster to work. It was packaged by a large > container image, which might take more than 5 minutes to pull down. With > that said, Rexray might be a choice for someone who are looking for cross > cloud-providers solution. Fuxi will focus on OpenStack and targets on both > overcloud and undercloud use cases. That means Fuxi can work with > Nova+Cinder or a standalone Cinder. As John pointed out in another reply, > another benefit of Fuxi is to resolve the fragmentation problem of existing > solutions. Those are the differentiators of Fuxi. > > > > Kuryr/Fuxi team is working very hard to deliver the docker network/storage > plugins. I wish you will work with us to get them integrated with > Magnum-provisioned cluster. > > > > Patches are welcome to support fuxi as an *option* instead of rexray, so > users can choose. > > > > Currently, COE clusters provisioned by Magnum is far away from > enterprise-ready. I think the Magnum project will be better off if it can > adopt Kuryr/Fuxi which will give you a better OpenStack integration. > > > > Best regards, > > Hongbin > > > > fuxi feature request: Add authentication using a trustee and a trustID. > > > > [Hongbin Lu] I believe this is already supported. > > > > Cheers, > Spyros > > > > > > From: Spyros Trigazis [mailto:strig...@gmail.com] > Sent: May-30-17 7:47 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for > Fuxi-golang > > > > 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 wrote: > > Hi John & Ben: > > I have committed a patch[1] to add a
Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang
Please find my replies inline. Best regards, Hongbin From: Spyros Trigazis [mailto:strig...@gmail.com] Sent: May-30-17 9:56 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang On 30 May 2017 at 15:26, Hongbin Lu mailto:hongbin...@huawei.com>> wrote: Please consider leveraging Fuxi instead. Is there a missing functionality from rexray? [Hongbin Lu] From my understanding, Rexray targets on the overcloud use cases and assumes that containers are running on top of nova instances. You mentioned Magnum is leveraging Rexray for Cinder integration. Actually, I am the core reviewer who reviewed and approved those Rexray patches. From what I observed, the functionalities provided by Rexray are minimal. What it was doing is simply calling Cinder API to search an existing volume, attach the volume to the Nova instance, and let docker to bind-mount the volume to the container. At the time I was testing it, it seems to have some mystery bugs that prevented me to get the cluster to work. It was packaged by a large container image, which might take more than 5 minutes to pull down. With that said, Rexray might be a choice for someone who are looking for cross cloud-providers solution. Fuxi will focus on OpenStack and targets on both overcloud and undercloud use cases. That means Fuxi can work with Nova+Cinder or a standalone Cinder. As John pointed out in another reply, another benefit of Fuxi is to resolve the fragmentation problem of existing solutions. Those are the differentiators of Fuxi. Kuryr/Fuxi team is working very hard to deliver the docker network/storage plugins. I wish you will work with us to get them integrated with Magnum-provisioned cluster. Patches are welcome to support fuxi as an *option* instead of rexray, so users can choose. Currently, COE clusters provisioned by Magnum is far away from enterprise-ready. I think the Magnum project will be better off if it can adopt Kuryr/Fuxi which will give you a better OpenStack integration. Best regards, Hongbin fuxi feature request: Add authentication using a trustee and a trustID. [Hongbin Lu] I believe this is already supported. Cheers, Spyros From: Spyros Trigazis [mailto:strig...@gmail.com<mailto:strig...@gmail.com>] Sent: May-30-17 7:47 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang 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 mailto:chenzeng...@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" mailto:john.griffi...@gmail.com>> 写道: On Thu, May 25, 2017 at 10:01 PM, zengchen mailto:chenzeng...@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" mailto:john.griffi...@gmail.com>> wrote: On Thu, May 25, 2017 at 5:50 AM, zengchen mailto:chenzeng...@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" mailto:chenzeng...@163.com>> wrote: Hi guys: hongbin had committed a bp of rewriting Fuxi with go language[1]. My question i
Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang
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" 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 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" 写道: On Thu, May 25, 2017 at 10:01 PM, zengchen 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" wrote: On Thu, May 25, 2017 at 5:50 AM, zengchen 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" 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-requ...@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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang
On Tue, May 30, 2017 at 5:47 AM, Spyros Trigazis 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 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" 写道: >> >> >> >> On Thu, May 25, 2017 at 10:01 PM, zengchen 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" >>> wrote: >>> >>> >>> >>> On Thu, May 25, 2017 at 5:50 AM, zengchen 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" 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-requ...@lists.op enstack.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-requ...@lists.op >>> enstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >> >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib >> e >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > Hi Spryos, Thanks for pointing that out, actually I wasn't aware that Magnum had adopted RexRay so that's good to know. There are actually a number of options out there RexRay, Cinder-Docker-Driver etc. They're all cool, and if they work for people that's great! The only problem I've had with any of these other options is that most are under ownership of a single storage vendor. Even though the licensing is agreeable, and in theory it shouldn't be a problem to contribute, the fact is that most organizations aren't going to be too keen on allowing their employees to contribute to a competitors project. Part of the goal of havin
Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang
On 30 May 2017 at 15:26, Hongbin Lu wrote: > Please consider leveraging Fuxi instead. > Is there a missing functionality from rexray? > Kuryr/Fuxi team is working very hard to deliver the docker network/storage > plugins. I wish you will work with us to get them integrated with > Magnum-provisioned cluster. > Patches are welcome to support fuxi as an *option* instead of rexray, so users can choose. > Currently, COE clusters provisioned by Magnum is far away from > enterprise-ready. I think the Magnum project will be better off if it can > adopt Kuryr/Fuxi which will give you a better OpenStack integration. > > > > Best regards, > > Hongbin > fuxi feature request: Add authentication using a trustee and a trustID. Cheers, Spyros > > > *From:* Spyros Trigazis [mailto:strig...@gmail.com] > *Sent:* May-30-17 7:47 AM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for > Fuxi-golang > > > > 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/magn > um/drivers/common/templates/swarm/fragments/volume- > service.sh?h=stable/ocata > > > > On 27 May 2017 at 12:15, zengchen 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" 写道: > > > > > > On Thu, May 25, 2017 at 10:01 PM, zengchen 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" wrote: > > > > > > On Thu, May 25, 2017 at 5:50 AM, zengchen 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" 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-requ...@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 > > > > > __ > OpenSt
Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang
Please consider leveraging Fuxi instead. Kuryr/Fuxi team is working very hard to deliver the docker network/storage plugins. I wish you will work with us to get them integrated with Magnum-provisioned cluster. Currently, COE clusters provisioned by Magnum is far away from enterprise-ready. I think the Magnum project will be better off if it can adopt Kuryr/Fuxi which will give you a better OpenStack integration. Best regards, Hongbin From: Spyros Trigazis [mailto:strig...@gmail.com] Sent: May-30-17 7:47 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang 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 mailto:chenzeng...@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" mailto:john.griffi...@gmail.com>> 写道: On Thu, May 25, 2017 at 10:01 PM, zengchen mailto:chenzeng...@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" mailto:john.griffi...@gmail.com>> wrote: On Thu, May 25, 2017 at 5:50 AM, zengchen mailto:chenzeng...@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" mailto:chenzeng...@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-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang
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 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" 写道: > > > > On Thu, May 25, 2017 at 10:01 PM, zengchen 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" wrote: >> >> >> >> On Thu, May 25, 2017 at 5:50 AM, zengchen 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" 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-requ...@lists.op >>> enstack.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-requ...@lists.openstack.org?subject:unsubscrib >> e >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang
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" 写道: On Thu, May 25, 2017 at 10:01 PM, zengchen 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" wrote: On Thu, May 25, 2017 at 5:50 AM, zengchen 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" 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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang
On Thu, May 25, 2017 at 10:01 PM, zengchen 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" wrote: > > > > On Thu, May 25, 2017 at 5:50 AM, zengchen 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" 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-requ...@lists.openstack.org?subject:unsubscrib >> e >> 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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang
Ya we should combine all the related efforts :) #openstack-cinder would be great place to chat, shall we set a time for the meeting ? On Fri, May 26, 2017 at 11:40 AM, John Griffith wrote: > > > On Thu, May 25, 2017 at 6:25 PM, Zhipeng Huang > wrote: > >> Hi John and Zeng, >> >> The OpenSDS community already developed a golang client for the >> os-brick[1], I think we could host the new golang os-brick code there as a >> new repo and after things settled port the code back to OpenStack >> >> [1]https://github.com/opensds/opensds/blob/master/pkg/dock/p >> lugins/connector/connector.go >> >> On Thu, May 25, 2017 at 10:47 PM, John Griffith > > wrote: >> >>> >>> >>> On Thu, May 25, 2017 at 5:50 AM, zengchen 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" 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-requ...@lists.op enstack.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-requ...@lists.op >>> enstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >> >> >> -- >> Zhipeng (Howard) Huang >> >> Standard Engineer >> IT Standard & Patent/IT Product Line >> Huawei Technologies Co,. Ltd >> Email: huangzhip...@huawei.com >> Office: Huawei Industrial Base, Longgang, Shenzhen >> >> (Previous) >> Research Assistant >> Mobile Ad-Hoc Network Lab, Calit2 >> University of California, Irvine >> Email: zhipe...@uci.edu >> Office: Calit2 Building Room 2402 >> >> OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado >> >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib >> e >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> I like the idea of the service version of brick, and then the golang > bindings. There's a lot of good investment already in os-brick that it > would be great to leverage. Walt and Ivan mentioned that they had a POC > for this a while back, might be worth considering taking the fork > referenced in the BP and submitting that upstream for the community? > #openstack-cinder IRC channel would be a great place to sync up on these > aspects in real time if folks would like. > > Thanks, > John > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Product Line Huawei Technologies Co,. Ltd Email: huangzhip...@huawei.com Office: Huawei Industrial Base, Longgang, Shenzhen (Previous) Research Assistant Mobile Ad-Hoc Network Lab, Calit2 University of California, Irvine Email: zhipe...@uci.edu Office: Calit2 Building Room 2402 OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang
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" wrote: On Thu, May 25, 2017 at 5:50 AM, zengchen 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" 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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang
On Thu, May 25, 2017 at 6:25 PM, Zhipeng Huang wrote: > Hi John and Zeng, > > The OpenSDS community already developed a golang client for the > os-brick[1], I think we could host the new golang os-brick code there as a > new repo and after things settled port the code back to OpenStack > > [1]https://github.com/opensds/opensds/blob/master/pkg/dock/ > plugins/connector/connector.go > > On Thu, May 25, 2017 at 10:47 PM, John Griffith > wrote: > >> >> >> On Thu, May 25, 2017 at 5:50 AM, zengchen 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" 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-requ...@lists.op >>> enstack.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-requ...@lists.openstack.org?subject:unsubscrib >> e >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > > -- > Zhipeng (Howard) Huang > > Standard Engineer > IT Standard & Patent/IT Product Line > Huawei Technologies Co,. Ltd > Email: huangzhip...@huawei.com > Office: Huawei Industrial Base, Longgang, Shenzhen > > (Previous) > Research Assistant > Mobile Ad-Hoc Network Lab, Calit2 > University of California, Irvine > Email: zhipe...@uci.edu > Office: Calit2 Building Room 2402 > > OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > I like the idea of the service version of brick, and then the golang bindings. There's a lot of good investment already in os-brick that it would be great to leverage. Walt and Ivan mentioned that they had a POC for this a while back, might be worth considering taking the fork referenced in the BP and submitting that upstream for the community? #openstack-cinder IRC channel would be a great place to sync up on these aspects in real time if folks would like. Thanks, John __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang
Hi John and Zeng, The OpenSDS community already developed a golang client for the os-brick[1], I think we could host the new golang os-brick code there as a new repo and after things settled port the code back to OpenStack [1] https://github.com/opensds/opensds/blob/master/pkg/dock/plugins/connector/connector.go On Thu, May 25, 2017 at 10:47 PM, John Griffith wrote: > > > On Thu, May 25, 2017 at 5:50 AM, zengchen 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" 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-requ...@lists.openstack.org?subject:unsubscrib >> e >> 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-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Product Line Huawei Technologies Co,. Ltd Email: huangzhip...@huawei.com Office: Huawei Industrial Base, Longgang, Shenzhen (Previous) Research Assistant Mobile Ad-Hoc Network Lab, Calit2 University of California, Irvine Email: zhipe...@uci.edu Office: Calit2 Building Room 2402 OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang
On Thu, May 25, 2017 at 5:50 AM, zengchen 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" 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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang
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" 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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang
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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev