Bug 536214 (RHQ-589) - RFE: support "locking" configuration properties
Summary: RFE: support "locking" configuration properties
Keywords:
Status: NEW
Alias: RHQ-589
Product: RHQ Project
Classification: Other
Component: Configuration
Version: 1.0.1
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: John Mazzitelli
QA Contact:
URL: http://jira.rhq-project.org/browse/RH...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-17 22:37 UTC by Joseph Marques
Modified: 2024-03-04 13:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)
patch to introduce resource config remediation (30.62 KB, patch)
2010-08-24 17:13 UTC, John Mazzitelli
no flags Details | Diff

Description Joseph Marques 2008-06-17 22:37:00 UTC
support "locking" of resource configuration properties and plugin configuration properties.  once a property is marked locked, the JON Server will keep track of incoming changes.  if there is an attempt to make a change to a "locked" property, the JON Server will send a request back down to the agent to override the resourceConfig / pluginConfig as appropriate (with whatever value the locked properties were locked with, merged with the recent/previous update from the agent).

Comment 1 Greg Hinkle 2008-10-13 21:14:22 UTC
This is a pretty decent sized feature. Push to scoping process.

Comment 2 Red Hat Bugzilla 2009-11-10 21:12:30 UTC
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-589


Comment 3 Corey Welton 2010-08-12 19:52:45 UTC
Mazz, what would be required to get this in?

Comment 4 John Mazzitelli 2010-08-24 17:13:12 UTC
Created attachment 440703 [details]
patch to introduce resource config remediation

The attached patch is something I coded up in December of 2009 that performs resource configuration remeditation. When a configuration changes and the agent reports that change, the server can detect that a locked config changed and immediately tell the agent to revert the configuration back to what it was. I blogged (with a demo) this functionality here: http://management-platform.blogspot.com/2009/12/configuration-remediation.html

Comment 6 Jay Shaughnessy 2014-05-14 14:14:40 UTC
This could be useful if we get more into applying policy.

Comment 7 John Mazzitelli 2014-05-14 14:16:34 UTC
FYI: here's the demo of the prototype I wrote a long time ago:

https://docs.jboss.org/author/display/RHQ/Configuration+Freeze


Note You need to log in before you can comment on or make changes to this bug.