477d44cab9
Systemd has the ability to manage mounts and ensure functionality / resource management. Using a systemd mount has the benifit of not requiring writes to the legacy fstab file which can impact OS functionality especially when deploying on baremetal. This change moves the glance NFS mount to a systemd unit file allowing systemd to manage it independently with no potentially breaking impact to the underlying operating system. Changes: - This PR corrects a long standing issue when using Glance+NFS where initial deployment would work but if the playbooks were run again it would fail due to the glance images location being an NFS mount point with a potentially different UID/GID. To correct this we stat the directory and if it does NOT exist it is created. - Following the nova pattern options have been provided to set the UID and GID of the glance user. - To ensure out NFS backend solution works with the installation of glance a test has been added to deploy glance using an NFS backend. - An upgrade task has been added to this commit to clean up legacy mounts, This task should be removed in R. Change-Id: I716c9fe35391629532e67e212d45ea27a5422d1b Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
12 lines
684 B
YAML
12 lines
684 B
YAML
---
|
|
features:
|
|
- When using Glance and NFS the NFS mount point will now be managed using a
|
|
systemd mount unit file. This change ensures the deployment of glance is not
|
|
making potentially system impacting changes to the ``/etc/fstab`` and
|
|
modernizes how we deploy glance when using shared storage.
|
|
- New variables have been added to the glance role allowing a deployer to set
|
|
the UID and GID of the glance user. The new options are,
|
|
``glance_system_user_uid`` and ``glance_system_group_uid``. These options
|
|
are useful when deploying glance with shared storage as the back-end for
|
|
images and will only set the UID and GID of the glance user when defined.
|