
Was previously looking at the last .start event when comparing important traits against the .exists event. Now it will look at the last important .end event it found (if any). For delete operations, it will be the last event in the chain. This may need to change to a specific event as well, like compute.instance.delete.end or something. Change-Id: Ie85e69716cd730c3546d06bae28e52e0c301940f
35 lines
794 B
INI
35 lines
794 B
INI
[metadata]
|
|
description-file = README.md
|
|
name = winchester
|
|
version = 0.55
|
|
author = Monsyne Dragon
|
|
author_email = mdragon@rackspace.com
|
|
summary = An OpenStack notification event processing library.
|
|
license = Apache-2
|
|
keywords =
|
|
stacktach
|
|
event_processing
|
|
pipeline
|
|
events
|
|
notification
|
|
openstack
|
|
triggers
|
|
|
|
classifiers =
|
|
Development Status :: 5 - Production/Stable
|
|
License :: OSI Approved :: Apache Software License
|
|
Operating System :: POSIX :: Linux
|
|
Programming Language :: Python :: 2.6
|
|
Programming Language :: Python :: 2.7
|
|
|
|
home-page = https://github.com/stackforge/stacktach-winchester
|
|
|
|
[files]
|
|
packages =
|
|
winchester
|
|
|
|
[entry_points]
|
|
console_scripts =
|
|
pipeline_worker = winchester.worker:main
|
|
winchester_db=winchester.db.db_admin:main
|