| 2017-07-25 19:50:27 |
Jason Hobbs |
bug |
|
|
added bug |
| 2017-07-25 19:51:58 |
Jason Hobbs |
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 of if the pod's zone matches the allocate request's zone. |
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 of if the pod's zone matches the allocate request's zone. See bug 1706196. |
|
| 2017-07-25 21:43:49 |
Mike Pontillo |
maas: status |
New |
Triaged |
|
| 2017-07-25 21:43:51 |
Mike Pontillo |
maas: importance |
Undecided |
Wishlist |
|
| 2017-07-25 21:43:59 |
Mike Pontillo |
summary |
pods don't have availability zones |
[2.2+] pods don't have availability zones |
|
| 2017-07-25 21:57:24 |
Jason Hobbs |
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 of if the pod's zone matches the allocate request's zone. See bug 1706196. |
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. |
|
| 2017-08-06 15:46:47 |
Nobuto Murata |
bug |
|
|
added subscriber Nobuto Murata |
| 2017-08-08 19:21:22 |
Jason Hobbs |
tags |
cdo-qa |
cdo-qa foundations-engine |
|
| 2017-10-05 13:17:36 |
Andres Rodriguez |
tags |
cdo-qa foundations-engine |
cdo-qa foundations-engine internal |
|
| 2017-11-21 23:05:32 |
Andres Rodriguez |
maas: milestone |
|
2.4.x |
|
| 2017-11-21 23:05:43 |
Andres Rodriguez |
maas: assignee |
|
Newell Jensen (newell-jensen) |
|
| 2017-11-21 23:05:52 |
Andres Rodriguez |
tags |
cdo-qa foundations-engine internal |
cdo-qa foundations-engine internal pod |
|
| 2017-11-22 01:06:46 |
Newell Jensen |
maas: status |
Triaged |
In Progress |
|
| 2017-11-28 04:35:37 |
Newell Jensen |
maas: status |
In Progress |
Confirmed |
|
| 2018-02-20 23:58:02 |
Newell Jensen |
maas: status |
Confirmed |
In Progress |
|
| 2018-02-20 23:59:30 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/338358 |
|
| 2018-02-25 18:48:59 |
MAAS Lander |
maas: status |
In Progress |
Fix Committed |
|
| 2018-03-01 14:36:11 |
Andres Rodriguez |
maas: milestone |
2.4.x |
2.4.0alpha2 |
|
| 2018-03-01 15:46:33 |
Andres Rodriguez |
maas: status |
Fix Committed |
In Progress |
|
| 2018-03-01 15:46:44 |
Andres Rodriguez |
merge proposal linked |
|
https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/340073 |
|
| 2018-03-01 19:10:37 |
MAAS Lander |
maas: status |
In Progress |
Fix Committed |
|
| 2018-03-13 12:13:04 |
Andres Rodriguez |
maas: status |
Fix Committed |
Fix Released |
|
