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

[Kapil Thangavelu]

On Sat, May 25, 2013 at 12:55 PM, Gustavo Niemeyer <gustavo at niemeyer.net>wrote:

> On Sat, May 25, 2013 at 1:45 PM, Kapil Thangavelu
> <kapil.thangavelu at canonical.com> wrote:
> > Build in this context is charm assembly, ie turn network downloads from
> > deployment runtime activities into pre-deployment activities that flush
> out
> > charm contents.
>
> "install" means "do whatever it takes to install the charm". If you
> want to download content as part of that, sounds fine.
>
> > The goal being robust deployment of units minimizing
> > environment external dependencies.
>
> I'm missing the connection between that and splitting a hook.
>

I'm not sure i would even call it a hook as its pre-deployment (ie sans
units or a service), but this usage of a build command is quite common
already in ops deployed charms, ie. no runtime network install dependencies
that are not under org control or available from the environment
infrastructure (s3, swift, etc), bundling the dep in the charm as
pre-deployment step is an easy solution that avoids issues of 3rd party
resource availability affecting the service deployment. That's distinct
perhaps from the usage in this thread as simple charm spec of package
metadata which afaics is mostly syntactic sugar. Addressing the
unreliability of 3rd party hosted deps is an important use case and why
many favor image deploys, and one way that's being solved with juju today
is a charm build command.

cheers,
Kapil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20130525/b97ef8c0/attachment.html>