[2.2+] pods don't have availability zones

Bug #1706438 reported by Jason Hobbs
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Wishlist
Newell Jensen

Bug Description

At least for virsh pods, where a pod is one physical machine, pods should have a 'zone' field, and all of the machines in a pod should be associated with the zone of the pod automatically.

Right now, MAAS will try to create machines in a pod using whatever zone is requested in the 'allocate' API call. In reality, a pod is in a specific zone and this doesn't make sense. MAAS should only allocate from the pod if no zone was requested or if the pod's zone matches the allocate request's zone. See bug 1706196.

Related branches

description: updated
Changed in maas:
status: New → Triaged
importance: Undecided → Wishlist
summary: - pods don't have availability zones
+ [2.2+] pods don't have availability zones
description: updated
tags: added: foundations-engine
tags: added: internal
Changed in maas:
milestone: none → 2.4.x
assignee: nobody → Newell Jensen (newell-jensen)
tags: added: pod
Changed in maas:
status: Triaged → In Progress
Changed in maas:
status: In Progress → Confirmed
Changed in maas:
status: Confirmed → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
milestone: 2.4.x → 2.4.0alpha2
Changed in maas:
status: Fix Committed → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
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.