Project

General

Profile

Actions

User story #8720

closed

User story #6733: Allow Node properties to be used in directives and ncf techniques

Generate a json file containing node properties for each node

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

Status:
Released
Priority:
2
Category:
Web - Config management
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

This is from Rudder web app point of view. We need to give the node everything so that he can work.

More preciselly, it means:
- for each node, create a JSON file that will be transfered to the node along with its policies,
- the file is: /var/rudder/share/123456-7890-xxxxx/rules/properties.d/node-properties.json
- the file contains a top level namespace ("node-properties"), and one key/value for each node property: { "node-properties" : { "key1": "value1", "key2": "value2" } }
- if the node doesn't have any properties, the file is generated and is { "node-properties" : {} }

Actions #1

Updated by François ARMAND over 7 years ago

  • Category set to Web - Config management
  • Assignee set to François ARMAND
  • Priority changed from N/A to 2
  • Target version set to 3.1.12
Actions #2

Updated by François ARMAND over 7 years ago

  • Status changed from New to In progress
Actions #3

Updated by François ARMAND over 7 years ago

  • Description updated (diff)
  • Status changed from In progress to New

It is better if all the json files are in a sub-repertory so that the parsing is a no brainer.
The directory name is just a proposed name.

Actions #4

Updated by François ARMAND over 7 years ago

  • Assignee changed from François ARMAND to Vincent MEMBRÉ
Actions #5

Updated by Vincent MEMBRÉ over 7 years ago

  • Status changed from New to In progress
Actions #6

Updated by Vincent MEMBRÉ over 7 years ago

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

Updated by François ARMAND over 7 years ago

  • Description updated (diff)

Shouldn't the name of the file be: 020-node-properties.json ?

Actions #8

Updated by Vincent MEMBRÉ over 7 years ago

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

Updated by Benoît PECCATTE over 7 years ago

Post-merge comment:

- yes the name would be better with a prefix since there are overriding rules for the properties based on an alphanumeric sort on the file names

- The file is /var/rudder/share/123456-7890-xxxxx/rules/cfengine-community/properties.d/node-properties.json and not /var/rudder/share/123456-7890-xxxxx/rules/properties.d/node-properties.json

Actions #10

Updated by Alexis Mousset over 7 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.12 and 3.2.5 which were released today.

Actions

Also available in: Atom PDF