As per the OpenStack TC decision [1], the doc requirements should
be listed separately.
This also simplifies the requirements handling. At them moment,
we're facing some issues due to conflicting doc related lower
constraints.
While at it, we're bumping the lower constraints based on Nova's
requirements, dropping indirect dependencies which are very difficult
to maintain.
[1] https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: Ifa2d545d1be6615bca1a85c471322c7e9a3da3b3
A recent patch[1] updated the 'unrescue' signature, adding a context
and dropping the 'network_info' parameter.
We'll need to pick up this change.
At the same time, we're re-adding the mock dependency. We're re-using
some of Nova's fixtures and other test helpers, which still use the
3rd party mock lib: [2].
[1] Id5e4b0f26d5a2a93db6a7d96555a2cff29d9a2cfre
[2] http://paste.openstack.org/raw/796530/
Change-Id: I0d46c4df4982e62ff81285a141c8b71bf06bcf15
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I614c930776145ab69a1b08d8affce43cae01f092
flake8 new release 3.8.0 added new checks and gate pep8
job start failing. hacking 3.0.1 fix the pinning of flake8 to
avoid bringing in a new version with new checks.
Though it is fixed in latest hacking but 2.0 and 3.0 has cap for
flake8 as <4.0.0 which mean flake8 new version 3.9.0 can also
break the pep8 job if new check are added.
To avoid similar gate break in future, we need to bump the hacking min
version.
- http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html
Change-Id: I49c423d7e659c31c60684c7ae0792649ec681132
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove python 2.7 stanza from setup.py
- Add requires on python >= 3.6 to setup.cfg so that pypi and pip
know about the requirement
- Update classifiers
- Update requirements, no need for python_version anymore
- Cleanup doc/source/conf.py to remove now obsolete content.
- Use newer openstackdocstheme version
- Move basepython into testenv
Change-Id: I96fe17a0a01b8bcca4dad16889def88305857d37
The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.
Fix problems found.
Update local hacking checks for new flake8.
Remove local vi check, hacking test H106 covers this now.
Remove hacking and friends from lower-constraints, they are not needed
to be installed at run-time.
Change-Id: Id87f8b2d81583a7a67ee1a81c78d3ae40c579c70
Use tox-docs instead of obsolete build-openstack-sphinx-docs job.
Add readme to index to fix RST building.
Update tox.ini for this change,
disable sphinx's option to tread warnings as errors since nova
autogenerated code contains links to nova documents that do not work
when build here. Note that the previous build-sphinx also disabled
warnings, so this is no change in behaviour in jobs.
Update old pike link to current stein.
Update requirements for global-requirements change.
Remove unneeded json test from doc environment, there are no json files in the
doc directory and thus the test fails.
Change-Id: Id57f462ff4f1fa843051721aa78bb332b8a37fcd
According to Openstack summit session [1],
stestr is maintained project to which all Openstack projects should migrate.
Let's switch to stestr as other projects have already moved to it.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: Ic328c6d6f47fabd3a9b8c013e60dfd44e9d38ac1
The oslosphinx theme has been deprecated. Besides, we're currently
inconsistent with the other project docs themes.
Change-Id: I6a7a105d8b689ff5e5ca2f7829ce06d166e8db2e
This change adds an automatically generated config sample to the
compute-hyperv docs.
The config sample is generated each time the docs are built, using
the oslo.config sphinxconfiggen extension.
Change-Id: Id8fa0311d653a438b143018f032e32d3eb6bbaa8
Related-Bug: #1731511
Until now, even if there were multiple paths on which we could
access a volume, we were estabilishing a single iSCSI session.
This patch changes this, so we may use all the targets/portals
that we retrieve in the connection info.
Also, a config option was added so that the deployer can request
which initiators will be used for estabilishing the session, for
example forcing some hardware initiators to be used. If none is
explicitly requested, we let the iSCSI initiator service pick one.
This will also require the MPIO service to be enabled and properly
configured, in order to claim the disks.
Change-Id: Ia5c0aa81d56bb862b3b30de4b782d9d1d15d44f5
Updates vmops and tests to use oslo_utils and oslo_service.
Updates test_vhdutils.py as the requirements causes an
unit test to fail.
Change-Id: Ifaf070c124047cfa8ce38fb1ea10fc930390f9c7