[Beowulf] Diskless Phi node installs?

Hearns, John john.hearns at mclaren.com
Tue May 7 01:40:52 PDT 2013



>> play games with symbolic links for other libraries.

> I'm going to play dumb here, but what's gamey about symlinks?
> (I'd probably just use a mount or bind-mount, but same effect.)


Nothing gamey about them really.
Just commenting that we have to use 'tricks' like that when the world view of the software developers
conflicts with what is on the ground in HPC systems.

As an aside, I note that Jason says /opt/intel/mic contains the networking information for the Phi 
and so has to be unique per-node.
Am I wrong in saying this should be somewhere in /etc/ if we are to ashere to the Linux FHS?

Actually, I am wrong, if I read the documentation:
http://www.tldp.org/LDP/Linux-Filesystem-Hierarchy/html/Linux-Filesystem-Hierarchy.html#opt

"Under no circumstances are other package files to exist outside the /opt, /var/opt, and /etc/opt hierarchies except for those package files that must reside in specific locations within the filesystem tree in order to function properly. For example, device lock files in /var/lock and devices in /dev."

Or maybe files like that should be installed in /etc/opt/mic
"Generally, all data required to support a package on a system must be present within /opt/'package', including files intended to be copied into /etc/opt/'package' and /var/opt/'package'"

So I THINK the RPM should run its post-install script and put the per-node customisation in /etc/opt/mic
Doesn't totally help with the cluster install though (I'm not that familiar with xCat)

The contents of this email are confidential and for the exclusive use of the intended recipient.  If you receive this email in error you should not copy it, retransmit it, use it or disclose its contents but should return it to the sender immediately and delete your copy.



More information about the Beowulf mailing list