Feature #28: allow to have reusable configurations (snippets) across operating systems - Foreman

Actions

Copy link

Feature #28

closed

allow to have reusable configurations (snippets) across operating systems

Added by Matt Moran over 14 years ago. Updated over 14 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Ohad Levy

Category:

Unattended installations

Target version:

0.1-2

Difficulty:

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

It would be nice to manage the puppet config that gets deployed via kickstart as a template.

At the moment it is hidden away in def puppet_conf (./app/helpers/unattended_helper.rb)

Would be great if this was a template in ./config

Actions

Copy link

Updated by Ohad Levy over 14 years ago

hmm.. that could be done, but I was hoping to avoid it, the main reason would be that I can ensure that puppet gets started (hopefully the default settings are working for you), than you can do what ever you think is right for your setup through puppet.

may I ask what would you like to change? maybe we can improve the defaults.

Actions

Copy link

Updated by Matt Moran over 14 years ago

I think the defaults are pretty much okay. The issue I have is that I never feel the puppet daemon completely works reparsing the config file. For instance, after I built I got puppet to roll out a new conf with runinterval = 300. Puppet outputted "reparsing config" in the logs, and then polled once, but didn't poll again after that. There are already plenty on the mailing list that see the same issues.

Due to this i'd rather just have the option to roll out a correct config first time.

I think it would be cool to have puppet configs defined in the gui, and then just applied to servers. Similar to choosing the puppetmaster for a node.

Actions

Copy link