Bug #2303
closed
The modification of the Distribute Policy PT have not been integrated in the rootServerInitialPromises
Description
As per http://www.rudder-project.org/redmine/issues/856, it would be great to report every modification within the rootServerInitialPromises
Updated by Jonathan CLARKE about 12 years ago
- Target version changed from 2.4.0~alpha6 to 2.4.0~alpha7
Updated by Jonathan CLARKE almost 12 years ago
- Target version changed from 2.4.0~alpha7 to 2.4.0~beta1
This needs clearing up.
Updated by Matthieu CERDA almost 12 years ago
- Status changed from New to Discussion
- Assignee changed from Matthieu CERDA to Nicolas CHARLES
I am a bit confused, in the title, it says "within the nodeInitialPromises" and in the description "within the rootServerInitialPromises"...
What should a I do ?????
- Report the main PT modifications in the nodeInitial ?
- Report the nodeInitial modifications in the rootServerInitial ?
Updated by Jonathan CLARKE almost 12 years ago
- Subject changed from The modification of the Distribute Policy PT have not been reported within the nodeInitialPromises to The modification of the Distribute Policy PT have not been integrated in the rootServerInitialPromises
- Status changed from Discussion to 2
- Assignee changed from Nicolas CHARLES to Matthieu CERDA
Matthieu CERDA wrote:
I am a bit confused, in the title, it says "within the nodeInitialPromises" and in the description "within the rootServerInitialPromises"...
What should a I do ?????
- Report the main PT modifications in the nodeInitial ?
- Report the nodeInitial modifications in the rootServerInitial ?
Well, the "Distribute Policy" PT is not in the node initial promises, so clearly, that was an error. Please integrate these changes in the rootServerInitialPromises.
The generated files from a running Rudder server (in /var/rudder/cfengine-community/inputs) should be as close as possible to the ones in the rootServerInitialPromises.
Updated by Matthieu CERDA almost 12 years ago
- Status changed from 2 to In progress
OK, this is in progress.
However, I strongly disagree with this approach: We are tremendously complicating our lives doing this sync. of the promises for two agent types (community and nova) when they will be replaced barely 5 minutes after the server installation by the regular promises set generated by Rudder after the initial reload...
We should keep these promises simple, even minimal, waiting for things to be settled by the Rudder server webapp. That would save us hours of pointless synchronization job.
Obviously, this is only valid for the server initial promises.
Updated by Matthieu CERDA almost 12 years ago
After a discussion between MCE, FAR and NCH, it a consensus has been found:
- Sync'ing promises is a time consuming task
- We do not want to do it every two weeks
Thus, we should find a way to automatize this. => See #2585
Updated by Matthieu CERDA almost 12 years ago
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
This task has been completed => http://www.rudder-project.org/redmine/projects/policy-templates/repository/revisions/bd5e0cbc88d91fb75ee19e2cc46d69834f894910
Updated by Nicolas CHARLES almost 12 years ago
This is valid, except the paths for the nova initial promises
Corrected in commit http://www.rudder-project.org/redmine/projects/policy-templates/repository/revisions/d96b7dd5d7d967894138fd7e14064c016c45ee7d
Updated by Jonathan CLARKE almost 12 years ago
All commits up to here look good to me.
But I've just made another commit to clean things up and make these promises easier to compare with generated ones. Nicolas, could you review this please?
Updated by Nicolas CHARLES almost 12 years ago
- Status changed from Pending technical review to Released
This looks valid, thank you all !