Formatting errors have crept into the manila devref
and have been accumulating over time. It would
be nice to fix these as part of the devref cleanup.
Closes-Bug: #1583850
Partially-implements: bp improve-manila-developer-docs
Change-Id: I7ec954e720b4b88a21e265cd71ea598ea9a5213b
Option "verbose" from group "DEFAULT" is deprecated for removal.
Its value may be silently ignored in the future.
If this option is not set explicitly, there is no such warning.
Furthermore, the default value of verbose is true, so there is no
need to set this value in config files.
And we use oslo_config.generator to generate a sample file.
We'd better fix the doc not encourage user to set verbose=True.
Change-Id: Ie9a68e511425d34cbce04e416f258db3064d0479
There is no single action that is based on debian/ubuntu.
Only pip and Linux tools are used that should be the
same for all platforms.
Trivial-fix
Change-Id: Iecb7474b2bb90ebb4c3965b37ab3a893a8ee1229
I cannot do name resolution of "controller" in the example,
because I cannot understand that the "controller" is variable.
So I think that the "controller" should be written between % and %.
Change-Id: I133bd85c9e1c3a8f491e97f251f17b86642e3a48
With oslo-incubator going away, we need to pull those classes into
the Manila code base, along with their unit tests. This presents a
good opportunity to do some long-needed housecleaning. This commit
does the following:
1. Moves the scheduler classes from openstack.common to manila.
2. Adds the unit tests from olso-incubator into Manila.
3. Removes duplication among the combined scheduler modules.
4. Moves scheduler drivers into a sub-module.
5. Normalizes class and module naming throughout the scheduler.
6. Splits some unit test files so they match the names of the
modules that they test.
7. Converts usage of mox & oslotest to mock & unittest.
8. Adds a few unit tests to boost coverage levels.
Implements: blueprint reorganize-manila-scheduler
Change-Id: I7aa237e17787e89a95bb198093ea9bc9498279cd
To prevent a microversioned client from managing a non-microversioned
Manila server, Manila must update its REST endpoints by adding /v2 for
all microversioned APIs.
This commit does the following:
* Add /v2 to the URL map, connected to all the same /v1 API methods
* Renumber the microversion sequence starting from 2.0
* Update the versions API to reflect v2
* Publish the new endpoint to Keystone in the DevStack plug-in
* Update relevant documentation
* Update Tempest tests for microversions
APIImpact
Co-Authored-By: Andrew Kerr <andrew.kerr@netapp.com>
Closes-Bug: 1488624
Change-Id: I56a516b5f81914557dd2465746629431cfd6deac
As discussed in the Liberty Design Summit "Moving apps to Python 3"
cross-project workshop, the way forward in the near future is to
switch to the pure-python PyMySQL library as a default.
https://etherpad.openstack.org/p/liberty-cross-project-python3
Change-Id: Ic5b8afd5968a3ea9cb32069d289f3c59729d776e
I found some problems with the quick start guide.
* Client version was old
* share-network-create syntax was wrong
* Example conf file left out important project/tenant names
Change-Id: I5360b3dd3a51ef4f1823eaa940e51adf3f437b3d
This doc describes steps that should be performed to install simple Manila
configuration in existing cloud.
It has installation-specific steps that can differ from deployment to
deployment.
Following steps are described here:
- Installation of Manila binaries
- Installation of Manila client
- Registration in Keystone
- Preparation of external files (configs, etc...)
- Basic configuration of Manila
- Setup of DB
- Running services of Manila
- Creation of pilot share
Not covered:
- network plugins configuration
- share drivers-specific configurations to all drivers except Generic driver,
and this one is covered in only small use case.
Change-Id: Ie68d861411358d227b6f7cc3487dffd1e0838e4d
