On Tuesday, March 5, 2013 10:48:10 AM UTC-6, Schofield wrote:
Not really a specific problem because obviously people are successfully
using this pattern. I'm really trying to explore the difference between
the different patterns and understand why you would chose one over the
other.
If you want to be able to install multiple versions of some piece of
software, then you should obtain or create packages that allow it. For
example, RedHat-family JDK packages (java-version-openjdk) support this,
whereas Oracle's JDK packages for RedHat family systems do not.
Agreed,
On Friday, March 1, 2013 7:46:33 PM UTC-5, Brendan O'Bra wrote:
I use hiera to externalize the versions, like this:
package{'jdk':
ensure = hiera('jdk_version','present'),
require = [ YumRepo['someyumrepo'] ],
}
And then just deliver yaml based on
On Monday, March 4, 2013 10:42:32 AM UTC-6, Schofield wrote:
On Friday, March 1, 2013 7:46:33 PM UTC-5, Brendan O'Bra wrote:
I use hiera to externalize the versions, like this:
package{'jdk':
ensure = hiera('jdk_version','present'),
require = [ YumRepo['someyumrepo'] ],
}
I am curious to get the opinion of the community on how people successfully
manage software versions in their puppet modules. Personally I have
adopted the profile/role pattern and have the need to support many
different combinations of java based middleware. My puppet environment has
