commit 19970092e3801f8aa354cc41b3fe1cf3e3486203
Author: Major Hayden <email address hidden>
Date: Mon Aug 31 20:17:32 2015 -0500
Used named veth pairs that match container
The default veth names from LXC make it difficult to tell which veth
corresponds to each container. This patch sets a unique veth name
that matches the container as well as the network device inside the
container. It should make troubleshooting a little easier.
Oddly enough, this patch seems to fix or greatly reduce the occurence
of the issues seen in ticket 1491440.
Reviewed: https:/ /review. openstack. org/222295 /git.openstack. org/cgit/ stackforge/ os-ansible- deployment/ commit/ ?id=19970092e38 01f8aa354cc41b3 fe1cf3e3486203
Committed: https:/
Submitter: Jenkins
Branch: kilo
commit 19970092e3801f8 aa354cc41b3fe1c f3e3486203
Author: Major Hayden <email address hidden>
Date: Mon Aug 31 20:17:32 2015 -0500
Used named veth pairs that match container
The default veth names from LXC make it difficult to tell which veth
corresponds to each container. This patch sets a unique veth name
that matches the container as well as the network device inside the
container. It should make troubleshooting a little easier.
Oddly enough, this patch seems to fix or greatly reduce the occurence
of the issues seen in ticket 1491440.
Partial-Bug: 1491440 91e11d55d56c3f0 f46af9e52be 6610c34220519b6 28e8f8c45c)
Implements: blueprint named-veths
Change-Id: I28553fd1b4f369
(cherry picked from commit 5e6dea8ab6f408e