summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorZuul <zuul@review.openstack.org>2018-10-14 17:59:59 +0000
committerGerrit Code Review <review@openstack.org>2018-10-14 17:59:59 +0000
commit27ce5fdd54576af4e92fe594fc8a04c80fe3adbf (patch)
treed854e799d2321d860f3194c9f560c77940fe2012
parenta4674a5e7f606898d568c5391a56d28f2350b447 (diff)
parent25b2ff220beb65988435dd82c9e884b2b06904b6 (diff)
Merge "Add Priorities page for Stein"
-rw-r--r--doc/source/index.rst2
-rw-r--r--priorities/stein-priorities.rst111
2 files changed, 113 insertions, 0 deletions
diff --git a/doc/source/index.rst b/doc/source/index.rst
index 8fa553f..d94e352 100644
--- a/doc/source/index.rst
+++ b/doc/source/index.rst
@@ -13,6 +13,7 @@ to focus on for the upcoming release. This is the output of those discussions:
13.. toctree:: 13.. toctree::
14 :glob: 14 :glob:
15 :maxdepth: 1 15 :maxdepth: 1
16 :reversed:
16 17
17 priorities/* 18 priorities/*
18 19
@@ -24,6 +25,7 @@ Here you can find the specs, and spec template, for each release:
24.. toctree:: 25.. toctree::
25 :glob: 26 :glob:
26 :maxdepth: 1 27 :maxdepth: 1
28 :reversed:
27 29
28 specs/queens/index 30 specs/queens/index
29 specs/rocky/index 31 specs/rocky/index
diff --git a/priorities/stein-priorities.rst b/priorities/stein-priorities.rst
new file mode 100644
index 0000000..7dc34f0
--- /dev/null
+++ b/priorities/stein-priorities.rst
@@ -0,0 +1,111 @@
1.. _stein-priorities:
2
3=========================
4Stein Project Priorities
5=========================
6
7List of priorities the Monasca drivers team is prioritizing in Stein.
8
9The owners listed are responsible for tracking the status of that work and
10helping get that work done. They are not the only contributors to this work,
11and not necessarily doing most of the coding!
12
13The implementation progress on these priorities and other identified important
14tasks is tracked in `this board`_.
15
16.. _this board: https://storyboard.openstack.org/#!/board/111
17
18Essential Priorities
19~~~~~~~~~~~~~~~~~~~~
20
21+-----------------------------------------------+-----------------------------+
22| Title | Owners |
23+===============================================+=============================+
24| `Kafka client upgrade`_ | witek |
25+-----------------------------------------------+-----------------------------+
26| `Monasca Events Agent`_ | joadavis, aagate |
27+-----------------------------------------------+-----------------------------+
28| `Merge Monasca APIs`_ | dougsz |
29+-----------------------------------------------+-----------------------------+
30| `Add query endpoint for logs/events`_ | dougsz |
31+-----------------------------------------------+-----------------------------+
32| `Run under Python 3 by default`_ | adriancz, Dobroslaw |
33+-----------------------------------------------+-----------------------------+
34| `Pre upgrade checks`_ | joadavis |
35+-----------------------------------------------+-----------------------------+
36
37High Priorities
38~~~~~~~~~~~~~~~
39
40+---------------------------------------------+-------------------------+
41| Title | Owners |
42+=============================================+=========================+
43| Auto-scaling with Heat | witek |
44+---------------------------------------------+-------------------------+
45| `Metrics retention policy`_ | joadavis |
46+---------------------------------------------+-------------------------+
47| Documentation refresh | |
48+---------------------------------------------+-------------------------+
49| Deployment in OpenStack Helm | srwilkers |
50+---------------------------------------------+-------------------------+
51| Integration with Watcher | yushiro |
52+---------------------------------------------+-------------------------+
53
54Details
55~~~~~~~
56
57Kafka client upgrade
58--------------------
59
60Currently, in all Python Monasca components, the copy of `kafka-python` library
61in version 0.9.5 (released on Feb 16, 2016) is used. Sticking with the old
62frozen client version is also unacceptable in terms of security. The goal is to
63upgrade the Apache Kafka client to `confluent-kafka-python`. This will
64dramatically improve the performance and reliability.
65
66Merge Monasca APIs
67------------------
68
69The goal is to merge all Monasca APIs into a single unified API to reduce
70maintenance overhead, make it easier for developers to add new features and
71improve the user experience.
72
73Monasca Events Agent
74--------------------
75
76The goal is to extend Monasca Ceilometer project and add a new events publisher
77which will publish Openstack notifications (or events) to Monasca Events API.
78
79Add query endpoint for logs/events
80----------------------------------
81
82`Add support`_ for querying ElasticSearch via the Monasca API to support tenant
83scoped access to logs and events. This should include accessing the logs via
84Grafana.
85
86.. _Add support: https://blueprints.launchpad.net/monasca/+spec/log-query-api
87
88Run under Python 3 by default
89-----------------------------
90
91As OpenStack Technical Committee agreed in the `Python2 Deprecation Timeline`_
92resolution, the next phase of our adoption of Python 3 is to begin running all
93jobs using Python 3 by default and only using Python 2 to test operating under
94Python 2 (via unit, functional, or integration tests). This goal describes the
95activities needed to move us to this `python 3 first`_ state.
96
97.. _Python2 Deprecation Timeline: https://governance.openstack.org/tc/resolutions/20180529-python2-deprecation-timeline.html#python2-deprecation-timeline
98.. _Python 3 first: https://governance.openstack.org/tc/goals/stein/python3-first.html
99
100Pre upgrade checks
101------------------
102
103The goal is to provide an `upgrade check command`_ which would perform any
104upgrade validation that can be automated.
105
106.. _upgrade check command: https://governance.openstack.org/tc/goals/stein/upgrade-checkers.html
107
108Metrics retention policy
109------------------------
110
111The goal is to add a new API for managing the mapping of metrics to TTL values.