manage/unmanage the container created by docker
The purpose of this bp is to enable zun to have the ability to manage containers created by docker
details:
If user create container A using the 'docker create --name A ubuntu' command, we cannot see this container on the zun side, nor can we use the zun command to operate this container.
We can implement this function so that zun can see the container created by docker and manage it
application scenarios：
In a newly deployed openstack environment, there are some docker containers created before deployment. Users want to use zun to manage these containers.
Whiteboard
(hongbin 2018-03-21) Hi @Ji.Wei, could you add more details about this requested feature? What are the use cases? How this feature will be implemented? Are there any alternative approach? Why it is critical to implement this feature? etc.
(hongbin 2018-03-29) Note: We needs to pay attention for two things: (i) Zun is using Kuryr-libnetwork as Docker network driver, however, the unmanaged containers might not use Kuryr. Whenever a unmanaged container becomes managed, we need to do a bunch of validations on the network configuration of the container and rejects it if the network configuration doesn't match. (ii) Zun's container is isolated by tenants, so we need to make sure the unmanaged container doesn't attach to resources (i.e. volume, network) from other tenants.
