On 14/01/17 01:20, Damir Krstic wrote: > So, my question is, does it make sense to continue with stateless > images, or would we be better served with statefull (installed on local > disk) images.
We started off stateful, but migrated to statelite a few years ago to get the best of both worlds. 1) no local HD's (increased reliability, HD failure was our biggest killer) 2) some way to have some state for things like GPFS, slurmd logs. We build libraries of osimages so we can drop back should we hit problems pretty seamlessly (needed a few times). No intention of going back to stateful here. cheers, Chris -- Christopher Samuel Senior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: [email protected] Phone: +61 (0)3 903 55545 http://www.vlsci.org.au/ http://twitter.com/vlsci ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
