manual bootstrap in 1.18
William Reade
william.reade at canonical.com
Mon Mar 3 16:54:26 UTC 2014
Hi all
We've been talking about what we need to do to finalise 1.18, and the issue
with manual bootstrap addresses in environments.yaml [0] has been causing
us some problems; in particular, we think it was a mistake to put the
bootstrap node address in environments.yaml in the first place, and that
what we should have done was to allow for `juju bootstrap --name foo --to
ssh:blah.blah` to create a .jenv without any reference to environments.yaml
at all.
However, blocking 1.18 on this change would be most unhelpful to many
people, so we would like to simply switch off manual provider bootstrap for
the 1.18 release; this would *not* be a regression, because we didn't have
manual bootstrap in 1.16.
If this would make you seriously unhappy, please speak now so we can try to
figure out a path that minimises global sadness.
Cheers
William
[0] https://bugs.launchpad.net/juju-core/+bug/1282642
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140303/dc26bf04/attachment.html>
More information about the Juju-dev
mailing list