Add a new tox target to build PDF documentation in accord
with the community goal [0] to have PDF docs available.
Also, only show genindex and search for HTML. These elements
do not make sense within PDF documents.
[0] https://governance.openstack.org/tc/goals/selected/train/pdf-doc-generation.html
Change-Id: Ia75423d1efbec65730130eedf169c458b92b0c9f
This commit reorganizes the doc structure in the way
suggested by doc-migration spec.
Note that user/ is not touched by this commit
as I plan to update it in a subsequent patch
which moves manila-ui user/admin guide from horizon.
Change-Id: I3c644c33cb912397bd1d5ee890f4991ac3e26501
This patch introduces a new directory layout
in doc/source in conformance with the OpenStack
manuals project migration spec [1], moves the
existing content in manila/doc/source into the
new directories, and adjusts index files accordingly.
This is the first step in the migration process
as outlined in the spec.
[1] https://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html
Partial-Bug: #1706181
Needed-By: Iac9a0180a8b1a45f6f1d84020c6d15f457ad92bf
Depends-On: I92cc896bbd505d10c9dc7101bacb4caedf43da8f
Depends-On: Ia750cb049c0f53a234ea70ce1f2bbbb7a2aa9454
Change-Id: I9c378a188f9009a82100f5488a936d43536bd5b6
Separating tabs of single panel to separate panels.
It will reduce amount of redundant calls, because it is very unlikely
that someone will need all tabs at once. Also, it is current approach
that is used by core projects.
Change-Id: I874253e0e9a35ede8239bc1bdf0a330a44ade413
Partially-Implements BluePrint create-share-panel-group
Changes [1] and [2] added new config options in code logic, but
not in settings file. So, add them to settings file too to ease
tracking of configuration options. These two are the only absent
defaults for the moment.
[1] I0c256d0007395e659f804e8874424f4148021ca8
[2] Ia3808486b8604270127c22d45e455e1955b36dba
Change-Id: Ia461c5a5b182d109b3e55696491766043eb0ad2b
Do not show share protocols in Shares drop-down menu if
the backend is not available.
This patch set is a workaround for this bug. We are using the
settings override feature. Operators will need to place a
'enabled_share_protocols: ['proto1', 'proto2', ...]' setting
on the OPENSTACK_MANILA_SETTINGS files.
The correct fix for this bug would be to add a capabilities
endpoint in the controller plane in order to get the available
backends.
Change-Id: I13637491994e6f074e66fe0f3026a303944892ec
Closes-Bug: #1622732
The enabled/ directory allows toggling of panels and plugins
while the local_settings.d/ allows overriding of settings.
We had OPENSTACK_MANILA_SETTINGS dict under enabled/ and for this
reason the settings overriden there were not taking effect.
This patch set moves OPENSTACK_MANILA_SETTINGS under local_settings.d/
Change-Id: Ie4cd49216f1a4a93c5fe1358c97682f8e4044b43
Closes-Bug: #1641624
Instead of manually editing local_settings.py, use the
UPDATE_HORIZON_CONFIG mechanism to set manila_ui overrides.
This simplifies the deployment process of the plugin.
Change-Id: I28b74892f6b400342b66cff8b599a29bf6cc6b56
Replace temporary address of manila-ui project with new constant one in file
README.rst
Closes-Bug: #1450605
Change-Id: I02e3db340069293c2e33b49065589f5090bd6f75
Removed the instructions from the README regarding installing patch
https://review.openstack.org/128133 into horizon since that change has
been merged into horizon
Update the instructions for running the unit test to reflect the fact
that the tests can now be executed directly within the plugin directory
rather than requiring the plugin to be installed and tested within
horizon.
Enable unit tests to be run standalane; that is, without having a
local copy of the horizon source. This is primarly intended for use in
automated builds. The approach, taken from tuskar-ui, is to add an
entry in test-requirements.txt that refers to a source tarball of
horizon which is expanded into the virtual environment, permitting
references to horizon and openstack_dashboard to resolve correctly.
Add additional tooling to support running tests and building virtual
environments to mirror what is done in horizon.
Several links in the README were automatically created by the
cookie-cutter tool, and they will not be valid until the project is
adopted into OpenStack. They are commented out until then.
Tom Barron