charm store: serve metadata and config?
William Reade
william.reade at canonical.com
Mon May 21 17:19:21 UTC 2012
On Mon, 2012-05-21 at 14:15 -0300, Gustavo Niemeyer wrote:
> Hey William,
>
> On Mon, May 21, 2012 at 12:26 PM, William Reade
> <william.reade at canonical.com> wrote:
> > We informally agreed recently that it would be nice not to have to
> > download charmstore charms to users' machines, and to reference them by
> > bundleURL exclusively; but, at the moment, we do still need to download
> > store charms (so that we can poke metadata/config into zookeeper). One
> > way to get around this requirement would be to also serve charms'
> > metadata and config directly from the charm store. Does anyone have an
> > opinion on this?
>
> The idea was always to have that metadata and the config readily
> available via the store, so that certainly sounds fine in principle.
>
> Is there an imminent use case for that?
If we want to avoid downloading charms, we'll need it for `juju deploy`,
which I'm just looking into the prereqs for at the moment. So there's
definitely a use case, but no strict requirement (yet?).
>
>
> gustavo @ http://niemeyer.net
More information about the Juju
mailing list