Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1493087 - [gui] support custom instance and meta attributes and cluster properties
Summary: [gui] support custom instance and meta attributes and cluster properties
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-19 11:05 UTC by Tomas Jelinek
Modified: 2021-01-15 07:42 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-15 07:42:18 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Tomas Jelinek 2017-09-19 11:05:47 UTC 
Resource instance attributes and cluster properties are displayed in a form whose fields are defined in metadata. If there is an instance attribute or a cluster property in the CIB which is not defined by metadata then it is not displayed in gui at all.

In this situation, if a resource attribute or a cluster property gets renamed (i.e. deprecated and replaced by another attribute) in metadata, it gets lost in the gui. It is not even possible to display its value in order to copy it to the new attribute.

We plan to split cluster properties and instance attributes to tabs "basic", "advanced" and "expert". We should add another tab labeled "custom". This "custom" tab would display a simple key-value table to manage custom properties - basically the table which is now used for managing meta-attributes or utilization.
Comment 2 RHEL Program Management 2021-01-15 07:42:18 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.