Project

General

Profile

Actions
Copy link

User story #7340

closed

Relay promises to nodes using cfengine mission portal

Added by Nicolas CHARLES about 9 years ago. Updated almost 9 years ago.

Status:
Released
Priority:
N/A
Assignee:
Nicolas CHARLES
Category:
Server components
Target version:
3.2.0~beta1
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

The goal of this ticket is to create two new roles within Rudder:
  1. relay-promises-only: a relay that is simply relaying promises (no apache for inventory, nor any other fancy)
  2. cfengine-mission-portal: a role for the CFEngine Enterprise Mission Portal, to be able to identify this node (rather than using a group)

Techniques should be updated to include these roles, the roles should be added in the configuration file, and a migration script should be done as well

Subtasks 5 (0 open — 5 closed)

User story #7341: Update the Techniques for relay-promises-only and cfengine-mission-portalReleasedBenoît PECCATTE2015-11-12Actions
Bug #7400: Remove $() variables in cfengine codeReleasedNicolas CHARLES2015-11-12Actions
Bug #7431: A policy server that haven't got any node connected to it don't share the masterfiles server, which may prevent to have the first node connecting to itReleasedBenoît PECCATTE2015-11-22Actions
User story #7342: Adapt the logic in Rudder to handle the two new rolesReleasedFrançois ARMAND2015-10-30Actions
User story #7343: Create a migration script for relay-promises-only and cfengine-mission-portal parameter in the config fileReleasedBenoît PECCATTE2015-10-30Actions
Actions
Copy link

Also available in: Atom PDF