search

sassoftware / viya4-deployment

This project contains Ansible code that creates a baseline in an existing Kubernetes environment for use with the SAS Viya Platform, generates the manifest for an order, and then can also deploy that order into the Kubernetes environment specified.
Apache License 2.0
71 stars 64 forks source link

feat: (IAC-739) Support a CDSPostgreSQL instance for Crunchy v5 #307

Closed dhoucgitter closed 2 years ago

dhoucgitter commented 2 years ago

Changes

Viya Retail and Planning application require the installation of a secondary PostgreSQL instance referred to as the Common Data Store Postgres instance. This updates includes the support to install a secondary internal instance of Postgres named "cds-postgres" and can be triggered by including the following postgres clause in the ansible-vars.yaml file used to deploy Viya.

## Postgres
V4_CFG_POSTGRES_SERVERS:
  default:
    internal: true
  cds-postgres:
    internal: true

Tests

Testing included deploying a fast 2020 Inventory Fulfillment Viya order while specifying two Postgres instances as above. The presence of planning application schemas created in the CDS Postgres instance were used to verify the successful deployment and configuration of the CDS Postgres instance.

riragh commented 2 years ago

@dhoucgitter There is stray TODO in the postgres-instance.yaml file, I think this was added in last round to fix with CDS changes could you please take a look. https://github.com/sassoftware/viya4-deployment/blob/feat-iac-739/roles/vdm/tasks/postgres/postgres-instance.yaml#L156

dhoucgitter commented 2 years ago

@riragh, it looks like Jay might have added that note with merge in PR #303 to remind us to re-examine the internal crd and external crd sections. It seems that both of those CRD blocks apply to pre 2022.10 cadence orders looking at the when clause content. I suspect we can make those where clauses more similar while leaving the internal/external comparisons in place.