jira.rhq-project.org has been archived and is now in read-only mode.

All issues have been moved to bugzilla.redhat.com. All new issues or updates to existing issues should be made through bugzilla.
Specific old RHQ issues can be found using a query of this form: https://bugzilla.redhat.com/show_bug.cgi?id=RHQ-1999.
New bugs can be raised here. Accounts at bugzilla.redhat.com have been created for existing RHQ users.
Open bugs raised in the last week can be found here.
Issue Details (XML | Word | Printable)

Key: RHQ-988
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Greg Hinkle
Reporter: Greg Hinkle
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
RHQ Project

Configuration changed detection

Created: 16/Oct/08 04:10 PM   Updated: 12/Jan/09 09:09 AM
Return to search
Component/s: FX - Configuration
Fix Version/s: 1.2

Time Tracking:
Original Estimate: 8 hours
Original Estimate - 8 hours
Remaining Estimate: 8 hours
Remaining Estimate - 8 hours
Time Spent: Not Specified
Remaining Estimate - 8 hours

Resolution Date: 16/Oct/08 04:17 PM
Date of First Response: 12/Jan/09 09:09 AM
Tester: Corey Welton
VCS Revision: 1,769


 Description  « Hide
This is a system for the agent to watch the configurations of resources inventory, notifying the server when changes are detected. This will provide a full historical audit for configurations including those that happen directly on the remote resource. This means the server will always know when a user goes and edits the config on disk. This will need to be done via a polling mechanism.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Greg Hinkle made changes - 16/Oct/08 04:10 PM
Field Original Value New Value
Status Open [ 1 ] Accepted [ 10001 ]
Greg Hinkle made changes - 16/Oct/08 04:10 PM
Status Accepted [ 10001 ] In Progress [ 3 ]
[ Permalink | « Hide ]
Greg Hinkle added a comment - 16/Oct/08 04:17 PM
Implemented as a polling solution in the configuration manager. The default settings are to start discovery 5 minutes after agent startup. We run the discovery on a default period of 1 hour. We won't run this detection when not in the agent (i.e. in the embedded PC scenario)

This can be tested by taking an existing resource in inventory and changing its underlying config file and waiting to see the change detected in at most 1 hour. (e.g. changing a config in a datasource) You should see a new copy of the config in the history for that resource.

Greg Hinkle made changes - 16/Oct/08 04:17 PM
Status In Progress [ 3 ] Resolved [ 5 ]
VCS Revision 1769
Resolution Fixed [ 1 ]
Jeff Weiss made changes - 08/Dec/08 07:30 AM
Status Resolved [ 5 ] Integrated [ 10002 ]
Corey Welton made changes - 10/Dec/08 10:16 PM
Tester cwelton
[ Permalink | « Hide ]
Jeff Weiss added a comment - 12/Jan/09 09:09 AM
Both corey and I have tested this and it looks good. Note -

> setconfig rhq.agent.plugins.configuration-discovery.period-secs=60

on the agent command line will make testing a LOT faster, you don't have to wait 1 hour to see if the change is detected. Or you can update this param in the agent config via the UI as well.

rev2561

Jeff Weiss made changes - 12/Jan/09 09:09 AM
Status Integrated [ 10002 ] Closed [ 6 ]
Jeff Weiss made changes - 29/Jan/09 09:20 AM
Workflow RHQ workflow r12 [ 15259 ] RHQ workflow r13 [ 16762 ]

Powered by a free Atlassian JIRA open source license for Hyperic HQ. Try JIRA - bug tracking software for your team.
Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13.5-#360) - Bug/feature request - Atlassian news - Contact Administrators