Switch to openstackdocstheme 2.2.1 version. Using
this version will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
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: I84774e86b7b834af52ace910cb1924f883e41cb9
Make a few cleanups:
- Remove python 2.7 stanza from setup.py
- Remove obsolete sections from setup.cfg
- Use newer openstackdocstheme version
- Remove install_command from tox.ini, the default is fine
- Cleanup tox.ini, the repo is now python3 only
Change-Id: Ia24cc501831202cb4d710a9a5e9b2fdb8bef070d
Specify the performance metrics that should be generated for
the Python version of the Monasca Persister to be consistent
with the perf metrics that were generated from the Java version.
Story: 2001576
Task: 6525
Change-Id: Ib0e2ad2e4789fc4c7cee33c91485aba644571b72
There are multiple steps necessary here:
- Switch to openstackdocstheme which, unlike the EOL'd oslosphinx theme,
supports Sphinx 2.0. This is mostly trivial, though we do need to set
the 'release' and 'version' options to the empty string since specs,
like release notes and API docs, are unversioned.
- Require yasfb 0.8.0, which adds support for Sphinx 2.0
- Remove configuration for configuration for the 'autodoc' extension,
any builder that isn't HTML or LaTeX, or stuff that duplicates
defaults. All of these were noise that was simply confusing matters.
Change-Id: I41552530a609ba1c7c6b56c1b963fdf1bfb715dc
Monasca Events API was developed to store events
data in Elasticsearch.
There is still a need to collect and publish
Openstack Notifications as Monasca Events.
This commit includes a specification for creating a new Monasca
Events Listener service that would be independent of Ceilometer.
This is being proposed for the Stein cycle.
Monasca Ceilometer project currently publishes ceilometer samples
to Monasca API. An alternate specification proposes to extend Monasca
Ceilometer project and add a new events publisher which would publish
Openstack notifications (or events) to Monasca Events API.
This solution was proposed for Rocky but will not be implemented
as the Ceilometer Events feature has been deprecated on master.
Co-Authored-By: Joseph Davis <joseph.davis@suse.com>
Co-Authored-By: Ashwin Agate <ashwin.agate@suse.com>
Story: 2003023
Task: 23047
Change-Id: I8ed7a19c0565a0cd613866934eb2540ae46c847d
This commit serves as a straw man for merging the Monasca APIs into a
single unified API.
APIImpact
Story: 2003881
Task: 26742
Change-Id: Id08a46bb5b54db5baa5c3595100b73bab85ea8ff
Support differentiable metrics retention policy based on metrics
type. Also outline alternatives.
Change-Id: I915376827604bc692cd26b7ed00812c64ee2e3c0
story: 2001576
Currently in all Python Monasca components the copy of `kafka-python`
library in version 0.9.5 (released on Feb 16, 2016) is used. This
specification describes the process of upgrading the Apache Kafka client
to `confluent-kafka-python`. This will improve the performance and
reliability. Sticking with the old frozen client version is also
unacceptable in terms of security.
Change-Id: I59f3effcdba39199d61d70a201d8e760840d3627
Story: 2003705
Task: 26360
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: Iafb959ea0c81fd0a89faee48949dc0f0af3457b5
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: I5220bfe8496d9578e65c14303d9ab6499f7a5aed
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I8a4bcf45488bf0aaa3f94d058759e5d2d705baef
Story: #2002586
Task: #24312
This commit adds a spec on converting Monasca from SQL scripts
to database migrations.
Change-Id: I398b8e1b5ab9b3529b0e671f197fdec5cf7b8e90
Story: 2001654
Task: 6681
Presently, neither monasca-api nor monasca-log-api use oslo.policy. Instead,
they contain their own policy enforcement code. Without oslo.policy they will
not be able to implement the policy in code community goal for Queens, which
requires the use of oslo mechanisms for defining and enforcing policy. This
spec gives a roadmap for switching monasca-{api,log-api} to using oslo.policy.
Change-Id: Icf9ec728a20ff38cfe29c72acae2df5f4383f0f6
Story: 2001233
Task: 5749
This adds a spec that proposes a separate Keystone domain for agent users
for better security and self-service agent user creation.
It also fixes some build/compatiblity issues for spec compilation.
Change-Id: Id58703a52bff134fdbb22eaac199a4036df0c0b5
Story: 2001214
Task: 5725