Feature #404
Foreman creates node when importing facts
| Status: | Closed | Start: | 10/12/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: |  Matt Moran |
% Done: | 0% |
|
| Category: | Importers | |||
| Target version: | - | |||
| Backlog: | No | Difficulity: | ||
| Votes: | 0 |
Description
Would be good to choose whether to create nodes or ignore nodes when foreman imports facts.
History
Updated by Ohad Levy over 1 year ago
- Target version set to 0.2
- Backlog set to No
how would you decided which host to import? or would you like to disable it completely?
Updated by Bash Shell over 1 year 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?
Updated by Ohad Levy over 1 year ago
- Status changed from New to Feedback
- Assigned to 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?
Updated by Matt Moran about 1 year ago
Hi Ohad,
How about a list in settings, say "Ignored Nodes" or similar. wild cards would be good -
servera.mydomain.local
*.compute.internal
Updated by Ohad Levy about 1 year ago
I think that the right way would be to let foreman delete the facts from the puppetmaster when deleting a host within foreman.
Updated by Ohad Levy 11 months 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#
