On 30 May 2017 at 15:26, Hongbin Lu <hongbin...@huawei.com> 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 <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" <john.griffi...@gmail.com> 写道:
>
>
>
>
>
> On Thu, May 25, 2017 at 10:01 PM, zengchen <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" <john.griffi...@gmail.com> wrote:
>
>
>
>
>
> On Thu, May 25, 2017 at 5:50 AM, zengchen <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" <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://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
>
>
__________________________________________________________________________
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

Reply via email to