Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(217)

Unified Diff: cmd/juju/deploy.go

Issue 94410043: Use lxc clone by default (Closed)
Patch Set: Use lxc clone by default Created 9 years, 10 months ago
Use n/p to move between diff chunks; N/P to move between comments. Please Sign in to add in-line comments.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: cmd/juju/deploy.go
=== modified file 'cmd/juju/deploy.go'
--- cmd/juju/deploy.go 2014-05-12 05:23:59 +0000
+++ cmd/juju/deploy.go 2014-05-13 08:08:46 +0000
@@ -66,6 +66,31 @@
by set-constraints).
Charms can be deployed to a specific machine using the --to argument.
+If the destination is an LXC container, as of trusty, the default is
+to use lxc-clone to create the container. A 'template' container is
+created with the name
+ juju-<series>-template
+where <series> is the OS series, for example 'juju-trusty-template'.
+
+You can override the use of clone by changing the provider configuration:
+ lxc-clone: false
+
+If you have the main container directory mounted on a btrfs partition,
+then the clone will be using btrfs snapshots to create the containers.
+This means that the clones use up much less disk space. If you do not have btrfs,
+lxc will attempt to use aufs (which is an overlay type filesystem). You can
+explicitly ask Juju to create full containers and not overlays by specifying
+the following in the provider configuration:
+ lxc-clone-aufs: false
+
+Examples:
+ juju deploy mysql --to 23 (Deploy to machine 23)
+ juju deploy mysql --to 24/lxc/3 (Deploy to lxc container 3 on host machine 24)
+ juju deploy mysql --to lxc:25 (Deploy to a new lxc container on host machine 25)
+
+ juju deploy mysql -n 5 --constraints mem=8G (deploy 5 instances of mysql with at least 8 GB of RAM each)
+
+ juju deploy mysql --networks=storage,mynet --exclude-networks=logging
Like constraints, service-specific network requirements can be
specified with --networks and --exclude-networks arguments, both can
@@ -75,15 +100,6 @@
and to ensure none of the networks in --exclude-networks are added to
the service's machines. Not supported on all providers.
-Examples:
- juju deploy mysql --to 23 (Deploy to machine 23)
- juju deploy mysql --to 24/lxc/3 (Deploy to lxc container 3 on host machine 24)
- juju deploy mysql --to lxc:25 (Deploy to a new lxc container on host machine 25)
-
- juju deploy mysql -n 5 --constraints mem=8G (deploy 5 instances of mysql with at least 8 GB of RAM each)
-
- juju deploy mysql --networks=storage,mynet --exclude-networks=logging
-
See Also:
juju help constraints
juju help set-constraints
« no previous file with comments | « [revision details] ('k') | cmd/juju/help_topics.go » ('j') | container/lxc/lxc.go » ('J')

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b