Over at HPC Admin, Douglas Eadline writes that adding and removing software from a running cluster is not as difficult as it used to be.
Regardless of the provisioning system, the goal is to make changes without having to reboot nodes. Not all changes can be made without booting nodes (i.e., changing the underlying provisioning); however, many application packages can be added or removed without too much trouble if some simple steps are taken.
Read the Full Story.
[SPONSORED GUEST ARTICLE] Think of the Microsoft Azure cloud platform as analogous to a general contractor who brings together the most skilled and knowledgeable artisans, technologically speaking, offering the latest and most powerful advanced AI capabilities. This would include the latest NVIDIA AI hardware….
The high-performance computing (HPC) market is witnessing a notable shift towards the cloud, partially driven by the benefits of enhanced energy efficiency. According to Hyperion Research nearly every organization running HPC workloads is either already using or investigating the cloud to accelerate application performance, with the cloud market for HPC workloads forecast to reach $11.5 […]
Featured RSS Feed More News from insideBIGDATA
I’ve got to say I’m a bit puzzled about this, I’ve been involved in HPC for almost 10 years now and I’ve never run a cluster where you’ve had to reboot a node after installing software. We just install software into:
/usr/local/$package-$compiler/$version
and then Modules (http://modules.sf.net/) to let users add/remove packages from their environment (and set up a default set for them of course).