I've noticed something odd and believe it's a result of this commit. I'm not sure it's a bug, but I preferred the previous behaviour. Currently, a container's rootfs is in /var/lib/lxc/<container>. For example:
root@jenk-heat-350-node1:/var/lib/lxc# ls -al jenk-heat-350-node1_cinder_api_container-32e9101e
total 104
drwxr-xr-x 22 root root 4096 Jun 29 14:57 .
drwx------ 27 root root 4096 Jun 29 14:17 ..
drwxr-xr-x 2 root root 4096 Jun 29 14:22 bin
drwxr-xr-x 2 root root 4096 Apr 10 2014 boot
-rw-r--r-- 1 root root 1370 Jun 29 14:57 config
-rw-r--r-- 1 root root 1219 Jun 29 14:18 config.2015-06-29@14:18:45~
drwxr-xr-x 5 root root 4096 Jun 29 15:00 dev
drwxr-xr-x 77 root root 4096 Jun 29 15:00 etc
-rw-r--r-- 1 root root 512 Jun 29 14:18 eth1.ini
-rw-r--r-- 1 root root 515 Jun 29 14:18 eth2.ini
-rw-r--r-- 1 root root 0 Jun 29 14:17 fstab
drwxr-xr-x 3 root root 4096 Jun 29 14:17 home
drwxr-xr-x 14 root root 4096 Jun 29 14:58 lib
drwxr-xr-x 2 root root 4096 May 31 20:07 lib64
drwxr-xr-x 2 root root 4096 Jul 29 2014 media
drwxr-xr-x 2 root root 4096 Apr 10 2014 mnt
drwxr-xr-x 2 root root 4096 Jun 29 14:57 opt
drwxr-xr-x 2 root root 4096 Apr 10 2014 proc
drwx--S--- 6 root root 4096 Jun 29 14:58 root
drwxr-xr-x 2 root root 4096 Jun 29 14:16 rootfs
drwxr-xr-x 9 root root 4096 Jun 29 14:17 run
drwxr-xr-x 2 root root 4096 Jun 29 14:58 sbin
drwxr-xr-x 2 root root 4096 Jul 29 2014 srv
drwxr-xr-x 2 root root 4096 Mar 13 2014 sys
drwxrwxrwt 2 root root 4096 Jun 30 09:17 tmp
drwxr-xr-x 10 root root 4096 Jul 29 2014 usr
drwxr-xr-x 12 root root 4096 Jun 15 12:38 var
root@jenk-heat-350-node1:/var/lib/lxc#
Previously, the rootfs would have been in /var/lib/lxc/<container>/rootfs.
This new behaviour is quite messy as it's going to become difficult to determine what files are LXC configuration versus files within the rootfs.
Assuming this is a bug, I'll go ahead and create a new bug for it.
I've noticed something odd and believe it's a result of this commit. I'm not sure it's a bug, but I preferred the previous behaviour. Currently, a container's rootfs is in /var/lib/ lxc/<container> . For example:
root@jenk- heat-350- node1:/ var/lib/ lxc# ls -al jenk-heat- 350-node1_ cinder_ api_container- 32e9101e 2015-06- 29@14:18: 45~ heat-350- node1:/ var/lib/ lxc#
total 104
drwxr-xr-x 22 root root 4096 Jun 29 14:57 .
drwx------ 27 root root 4096 Jun 29 14:17 ..
drwxr-xr-x 2 root root 4096 Jun 29 14:22 bin
drwxr-xr-x 2 root root 4096 Apr 10 2014 boot
-rw-r--r-- 1 root root 1370 Jun 29 14:57 config
-rw-r--r-- 1 root root 1219 Jun 29 14:18 config.
drwxr-xr-x 5 root root 4096 Jun 29 15:00 dev
drwxr-xr-x 77 root root 4096 Jun 29 15:00 etc
-rw-r--r-- 1 root root 512 Jun 29 14:18 eth1.ini
-rw-r--r-- 1 root root 515 Jun 29 14:18 eth2.ini
-rw-r--r-- 1 root root 0 Jun 29 14:17 fstab
drwxr-xr-x 3 root root 4096 Jun 29 14:17 home
drwxr-xr-x 14 root root 4096 Jun 29 14:58 lib
drwxr-xr-x 2 root root 4096 May 31 20:07 lib64
drwxr-xr-x 2 root root 4096 Jul 29 2014 media
drwxr-xr-x 2 root root 4096 Apr 10 2014 mnt
drwxr-xr-x 2 root root 4096 Jun 29 14:57 opt
drwxr-xr-x 2 root root 4096 Apr 10 2014 proc
drwx--S--- 6 root root 4096 Jun 29 14:58 root
drwxr-xr-x 2 root root 4096 Jun 29 14:16 rootfs
drwxr-xr-x 9 root root 4096 Jun 29 14:17 run
drwxr-xr-x 2 root root 4096 Jun 29 14:58 sbin
drwxr-xr-x 2 root root 4096 Jul 29 2014 srv
drwxr-xr-x 2 root root 4096 Mar 13 2014 sys
drwxrwxrwt 2 root root 4096 Jun 30 09:17 tmp
drwxr-xr-x 10 root root 4096 Jul 29 2014 usr
drwxr-xr-x 12 root root 4096 Jun 15 12:38 var
root@jenk-
Previously, the rootfs would have been in /var/lib/ lxc/<container> /rootfs.
This new behaviour is quite messy as it's going to become difficult to determine what files are LXC configuration versus files within the rootfs.
Assuming this is a bug, I'll go ahead and create a new bug for it.
Comments? Thoughts?