Commit Graph

2 Commits

Author SHA1 Message Date
Lucian Petrut f32ea3f0bd Use a separate doc requirements file
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
2020-12-10 10:45:02 +02:00
Lucian Petrut 3d816ede99 Prepare for readthedocs
Since compute-hyperv is not an official OpenStack project, we cannot
host our docs on docs.openstack.org. For this reason, we'll use
readthedocs.

As readthedocs will not use tox, we have to explicitly provide the doc
build requirements that are not included in requirements.txt.
Unfortunately, we'll have to update this file manually at least once
per release.

Also, reathedocs will invoke sphinx-doc from the /doc dir, for which
reason it cannot find etc/compute-hyperv-config-generator.conf. The
according reference is updated, explicitly declaring the namespaces
to be used when generating the config reference.

Change-Id: Idab6f10f92f7f2e40962f1cabaac8691e6c46619
2018-02-07 13:11:16 +02:00