LXC cloning should be default behaviour

Bug #1318485 reported by Ian Booth on 2014-05-12
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
High
Ian Booth

Bug Description

We support LXC image cloning to make deploying to LXC containers faster. This was originally done as a local provider option via the use-clone setting but now there's also a global lxc-use-clone setting used for all providers.

As a minimum, we need to consolidate the settings.
Where supported, the use of cloning should be on by default. What does "supported" mean? It seems this may not work on PPC. So we could detect arch and warn the user that it is not supported if they have asked for it.

Tags: lxc Edit Tag help

Related branches

Andrew Wilkins (axwalk) wrote :

Also, I forgot that there was an lxc-clone config attribute for the local provider. We should probably change the global attribute to lxc-clone, rather than lxc-use-clone.

Ian Booth (wallyworld) on 2014-05-13
Changed in juju-core:
assignee: nobody → Ian Booth (wallyworld)
status: Triaged → In Progress
Go Bot (go-bot) on 2014-05-15
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui) on 2014-05-30
Changed in juju-core:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers