1. Proposed title of this feature request Add resource move and ban commands to PCSD web UI -------------------- 2. Who is the customer behind the request? -------------------- 3. What is the nature and description of the request? Add buttons to the PCSD web UI for `pcs resource move` and `pcs resource ban`, with an optional dropdown for selecting a target node. -------------------- 4. Why does the customer need this? (List the business requirements here) - Customer administers cluster primarily through web UI, and moving/banning resources is a fairly standard administrative operation. They have had to run these operations from the command line or by manually adding INFINITY/-INFINITY location constraints. - Currently they have resources that should be cloned, which they want to be able to ban from one node temporarily. In the absence of a "Ban" button, they are concerned that a user will accidentally click "Disable", thus preventing the cloned resource from running on any node. They have created duplicate non-cloned resources, each constrained to a specific node, to protect against such user error. They would like to replace these with cloned resources when a Ban button is available. -------------------- 5. How would the customer like to achieve this? (List the functional requirements here) A button for "Move" and a button for "Ban" under "Resources > RESOURCE_ID", with an optional dropdown or autofill box to select a target node. -------------------- 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. - Visually verify that the move/ban buttons and their respective dropdown boxes are present under the Resources tab of the PCSD web UI after clicking a resource name. - Click the Move button. Verify that there is a -INFINITY location constraint for the resource on the node where it was initially running. Clear the constraint. - Click the Ban button. Verify that there is a -INFINITY location constraint for the resource on the node where it was initially running. Clear the constraint. - Click the Move button and specify a target node. Verify that there is an INFINITY constraint for the resource on the target node. - Click the Ban button and specify a target node. Verify that there is a -INFINITY constraint for the resource on the target node. -------------------- 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? No -------------------- 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? No; "the sooner it is the better" -------------------- 9. Is the sales team involved in this request and do they have any additional input? No -------------------- 10. List any affected packages or components. pcs -------------------- 11. Would the customer be able to assist in testing this functionality if implemented? Yes
*** Bug 1281393 has been marked as a duplicate of this bug. ***
Hi, we can implement it for rhel9.4. However, there is not support in the backend for ban with autoclean, so it will be without that feature.
(In reply to Ivan Devat from comment #16) > Hi, > we can implement it for rhel9.4. However, there is not support in the > backend for ban with autoclean, so it will be without that feature. Ivan Devat++ Thanks for quick reply.