- Add PEP8 section to tox.ini
- Add hacking to requirements to enforce OpenStack style requirements
- Fix large number of formatting issues flagged by flake8 check
- Add copyright notices to all remaining files
- Fix bug in trigger_manager related to logging calls
- Add .gitignore file
Change-Id: I755ab9c8bcc436836f9006fcd671408cc77214c4
For publishing new events into an exchange.
PipelineHandlers can return new Events for subsequent processing.
However, sometimes we need to publish Notifications. Remember that
Notifications are less restrictive than Events. They can be larger.
They can be nested. They can contain lists.
We store these pending notifications in the handler env variable
so downstream handlers can access them.
The NotabeneHandler takes a configuration variable 'env_keys' which
specifies the env keys to look for. Lists of notifications in these
variables are published to the queue using the connection parameters
supplied.
Errors in transmission are logged and ignored since exceptions during
the commit() phase do not flag the steam as in error.
A sample pipeline definition might look like this:
test_expire_pipeline:
- logger
- usage
- name: notabene
params:⋅
host: localhost
user: guest
password: guest
port: 5672
vhost: /
library: librabbitmq
exchange: nova
exchange_type: topic
queue_name: monitor.info
env_keys:
- usage_notifications
Change-Id: If1958135ad6fbed88e2c18b9fac7efde51ee3113
Introduces the time_sync object which can sync
time with an external time service (like the time_sync
service in notigen).
This is used for playback of old events. It prevents
premature expiry triggers.
Also some tweaks to the UsageHandler, work in progress
and used for testing.
Change-Id: I45033fbd9c12d98f96816a4f90cf7dc8c915ef51