Ticket #945 (closed defect: worksforme)

Opened 13 years ago

Last modified 10 years ago

Reporting feature addition

Reported by: Owned by: desai
Priority: major Milestone: Bcfg2 1.3.0 Release
Component: bcfg2-reports Version: 1.0
Keywords: Cc: [email protected]


In my environment, each SA have their own working copy of the bcfg2 repo where they make changes to and commit them after they are done. At 4pm everyday, the master bcfg2 repository (/var/lib/bcfg2) gets updated with all the changes that have been committed to the repo that day. Then from 5PM to 4AM (next day) the bcfg2 client runs on all servers and get their respective updates/config changes etc.

What I would like is to get a report of exactly what is going to change on each host and/or group of hosts (based on their profile) before the changes are actually applied on each server. That way, all admins have an idea of the changes that will be happening during the night. Plus this might help us detect a unintentional catastrophic change before it is actually applied to the servers.

Thanks, much. -pedro


Change History

comment:1 Changed 12 years ago by

Any updates on this request?

comment:2 Changed 12 years ago by solj

This can be accomplished by running the clients in dryrun mode and then using the reporting system functionality to determine what changes will be made.

comment:3 Changed 12 years ago by solj

  • Milestone changed from Bcfg2 1.2.0 Release to Bcfg2 1.3.0 Release

Pedro, were you able to get this working by running in dryrun mode?

comment:4 Changed 10 years ago by solj

  • Status changed from new to closed
  • Resolution set to worksforme

Closing for now. Feel free to reopen if you still have issues.

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.


Add a comment

Modify Ticket

Change Properties
<Author field>
as closed
The resolution will be deleted. Next status will be 'reopened'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.