bootstrap constraints

[Liam Young]

Definite +1, I think it makes the scope of the constraint clear.

Thanks
Liam

On 28/08/15 12:36, Mark Shuttleworth wrote:
> On 28/08/15 11:30, Liam Young wrote:
> > Fwiw I raised Bug #1240431 a while ago because I also felt that it wasn't intuitive that the 
> constraints passed when bootstrapping refereed to the whole environment.
>
> The shift to have multiple environments in a single juju server means 
> that we obviously have to decouple the "admin" environment, where the 
> state servers are hosted, from any other environments that get created.
>
> Today, you'll bootstrap for every environment. In the upcoming stable 
> release, you'll bootstrap once then create environments on demand.
>
> I think it's fine to re-use the "constraints" language for the 
> bootstrap machines and also keep this language as the way to describe 
> the default host on create-environment. In other words:
>
>   juju bootstrap constraints=XXX
>   juju create-environment foo constraints=XXX
>
> Does that sound about right?
>
> Mark
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20150828/976f80f7/attachment.html>