lp:~kim0/pyjuju/fix-faq-formula-licensing-806037
- Get this branch:
- bzr branch lp:~kim0/pyjuju/fix-faq-formula-licensing-806037
Branch merges
Branch information
Recent revisions
- 376. By Gustavo Niemeyer
-
Merge fix-failing-
local-tests branch by Clint [r=niemeyer] [trivial] This fixes tests so that they don't depend on installed user ssh keys.
- 375. By Kapil Thangavelu
-
merge lxc-provider-
rename- local [r=niemeyer] [f=860982] Rename lxc provider to local provider.
- 374. By Kapil Thangavelu
-
merge unit-with-addresses [r=niemeyer]
[f=859308] Command line tools use unit addresses (status, ssh, debug-hooks, etc).
- 373. By Kapil Thangavelu
-
merge unit-with-addresses [r=niemeyer]
[f=859308] Units detect and record their public/private addresses into the unit state,
in a provider specific manner. - 372. By Gustavo Niemeyer
-
Revert example changes introduced with lxc-omega so that they
work again on EC2. - 371. By Benjamin Saller
-
[TRIVAL] Merge style changes related to lxc-omega merge and patch around master_template rename
- 370. By Gustavo Niemeyer
-
Rename readme.txt to README since we already have one of those. [trivial]
But really, this is just bumping the revno for an ftest cycle. :-)
- 369. By Benjamin Saller
-
Merge lxc-omega enabling local dev [f=859180] [r=niemeyer,hazmat]
To experiment with local dev you should
Merge the following to your ~/.juju/
environments. yaml juju: environments
default: laptoplaptop
type: lxc
dmin-secret: whoknows
data-dir: /tmpI recommend adding dmsmasq to your /etc/resolv.conf with:
nameserver 192.168.122.1
as the first nameserver
However a subsequent branch makes status and ssh find the proper VM for you.
Machines are named via a pattern <username>-<env name>-<
servicename> -<unitid> So for me a wordpress deployment from the local repo would result in a machine at
bcsaller-laptop- wordpress- 0
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:pyjuju