Don't link manila for /home to manila for /project in caas

stackhpc / ansible-slurm-appliance

A Slurm-based HPC workload management environment, driven by Ansible.

36 stars 15 forks source link

Don't link manila for /home to manila for /project in caas #363

Closed sjpb closed 4 months ago

sjpb commented 4 months ago

Enables making the use of manila for /home in CaaS clusters an explicit opt-in via azimuth-ops configuration. This is to avoid the current situation where:

Deploy vanilla Azimuth
Deploy a Slurm cluster, gets Cinder home
Enable the project share support in Azimuth
Patch the Slurm cluster - existing data in /home gets deleted

sjpb commented 4 months ago

Testing at this commit:

Created azimuth without setting azimuth_openstack_manila_project_share_gb
Created slurm had no /project and /home was cinder - correct
Reprovisioned azimuth with azimuth_openstack_manila_project_share_gb: 10
New slurm had /project but /home was still cinder - correct

mkjpryor commented 4 months ago

I have also verified that the following works:

Created azimuth without setting azimuth_openstack_manila_project_share_gb
Created slurm had no /project and /home was cinder - correct
Reprovisioned azimuth with azimuth_openstack_manila_project_share_gb: 10
Update of existing slurm picks up /project but /home was still cinder - correct