provider/maas: StartInstance does not use standard arch preference algo
Bug #1358219 reported by
Andrew Wilkins
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Low
|
Unassigned | ||
Bug Description
In the maas provider, we currently just acquire an arbitrary node unless an arch constraint is specified. Ideally we would use the same algorithm as in the other providers if no architecture is specified. That is, use the first available arch of the supported arches ordered first by bit-width (descending), and then by name (ascending).
There is some complication in maas, because resources are finite.
| tags: | added: constraints |
| Changed in juju-core: | |
| importance: | Low → High |
| milestone: | none → 2.1.0 |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.1.0 → none |
| milestone: | none → 2.1.0 |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #1 |
| tags: | added: tech-debt |
| Changed in juju: | |
| importance: | High → Low |
| milestone: | 2.1.0 → none |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #2 |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #3 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This looks like a tech debt item. I re-triaging this to Low.