Feature #13871
openList capsule status similar to virsh
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1255498
Description of problem:
As we are scaling capsules, would need to show capsule status (off/on)
In below list around 100 capsules/VM's are shutdown. End user has no clue about these capsule status
[root@perfc-380g8-01 ~]# hammer u admin -p changeme capsule list|--------------------------------------------|--------------------------------------------------------
---
ID | NAME | URL
----|--------------------------------------------|--------------------------------------------------------
1 | perfc-380g8-01.perf.lab.eng.rdu.redhat.com | https://perfc-380g8-01.perf.lab.eng.rdu.redhat.com:9090
2 | vmcapsule001.perf.lab.eng.rdu.redhat.com | https://vmcapsule001.perf.lab.eng.rdu.redhat.com:9090
3 | vmcapsule002.perf.lab.eng.rdu.redhat.com | https://vmcapsule002.perf.lab.eng.rdu.redhat.com:9090
4 | vmcapsule003.perf.lab.eng.rdu.redhat.com | https://vmcapsule003.perf.lab.eng.rdu.redhat.com:9090
5 | vmcapsule004.perf.lab.eng.rdu.redhat.com | https://vmcapsule004.perf.lab.eng.rdu.redhat.com:9090
6 | vmcapsule005.perf.lab.eng.rdu.redhat.com | https://vmcapsule005.perf.lab.eng.rdu.redhat.com:9090
7 | vmcapsule006.perf.lab.eng.rdu.redhat.com | https://vmcapsule006.perf.lab.eng.rdu.redhat.com:9090
8 | vmcapsule007.perf.lab.eng.rdu.redhat.com | https://vmcapsule007.perf.lab.eng.rdu.redhat.com:9090
9 | vmcapsule008.perf.lab.eng.rdu.redhat.com | https://vmcapsule008.perf.lab.eng.rdu.redhat.com:9090
10 | vmcapsule009.perf.lab.eng.rdu.redhat.com | https://vmcapsule009.perf.lab.eng.rdu.redhat.com:9090
11 | vmcapsule010.perf.lab.eng.rdu.redhat.com | https://vmcapsule010.perf.lab.eng.rdu.redhat.com:9090
...
We should list capsule status some thing similar to virsh/libvirt.
For ex:
virsh # list --all
Id Name State
----------------------------------------------------
21 vm1 running
22 vm2 running
23 vm3 running
24 vm4 running
25 vm5 running
26 vm6 running
27 vm7 running
28 vm8 running
29 vm9 running
30 vm10 running
31 vm11 running
32 vm12 running
33 vm13 running
34 vm14 running
35 vm15 running
36 vm16 running
- dhcp31-68 shut off
- master shut off
- rhel71 shut off
virsh #
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Stop capsule nodes.
2.
3.
Actual results:
Capsule status is not shown.
Expected results:
Show capsule status
Additional info:
Updated by Tomáš Strachota almost 9 years ago
- Description updated (diff)
- Category set to Foreman commands (obsolete)
Updated by Tomáš Strachota almost 9 years ago
- Related to Tracker #12719: As a user I would like to consume Proxy additional information via hammer. added
Updated by Tomáš Strachota almost 9 years ago
Fetching status for each proxy in the list might cause serious performance issues. We do it asynchronously in the UI. Shlomi, will the proxy info caching help us in this case?
Updated by Shlomi Zadok almost 9 years ago
I think it will. We should be able to say if it is on / off (and cache that). Please note that default caching is for 3 minutes
Updated by Tomáš Strachota over 6 years ago
- Category changed from Foreman commands (obsolete) to Proxy