Re: [openstack-dev] [magnum] Nesting /containers resource under /bays

t; Subject: Re: [openstack-dev] [magnum] Nesting /containers resource under /bays A reason is the container abstraction brings containers to OpenStack: Keystone for authentication, Heat for orchestration, Horizon for UI, etc. From: Kyle Kelley [mailto:rgb...@gmail.com] Sent: January-15-16

Re: [openstack-dev] [magnum] Nesting /containers resource under /bays

uuid, > record its “docker_id” that is the ID assigned by native tool. > > 3. Call Docker Swarm API with “docker_id” to perform the operation. > > > > Magnum doesn’t assume all operations to be routed through Magnum > endpoints. Alternatively, users can directly call

Re: [openstack-dev] [magnum] Nesting /containers resource under /bays

When using the native Docker tooling, the Docker daemon controls the UUID of the container, not Magnum. -- Kyle From: Ryan Brown Sent: Wednesday, January 13, 2016 3:16 PM To: openstack-dev@lists.openstack.org Subject: Re:

Re: [openstack-dev] [magnum] Nesting /containers resource under /bays

This presumes a model where Magnum is in complete control of the IDs of individual containers. How does this work with the Docker daemon? > In Rest API, you can set the “uuid” field in the json request body (this is > not supported in CLI, but it is an easy add).​ In the Rest API for Magnum