Browse Source

Merge "Add Priorities page for Stein"

Zuul 7 months ago
parent
commit
27ce5fdd54
2 changed files with 113 additions and 0 deletions
  1. 2
    0
      doc/source/index.rst
  2. 111
    0
      priorities/stein-priorities.rst

+ 2
- 0
doc/source/index.rst View File

@@ -13,6 +13,7 @@ to focus on for the upcoming release. This is the output of those discussions:
13 13
 .. toctree::
14 14
    :glob:
15 15
    :maxdepth: 1
16
+   :reversed:
16 17
 
17 18
    priorities/*
18 19
 
@@ -24,6 +25,7 @@ Here you can find the specs, and spec template, for each release:
24 25
 .. toctree::
25 26
    :glob:
26 27
    :maxdepth: 1
28
+   :reversed:
27 29
 
28 30
    specs/queens/index
29 31
    specs/rocky/index

+ 111
- 0
priorities/stein-priorities.rst View File

@@ -0,0 +1,111 @@
1
+.. _stein-priorities:
2
+
3
+=========================
4
+Stein Project Priorities
5
+=========================
6
+
7
+List of priorities the Monasca drivers team is prioritizing in Stein.
8
+
9
+The owners listed are responsible for tracking the status of that work and
10
+helping get that work done. They are not the only contributors to this work,
11
+and not necessarily doing most of the coding!
12
+
13
+The implementation progress on these priorities and other identified important
14
+tasks is tracked in `this board`_.
15
+
16
+.. _this board: https://storyboard.openstack.org/#!/board/111
17
+
18
+Essential 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
+
37
+High 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
+
54
+Details
55
+~~~~~~~
56
+
57
+Kafka client upgrade
58
+--------------------
59
+
60
+Currently, in all Python Monasca components, the copy of `kafka-python` library
61
+in version 0.9.5 (released on Feb 16, 2016) is used. Sticking with the old
62
+frozen client version is also unacceptable in terms of security. The goal is to
63
+upgrade the Apache Kafka client to `confluent-kafka-python`. This will
64
+dramatically improve the performance and reliability.
65
+
66
+Merge Monasca APIs
67
+------------------
68
+
69
+The goal is to merge all Monasca APIs into a single unified API to reduce
70
+maintenance overhead, make it easier for developers to add new features and
71
+improve the user experience.
72
+
73
+Monasca Events Agent
74
+--------------------
75
+
76
+The goal is to extend Monasca Ceilometer project and add a new events publisher
77
+which will publish Openstack notifications (or events) to Monasca Events API.
78
+
79
+Add query endpoint for logs/events
80
+----------------------------------
81
+
82
+`Add support`_ for querying ElasticSearch via the Monasca API to support tenant
83
+scoped access to logs and events. This should include accessing the logs via
84
+Grafana.
85
+
86
+.. _Add support: https://blueprints.launchpad.net/monasca/+spec/log-query-api
87
+
88
+Run under Python 3 by default
89
+-----------------------------
90
+
91
+As OpenStack Technical Committee agreed in the `Python2 Deprecation Timeline`_
92
+resolution, the next phase of our adoption of Python 3 is to begin running all
93
+jobs using Python 3 by default and only using Python 2 to test operating under
94
+Python 2 (via unit, functional, or integration tests). This goal describes the
95
+activities 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
+
100
+Pre upgrade checks
101
+------------------
102
+
103
+The goal is to provide an `upgrade check command`_ which would perform any
104
+upgrade validation that can be automated.
105
+
106
+.. _upgrade check command: https://governance.openstack.org/tc/goals/stein/upgrade-checkers.html
107
+
108
+Metrics retention policy
109
+------------------------
110
+
111
+The goal is to add a new API for managing the mapping of metrics to TTL values.

Loading…
Cancel
Save