Project

General

Profile

Actions
Copy link

User story #5025

closed

User story #4928: Allow splitting Rudder into independent role-based entities

Update the rudder-rsyslog configuration and send inventory target to send syslog message and inventory to the proper component

Added by Nicolas CHARLES almost 11 years ago. Updated about 10 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Jonathan CLARKE
Category:
System techniques
Target version:
2.11.0~beta1
Pull Request:
https://github.com/Normation/rudder-t...
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

In the splitted architecture, the inventory should go to the rudder-inventory-endpoint defined, and the reports should go to the rudder-reports

The Technique server-roles defines which are these components, so we need to extract the information from it, and use it for rsyslog configuration and inventory sending

Subtasks 3 (0 open — 3 closed)

Bug #5029: Error when the webabb reloads Techniques from #5025RejectedNicolas CHARLES2014-06-15Actions
Bug #5030: Invalid promises generated for distributePolicy as of #5025ReleasedNicolas CHARLES2014-06-15Actions
Bug #5033: Role for the reports server is invalid in the technique, it should be rudder-reports, and not rudder-dbRejectedNicolas CHARLES2014-06-15Actions

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #5117: Promises generated generated for server roles are not correct and are missing from initial promisesReleasedJonathan CLARKE2014-06-23Actions
Actions
Copy link
 #1

Updated by Nicolas CHARLES almost 11 years ago

Part of this is to move the rsyslog configuration from the Technique DistributePolicy to server-roles

Actions
Copy link
 #2

Updated by Nicolas CHARLES almost 11 years ago

Nicolas CHARLES wrote:

Part of this is to move the rsyslog configuration from the Technique DistributePolicy to server-roles

hum, actually no. I'm a bit too tired to think properly

Actions
Copy link
 #3

Updated by Nicolas CHARLES almost 11 years ago

  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/413

PR for work in progress (don't merge)
https://github.com/Normation/rudder-techniques/pull/413

Actions
Copy link
 #4

Updated by Nicolas CHARLES almost 11 years ago

  • Status changed from New to Discussion
  • Assignee changed from Nicolas CHARLES to Jonathan CLARKE

Jon,

I think I made everything, can you review ? I feel I miss something, but don't know what
Side topic: I don't know how it should be reflected in initial promises

Actions
Copy link
 #5

Updated by Nicolas CHARLES almost 11 years ago

  • Status changed from Discussion to Pending technical review

PR has been updated

Actions
Copy link
 #6

Updated by Nicolas CHARLES almost 11 years ago

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

Applied in changeset policy-templates:commit:66afa7035462007b9aaa03276f9eabf734885d41.

Actions
Copy link
 #7

Updated by Vincent MEMBRÉ almost 11 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.0~beta1 that was released yesterday.

Actions
Copy link
 #8

Updated by Benoît PECCATTE about 10 years ago

  • Tracker changed from Enhancement to User story
Actions
Copy link

Also available in: Atom PDF