Open Stack

Hi team,

As Adrian mentioned, we decided to narrow the scope of the Magnum project, and needed to revise Magnum’s mission statement to reflect our mission clearly and accurately. I would suggest to work on this effort as a team and created an etherpad for that:

https://etherpad.openstack.org/p/magnum-mission-statement

Your comments on the etherpad will be appreciated.

Best regards,
Hongbin

From: Adrian Otto [mailto:adrian.otto at rackspace.com]
Sent: April-29-16 8:47 PM
To: openstack-dev at lists.openstack.org
Subject: [openstack-dev] [magnum] Proposed Revision to Magnum's Mission

Magnum Team,

In accordance with our Fishbowl discussion yesterday at the Newton Design Summit in Austin, I have proposed the following revision to Magnum’s mission statement:

https://review.openstack.org/311476

The idea is to narrow the scope of our Magnum project to allow us to focus on making popular COE software work great with OpenStack, and make it easy for OpenStack cloud users to quickly set up fleets of cloud capacity managed by chosen COE software (such as Swam, Kubernetes, Mesos, etc.). Cloud operators and users will value Multi-Tenancy for COE’s, tight integration with OpenStack, and the ability to source this all as a self-service resource.

We agreed to deprecate and remove the /containers resource from Magnum’s API, and will leave the door open for a new OpenStack project with its own name and mission to satisfy the interests of our community members who want an OpenStack API service that abstracts one or more COE’s.

Regards,

Adrian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160502/4bae4f95/attachment.html>