Bug 1578667

Summary: [GUI][RFE] Add resource move and ban commands to PCSD web UI
Product: Red Hat Enterprise Linux 9 Reporter: Reid Wahl <nwahl>
Component: pcsAssignee: Ivan Devat <idevat>
Status: CLOSED MIGRATED QA Contact: cluster-qe <cluster-qe>
Severity: medium Docs Contact:
Priority: medium    
Version: 9.0CC: cluster-maint, hbiswas, idevat, mlisik, mpospisi, nhostako, omular, sanyadav, sbradley, tojeline
Target Milestone: rcKeywords: FutureFeature, MigratedToJIRA, Triaged
Target Release: 9.4Flags: pm-rhel: mirror+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-22 18:32:42 UTC Type: Story
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Reid Wahl 2018-05-16 06:31:40 UTC
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

Comment 4 Tomas Jelinek 2018-05-16 07:15:43 UTC
*** Bug 1281393 has been marked as a duplicate of this bug. ***

Comment 16 Ivan Devat 2023-07-17 07:10:29 UTC
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.

Comment 17 Sandeep Yadav 2023-07-17 08:43:17 UTC
(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.

Comment 19 RHEL Program Management 2023-09-22 18:16:25 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 20 RHEL Program Management 2023-09-22 18:32:42 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.