topic Re: Deploying SAS Viya on OCP in a dark-site (no Internet access) in Administration and Deployment

Deploying SAS Viya on OCP in a dark-site (no Internet access)

EyalGonen — Sun, 11 May 2025 06:33:20 GMT

Hi experts,

I need to deploy SAS Viya on-prem on OpenShift with no Internet access at all (dark site) using the SAS Deployment Operator.

Looking at https://documentation.sas.com/doc/en/sasadmincdc/v_056/dplyml0phy0dkr/p0nid9gu3x2cvln1pzpcxa68tpom.htm#p012wq5dhcqbx8n12abyqe25m4nu

at the --repository-warehouse parameter and I see it is required for a dark site deployment but no further info is available.

I am in contact with SAS Technical Support but I wonder if there is anyone out there who actually managed to install SAS Viya with this configuration and can share their input about this --repository-warehouse parameter and how they used it.

Thanks.

Re: Deploying SAS Viya on OCP in a dark-site (no Internet access)

gwootton — Mon, 12 May 2025 16:50:20 GMT

You can use mirror manager to create the repository location:

Create a Mirror Registry at an Air-Gapped Site
https://go.documentation.sas.com/doc/en/itopscdc/v_063/dplyml0phy0dkr/n1f39x15xt82m4n13f7bu37l9qum.htm

The documentation indicates you would then specify that local path when running the sas-orchestration tool.

For the Deployment Operator, as you mentioned on your other post the viya4-warehouse project can also download the warehouse files without making use of mirror manager:

https://github.com/sassoftware/viya4-warehouse

If you serve that download path as the top level from a cluster-local web server you could specify that as the repository-warehouse-location. And the various deployment operator tasks should call that URL instead.

Re: Deploying SAS Viya on OCP in a dark-site (no Internet access)

EyalGonen — Tue, 13 May 2025 06:14:01 GMT

Hi @gwootton

Let me summarize and tell me if this correct:

(assuming dark-site with no Internet access at all)

1. I use mirror manager to download the mirror. The downloaded mirror includes all the docker images and additionally the four "warehouse" files:

entitlements.json
cadences/shipped.mc
rel/<cadence>/<version>
lod/<cadence>/<version>/<release>

2. The docker images are then uploaded/pushed to JFrog from the downloaded mirror using mirror manager

3. The four "warehouse" files listed above are copied over (with their parent folders) to a local HTTP Server that is accessible from the cluster pods

4. When creating the SASDeployment CRD, I add the following two options:

--image-registry registry-host:registry-port/registry-namespace \
--repository-warehouse http://<local-HTTP-Server>/<repository-warehouse-folder> \

Is this correct?

Re: Deploying SAS Viya on OCP in a dark-site (no Internet access)

gwootton — Tue, 13 May 2025 17:39:13 GMT

Yes, I think the only caveat I'd point out is the contents of rel and lod are going to change when you pull a new release.

Re: Deploying SAS Viya on OCP in a dark-site (no Internet access)

EyalGonen — Wed, 14 May 2025 06:26:45 GMT

Hi @gwootton

So when I will want to upgrade to a newer SAS version then what would I need to do with respect to the "repository warehouse" files?

Thanks

Re: Deploying SAS Viya on OCP in a dark-site (no Internet access)

gwootton — Wed, 14 May 2025 15:52:31 GMT

When upgrading you'd need to run mirrormgr again to mirror the images you'd also want to put the new repository warehouse files into the location served by your HTTP server.