Default constraints make no sense on MAAS
|||Release Notes for Ubuntu||
I have a MAAS cluster consisting entirely of ARM nodes. I run "juju bootstrap" against this environment, and juju requests amd64 nodes and then fails. This works as expected. But the default does not make sense here.
I understand that on EC2 a reasonable user would expect some sensible instance type instantiated by default, and this is what the default constraints currently achieve.
But with MAAS, I think a reasonable user would expect no constraints to be applied by default.
Does this mean that default constraints need to be per-provider?
Other users affected: those with i386, or with mem < 512M.
Workaround: use: juju bootstrap --constraints "arch=any mem=0"
- Default architecture constraint of amd64 makes no sense on arm
+ Default constraints makes no sense on MAAS
- Default constraints makes no sense on MAAS
+ Default constraints make no sense on MAAS
|Changed in ubuntu-release-notes:|
|status:||New → Invalid|
|Changed in juju:|
|importance:||Undecided → Low|
|status:||New → Triaged|