Project

General

Profile

Feature #86

Support for default node when using external nodes

Added by Martin Englund over 9 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Category:
External Nodes
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

It should be possible to define a default node which is returned when there is no exact match.

History

#1 Updated by Ohad Levy over 9 years ago

  • Status changed from New to Feedback
  • Assignee changed from Ohad Levy to Martin Englund

It doesn't make a lot of sense to enable it when Foreman is used as an unattended service(and puppetca), I think that it should be enabled only if you disable the unattended part.

How would you define the default node? what would be the class? would you select it from the list of classes, or would it be hard coded somewhere (e.g. in the settings.yaml file)?

In general, I see it as a bad practice having "unmanaged nodes" and the main goal with Foreman is to automate the whole process in a way that your nodes are always manageable.

#2 Updated by Martin Englund over 9 years ago

  • Status changed from Feedback to Closed

The reason for having a default node is to get some basic configuration done while the system is waiting for a full config through foreman.

I have found a workaround which is usable:
just define the default node in the site.pp file

Also available in: Atom PDF