java_ark "jdk" do
url 'http://download.oracle.com/otn-pub/java/jdk/6u29-b11/jdk-6u29-linux-x64.bin'
checksum 'a8603fa62045ce2164b26f7c04859cd548ffe0e33bfc979d9fa73df42e3b3365'
app_home '/usr/local/java/default'
bin_cmds ["java", "javac"]
action :install
end
serve the tar ball via file resource or remote file resource,( specify checksum to make it idempotent), notify an un-tar execute resource from the earlier file/remote file resource. you should not check for individual file content/permission check if the number of files are in thousands. You might want to use tar against the uncompressed directory and then verify the checksum .On Fri, Jan 20, 2012 at 8:01 PM, Bryan Berry < " target="_blank"> > wrote:I created the java_ark lwrp exactly for this use case. While it is in the java cookbook, it is not actually specific to javahttps://github.com/bryanwb/cookbooks/blob/master/java/README.md
On Fri, Jan 20, 2012 at 3:28 PM, Van Fossan,Randy < " target="_blank"> > wrote:How is the best way to handle installations from tarballs? Currently, we have several tarballs that we use to deploy software. These tarballs are just extracted to the correct directory and the software is installed.
I want the software installation to be idempotent and not have the recipe do any more work than necessary. I also want the recipe to replace a file that may have been overwritten by someone or some other process. I do not want to have to extract the tarball on every run . I considered extracting the tarball into the file portion of the cookbook, but it is in many cases several thousand files that is in these tarballs.
Anyone have any ideas?
Randy
Archive powered by MHonArc 2.6.16.