)]}'
{"specs/kilo/notification-pipeline.rst":[{"author":{"_account_id":4491,"name":"Lianhao Lu","email":"llh_misc@outlook.com","username":"lianhao-lu"},"change_message_id":"a51c62206d07058137a358b6a2ce81f215896463","unresolved":false,"context_lines":[{"line_number":5,"context_line":" http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":8,"context_line":"Notification Pipelines"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_a21271fa","line":8,"updated":"2014-12-04 06:20:26.000000000","message":"Should this be called event pipeline? Because it seems we also have https://review.openstack.org/#/c/128411","commit_id":"7dc7f7c5c90b4be320d18f44b18307407a5b97ef"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"7010d0171b187387e0cbd5f243c167336c68b6a0","unresolved":false,"context_lines":[{"line_number":5,"context_line":" http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":8,"context_line":"Notification Pipelines"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_38c06449","line":8,"in_reply_to":"5a890539_a21271fa","updated":"2014-12-04 15:06:30.000000000","message":"yes. i\u0027ll change it.","commit_id":"7dc7f7c5c90b4be320d18f44b18307407a5b97ef"},{"author":{"_account_id":4491,"name":"Lianhao Lu","email":"llh_misc@outlook.com","username":"lianhao-lu"},"change_message_id":"a51c62206d07058137a358b6a2ce81f215896463","unresolved":false,"context_lines":[{"line_number":38,"context_line":"            - sink2"},{"line_number":39,"context_line":"  sinks:"},{"line_number":40,"context_line":"      - name: sink1 # any unique name for sink"},{"line_number":41,"context_line":"        transformers: # one or many transformers -- outside scope of bp"},{"line_number":42,"context_line":"        triggers: # potential for triggering (short term inline alarms)"},{"line_number":43,"context_line":"        publishers: # we will not support rpc it isn\u0027t great for performance"},{"line_number":44,"context_line":"            - notifier://"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_22acc19e","line":41,"updated":"2014-12-04 06:20:26.000000000","message":"What is passed to the transformer? event or notification message?","commit_id":"7dc7f7c5c90b4be320d18f44b18307407a5b97ef"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"7010d0171b187387e0cbd5f243c167336c68b6a0","unresolved":false,"context_lines":[{"line_number":38,"context_line":"            - sink2"},{"line_number":39,"context_line":"  sinks:"},{"line_number":40,"context_line":"      - name: sink1 # any unique name for sink"},{"line_number":41,"context_line":"        transformers: # one or many transformers -- outside scope of bp"},{"line_number":42,"context_line":"        triggers: # potential for triggering (short term inline alarms)"},{"line_number":43,"context_line":"        publishers: # we will not support rpc it isn\u0027t great for performance"},{"line_number":44,"context_line":"            - notifier://"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_b8fe1468","line":41,"in_reply_to":"5a890539_22acc19e","updated":"2014-12-04 15:06:30.000000000","message":"so i was debating this as well. currently, our event_definitions is essentially a transformer because it filters... but i think ultimately it should be events because if we pass a raw notification through without any initial processing and the pipeline says no transformers, we will either be storing something we don\u0027t understand (unprocessed notification), or we\u0027re storing something extremely verbose.\n\ni\u0027ll explicit add it will be an event.","commit_id":"7dc7f7c5c90b4be320d18f44b18307407a5b97ef"},{"author":{"_account_id":8290,"name":"liusheng","email":"liusheng2048@gmail.com","username":"LiuSheng"},"change_message_id":"c8b12fd7deb19601afb5aa099ee71fee8cd076f8","unresolved":false,"context_lines":[{"line_number":48,"context_line":"            # envision a trigger that built performance samples. ie time"},{"line_number":49,"context_line":"            # between corresponding start/end events and republish as a sample"},{"line_number":50,"context_line":"            # alternatively, that same work could send an alarm if it didn\u0027t"},{"line_number":51,"context_line":"            # meet a certain threshold"},{"line_number":52,"context_line":"        publishers: # we will not support rpc it isn\u0027t great for performance"},{"line_number":53,"context_line":"            - notifier://"},{"line_number":54,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"5a890539_f5e891e0","line":51,"updated":"2014-12-05 02:53:23.000000000","message":"Hi gordon chung, what do you mean \"same work could send an alarm\", dose the notification pipline support \"alarm base on events\" or function like this ?","commit_id":"068e5a6d0437654118bfa9445d1f77af8b536acf"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"73e0013ea5054032c778b129e5840b68709c48e2","unresolved":false,"context_lines":[{"line_number":48,"context_line":"            # envision a trigger that built performance samples. ie time"},{"line_number":49,"context_line":"            # between corresponding start/end events and republish as a sample"},{"line_number":50,"context_line":"            # alternatively, that same work could send an alarm if it didn\u0027t"},{"line_number":51,"context_line":"            # meet a certain threshold"},{"line_number":52,"context_line":"        publishers: # we will not support rpc it isn\u0027t great for performance"},{"line_number":53,"context_line":"            - notifier://"},{"line_number":54,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"5a890539_982da600","line":51,"in_reply_to":"5a890539_f5e891e0","updated":"2014-12-05 17:49:41.000000000","message":"that\u0027s up for discussion i guess. i believe there are \"light-weight\" alarms we could easily run inline. for instance. when you start an instance you have instance.create.start and an instance.create.end events. i imagine someone might be interested if this process took longer than x amounts of seconds, that this might raise an alarm that might notify someone.","commit_id":"068e5a6d0437654118bfa9445d1f77af8b536acf"},{"author":{"_account_id":8290,"name":"liusheng","email":"liusheng2048@gmail.com","username":"LiuSheng"},"change_message_id":"c8b12fd7deb19601afb5aa099ee71fee8cd076f8","unresolved":false,"context_lines":[{"line_number":54,"context_line":""},{"line_number":55,"context_line":"Publishers here can be a little different. we currently publish events straight"},{"line_number":56,"context_line":"to the database avoiding the collector. In this spec, we will continue this"},{"line_number":57,"context_line":"offering in addition to the notifier, udp, file options. The collector offers"},{"line_number":58,"context_line":"no discernible benefit apart from moving any synchronous task off the"},{"line_number":59,"context_line":"notification agent to the collector. As we already requeue items for each"},{"line_number":60,"context_line":"pipeline, this synchronous bottleneck exists only on the pipeline which has the"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5a890539_558085be","line":57,"updated":"2014-12-05 02:53:23.000000000","message":"Did you propose to implement a new publisher plugin that straight to the database as the default publisher?  if use \"notifier:// \" as the default publisher, means message will put into message queue","commit_id":"068e5a6d0437654118bfa9445d1f77af8b536acf"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"73e0013ea5054032c778b129e5840b68709c48e2","unresolved":false,"context_lines":[{"line_number":54,"context_line":""},{"line_number":55,"context_line":"Publishers here can be a little different. we currently publish events straight"},{"line_number":56,"context_line":"to the database avoiding the collector. In this spec, we will continue this"},{"line_number":57,"context_line":"offering in addition to the notifier, udp, file options. The collector offers"},{"line_number":58,"context_line":"no discernible benefit apart from moving any synchronous task off the"},{"line_number":59,"context_line":"notification agent to the collector. As we already requeue items for each"},{"line_number":60,"context_line":"pipeline, this synchronous bottleneck exists only on the pipeline which has the"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5a890539_381d92bf","line":57,"in_reply_to":"5a890539_558085be","updated":"2014-12-05 17:49:41.000000000","message":"yes, i think db:// would be the default as i don\u0027t know of any other consumers currently.","commit_id":"068e5a6d0437654118bfa9445d1f77af8b536acf"},{"author":{"_account_id":7336,"name":"Phil Neal","email":"phil.neal@hp.com","username":"nealph"},"change_message_id":"fac25d13c90d73f8e190480868a7a4d896719be4","unresolved":false,"context_lines":[{"line_number":74,"context_line":"REST API impact"},{"line_number":75,"context_line":"---------------"},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"None currently but it\u0027ll affect pipeline in database work."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"Security impact"},{"line_number":80,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_9072740f","line":77,"updated":"2014-12-10 23:37:13.000000000","message":"I think there\u0027s also an overlap with the work to distinguish the notification-and pipeline-specific configurations within the pipeline.yaml: https://review.openstack.org/#/c/128411/5/specs/kilo/notification_filter.rst, though I realize this is the raw event storage (vs. the notification-to-sample pipeline addressed in that bp). \n\nAt minimum I think it\u0027s worth discussing how these two will interact.","commit_id":"068e5a6d0437654118bfa9445d1f77af8b536acf"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"4ee3207328c1554ea6161fabd0f3033f46f51418","unresolved":false,"context_lines":[{"line_number":74,"context_line":"REST API impact"},{"line_number":75,"context_line":"---------------"},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"None currently but it\u0027ll affect pipeline in database work."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"Security impact"},{"line_number":80,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_897ebc17","line":77,"in_reply_to":"3a961159_9072740f","updated":"2014-12-11 14:32:49.000000000","message":"i\u0027m not sure it overlaps notification filter work. Fabio\u0027s work is exclusively controlling what notifications become samples while this work is controlling events...\n\nit does impact the pipeline work you\u0027re doing... i\u0027m not sure how you plan to differentiate conf files on your patch... how would you differ the conf file for ceilometer.conf vs pipeline.yaml vs event_definition? or does your work only reflect pipeline.yaml\n\ni would assume on your end you\u0027d have an extra level to manage the different conf files that are stored in db?","commit_id":"068e5a6d0437654118bfa9445d1f77af8b536acf"}]}