What would you like to see in the virtual Charm School hangouts?

[Mark Canonical Ramm-Christensen]

Just last week a few of us were just discussing the possible need for an
optional "build" hook which was restricted (by policy) to just setup
dependencies, and not actually configure or start anything.  It would solve
this immediate need, and might be useful at some point in the future as a
place to snapshot images of the unit's container in order to enhance the
performance of further "add-unit" commands.

The current use case is compelling enough that I think this would be
valuable to us even without consideration of the future possibilities that
this could bring when units are generally containerized.



On Fri, May 24, 2013 at 10:47 AM, Stuart Bishop <stuart.bishop at canonical.com
> wrote:

> On Fri, May 24, 2013 at 4:25 PM,  <franck.dehay at orange.com> wrote:
> > Couldn’t we get a “pre-install” hook somewhere?
>
> I would certainly like to see some sort of a pre-install hook or list
> of dependencies- perhaps just a list of packages in one of the top
> level yaml files that are installed before the install hook is
> invoked.
>
> A few times I've seen problems where the install hook fails because
> the module the hook is in or one of its helper modules is attempting
> to import from a library that isn't yet installed. There are numerous
> examples in the charm store of charms with imports being done inside a
> function's scope instead of in the module's scope to avoid this.
>
> This could also provide a nicer mechanism for distributing common
> libraries of charm helpers that is better than the current process of
> just making a copy of the helpers into your charm.
>
>
> --
> Stuart Bishop <stuart.bishop at canonical.com>
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20130525/bed2f7ff/attachment.html>