On 17 April 2014 05:12, John A Meinel <email address hidden> wrote:
> I'm not sure where distro-info is coming into play when determining what
> machines should be deployed.
>
> It is supposed to always deploy a machine based on the series of the charm.
> So doing "juju deploy mysql" will do a lookup in the charm store (via the API Server) for what series "mysql" should use, and that should return precise/trusty based on what versions of charms are available.
distro-info is used when we are creating a machine without a charm.
This happens when bootstrapping, when using add-machine
and when using ensure-availability.
> Or perhaps this bug isn't about a charm, but instead only affects the
> "ensure-state-availability" code since that doesn't actually have a
> charm that it is deploying.
On 17 April 2014 05:12, John A Meinel <email address hidden> wrote:
> I'm not sure where distro-info is coming into play when determining what
> machines should be deployed.
>
> It is supposed to always deploy a machine based on the series of the charm.
> So doing "juju deploy mysql" will do a lookup in the charm store (via the API Server) for what series "mysql" should use, and that should return precise/trusty based on what versions of charms are available.
distro-info is used when we are creating a machine without a charm. availability.
This happens when bootstrapping, when using add-machine
and when using ensure-
> Or perhaps this bug isn't about a charm, but instead only affects the state-availabil ity" code since that doesn't actually have a
> "ensure-
> charm that it is deploying.
Yes. I should have made that clearer.