Jira (PUP-2947) Add a setting for second level environment (tier)

[Javier Palacios (JIRA)]

Title: Message Title










 

 Javier Palacios created an issue


















 Puppet /  PUP-2947



  Add a setting for second level environment (tier) 










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 17/Jul/14 11:16 AM




Priority:

  Normal




Reporter:

 Javier Palacios










In some environments it could be useful to have two simultaneous environment-alike variables to choose the manifests for a node. The use case is taken from the company I've just started to work for.
We develop a complex application that is offered also by multiple partners (so, multiple simultaneous versions). That means that we have multiple qa/pre/prod sets, and as not every set run the same software version, thus potentially different module versions (mainly for our own apps), and we miss a finer grained grouping.
Although we could use prod_partner as environment, it forces to get multiple copies of the same module+version, with overhead on puppet master management side. In this context I see really useful the tier setting, with a a module path like '$confdir/$environment/$tier/modules'.
I've tried this with a simple approach with the new setting and basic tests(on https://github.com/javiplx/puppet/pull/3), although I have no real idea how could I extend the tests to parts like directory based environments nor how it could impact on other puppet areas.












   

 Add Comment

Jira (PUP-2947) Add a setting for second level environment (tier)

[Javier Palacios (JIRA)]

Title: Message Title










 

 Javier Palacios commented on an issue


















  Re: Add a setting for second level environment (tier) 










You were right supposing that I pretended to sent tier from agent to master. Actually, I see that setting as only suitable for the [agent] section.
I now that the prod_partner can solve my problem, but I would like not to get the overhead. More than 90% of the puppet modules/code is actually common to all prod or can be managed with hiera without big problems (that's even true for the qa/pre/prod sets).












   

 Add Comment

























 Puppet /  PUP-2947



  Add a setting for second level environment (tier) 







 In some environments it could be useful to have two simultaneous environment-alike variables to choose the manifests for a node. The use case is taken from the company I've just started to work for.   We develop a complex application that is offered also by multiple partners (so, multiple simultaneous versions). That means that we have multiple qa/pre/pr...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe