617b772e55
Problem description: If DevStack is used to instantiate the magnum plugin, and the devstack localrc/local.conf has the default values for: LOG_COLOR (default value = True) SYSLOG (default value = False) then upon startup (i.e. running DevStack's stack.sh), the magnum devstack lib calls the DevStack common setup_colorized_logging function, but without passing the optional 'project_var' and 'user_var' arguments to this function. As a result, the setup_colorized_logging function uses its default values of "user_name" and "project_name" when it defines the logging_context_format_string (which in turn gets configured in /etc/magnum/magnum.conf). The problem is that "user_name" and "project_name" are not defined in the API context used by Magnum, so that whenever the magnum plugin does a logging call, a KeyError exception for the non-existant key "user_name" is generated. Fix description: The fix is to modify the Magnum context to use "user_name" and "project_name" attributes to be consistent with the default context format string set up by DevStack. Change-Id: Ia0c34899609735ff9d8b4597101e004e2684657e Closes-Bug: #1464376 |
||
|---|---|---|
| contrib/templates/example | ||
| devstack | ||
| doc/source | ||
| etc/magnum | ||
| magnum | ||
| specs | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .testr.conf | ||
| CONTRIBUTING.rst | ||
| Dockerfile | ||
| HACKING.rst | ||
| LICENSE | ||
| MANIFEST.in | ||
| README.rst | ||
| babel.cfg | ||
| bandit.yaml | ||
| functional_creds.conf.sample | ||
| openstack-common.conf | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements-bandit.txt | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
Magnum
new Openstack project for containers.
- Free software: Apache license
- Documentation: http://docs.openstack.org/developer/magnum
- Source: http://git.openstack.org/cgit/openstack/magnum
- Bugs: http://bugs.launchpad.net/magnum
- ReST Client: http://git.openstack.org/cgit/openstack/python-magnumclient
Architecture
There are seven different types of objects in the Magnum system:
- Bay: A collection of node objects where work is scheduled
- BayModel: An object stores template information about the bay which is used to create new bays consistently
- Node: A baremetal or virtual machine where work executes
- Pod: A collection of containers running on one physical or virtual machine
- Service: An abstraction which defines a logical set of pods and a policy by which to access them
- ReplicationController: An abstraction for managing a group of PODs to ensure a specified number of PODs are running
- 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-conductor process. The ReST server is horizontally scalable. At this time, the conductor is limited to one process, but we intend to add horizontal scalability to the conductor as well.
The magnum-conductor 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.
Features
- Abstractions for bays, containers, nodes, pods, and services
- Integration with Kubernetes and Docker for backend container technology.
- Integration with Keystone for multi-tenant security.
- Integration with Neutron for k8s multi-tenancy network security.
Installation and Usage
- Getting Started Guides: http://git.openstack.org/cgit/openstack/magnum/tree/doc/source/dev/dev-quickstart.rst