Description of problem: From a broker I'd like to see all my running gears on all my nodes from the command line. So in the same way each node can show me gears with: oo-admin-ctl-gears list Version-Release number of selected component (if applicable): # cat /etc/openshift-enterprise-release OpenShift Enterprise 2.1.7 How reproducible: There are no commands to show all gears running. Steps to Reproduce: 1. Login to broker 2. Look for oo commands to query all gears. 3. Actual results: No commands available. Expected results: A version of oo-admin-ctl-gears Is present that uses MCO to query each node and report back. Additional info:
Would you mind sharing the use case behind this? It seems like a command that would only be useful if you only had a small number of relatively static gears. If you had thousands (or tens of thousands) of gears that were constantly changing state how is this list useful?
Mostly it's desired for speed of administration. Basically if someone says they are having issues with a gear they tell me the UUID, which they grabbed from an rhc app-show or something. I usually then want to login to the node the gear is on with an admin login and poke around. So i have been going to the admin-console and searching for the user, finding his gear that the complaint is about and seeing the node. I can then hop onto the node to troubleshoot. But the minute i hit the gui it feels "wrong". I'd prefer to get on a broker and get the info; kinda treating the broker as a centralized admin space and being able to script it quickly. But i do see what you mean - it's kinda asking for a "shortcut" to things that have other ways already.
(In reply to August Simonelli from comment #5) > Mostly it's desired for speed of administration. Basically if someone says > they are having issues with a gear they tell me the UUID, OK, but that's what oo-app-info is for. See e.g. # oo-app-info --login demo (see all apps for a user) # oo-app-info --login demo --app py33s (see a specific app for that user) # oo-app-info -u 544716d7f09833e743000009 (see a specific gear) Looking at the admin guide, I see we don't currently mention that tool. It's the right one for the job (barring an admin API which should run a lot faster). I'll file a bug to mention it in the docs. Aside from this use case which I would consider "handled", is there any other reason to prioritize this RFE?
OpenShift Enterprise v2 has officially reached EoL. This product is no longer supported and bugs will be closed. Please look into the replacement enterprise-grade container option, OpenShift Container Platform v3. https://www.openshift.com/container-platform/ More information can be found here: https://access.redhat.com/support/policy/updates/openshift/