Driver.plug_vifs is sometimes called when the container is not
running, such as called by _init_instance in ComputeManager.
In this patch, plug_vifs is only responsible for creating bridges
and preparing the peer devices, which does not require the container
running, attach_vifs is responsible for preparing the netns and
attaching the peer device to container.
When starting a container, attach_vifs is called after plug_vifs.
Reviewed: https:/ /review. openstack. org/106684 /git.openstack. org/cgit/ stackforge/ nova-docker/ commit/ ?id=000f5f2a02e 4b32f6bcbfab6a7 2cc67ab4ab821d
Committed: https:/
Submitter: Jenkins
Branch: master
commit 000f5f2a02e4b32 f6bcbfab6a72cc6 7ab4ab821d
Author: gupeng <gp_stack@163.com>
Date: Mon Jul 14 12:10:26 2014 +0800
Split plug_vifs into plug_vifs and attach_vifs
Driver. plug_vifs is sometimes called when the container is not
running, such as called by _init_instance in ComputeManager.
In this patch, plug_vifs is only responsible for creating bridges
and preparing the peer devices, which does not require the container
running, attach_vifs is responsible for preparing the netns and
attaching the peer device to container.
When starting a container, attach_vifs is called after plug_vifs.
Change-Id: Icc5e2cebde22c1 0a318379d41bb4c 50085b07162
Closes-bug: #1341423