Project

General

Profile

Actions

User story #9710

closed

User story #9707: Add a Relay API: share files between nodes, launch run on remote run behind relay

Generate a file in relays promises that contain the map of nodes and relays below it

Added by Alexis Mousset over 7 years ago. Updated about 7 years ago.

Status:
Released
Priority:
N/A
Category:
System techniques
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

We need a list containing:

  • hostname
  • ip
  • public key
  • policy server

of all nodes and relays below a given policy server.

Actions #1

Updated by Alexis Mousset over 7 years ago

{
    "uuid1": {
        "hostname": "host1",
        "key-hash": "key1" 
    },
    "uuid2": {
        "hostname": "host2",
        "key-hash": "key2" 
    },
    "uuid3": {
        "hostname": "host3",
        "key-hash": "key3",
        "next-hop": "uuid2" 
    },
    "uuid4": {
        "hostname": "host4",
        "key-hash": "key4",
        "next-hop": "myuuid" 
    }
}
Actions #2

Updated by Alexis Mousset over 7 years ago

  • Subject changed from Generate a file in relay spromises that contain the map of nodes and relays below it to Generate a file in relays promises that contain the map of nodes and relays below it

The structure should be:

{
    "uuid1": {
        "hostname": "host1",
        "key-hash": "key1",
        "policy-server": "9b25d384-a0ed-4ac1-adf2-b5b0277a455d" 
    },
    "uuid2": {
        "hostname": "host2",
        "key-hash": "key2",
        "policy-server": "9b25d384-a0ed-4ac1-adf2-b5b0277a455d" 
    },
    "uuid3": {
        "hostname": "host3",
        "key-hash": "key3",
        "policy-server": "uuid2" 
    },
    "uuid4": {
        "hostname": "host4",
        "key-hash": "key4",
        "policy-server": "uuid3" 
    }
}
Actions #3

Updated by Janos Mattyasovszky over 7 years ago

Could you eventually generate something, that can be used to have all paths of policies that have to exist for a relay?

I mean if you generate also an array like:

[ 
 "bbefcbab-e08f-4091-a0bc-581aaa6077a7/share/a3437bc2-7cc4-42b7-941c-31c5f26c30e5",
 "bbefcbab-e08f-4091-a0bc-581aaa6077a7/share/a3437bc2-7cc4-42b7-941c-31c5f26c30e5/share/57765741-664e-4e93-994d-3c5f52de1e27",
]

That would allow the implementation of a solution for #4709 and #7288.

Actions #4

Updated by Benoît PECCATTE over 7 years ago

  • Status changed from New to In progress
  • Assignee set to Benoît PECCATTE
Actions #5

Updated by Benoît PECCATTE over 7 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Alexis Mousset
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/1085
Actions #6

Updated by Benoît PECCATTE over 7 years ago

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

Updated by Vincent MEMBRÉ about 7 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.0 which was released today.

Actions

Also available in: Atom PDF