Postscripts are the best solution to this problem. Encapsulating the installation procedure for a piece of software lends itself quite well to moving to a configuration management platform later (i.e. Chef, Puppet, or Ansible). It's also self documenting and atomic.
The downside is a lack of versioning in a CN build. In other words, which version of the postscript was used when node42 was imaged? There are ways to solve this problem of course, but they tend to make things more complex. > On 07/02/2020 9:00 PM Lachlan Musicman <data...@gmail.com> wrote: > > > Hola, > > We are installing Open On Demand which has a requirement of > websockify>0.8.0 which in turn has a python3 requirement. > > CentOS 7 (for eg) only packages an older version of python-websockify, > so we need to deploy manually. IE python3 /path/to/websockify/setup.py > install > > What's the recommended way to do this - do we create a software kit, > or a postscript, or just push it out with xdsh and add some > documentation to remind ourselves to update it when we update > underlying python? > > Cheers > L. > > > _______________________________________________ > xCAT-user mailing list > xCAT-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xcat-user _______________________________________________ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
