This patch moves EMC drivers under dell_emc folder and
changes vendor name to "Dell EMC".
The base driver remains as EMCShareDriver.
DocImpact
UpgradeImpact
Implements-blueprint: move-emc-driver-to-dell-emc-folder
Change-Id: I799c7fcb59fbe887045fe81beb1e257586ba2f0e
Add new neutron plugin which enables port bind actions for network
fabrics. This driver waits until all ports are in state "active"
and sets the binding host flag. Default vNIC type is set to
"baremetal" in order to benefit from the code already in place for
Ironic. It's also possible to switch to 'normal' which assumes an
neutron agent in place.
The feature can be tested using the docker driver.
DocImpact
Co-Authored-By: Daniel Gonzalez <daniel@gonzalez-nothnagel.de>
Partially-Implements: bp manila-hpb-support
Change-Id: I3156d7468d48f84f1b46885780a2426f9b99a387
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
Glossary should be used to describe common terms used in Manila's
documentation. Starting using it for "manila-share", "manila-api" and
"manila-scheduler".
Change-Id: I288332f5b599c9c78d45f0102e4d2a20753af3a6
The configuration example for multiple backends is visibly wrong.
Use a literal code block (marked as such with "::" and indentation) to
show the example configuration.
Change-Id: If994eddee9e9cf586e4c629d984bc4bf479f4e5b
The correct option name is enabled_share_backends.
This change removes the obsolete option and corrects
the documentation to reference the correct name.
Change-Id: I616f6006966f33b261e8ead43bd7757c03797bef
Closes-Bug: #1425237
The Manila cDOT driver is a single file exceeding 1200 lines. It contains
multiple things (driver code, protocol helpers, ZAPI invocation code,
options) that should be split apart to allow for easier maintenance and
readability and add the potential for code sharing when we reintroduce
a 7-mode driver, add a single-SVM cDOT driver, etc.
We recently refactored NetApp's DOT Cinder drivers into a 4-layer
structure (interface, library, client, API) that separates concerns and
achieves the goals set forth above. This commit satisfies a plan to
do the same thing in Manila. The implementation steps are:
1. Update directory structure to match that of the Cinder NetApp drivers
2. Create driver interface shim
3. Move driver code to library (with base & C-mode classes, to allow for
7-mode code sharing later)
4. Move protocol helpers to separate files (already organized by base &
C-mode classes)
5. Split out ZAPI code to client layer (with base & C-mode classes, to
allow for 7-mode code sharing later)
6. Implement NetApp driver factory as in Cinder
7. Implement common NetApp options file as in Cinder
8. Implement cDOT API call optimizations
9. Update all unit tests as needed
Note that this patch appears to treble the total number of code lines.
This is due to the addition of many more unit tests plus a large amount
of fake controller API data to feed the API client tests.
Implements: blueprint netapp-manila-cdot-driver-refactoring
Closes-Bug: #1410317
Partial-Bug: #1396953
Closes-Bug: #1370965
Closes-Bug: #1418690
Closes-Bug: #1418696
Change-Id: I3fc0d09adf84a3708f110a89a7c8c760f4ce3588
Fix the following that shows up when running "python setup.py
build_sphinx":
manila/doc/source/adminref/index.rst:16:
WARNING: toctree contains reference to nonexisting document
u'adminref/launchpad'
manila/doc/source/adminref/index.rst:16:
WARNING: toctree contains reference to nonexisting document
u'adminref/gerrit'
manila/doc/source/adminref/index.rst:16:
WARNING: toctree contains reference to nonexisting document
u'adminref/jenkins'
checking consistency...
manila/doc/source/adminref/index.rst::
WARNING: document isn't included in any toctree
Cleanup adminref/index.rst file and remove content that is duplicated
from the devref/index.rst and not relevant here.
Change-Id: I57accea0f041ac59e507e4cf6461d2239f60b3b7
Add doc for an Introduction to Manila dealing with the fundamentals and basic
terminology used with respect to Manila from an Admin perspective.
Also, create a directory for an Admin ref along with a sample index.rst.
Change-Id: I1847f291750227927a747b5ea224a6861310a529
