[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 __ 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] [magnum] Proposed Revision to Magnum's Mission
Adrian, fyi, there's one more already filed by Josh - https://review.openstack.org/#/c/310941/ -- Dims On Fri, Apr 29, 2016 at 7:47 PM, Adrian Otto wrote: > 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 > > __ > 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 > -- Davanum Srinivas :: https://twitter.com/dims __ 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] [magnum] Proposed Revision to Magnum's Mission
Cool, abandoning mine as it seems the team is working on one anyway. (I just didn't want a mission statement change to wait until some unknown project comes along, someday in the future...) -Josh Davanum Srinivas wrote: Adrian, fyi, there's one more already filed by Josh - https://review.openstack.org/#/c/310941/ -- Dims On Fri, Apr 29, 2016 at 7:47 PM, Adrian Otto wrote: 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 __ 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] [magnum] Proposed Revision to Magnum's Mission
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.o...@rackspace.com] Sent: April-29-16 8:47 PM To: openstack-dev@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 __ 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