Dr. Ed Morbius writes: > While you're considering providers, another case we encounter fairly > frequently are just general crap ISV or HW vendor-provided blob shell > installers. Usually a self-unpacking shell script, which may itself > include various internal packaging formats (tarballs, RPMs, etc.). > Dell, VMWare, Oracle, and others.
What we have done is to turn such blob installers into OS packages for installation via Puppet, rather than try to manage the direct installation of the blob installer via a convoluted set of execs and such. Overall it is still much easier to manage OS package installation, even with the overhead of having to create the custom package. So as one example, we get the blob into the Mock RPM build environment, unpack it, feed canned input to its configuration script, and then wrap up the finished file tree as an RPM, then get that RPM installed on the hosts that need it. > I haven't put deep thought into a puppet solution, but the generalized > method would be for the installer script / binary / ISO image, a > configuration script (or arbitrary shell arguments and ancillary file > list(s)), and some arbitrary post-installation test providing some level > of assurance that what you wanted to have installed was actually > installed. The thing is, RPM or DEB packages already do those things for you, so why go to so much effort to duplicate that functionality outside your package system? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
