Bug #2303

The modification of the Distribute Policy PT have not been integrated in the rootServerInitialPromises

Added by Nicolas CHARLES over 1 year ago. Updated 11 months ago.

Status:Released Start date:2012-02-17
Priority:3 Due date:
Assignee:Matthieu CERDA % Done:

100%
Category:Techniques - Sys & init promis
Target version:2.4.0~beta1
Needs translating:No Pull Request:

Description

As per http://www.rudder-project.org/redmine/issues/856, it would be great to report every modification within the rootServerInitialPromises

Associated revisions

Revision bd5e0cbc
Added by Matthieu CERDA 11 months ago

Fixes #2303: The initial promises for the root server were sync'ed with the regular Rudder technique tree

Revision d96b7dd5
Added by Nicolas CHARLES 11 months ago

Refs #2303 : correct the binary path for the nova initial promises

Revision 2c2ee4ec
Added by Jonathan CLARKE 11 months ago

Merge branch 'branches/rudder/2.4'

  • branches/rudder/2.4:
    Followup to previous merge: move policies to techniques
    Fixes #2600 Correct description problem in Directive Management
    Fixes #2255: The Rudder distributePolicy now checks that the apache configuration is secure
    Refs #2303 : correct the binary path for the nova initial promises
    Fixes #2488: Enabled the user to use processManagement without specifying an argument to the command used
    Fixes #2457: Fixed the fileManagement PT: Delete files matching the desired age when the operation is 'this file or directory only'
    Fixes #2303: The initial promises for the root server were sync'ed with the regular Rudder technique tree
    Fixes #2561 : the windows path in the repository don't mix well with cfengine community

Conflicts:
techniques/system/distributePolicy/1.0/metadata.xml

Revision a8abcd4e
Added by Jonathan CLARKE 11 months ago

More initial promise sync'ing and cleanup for root server initial promises. Refs #2303

Revision d5546da2
Added by Jonathan CLARKE 11 months ago

Merge branch 'branches/rudder/2.4'

  • branches/rudder/2.4:
    More initial promise sync'ing and cleanup for root server initial promises. Refs #2303
    Fixes #2599 : removing body uncompatible with our version of CFEngine
    Upgrade cfengine_stdlib.cf. Fixes #2599

Conflicts:
techniques/system/distributePolicy/1.0/apacheCheck.st

History

#1 Updated by Jonathan CLARKE about 1 year ago

  • Target version changed from 2.4.0~alpha6 to 2.4.0~alpha7

#2 Updated by Jonathan CLARKE about 1 year ago

  • Priority changed from 5 to 3

#3 Updated by Jonathan CLARKE 12 months ago

  • Target version changed from 2.4.0~alpha7 to 2.4.0~beta1

This needs clearing up.

#4 Updated by Matthieu CERDA 12 months 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 ?

#5 Updated by Jonathan CLARKE 12 months 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.

#6 Updated by Matthieu CERDA 11 months 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.

#7 Updated by Matthieu CERDA 11 months 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

#8 Updated by Matthieu CERDA 11 months ago

  • Status changed from In progress to Pending technical review
  • % Done changed from 0 to 100

#9 Updated by Nicolas CHARLES 11 months ago

#10 Updated by Jonathan CLARKE 11 months 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?

#11 Updated by Nicolas CHARLES 11 months ago

  • Status changed from Pending technical review to Released

This looks valid, thank you all !

Also available in: Atom PDF