Comment 1 for bug 1768308

actually it is the other way around. --constraints affects everything,
including the controller and any future applications that are deployed.
--bootstrap-constraints only effects the controllers and not deployed apps.

John
=:->

On Tue, May 1, 2018, 19:35 Peter Matulis <email address hidden>
wrote:

> Public bug reported:
>
> When I specify a default constraint during controller-creation time with
> '--constraints' it appears that it (here disk space) gets applied to the
> controller:
>
> $ juju bootstrap --no-gui --bootstrap-series=bionic --constraints
> "root-disk=64G" aws aws-bionic-constraints2
> $ juju ssh -m controller 0 'df -h'
>
> /dev/xvda1 62G 3.0G 60G 5% /
>
> When I use no constraints I get a much smaller disk for the controller:
>
> $ juju bootstrap --no-gui --bootstrap-series=bionic aws
> aws-bionic-constraints3
> $ juju ssh -m controller 0 'df -h'
>
> Filesystem Size Used Avail Use% Mounted on
> udev 1.9G 0 1.9G 0% /dev
> tmpfs 376M 744K 375M 1% /run
> /dev/xvda1 31G 3.0G 28G 10% /
>
> I thought the controller is only affected by '--bootstrap-constraints'?
>
> https://paste.ubuntu.com/p/BCcqHtGWfr/
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
>
> ** Tags: docteam
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1768308
>
> Title:
> Machine constraints are used as Controller constraints
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1768308/+subscriptions
>