Re: plone charm for juju

Hi,

Thanks for your feedback !

I will play more with juju when I am back from holidays :)

cheers

Sven

On 05/15/2013 08:48 PM, Sidnei da Silva wrote:
> Hi Sven, here's some feedback.
>
>
> On Mon, May 6, 2013 at 2:59 PM, sven <[email protected]
> <mailto:[email protected]>> wrote:
> >
> > Hey,
> >
> > Sorry for the delay I was supposed to mail this on Saturday, but we
> have sun and more than 10 degrees Celsius :)
> >
> > During the last weekend I was playing a bit with Juju
> [https://juju.ubuntu.com/] the Ubuntu deployment.
> >
> > juju aims to be a service deployment and orchestration tool which
> enables the same kind of collaboration and ease of use which today is
> seen around package management to happen on a higher level, around
> services.
> >
> >
> > Since I did not wanted to reinvent the wheel, my goal was to use our
> UI-installer and just do the deploy via juju, another goal was to keep
> the config file for juju as small as possible.
> >
> > The result is here:
> >
> > https://github.com/svx/plone-charm
> >
> > At this moment its really just a 'quick and dirty' proof of concept
> and tested with local deployments on lxc container.
> >
> > There is plenty of room for improvement, but first I wanted to hear
> other opinions, ideas, if we want to do that at all and so on ....
> >
> > What is good to know is, that there at least at the moment some
> limitations with juju, for example to set config on the fly like:
> >
> > 'juju deploy user=foo pas=bar setup=zeo .....'
> >
> > There is a 'set' option in juju, but this option will be executed
> *after* the install. There are open bugs and feature requests about this.
> > So the easiest thing for the moment is to use a config file and
> change stuff there.
>
> You can use juju deploy --config=<path to yaml file>, nad have
> user/pass in the yaml file.
>



> Other than that, the best advice I can give you is to *not* use shell
> scripts for your hooks. Yes, it's easy to get off the ground using
> shell, but it makes for highly difficult to test and debug code.
>
> If you need some inspiration, take a look at the work I did on the
> haproxy charm, specially in tests
> (https://bazaar.launchpad.net/~sidnei/charms/precise/haproxy/trunk/files/head:/hooks/tests/
> <https://bazaar.launchpad.net/%7Esidnei/charms/precise/haproxy/trunk/files/head:/hooks/tests/>).
> We're moving some code that's common between different charms into
> helper
> libraries. https://code.launchpad.net/~charm-helpers/charm-helpers/devel
> <https://code.launchpad.net/%7Echarm-helpers/charm-helpers/devel> is a
> collection of the different ones that cropped up organically and we're
> polishing them to make it the official library to use.
>
> As a last note, think about how you can improve further and make the
> charm support a more scalable setup, separating for example zeo into
> it's own charm, specifying zeo settings over the relation such that
> you can join a plone service to a zeo service and have them scale
> separatedly, things like that. 
>
> Using juju to simply deploy a single unit of a service is not
> interesting, the beauty comes when you have multiple complicated
> services to join together and making them scale independently by
> adding more units here and there, without having to manually change
> config files.
>
> -- Sidnei
>

------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d

_______________________________________________
Plone-installers mailing list
Plone-installers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-installers