Project

General

Profile

Actions

Architecture #10823

closed

Select system techniques and generate correct policies based on agent type

Added by François ARMAND almost 7 years ago. Updated almost 7 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Effort required:
Name check:
Fix check:
Regression:

Description

We are addding a new kind of agent with totally different system techniques (policy generation input) and policy file format (policy generation output).

So we need to be able to configure the generation process based on the agent type (and have one generation pipeline for system technique for each agent type).


Subtasks 1 (0 open1 closed)

Architecture #10842: Update write test for 4.1 and add generation for a nodeReleasedVincent MEMBRÉActions
Actions #3

Updated by François ARMAND almost 7 years ago

For now, the ouput is:

% tree test-rudder-config-repo-2017-06-02T18:51:26.621+02:00/share-dsc-node/c8813416-316f-4307-9b6a-ca9c109a9fb0
test-rudder-config-repo-2017-06-02T18:51:26.621+02:00/share-dsc-node/c8813416-316f-4307-9b6a-ca9c109a9fb0
└── rules
    └── dsc
        ├── Create_file
        │   └── 1.0
        │       ├── Create_file.cf
        │       └── rudder_reporting.cf
        ├── dsc-agent
        │   └── 1.0
        │       └── some-resource.conf
        ├── properties.d
        │   └── properties.json
        ├── rudder_expected_reports.csv
        └── rudder.ps1

7 directories, 6 files

Given the "dsc-agent" technique here: https://github.com/fanf/rudder/commit/cedf9f23e2a74892c5a520d9c36726a6ea90cd00

Actions #4

Updated by François ARMAND almost 7 years ago

You can test with:

mvn -Dtests.clean.tmp=false test -Dtest=WriteSystemTechniquesTest

The test will fail, but it will create output in: /tmp/test-rudder-config-repo-2017-06-02T18:51:26.621+02:00/share-dsc-node/c8813416-316f-4307-9b6a-ca9c109a9fb0 (with of course correct date).

Actions #5

Updated by François ARMAND almost 7 years ago

Now, need to:

  • remove rudder_expected_reports.csv
  • generate system parameter file
  • generate equiv of rudder-directive.cf and rudder-system-directive.cf (if needed for the second)
  • add an example of one technique with both .cf and .ps1 resource, corresponding metadata.xml, and output the correct result
Actions #7

Updated by François ARMAND almost 7 years ago

Started to do some filtering, with the current wip we have:

% tree /tmp/test-rudder-config-repo-2017-06-08T18:58:04.135+02:00/share-dsc-node/c8813416-316f-4307-9b6a-ca9c109a9fb0/rules/dsc
/tmp/test-rudder-config-repo-2017-06-08T18:58:04.135+02:00/share-dsc-node/c8813416-316f-4307-9b6a-ca9c109a9fb0/rules/dsc
├── Create_file
│   └── 1.0
│       ├── Create_file.cf
│       └── rudder_reporting.cf
├── dsc-agent
│   └── 1.0
│       └── some-resource.conf
├── properties.d
│   └── properties.json
├── rudder.json
└── rudder.ps1

5 directories, 6 files

So:

  • no more expected_reports.csv for DSC agent,
  • but a rudder.json file for them.
Actions #10

Updated by François ARMAND almost 7 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/1667
Actions #11

Updated by François ARMAND almost 7 years ago

  • Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
Actions #12

Updated by François ARMAND almost 7 years ago

  • Assignee changed from Nicolas CHARLES to Vincent MEMBRÉ
Actions #13

Updated by François ARMAND almost 7 years ago

  • Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
Actions #14

Updated by François ARMAND almost 7 years ago

  • Assignee changed from Nicolas CHARLES to Vincent MEMBRÉ
Actions #15

Updated by François ARMAND almost 7 years ago

  • Status changed from Pending technical review to Pending release
Actions #16

Updated by Alexis Mousset almost 7 years ago

  • Target version changed from 4.2.0~prototype to 4.2.0~beta1
Actions #17

Updated by Alexis Mousset almost 7 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.2.0~beta1 which was released today.

Actions

Also available in: Atom PDF