Difference between revisions of "Magnum"
Adrian Otto (talk | contribs) |
Adrian Otto (talk | contribs) (→Frequently Asked Questions) |
||
Line 40: | Line 40: | ||
= Frequently Asked Questions = | = 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. | ||
== Etherpad links == | == Etherpad links == |
Revision as of 22:32, 4 March 2015
Contents
News
- We have announced Magnum's first release, now available for download.
Contributing
- We want you to contribute to Magnum!
Summary
Magnum is an API service developed by the OpenStack Containers Team for OpenStack to make container management tools 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.
The project is under active development by our OpenStack Containers Team. We meet weekly by IRC. Magnum's meetings are normally chaired by our PTL Adrian Otto.
Resources
- Launchpad Project Pages
- Magnum Launchpad Project for Blueprints
- python-magnumclient Launchpad Project for Blueprints
- Mailing List
- OpenStack Mailing List for project related discussion
- Add [Magnum] to the subject line of new posts about this project.
- OpenStack Mailing List Archives for current discussion.
- OpenStack Mailing List for project related discussion
- Code Reviews
- Code Repository
- Specification
IRC
Our developers use IRC in #openstack-containers on freenode for development discussion.
Meetings
- The weekly Containers IRC meeting is held on Tuesdays at 1600 UTC and 2200 UTC on alternating weeks [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.