| 2021-08-04 16:08:27 |
James Vaughn |
bug |
|
|
added bug |
| 2021-08-04 16:57:52 |
Amy Pattanasethanon |
description |
This comes from a customer request.
As per title, would it be possible to filter machines by power address (BMC, iLO, iDRAC, etc.)?
In case anybody else wants this feature and comes across this request, at the moment, I can think of a couple of workarounds (of varying suitability):
- Use tags. It isn't possible to partially match a tag (e.g. tag "192.168.1.10" won't be matched by a search for "192"), so it makes most sense to implement some sort of tagging scheme to achieve this, e.g. if you have a BMC network of 192.168.1.0/24 and a machine with a power address of 192.168.1.10, you could have "power:192.168.1.0/24" and "power:192.168.1.10" as tags for that machine.
- Use `jq` in the CLI. This was thrown together quickly, but the following could be used to return the power parameters and "system_id" of every machine managed by MAAS:
```
for i in $(maas "$MAAS_USER" machines read | jq -r '.[].system_id'); do maas <LOGIN> machine power-parameters "$i" | jq ". + {\"system_id\": \"$i\"}"; done | jq -s
```
Alternatively, to filter by particular attributes, such as "power_type":
```
for i in $(maas "$MAAS_USER" machines read | jq -r '.[] | select(.power_type == "moonshot") | .system_id'); do maas <LOGIN> machine power-parameters "$i" | jq ". + {\"system_id\": \"$i\"}"; done | jq -s
```
These would return:
```
[
{
"power_pass": "notapass",
"power_user": "notauser",
"power_address": "10.188.127.24",
"power_hwaddress": "52:54:00:5e:28:8f",
"system_id": "ybb6aq"
},
{
"power_pass": "notauser2",
"power_user": "notapass2",
"power_address": "10.188.127.25",
"power_hwaddress": "52:54:00:71:ef:f3",
"system_id": "8wyxah"
}
]
```
Which can then further be filtered with `jq`. Of course, given that a `power-parameters` query is made for every MAAS machine, this is slow. Additionally, "system_id" is not a particularly human-readable attribute; including "fqdn", for example, would be much more useful. However, this is beyond the scope here. |
This comes from a customer request.
As per title, would it be possible to filter machines by power address (BMC, iLO, iDRAC, etc.)?
In case anybody else wants this feature and comes across this request, at the moment, I can think of a couple of workarounds (of varying suitability):
- Use tags. It isn't possible to partially match a tag (e.g. tag "192.168.1.10" won't be matched by a search for "192"), so it makes most sense to implement some sort of tagging scheme to achieve this, e.g. if you have a BMC network of 192.168.1.0/24 and a machine with a power address of 192.168.1.10, you could have "power:192.168.1.0/24" and "power:192.168.1.10" as tags for that machine.
- Use `jq` in the CLI. This was thrown together quickly, but the following could be used to return the power parameters and "system_id" of every machine managed by MAAS:
```
for i in $(maas "$MAAS_USER" machines read | jq -r '.[].system_id'); do maas <LOGIN> machine power-parameters "$i" | jq ". + {\"system_id\": \"$i\"}"; done | jq -s
```
Alternatively, to filter by particular attributes, such as "power_type":
```
for i in $(maas "$MAAS_USER" machines read | jq -r '.[] | select(.power_type == "moonshot") | .system_id'); do maas <LOGIN> machine power-parameters "$i" | jq ". + {\"system_id\": \"$i\"}"; done | jq -s
```
These would return:
```
[
{
"power_pass": "notapass",
"power_user": "notauser",
"power_address": "10.188.127.24",
"power_hwaddress": "52:54:00:5e:28:8f",
"system_id": "ybb6aq"
},
{
"power_pass": "notauser2",
"power_user": "notapass2",
"power_address": "10.188.127.25",
"power_hwaddress": "52:54:00:71:ef:f3",
"system_id": "8wyxah"
}
]
```
Which can then further be filtered with `jq`. Of course, given that a `power-parameters` query is made for every MAAS machine, this is slow. Additionally, "system_id" is not a particularly human-readable attribute; including "fqdn", for example, would be much more useful. However, this is beyond the scope here.
Reference to a case link: https://canonical.lightning.force.com/lightning/r/Case/5004K000009Vg1LQAS/view |
|
| 2021-08-04 17:12:05 |
🤖 prod-design-maas-ui-lp-bot |
bug watch added |
|
https://github.com/canonical-web-and-design/maas-ui/issues/2927 |
|
| 2021-08-04 17:12:07 |
🤖 prod-design-maas-ui-lp-bot |
maas-ui: remote watch |
|
github.com/canonical-web-and-design/maas-ui/issues #2927 |
|
| 2021-08-09 20:15:32 |
Bill Wear |
maas: status |
New |
Invalid |
|
| 2021-08-09 20:15:55 |
Bill Wear |
maas: status |
Invalid |
New |
|
| 2021-08-17 15:13:19 |
James Vaughn |
summary |
Filter machines by power address (BMC, iLO, DRAC, etc.) |
Filter machines by power address, serial number (BMC, iLO, DRAC, etc.) |
|
| 2021-08-17 15:15:16 |
James Vaughn |
description |
This comes from a customer request.
As per title, would it be possible to filter machines by power address (BMC, iLO, iDRAC, etc.)?
In case anybody else wants this feature and comes across this request, at the moment, I can think of a couple of workarounds (of varying suitability):
- Use tags. It isn't possible to partially match a tag (e.g. tag "192.168.1.10" won't be matched by a search for "192"), so it makes most sense to implement some sort of tagging scheme to achieve this, e.g. if you have a BMC network of 192.168.1.0/24 and a machine with a power address of 192.168.1.10, you could have "power:192.168.1.0/24" and "power:192.168.1.10" as tags for that machine.
- Use `jq` in the CLI. This was thrown together quickly, but the following could be used to return the power parameters and "system_id" of every machine managed by MAAS:
```
for i in $(maas "$MAAS_USER" machines read | jq -r '.[].system_id'); do maas <LOGIN> machine power-parameters "$i" | jq ". + {\"system_id\": \"$i\"}"; done | jq -s
```
Alternatively, to filter by particular attributes, such as "power_type":
```
for i in $(maas "$MAAS_USER" machines read | jq -r '.[] | select(.power_type == "moonshot") | .system_id'); do maas <LOGIN> machine power-parameters "$i" | jq ". + {\"system_id\": \"$i\"}"; done | jq -s
```
These would return:
```
[
{
"power_pass": "notapass",
"power_user": "notauser",
"power_address": "10.188.127.24",
"power_hwaddress": "52:54:00:5e:28:8f",
"system_id": "ybb6aq"
},
{
"power_pass": "notauser2",
"power_user": "notapass2",
"power_address": "10.188.127.25",
"power_hwaddress": "52:54:00:71:ef:f3",
"system_id": "8wyxah"
}
]
```
Which can then further be filtered with `jq`. Of course, given that a `power-parameters` query is made for every MAAS machine, this is slow. Additionally, "system_id" is not a particularly human-readable attribute; including "fqdn", for example, would be much more useful. However, this is beyond the scope here.
Reference to a case link: https://canonical.lightning.force.com/lightning/r/Case/5004K000009Vg1LQAS/view |
This comes from a customer request.
As per title, would it be possible to filter machines by power address (BMC, iLO, iDRAC, etc.)?
In case anybody else wants this feature and comes across this request, at the moment, I can think of a couple of workarounds (of varying suitability):
- Use tags. It isn't possible to partially match a tag (e.g. tag "192.168.1.10" won't be matched by a search for "192"), so it makes most sense to implement some sort of tagging scheme to achieve this, e.g. if you have a BMC network of 192.168.1.0/24 and a machine with a power address of 192.168.1.10, you could have "power:192.168.1.0/24" and "power:192.168.1.10" as tags for that machine.
- Use `jq` in the CLI. This was thrown together quickly, but the following could be used to return the power parameters and "system_id" of every machine managed by MAAS:
```
for i in $(maas "$MAAS_USER" machines read | jq -r '.[].system_id'); do maas <LOGIN> machine power-parameters "$i" | jq ". + {\"system_id\": \"$i\"}"; done | jq -s
```
Alternatively, to filter by particular attributes, such as "power_type":
```
for i in $(maas "$MAAS_USER" machines read | jq -r '.[] | select(.power_type == "moonshot") | .system_id'); do maas <LOGIN> machine power-parameters "$i" | jq ". + {\"system_id\": \"$i\"}"; done | jq -s
```
These would return:
```
[
{
"power_pass": "notapass",
"power_user": "notauser",
"power_address": "10.188.127.24",
"power_hwaddress": "52:54:00:5e:28:8f",
"system_id": "ybb6aq"
},
{
"power_pass": "notauser2",
"power_user": "notapass2",
"power_address": "10.188.127.25",
"power_hwaddress": "52:54:00:71:ef:f3",
"system_id": "8wyxah"
}
]
```
Which can then further be filtered with `jq`. Of course, given that a `power-parameters` query is made for every MAAS machine, this is slow. Additionally, "system_id" is not a particularly human-readable attribute; including "fqdn", for example, would be much more useful. However, this is beyond the scope here.
Reference to a case link: https://canonical.lightning.force.com/lightning/r/Case/5004K000009Vg1LQAS/view
EDIT (2021-08-17): I've tested a MAAS 2.7.2 installation (STS MAAS) and found that if filtering by power address or serial number works. It therefore seems that there might be a regression here. |
|
| 2021-08-17 15:41:40 |
James Vaughn |
tags |
feature ui |
ui |
|
| 2021-08-18 08:51:27 |
Adam Collard |
maas: status |
New |
Incomplete |
|
| 2021-08-20 12:27:34 |
James Vaughn |
attachment added |
|
lp1938927-screenshots.tar.xz https://bugs.launchpad.net/maas/+bug/1938927/+attachment/5519399/+files/lp1938927-screenshots.tar.xz |
|
| 2021-08-26 14:01:59 |
James Vaughn |
tags |
ui |
feature ui |
|
| 2021-09-14 13:53:03 |
Alexsander de Souza |
maas: status |
Incomplete |
Invalid |
|
| 2021-09-15 13:16:56 |
Bug Watch Updater |
maas-ui: importance |
Undecided |
Unknown |
|
| 2023-06-01 15:20:05 |
Thorsten Merten |
maas-ui: remote watch |
MAAS UI GitHub issues #2927 |
|
|
| 2023-06-15 07:15:21 |
Thorsten Merten |
maas-ui: importance |
Unknown |
Low |
|
| 2023-06-15 07:15:21 |
Thorsten Merten |
maas-ui: status |
New |
Fix Released |
|
| 2023-06-15 07:15:21 |
Thorsten Merten |
maas-ui: milestone |
|
3.4.0-beta1 |
|
