The baymodel object and ReST object is used to control bay properties for different bay models. It is then possible to launch bay models using this functionality. Change-Id: I317bda292719ca3f4649283f7e27674c813cc3b0
|9 years ago|
|doc/source||9 years ago|
|etc/magnum||9 years ago|
|magnum||9 years ago|
|specs||9 years ago|
|.coveragerc||9 years ago|
|.gitignore||9 years ago|
|.gitreview||9 years ago|
|.mailmap||9 years ago|
|.testr.conf||9 years ago|
|CONTRIBUTING.rst||9 years ago|
|Dockerfile||9 years ago|
|HACKING.rst||9 years ago|
|LICENSE||9 years ago|
|MANIFEST.in||9 years ago|
|README.rst||9 years ago|
|babel.cfg||9 years ago|
|openstack-common.conf||9 years ago|
|requirements.txt||9 years ago|
|setup.cfg||9 years ago|
|setup.py||9 years ago|
|test-requirements.txt||9 years ago|
|tox.ini||9 years ago|
new Openstack project for containers.
- Free software: Apache license
- Documentation: http://docs.openstack.org/developer/magnum
- Source: http://git.openstack.org/cgit/stackforge/magnum
- Bugs: http://bugs.launchpad.net/magnum
- ReST Client: http://git.openstack.org/cgit/stackforge/python-magnumclient
There are five different types of objects in the Magnum system:
- Bay: A collection of node objects where work is scheduled
- Node: A baremetal or virtual machine where work executes
- Pod: A collection of containers running on one physical or virtual machine
- Service: A port to Pod mapping
- Container: A docker container
Two binaries work together to compose the Magnum system. The first binary accessed by the python-magnumclient code is the magnum-api ReST server. The ReST server may run as one process or multiple processes. When a ReST request is sent to the client API, the request is sent via AMQP to the magnum-backend process. The ReST server is horizontally scalable. AT this time, the backend is limited to one process, but we intend to add horizontal scalability to the backend as well.
The magnum-backend process runs on a controller machine and connects to a kubernetes or docker ReST API endpoint. The kubernetes and docker ReST API endpoints are managed by the bay object.
When service or pod objects are created, Kubernetes is directly contacted via the k8s ReST API. When container objects are acted upon, the docker ReST API is directly contacted.
- Abstractions for bays, containers, nodes, pods, and services
- Integration with Kubernetes and Docker for backend container technology.
- Integration with Keystone for multi-tenant security.
- Integraiton with Neutron for k8s multi-tenancy network security.
Installation and Usage
For installation and usage, please read the developer installation guide located at doc/source/dev/dev-quickstart.rst.