Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Making changes to templates #66

Open
uojiaku opened this issue Jul 12, 2017 · 2 comments
Open

Making changes to templates #66

uojiaku opened this issue Jul 12, 2017 · 2 comments

Comments

@uojiaku
Copy link

uojiaku commented Jul 12, 2017

Hi,

I am trying to add changes to the templates from hiera. For instance these files (10_security.config.erb and condor_config.local.erb) appear in my /etc/condor/config.d dir but how do I modify them from hiera? Also I am trying to add gangliad and then configure '23_ganglia.config.erb' with hiera too.

Thanks in advance,

Uche

@ccnifo
Copy link
Collaborator

ccnifo commented Nov 14, 2017

I would also need some more flexibility in the templates to achieve my target config. After looking at the templates, I saw it cannot be through modifying hiera values.

I see at least 2 possibilities:

  • Modifying the templates to integrate more params and conditionnals. That's the cleaner, but also the harder and less flexible way.
  • Giving the possibility to add new files in /etc/condor/config.d , which would be read by condor after the others, thus offering the possibility to redefine parameters.

It seems to me that going for both solutions can be a good idea, even though the first method should always be prefered.

@kreczko
Copy link
Member

kreczko commented Nov 14, 2017

@ccnifo The latter ("possibility to add new files in /etc/condor/config.d") is indeed what we do locally, see
worker example manifest.

We also use hiera to fill the parameters (see htcondor_worker.yaml and node-example.yaml).

This solution allows for customisation while reducing feature-creep in the main package.
I was also thinking of a way to add any parameter to a custom config part (issue #57) but never got around to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants