SAS Grid Installation Query and Plan file generation query

[start4mzero]

We are about to install SASHome/SASBinaries in SAS Metadata Server , Grid control and Grid nodes and Middle tier Servers . There is a mount called /SASHOME is mounted in all metadata , grid control , grid node and middle tier servers . We use shared (nfs) mountpoints for
storing the SASBinaries and SAS Configurations .

1. Our doubts is one time installation of SASBinaries/SASHome is sufficient or we need to install SAS Binaries and every time for each servers ( meta , grid control , grid node , midtier ) on the SASHOME mount?
2. how do we plan the plan file(plan.xml) for this type of installation from planapp

[JuanS_OCS]

Hi @start4mzero ,

these kind of decisions should not be done at deployment time, but during the architecture sessions.
There are many variables involved.

For example, the fact that you are using NFS, instead of an Distributed Shared File System (DFS) has many implications for the questions you are posting. How will NFS will handle it? Files/blocks locking? Performance? Limitations of NFS (based on version and platform used)?

In general, and just to answer to your questions, very generally - but please mind my previous comment(s):

1- 1 time shared binaries /sashome should be enough. In all tiers. However I have no clue how your NFS will behave with such dependency. MIght create serious issues when you reach Production workloads. I suggest thorough testing and validation, and risk management.

2- I don't expect, by default, differences in the plan file. But of course all depends on architectural decisions

[start4mzero]

Hi @JuanS_OCS 

Thanks for your response .

I agree that this need to be discussed during Architectural decisions .

NFS cluster will hold the SAS Binaries , which will be mounted on SASMETADATA, GRIDCONTROL, GRIDNODES,MIDDLETIER nodes . Which will acts as the single SAS Binaries to be consumed for execution of SAS Programs across each nodes . Performance will be tested after the deployment.

1. Thank you once again for confirming that sharing SAS binaries one time is enough . If not NFS , are you saying SASBINARIES/SASHOME should be placed in DFS instead of NFS for performance reasons ?
2.Need to create a plan file based on architecture / server topology ?

[JuanS_OCS · Accepted solution]

Hi @start4mzero ,

I am now a little confused by what you are proposing/intending to achieve, or I might not be understanding well.

To clarify my previous comment:

- while /home binaries could potentially be in NFS, not all under a single same /sashome folder. You still want different NFS filesystem per SAS layer (eg /sashome/meta, /sashome/comp & /sashome/web)

- NFS might be suitable, but depends a lot of your configuration. A SAS tested DFS is definetely more recommended.

https://communities.sas.com/t5/SAS-Communities-Library/Contemplating-shared-file-systems-for-SAS/ta-...

https://support.sas.com/resources/papers/proceedings17/SAS0569-2017.pdf

- you always need to prepare a plan file, custom to your designed deployment. However, if you follow above, there should not be a lot to customize.

A last note, in terms of recommendations:

---

Not for Sharing SAS 9.4 Deployment Files Across Meta and Middle Tiers:

• The section above mentioned using a shared file system to host SAS 9.4 deployment files (software and configuration) for the SAS 9.4 compute tier software
• However, the SAS 9.4 meta and middle tiers follow a different availability paradigm. We prefer that each host for the meta and middle tiers have their own local SAS software and configuration files
• And even more importantly, never direct the SAS 9.4 Deployment Wizard to install one tier's software and configuration into the same physical directories for a different tier. In that way lies madness. 

[start4mzero]

Hi @JuanS_OCS 

Thanks for the clear write up . The paper you have tagged is very useful.