-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support manila fileshares (cephfs) #344
Conversation
Checked share works ok after reboot |
0ed5076
to
80a8222
Compare
Fat image build w/ (default nautilus) manila client: https://github.com/stackhpc/ansible-slurm-appliance/actions/runs/7543193442 |
Fat image build: https://github.com/stackhpc/ansible-slurm-appliance/actions/runs/7544263443 |
Example additional config on arcus rcp-cloud-portal-demo:
|
…hares" This reverts commit 3d9cfba.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My only real worry is clashing with this change:
#348
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's remove that ui-meta, after that consider the approved, awesome work on getting this sorted!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, thank you
Adds general support for multiple manila fileshares using CephFS protocol. See groups, group_vars and role for
manila
.In
.caas
environment for Azimuth:a. Storage for home directories is now configurable using bool
cluster_home_manila_share
:true
, a manila share is created and deleted with the cluster. In this case the share type must be defined withcluster_home_manila_share_type
unless the a default share type is defined in OpenStack.false
, an OpenStack volume attached to control node and NFS exported to cluster (pre-PR behaviour)In both cases
home_volume_size
defines the size (in GB) of the relevant storageb. A project share can be enabled by setting bool
cluster_project_manila_share: true
. This is expected to already exist (i.e. its lifecycle is not tied to the cluster). Its name is defined bycluster_project_manila_share_name
, defaulting toazimuth-project-share
. Seeenvironments/.caas/inventory/group_vars/all/manila.yml
.In skeleton terraform (used by new cookiecutter environments and stackhpc CI environment):
a.
home_volume_size
can be set to 0 to not create a home volume. This allows e.g. a manila share to be externally defined or defined in additional terraformb. Manila client (default nautilus version) installed in fat image.