6879bd0720
This patch allows an OpenStack environment to run as a secure NAS environment from the client and server perspective, including having root squash enabled and not running file operations as the 'root' user. This also sets Cinder file permissions as 660: removing other/world file access. The "nas_secure_file_permissions" option controls the setting of file permissions when Cinder volumes are created. The option defaults to "auto" to gracefully handle upgrade scenarios. When set to "auto", a check is done during Cinder startup to determine if there are existing Cinder volumes: no volumes will set the option to 'true', and use secure file permissions. The detection of existing volumes will set the option to 'false', and use the current insecure method of handling file permissions. The "nas_secure_file_operations" option controls whether file operations are run as the 'root' user or the current OpenStack 'process' user. The option defaults to "auto" to gracefully handle upgrade scenarios. When set to "auto", a check is done during Cinder startup to determine if there are existing Cinder volumes: no volumes will set the option to 'true', be secure and do NOT run as the 'root' user. The detection of existing volumes will set the option to 'false', and use the current method of running operations as the 'root' user. For new installations, a 'marker file' is written so that subsequent restarts of Cinder will know what the original determination had been. This patch enables this functionality only for the NFS driver. Other similar drivers can use this code to enable the same functionality with the same config options. DocImpact Change-Id: I3d25f593beab7f5462576b14ab62d13d8c53e7c6 Implements: blueprint secure-nfs Partial-Bug: 1260679 |
||
|---|---|---|
| .. | ||
| initiator | ||
| iscsi | ||
| local_dev | ||
| remotefs | ||
| README.txt | ||
| __init__.py | ||
| exception.py | ||
| executor.py | ||
README.txt
Brick is a new library that currently is maintained in Cinder for the Havana release. It will eventually be moved external to Cinder, possibly oslo, or pypi. Any defects found in Brick, should be submitted against Cinder and fixed there, then pulled into other projects that are using brick. * Brick is used outside of Cinder and therefore cannot have any dependencies on Cinder and/or it's database.