Musings around environments, cloud credentials, and the new Juju Controllers
Rick Harding
rick.harding at canonical.com
Fri Nov 13 11:22:12 UTC 2015
No there is still only one state server. It's just that you're auto dropped
into a fresh environment that is not the main controller admin one.
On Fri, Nov 13, 2015, 3:52 AM roger peppe <roger.peppe at canonical.com> wrote:
> On 13 November 2015 at 02:36, Tim Penhey <tim.penhey at canonical.com> wrote:
> > This means that when we bootstrap a controller, we should create one
> > environment for managing the controller (the controller environment),
> > and another empty environment which is the active environment at the end
> > of bootstrap which the user can immediately start deploying workloads
> into.
>
> Won't this have a significant impact on existing deployments that
> reuse the state
> server machine(s) for other units, which can lead to significant cost
> savings in small
> environments?
>
> --
> 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/20151113/4bbe7a76/attachment.html>
More information about the Juju-dev
mailing list