Project

General

Profile

Actions

User story #4024

closed

User story #4023: Implement Relay Server within Rudder

Have the promises of servers in the correct location when we use relay server

Added by Nicolas CHARLES over 10 years ago. Updated almost 9 years ago.

Status:
Released
Priority:
2
Category:
Server components
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

For relay servers to be usable the most easily, we must generate the promises in the correct location
The organisation is, for the config root - root policy server, and relay - relay policy server, and node1 under root, and node2 under relay, the following paths

/var/rudder/share/node1/rules
/var/rudder/share/relay/rules
/var/rudder/share/relay/share/node2

Hence relay will propagate share from /var/rudder/share/relay/ on root to /var/rudder/share on relay

Actions #1

Updated by Nicolas CHARLES over 10 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/330
Actions #2

Updated by François ARMAND over 10 years ago

  • Status changed from Pending technical review to 12

RT OK, merge pending (not done to be able synchronise each parts).

Actions #3

Updated by Nicolas CHARLES over 10 years ago

  • Status changed from 12 to Pending release
  • % Done changed from 0 to 100
Actions #5

Updated by Vincent MEMBRÉ over 10 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.8.0~beta1, which was released today.
Check out:

Actions #6

Updated by Benoît PECCATTE almost 9 years ago

  • Tracker changed from Enhancement to User story
Actions

Also available in: Atom PDF