Comment 0 for bug 1064291
Revision history for this message
| Robie Basak (racb) wrote Default architecture constraint of amd64 makes no sense on arm | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
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.
The current solution is to run "juju bootstrap --constraints arch=arm" instead. 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?