how to install SAS Viya 3.5 (Centos7.9) on external HD?

[teolly]

Hi All, if i start viya3.5 installation in this way "ansible-playbook site.yml" as root user it's fails, because "sda2" it's too small, i need to install as root user SAS viya3.5 on external disk "data-data_lv " instead "sda2", how can I do that?
Tnx in advance for further replies.

Here more information:
List disks:
[root@test-interni sas]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 16G 0 16G 0% /dev
tmpfs 16G 208K 16G 1% /dev/shm
tmpfs 16G 18M 16G 1% /run
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/sda2 30G 6.5G 24G 22% /
/dev/mapper/data-data_lv 252G 33G 207G 14% /opt/sas
/dev/sdb1 148G 61M 140G 1% /mnt/resource
tmpfs 3.2G 0 3.2G 0% /run/user/1000

[root@test-interni sas_viya_playbook]# ansible-playbook system-assessment.yml
........
PLAY RECAP ****************************************************************************************************************************************************
deployTarget : ok=129 changed=9 unreachable=0 failed=0 skipped=65 rescued=0 ignored=0
localhost : ok=10 changed=0 unreachable=0 failed=0 skipped=6 rescued=0 ignored=0

[Patrick]

If this is a new install why aren't you choosing the latest Viya 4 release? There have been so many improvements since Viya 3.5.

[teolly]

It's first installation for me, it's for testing how Viya works. I get only this kind of lincence for training.

[gwootton]

You can set VERIFY_DEPLOYMENT to false in vars.yml to not perform these checks.

Set the Pre-deployment Validation Parameters
https://go.documentation.sas.com/doc/en/calcdc/3.5/dplyml0phy0lax/n1knvzbsifo9xqn1al0bh7wxrrkg.htm#p...

[teolly]

Hi, thx for your answer and usufull suggest. I changed this parameter as here below:

# Recommended Ansible version
MAXIMUM_RECOMMENDED_ANSIBLE_VERSION: "2.14"

#  DEPLOYMENT_LABEL sets the datacenter for the Consul server. In addition, any
#  local Consul agents will use DEPLOYMENT_LABEL to become members of a
#  multi-machine deployment. A valid label can contain only lowercase characters,
#  numeric characters, and hyphens.

DEPLOYMENT_LABEL: "{{ DEPLOYMENT_ID }}"

# run deployment assessment during playbook execution
VERIFY_DEPLOYMENT: false

I need to install viya 3.5, single tenant, on external partition disk (/opt/sas), here below which one, usually when i start installation the root partition fill up at 100% :

/dev/sda2 30G 6.5G 24G 22% /
/dev/mapper/data-data_lv 252G 33G 207G 14% /opt/sas

More information about ansible version:

[root@test-interni tmp]# ansible --version
[DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the controller starting with Ansible 2.12. Current version: 3.6.8 (default, Nov 14 2023,
16:29:52) [GCC 4.8.5 20150623 (Red Hat 4.8.5-44)]. This feature will be removed from ansible-core in version 2.12. Deprecation warnings can be disabled by
setting deprecation_warnings=False in ansible.cfg.
/usr/local/lib/python3.6/site-packages/ansible/parsing/vault/__init__.py:44: CryptographyDeprecationWarning: Python 3.6 is no longer supported by the Python core team. Therefore, support for it is deprecated in cryptography. The next release of cryptography will remove support for Python 3.6.
  from cryptography.exceptions import InvalidSignature
ansible [core 2.11.12]
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python3.6/site-packages/ansible
  ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/local/bin/ansible
  python version = 3.6.8 (default, Nov 14 2023, 16:29:52) [GCC 4.8.5 20150623 (Red Hat 4.8.5-44)]
  jinja version = 3.0.3
  libyaml = True

So, after this modify i tried to execute "ansible-playbook site.yml" as root user and now i get this java error:

TASK [sas-requirements-java : Install the SAS Java configuration] ********************************************************************************
skipping: [deployTarget]

TASK [sas-requirements-java : Set SAS_JAVA_HOME] *********************************************************************************
fatal: [deployTarget]: FAILED! => {"changed": false, "msg": "Destination /opt/sas/viya/config/etc/sysconfig/sas-javaesntl/sas-java does not exist !", "rc": 257}

NO MORE HOSTS LEFT *********************************************************************************

PLAY RECAP *********************************************************************************
deployTarget               : ok=137  changed=16   unreachable=0    failed=1    skipped=68   rescued=0    ignored=0
localhost                  : ok=8    changed=0    unreachable=0    failed=0    skipped=7    rescued=0    ignored=0

Could you please have more suggest for me?
Tnx in advance.

[gwootton]

You may wish to engage SAS Technical Support, if your root is filling up this could certainly cause other problems.

[teolly]

Ok.
I didn't understand why if i run this command "yum install -y sas*" my root disk fill up instead of /opt/sas.
The same kind of behavior if i launched "ansible-playbook site.yml".

This is an example of disk saturation during execution command, "yum install -y sas*":
/dev/sda2 30G 11G 20G 37% /
/dev/mapper/data-data_lv 252G 108G 132G 46% /opt/sas

several minutes later:
/dev/sda2 30G 12G 19G 38% /
/dev/mapper/data-data_lv 252G
108G 132G 46% /opt/sas

...and continue until 100%

[gwootton]

I suspect this has to do with yum downloading the packages into its cache, but you could probably use du to locate the offending files on your root.

[teolly]

Yes, it's true... I have recognized that was "/var" the folder indicted but i don't know why site.yml wrote all onte thoose folder.
Vars.yml seems to be right, these are the only section completed:

# Recommended Ansible version
MAXIMUM_RECOMMENDED_ANSIBLE_VERSION: "2.14"

# DEPLOYMENT_LABEL sets the datacenter for the Consul server. In addition, any
# local Consul agents will use DEPLOYMENT_LABEL to become members of a
# multi-machine deployment. A valid label can contain only lowercase characters

DEPLOYMENT_LABEL: "{{ DEPLOYMENT_ID }}"

# run deployment assessment during playbook execution
VERIFY_DEPLOYMENT: false

# Determine how Consul's ports are configured. Setting this variable to false
# will only open the HTTP port (8500). Setting this variable to true will enable
# the combination of the HTTP port (8500) and the HTTPS port (8501).
SECURE_CONSUL: true

# Toggles the status of the Consul port operating over HTTP.
#
# If this variable is set to true when SECURE_CONSUL is true,
# then Consul will only be able to communicate over HTTPS (port 8501).
#
# If this variable is set to false when SECURE_CONSUL is true,
# then Consul will be able to communicate over both HTTP (port 8500),
# and HTTPS (port 8501).
#
# This setting is only honored when SECURE_CONSUL is true.
DISABLE_CONSUL_HTTP_PORT: true

# Path to the HTTPD certificate to distribute into SAS truststores
HTTPD_CERT_PATH: "/etc/pki/tls/certs/localhost.crt"

# The name of the license file on the Ansible machine.
LICENSE_FILENAME: "SASViyalicence.txt"

# The name of the composite license file on the Ansible machine.
# If both files are present, the playbook will use the
# composite license file.
LICENSE_COMPOSITE_FILENAME: "SASViyalicence.jwt"
....
REPOSITORY_WAREHOUSE: "/opt/sas/install/mirror"

# Multiple invocation definitions
# The machine reference (with deployTarget as the default) must be enclosed
# in quotes if it is set to a value that starts with a number.
INVOCATION_VARIABLES:
deployTarget:
pgpoolc:
- HA_PGPOOL_VIRTUAL_IP: ''
HA_PGPOOL_WATCHDOG_PORT: ''
PCP_PORT: '5430'
PERMS_OVERRIDE: 'false'
PGPOOL_PORT: '5431'
POOL_NUMBER: '0'
SANMOUNT: '{{ SAS_CONFIG_ROOT }}/data/sasdatasvrc'
SERVICE_NAME: postgres
sasdatasvrc:
- NODE_NUMBER: '0'
PG_PORT: '5432'
SANMOUNT: '{{ SAS_CONFIG_ROOT }}/data/sasdatasvrc'
SERVICE_NAME: postgres
....
# deployment and set the path to Java in sasenv_java_home.
sas_install_java: false

# User specific location of where Java resides on the host.
# If not set, the deployment will use the Java defined on the host.
# This is an optional setting.
# Example:
# sasenv_java_home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.101-3.b13.el6_8.x86_64/jre
sasenv_java_home: "/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.392.b08-2.el7_9.x86_64/jre"

# When set to true, enables extra logging during the deployment
sas_deploy_debug: false
....
CAS configuration
# This user must be a member of the "sas" group
casenv_user: cas
# The group that the CAS user belongs to
casenv_group: sas

[gwootton]

The use of /var by the yum package manager is not something configurable in vars.yml. You may want to turn of caching in your yum configuration on the host if you enabled it.

Enable the Yum Cache
https://go.documentation.sas.com/doc/en/calcdc/3.5/dplyml0phy0lax/n0x1r3nedccwvkn1d5xqbokck0m5.htm

[teolly]

Hi, i change my "yum.conf", theese the next step i've been done with file changed:
vim /etc/yum.conf--> keepcache=1

deploy-cleanup.yml

site.yml --> failed: "msg": "Destination /opt/sas/viya/config/etc/sysconfig/sas-javaesntl/sas-java does not exist !", "rc": 257

sudo rpm -e $(rpm -qg SAS) --nopreun

yum clean all --> Repository 'sas-vtxtan-125-x64_redhat_linux_6-yum': Error parsing config: Error parsing "baseurl = '/opt/sas/install/mirror/repos/shipped/vtxtan/125/vtxtan-125-x64_redhat_linux_6-yum'": URL must be http, ftp, file or https not ""

yum install java* -->nothing to do

ansible-playbook site.yml --> fatal: [deployTarget]: FAILED! => {
"changed": false,
"invocation": {
"module_args": {
"allow_downgrade": false,
"autoremove": false,
"bugfix": false,
"conf_file": null,
"disable_excludes": null,
"disable_gpg_check": true,
"disable_plugin": [],
"disablerepo": [],
"download_dir": null,
"download_only": false,
"enable_plugin": [],
"enablerepo": [],
"exclude": [],
"install_repoquery": true,
"install_weak_deps": true,
"installroot": "/",
"list": null,
"lock_timeout": 30,
"name": [
"sas-cleanutils"
],
"releasever": null,
"security": false,
"skip_broken": false,
"state": "latest",
"update_cache": false,
"update_only": false,
"use_backend": "auto",
"validate_certs": true
}
},
"msg": "No package matching 'sas-cleanutils' found available, installed or updated",
"rc": 126,
"results": [
"No package matching 'sas-cleanutils' found available, installed or updated"]}

yum install -y sas* --> ok

site.yml --> fatal: [deployTarget]: FAILED! => { ..... --> sas-cleanutils

yum install -y sas-lifecycle --> No package sas-lifecycle available.
Error: Nothing to do

[gwootton]

I think you'd want keepcache=0 if you don't want to keep the cache.

[teolly]

Done, thx. I tried to launch again site.yml and i commented this section in vars.yml:
#CAS_DISK_CACHE: "/opt/sas/cascache" got this:

fatal: [deployTarget]: FAILED! => {
"changed": false,
"invocation": {
"module_args": {
"allow_downgrade": false,
"autoremove": false,
"bugfix": false,
"conf_file": null,
"disable_excludes": null,
"disable_gpg_check": true,
"disable_plugin": [],
"disablerepo": [],
"download_dir": null,
"download_only": false,
"enable_plugin": [],
"enablerepo": [],
"exclude": [],
"install_repoquery": true,
"install_weak_deps": true,
"installroot": "/",
"list": null,
"lock_timeout": 30,
"name": [
"sas-cleanutils"
],
"releasever": null,
"security": false,
"skip_broken": false,
"state": "latest",
"update_cache": false,
"update_only": false,
"use_backend": "auto",
"validate_certs": true
}
},
"msg": "No package matching 'sas-cleanutils' found available, installed or updated",
"rc": 126,
"results": [
"No package matching 'sas-cleanutils' found available, installed or updated"]}

[gwootton]

This error message suggests that there is no enabled yum repository that contains the sas-cleanutils package.
You may want to do a deploy-cleanup and try again, or restore from a backup prior to the event when the root file system was filled.