Default constraints make no sense on MAAS

Bug #1064291 reported by Robie Basak on 2012-10-09
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Release Notes for Ubuntu

Bug Description

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"

Tags: arm Edit Tag help
Robie Basak (racb) on 2012-10-09
tags: added: arm
Robie Basak (racb) wrote :

This actually applies to other default constraints as well. Why should MAAS+juju require 512M by default? If I set up a MAAS cluster of only nodes with 256M, then it won't work by default as it is. I accept that this is unlikely, but it does demonstrate that default constraints don't make sense on MAAS at all.

summary: - Default architecture constraint of amd64 makes no sense on arm
+ Default constraints makes no sense on MAAS
summary: - Default constraints makes no sense on MAAS
+ Default constraints make no sense on MAAS
Pete Graner (pgraner) on 2013-04-22
Changed in ubuntu-release-notes:
status: New → Invalid
Robie Basak (racb) wrote :

Another failure case has been pointed out to me on IRC. Users of i386 nodes are affected by this too. This bug causes MAAS not to work for them by default.

Robie Basak (racb) on 2013-05-02
description: updated
description: updated
Curtis Hovey (sinzui) on 2013-10-12
Changed in juju:
importance: Undecided → Low
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers