It is using nested containers, yes. There's a top level container,
inside which we install juju with the above env.yaml, and deploy from in there.
So the containers which juju creates are nested one level deep.
Note that the machines created by juju in earlier logs had 10.0.6.x,
but the latest one has 10.0.7.x.
We explicitly set lxcbr0 to 10.0.N.x where N is 6 or
greater, to avoid clashing with other installs when we add a static
route to the container network from the host. We manually set the lxc-net
config in the container. In this case it's the following:
ubuntu@openstack-single-ubuntu:~$ cat /etc/default/lxc-net
# Custom lxc-net for Single Installer
USE_LXC_BRIDGE="true"
LXC_BRIDGE="lxcbr0"
LXC_ADDR=10.0.7.1
LXC_NETMASK=255.255.255.0
LXC_NETWORK=10.0.7.0/24
LXC_DHCP_RANGE="10.0.7.2,10.0.7.254"
LXC_DHCP_MAX="196"
#LXC_DHCP_CONFILE=/etc/lxc/dnsmasq.conf
#LXC_DOMAIN="lxc"
Here's some further network info. 'ancient-spot' is the top level
host. The top level container is called 'openstack-single-ubuntu'.
ubuntu@ancient-spot:~⟫ sudo ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever
inet6 ::1/128 scope host valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether ec:a8:6b:fb:3a:5e brd ff:ff:ff:ff:ff:ff
inet 172.16.0.66/24 brd 172.16.0.255 scope global eth0 valid_lft forever preferred_lft forever
inet6 fe80::eea8:6bff:fefb:3a5e/64 scope link valid_lft forever preferred_lft forever
3: lxcbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether fe:bb:ba:5e:ec:13 brd ff:ff:ff:ff:ff:ff
inet 10.0.3.1/24 scope global lxcbr0 valid_lft forever preferred_lft forever
inet6 fe80::f897:dff:fe56:8118/64 scope link valid_lft forever preferred_lft forever
6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 52:54:00:cf:09:a4 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever
7: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 500
link/ether 52:54:00:cf:09:a4 brd ff:ff:ff:ff:ff:ff
17: vethPE50B4@if16: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master lxcbr0 state UP group default qlen 1000
link/ether fe:bb:ba:5e:ec:13 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::fcbb:baff:fe5e:ec13/64 scope link valid_lft forever preferred_lft forever
ubuntu@ancient-spot:~⟫ sudo ip route show
default via 172.16.0.1 dev eth0
10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1
10.0.6.0/24 via 10.0.3.201 dev lxcbr0
10.0.7.0/24 via 10.0.3.45 dev lxcbr0
172.16.0.0/24 dev eth0 proto kernel scope link src 172.16.0.66
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
ubuntu@ancient-spot:~⟫ sudo lxc-ls -f
NAME STATE IPV4 IPV6 GROUPS AUTOSTART
---------------------------------------------------------------------------------------------
openstack-single-ubuntu RUNNING 10.0.3.45, 10.0.7.1, 192.168.122.1 - - YES
attached machine-0.log as a gzipped file, it was 40MB.
as to your other questions:
This is using the local provider. Here's the environments.yaml:
default: local
environments:
authorized- keys-path: ~/.ssh/id_rsa.pub
network- bridge: lxcbr0
default- series: trusty
admin- secret: "ubuntu"
local:
type: local
container: kvm
lxc-clone: true
no-proxy: localhost
It is using nested containers, yes. There's a top level container,
inside which we install juju with the above env.yaml, and deploy from in there.
So the containers which juju creates are nested one level deep.
Note that the machines created by juju in earlier logs had 10.0.6.x,
but the latest one has 10.0.7.x.
We explicitly set lxcbr0 to 10.0.N.x where N is 6 or
greater, to avoid clashing with other installs when we add a static
route to the container network from the host. We manually set the lxc-net
config in the container. In this case it's the following:
ubuntu@ openstack- single- ubuntu: ~$ cat /etc/default/ lxc-net LXC_BRIDGE= "true" BRIDGE= "lxcbr0" ADDR=10. 0.7.1 NETMASK= 255.255. 255.0 NETWORK= 10.0.7. 0/24 DHCP_RANGE= "10.0.7. 2,10.0. 7.254" DHCP_MAX= "196" DHCP_CONFILE= /etc/lxc/ dnsmasq. conf DOMAIN= "lxc"
# Custom lxc-net for Single Installer
USE_
LXC_
LXC_
LXC_
LXC_
LXC_
LXC_
#LXC_
#LXC_
Here's some further network info. 'ancient-spot' is the top level single- ubuntu' .
host. The top level container is called 'openstack-
ubuntu@ ancient- spot:~⟫ sudo ip addr show UP,LOWER_ UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
valid_ lft forever preferred_lft forever
valid_ lft forever preferred_lft forever MULTICAST, UP,LOWER_ UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
valid_ lft forever preferred_lft forever 6bff:fefb: 3a5e/64 scope link
valid_ lft forever preferred_lft forever MULTICAST, UP,LOWER_ UP> mtu 1500 qdisc noqueue state UP group default
valid_ lft forever preferred_lft forever dff:fe56: 8118/64 scope link
valid_ lft forever preferred_lft forever BROADCAST, MULTICAST, UP> mtu 1500 qdisc noqueue state DOWN group default
valid_ lft forever preferred_lft forever MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 500 MULTICAST, UP,LOWER_ UP> mtu 1500 qdisc pfifo_fast master lxcbr0 state UP group default qlen 1000 baff:fe5e: ec13/64 scope link
valid_ lft forever preferred_lft forever
1: lo: <LOOPBACK,
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
2: eth0: <BROADCAST,
link/ether ec:a8:6b:fb:3a:5e brd ff:ff:ff:ff:ff:ff
inet 172.16.0.66/24 brd 172.16.0.255 scope global eth0
inet6 fe80::eea8:
3: lxcbr0: <BROADCAST,
link/ether fe:bb:ba:5e:ec:13 brd ff:ff:ff:ff:ff:ff
inet 10.0.3.1/24 scope global lxcbr0
inet6 fe80::f897:
6: virbr0: <NO-CARRIER,
link/ether 52:54:00:cf:09:a4 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
7: virbr0-nic: <BROADCAST,
link/ether 52:54:00:cf:09:a4 brd ff:ff:ff:ff:ff:ff
17: vethPE50B4@if16: <BROADCAST,
link/ether fe:bb:ba:5e:ec:13 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::fcbb:
ubuntu@ ancient- spot:~⟫ sudo ip route show 168.122. 0/24 dev virbr0 proto kernel scope link src 192.168.122.1
default via 172.16.0.1 dev eth0
10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1
10.0.6.0/24 via 10.0.3.201 dev lxcbr0
10.0.7.0/24 via 10.0.3.45 dev lxcbr0
172.16.0.0/24 dev eth0 proto kernel scope link src 172.16.0.66
192.
ubuntu@ ancient- spot:~⟫ sudo lxc-ls -f ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------ single- ubuntu RUNNING 10.0.3.45, 10.0.7.1, 192.168.122.1 - - YES
NAME STATE IPV4 IPV6 GROUPS AUTOSTART
---
openstack-
I don't know if it's just wily.