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-355) Enable Multi-tenant deployments #257

Closed riragh closed 2 years ago

riragh commented 2 years ago

Changes

Enabling DAC to do multi-tenant deployments. Tasks were divided into different tickets.

Tests

See the above mentioned internal tickets for testing

riragh commented 2 years ago

Variable names updated: SAS_TENANT_IDS is being renamed to V4MT_TENANT_IDS and SAS_PROVIDER_PASSWORD is renamed to V4MT_PROVIDER_PASSWORD. Files were updated to be all lower case and use hyphens instead of underscore. README documents now SAS Viya Multi-tenancy instead of only Multi-tenancy.

riragh commented 2 years ago

The more I think about this one, the actions should have been name spaced as we have with other tasks:

baseline - performs baseline items viya - performs viya items

There should be a multi-tenancy item:

mt - performs multi-tenancy items. This would have actions like: onboard, cas-onboard, etc

At this point we'd have to retest but again, long term thinking and pattern matching with the code base would have made this seem like the logical choice. As it is now we just run onboard or cas-onboard they have no real meaning and or context.

If you look at the doc here. You can see there are Actions and Tasks with this new implementation things are broken. There are no more actions or tasks.

In the new change, updated the actions and tasks. Task is multi-tenancy and actions are onboard, cas-onboard and offboard. Ran different scenarios to cover this new change.

riragh commented 2 years ago

Talked with Ritika, there are some doc links need to be updated.

Done. Updated all links to always point to default cadence.