Thread: Several SymDE clusters in the same physical clusters, using same binaries on NFS

Let's assume I have a linux cluster of 30 machines, and an NFS drive on which I installed SymDE. So far so good, I have vem_resource.conf on all machines.

Now imagine I want to split that cluster in two (2) distinct symde cluster.
Somehow I manage to rewrite the 2 corresponding different vem_resource.conf files.
Assumption is that I'm always using the NFS drive to get the binaries.

My question is: what do I do with my vem_resource.conf files ?
--> If I replace the one on NFS, only one of the DE clusters will work.
Solution seems to create separate directories for each vem_resource.conf, and then modify SOAM_HOME on each machine to point on these BUT I'm not sure that soamstartup will retrieve the binaries
So next question is: how does soamstartup retrieve vem_resource_conf and the binaries ? local dir first, then path ?

Hi Guillaume,

Thanks for the great question. Symphony DE finds commands on Linux by using the current PATH which should be set correctly by using the source command. It figures out what commands to run from the vem_resource.conf.

SD_SDK :15051:localhost:sd

In the above line, the binary name is the last colon delimited string. In this case sd.

Symphony DE determines the start directory by concatenating $SOAM_HOME and the string "work", i.e. if your $SOAM_HOME is /shared/symde, then the start directory would be /shared/symde/work.

-----

To split your shared clusters, you need to create a new subdirectory on your NFS partition and install a new copy of Sym DE. You then need to go to each host in the new cluster and re-source the environment with the cshrc in the new installation directory and then run soamstartup.

If you want a short-cut, you can share the binaries in one location, i.e., instead of installing another copy of Symphony, you can just copy the /conf and /work directories into a new directory - new SOAM_HOME, and just change SOAM_HOME manually on each machine to point to new SOAM_HOME. On a freshly booted host, you have to source the env using the old cshrc and then set SOAM_HOME manually afterwards.

- Ajith