[2.3b3, Filtering] I want to be able to filter out the VMS of a Pod from the machine listing
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Undecided
|
Alberto Donato | ||
| maas (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| Xenial |
New
|
Undecided
|
Unassigned | ||
Bug Description
I got feedback from the CPE team that they want to filter out the VMs from the machine listing, so that they can manage their servers. We had designed a filter for pods as part of the Intel RSD work, which didn't get implemented.
This filter is quite useful for the customers who work with Pods, and I assume this use case will increase as MAAS gets integrated in bigger data centres with a variety of hardware.
Bug description:
* Current result:
Given I am in Machine listing
When I try to only see my physical servers or when I only try to see the VMs within a Pod
Then I cannot filter the list to do so
* Expected/ correct result:
Given I am in Machine listing
When I try to only see my physical servers or when I only try to see the VMs within a Pod
Then I should be able to filter the list by Pod
Designs can be found here:
[OS X Sierra]
Chrome, Version 61.0.3163.100 (64-bit)
Related branches
- MAAS Lander: Approve
- Blake Rouse (community): Approve
-
Diff: 158 lines (+59/-4)8 files modifiedsrc/maasserver/static/js/angular/factories/machines.js (+3/-0)
src/maasserver/static/js/angular/factories/tests/test_machines.js (+2/-2)
src/maasserver/static/js/angular/filters/nodes.js (+3/-0)
src/maasserver/static/js/angular/filters/tests/test_nodes.js (+15/-0)
src/maasserver/static/partials/nodes-list.html (+10/-0)
src/maasserver/websockets/handlers/machine.py (+1/-1)
src/maasserver/websockets/handlers/node.py (+6/-0)
src/maasserver/websockets/handlers/tests/test_machine.py (+19/-1)
| Maria Vrachni (m-vrachnis) wrote | #1 |
| Changed in maas: | |
| assignee: | nobody → Alberto Donato (ack) |
| tags: | added: pods |
| tags: |
added: pod removed: pods |
| Changed in maas: | |
| status: | New → In Progress |
| Changed in maas: | |
| milestone: | none → next |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| milestone: | next → 2.4.0alpha1 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
| Doug Parrish (dparrish) wrote | #2 |
This bug has appeared in 2.3.6, whereas 2.3.5 was fine. Manually updating node.py with the same fix resolved the problem. Can this fix be backported? There are quite a few FCBs with MAAS running on Xenial. Thank you.