Add magnum native docker compute support

Registered by Guangya Liu (Jay Lau)

1) The magnum native docker compute should be able to collect docker host metrics for scheduling.
2) The docker conductor logic which interact with docker host should also be moved to magnum native docker compute

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Guangya Liu (Jay Lau)
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
Accepted for trunk
Implementation:
Unknown
Milestone target:
None
Completed by
Adrian Otto

Related branches

Sprints

Whiteboard

Jay, after further consideration, do you think that the docker-swarm bay type may be a better fit for this? We could use the same scheduler hooks that swarm uses for integration with Mesos to integrate with Gantt when it takes form. If this sounds better to you, maybe we should withdraw this blueprint, and focus our efforts on the magnum-swarm-scheduling blueprint. Please let me know your thoughts.

Adrian, I was also thinking if we can re-use docker-swarm bay to manage native docker cluster in magnum. The problem is that in swarm, there is also a scheduler, after we deploy docker-swarm bay, it is a pure swarm cluster, and swarm scheduler can help do scheduling for such a cluster. Do you mean that we only use swarm collect metrics for scheduler but add a new magnum-swarm-scheduler to help scheduling? Another I want to ask is, seems the current docker-swarm template can only provision a swarm cluster but magnum do not have interface/api to interact with swarm cluster, right? --jay-lau-513 2015-04-14

2015-06-16 adrian_otto: We have this capability on our Swarm bay type.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.