KVM compose should inherit AZ from host

Bug #1805112 reported by Anthony Dillon
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Steve Rydz

Related branches

description: updated
Revision history for this message
Andres Rodriguez (andreserl) wrote :

The zone name is “default”. Are you saying that if you change that to a different zone (the pod) the compose menu still uses “default”? (The screenshot doesn’t show that difference)

Changed in maas:
status: New → Incomplete
Revision history for this message
Martin Storey (cassiocassio) wrote :

I think the argument was that AZ was a description of physical availablity - something like north-building or floor three or on-big-switch-with-backup-power-B.

It's a promise of reliability, that if you split HA units between AZs you will have greater resilience.

And so

(1) AZ is a property of the KVM host, and it's child-VMs should inherit this value. The user should not be able to assign this value at KVM VM compose time. (as it currrently is?)

So yes,

(2) if the pod changes it's AZ, then that truth would ripple throughout child-machines.

Changed in maas:
status: Incomplete → Confirmed
importance: Undecided → High
Steve Rydz (steverydz)
Changed in maas:
assignee: nobody → Steve Rydz (steverydz)
Changed in maas:
milestone: none → next
status: Confirmed → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
Changed in maas:
milestone: next → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.