From 676a0dc4aa73a248be0446b73a810225d21f69e7 Mon Sep 17 00:00:00 2001 From: Adrian Otto Date: Tue, 3 Mar 2015 23:07:36 +0000 Subject: [PATCH] Magnum - OpenStack Containers Service Addition of the Magnum Project - a collaboration of 24 engineers from 13 affiliations to bring containers to Openstack as a first class resource. We just concluded our Midcycle meetup. Magnum builds on Heat to produce Nova instances on which to run application containers. It is licensed under Apache 2.0, and all contributors have signed an OpenStack CLA. All library dependencies allow for unrestricted distribution and deployment. Our PTL is chosen by our contributors, and holds weekly IRC meetings in #openstack-meeting-alt and are logged using Meetbot. We are also available in #openstack-containers to for daily discussion and as a way for users to converse with our developers openly. All Magnum source code is posted to Gerrit, and reviewed. We allow code merge after two +2 votes. Our code is automatically unit tested by the OpenStack CI infrastructure. Our PTL serves as a contact for cross-project teams in OpenStack. We make extensive use of existing software, and have not deliberately reproduced functionality that already exists in other ecosystem projects. Magnum doesn't compete with Swarm, Docker, or Kubernetes, but instead offers a user experience that integrates those systems for use with OpenStack. We are open to integrating best-of-breed technologies that help OpenStack operators offer application containers to their cloud users. We have implemented Magnum using the oslo common libraries and the Pecan+WSME WSGI framework. Magnum completely conforms to the OpenStack development style. Project direction has been publically discussed at the Oregon Nova Midcycle, the Paris OpenStack Design Summit, and in March 2015 at the Magnum Midcycle in San Francisco. We use the openstack-dev ML for project discussion and do not use any other mailing lists. Magnum is compatible with OpenStack APIs, and uses Keystone middleware to integrate with OpenStack Identity. All per-tenant Magnum infrastructure is deployed using OpenStack Orchestration using HOT files. There are numerous active contributors from several affiliations who have allocated full-time engineers to contribute to Magnum. Magnum is different from Nova, because it provides a purpose built API to manage application containers, which have a distinctly different lifecycle and operations than Nova (machine) Instances. Magnum is also different from Docker and Kubernetes, by offering an asynchronous REST API that's compatible with Keystone, and a complete multi-tenancy implementation. It does not perform orchestration internally, and instead relies on OpenStack Orchestration. Change-Id: I1880a7310876c54bd5bd4bc16c6c5132c6ecb706 --- reference/projects.yaml | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/reference/projects.yaml b/reference/projects.yaml index 2f6868481..b25898c82 100644 --- a/reference/projects.yaml +++ b/reference/projects.yaml @@ -474,6 +474,17 @@ Designate: - repo: openstack/designate-specs - repo: openstack/python-designateclient +Magnum: + ptl: Adrian Otto (aotto) + service: Containers Service + mission: > + To provide a set of services for management of application containers + in a multitenant cloud environment. + url: https://wiki.openstack.org/wiki/Magnum + projects: + - repo: openstack/magnum + - repo: openstack/python-magnumclient + Manila: ptl: Ben Swartzlander (bswartz) service: Shared file systems