Added Trusty so we can track SRU when filed
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Also affects: juju-core (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu)
Importance: Undecided => High
** Changed in: juju-core (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: juju-core (Ubuntu)
Status: New => Confirmed
** Changed in: juju-core (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: juju-core (Ubuntu Trusty)
Milestone: None => ubuntu-14.04.1
** Description changed:
- When deploying services within an LXC nested in a KVM machine the lxc-
- clone support is not used.
+ [Impact]
+ Users wishing to use nested lxc containers will benefit from the additional
speed that cloning provides.
+
+ [Test Case]
+ When deploying services within an LXC nested in a KVM machine the lxc-clone
support is not used.
status output:
environment: local
machines:
- "0":
- agent-state: started
- agent-version: 1.18.1.1
- dns-name: localhost
- instance-id: localhost
- series: trusty
- "1":
- agent-state: started
- agent-version: 1.18.1.1
- dns-name: 10.0.3.129
- instance-id: poe-local-machine-1
- series: trusty
- containers:
- 1/lxc/0:
- instance-id: pending
- series: precise
- hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M
+ "0":
+ agent-state: started
+ agent-version: 1.18.1.1
+ dns-name: localhost
+ instance-id: localhost
+ series: trusty
+ "1":
+ agent-state: started
+ agent-version: 1.18.1.1
+ dns-name: 10.0.3.129
+ instance-id: poe-local-machine-1
+ series: trusty
+ containers:
+ 1/lxc/0:
+ instance-id: pending
+ series: precise
+ hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M
services:
- wordpress:
- charm: cs:precise/wordpress-21
- exposed: false
- relations:
- loadbalancer:
- - wordpress
- units:
- wordpress/0:
- agent-state: pending
- machine: 1/lxc/0
+ wordpress:
+ charm: cs:precise/wordpress-21
+ exposed: false
+ relations:
+ loadbalancer:
+ - wordpress
+ units:
+ wordpress/0:
+ agent-state: pending
+ machine: 1/lxc/0
lxc-ls output from the kvm machine
ubuntu@ubuntu:~$ sudo lxc-ls --fancy
- NAME STATE IPV4 I PV6
AUTOSTART
+ NAME STATE IPV4 I PV6
AUTOSTART
---------------------------------------------------------------------
juju-machine-1-lxc-0 RUNNING 10.0.3.105 - NO
No juju-trusty-template is ever defined for re-use.
+ [Regression Potentional]
+ This only applies to new bootstrapped environments with lxc-use-clone
applied. Existing environments will continue unaffected.
+
+
Thanks
Adam
** Description changed:
[Impact]
- Users wishing to use nested lxc containers will benefit from the additional
speed that cloning provides.
+ When deploying services within an LXC nested in a KVM machine the lxc-clone
support is not used.
[Test Case]
- When deploying services within an LXC nested in a KVM machine the lxc-clone
support is not used.
status output:
environment: local
machines:
"0":
agent-state: started
agent-version: 1.18.1.1
dns-name: localhost
instance-id: localhost
series: trusty
"1":
agent-state: started
agent-version: 1.18.1.1
dns-name: 10.0.3.129
instance-id: poe-local-machine-1
series: trusty
containers:
1/lxc/0:
instance-id: pending
series: precise
hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M
services:
wordpress:
charm: cs:precise/wordpress-21
exposed: false
relations:
loadbalancer:
- wordpress
units:
wordpress/0:
agent-state: pending
machine: 1/lxc/0
lxc-ls output from the kvm machine
ubuntu@ubuntu:~$ sudo lxc-ls --fancy
NAME STATE IPV4 I PV6
AUTOSTART
---------------------------------------------------------------------
juju-machine-1-lxc-0 RUNNING 10.0.3.105 - NO
No juju-trusty-template is ever defined for re-use.
[Regression Potentional]
This only applies to new bootstrapped environments with lxc-use-clone
applied. Existing environments will continue unaffected.
-
Thanks
Adam
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315216
Title:
lxc nested within kvm machines do not use lxc-clone
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1315216/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
