A docker plugin backend for the magnum-backend process
Export the "container" object to the magnum backend.
Blueprint information
- Status:
- Complete
- Approver:
- Steven Dake
- Priority:
- Essential
- Drafter:
- Steven Dake
- Direction:
- Approved
- Assignee:
- Digambar
- Definition:
- Approved
- Series goal:
- Accepted for milestone-1
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Digambar
- Completed by
- Adrian Otto
Related branches
Related bugs
Sprints
Whiteboard
Implement https:/
Lines 72-104 should be implemented. When the ReST API receives a request on a container, it will package it up and send it via magnum/
Will we be using Zaqar or AMQP ?
Because as per the meeting we have decided Zaqar implementation instead AMQP.
Ideally we would use neither but instead communicate with the bay's Docker service via the Docker ReST API that Docker exports to users. There is even a python binding already available. We really don't want dependencies on any agents IMO, so if we can avoid them (which we can) we should.
Gerrit topic: https:/
Addressed by: https:/
Adding docker backend to the magnum.
Addressed by: https:/
Added docker backend to magnum in handler.
Addressed by: https:/
Implemented docker backend in the handler.
Addressed by: https:/
Docker has implemented in the conductor/handlers.
Addressed by: https:/
Docker implementation with import error fixed.
Addressed by: https:/
Grouped Import error has fixed. Implements: blueprint magnum-
Addressed by: https:/
Implemented docker backend for magnum service.
Work Items
Dependency tree
* Blueprints in grey have been implemented.