Project

General

Profile

Feature #404

Foreman creates node when importing facts

Added by Matt Moran almost 9 years ago. Updated about 8 years ago.

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

Description

Would be good to choose whether to create nodes or ignore nodes when foreman imports facts.

History

#1 Updated by Ohad Levy almost 9 years ago

  • Target version set to 0.2

how would you decided which host to import? or would you like to disable it completely?

#2 Updated by Bash Shell over 8 years ago

It would be nice to add a Search feature which can search for hosts with no Hostgroup, or with no class.

This way, hosts imported by the Fact importer cron task can be detected.

Should I make another ticket for this?

#3 Updated by Ohad Levy over 8 years ago

  • Status changed from New to Feedback
  • Assignee changed from Ohad Levy to Matt Moran
  • Target version deleted (0.2)

So I'm still unclear of how to implement this feature... how would we decided what not to import?

#4 Updated by Matt Moran over 8 years ago

Hi Ohad,

How about a list in settings, say "Ignored Nodes" or similar. wild cards would be good -

servera.mydomain.local
*.compute.internal

#5 Updated by Ohad Levy over 8 years ago

I think that the right way would be to let foreman delete the facts from the puppetmaster when deleting a host within foreman.

#6 Updated by Ohad Levy about 8 years ago

note that is solved if you use [1] as your external nodes script

[1] - http://groups.google.com/group/foreman-users/browse_thread/thread/dbfacacaa6286014#

#7 Updated by Ohad Levy about 8 years ago

  • Status changed from Feedback to Closed

the new external nodes script in #347 now solves this issue.

Also available in: Atom PDF