Skip to content

Releases: sassoftware/viya-ark

Viya35-ark-1.10 - October 20, 2020

20 Oct 19:40
Compare
Choose a tag to compare
  • Summary:
    Changing range of Ansible versions supported. Enhancing obsolete log archiving.
  • Issues addressed:
    • General
      • VIYAARK-188 - Support Ansible 2.10.
      • VIYAARK-216 - Add Bug Report template to GitHub Issue submission.
    • SAS Viya Upgrade Tasks Playbooks
      • VIYAARK-104 - Produce summary report for Archive Obsolete Folders playbook.
  • Ansible Support: Ansible 2.8 - Ansible 2.10

Viya35-ark-1.9 - September 30, 2020

30 Sep 18:28
Compare
Choose a tag to compare
  • Summary:
    Fix related to MMSU, Pre-Install & Post Upgrade.
  • Issues addressed:
    • General
      • VIYAARK-212 - Remove deprecated includes from codebase. MMSU & Post Upgrade.
    • SAS Viya Pre-Installation Playbook
      • VIYAARK-209 - Clean up references to max_num_priv_ips.
    • SAS Multi-Machine Service Utilties
      • VIYAARK-103 - Add a confirmation before stopping
  • Ansible Support: Ansible 2.7.2 - Ansible 2.9

Viya35-ark-1.8 - August 31, 2020

31 Aug 16:16
Compare
Choose a tag to compare
  • Summary:
    Fix related to Merge Playbook.
  • Issues addressed:
    • SAS Viya Upgrade Tasks Playbooks
      • VIYAARK-208 - Merge Playbook: Adding a new property, PERMS_OVERRIDE, to INVOCATION_VARIABLE.
  • Ansible Support: Ansible 2.7.2 - Ansible 2.9

Viya35-ark-1.7 - July 29, 2020

29 Jul 20:45
Compare
Choose a tag to compare
  • Summary:
    Enhancements and fixes related to Pre-Install playbook & Deployment Report.
  • Issues addressed:
    • SAS Viya Pre-Installation Playbook
      • VIYAARK-56 - Multi-nic limitation checks removed.
    • SAS Viya Deployment Report
      • VIYAARK-207 - Deployment Report not working when including hotfixes.
    • General
      • VIYAARK-200 - Develop a list of data to be submitted with github issues.
      • VIYAARK-205 - Home Directory Creator tool removed from SAS Viya ARK.
  • Ansible Support: Ansible 2.7.2 - Ansible 2.9

Viya35-ark-1.6 - July 1, 2020

01 Jul 18:39
Compare
Choose a tag to compare
  • Summary:
    Enhancements and fixes related to Pre-Install playbook, MMSU & LDAP Validator.
  • Issues addressed:
    • SAS Viya Pre-Installation Playbook
      • VIYAARK-11 - SSL Certificate check and validation.
      • VIYAARK-30 - HTTP/HTTPS proxy check and validation.
      • VIYAARK-169 - Import SSL and proxy check tasks to playbook.
    • SAS Multi-Machine Service Utilties
      • VIYAARK-201 - Update README: programming-only deployment not supported.
    • SAS LDAP Validator
      • VIYAARK-202 - Input (-b) needed for basic connection tasks to work.
  • Ansible Support: Ansible 2.7.2 - Ansible 2.9

Viya35-ark-1.5 - June 4, 2020

04 Jun 20:39
Compare
Choose a tag to compare
  • Summary:
    Update Support statement and revise Change Log from prior release.
  • Issues addressed:
    • General
      • VIYAARK-190 - Update Viya ARK support statement.
  • Ansible Support: Ansible 2.7.2 - Ansible 2.9

Viya35-ark-1.4 - May 29, 2020

29 May 20:51
Compare
Choose a tag to compare
  • Summary:
    Enhancements and fixes related to Upgrade & Multi-Machine Services Utilities.
  • Issues addressed:
    • SAS Multi-Machine Service Utilties
      • VIYAARK-122 - Support using GEL script in start/stop.
      • VIYAARK-124 - Consul logging need to be redirected to stdout.
      • VIYAARK-125 - Rewording message when consul has a slow start.
      • VIYAARK-126 - Tool may not work properly for single machine deployment.
      • VIYAARK-128 - Performance improvement when rerun viya-services-stop.yml.
      • VIYAARK-129 - When running playbook stop, rabbitmq may have process left behind.
      • VIYAARK-130 - Upon failure, playbook viya-services-stop.yml should stop instead of continue.
      • VIYAARK-150 - Parameter LIST should be quoted.
      • VIYAARK-151 - User request to update task name for Data Server Consul Template.
    • SAS Viya Upgrade Tasks Playbooks
      • VIYAARK-184 - Merge playbook fails to parse ansible.cfg correctly for SAS-internal deployment.
  • Ansible Support: Ansible 2.7.2 - Ansible 2.9

Viya35-ark-1.3 - April 1, 2020

01 Apr 21:24
c5d6068
Compare
Choose a tag to compare
  • Summary:
    Enhancements and fixes related to Upgrade, Multi-Machine Services Utilities, Pre-Installation playbooks.
  • Issues addressed:
    • SAS Viya Upgrade Tasks Playbooks
      • VIYAARK-121 - Pre-upgrade failure due to Ansible 2.7 incompatible function.
      • VIYAARK-105 - hostname comparison should be case insensitive
      • VIYAARK-89 - Merge Playbook should handle multi-NIC inventory/vars
    • SAS Multi-Machine Service Utilties
      • VIYAARK-118 - Improving code for multiple CAS controllers
      • VIYAARK-113 - Support MMSU when DB node0/pgpool0 is down and DB is functional
    • SAS Viya Pre-Installation Playbook
      • VIYAARK-83 - Check that the SSH ClientAliveInterval is adequate
      • VIYAARK-5 - Catch when no permission to SAS home directory
  • Ansible Support: Ansible 2.7.2 - Ansible 2.9

Viya35-ark-1.2 - February 28, 2020

28 Feb 19:53
Compare
Choose a tag to compare
  • Summary:
    Enhancements and fixes related to Upgrade, Multi-Machine Services Utilities, Deployment Report, Pre-Installation playbooks and documentation.
  • Issues addressed:
    • General
      • VIYAARK-87 - Validation of Python3 support across the applicable tools.
      • VIYAARK-63 - Improve speed of playbook when skipping hyphenated hostname [sas-all] fix
      • VIYAARK-29 - Validation of Linux on Power hosting environment across the tools. (See main README for info on Linux on Power support in SAS Viya 3.5)
    • SAS Viya Upgrade Tasks Playbooks
      • VIYAARK-44 - Archive Obsolete Folders playbook: Addresses the large number of outdated service directories in the logs location for upgrade customers
      • VIYAARK-65 - Improve merge playbook inventory and INVOCATION_VARIABLES when new hostgroups exist
      • VIYAARK-60 - Improve handling of return codes from actions of Pre-Upgrade playbook
      • VIYAARK-42 - Pre-Upgrade playbook disk space check needs to handle no /opt/sas path without failure
    • SAS Multi-Machine Service Utilties
      • VIYAARK-55 - viya-services-stop.yml message output typo
      • VIYAARK-40 - Honor svc-ignore entries
      • VIYAARK-62 - Provide a reliable startup script for distributed Viya with automatic Consul cleanup
    • SAS Viya Deployment Report
      • VIYAARK-38 - Improve Hotfix deployment report to only show applicable hotfixes per release
      • VIYAARK-86 - deployment-report playbook fails when remote host is using Python 3.x
      • VIYAARK-49 - jQuery XSS vulnerability - moving from v3.3.1 to v3.4.1
      • VIYAARK-88 - Error thrown when run against an incomplete deployment
    • SAS Viya Pre-Installation Playbook
      • VIYAARK-27 - Correct package selection in Linux on Power hosting environment.
      • VIYAARK-14 - Suppress RHEL package version check for Linux on Power RHEL hosting environment.
      • VIYAARK-9 - Playbook tasks using Linux shell command incorrect recap showing Changed > 0 after multiple re-runs of playbook.
  • Ansible Support: Ansible 2.7.2 - Ansible 2.9

Viya35-ark-1.1 - December 19, 2019

19 Dec 17:04
Compare
Choose a tag to compare
  • Summary:
    Enhancements and fixes related to Upgrade, Deployment Report, Pre-Installation playbooks and documentation.
  • Issues addressed:
    • General
      • VIYAARK-64 - Known Issues section added to main README
    • SAS Viya Upgrade Tasks Playbooks
      • VIYAARK-45 - DEFAULT_BACKUP_SCHEDULE job not recreated after upgrade from SAS Viya 3.3 to SAS Viya 3.4/3.5
      • VIYAARK-41 - Pre-Upgrade playbook fails if SAS Viya 3.5 software order adds [ModelServer]
    • SAS Viya Deployment Report
      • VIYAARK-46 - Temporarily disable hotfix report for earlier release
    • SAS Viya Pre-Installation Playbook
      • VIYAARK-43 - Remove libXp.i686 from required software packages
      • VIYAARK-25 - Non-supported Java version check done in normal mode as well as check mode
      • VIYAARK-50 - Kernel semaphore performance configuration task not adjusting settings as expected (Python 2) and failing playbook (Python 3)