Juju: Difference between revisions

Line 7:

== Links ==

# https://jujucharms.com/get-started

# https://jujucharms.com/docs/1.20/config-manual

# https://jujucharms.com/docs/1.20/config-aws

Line 16:

Line 15:

sudo add-apt-repository ppa:juju/stable

sudo apt-get update

sudo apt-get install juju-quickstart

sudo apt-get install juju-core

Line 21:

Line 22:

# juju generate-config --show

juju generate-config

# edit to add your AWS KEYS

# edit .juju/environments.yaml to add your AWS KEYS

juju bootstrap

juju status

Line 58:

Line 59:

<code>ssh -i /home/user/.ssh/id_rsa -o IdentitiesOnly=true -vvv ubuntu@ec2-55-5-555-55.compute-1.amazonaws.com</code>

https://jujucharms.com/mediawiki/trusty/3

The above 'recipe' installs [https://jujucharms.com/mediawiki/trusty/3 this MediaWiki charm] which has been deployed 813 times as of this writing. BFD. It didn't work for me (I had to add [https://jujucharms.com/apache2/trusty/13/ Apache]). Although this charm invokes a2enconf, I don't see any code which installs or verifies Apache2 as a dependency in the [http://bazaar.launchpad.net/~charmers/charms/trusty/mediawiki/trunk/view/head:/hooks/install install hook]. So, yeah, garbage. They should read the docs about [https://jujucharms.com/docs/1.20/authors-charm-writing how to write a charm]. The example explicitly installs, configures and starts Apache as part of a simple web service. But the documentation is very sparse. The only "interface" (a primary element of orchestration) that is documented is 'mysql' and even that is barely covered.

[https://jujucharms.com/wordpress/trusty/2 The Wordpress charm] is [http://bazaar.launchpad.net/~charmers/charms/trusty/wordpress/trunk/files written better] because it works, and actually offers a simple switch between nginx and Apache. Although it's a bit more 'polished' the WordPress Charm is still [http://bazaar.launchpad.net/~charmers/charms/trusty/wordpress/trunk/view/head:/inc/common a bunch of bash scripts] that end up installing things all over the place (standard locations?). It installs [http://php-fpm.org/ php-fpm] (FastCGI Process Manager, which is an alternative PHP FastCGI implementation) It does use git, but is it configurable as to who/what/where you can pull from? I figured out that for the Wordpress charm, you can see the 'components' in the [http://bazaar.launchpad.net/~charmers/charms/trusty/wordpress/trunk/files/head:/files/charm/ 'charm' directory].

In general, I'm '''very''' unimpressed with the implementation of the Charm Store. The underlying technology doesn't seem fully baked either, but I profess that I didn't look into it much.

@@ Line 7: / Line 7: @@
 == Links ==
 # https://jujucharms.com/get-started
 # https://jujucharms.com/docs/1.20/config-manual
 # https://jujucharms.com/docs/1.20/config-aws
@@ Line 16: / Line 15: @@
 <source lang="bash">
 sudo add-apt-repository ppa:juju/stable
+sudo apt-get update
 sudo apt-get install juju-quickstart
 sudo apt-get install juju-core
@@ Line 21: / Line 22: @@
 # juju generate-config --show
 juju generate-config
-# edit to add your AWS KEYS
+# edit .juju/environments.yaml to add your AWS KEYS
 juju bootstrap
 juju status
@@ Line 58: / Line 59: @@
 <code>ssh -i /home/user/.ssh/id_rsa -o IdentitiesOnly=true -vvv ubuntu@ec2-55-5-555-55.compute-1.amazonaws.com</code>
-https://jujucharms.com/mediawiki/trusty/3
+The above 'recipe' installs [https://jujucharms.com/mediawiki/trusty/3 this MediaWiki charm] which has been deployed 813 times as of this writing.  BFD.  It didn't work for me (I had to add [https://jujucharms.com/apache2/trusty/13/ Apache]).  Although this charm invokes a2enconf, I don't see any code which installs or verifies Apache2 as a dependency in the [http://bazaar.launchpad.net/~charmers/charms/trusty/mediawiki/trunk/view/head:/hooks/install install hook].  So, yeah, garbage.  They should read the docs about [https://jujucharms.com/docs/1.20/authors-charm-writing how to write a charm]. The example explicitly installs, configures and starts Apache as part of a simple web service.  But the documentation is very sparse. The only "interface" (a primary element of orchestration) that is documented is 'mysql' and even that is barely covered.
+[https://jujucharms.com/wordpress/trusty/2 The Wordpress charm] is [http://bazaar.launchpad.net/~charmers/charms/trusty/wordpress/trunk/files written better] because it works, and actually offers a simple switch between nginx and Apache.  Although it's a bit more 'polished' the WordPress Charm is still [http://bazaar.launchpad.net/~charmers/charms/trusty/wordpress/trunk/view/head:/inc/common a bunch of bash scripts] that end up installing things all over the place (standard locations?).  It installs [http://php-fpm.org/ php-fpm] (FastCGI Process Manager, which is an alternative PHP FastCGI implementation) It does use git, but is it configurable as to who/what/where you can pull from? I figured out that for the Wordpress charm, you can see the 'components' in the [http://bazaar.launchpad.net/~charmers/charms/trusty/wordpress/trunk/files/head:/files/charm/ 'charm' directory].
+In general, I'm '''very''' unimpressed with the implementation of the Charm Store.  The underlying technology doesn't seem fully baked either, but I profess that I didn't look into it much.