Merge lp:~marcoceppi/pyjuju/local-provider-fixes into lp:~charm-contributors/pyjuju/docs

[Marco Ceppi]

[Kapil Thangavelu (hazmat)]

There's some discussion/review of this change on the mailing list.

[Marco Ceppi (marcoceppi)]

Rejecting until I can implement changes discussed in IRC and mailing list

[Kapil Thangavelu (hazmat)]

Hi Marco,

fwiw, typical thing to do here is just set the merge proposal to "Work in
progress" while the changes are being made.

On Wed, May 23, 2012 at 10:09 AM, Marco Ceppi <email address hidden> wrote:

> Rejecting until I can implement changes discussed in IRC and mailing list
> --
>
> https://code.launchpad.net/~marcoceppi/juju/local-provider-fixes/+merge/105406
> Your team juju Charm Contributors is requested to review the proposed
> merge of lp:~marcoceppi/juju/local-provider-fixes into lp:juju/docs.
>

[Marco Ceppi (marcoceppi)]

Thanks, was trying to get it to drop out of the review-queue. Wasn't sure if WIP would do that.

review: Needs Fixing

Unmerged revisions

22. By Marco Ceppi on 2012-05-10

Updated local provider configuration

=== modified file 'source/getting-started.rst'
--- source/getting-started.rst	2012-05-04 17:17:34 +0000
+++ source/getting-started.rst	2012-05-10 22:12:19 +0000
@@ -21,14 +21,14 @@
 
 For the moment, though, the only environment supported is EC2, OpenStack, and LXC containers. 
 
-Running from PPA (11.10 only)
+Running from PPA (required for 11.10)
 -----------------------------
 
 The juju team's Personal Package Archive (PPA) installation is
 currently the preferred installation mechanism for juju for 11.10 users. It
 includes newer upstream versions of binary dependencies like Zookeeper
 which are more recent than the latest ubuntu release (11.10) and
-contain important bugfixes. For users in 12.04 we recommend using the package in the archive
+contain important bugfixes. For users in 12.04 juju is available in the archive
 
 To install juju from the PPA, execute the following in a shell::
 
@@ -82,17 +82,27 @@
 Configuring a local environment
 -------------------------------
 
-First install some dependencies it needs.
+First install juju and it's dependancies::
 
   sudo apt-get install libvirt-bin lxc apt-cacher-ng libzookeeper-java zookeeper juju
 
-After installing it, you may have to reboot (I had to else libvirt couldn't create the network bridge indicating it was already in use). After that you might get error for ``SSH authorized/public key not found. ERROR SSH authorized/public key not found.``
-
-  ssh-keygen -t rsa
-
-First configure your environment local environment:
-
-In ``~/.juju/environments.yaml``, add a section for type "local"::
+Check if you've been added to the ``libvirtd`` group::
+
+  groups
+
+This will produce a list of groups your user is part of, if ``libvirtd`` is not in 
+that list perform the following::
+
+  sudo usermod -a -G libvirtd `whoami`
+
+This change won't affect your current session. You can either log out then back in or 
+issue the following command to log in under the new group::
+
+  newgrp libvirtd
+
+However, this will only apply to that terminal session. Isuse a ``juju 
+bootstrap`` to create the necessary skeleton files. In ``~/.juju/environments.yaml``, 
+add a section for type "local"::
 
     environments:
       sample:
@@ -103,11 +113,22 @@
         juju-origin: distro
         data-dir: /home/jorge/whatever
 
-The ``data-dir`` is going to be where the containers and stuff will keep their data. As far as I can tell `control-bucket` and `admin-secret` can be whatever you want. If you are going to use juju from the PPA (11.10 users) then change ``juju-origin`` to ``ppa``. After this you can then:
+The ``data-dir`` is going to be where the containers and stuff will keep 
+their data. As far as I can tell `control-bucket` and `admin-secret` can 
+be whatever you want. If you are going to use juju from the PPA then change 
+``juju-origin`` to ``ppa``. After this you can then::
 
   juju bootstrap
 
-The first time this runs it might take a bit, as it's doing a netinstall for the container. Subsequent bootstraps should be much quicker. You can then locally deploy charms, make note of the "local:" in front of each service:
+If during bootstrap you get the following error ``SSH authorized/public key 
+not found. ERROR SSH authorized/public key not found.`` you will need to 
+create an SSH Keypair, do so by issuing the following command::
+
+  ssh-keygen -t rsa
+
+The first time this runs it might take a bit, as it's doing a netinstall 
+for the container. Subsequent bootstraps should be much quicker. You can 
+then locally deploy charms, make note of the "local:" in front of each service::
 
   juju deploy mysql
   juju deploy wordpress
@@ -115,37 +136,41 @@
 
 When it's deployed juju should return something like this in status::
 
-    machines:
-      0: {dns-name: localhost, instance-id: local}
-    services:
-      mysql:
-        charm: local:oneiric/mysql-11
-        relations: {db: wordpress}
-        units:
-          mysql/0:
-            machine: 0
-            public-address: 192.168.122.137
-            relations:
-              db: {state: up}
-            state: started
-      wordpress:
-        charm: local:oneiric/wordpress-31
-        relations: {db: mysql}
-        units:
-          wordpress/0:
-            machine: 0
-            public-address: 192.168.122.166
-            relations:
-              db: {state: up}
-            state: started
-    2011-10-11 18:44:32,268 INFO 'status' command finished successfully
+  machines:
+    0:
+  	agent-state: running
+  	dns-name: localhost
+  	instance-id: local
+  	instance-state: running
+  services:
+    mysql:
+  	charm: cs:precise/mysql-1
+  	relations:
+  	  db:
+  	  - wordpress
+  	units:
+  	  mysql/0:
+  		agent-state: started
+  		machine: 0
+  		public-address: 192.168.122.47
+    wordpress:
+  	charm: cs:precise/wordpress-0
+  	relations:
+  	  db:
+  	  - mysql
+  	units:
+  	  wordpress/0:
+  		agent-state: started
+  		machine: 0
+  		public-address: 192.168.122.193
 
-Expose your service with:
+Expose your service with::
 
   juju expose wordpress
 
-In this example, navigating the browser to 192.168.122.166 should take you to the wordpress configuration page. 
+In this example, navigating the browser to 192.168.122.166 should take you 
+to the wordpress configuration page. 
 
-Enabling logging option.
+Enabling logging option::
 
   juju debug-log