openstack/monasca-notification
Code Issues Proposed changes

Update README.md

Browse Source
This commit is contained in:
Roland Hochmuth 2014-05-09 08:57:31 -06:00
parent 5c3bb2a24d
commit 57b9ff3c0c
1 changed files with 17 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
README.md
View File

@ -35,23 +35,6 @@ the processing to continue even though some notifications can be slow. In the ev
notifications could be sent but the alarms not yet acknowledged. This is an acceptable failure mode, better to send a notifications could be sent but the alarms not yet acknowledged. This is an acceptable failure mode, better to send a
notification twice than not at all. notification twice than not at all.
# License
Copyright (c) 2014 Hewlett-Packard Development Company, L.P.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied.
See the License for the specific language governing permissions and
limitations under the License.
The general process when a major error is encountered is to exit the daemon which should allow another daemon to take The general process when a major error is encountered is to exit the daemon which should allow another daemon to take
over according to the HA strategy. It is also assumed the notification engine will be run by a process supervisor which over according to the HA strategy. It is also assumed the notification engine will be run by a process supervisor which
will restart it in case of a failure. This way any errors which are not easy to recover from are automatically handled will restart it in case of a failure. This way any errors which are not easy to recover from are automatically handled
@ -99,3 +82,20 @@ are gathered per thread, the thread number is indicated by a -# at the end of th
details for each alarm but eventually I may want to cache that info. details for each alarm but eventually I may want to cache that info.
- I am starting with a single KafkaConsumer and a single SentNotificationProcessor depending on load this may need - I am starting with a single KafkaConsumer and a single SentNotificationProcessor depending on load this may need
to scale. to scale.
# License
Copyright (c) 2014 Hewlett-Packard Development Company, L.P.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied.
See the License for the specific language governing permissions and
limitations under the License.