[openstack-dev] [magnum] Seek advices for a licence issue
hongbin.lu at huawei.com
Wed Apr 20 21:35:47 UTC 2016
I have went though the announcement in details, From my point of view, it seems to resolve the license issue that was blocking us in before. I have included the Magnum team in ML to see if our team members have any comment.
Thanks for the support from foundation.
From: Mark Collier [mailto:mark at openstack.org]
Sent: April-19-16 12:36 PM
To: Hongbin Lu
Cc: foundation at lists.openstack.org; Guang Ya GY Liu
Subject: Re: [OpenStack Foundation] [magnum] Seek advices for a licence issue
Hopefully today’s news that Mesosphere is open major sourcing components of DCOS under an Apache 2.0 license will make things easier:
I’ll be interested to hear your take after you have time to look at it in more detail, Hongbin.
On Apr 9, 2016, at 10:02 AM, Hongbin Lu <hongbin.lu at huawei.com<mailto:hongbin.lu at huawei.com>> wrote:
A brief introduction to myself. I am the Magnum Project Team Lead (PTL). Magnum is the OpenStack container service. I wrote this email because the Magnum team is seeking clarification for a licence issue for shipping third-party software (DCOS  in particular) and I was advised to consult OpenStack Board of Directors in this regards.
Before getting into the question, I think it is better to provide some backgroup information. A feature provided by Magnum is to provision container management tool on top of a set of Nova instances. One of the container management tool Magnum supports is Apache Mesos . Generally speaking, Magnum ships Mesos by providing a custom cloud image with the necessary packages pre-installed. So far, all the shipped components are open source with appropriate license, so we are good so far.
Recently, one of our contributors suggested to extend the Mesos support to DCOS . The Magnum team is unclear if there is a license issue for shipping DCOS, which looks like a close-source product but has community version in Amazon Web Services . I want to know what are the appropriate actions Magnum team should take in this pursuit, or we should stop pursuing this direction further? Advices are greatly appreciated. Please let us know if we need to provide further information. Thanks.
Foundation mailing list
Foundation at lists.openstack.org<mailto:Foundation at lists.openstack.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev