← Back to branch summary

~evilnick/clouddocs/trunk

« back to all changes in this revision

Viewing changes to Admin/Upgrading-and-Patching-Juju.md

  • Committer: Nick Veitch
  • Date: 2014-04-30 16:46:17 UTC
  • mfrom: (23.1.8 trunk)
  • Revision ID: nick.veitch@canonical.com-20140430164617-0x4xny3b7t1useo8
jens edits to admin

Show diffs side-by-side

added added

removed removed

Lines of Context:
Admin/Upgrading-and-Patching-Juju.md
15
15
 
16
16
The upgrade of a Juju environment is done using the Juju client and its command:
17
17
 
18
 
````
19
 
$ juju upgrade-juju
20
 
````
 
18
```
 
19
juju upgrade-juju
 
20
```
21
21
 
22
22
This command sets the version number for all Juju agents to run. This 
23
 
is the most-recent supported version compatible with the command-line tools version.
 
23
is the most recent supported version compatible with the command-line tools version.
24
24
First, ensure you have upgraded the Juju client.
25
25
 
26
26
When run without arguments, `upgrade-juju` will try to upgrade to the following 
33
33
Both of these depend on availability of the according tools. On MAAS, you've
34
34
got to manage this yourself using the command:
35
35
 
36
 
````
37
 
$ juju sync-tools
38
 
````
 
36
```
 
37
juju sync-tools
 
38
```
39
39
 
40
40
This copies the Juju tools tarball from the official tools store (located
41
41
at https://streams.canonical.com/juju) into your environment.