I had a user ask for Java to be installed on the cluster systems, so I started up by making a simple JRE5 module for puppet, but this first one didn’t quite work:<\/p>\n
\nclass jre5 {\n package { \"sun-java5-jre\":\n ensure => latest;\n }\n}\n<\/pre>\nIt doesn’t work because Sun wants you to agree to its license before installing the JRE. There’s a couple of ways around this. First, the old-school method:<\/p>\n
\nssh host \"yes | apt-get -y install sun-java5-jre\"\n<\/pre>\nwhere ‘yes’ is a standard Unix program that just prints out “yes” over and over until the program on the other side of the pipe terminates. But “ssh host foo” is not the way of the managed infrastructure. <\/p>\n
The second method, much more friendly to centralized management, is to first install debconf-utils on a candidate system, and then install sun-java5-jre on the same system. Once that’s done, you can query the debconf database to see how it stored your answers to the Sun license agreement:<\/p>\n
\nch226-12:~# debconf-get-selections | grep sun-\nsun-java5-bin shared\/accepted-sun-dlj-v1-1 boolean true\nsun-java5-jre shared\/accepted-sun-dlj-v1-1 boolean true\nsun-java5-jre sun-java5-jre\/jcepolicy note\nsun-java5-jre sun-java5-jre\/stopthread boolean true\nsun-java5-bin shared\/error-sun-dlj-v1-1 error\nsun-java5-jre shared\/error-sun-dlj-v1-1 error\nsun-java5-bin shared\/present-sun-dlj-v1-1 note\nsun-java5-jre shared\/present-sun-dlj-v1-1 note\n<\/pre>\nSave those results (debconf seeds) into a file on the gold server. Then we can modify our jre5 class as follows:<\/p>\n
\nclass jre5 {\n package { \"sun-java5-jre\":\n require => File[\"\/var\/cache\/debconf\/jre5.seeds\"],\n responsefile => \"\/var\/cache\/debconf\/jre5.seeds\",\n ensure => latest;\n }\n\n file { \"\/var\/cache\/debconf\/jre5.seeds\":\n source => \"puppet:\/\/\/jre5\/jre5.seeds\",\n ensure => present;\n }\n}\n<\/pre>\nNow our class will download the preseeded answers for the Java license, download and install the JRE, and then use the preseeded answers to skip past the license agreement. I had never messed with debconf seeding previously, since I had either just imaged my systems, or provided config files that would be used when I restarted any daemons or programs that depended on those files. Now debconf-utils is part of my standard system class definition.<\/p>\n
Note that this method doesn’t work with the default puppet provided in Debian Etch (version 0.20) — the responsefile parameter for Debian packages was only added in puppet 0.22.<\/p>\n","protected":false},"excerpt":{"rendered":"
I had a user ask for Java to be installed on the cluster systems, so I started up by making a simple JRE5 module for puppet, but this first one didn’t quite work: class jre5 { package { “sun-java5-jre”: ensure => latest; } } It doesn’t work because Sun wants you to agree to its … <\/p>\n