On 04/03/14 15:22, Andrew Wilkins wrote:
> On Tue, Mar 4, 2014 at 12:54 AM, William Reade
> 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 regre
On Tue, Mar 4, 2014 at 12:54 AM, William Reade
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 boots
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 shou
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 wrote:
> H
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
wrote:
> Hi all
>
> We've been talking about what we need to do to finalise
On Mon, Mar 3, 2014 at 11:54 AM, William Reade
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 boots
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14-03-03 11:54 AM, William Reade wrote:
> 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
>
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 tha
