Pull Docker Connection Details from Docker Bay

Registered by Andrew Melton

Docker conductor should use connection details from one of the user's Docker based bays to build it's client instead of getting connection details from magnum's config file.

The current Docker conductor uses the config value 'host_url' as the connection string for it's Docker client. The ultimate goal of this blueprint is to associate each container with a bay, so that the Docker
conductor can instead use the api_address from the container's bay as the connection string. This way, instead of having people manually change config values, they will just spawn containers in bays.

Blueprint information

Status:
Complete
Approver:
Adrian Otto
Priority:
High
Drafter:
Andrew Melton
Direction:
Needs approval
Assignee:
Andrew Melton
Definition:
New
Series goal:
Accepted for kilo
Implementation:
Implemented
Milestone target:
milestone icon k3
Started by
Andrew Melton
Completed by
Andrew Melton

Related branches

Sprints

Whiteboard

Size Estimate: M

Gerrit topic: https://review.openstack.org/#q,topic:bp/docker-conductor-connect-to-docker-bay,n,z

Addressed by: https://review.openstack.org/175339
    Add bay_uuid attribute to Container model

Addressed by: https://review.openstack.org/176470
    Use container's bay for docker endpoint

Addressed by: https://review.openstack.org/176425
    Use proper rpcapi in Containers API

Gerrit topic: https://review.openstack.org/#q,topic:bug/1405356,n,z

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.