![]() We used a workaround to solve the lack of legacy credentials in our devstack plugin script by sourcing credentials early [1]. This workaround breaks when using the devstack-system-admin persona from the /etc/openstack/clouds.yaml that devstack sets up, because we'd be sourcing project credentials that aren't popped off in time [2]. Cloud profiles work with OSC, we could switch to that in the devstack plugin rather than rely on legacy credential helpers from devstack. The only remaining piece is the group type setup [3] which is expected to be complete soon. [1] https://review.opendev.org/c/openstack/manila/+/818617 [2] https://review.opendev.org/c/openstack/devstack/+/817074 [3] https://review.opendev.org/c/openstack/python-manilaclient/+/805064 Change-Id: Icc15f427cc02054021fa23626ea14e6cd37b18fb Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com> |
||
---|---|---|
.. | ||
files | ||
upgrade | ||
README.rst | ||
apache-manila.template | ||
plugin.sh | ||
settings |
README.rst
Enabling in Devstack
We can enable the manila service in DevStack. For details, please refer to development-environment-devstack, the following steps can be used as a quickstart reference:
Download DevStack
Add this repo as an external repository:
> cat local.conf [[local|localrc]] # Enable manila enable_plugin manila https://opendev.org/openstack/manila # Enable manila ui in the dashboard enable_plugin manila-ui https://opendev.org/openstack/manila-ui
run
stack.sh