This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes

Bug 845401

Summary: Allow the modification of PropertyList configuration elements in group configuration page
Product: [Other] RHQ Project Reporter: Larry O'Leary <loleary>
Component: Configuration, Core UIAssignee: RHQ Project Maintainer <rhq-maint>
Status: NEW --- QA Contact: Mike Foley <mfoley>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.4CC: hrupp
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Larry O'Leary 2012-08-02 20:28:54 EDT
Description of problem:
If a user wants to view or update configuration for all members of a group, they see a message saying:

    List properties are not currently supported for group configurations.

This can be seen for properties such as Log Event Sources for a JBoss AS resource. It is expected that the properties should be editable and viewable within the JON UI. For example, for Log Event Sources:

Scenario 1:	
    Member 1:
        Enabled: false   Log File Path: /tmp/member1/logfile.log

    Member 2:
        Enabled: false   Log File Path: /tmp/member2/logfile.log

    Group View:
                         Enabled       Log File Path
    Log Event Sources     false     member values differ

Scenario 2:
    Member 1:
        Enabled: false   Log File Path: /tmp/member1/logfile.log
        Enabled: true   Log File Path: /tmp/member1/myotherLogFile.log

    Member 2:
        Enabled: false   Log File Path: /tmp/member2/logfile.log

    Group View:
                               Enabled               Log File Path
    Log Event Sources    member values differ     member values differ

When editing, each property in the property map should be treated uniquely. Thus allowing the user to enable all log event sources or disable them all.

The above example is simply that and should not be interpreted as the appropriate implementation. It simply shows what the user should be able to accomplish. Perhaps other properties won't work this way or simply won't make sense. Perhaps this should be exposed as a property option in the plug-in descriptor. Something to identify what is eligible for group view and/or group update. The Log Event Sources example demonstrates two issues:

  1) the user should be able to enable/disable log event sources at the resource group level

  2) the log event source log file path is expected to be different for all resources and it would not make sense for this field to be modifiable unless all members had the exact same value