39734a70c5
When you run unstack.sh from devstack, other devstack services are stopped and disabled to provide a clean environment for a restack, but manila services are left running. This doesn't matter for CI where a new VM is stood up for each devstack but it's inconvenient for local devstack and if you restack without restarting the services manually the results you see may not actually match the environment you intended. Change-Id: I6761619042e4bc36ec2f1cab4be33cb1b39d00d7
Team and repository tags
MANILA
You have come across an OpenStack shared file system service. It has identified itself as "Manila." It was abstracted from the Cinder project.
- Wiki: https://wiki.openstack.org/wiki/Manila
- Developer docs: https://docs.openstack.org/manila/latest/
Getting Started
If you'd like to run from the master branch, you can clone the git repo:
git clone https://opendev.org/openstack/manila
For developer information please see HACKING.rst
You can raise bugs here https://bugs.launchpad.net/manila
Python client
https://opendev.org/openstack/python-manilaclient
- Documentation for the project can be found at:
https://docs.openstack.org/manila/latest/
- Release notes for the project can be found at:
https://docs.openstack.org/releasenotes/manila/
- Source for the project:
https://opendev.org/openstack/manila
- Bugs:
https://bugs.launchpad.net/manila
- Blueprints:
https://blueprints.launchpad.net/manila
- Design specifications are tracked at: