summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authoriberezovskiy <iberezovskiy@mirantis.com>2015-07-28 19:47:02 +0300
committerNadya Shakhat <nprivalova@mirantis.com>2015-11-09 16:48:13 +0300
commit1ef0e13a5002df8521882db7a32ebc37a1b125a8 (patch)
tree06d58916733f6f7476850d82dd9c86aeaf5f0dd2
parenta53478afe9d379403392a912a9b0134955b539d8 (diff)
Add documentation for Ceilometer Redis plugin
* Add LICENSE * Add README with information about plugin * Add /doc directory with user-guide, installation-guide files Partially implements: blueprint ceilometer-central-agent-ha Change-Id: I918c7542be8d5311e28ea2a87bb792127fcc70c9
Notes
Notes (review): Verified+2: Jenkins Code-Review+2: Ivan Berezovskiy <iberezovskiy@mirantis.com> Workflow+1: Ivan Berezovskiy <iberezovskiy@mirantis.com> Code-Review+1: Vitaly Gusev <vgusev@mirantis.com> Submitted-by: Jenkins Submitted-at: Mon, 09 Nov 2015 14:05:20 +0000 Reviewed-on: https://review.openstack.org/206620 Project: openstack/fuel-plugin-ceilometer-redis Branch: refs/heads/master
-rw-r--r--LICENSE202
-rw-r--r--README.md37
-rw-r--r--doc/content/description.rst35
-rw-r--r--doc/content/guide.rst77
-rw-r--r--doc/content/images/redis-plugin-on.pngbin0 -> 107638 bytes
-rw-r--r--doc/content/images/redis-plugin.pngbin0 -> 70618 bytes
-rw-r--r--doc/content/installation.rst35
-rw-r--r--doc/content/tests.rst0
-rw-r--r--specs/ceilometer-redis.rst258
9 files changed, 644 insertions, 0 deletions
diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000..e06d208
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,202 @@
1Apache License
2 Version 2.0, January 2004
3 http://www.apache.org/licenses/
4
5 TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
7 1. Definitions.
8
9 "License" shall mean the terms and conditions for use, reproduction,
10 and distribution as defined by Sections 1 through 9 of this document.
11
12 "Licensor" shall mean the copyright owner or entity authorized by
13 the copyright owner that is granting the License.
14
15 "Legal Entity" shall mean the union of the acting entity and all
16 other entities that control, are controlled by, or are under common
17 control with that entity. For the purposes of this definition,
18 "control" means (i) the power, direct or indirect, to cause the
19 direction or management of such entity, whether by contract or
20 otherwise, or (ii) ownership of fifty percent (50%) or more of the
21 outstanding shares, or (iii) beneficial ownership of such entity.
22
23 "You" (or "Your") shall mean an individual or Legal Entity
24 exercising permissions granted by this License.
25
26 "Source" form shall mean the preferred form for making modifications,
27 including but not limited to software source code, documentation
28 source, and configuration files.
29
30 "Object" form shall mean any form resulting from mechanical
31 transformation or translation of a Source form, including but
32 not limited to compiled object code, generated documentation,
33 and conversions to other media types.
34
35 "Work" shall mean the work of authorship, whether in Source or
36 Object form, made available under the License, as indicated by a
37 copyright notice that is included in or attached to the work
38 (an example is provided in the Appendix below).
39
40 "Derivative Works" shall mean any work, whether in Source or Object
41 form, that is based on (or derived from) the Work and for which the
42 editorial revisions, annotations, elaborations, or other modifications
43 represent, as a whole, an original work of authorship. For the purposes
44 of this License, Derivative Works shall not include works that remain
45 separable from, or merely link (or bind by name) to the interfaces of,
46 the Work and Derivative Works thereof.
47
48 "Contribution" shall mean any work of authorship, including
49 the original version of the Work and any modifications or additions
50 to that Work or Derivative Works thereof, that is intentionally
51 submitted to Licensor for inclusion in the Work by the copyright owner
52 or by an individual or Legal Entity authorized to submit on behalf of
53 the copyright owner. For the purposes of this definition, "submitted"
54 means any form of electronic, verbal, or written communication sent
55 to the Licensor or its representatives, including but not limited to
56 communication on electronic mailing lists, source code control systems,
57 and issue tracking systems that are managed by, or on behalf of, the
58 Licensor for the purpose of discussing and improving the Work, but
59 excluding communication that is conspicuously marked or otherwise
60 designated in writing by the copyright owner as "Not a Contribution."
61
62 "Contributor" shall mean Licensor and any individual or Legal Entity
63 on behalf of whom a Contribution has been received by Licensor and
64 subsequently incorporated within the Work.
65
66 2. Grant of Copyright License. Subject to the terms and conditions of
67 this License, each Contributor hereby grants to You a perpetual,
68 worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69 copyright license to reproduce, prepare Derivative Works of,
70 publicly display, publicly perform, sublicense, and distribute the
71 Work and such Derivative Works in Source or Object form.
72
73 3. Grant of Patent License. Subject to the terms and conditions of
74 this License, each Contributor hereby grants to You a perpetual,
75 worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76 (except as stated in this section) patent license to make, have made,
77 use, offer to sell, sell, import, and otherwise transfer the Work,
78 where such license applies only to those patent claims licensable
79 by such Contributor that are necessarily infringed by their
80 Contribution(s) alone or by combination of their Contribution(s)
81 with the Work to which such Contribution(s) was submitted. If You
82 institute patent litigation against any entity (including a
83 cross-claim or counterclaim in a lawsuit) alleging that the Work
84 or a Contribution incorporated within the Work constitutes direct
85 or contributory patent infringement, then any patent licenses
86 granted to You under this License for that Work shall terminate
87 as of the date such litigation is filed.
88
89 4. Redistribution. You may reproduce and distribute copies of the
90 Work or Derivative Works thereof in any medium, with or without
91 modifications, and in Source or Object form, provided that You
92 meet the following conditions:
93
94 (a) You must give any other recipients of the Work or
95 Derivative Works a copy of this License; and
96
97 (b) You must cause any modified files to carry prominent notices
98 stating that You changed the files; and
99
100 (c) You must retain, in the Source form of any Derivative Works
101 that You distribute, all copyright, patent, trademark, and
102 attribution notices from the Source form of the Work,
103 excluding those notices that do not pertain to any part of
104 the Derivative Works; and
105
106 (d) If the Work includes a "NOTICE" text file as part of its
107 distribution, then any Derivative Works that You distribute must
108 include a readable copy of the attribution notices contained
109 within such NOTICE file, excluding those notices that do not
110 pertain to any part of the Derivative Works, in at least one
111 of the following places: within a NOTICE text file distributed
112 as part of the Derivative Works; within the Source form or
113 documentation, if provided along with the Derivative Works; or,
114 within a display generated by the Derivative Works, if and
115 wherever such third-party notices normally appear. The contents
116 of the NOTICE file are for informational purposes only and
117 do not modify the License. You may add Your own attribution
118 notices within Derivative Works that You distribute, alongside
119 or as an addendum to the NOTICE text from the Work, provided
120 that such additional attribution notices cannot be construed
121 as modifying the License.
122
123 You may add Your own copyright statement to Your modifications and
124 may provide additional or different license terms and conditions
125 for use, reproduction, or distribution of Your modifications, or
126 for any such Derivative Works as a whole, provided Your use,
127 reproduction, and distribution of the Work otherwise complies with
128 the conditions stated in this License.
129
130 5. Submission of Contributions. Unless You explicitly state otherwise,
131 any Contribution intentionally submitted for inclusion in the Work
132 by You to the Licensor shall be under the terms and conditions of
133 this License, without any additional terms or conditions.
134 Notwithstanding the above, nothing herein shall supersede or modify
135 the terms of any separate license agreement you may have executed
136 with Licensor regarding such Contributions.
137
138 6. Trademarks. This License does not grant permission to use the trade
139 names, trademarks, service marks, or product names of the Licensor,
140 except as required for reasonable and customary use in describing the
141 origin of the Work and reproducing the content of the NOTICE file.
142
143 7. Disclaimer of Warranty. Unless required by applicable law or
144 agreed to in writing, Licensor provides the Work (and each
145 Contributor provides its Contributions) on an "AS IS" BASIS,
146 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147 implied, including, without limitation, any warranties or conditions
148 of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149 PARTICULAR PURPOSE. You are solely responsible for determining the
150 appropriateness of using or redistributing the Work and assume any
151 risks associated with Your exercise of permissions under this License.
152
153 8. Limitation of Liability. In no event and under no legal theory,
154 whether in tort (including negligence), contract, or otherwise,
155 unless required by applicable law (such as deliberate and grossly
156 negligent acts) or agreed to in writing, shall any Contributor be
157 liable to You for damages, including any direct, indirect, special,
158 incidental, or consequential damages of any character arising as a
159 result of this License or out of the use or inability to use the
160 Work (including but not limited to damages for loss of goodwill,
161 work stoppage, computer failure or malfunction, or any and all
162 other commercial damages or losses), even if such Contributor
163 has been advised of the possibility of such damages.
164
165 9. Accepting Warranty or Additional Liability. While redistributing
166 the Work or Derivative Works thereof, You may choose to offer,
167 and charge a fee for, acceptance of support, warranty, indemnity,
168 or other liability obligations and/or rights consistent with this
169 License. However, in accepting such obligations, You may act only
170 on Your own behalf and on Your sole responsibility, not on behalf
171 of any other Contributor, and only if You agree to indemnify,
172 defend, and hold each Contributor harmless for any liability
173 incurred by, or claims asserted against, such Contributor by reason
174 of your accepting any such warranty or additional liability.
175
176 END OF TERMS AND CONDITIONS
177
178 APPENDIX: How to apply the Apache License to your work.
179
180 To apply the Apache License to your work, attach the following
181 boilerplate notice, with the fields enclosed by brackets "{}"
182 replaced with your own identifying information. (Don't include
183 the brackets!) The text should be enclosed in the appropriate
184 comment syntax for the file format. We also recommend that a
185 file or class name and description of purpose be included on the
186 same "printed page" as the copyright notice for easier
187 identification within third-party archives.
188
189 Copyright {yyyy} {name of copyright owner}
190
191 Licensed under the Apache License, Version 2.0 (the "License");
192 you may not use this file except in compliance with the License.
193 You may obtain a copy of the License at
194
195 http://www.apache.org/licenses/LICENSE-2.0
196
197 Unless required by applicable law or agreed to in writing, software
198 distributed under the License is distributed on an "AS IS" BASIS,
199 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200 See the License for the specific language governing permissions and
201 limitations under the License.
202
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..e7576a8
--- /dev/null
+++ b/README.md
@@ -0,0 +1,37 @@
1Ceilometer Redis plugin
2=======================
3
4Provides a mechanism to allow Ceilometer agents to be horizontally scaled out
5and to balance workload between corresponding agents. The current plugin version
6provides this mechanism *only* for Central agent.
7
8Building the plugin
9-------------------
10
111. Clone the fuel-plugin repo:
12
13 ``git clone https://review.openstack.org/openstack/fuel-plugin-ceilometer-redis``
14
152. Install the Fuel Plugin Builder:
16
17 ``pip install fuel-plugin-builder``
18
193. Build Ceilometer Redis Fuel plugin:
20
21 ``fpb --build fuel-plugin-ceilometer-redis/``
22
234. The ceilometer-redis-<x.x.x>.rpm plugin package will be created in the plugin folder
24 (fuel-plugin-ceilometer-redis/).
25
265. Move this file to the Fuel Master node with secure copy (scp):
27
28 ``scp fuel-plugin-ceilometer-redis/ceilometer-redis-<x.x.x>.rpm root@:<the_Fuel_Master_node_IP address>:/tmp``
29 ``ssh root@:<the_Fuel_Master_node_IP address>``
30 ``cd /tmp``
31
326. Install the Ceilometer Redis plugin:
33
34 ``fuel plugins --install ceilometer-redis-<x.x.x>.rpm``
35
367. Plugin is ready to be used and can be enabled on the Settings tab of the Fuel web UI.
37
diff --git a/doc/content/description.rst b/doc/content/description.rst
new file mode 100644
index 0000000..2a219cd
--- /dev/null
+++ b/doc/content/description.rst
@@ -0,0 +1,35 @@
1Ceilometer Redis plugin
2=======================
3
4Ceilometer Redis Plugin provides a coordination mechanism for
5`Ceilometer agents <https://ceilometer.readthedocs.org/en/latest/architecture.html>`_.
6The first version of plugin will support only `Central Agent <https://ceilometer.readthedocs.org/en/latest/glossary.html#term-central-agent>`_.
7It uses `tooz library <http://docs.openstack.org/developer/tooz/>`_ with
8`Redis backend <http://redis.io>`_ to provide a set of resources
9to be polled for each Central agent. The plugin also changes deployment of Ceilometer central agent:
10now every controller has its own running ceilometer central service
11which are joined into coordination group. These changes in deployment will be done automatically.
12It also configures redis-server under pacemaker to monitor its process. The plugin configures
13`redis-sentinel <http://redis.io/topics/sentinel>`_ to monitor the state of redis cluster,
14to elect new master during failovers, to forward ceilometer agents to new elected redis master, to organize sync between redis nodes.
15
16
17Requirements
18------------
19
20======================= ================
21Requirement Version/Comment
22======================= ================
23Fuel 7.0
24tooz <0.14.0,>=0.13.1
25======================= ================
26
27Limitations
28-----------
29
30* The plugin version 1.0.0 provides coordination only for Agent Central service.
31 Alarm evaluator and Notification agent will be supported in the next plugin
32 version.
33
34.. include:: installation.rst
35.. include:: guide.rst
diff --git a/doc/content/guide.rst b/doc/content/guide.rst
new file mode 100644
index 0000000..e91f88a
--- /dev/null
+++ b/doc/content/guide.rst
@@ -0,0 +1,77 @@
1User Guide
2==========
3
4Once the Ceilometer Redis plugin plugin has been installed (following `Installation Guide`_), you can
5create *OpenStack* environments with Ceilometer whose Central agent works in workload_partitioned mode.
6
7Ceilometer installation
8-----------------------
9
10This plugin was created to provide partitioning for Ceilometer services. So its
11usage is senseless without Ceilometer installed.
12So, you will need to `create a new OpenStack environment <https://docs.mirantis.com/openstack/fuel/fuel-7.0/user-guide.html#create-a-new-openstack-environment>`_
13with `Ceilometer <https://docs.mirantis.com/openstack/fuel/fuel-7.0/user-guide.html#related-projects>`_ using the Fuel UI Wizard.
14
15
16Plugin configuration
17--------------------
18
19#. First of all, make sure that plugin was successfully installed.
20 Go to the *Plugins* tab. You should see the following:
21
22 .. image:: images/redis-plugin.png
23 :width: 100%
24
25#. The next step is enable the plugin. Go to *Environments* tab and
26 select the *Redis plugin for Ceilometer* checkbox:
27
28 .. image:: images/redis-plugin-on.png
29 :width: 100%
30
31#. Run `network verification check <https://docs.mirantis.com/openstack/fuel/fuel-7.0/user-guide.html#verify-networks>`_.
32
33#. Press `Deploy button <https://docs.mirantis.com/openstack/fuel/fuel-7.0/user-guide.html#deploy-changes>`_ to once you are done with environment configuration.
34
35
36How to check that plugin works
37------------------------------
38#. Check that ceilometer-agent-central service is running on each controller. Run ``pcs resource``
39 and you should see the following in the output::
40
41 Clone Set: clone_p_ceilometer-agent-central [p_ceilometer-agent-central]
42 Started: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ]
43
44
45 ``Started`` list should contain all controllers.
46
47#. Check that samples are not duplicated. For this purpose you may choose
48 any metric collected by central agent. All these metrics may be found here
49 `Measurements <http://docs.openstack.org/admin-guide-cloud/telemetry-measurements.html>`_ .
50 You may choose any section *except* OpenStack Compute and then select metric with 'Pollster' Origin.
51 For example, let's choose storage.objects.
52
53 Plugin works *correctly* if you see one sample for each resource every polling_interval (1 minute in this example)::
54
55 root@node-2:~# ceilometer sample-list -m storage.objects -l 10| grep storage.objects
56 | 65e486c734394d3ea321ae72639ebe91 | storage.objects | gauge | 0.0 | object | 2015-11-05T10:32:27 |
57 | 65e486c734394d3ea321ae72639ebe91 | storage.objects | gauge | 0.0 | object | 2015-11-05T10:31:29 |
58
59
60
61 Plugin works *incorrectly* if there are duplications. In this example is seen that every
62 ``polling_interval`` there are 3 samples about one resource::
63
64 root@node-2:~# ceilometer sample-list -m storage.objects -l 20| grep storage.objects
65 | 65e486c734394d3ea321ae72639ebe91 | storage.objects | gauge | 0.0 | object ....|
66 | 65e486c734394d3ea321ae72639ebe91 | storage.objects | gauge | 0.0 | object ....|
67 | 65e486c734394d3ea321ae72639ebe91 | storage.objects | gauge | 0.0 | object ....|
68 | 65e486c734394d3ea321ae72639ebe91 | storage.objects | gauge | 0.0 | object ....|
69 | 65e486c734394d3ea321ae72639ebe91 | storage.objects | gauge | 0.0 | object ....|
70 | 65e486c734394d3ea321ae72639ebe91 | storage.objects | gauge | 0.0 | object ....|
71
72 .... 2015-11-05T10:27:37 |
73 .... 2015-11-05T10:27:26 |
74 .... 2015-11-05T10:27:17 |
75 .... 2015-11-05T10:26:38 |
76 .... 2015-11-05T10:26:26 |
77 .... 2015-11-05T10:26:17 |
diff --git a/doc/content/images/redis-plugin-on.png b/doc/content/images/redis-plugin-on.png
new file mode 100644
index 0000000..b37e9e5
--- /dev/null
+++ b/doc/content/images/redis-plugin-on.png
Binary files differ
diff --git a/doc/content/images/redis-plugin.png b/doc/content/images/redis-plugin.png
new file mode 100644
index 0000000..9978778
--- /dev/null
+++ b/doc/content/images/redis-plugin.png
Binary files differ
diff --git a/doc/content/installation.rst b/doc/content/installation.rst
new file mode 100644
index 0000000..9715e29
--- /dev/null
+++ b/doc/content/installation.rst
@@ -0,0 +1,35 @@
1
2Installation Guide
3==================
4
5Install the Plugin
6------------------
7
8To install the Redis plugin:
9
10#. Download the Redis plugin from the
11 `Fuel Plugins Catalog <https://www.mirantis.com/products/openstack-drivers-and-plugins/fuel-plugins/>`_.
12
13#. Move the plugin's rpm to the
14 `Fuel Master node <https://docs.mirantis.com/openstack/fuel/fuel-7.0/quickstart-guide.html#quickstart-guide>`_ with secure copy (scp)::
15
16 scp fuel-plugin-ceilometer-redis/ceilometer-redis-1.0-1.0.0-1.noarch.rpm /
17 root@:<the_Fuel_Master_node_IP address>:/tmp
18
19
20#. Log into the Fuel Master node and install the Ceilometer Redis plugin::
21
22 ssh root@:<the_Fuel_Master_node_IP address>
23 cd /tmp
24 fuel plugins --install ceilometer-redis-1.0-1.0.0-1.noarch.rpm
25
26
27#. Verify that the plugin is installed correctly::
28
29 [root@fuel-master ~]# fuel plugins list
30 id | name | version | package_version
31 ---|------------------|---------|----------------
32 4 | ceilometer-redis | 1.0.0 | 2.0.0
33
34
35
diff --git a/doc/content/tests.rst b/doc/content/tests.rst
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/doc/content/tests.rst
diff --git a/specs/ceilometer-redis.rst b/specs/ceilometer-redis.rst
new file mode 100644
index 0000000..68851ba
--- /dev/null
+++ b/specs/ceilometer-redis.rst
@@ -0,0 +1,258 @@
1..
2 This work is licensed under a Creative Commons Attribution 3.0 Unported
3 License.
4
5 http://creativecommons.org/licenses/by/3.0/legalcode
6
7==============================================
8Add central agent HA and workload partitioning
9==============================================
10
11https://blueprints.launchpad.net/fuel/+spec/ceilometer-central-agent-ha
12
13Implement Redis installation and using it as a coordination backend
14for ceilometer central agents
15
16Problem description
17===================
18
19A detailed description of the problem:
20
21* Currently there are several Ceilometer services which do not support workload
22 partitioning in MOS: central agent, alarm evaluator and agent notification. During
23 Juno release cycle workload partitioning for central agent was implemented.
24 In Kilo, partition coordination was introduced to alarm evaluator and agent
25 notification. In Liberty, coordination for notification agent was further improved.
26 Thus, it should be supported in MOS.
27 For this purpose we should provide tooz library support. This library is responsible for
28 coordination between services and supports several backends: zookeeper, redis, memcached.
29 Redis was chosen as the tooz backend in MOS.
30
31Proposed change
32===============
33
34Support for Ceilometer services coordination is an experimental feature and it was
35decided to implement it as a fuel plugin.
36
37Its implementation requires the following things to be done:
38* Implement Redis installation on controller nodes in HA mode
39* Prepare Redis packages and their dependencies
40* Enable partitioning in config for ceilometer central agents
41* Enable partitioning in config for ceilometer alarm evaluator
42* Enable partitioning in config for ceilometer notification agents
43
44Installation diagram for central agent is below. The schemas for alarm-evaluator and
45notification agent are similar
46
47::
48
49 +---------------------+
50 | |
51 | +---------------+ |
52 | | ceilometer +-------------------------+
53 | | central agent | | |
54 | +---------------+ | |
55 | | |
56 | Primary controller | |
57 | | |
58 | +---------------+ | |
59 | | redis <------------------------------+
60 | | master | | | |
61 | +---------------+ | | |
62 | | | |
63 +---------------------+ | |
64 | |
65 +---------------------+ | |
66 | | | |
67 | +---------------+ | | |
68 | | ceilometer +-------------------------+ |
69 | | central agent | | | |
70 | +---------------+ | | |
71 | | +------v----+--+
72 | controller 1 | | |
73 | | | Coordination |
74 | +---------------+ | | |
75 | | redis | | +------^----+--+
76 | | slave1 | | | |
77 | | <------------------------------+
78 | +---------------+ | | |
79 | | | |
80 +---------------------+ | |
81 | |
82 +---------------------+ | |
83 | | | |
84 | +---------------+ | | |
85 | | ceilometer +-------------------------+ |
86 | | central agent | | |
87 | +---------------+ | |
88 | | |
89 | controller 2 | |
90 | | |
91 | +---------------+ | |
92 | | redis | | |
93 | | slave2 <------------------------------+
94 | | | |
95 | +---------------+ |
96 | |
97 +---------------------+
98
99
100Alternatives
101------------
102
103* We may use MQ queues for task ditribution between the services. The problem is
104 that MQ is one of the most weak point in OpenStack now and it may be not safe
105 to make it responsible for HA and coordination.
106
107Data model impact
108-----------------
109
110None
111
112REST API impact
113---------------
114
115None
116
117Upgrade impact
118--------------
119
120These changes will be needed in puppet scripts:
121
122* Add redis module
123
124* Configure ceilometer agents to be partitioned
125
126
127This change will be needed in packages:
128
129* Use upstream Redis packages and its dependencies
130
131Security impact
132---------------
133
134None
135
136Notifications impact
137--------------------
138
139None
140
141Other end user impact
142---------------------
143
144None
145
146Performance Impact
147------------------
148
149Performance should become better because the same amount of work will be
150done using several workers
151
152Other deployer impact
153---------------------
154
155This could be installed only in HA mode with ceilometer
156
157Developer impact
158----------------
159
160None
161
162Implementation
163==============
164
165Assignee(s)
166-----------
167
168Primary assignee:
169 Ivan Berezovskiy
170
171Other contributors:
172 Nadya Shakhat, Ilya Tyaptin, Igor Degtiarov
173
174Reviewer:
175 Vladimir Kuklin Sergii Golovatiuk
176
177QA:
178 Vitaly Gusev
179
180Work Items
181----------
182
183* Implement redis installation from puppet (iberezovskiy)
184
185* Configure ceilometer central agent (iberezovskiy)
186
187* Configure alarm evaluator (Nadya Shakhat)
188
189* Configure notification agents (Nadya Shakhat)
190
191* Write a documentation (Nadya Shakhat)
192
193Dependencies
194============
195
196None
197
198Testing
199=======
200
201General testing approach:
202
203* Environment with ceilometer in HA mode should be successfully deployed
204
205* Redis cluster should be with one master and two slaves
206
207* Ensure that after node with redis master was broken ceilometer services
208 can work with new redis master
209
210
211Testing approach for central agent:
212
213* Ceilometer should collect all enabled polling meters for deployed
214 environment
215
216* Ensure that the sets of meters to be polled by each central agent are disjoint
217
218* Ensure that after one central agent is broken, during the next polling
219 cycle all measurements will be rescheduled between two another,
220 and all of meters will be collected
221
222
223Testing approach for alarm evaluator:
224
225* Ensure that alarms can be successfully created
226
227* Ensure that after one alarm evaluator is broken, during the next alarm evaluation
228 cycle all alarms will be rescheduled between two another for further evaluation
229 and all of alarms will be successfully evaluated
230
231* Ensure that the sets of alarms for each alarm evaluator are disjoint
232
233
234Testing approach for notification agent:
235
236* Ensure that messages don't not stuck in notification.info queue
237
238* Ensure that IPC queues are created in MQ, chech that list of IPC queues corresponds
239 to pipeline.yaml and each queue has the one consumer
240
241* Ensure that after one alarm evaluator was broken, during the next alarm evaluation
242 cycle all alarms will be rescheduled between two another for further evaluation
243 and all of them will be successfully evaluated
244
245Documentation Impact
246====================
247
248A Plugin Guide about redis plugin installation should be created.
249Also, the document about ceilometer HA and partitioning should be done.
250
251For validation and testing purpose, the test plan and test report should be provided.
252
253References
254==========
255
2561. Central agent: https://github.com/openstack/ceilometer-specs/blob/master/specs/juno/central-agent-partitioning.rst
2572. Notification agent: https://github.com/openstack/ceilometer-specs/blob/master/specs/kilo/notification-coordiation.rst
2583. Notification agent cont.: https://github.com/openstack/ceilometer-specs/blob/master/specs/liberty/distributed-coordinated-notifications.rst