This is rather unfortunate. The only way that I can think of is to change the deb/rpm package and serve that on your own.
We are using cassandra on some deployment too but force JAVA_HOME explicitly in configuration files to the oracle jdk -- Nikola On Wed, Jul 24, 2013 at 02:29:44PM -0700, Paul Pham wrote: > Hello, puppet n00b here. > > Trying to install cassandra via puppet. Works great, only caveat is > cassandra (dsc12 package) lists openjdk as a dependency. Ironically enough, > the datastax guys themselves recommend using Oracle JRE instead of openjdk, > and there is even a bug > <https://bugzilla.redhat.com/show_bug.cgi?id=907485>that prevents cassandra > from starting if it's using openjdk. Anyway, I > fixed it by adding an exec to my puppet-java module that sets the Oracle > JRE runtime as the defaults via alternatives, and it works fine. However, I > still end up with two different java runtimes installed which I find to be > a bit unclean. > > The root of the problem to me, though, is that by having puppet install > dsc12, I lose visibility into what all those dependencies were that got > installed along with it (I didn't realize openjdk was even installing until > I started investigating why cassandra wasn't starting). So what I'd prefer > to do is add each individual package dependency into my cassandra module > itself, thereby explicitly installing only what I intend to install, and > nothing else. > > The only way this works, though, is if I can somehow pass the "--nodeps" > option into yum during puppet apply time. Otherwise, regardless of whether > I already installed Oracle JRE, using yum to install dsc12 will > automatically install openjdk. > > > > How have you guys handled scenarios like this? I tried searching through > the topics here for "yum nodeps" but it seems people found different ways > of solving their individual problems rather than sending flags to the yum > provider itself. I also noticed this puppet feature > request<https://projects.puppetlabs.com/issues/4976>which unfortunately has > remained open(?) for 3 years. I've also seen people > suggest that nodeps should never be used with yum since the purpose of yum > is to handle dependencies... but we also like some of the other features of > yum, like being able to pull packages down by name automatically from our > yum repo (which we manage in-house). > > Anyway, any insights would be great! Thanks, > Paul > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
