Magnum is an OpenStack API service developed by the OpenStack Containers Team making container orchestration engines such as Docker and Kubernetes available as first class resources in OpenStack. Magnum uses Heat to orchestrate an OS image which contains Docker and Kubernetes and runs that image in either virtual machines or bare metal in a cluster configuration. Click below for a 5 minute demo of how Magnum works.
- 2015-10-20 We have published a list of sessions to attend at the Mitaka Design Summit in Tokyo
- 2015-08-26 Magnum will be presenting a session on Magnum at the 2015 OpenStack Summit in Tokyo on October 28 4:40pm - 5:20pm Video
- 2015-05-21 We presented a session on Magnum at the 2015 OpenStack Summit in Vancouver on Thursday, May 21 9:00am - 9:40am US/Pacific. Video
- 2015-03-24 Magnum has officially joined the OpenStack project list upon approval by a unanimous vote by the Technical Committee.
- 2015-03-09 Our Kilo-2 release is now available for download.
- 2015-01-20 We have announced Magnum's first release, now available for download.
Getting Started / Download
To get started with Magnum, see: Our Quickstart Guide
Version 22.214.171.124b1 (Liberty Beta 1) Downloads:
- We want you to contribute to Magnum!
- Launchpad Project Pages
- Mailing List
- Code Reviews
- Code Repository
- git clone git://git.openstack.org/openstack/magnum
Our developers use IRC in #openstack-containers on freenode for development discussion.
- The weekly Containers IRC meeting is held on Tuesdays at 1600 UTC [schedule].
- 2014 Containers Meeting Archive
Frequently Asked Questions
1) How is Magnum is different from Nova?
Magnum provides a purpose built API to manage application containers, which have a distinctly different life cycle and operations than Nova (machine) Instances. We actually use Nova instances to run our application containers.
2) How is Magnum different than Docker or Kubernetes?
Magnum offers an asynchronous API that's compatible with Keystone, and a complete multi-tenancy implementation. It does not perform orchestration internally, and instead relies on OpenStack Orchestration. Magnum does leverage both Kubernetes and Docker as components.
3) Is this the same thing as Nova-Docker?
No, Nova-Docker is a virt driver for Nova that allows containers to be created as Nova instances. This is suitable for use cases when you want to treat a container like a lightweight machine. Magnum provides container specific features that are beyond the scope of Nova's API, and implements its own API to surface these features in a way that is consistent with other OpenStack services. Containers started by Magnum are run on top of Nova instances that are created using Heat.
4) Who is Magnum for?
Magnum is for OpenStack cloud operators (public or private) who want to offer a self-service solution to provide containers to their cloud users as a managed hosted service. Magnum simplifies the required integration with OpenStack, and allows for cloud users who can already launch cloud resources such as Nova Instances, Cinder Volumes, Trove Databases, etc. to also create application containers to run applications in an environment that provides advanced features that are beyond the scope of existing cloud resources. The same identity credentials used to create IaaS resources can be used to run containerized applications using Magnum. Some examples of advanced features available with Magnum are the ability to scale an application to a specified number of instances, to cause your application to automatically re-spawn an instance in the event of a failure, and to pack applications together more tightly than would be possible using Virtual Machines.
5) Will I get the same thing if I use the Docker resource in Heat?
No, the Docker Heat resource does not provide a resource scheduler, or a choice of container technology used. It is specific to Docker, and uses Glance to store container images. It does not currently allow for layered image features, which can cause containers to take longer to start than if layered images are used with a locally cached base image. Magnum leverages all of the speed benefits that Docker offers.
6) What does multi-tenancy mean in Magnum (Is Magnum Secure)?
Resources such as Containers, Services, Pods, Bays, etc. started by Magnum can only be viewed and accessed by users of the tenant that created them. Bays are not shared, meaning that containers will not run on the same kernel as neighboring tenants. This is a key security feature that allows containers belonging to the same tenant to be tightly packed within the same Pods and Bays, but runs separate kernels (in separate Nova Instances) between different tenants. This is different than using a system like Kubernetes without Magnum, which is intended to be used only by a single tenant, and leaves the security isolation design up to the implementer. Using Magnum provides the same level of security isolation as Nova provides when running Virtual Machines belonging to different tenants on the same compute nodes.