Skip to main content


Get Helm Chart manifest from Kubernetes

Below command can be used to get Helm manifest from Kubernetes secret.  kubectl get secrets sh.helm.release.v1.test-deomo -o jsonpath="{ .data.release }" | base64 -d | base 64 -d  | gunzip | json_pp Alternative: helm get manifest test-demo
Recent posts

Grid Administration Notes - LSF

 LSF connects server to a single cluster. In SAS, LSF Cluster and SAS Grid refers to same. Platform Suite of SAS comprised of following softwares : LSF - Load Sharing Facility PM - Process Manager GMS - Grid Management Services LSF: LSF requires that its configuration files reside in a shared drive which is accessible from all servers in the grid. LSF cluster is controlled by LSF Master. There can be multiple master but only one will be active. It dispatches job to the server based on load indices and policies. LSF Queues - Any job submission first goes to queue and LSF check the queue for every 30 seconds and dispatch to the server. EGO - Enterprise Grid Orchestrator - Provides Fault Tolerance and High Availability  Platform Process Manager - Flow manager and calendar editor. It runs process jfd Grid Management Services  - Information from LSF is passed to SAS Grid Manager plugin in SMC Daemon: SAS Grid Manager SAS Components: Grid Manager Plugin - SMC plugin SASGSUB - Synchronous a

Why Gemfire Used in SAS?

Answer: Latency Latency Pyramid - CPU vs Memory vs Disk The below chart show how much time it takes to process data in each resource. We can see Disk Seek is the biggest bottleneck. We can improve it by storing the data in-memory. Gemfire allows to store data in in-memory data grid.

Verify Certificate Key and CRT in SAS using OpenSSL Command

 Error: [Wed Jan 13 19:37:41 2021] [warn] RSA server certificate CommonName (CN) `hostname' does NOT match server name!? [Wed Jan 13 19:37:41 2021] [warn] RSA server certificate CommonName (CN) `hostname' does NOT match server name!? [Wed Jan 13 19:37:41 2021] [notice] Apache/ (Unix) PivotalWebServer/5.5.4 mod_ssl/ OpenSSL/1.0.2l-fips mod_bmx/0.9.6 configured -- resuming normal operations [Wed Jan 13 19:37:50 2021] [error] [client] File does not exist: /test/sasconfig/Lev1/Web/WebServer/htdocs/favicon.ico, referer: https://hostname:8343/ [Wed Jan 13 19:38:19 2021] [error] [client] File does not exist: /test/sasconfig/Lev1/Web/WebServer/htdocs/favicon.ico, referer: https://hostname:8343/ Command for crt file: openssl x509 -noout -modulus -in hostname.crt | openssl md5 Output: (stdin)= b3d24204e284a8a300fc462a6e2f9357 Command for Key file: openssl x509 -noout -modulus -in hostname.crt_bkp | openssl md5 Output: (stdin)= b3d24204e284a8a

iotest script

# print usage usage () {         echo ""         echo "<<USAGE>>  ${PROG} -i <iterations> -t <target filesystem> -b <block count> -s <block size>"         echo ""         echo "  function run current dd write and read tests to a SAS filesystem to test thruput"         echo "           where results will be stored in ${PROG}.results.<iterations>"         echo ""         echo "  where    iterations are the number of concurrent tests to run"         echo "           target filesystem is the SAS read/write filesystem to test"         echo "           block count is the number of block you want dd to process (eg: 20000)"         echo "           block size is the size of the blocks you want dd to process in K (eg: 64)" } # validate input parameters for iterations and writeable target directory validateinput () {         UNAME=`uname`         TMPNAME=t

SASWork throughput requirement

Below is the SASWORK throughput requirement that you should remember while architecting: Write - 100MB/second for each CPU core Read - 100MB/second for each CPU core This can be calculated using the script attached in this article -> Reference -> If you are not able to download the script you can copy it from here .