manual bootstrap in 1.18

[Mark Canonical Ramm-Christensen]

I think this is a huge regression for a lot of people on the devel release.
 It means you can have manual provisioning within a cloud, but that you
can't use Kapil's digital ocean plugin, use a pile of servers in your
basement (which don't have good IPMI, and can't run with MAAS), etc.

So, it should be handled very carefully.

Why not release 1.18 with the issues described and fix them in 1.19/1.20?

How much work is it to fix this before we release 1.18?

--Mark Ramm


On Mon, Mar 3, 2014 at 12:51 PM, Nate Finch <nate.finch at canonical.com>wrote:

> What you'll be able to do is to bootstrap a normal environment (like EC2)
> and then add manual machines to that environment (like your Digital Ocean
> machine).  All it disables is the ability to have the bootstrap node on a
> non-cloud provider.
>
>
> On Mon, Mar 3, 2014 at 12:46 PM, Sean Feole <sean.feole at canonical.com>wrote:
>
>> Hey William,
>>
>> Will switching off the manual bootstrap feature disable manual provider
>> functionality all together?
>>
>>  Just trying to get a better understanding!
>>
>> Thanks
>> -Sean
>>
>>
>> On Mon, Mar 3, 2014 at 11:54 AM, William Reade <
>> william.reade at canonical.com> wrote:
>>
>>> 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
>>>
>>> --
>>> Juju-dev mailing list
>>> Juju-dev at lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>>
>>>
>>
>> --
>> Juju-dev mailing list
>> Juju-dev at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>
>>
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140303/8b2866f1/attachment.html>