Rudder

2014-09-26

19:17 Bug #5573 (Pending technical review): Patch rudder-agent to have it understand SIGHUP to reload its promises

Jonathan CLARKE

16:11 Bug #5573: Patch rudder-agent to have it understand SIGHUP to reload its promises

(see also https://dev.cfengine.com/issues/6604) Nicolas CHARLES

16:11 Bug #5573: Patch rudder-agent to have it understand SIGHUP to reload its promises

https://github.com/Normation/rudder-packages/pull/490 Nicolas CHARLES

16:08 Bug #5573 (Released): Patch rudder-agent to have it understand SIGHUP to reload its promises

The server component of rudder-agent doesn't understand SIGHUP
The goal here is to implement support of sighup Nicolas CHARLES

19:14 Bug #5567: Initial promises use yum list installed to check installed package rather than rpm

Applied in changeset policy-templates:commit:28a86e3f7ccde8060c5f0a377475fbfb2f49c578. Jonathan CLARKE

19:14 Bug #5567 (Pending release): Initial promises use yum list installed to check installed package rather than rpm

Applied in changeset policy-templates:commit:fee9d1f1ad065aee79d93cf57cc6fa2dee9db34b. Nicolas CHARLES

19:13 Revision 28a86e3f (rudder-techniques): Merge pull request #510 from ncharles/bug_5567/initial_promises_use_yum

Fixes #5567: initial promises should not use yum list installed Jonathan CLARKE

19:07 User story #5580 (Released): Check the monotony of promises generation time on copy to nodes

Today, an agent trying to update its promises is checking promises_generated file to know if they have changed and ac... François ARMAND

18:56 User story #5579 (Released): Send reports from the agent to provide a heartbeat

That part take care of the implementation logic of what it means to have an heartbeat on the agent and accordingly se... François ARMAND

18:54 User story #5578 (Released): Heartbeat Rudder/technique integration

That part deals with what the UI give to store it in the backend and pass it correctly to promises when they are gene... François ARMAND

18:50 User story #5577 (Released): UI for configuring heartbeat by node

The UI that allows to configure heartbeat frequency by node.
The frequency really is configured for each node + o... François ARMAND

18:45 User story #5576 (Released): Add a heartbeat feature that force agent to periodically contact Rudder

With the changes only mode defined in #5293, we can imagine having nodes NEVER contacting Rudder because everything i... François ARMAND

18:40 User story #5572: Change management: Feature to group change requests by external change id

Thanks for all the precision, that make for a really nice user story. I can't commit any deadline for it because it s... François ARMAND

18:05 User story #5572: Change management: Feature to group change requests by external change id

"- that change request is seen as only one item by the validator, with all the modification (and all the diff) access... Florian Heigl

18:03 User story #5572: Change management: Feature to group change requests by external change id

I think it's likely there will be multiple people involved.
Possible interactions to toy around with:
x Team A ... Florian Heigl

17:55 User story #5572: Change management: Feature to group change requests by external change id

The full idea would be:
- when doing a modification on a group/directive/change, have to possibility to add it t... François ARMAND

17:18 User story #5572: Change management: Feature to group change requests by external change id

forgot this:
... but my concern was mostly making it safe for the change validator that he'll find all pieces th... Florian Heigl

17:17 User story #5572: Change management: Feature to group change requests by external change id

Hi,
understood correctly.
Re: 5472 it sounds as if they are similar and the risk of partial downloads there is im... Florian Heigl

17:11 User story #5572: Change management: Feature to group change requests by external change id

Hello,
Thanks for reporting.
I thing (if I understand correctly) that there is two part in your comment:
1... François ARMAND

12:46 User story #5572 (New): Change management: Feature to group change requests by external change id

One infrastructure change can translate into multiple policy changes inside rudder. It would be good if the person do... Florian Heigl

18:24 User story #662 (Rejected): Relay servers must transmit received inventories to the root server

This was fixed by #4023. Jonathan CLARKE

18:17 User story #1858: Relay server package

We discussed the specifications for this:
* Name: rudder-server-relay
* Conflicts: with rudder-server-root and ru... Jonathan CLARKE

18:09 Bug #5574: Have a configuration property to execute a post promise writing hook

https://github.com/Normation/rudder/pull/617 Nicolas CHARLES

18:07 Bug #5574: Have a configuration property to execute a post promise writing hook

Option is rudder.cfengine.reload.server.command
so that we know it is really for that, and nothing else Nicolas CHARLES

16:12 Bug #5574 (Released): Have a configuration property to execute a post promise writing hook

Once the promises have been written, we may need to execute a command (like, SIGHUP'ing cf-serverd to force it to rel... Nicolas CHARLES

17:49 Bug #5575 (Released): Upgrading rudder-inventory-ldap between two major OS versions makes slapd unable to operate because of BerkeleyDB

When an upgrade of Rudder is done after a major OS upgrade (that changes BerkeleyDB to a superior version), slapd ref... Matthieu CERDA

17:11 User story #5183: Make Rudder Apache 2.4 compliant

Matthieu CERDA

16:07 User story #5571: Permit the nodes access rules to be reloaded automatically after each promises generation (was Promises are reloaded by cf-serverd only every 5 minutes)

The idea here is to have the cf-serverd reload its promises when SIGHUP'ed
It need one modification in cf-serverd, o... Nicolas CHARLES

11:57 User story #5571 (Released): Permit the nodes access rules to be reloaded automatically after each promises generation (was Promises are reloaded by cf-serverd only every 5 minutes)

cf-serverd reloads its promises only every 5 minutes, so when we accept new nodes, we may have to wait up to 5 minute... Nicolas CHARLES

11:51 Bug #4557: Rule compliance shows red when it should be yellow

Yeah i already saw screenshots of the modernish bars. I like it a lot. Keep up the good work. :) Dennis Cabooter

11:23 Bug #4557: Rule compliance shows red when it should be yellow

That ticket can't really be addressed until we change the way we calculate and display compliance. This will be (and ... François ARMAND

11:21 User story #5256: Accepted nodes and techniques shared among relays

This can not be considered a bug, since this behaviour was never intended. In fact, quite the opposite: one of the ro... Jonathan CLARKE

11:10 User story #5359 (In progress): Add a logger to trace bootstrap action and clean them

The output is not clean for now. François ARMAND