nfs-shares may contain multiple NFS mount points
Bug #1894817 reported by
James Page
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
TrilioVault Data Mover Charm |
Fix Released
|
Medium
|
James Page | ||
TrilioVault Workload Manager Charm |
Fix Released
|
Medium
|
James Page | ||
charms.openstack |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Hi,
We have some cases where we need to have multiple NFS shares for the same Trilio installation.
That can be either one NFS share for the OpenStack + other shares from other clouds that are also available to read; or multiple shares to write on purely simple.
Current Trilio charms do not support that.
The ongoing new charms should come with this support.
I can see on DM supports bind mounts for incremental copies [0], however we should also be able to pass multiple entries to DM config files as well.
Changed in charm-trilio-data-mover: | |
milestone: | none → 20.10 |
Changed in charm-trilio-wlm: | |
milestone: | none → 20.10 |
Changed in charm-trilio-data-mover: | |
importance: | Undecided → Medium |
Changed in charm-trilio-wlm: | |
importance: | Undecided → Medium |
Changed in charms.openstack: | |
importance: | Undecided → Medium |
Changed in charm-trilio-data-mover: | |
status: | Fix Committed → Fix Released |
Changed in charm-trilio-wlm: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/750317 /git.openstack. org/cgit/ openstack/ charms. openstack/ commit/ ?id=4c2486660fa 3e201f3a39a0371 d7bf310fe3ab3e
Committed: https:/
Submitter: Zuul
Branch: master
commit 4c2486660fa3e20 1f3a39a0371d7bf 310fe3ab3e
Author: James Page <email address hidden>
Date: Tue Sep 8 11:49:49 2020 +0100
trilio: Support multiple NFS share configurations
TrilioVault supports use of multiple NFS shares using a comma
separated list. Update the ghost-nfs-share action code to
support this type of configuration.
The assumption is that the order of shares provided to the
action is the same as the order of shares in the nfs-shares
configuration option in terms of replication between sites.
Mismatched length lists will generate an exception which can
be propagated back to the operator.
Change-Id: I7d501a3e44d4e7 c732e7625fa2a8c de9a34ff564
Closes-Bug: 1894817