)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":9526,"name":"Zi Lian Ji","email":"jizilian@cn.ibm.com","username":"jizilian"},"change_message_id":"e3a5a51d1ced850af0a2a39acb48590bd83733f6","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     doantungbk \u003cdoantungbk.203@gmail.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2016-04-15 10:45:39 -0700"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Add alarm-based monitoring driver to Tacker with the support of OpenStack Ceilometer"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Change-Id: If7499839dbedb1a94cc76d1f20e00977571d416f"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"1a122d0e_12274f13","line":7,"updated":"2016-04-18 03:38:33.000000000","message":"Hi,\n\nI think this line is too long. Please follow the guide https://wiki.openstack.org/wiki/GitCommitMessages.\n\nThanks for your work","commit_id":"3e241c7eb195138059136bbdbe0e9fac8f93c8ff"},{"author":{"_account_id":19465,"name":"Bruce Thompson","email":"brucet@cisco.com","username":"brucetcisco"},"change_message_id":"c9a98e625893e5b105a054421e9574f4f90e311e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"dab17558_58613f04","side":"PARENT","updated":"2016-05-12 00:54:44.000000000","message":"I think much of the functionality described in this spec will end up getting implemented within a Heat stack using the Heat autoscaling resource combined with a Ceilometer resource and a Heat scalingpolicy resource. See https://drive.google.com/file/d/0B-ruQ8Tx46wSNFdnVkNfR3Z4aDFXZ1F5R0ttLTRPQVhBQ1VJ/view for details.","commit_id":"07e1bc062f3a5aab393d74fd2fa28006a1827c70"}],"specs/newton/alarm-based-monitoring-driver.rst":[{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"7fcacbe2b59881859c023e9a069e0378628d96e0","unresolved":false,"context_lines":[{"line_number":3,"context_line":"Add an alarm-based monitoring driver"},{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"Include the URL of your launchpad blueprint:"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver"},{"line_number":9,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_5deef5b4","line":6,"updated":"2016-05-09 06:45:37.000000000","message":"kindly remove this line","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"420d2c0d772cd2347621d601c3684319dc7e9294","unresolved":false,"context_lines":[{"line_number":3,"context_line":"Add an alarm-based monitoring driver"},{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"Include the URL of your launchpad blueprint:"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver"},{"line_number":9,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_3004cf7c","line":6,"in_reply_to":"dab17558_198f26cd","updated":"2016-05-15 11:22:29.000000000","message":"thx","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"bf5a0e3649adc48e83e3d12cb64ffbeff32a3713","unresolved":false,"context_lines":[{"line_number":3,"context_line":"Add an alarm-based monitoring driver"},{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"Include the URL of your launchpad blueprint:"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver"},{"line_number":9,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_198f26cd","line":6,"in_reply_to":"dab17558_5deef5b4","updated":"2016-05-10 13:30:23.000000000","message":"Done","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"7fcacbe2b59881859c023e9a069e0378628d96e0","unresolved":false,"context_lines":[{"line_number":8,"context_line":"https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"This spec describes the plan to introduce an alarm-based monitoring driver in Tacker using"},{"line_number":11,"context_line":"Ceilometer API."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Problem description"},{"line_number":14,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_3d27b113","line":11,"updated":"2016-05-09 06:45:37.000000000","message":"as we discussed in austin meeting, IMHO, its better to go with heat auto-scaling as tacker already making use of the heat.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"5ce3378860521c8f1a9ed41a3e4c7a5d851ca0e4","unresolved":false,"context_lines":[{"line_number":8,"context_line":"https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"This spec describes the plan to introduce an alarm-based monitoring driver in Tacker using"},{"line_number":11,"context_line":"Ceilometer API."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Problem description"},{"line_number":14,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_96f4e987","line":11,"in_reply_to":"dab17558_3d27b113","updated":"2016-05-12 23:00:06.000000000","message":"+1","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"bf5a0e3649adc48e83e3d12cb64ffbeff32a3713","unresolved":false,"context_lines":[{"line_number":8,"context_line":"https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"This spec describes the plan to introduce an alarm-based monitoring driver in Tacker using"},{"line_number":11,"context_line":"Ceilometer API."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Problem description"},{"line_number":14,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_f97982c9","line":11,"in_reply_to":"dab17558_3d27b113","updated":"2016-05-10 13:30:23.000000000","message":"It is very nice to work with you, Kanagaraj. Heat auto-scaling is a reason which this spec has been being considered. I will fix in the next PatchSet.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":8246,"name":"Qiming Teng","email":"tengqm@outlook.com","username":"tengqm"},"change_message_id":"b8eea099a93e62fa4423e469c6dc532aff3d054d","unresolved":false,"context_lines":[{"line_number":8,"context_line":"https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"This spec describes the plan to introduce an alarm-based monitoring driver in Tacker using"},{"line_number":11,"context_line":"Ceilometer API."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Problem description"},{"line_number":14,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_df926b56","line":11,"in_reply_to":"dab17558_3d27b113","updated":"2016-05-17 04:06:23.000000000","message":"heat autoscaling has a lot problems, you will only realize that when you are putting your code into a real deployment. The next-gen scaling service will be provided by senlin, this has been a Heat decision since Vancouver summit.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"6a0b5c8007f8287819feb947c4313cb7cb61f998","unresolved":false,"context_lines":[{"line_number":8,"context_line":"https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"This spec describes the plan to introduce an alarm-based monitoring driver in Tacker using"},{"line_number":11,"context_line":"Ceilometer API."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Problem description"},{"line_number":14,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_1c94eb34","line":11,"in_reply_to":"dab17558_df926b56","updated":"2016-05-17 11:49:09.000000000","message":"I would suggest to go with heat auto-scaling till it get deprecated by senlin scaling policy, and in newton we don\u0027t have any such plan.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"7fcacbe2b59881859c023e9a069e0378628d96e0","unresolved":false,"context_lines":[{"line_number":23,"context_line":"  designed to run inside a virtual machine (VM). When VM is broken by hardware failure, VNF cannot"},{"line_number":24,"context_line":"  work well. Currently, in order to detect hardware failure, alarm configuration related to CPU usage"},{"line_number":25,"context_line":"  and memory usage could be created by Heat in terms of Heat auto-scaling. However, a user of NFV"},{"line_number":26,"context_line":"  could hardly change alarm parameters like threshold, period and actions."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"* Another goal is to support high availability for Service Function Chain (SFC).  Some fault VNFs"},{"line_number":29,"context_line":"  detected by the monitoring driver can belong to several chains, therefore ensuring high availability"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_1d210db5","line":26,"updated":"2016-05-09 06:45:37.000000000","message":"yes. well said. we may need to form the use case on how to expose the monitoring strategy to the tacker user? is it via Tosca template or via custom convention in tacker, which needsto be traslated to Tosca monitoring element","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"420d2c0d772cd2347621d601c3684319dc7e9294","unresolved":false,"context_lines":[{"line_number":23,"context_line":"  designed to run inside a virtual machine (VM). When VM is broken by hardware failure, VNF cannot"},{"line_number":24,"context_line":"  work well. Currently, in order to detect hardware failure, alarm configuration related to CPU usage"},{"line_number":25,"context_line":"  and memory usage could be created by Heat in terms of Heat auto-scaling. However, a user of NFV"},{"line_number":26,"context_line":"  could hardly change alarm parameters like threshold, period and actions."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"* Another goal is to support high availability for Service Function Chain (SFC).  Some fault VNFs"},{"line_number":29,"context_line":"  detected by the monitoring driver can belong to several chains, therefore ensuring high availability"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_eb5536c6","line":26,"in_reply_to":"dab17558_132f70a2","updated":"2016-05-15 11:22:29.000000000","message":"heat does provide the scaling with automation, so i believe for MANO, we should be able to use it as a whole, but having the control on when to scale from tacker as described in the etherpad https://etherpad.openstack.org/p/tacker-scaling","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"bf5a0e3649adc48e83e3d12cb64ffbeff32a3713","unresolved":false,"context_lines":[{"line_number":23,"context_line":"  designed to run inside a virtual machine (VM). When VM is broken by hardware failure, VNF cannot"},{"line_number":24,"context_line":"  work well. Currently, in order to detect hardware failure, alarm configuration related to CPU usage"},{"line_number":25,"context_line":"  and memory usage could be created by Heat in terms of Heat auto-scaling. However, a user of NFV"},{"line_number":26,"context_line":"  could hardly change alarm parameters like threshold, period and actions."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"* Another goal is to support high availability for Service Function Chain (SFC).  Some fault VNFs"},{"line_number":29,"context_line":"  detected by the monitoring driver can belong to several chains, therefore ensuring high availability"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_9915d64a","line":26,"in_reply_to":"dab17558_1d210db5","updated":"2016-05-10 13:30:23.000000000","message":"Thanks. Tosca template is suitable for deploying the monitoring strategy.  In this spec, the monitoring strategy is exposed in the monitoring policy of TOSCA template.  This kind of TOSCA template will be translated and the monitoring strategy will be applied for instances as well.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":8246,"name":"Qiming Teng","email":"tengqm@outlook.com","username":"tengqm"},"change_message_id":"b8eea099a93e62fa4423e469c6dc532aff3d054d","unresolved":false,"context_lines":[{"line_number":23,"context_line":"  designed to run inside a virtual machine (VM). When VM is broken by hardware failure, VNF cannot"},{"line_number":24,"context_line":"  work well. Currently, in order to detect hardware failure, alarm configuration related to CPU usage"},{"line_number":25,"context_line":"  and memory usage could be created by Heat in terms of Heat auto-scaling. However, a user of NFV"},{"line_number":26,"context_line":"  could hardly change alarm parameters like threshold, period and actions."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"* Another goal is to support high availability for Service Function Chain (SFC).  Some fault VNFs"},{"line_number":29,"context_line":"  detected by the monitoring driver can belong to several chains, therefore ensuring high availability"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_a20aec1d","line":26,"in_reply_to":"dab17558_1d210db5","updated":"2016-05-17 04:06:23.000000000","message":"yes, using VNF metric is more realistic because: 1) autoscaling should not be driven by VIM infra; instead, it should be driven by user level metrics. Users know better whether a scaling operation is needed. VIM should not do that automatically. 2) Even you do want to trigger scaling based on cpu/memory metrics, getting accurate number is not that easy as imagined. 3) If a VNF is down, the VM state becomes meanlingless. So auto-healing should also based on user-level metrics.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"5ce3378860521c8f1a9ed41a3e4c7a5d851ca0e4","unresolved":false,"context_lines":[{"line_number":23,"context_line":"  designed to run inside a virtual machine (VM). When VM is broken by hardware failure, VNF cannot"},{"line_number":24,"context_line":"  work well. Currently, in order to detect hardware failure, alarm configuration related to CPU usage"},{"line_number":25,"context_line":"  and memory usage could be created by Heat in terms of Heat auto-scaling. However, a user of NFV"},{"line_number":26,"context_line":"  could hardly change alarm parameters like threshold, period and actions."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"* Another goal is to support high availability for Service Function Chain (SFC).  Some fault VNFs"},{"line_number":29,"context_line":"  detected by the monitoring driver can belong to several chains, therefore ensuring high availability"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_132f70a2","line":26,"in_reply_to":"dab17558_9915d64a","updated":"2016-05-12 23:00:06.000000000","message":"+1 \n\nA monitoring policy described in a TOSCA template is the way to go.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"6a0b5c8007f8287819feb947c4313cb7cb61f998","unresolved":false,"context_lines":[{"line_number":23,"context_line":"  designed to run inside a virtual machine (VM). When VM is broken by hardware failure, VNF cannot"},{"line_number":24,"context_line":"  work well. Currently, in order to detect hardware failure, alarm configuration related to CPU usage"},{"line_number":25,"context_line":"  and memory usage could be created by Heat in terms of Heat auto-scaling. However, a user of NFV"},{"line_number":26,"context_line":"  could hardly change alarm parameters like threshold, period and actions."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"* Another goal is to support high availability for Service Function Chain (SFC).  Some fault VNFs"},{"line_number":29,"context_line":"  detected by the monitoring driver can belong to several chains, therefore ensuring high availability"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_5c5b1386","line":26,"in_reply_to":"dab17558_a20aec1d","updated":"2016-05-17 11:49:09.000000000","message":"I believe Heat auto-scaling is an just a means to carry out the scaling on the event of alarm. And monitoring component is the one make a call on what to alarm based on the user defined thresholds. Here user only set the threshold level, i believe","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"7fcacbe2b59881859c023e9a069e0378628d96e0","unresolved":false,"context_lines":[{"line_number":28,"context_line":"* Another goal is to support high availability for Service Function Chain (SFC).  Some fault VNFs"},{"line_number":29,"context_line":"  detected by the monitoring driver can belong to several chains, therefore ensuring high availability"},{"line_number":30,"context_line":"  for SFC should be considered. Service Function Chaining management has been approved by Tacker, but"},{"line_number":31,"context_line":"  no mechanism is used to support high availability for SFC."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Currently, Tacker deploys VNFs on a single OpenStack site. Recently, supporting multisite VIM has"},{"line_number":34,"context_line":"  been taken into consideration and therefore Tacker also has the ability to support VNF management"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_1d73cde8","line":31,"updated":"2016-05-09 06:45:37.000000000","message":"heat does provides auto-scaling against given number of resoruce all the time, to make sure, the number of VM are maintained. need to investigate on how ceilometer does support on number of vms ina given group is monitored?","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"bf5a0e3649adc48e83e3d12cb64ffbeff32a3713","unresolved":false,"context_lines":[{"line_number":28,"context_line":"* Another goal is to support high availability for Service Function Chain (SFC).  Some fault VNFs"},{"line_number":29,"context_line":"  detected by the monitoring driver can belong to several chains, therefore ensuring high availability"},{"line_number":30,"context_line":"  for SFC should be considered. Service Function Chaining management has been approved by Tacker, but"},{"line_number":31,"context_line":"  no mechanism is used to support high availability for SFC."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Currently, Tacker deploys VNFs on a single OpenStack site. Recently, supporting multisite VIM has"},{"line_number":34,"context_line":"  been taken into consideration and therefore Tacker also has the ability to support VNF management"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_c40aca78","line":31,"in_reply_to":"dab17558_1d73cde8","updated":"2016-05-10 13:30:23.000000000","message":"Right. I am considering this problem with Ceilometer.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":8246,"name":"Qiming Teng","email":"tengqm@outlook.com","username":"tengqm"},"change_message_id":"b8eea099a93e62fa4423e469c6dc532aff3d054d","unresolved":false,"context_lines":[{"line_number":28,"context_line":"* Another goal is to support high availability for Service Function Chain (SFC).  Some fault VNFs"},{"line_number":29,"context_line":"  detected by the monitoring driver can belong to several chains, therefore ensuring high availability"},{"line_number":30,"context_line":"  for SFC should be considered. Service Function Chaining management has been approved by Tacker, but"},{"line_number":31,"context_line":"  no mechanism is used to support high availability for SFC."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Currently, Tacker deploys VNFs on a single OpenStack site. Recently, supporting multisite VIM has"},{"line_number":34,"context_line":"  been taken into consideration and therefore Tacker also has the ability to support VNF management"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_e237d4e0","line":31,"in_reply_to":"dab17558_1d73cde8","updated":"2016-05-17 04:06:23.000000000","message":"this is not true. maintaining a fixed number of resources in a group has to be done via auto-convergence, which has been given up by heat team. we\u0027d better look for some global workflow to do that.\n\nceilometer side of monitoring is based on metadata filtering.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"5ce3378860521c8f1a9ed41a3e4c7a5d851ca0e4","unresolved":false,"context_lines":[{"line_number":28,"context_line":"* Another goal is to support high availability for Service Function Chain (SFC).  Some fault VNFs"},{"line_number":29,"context_line":"  detected by the monitoring driver can belong to several chains, therefore ensuring high availability"},{"line_number":30,"context_line":"  for SFC should be considered. Service Function Chaining management has been approved by Tacker, but"},{"line_number":31,"context_line":"  no mechanism is used to support high availability for SFC."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Currently, Tacker deploys VNFs on a single OpenStack site. Recently, supporting multisite VIM has"},{"line_number":34,"context_line":"  been taken into consideration and therefore Tacker also has the ability to support VNF management"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_d6715679","line":31,"in_reply_to":"dab17558_c40aca78","updated":"2016-05-12 23:00:06.000000000","message":"As we discussed in the last meeting, let\u0027s limit scope of this spec (and work items coming from it) to only do:\n\na) Mark some VDUs within a VNF to scale-out and scale-in (within a min \u0026 max)\n\nb) Introduce alarm based monitoring on those VDUs to trigger scale-out/scale-in workflow actions\n\nc) Expose API calls for those VDUs to manually scale-out/scale-in\n\n*Everything else*, including SFC, should be out of scope for this spec. We can plan follow on specs \u0026 RFE to address them. Perhaps it is worth to list those things that are relevant but out of scope for this spec.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":8246,"name":"Qiming Teng","email":"tengqm@outlook.com","username":"tengqm"},"change_message_id":"b8eea099a93e62fa4423e469c6dc532aff3d054d","unresolved":false,"context_lines":[{"line_number":28,"context_line":"* Another goal is to support high availability for Service Function Chain (SFC).  Some fault VNFs"},{"line_number":29,"context_line":"  detected by the monitoring driver can belong to several chains, therefore ensuring high availability"},{"line_number":30,"context_line":"  for SFC should be considered. Service Function Chaining management has been approved by Tacker, but"},{"line_number":31,"context_line":"  no mechanism is used to support high availability for SFC."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Currently, Tacker deploys VNFs on a single OpenStack site. Recently, supporting multisite VIM has"},{"line_number":34,"context_line":"  been taken into consideration and therefore Tacker also has the ability to support VNF management"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_e26514e1","line":31,"in_reply_to":"dab17558_d6715679","updated":"2016-05-17 04:06:23.000000000","message":"senlin already provides such apis for scale-in and scale-out. it provides receivers (callbacks) so that a cluster operation can be triggered from any monitoring service/software a user wants to use. The cluster operation can be scale-in/out, or about manual membership management. It covers Tacker use cases well.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"420d2c0d772cd2347621d601c3684319dc7e9294","unresolved":false,"context_lines":[{"line_number":28,"context_line":"* Another goal is to support high availability for Service Function Chain (SFC).  Some fault VNFs"},{"line_number":29,"context_line":"  detected by the monitoring driver can belong to several chains, therefore ensuring high availability"},{"line_number":30,"context_line":"  for SFC should be considered. Service Function Chaining management has been approved by Tacker, but"},{"line_number":31,"context_line":"  no mechanism is used to support high availability for SFC."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Currently, Tacker deploys VNFs on a single OpenStack site. Recently, supporting multisite VIM has"},{"line_number":34,"context_line":"  been taken into consideration and therefore Tacker also has the ability to support VNF management"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_ab720e7a","line":31,"in_reply_to":"dab17558_d6715679","updated":"2016-05-15 11:22:29.000000000","message":"yes, thanks Sridhar.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"6a0b5c8007f8287819feb947c4313cb7cb61f998","unresolved":false,"context_lines":[{"line_number":28,"context_line":"* Another goal is to support high availability for Service Function Chain (SFC).  Some fault VNFs"},{"line_number":29,"context_line":"  detected by the monitoring driver can belong to several chains, therefore ensuring high availability"},{"line_number":30,"context_line":"  for SFC should be considered. Service Function Chaining management has been approved by Tacker, but"},{"line_number":31,"context_line":"  no mechanism is used to support high availability for SFC."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Currently, Tacker deploys VNFs on a single OpenStack site. Recently, supporting multisite VIM has"},{"line_number":34,"context_line":"  been taken into consideration and therefore Tacker also has the ability to support VNF management"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_50049713","line":31,"in_reply_to":"dab17558_e237d4e0","updated":"2016-05-17 11:49:09.000000000","message":"ok. there are different perspetive here. To maintain the number of resources in a group, someone should monitor and signal to heat. FWIW, monasca already supports to trigger the alarm based on the number of active resources in a group, ceilometer, i need to check. \n\nin other words, we could simply achieve this using tacker ping monitor driver, but here we would like to give the task to the right candidate who does the required role, that way, monitoring -\u003e ceilometer, auto-scaling -\u003e heat. and use them in tacker to complete the end-end.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"6a0b5c8007f8287819feb947c4313cb7cb61f998","unresolved":false,"context_lines":[{"line_number":28,"context_line":"* Another goal is to support high availability for Service Function Chain (SFC).  Some fault VNFs"},{"line_number":29,"context_line":"  detected by the monitoring driver can belong to several chains, therefore ensuring high availability"},{"line_number":30,"context_line":"  for SFC should be considered. Service Function Chaining management has been approved by Tacker, but"},{"line_number":31,"context_line":"  no mechanism is used to support high availability for SFC."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Currently, Tacker deploys VNFs on a single OpenStack site. Recently, supporting multisite VIM has"},{"line_number":34,"context_line":"  been taken into consideration and therefore Tacker also has the ability to support VNF management"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_d03ec7b6","line":31,"in_reply_to":"dab17558_e26514e1","updated":"2016-05-17 11:49:09.000000000","message":"same as above suggestion on using senlin.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":19465,"name":"Bruce Thompson","email":"brucet@cisco.com","username":"brucetcisco"},"change_message_id":"c9a98e625893e5b105a054421e9574f4f90e311e","unresolved":false,"context_lines":[{"line_number":29,"context_line":"  detected by the monitoring driver can belong to several chains, therefore ensuring high availability"},{"line_number":30,"context_line":"  for SFC should be considered. Service Function Chaining management has been approved by Tacker, but"},{"line_number":31,"context_line":"  no mechanism is used to support high availability for SFC."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Currently, Tacker deploys VNFs on a single OpenStack site. Recently, supporting multisite VIM has"},{"line_number":34,"context_line":"  been taken into consideration and therefore Tacker also has the ability to support VNF management"},{"line_number":35,"context_line":"  on multiple OpenStack sites. This implies that a monitoring driver in Tacker should be supported to"},{"line_number":36,"context_line":"  the multisite scenario. It is feasible to deploy our monitoring driver in multisite scenario"},{"line_number":37,"context_line":"  because our proposal is to get alarm triggered from Ceilometer. Actually, each site always has an"},{"line_number":38,"context_line":"  OpenStack Ceilometer."},{"line_number":39,"context_line":""},{"line_number":40,"context_line":""},{"line_number":41,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a122d0e_3757d527","line":38,"range":{"start_line":32,"start_character":0,"end_line":38,"end_character":23},"updated":"2016-05-12 00:54:44.000000000","message":"See below for the proposal to use Ceilometer resources in the Heat template for Autoscaling. If we use Ceilometer resources in the Heat template generated for autoscaling then the current multisite implementation will work with Ceilometer for autoscaling without any changes.\n\nIf this feature is needed for functionality not already available in Heat, then I think it may make sense to look at a more general approach for distributing OpenStack API calls between multiple Openstack instances. Instead of having each Tacker subsystem distribute OpenStack API calls, it may make more sense to have Tacker use a subsystem such as Tricircle to distribute OpenStack API calls in a way that abstracts the API distribution layer from the Tacker implementation. For now, I would suggest not trying to solve this problem in the monitoring driver.\n\nAlso, see below for another method of hooking the Heat scaling policy resource with the Tacker monitoring driver using Webhooks. I am not sure if Webhooks work across OpenStack instance. If they do, then this could be the method used to deliver Heat scaling policy events to a Tacker monitoring driver implemented in Tacker itself.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"65c6e4b4465d4288509eac9dc900d060c97ed8b5","unresolved":false,"context_lines":[{"line_number":29,"context_line":"  detected by the monitoring driver can belong to several chains, therefore ensuring high availability"},{"line_number":30,"context_line":"  for SFC should be considered. Service Function Chaining management has been approved by Tacker, but"},{"line_number":31,"context_line":"  no mechanism is used to support high availability for SFC."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Currently, Tacker deploys VNFs on a single OpenStack site. Recently, supporting multisite VIM has"},{"line_number":34,"context_line":"  been taken into consideration and therefore Tacker also has the ability to support VNF management"},{"line_number":35,"context_line":"  on multiple OpenStack sites. This implies that a monitoring driver in Tacker should be supported to"},{"line_number":36,"context_line":"  the multisite scenario. It is feasible to deploy our monitoring driver in multisite scenario"},{"line_number":37,"context_line":"  because our proposal is to get alarm triggered from Ceilometer. Actually, each site always has an"},{"line_number":38,"context_line":"  OpenStack Ceilometer."},{"line_number":39,"context_line":""},{"line_number":40,"context_line":""},{"line_number":41,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_a8a6fd50","line":38,"range":{"start_line":32,"start_character":0,"end_line":38,"end_character":23},"in_reply_to":"1a122d0e_3757d527","updated":"2016-05-12 14:56:28.000000000","message":"Hi Brucet. I already followed a session related to multi-site OpenStack in Austin summit. As far as I know, Tricircle is a solution for multi-site but it is not clear to me how Tricircle can support monitoring solution for multi-site. And I think that building a monitoring driver for multi-site is feasible because actually the monitoring policy can be completely defined by NFV user and therefore it does not make Tacker too complex. The important thing we have in multi-site is the support of Ceilometer alarm interface. Getting alarms from OpenStack multi-site is much more feasible in my mind. In addition, I can see that the ceilometer monitoring driver in Tacker brings too many benefits in terms of multi-site scenario.  First thing I can see is that it is easy to deploy and update the monitoring policy. IMHO, I think what Tacker can do, just let it shine. Please consider this.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"7fcacbe2b59881859c023e9a069e0378628d96e0","unresolved":false,"context_lines":[{"line_number":37,"context_line":"  because our proposal is to get alarm triggered from Ceilometer. Actually, each site always has an"},{"line_number":38,"context_line":"  OpenStack Ceilometer."},{"line_number":39,"context_line":""},{"line_number":40,"context_line":""},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Proposed change"},{"line_number":43,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_dd478575","line":40,"updated":"2016-05-09 06:45:37.000000000","message":"heat does already support multi-site. so we could leverage it.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"420d2c0d772cd2347621d601c3684319dc7e9294","unresolved":false,"context_lines":[{"line_number":37,"context_line":"  because our proposal is to get alarm triggered from Ceilometer. Actually, each site always has an"},{"line_number":38,"context_line":"  OpenStack Ceilometer."},{"line_number":39,"context_line":""},{"line_number":40,"context_line":""},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Proposed change"},{"line_number":43,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_4b12820a","line":40,"in_reply_to":"dab17558_1419ad79","updated":"2016-05-15 11:22:29.000000000","message":"yes, heat is very generic in nature and it supports multi site as part of it, scaling controlled by monitoring is aslo possible","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"6a0b5c8007f8287819feb947c4313cb7cb61f998","unresolved":false,"context_lines":[{"line_number":37,"context_line":"  because our proposal is to get alarm triggered from Ceilometer. Actually, each site always has an"},{"line_number":38,"context_line":"  OpenStack Ceilometer."},{"line_number":39,"context_line":""},{"line_number":40,"context_line":""},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Proposed change"},{"line_number":43,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_30bd9302","line":40,"in_reply_to":"dab17558_428fc074","updated":"2016-05-17 11:49:09.000000000","message":"in case of multi-site, resources are getting deployed across multiple regions by modelling them as remote stack and keep it part of scaling group, i believe, its possible in heat.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":8246,"name":"Qiming Teng","email":"tengqm@outlook.com","username":"tengqm"},"change_message_id":"b8eea099a93e62fa4423e469c6dc532aff3d054d","unresolved":false,"context_lines":[{"line_number":37,"context_line":"  because our proposal is to get alarm triggered from Ceilometer. Actually, each site always has an"},{"line_number":38,"context_line":"  OpenStack Ceilometer."},{"line_number":39,"context_line":""},{"line_number":40,"context_line":""},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Proposed change"},{"line_number":43,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_c2c8d0aa","line":40,"in_reply_to":"dab17558_4b12820a","updated":"2016-05-17 04:06:23.000000000","message":"we cannot say that yet. Resource utilization from one site may have quite different meanings across sites (regions). Scaling across sites is not a simple solution, at least from a metric collection\u0027s perspective.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"bf5a0e3649adc48e83e3d12cb64ffbeff32a3713","unresolved":false,"context_lines":[{"line_number":37,"context_line":"  because our proposal is to get alarm triggered from Ceilometer. Actually, each site always has an"},{"line_number":38,"context_line":"  OpenStack Ceilometer."},{"line_number":39,"context_line":""},{"line_number":40,"context_line":""},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Proposed change"},{"line_number":43,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_1419ad79","line":40,"in_reply_to":"dab17558_dd478575","updated":"2016-05-10 13:30:23.000000000","message":"Yes, I know this. I mentioned to multi-site scenario here because actually a monitoring driver in Tacker should have the ability to get alarms from multiple sites. Heat will help us to deploy monitoring strategy in multiple sites as well. Is it possible?","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":8246,"name":"Qiming Teng","email":"tengqm@outlook.com","username":"tengqm"},"change_message_id":"b8eea099a93e62fa4423e469c6dc532aff3d054d","unresolved":false,"context_lines":[{"line_number":37,"context_line":"  because our proposal is to get alarm triggered from Ceilometer. Actually, each site always has an"},{"line_number":38,"context_line":"  OpenStack Ceilometer."},{"line_number":39,"context_line":""},{"line_number":40,"context_line":""},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Proposed change"},{"line_number":43,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_428fc074","line":40,"in_reply_to":"dab17558_dd478575","updated":"2016-05-17 04:06:23.000000000","message":"heat doesn\u0027t support resource groups across multiple regions or AZs. there were some efforts leading down to a incorrect direction thus got killed.\n\nthe consensus is to offload multi-region, multi-az placement to senlin. Senlin has already supported these two policies. Besides that, senlin also support anti-affinity policy for deployment within a region.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"5ce3378860521c8f1a9ed41a3e4c7a5d851ca0e4","unresolved":false,"context_lines":[{"line_number":42,"context_line":"Proposed change"},{"line_number":43,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"As discussed earlier, alarm-based monitoring driver implemented in OpenStack Tacker can monitor"},{"line_number":46,"context_line":"instances by using alarms from OpenStack Ceilometer. The main focus in this spec is on Tacker,"},{"line_number":47,"context_line":"Ceilometer and the combination between them as described in Figure 1. Ceilometer encompasses three"},{"line_number":48,"context_line":"main components: API service, computer agent, and alarm evaluator. As described in Figure 2, API"},{"line_number":49,"context_line":"service provides the API so that other OpenStack projects can use to access into database."},{"line_number":50,"context_line":"Computer agent is responsible monitoring instances and collecting data. Based on collected data,"},{"line_number":51,"context_line":"alarm evaluator will raise the alarm and trigger it to target projects."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"::"},{"line_number":54,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_fe50a360","line":51,"range":{"start_line":45,"start_character":0,"end_line":51,"end_character":71},"updated":"2016-05-12 23:00:06.000000000","message":"The challenge in this spec, as some of you have already pointed out, is we are mixing two related but different things...\n\n(1) Enable VNF resource monitoring (using Ceilometer)\n(2) Supporting auto-scaling\n\nLet\u0027s step back a bit and see what we exposing out of Tacker. For a moment ignore underlying technologies like Ceilometer and Heat AutoScaling.\n\nWhat do we have today? From sample tosca vnfd [1]\n\n        monitoring_policy:\n          name: ping\n          parameters:\n            monitoring_delay: 45\n            count: 3\n            interval: 1\n            timeout: 2\n          actions:\n            failure: respawn\n\nIf this can be abstracted into something generic, we will get this ...\n\n        monitoring_policy:\n          name: {ping | http_ping | custom-foo }\n          parameters:\n            monitoring_delay: 45\n            param-a: value-a\n            param-b: value-b\n            param-c: value-c\n          actions:\n            \"disposition-blah\": { respawn | log }\n\n\nNow this spec is proposing,\n\n        monitoring_policy:\n          name: {ping | http_ping | cpu_util | custom-foo }\n          parameters:\n            monitoring_delay: 45\n            param-a: value-a\n            param-b: value-b\n            param-c: value-c\n          actions:\n            \"disposition-blah\": { respawn | log | scale-up | scale-down }\n\n\nThere are different permutations possible. For e.g. using cpu_util monitor I might want to just do \"log\" action if CPU utilization is high. Or, based on a custom monitoring driver (\"custom-foo\", say calls-per-sec monitoring in vIMS VNF) I might want to do \"scale-out\" action.\n\nPlease think about these scenarios as you shape this spec. Ceilometer and Heat-AutoScaling are just means to an end.\n\n[1] https://github.com/openstack/tacker/blob/master/devstack/samples/sample-tosca-vnfd-monitor.yaml","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"420d2c0d772cd2347621d601c3684319dc7e9294","unresolved":false,"context_lines":[{"line_number":42,"context_line":"Proposed change"},{"line_number":43,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"As discussed earlier, alarm-based monitoring driver implemented in OpenStack Tacker can monitor"},{"line_number":46,"context_line":"instances by using alarms from OpenStack Ceilometer. The main focus in this spec is on Tacker,"},{"line_number":47,"context_line":"Ceilometer and the combination between them as described in Figure 1. Ceilometer encompasses three"},{"line_number":48,"context_line":"main components: API service, computer agent, and alarm evaluator. As described in Figure 2, API"},{"line_number":49,"context_line":"service provides the API so that other OpenStack projects can use to access into database."},{"line_number":50,"context_line":"Computer agent is responsible monitoring instances and collecting data. Based on collected data,"},{"line_number":51,"context_line":"alarm evaluator will raise the alarm and trigger it to target projects."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"::"},{"line_number":54,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_cba8327a","line":51,"range":{"start_line":45,"start_character":0,"end_line":51,"end_character":71},"in_reply_to":"dab17558_fe50a360","updated":"2016-05-15 11:22:29.000000000","message":"yes, it basically adopting the openstack scaling and monitoroing as part of TOSCA monitoring element. thanks Sridhar.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"7fcacbe2b59881859c023e9a069e0378628d96e0","unresolved":false,"context_lines":[{"line_number":53,"context_line":"::"},{"line_number":54,"context_line":""},{"line_number":55,"context_line":" Alarm-based monitoring driver:"},{"line_number":56,"context_line":"                                                    OpenStack Ceilometer"},{"line_number":57,"context_line":"                                                          +----------------------------+"},{"line_number":58,"context_line":"                                                          |                            |"},{"line_number":59,"context_line":"                                                          |                            |"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_7dfdb939","line":56,"updated":"2016-05-09 06:45:37.000000000","message":"these parts are not required to detail here in this spec. \nAnd let us add the details on how to make use of heat auto-scaling via heat templates.\n\nsee diff of how scaling is supported in Tosca and what ceilometer supports\nare those tosca elements could be translated to hot resource type\nmake sure that hot template carries the ceilometer alarm part as expected.\nheat provides hook for auto-scaling policies, how to trigger them? let ceilometer trigger automatically? or tacker wants to trigger manually?","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"bf5a0e3649adc48e83e3d12cb64ffbeff32a3713","unresolved":false,"context_lines":[{"line_number":53,"context_line":"::"},{"line_number":54,"context_line":""},{"line_number":55,"context_line":" Alarm-based monitoring driver:"},{"line_number":56,"context_line":"                                                    OpenStack Ceilometer"},{"line_number":57,"context_line":"                                                          +----------------------------+"},{"line_number":58,"context_line":"                                                          |                            |"},{"line_number":59,"context_line":"                                                          |                            |"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_f4b18948","line":56,"in_reply_to":"dab17558_7dfdb939","updated":"2016-05-10 13:30:23.000000000","message":"Thanks, Kanagaraj. However, please note that these parts are different. We have some missing points here, Kanagaraj. If we only mention to heat auto-scaling, nothing is necessary for developing because heat auto-scaling itself is perfect. But in the view of Tacker, Tacker should know what happened with VNF instances. That’s why I want to build the alarm-based monitoring here.  \nThe main focus of these parts is on alarm-based monitoring driver in Tacker. Accordingly, Ceilometer will also trigger alarms to the alarm-based monitoring driver. \nRegarding to trigger action, I think we should let Ceilometer trigger automatically. Because actually Ceilometer only triggers alarms when some actions happen. This work makes sense and therefore Tacker does not need to process too much information.\nFinally, ensuring that hot template can recognize the alarm configuration is an important part in this spec.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"420d2c0d772cd2347621d601c3684319dc7e9294","unresolved":false,"context_lines":[{"line_number":53,"context_line":"::"},{"line_number":54,"context_line":""},{"line_number":55,"context_line":" Alarm-based monitoring driver:"},{"line_number":56,"context_line":"                                                    OpenStack Ceilometer"},{"line_number":57,"context_line":"                                                          +----------------------------+"},{"line_number":58,"context_line":"                                                          |                            |"},{"line_number":59,"context_line":"                                                          |                            |"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_abd16efd","line":56,"in_reply_to":"dab17558_f4b18948","updated":"2016-05-15 11:22:29.000000000","message":"sure. it needs to be updated the below diagram in to sequence diagram\n1. Heat creates the scale group in openstack\n2. Heat setup the alarm in ceilometer to monitor the scale group, on the event of alarm, it invokes the tacker driver\n3. Now tacker monitoring driver decides and signal the heat scale group.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":19465,"name":"Bruce Thompson","email":"brucet@cisco.com","username":"brucetcisco"},"change_message_id":"c9a98e625893e5b105a054421e9574f4f90e311e","unresolved":false,"context_lines":[{"line_number":55,"context_line":" Alarm-based monitoring driver:"},{"line_number":56,"context_line":"                                                    OpenStack Ceilometer"},{"line_number":57,"context_line":"                                                          +----------------------------+"},{"line_number":58,"context_line":"                                                          |                            |"},{"line_number":59,"context_line":"                                                          |                            |"},{"line_number":60,"context_line":"             +--------------------+                       |   +--------------------+   |"},{"line_number":61,"context_line":"             |                    |       Create alarms   |   |                    |   |"},{"line_number":62,"context_line":"             |    Heat Engine     +---------------------------\u003e                    |   |"},{"line_number":63,"context_line":"             |    (OpenStack)     |                       |   |     API service    |   |"},{"line_number":64,"context_line":"             |                    |                       |   |                    |   |"},{"line_number":65,"context_line":"             +--------------------+                       |   +--------------------+   |"},{"line_number":66,"context_line":"                                                          |                            |"},{"line_number":67,"context_line":"                                                          |                            |"},{"line_number":68,"context_line":"                                                          |                            |"},{"line_number":69,"context_line":"             +--------------------+                       |   +--------------------+   |"},{"line_number":70,"context_line":"             |                    |       Triggers alarms |   |                    |   |"},{"line_number":71,"context_line":"             |     Alarm+based    |         (Webhook)     |   |                    |   |"},{"line_number":72,"context_line":"             |  monitoring driver \u003c---------------------------+   Alarm evaluator  |   |"},{"line_number":73,"context_line":"             |      (tacker)      |                       |   |                    |   |"},{"line_number":74,"context_line":"             +--------------------+                       |   +--------------------+   |"},{"line_number":75,"context_line":"    Stack                                                 |                            |"},{"line_number":76,"context_line":"    +---------------------------------------+             |                            |"},{"line_number":77,"context_line":"    |  +----------|                         |             |   +--------------------+   |"},{"line_number":78,"context_line":"    |  |  +----------+                      |  Monitor    |   |                    |   |"},{"line_number":79,"context_line":"    |  |  |       |  |                      | instances   |   |                    |   |"},{"line_number":80,"context_line":"    |  +----------+  |                      \u003c-----------------+    Computer Agent  |   |"},{"line_number":81,"context_line":"    |     +----------+                      |             |   |                    |   |"},{"line_number":82,"context_line":"    |                                       |             |   +--------------------+   |"},{"line_number":83,"context_line":"    |                                       |             |                            |"},{"line_number":84,"context_line":"    |                                       |             +----------------------------+"},{"line_number":85,"context_line":"    +---------------------------------------+"},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"In this spec, the objective of the alarm-based monitoring driver is to support VNF scaling and"},{"line_number":88,"context_line":"high availability for SFC not only on a single VIM but also on multisite VIM as shown below."}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_d8f08f69","line":85,"range":{"start_line":58,"start_character":3,"end_line":85,"end_character":45},"updated":"2016-05-12 00:54:44.000000000","message":"I believe there is a simpler way to integrate the Ceilometer monitoring driver in Tacker with Heat autoscaling functionality. When a Heat template creates an alarm using a Ceilometer resource, it can also provide a handler for that alarm within the Heat template using a combination of the Heat scaling policy and a Heat autoscaling resource. See https://drive.google.com/file/d/0B-ruQ8Tx46wSNFdnVkNfR3Z4aDFXZ1F5R0ttLTRPQVhBQ1VJ/view and below for details.\n\nIf Heat provides a handler for the Ceilometer alarm, than that handler can then take action on the alarm within the context of the Heat stack itself. This is a much better approach when you consider Tacker multi site functionality. It is much better to destribute the alarm / action associated with Ceilometer to the target OpenStack instance than run this control loop between 2 OpenStack instances (the Tacker instance and the remote OpenStack instance).\n\nThe same handler within the Heat template can also generate a webhook to allow the Tacker monitoring driver to take any actions not implemented in the Heat stack itself.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"65c6e4b4465d4288509eac9dc900d060c97ed8b5","unresolved":false,"context_lines":[{"line_number":55,"context_line":" Alarm-based monitoring driver:"},{"line_number":56,"context_line":"                                                    OpenStack Ceilometer"},{"line_number":57,"context_line":"                                                          +----------------------------+"},{"line_number":58,"context_line":"                                                          |                            |"},{"line_number":59,"context_line":"                                                          |                            |"},{"line_number":60,"context_line":"             +--------------------+                       |   +--------------------+   |"},{"line_number":61,"context_line":"             |                    |       Create alarms   |   |                    |   |"},{"line_number":62,"context_line":"             |    Heat Engine     +---------------------------\u003e                    |   |"},{"line_number":63,"context_line":"             |    (OpenStack)     |                       |   |     API service    |   |"},{"line_number":64,"context_line":"             |                    |                       |   |                    |   |"},{"line_number":65,"context_line":"             +--------------------+                       |   +--------------------+   |"},{"line_number":66,"context_line":"                                                          |                            |"},{"line_number":67,"context_line":"                                                          |                            |"},{"line_number":68,"context_line":"                                                          |                            |"},{"line_number":69,"context_line":"             +--------------------+                       |   +--------------------+   |"},{"line_number":70,"context_line":"             |                    |       Triggers alarms |   |                    |   |"},{"line_number":71,"context_line":"             |     Alarm+based    |         (Webhook)     |   |                    |   |"},{"line_number":72,"context_line":"             |  monitoring driver \u003c---------------------------+   Alarm evaluator  |   |"},{"line_number":73,"context_line":"             |      (tacker)      |                       |   |                    |   |"},{"line_number":74,"context_line":"             +--------------------+                       |   +--------------------+   |"},{"line_number":75,"context_line":"    Stack                                                 |                            |"},{"line_number":76,"context_line":"    +---------------------------------------+             |                            |"},{"line_number":77,"context_line":"    |  +----------|                         |             |   +--------------------+   |"},{"line_number":78,"context_line":"    |  |  +----------+                      |  Monitor    |   |                    |   |"},{"line_number":79,"context_line":"    |  |  |       |  |                      | instances   |   |                    |   |"},{"line_number":80,"context_line":"    |  +----------+  |                      \u003c-----------------+    Computer Agent  |   |"},{"line_number":81,"context_line":"    |     +----------+                      |             |   |                    |   |"},{"line_number":82,"context_line":"    |                                       |             |   +--------------------+   |"},{"line_number":83,"context_line":"    |                                       |             |                            |"},{"line_number":84,"context_line":"    |                                       |             +----------------------------+"},{"line_number":85,"context_line":"    +---------------------------------------+"},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"In this spec, the objective of the alarm-based monitoring driver is to support VNF scaling and"},{"line_number":88,"context_line":"high availability for SFC not only on a single VIM but also on multisite VIM as shown below."}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_887699d6","line":85,"range":{"start_line":58,"start_character":3,"end_line":85,"end_character":45},"in_reply_to":"dab17558_d8f08f69","updated":"2016-05-12 14:56:28.000000000","message":"I do not think that generating a webhook to contact with Tacker monitoring driver is a scope of Heat in this case. Meanwhile, it is available in Ceilometer. It should not be done by Heat. Please also consider this.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"5ce3378860521c8f1a9ed41a3e4c7a5d851ca0e4","unresolved":false,"context_lines":[{"line_number":82,"context_line":"    |                                       |             |   +--------------------+   |"},{"line_number":83,"context_line":"    |                                       |             |                            |"},{"line_number":84,"context_line":"    |                                       |             +----------------------------+"},{"line_number":85,"context_line":"    +---------------------------------------+"},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"In this spec, the objective of the alarm-based monitoring driver is to support VNF scaling and"},{"line_number":88,"context_line":"high availability for SFC not only on a single VIM but also on multisite VIM as shown below."}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_f69295f5","line":85,"in_reply_to":"dab17558_d8f08f69","updated":"2016-05-12 23:00:06.000000000","message":"I totally agree with w/ Bruce here. As much as possible see if we can leverage remote heat-engine and Heat\u0027s Ceilometer integration to achieve most of the functionality for this initial release.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":19465,"name":"Bruce Thompson","email":"brucet@cisco.com","username":"brucetcisco"},"change_message_id":"c9a98e625893e5b105a054421e9574f4f90e311e","unresolved":false,"context_lines":[{"line_number":89,"context_line":""},{"line_number":90,"context_line":"::"},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"  Alarm-based monitoring driver with multisite VIM feature:"},{"line_number":93,"context_line":""},{"line_number":94,"context_line":"                        +------------------------------+"},{"line_number":95,"context_line":"                        |        Tacker service        |"},{"line_number":96,"context_line":"                        |        VNFM component        |"},{"line_number":97,"context_line":"                        |     +--------------------+   |"},{"line_number":98,"context_line":"                        |     |     Alarm-based    |   |"},{"line_number":99,"context_line":"                        |     |  monitoring driver |   |"},{"line_number":100,"context_line":"                        |     +---------+----------+   |"},{"line_number":101,"context_line":"                        |               |              |"},{"line_number":102,"context_line":"                        +------------------------------+"},{"line_number":103,"context_line":"                                        |"},{"line_number":104,"context_line":"          +-----------------------------------------+XXXXXXXX+---------------+"},{"line_number":105,"context_line":"              |                             |                              |"},{"line_number":106,"context_line":"              |                             |                              |"},{"line_number":107,"context_line":"    +-------------------+         +-------------------+          +-------------------+"},{"line_number":108,"context_line":"    |         |         |         |         |         |          |         |         |"},{"line_number":109,"context_line":"    |         v         |         |         v         |          |         v         |"},{"line_number":110,"context_line":"    |   +-----+----+    |         |   +-----+----+    | XXXXXXXX |   +-----+----+    |"},{"line_number":111,"context_line":"    |   |Ceilometer|    |         |   |Ceilometer|    |          |   |Ceilometer|    |"},{"line_number":112,"context_line":"    |   +----------+    |         |   +----------+    |          |   +----------+    |"},{"line_number":113,"context_line":"    +-------------------+         +-------------------+          +-------------------+"},{"line_number":114,"context_line":"           Site 1                        Site 2                          Site N"},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"Alternatives"},{"line_number":117,"context_line":"------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_78f6c35d","line":114,"range":{"start_line":92,"start_character":2,"end_line":114,"end_character":79},"updated":"2016-05-12 00:54:44.000000000","message":"I suggest not attempting to tackle this in the Ceilometer monitoring driver. As I mentioned above, I believe a more general approach (such as OpenStack Tricircle) can be used when we try to distribute this type of functionality outside the context of a Heat stack.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"5ce3378860521c8f1a9ed41a3e4c7a5d851ca0e4","unresolved":false,"context_lines":[{"line_number":111,"context_line":"    |   |Ceilometer|    |         |   |Ceilometer|    |          |   |Ceilometer|    |"},{"line_number":112,"context_line":"    |   +----------+    |         |   +----------+    |          |   +----------+    |"},{"line_number":113,"context_line":"    +-------------------+         +-------------------+          +-------------------+"},{"line_number":114,"context_line":"           Site 1                        Site 2                          Site N"},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"Alternatives"},{"line_number":117,"context_line":"------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_015276dd","line":114,"in_reply_to":"dab17558_78f6c35d","updated":"2016-05-12 23:00:06.000000000","message":"Bruce - \n\nWe got to table any discussion on leveraging Tricircle for Tacker MultiSite until we have data from our target NFV operator community that they are planning on using Tricircle to solve their MultiSite deployment challenges. Please share any data if you\u0027ve on its adoption. I don\u0027t want to tie Tacker and its key features to implicitly assume Tricircle is going to be adopted by OpenStack deployers.\n\nAs we discussed earlier, it is definitely an option down the line, where a Tricircle site could be made to \"look\" like a site for Tacker. But lets address that use-case if \u0026 when our user community asks for it, which will come *after* Tricircle becomes an accepted way to solve multisite in OpenStack.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"65c6e4b4465d4288509eac9dc900d060c97ed8b5","unresolved":false,"context_lines":[{"line_number":89,"context_line":""},{"line_number":90,"context_line":"::"},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"  Alarm-based monitoring driver with multisite VIM feature:"},{"line_number":93,"context_line":""},{"line_number":94,"context_line":"                        +------------------------------+"},{"line_number":95,"context_line":"                        |        Tacker service        |"},{"line_number":96,"context_line":"                        |        VNFM component        |"},{"line_number":97,"context_line":"                        |     +--------------------+   |"},{"line_number":98,"context_line":"                        |     |     Alarm-based    |   |"},{"line_number":99,"context_line":"                        |     |  monitoring driver |   |"},{"line_number":100,"context_line":"                        |     +---------+----------+   |"},{"line_number":101,"context_line":"                        |               |              |"},{"line_number":102,"context_line":"                        +------------------------------+"},{"line_number":103,"context_line":"                                        |"},{"line_number":104,"context_line":"          +-----------------------------------------+XXXXXXXX+---------------+"},{"line_number":105,"context_line":"              |                             |                              |"},{"line_number":106,"context_line":"              |                             |                              |"},{"line_number":107,"context_line":"    +-------------------+         +-------------------+          +-------------------+"},{"line_number":108,"context_line":"    |         |         |         |         |         |          |         |         |"},{"line_number":109,"context_line":"    |         v         |         |         v         |          |         v         |"},{"line_number":110,"context_line":"    |   +-----+----+    |         |   +-----+----+    | XXXXXXXX |   +-----+----+    |"},{"line_number":111,"context_line":"    |   |Ceilometer|    |         |   |Ceilometer|    |          |   |Ceilometer|    |"},{"line_number":112,"context_line":"    |   +----------+    |         |   +----------+    |          |   +----------+    |"},{"line_number":113,"context_line":"    +-------------------+         +-------------------+          +-------------------+"},{"line_number":114,"context_line":"           Site 1                        Site 2                          Site N"},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"Alternatives"},{"line_number":117,"context_line":"------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_885df94a","line":114,"range":{"start_line":92,"start_character":2,"end_line":114,"end_character":79},"in_reply_to":"dab17558_78f6c35d","updated":"2016-05-12 14:56:28.000000000","message":"I will consider this problem carefully. Anyway, please also note my explanation as mentioned above.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":19465,"name":"Bruce Thompson","email":"brucet@cisco.com","username":"brucetcisco"},"change_message_id":"c9a98e625893e5b105a054421e9574f4f90e311e","unresolved":false,"context_lines":[{"line_number":191,"context_line":"        flavor: m1.tiny"},{"line_number":192,"context_line":"        availability_zone: nova"},{"line_number":193,"context_line":"        mgmt_driver: noop"},{"line_number":194,"context_line":"        config: |"},{"line_number":195,"context_line":"          param0: key1"},{"line_number":196,"context_line":"          param1: key2"},{"line_number":197,"context_line":"        monitoring_policy:"},{"line_number":198,"context_line":"          name: cpu_util"},{"line_number":199,"context_line":"          parameters:"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_1d6cc906","line":196,"range":{"start_line":194,"start_character":9,"end_line":196,"end_character":22},"updated":"2016-05-12 00:54:44.000000000","message":"This attribute indirectly maps to the Heat SoftwareConfig Resource. See https://drive.google.com/file/d/0B-ruQ8Tx46wSNFdnVkNfR3Z4aDFXZ1F5R0ttLTRPQVhBQ1VJ/view for details. I am not sure if this attribute is already defined in the lastest Tosca Simple Yaml Profile. The fact that this resource maps to a Heat Resource means that it should be implemented as part of the Heat driver in the Tosca / Heat translator.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"65c6e4b4465d4288509eac9dc900d060c97ed8b5","unresolved":false,"context_lines":[{"line_number":191,"context_line":"        flavor: m1.tiny"},{"line_number":192,"context_line":"        availability_zone: nova"},{"line_number":193,"context_line":"        mgmt_driver: noop"},{"line_number":194,"context_line":"        config: |"},{"line_number":195,"context_line":"          param0: key1"},{"line_number":196,"context_line":"          param1: key2"},{"line_number":197,"context_line":"        monitoring_policy:"},{"line_number":198,"context_line":"          name: cpu_util"},{"line_number":199,"context_line":"          parameters:"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_a8da78e7","line":196,"range":{"start_line":194,"start_character":9,"end_line":196,"end_character":22},"in_reply_to":"dab17558_1d6cc906","updated":"2016-05-12 14:56:28.000000000","message":"As far as I know, this attribute is already defined in the Tosca Simple Yaml Profile.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":19465,"name":"Bruce Thompson","email":"brucet@cisco.com","username":"brucetcisco"},"change_message_id":"c9a98e625893e5b105a054421e9574f4f90e311e","unresolved":false,"context_lines":[{"line_number":194,"context_line":"        config: |"},{"line_number":195,"context_line":"          param0: key1"},{"line_number":196,"context_line":"          param1: key2"},{"line_number":197,"context_line":"        monitoring_policy:"},{"line_number":198,"context_line":"          name: cpu_util"},{"line_number":199,"context_line":"          parameters:"},{"line_number":200,"context_line":"            statistic: avg"},{"line_number":201,"context_line":"            period: \"60\""},{"line_number":202,"context_line":"            evaluation_periods: \"1\""},{"line_number":203,"context_line":"            threshold: \"70\""},{"line_number":204,"context_line":"          actions:"},{"line_number":205,"context_line":"            - {trigger: failure, action: scale_up}"},{"line_number":206,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_dd336112","line":203,"range":{"start_line":197,"start_character":8,"end_line":203,"end_character":27},"updated":"2016-05-12 00:54:44.000000000","message":"This attribute mostly maps to the Heat ScalingPolicy resource.  See https://drive.google.com/file/d/0B-ruQ8Tx46wSNFdnVkNfR3Z4aDFXZ1F5R0ttLTRPQVhBQ1VJ/view for details. I am not sure if this attribute is already defined in the lastest Tosca Simple Yaml Profile. The fact that this resource maps to a Heat Resource means that it should be implemented as part of the Heat driver in the Tosca / Heat translator.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"5ce3378860521c8f1a9ed41a3e4c7a5d851ca0e4","unresolved":false,"context_lines":[{"line_number":194,"context_line":"        config: |"},{"line_number":195,"context_line":"          param0: key1"},{"line_number":196,"context_line":"          param1: key2"},{"line_number":197,"context_line":"        monitoring_policy:"},{"line_number":198,"context_line":"          name: cpu_util"},{"line_number":199,"context_line":"          parameters:"},{"line_number":200,"context_line":"            statistic: avg"},{"line_number":201,"context_line":"            period: \"60\""},{"line_number":202,"context_line":"            evaluation_periods: \"1\""},{"line_number":203,"context_line":"            threshold: \"70\""},{"line_number":204,"context_line":"          actions:"},{"line_number":205,"context_line":"            - {trigger: failure, action: scale_up}"},{"line_number":206,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_fe92639e","line":203,"range":{"start_line":197,"start_character":8,"end_line":203,"end_character":27},"in_reply_to":"dab17558_140da437","updated":"2016-05-12 23:00:06.000000000","message":"We need to be careful not to assume a particular action based on name and paramaters. The action could just be \"log\" for a high cpu-util condition.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"65c6e4b4465d4288509eac9dc900d060c97ed8b5","unresolved":false,"context_lines":[{"line_number":194,"context_line":"        config: |"},{"line_number":195,"context_line":"          param0: key1"},{"line_number":196,"context_line":"          param1: key2"},{"line_number":197,"context_line":"        monitoring_policy:"},{"line_number":198,"context_line":"          name: cpu_util"},{"line_number":199,"context_line":"          parameters:"},{"line_number":200,"context_line":"            statistic: avg"},{"line_number":201,"context_line":"            period: \"60\""},{"line_number":202,"context_line":"            evaluation_periods: \"1\""},{"line_number":203,"context_line":"            threshold: \"70\""},{"line_number":204,"context_line":"          actions:"},{"line_number":205,"context_line":"            - {trigger: failure, action: scale_up}"},{"line_number":206,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_140da437","line":203,"range":{"start_line":197,"start_character":8,"end_line":203,"end_character":27},"in_reply_to":"dab17558_dd336112","updated":"2016-05-12 14:56:28.000000000","message":"The last time when I discussed with Bob, it has not been defined in the TOSCA Simple Yaml File yet.\n\nYes, you are right. Heat driver will be responsible for translating this kind of policy.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"420d2c0d772cd2347621d601c3684319dc7e9294","unresolved":false,"context_lines":[{"line_number":194,"context_line":"        config: |"},{"line_number":195,"context_line":"          param0: key1"},{"line_number":196,"context_line":"          param1: key2"},{"line_number":197,"context_line":"        monitoring_policy:"},{"line_number":198,"context_line":"          name: cpu_util"},{"line_number":199,"context_line":"          parameters:"},{"line_number":200,"context_line":"            statistic: avg"},{"line_number":201,"context_line":"            period: \"60\""},{"line_number":202,"context_line":"            evaluation_periods: \"1\""},{"line_number":203,"context_line":"            threshold: \"70\""},{"line_number":204,"context_line":"          actions:"},{"line_number":205,"context_line":"            - {trigger: failure, action: scale_up}"},{"line_number":206,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_0b2ebaf9","line":203,"range":{"start_line":197,"start_character":8,"end_line":203,"end_character":27},"in_reply_to":"dab17558_fe92639e","updated":"2016-05-15 11:22:29.000000000","message":"do we have standardized parameters and actions for the monitoring in TOSCA","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":19465,"name":"Bruce Thompson","email":"brucet@cisco.com","username":"brucetcisco"},"change_message_id":"c9a98e625893e5b105a054421e9574f4f90e311e","unresolved":false,"context_lines":[{"line_number":201,"context_line":"            period: \"60\""},{"line_number":202,"context_line":"            evaluation_periods: \"1\""},{"line_number":203,"context_line":"            threshold: \"70\""},{"line_number":204,"context_line":"          actions:"},{"line_number":205,"context_line":"            - {trigger: failure, action: scale_up}"},{"line_number":206,"context_line":""},{"line_number":207,"context_line":"2. Ensure that Heat can set successfully alarm configuration into Ceilometer."},{"line_number":208,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_3d238dbe","line":205,"range":{"start_line":204,"start_character":8,"end_line":205,"end_character":50},"updated":"2016-05-12 00:54:44.000000000","message":"These actions can be handled by a Heat template with an scaling policy resource tied to an autoscaling resource through the \"auto_scaling_group_id\" attribute of the scalingpolicy resource. See https://drive.google.com/file/d/0B-ruQ8Tx46wSNFdnVkNfR3Z4aDFXZ1F5R0ttLTRPQVhBQ1VJ/view for details. In other words, a ceilometer based monitoring driver is not needed to support these actions. The fact that this resource maps to a set of Heat Resources means that it should be implemented as part of the Heat driver in the Tosca / Heat translator.\n\nIn fact, if we can not think of any actions we need to support that are not already available in a Heat template, then I think we will not actually need a ceilometer monitoring driver separate from what will become available in the Heat autoscaling feature.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"65c6e4b4465d4288509eac9dc900d060c97ed8b5","unresolved":false,"context_lines":[{"line_number":201,"context_line":"            period: \"60\""},{"line_number":202,"context_line":"            evaluation_periods: \"1\""},{"line_number":203,"context_line":"            threshold: \"70\""},{"line_number":204,"context_line":"          actions:"},{"line_number":205,"context_line":"            - {trigger: failure, action: scale_up}"},{"line_number":206,"context_line":""},{"line_number":207,"context_line":"2. Ensure that Heat can set successfully alarm configuration into Ceilometer."},{"line_number":208,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_bebab208","line":205,"range":{"start_line":204,"start_character":8,"end_line":205,"end_character":50},"in_reply_to":"dab17558_3d238dbe","updated":"2016-05-12 14:56:28.000000000","message":"Regarding to these actions, I will consider and maybe it will be changed in the next Patchset. Thanks","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":19465,"name":"Bruce Thompson","email":"brucet@cisco.com","username":"brucetcisco"},"change_message_id":"c9a98e625893e5b105a054421e9574f4f90e311e","unresolved":false,"context_lines":[{"line_number":204,"context_line":"          actions:"},{"line_number":205,"context_line":"            - {trigger: failure, action: scale_up}"},{"line_number":206,"context_line":""},{"line_number":207,"context_line":"2. Ensure that Heat can set successfully alarm configuration into Ceilometer."},{"line_number":208,"context_line":""},{"line_number":209,"context_line":"3. The monitoring driver can get alarm when VNFs go down or get overloaded."},{"line_number":210,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_58d13f22","line":207,"range":{"start_line":207,"start_character":0,"end_line":207,"end_character":77},"updated":"2016-05-12 00:54:44.000000000","message":"This can be done as part of the Heat template itself. It can be done using the Ceilometer:Alarm resource in the Heat template.  See https://drive.google.com/file/d/0B-ruQ8Tx46wSNFdnVkNfR3Z4aDFXZ1F5R0ttLTRPQVhBQ1VJ/view for details. The fact that Ceilometer configuration can be done directly in Heat means that the Ceilometer monitoring driver will not be needed for Ceilometer configuration and action functionality that is already implemented in Heat.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"65c6e4b4465d4288509eac9dc900d060c97ed8b5","unresolved":false,"context_lines":[{"line_number":204,"context_line":"          actions:"},{"line_number":205,"context_line":"            - {trigger: failure, action: scale_up}"},{"line_number":206,"context_line":""},{"line_number":207,"context_line":"2. Ensure that Heat can set successfully alarm configuration into Ceilometer."},{"line_number":208,"context_line":""},{"line_number":209,"context_line":"3. The monitoring driver can get alarm when VNFs go down or get overloaded."},{"line_number":210,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_9eafee2a","line":207,"range":{"start_line":207,"start_character":0,"end_line":207,"end_character":77},"in_reply_to":"dab17558_58d13f22","updated":"2016-05-12 14:56:28.000000000","message":"Sorry, this sentence is not clear. I mean Heat driver could translate successfully TOSCA elements to HOT resource.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":19465,"name":"Bruce Thompson","email":"brucet@cisco.com","username":"brucetcisco"},"change_message_id":"c9a98e625893e5b105a054421e9574f4f90e311e","unresolved":false,"context_lines":[{"line_number":206,"context_line":""},{"line_number":207,"context_line":"2. Ensure that Heat can set successfully alarm configuration into Ceilometer."},{"line_number":208,"context_line":""},{"line_number":209,"context_line":"3. The monitoring driver can get alarm when VNFs go down or get overloaded."},{"line_number":210,"context_line":""},{"line_number":211,"context_line":"Dependencies"},{"line_number":212,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_1834d747","line":209,"range":{"start_line":209,"start_character":0,"end_line":209,"end_character":75},"updated":"2016-05-12 00:54:44.000000000","message":"It is possible for the monitoring driver to get Ceilometer events using the Heat webhook functionality. See https://drive.google.com/file/d/0B-ruQ8Tx46wSNFdnVkNfR3Z4aDFXZ1F5R0ttLTRPQVhBQ1VJ/view for details.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"65c6e4b4465d4288509eac9dc900d060c97ed8b5","unresolved":false,"context_lines":[{"line_number":206,"context_line":""},{"line_number":207,"context_line":"2. Ensure that Heat can set successfully alarm configuration into Ceilometer."},{"line_number":208,"context_line":""},{"line_number":209,"context_line":"3. The monitoring driver can get alarm when VNFs go down or get overloaded."},{"line_number":210,"context_line":""},{"line_number":211,"context_line":"Dependencies"},{"line_number":212,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"dab17558_f4baa070","line":209,"range":{"start_line":209,"start_character":0,"end_line":209,"end_character":75},"in_reply_to":"dab17558_1834d747","updated":"2016-05-12 14:56:28.000000000","message":"Please see my explanation above and let me consider your case.","commit_id":"212e637905ac55514d97d77a41829911ef7f675f"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"f5669874b8101a9f8a44c0fa9d6dc2b5e8aecec8","unresolved":false,"context_lines":[{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":"https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Add support to auto-scale the VNF VDUs using heat auto-scaling  by monitoring"},{"line_number":8,"context_line":"them using ceilometer."},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"Problem description"},{"line_number":11,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_9797358f","line":8,"range":{"start_line":7,"start_character":0,"end_line":8,"end_character":22},"updated":"2016-05-16 21:45:50.000000000","message":"The above statement leads to mean this spec is purely about auto-scaling. IMHO it made of equal parts alarm-based monitoring and auto-scaling :) Auto-scale is just one action that the VNFD template author can choose.\n\nPerhaps this should be be worded as,\n\n\"Add support for alarm based monitoring using ceilometer and auto-scale action for VNF VDUs\"\n\nI\u0027m wondering whether we should split this effort into two specs,\n\n1) alarm based monitoring WITHOUT auto-scaling\n2) auto and manual scaling using custom and alarm based monitoring\n\nWe can let (1) go in first and have (2) as a dependent blueprint immediately following (1).\n\nWhat do you think ?","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":13485,"name":"Sripriya Seetharam","email":"sseetha@brocade.com","username":"Sripriya"},"change_message_id":"5a1c2d094688926654e30f7909f32b84e77634dd","unresolved":false,"context_lines":[{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":"https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Add support to auto-scale the VNF VDUs using heat auto-scaling  by monitoring"},{"line_number":8,"context_line":"them using ceilometer."},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"Problem description"},{"line_number":11,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_a8177443","line":8,"range":{"start_line":7,"start_character":0,"end_line":8,"end_character":22},"in_reply_to":"dab17558_6d247e0c","updated":"2016-05-17 00:41:20.000000000","message":"we should provide support for multiple actions for a single policy. the user would want to log the event and also scale up/down based on vdu alarms","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":13485,"name":"Sripriya Seetharam","email":"sseetha@brocade.com","username":"Sripriya"},"change_message_id":"5a1c2d094688926654e30f7909f32b84e77634dd","unresolved":false,"context_lines":[{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":"https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Add support to auto-scale the VNF VDUs using heat auto-scaling  by monitoring"},{"line_number":8,"context_line":"them using ceilometer."},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"Problem description"},{"line_number":11,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_cd4beaaf","line":8,"range":{"start_line":7,"start_character":0,"end_line":8,"end_character":22},"in_reply_to":"dab17558_9797358f","updated":"2016-05-17 00:41:20.000000000","message":"+1 agree","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":16511,"name":"Bob Haddleton","email":"bob.haddleton@nokia.com","username":"bobh"},"change_message_id":"e968fc1c7c59d2a2782ec879fed32f394d35dee4","unresolved":false,"context_lines":[{"line_number":5,"context_line":"https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Add support to auto-scale the VNF VDUs using heat auto-scaling  by monitoring"},{"line_number":8,"context_line":"them using ceilometer."},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"Problem description"},{"line_number":11,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_b907c716","line":8,"in_reply_to":"dab17558_9797358f","updated":"2016-05-17 02:13:27.000000000","message":"I think this bp should focus on the implementation of a Ceilometer monitoring plugin, and then subsequent blueprints can deal with the actions triggered by the ceilometer plugin.","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"3b2f4d8173c03e3fe919f806f2934b79613918f6","unresolved":false,"context_lines":[{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":"https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Add support to auto-scale the VNF VDUs using heat auto-scaling  by monitoring"},{"line_number":8,"context_line":"them using ceilometer."},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"Problem description"},{"line_number":11,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_6d247e0c","line":8,"range":{"start_line":7,"start_character":0,"end_line":8,"end_character":22},"in_reply_to":"dab17558_9797358f","updated":"2016-05-16 22:56:53.000000000","message":"Thank you, Kanagaraj and Sridhar.\nI also agree that this PatchSet seems to focus on auto-scaling. Because the spec itself is about the alarm-based monitoring driver, I would like to drive this spec with actions:\n-  \"Log\" action: The monitoring driver supports VNF resource monitoring. The monitoring information can be used to report to Tacker user.\n- \"scale up/down\" action: The monitoring driver supports automatic/manual scaling. In terms of auto-scaling, I need Kanagaraj\u0027s help. I could try with manual scaling.\n\nIs fine for you, Sridhar?","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":16511,"name":"Bob Haddleton","email":"bob.haddleton@nokia.com","username":"bobh"},"change_message_id":"e968fc1c7c59d2a2782ec879fed32f394d35dee4","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"ETSI MANO atchitecture describes to monitor the VNF to take appropriate action"},{"line_number":14,"context_line":"such as fault management, performance management. For example, when the VNF"},{"line_number":15,"context_line":"element\u0027s CPU reaches the threshold, automatically it needs to be scaled up and"},{"line_number":16,"context_line":"vice-versa. so monitoring became as important aspect in MANO architecture."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"Currently, Tacker provides an very minimal support for check the liveliness"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_1946d47a","line":15,"updated":"2016-05-17 02:13:27.000000000","message":"This should be scale-out not up, right?","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"3abecc733fad8148c203eb6b2fc6bce702ba21ec","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"ETSI MANO atchitecture describes to monitor the VNF to take appropriate action"},{"line_number":14,"context_line":"such as fault management, performance management. For example, when the VNF"},{"line_number":15,"context_line":"element\u0027s CPU reaches the threshold, automatically it needs to be scaled up and"},{"line_number":16,"context_line":"vice-versa. so monitoring became as important aspect in MANO architecture."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"Currently, Tacker provides an very minimal support for check the liveliness"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_7314459f","line":15,"in_reply_to":"dab17558_1946d47a","updated":"2016-05-17 12:16:51.000000000","message":"yes, scale-in/out. thanks","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":16511,"name":"Bob Haddleton","email":"bob.haddleton@nokia.com","username":"bobh"},"change_message_id":"e968fc1c7c59d2a2782ec879fed32f394d35dee4","unresolved":false,"context_lines":[{"line_number":25,"context_line":"Proposed change"},{"line_number":26,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"To support scaling VDU:"},{"line_number":29,"context_line":"-----------------------"},{"line_number":30,"context_line":"In OpenStack, heat does provide an feature to setup a scaling group, which can"},{"line_number":31,"context_line":"be scaled up/down based on the pre-defined scaling policy. Here scaling group"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_396117d4","line":28,"updated":"2016-05-17 02:13:27.000000000","message":"This whole section probably belongs in a separate bp","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"3abecc733fad8148c203eb6b2fc6bce702ba21ec","unresolved":false,"context_lines":[{"line_number":25,"context_line":"Proposed change"},{"line_number":26,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"To support scaling VDU:"},{"line_number":29,"context_line":"-----------------------"},{"line_number":30,"context_line":"In OpenStack, heat does provide an feature to setup a scaling group, which can"},{"line_number":31,"context_line":"be scaled up/down based on the pre-defined scaling policy. Here scaling group"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_f36f9528","line":28,"in_reply_to":"dab17558_396117d4","updated":"2016-05-17 12:16:51.000000000","message":"sure, let us discuss in today\u0027s IRC meeting.","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":16511,"name":"Bob Haddleton","email":"bob.haddleton@nokia.com","username":"bobh"},"change_message_id":"e968fc1c7c59d2a2782ec879fed32f394d35dee4","unresolved":false,"context_lines":[{"line_number":28,"context_line":"To support scaling VDU:"},{"line_number":29,"context_line":"-----------------------"},{"line_number":30,"context_line":"In OpenStack, heat does provide an feature to setup a scaling group, which can"},{"line_number":31,"context_line":"be scaled up/down based on the pre-defined scaling policy. Here scaling group"},{"line_number":32,"context_line":"can contain any OpenStack resource such as nova instance, cinder volume, etc,"},{"line_number":33,"context_line":"where as scaling policy helps to scale up/down in numbers, percentage, etc."},{"line_number":34,"context_line":"so this heat feature could be used to accomplish the scaling of VDU in"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_3938f8ed","line":31,"updated":"2016-05-17 02:13:27.000000000","message":"should be scaled out/in","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"3abecc733fad8148c203eb6b2fc6bce702ba21ec","unresolved":false,"context_lines":[{"line_number":28,"context_line":"To support scaling VDU:"},{"line_number":29,"context_line":"-----------------------"},{"line_number":30,"context_line":"In OpenStack, heat does provide an feature to setup a scaling group, which can"},{"line_number":31,"context_line":"be scaled up/down based on the pre-defined scaling policy. Here scaling group"},{"line_number":32,"context_line":"can contain any OpenStack resource such as nova instance, cinder volume, etc,"},{"line_number":33,"context_line":"where as scaling policy helps to scale up/down in numbers, percentage, etc."},{"line_number":34,"context_line":"so this heat feature could be used to accomplish the scaling of VDU in"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_b3586d8b","line":31,"in_reply_to":"dab17558_3938f8ed","updated":"2016-05-17 12:16:51.000000000","message":"yes","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":16511,"name":"Bob Haddleton","email":"bob.haddleton@nokia.com","username":"bobh"},"change_message_id":"e968fc1c7c59d2a2782ec879fed32f394d35dee4","unresolved":false,"context_lines":[{"line_number":30,"context_line":"In OpenStack, heat does provide an feature to setup a scaling group, which can"},{"line_number":31,"context_line":"be scaled up/down based on the pre-defined scaling policy. Here scaling group"},{"line_number":32,"context_line":"can contain any OpenStack resource such as nova instance, cinder volume, etc,"},{"line_number":33,"context_line":"where as scaling policy helps to scale up/down in numbers, percentage, etc."},{"line_number":34,"context_line":"so this heat feature could be used to accomplish the scaling of VDU in"},{"line_number":35,"context_line":"tacker as mentioned below:"},{"line_number":36,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_59233cbd","line":33,"updated":"2016-05-17 02:13:27.000000000","message":"out/in","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":16511,"name":"Bob Haddleton","email":"bob.haddleton@nokia.com","username":"bobh"},"change_message_id":"e968fc1c7c59d2a2782ec879fed32f394d35dee4","unresolved":false,"context_lines":[{"line_number":36,"context_line":""},{"line_number":37,"context_line":"#. Model the VNF VDU element to be part of heat scaling group"},{"line_number":38,"context_line":"OS::Heat::ScalingGroup. For example, consider a simple VNF VDU with m1.medium"},{"line_number":39,"context_line":"falvor. Now we wanted this VDU to be scaled up/down between 2 to 5 counts with"},{"line_number":40,"context_line":"initial setup with 3 elements. In this case, use the below heat template to"},{"line_number":41,"context_line":"setup the scale group."},{"line_number":42,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_3933d7f7","line":39,"updated":"2016-05-17 02:13:27.000000000","message":"out/in","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":16511,"name":"Bob Haddleton","email":"bob.haddleton@nokia.com","username":"bobh"},"change_message_id":"e968fc1c7c59d2a2782ec879fed32f394d35dee4","unresolved":false,"context_lines":[{"line_number":61,"context_line":""},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"NOTE:"},{"line_number":64,"context_line":"* if VDU scale group could be modeled in TOSCA, then same has to be"},{"line_number":65,"context_line":"supported in heat template-traslator to convert in into heat scaling group."},{"line_number":66,"context_line":"* Make use of vnfd template parameterization to customize min_size, max_size,"},{"line_number":67,"context_line":"desired_capacity and flavor based on scaling need and same has to made as"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_f9430f40","line":64,"updated":"2016-05-17 02:13:27.000000000","message":"This can\u0027t be optional - it must be able to be modeled in TOSCA","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"3abecc733fad8148c203eb6b2fc6bce702ba21ec","unresolved":false,"context_lines":[{"line_number":61,"context_line":""},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"NOTE:"},{"line_number":64,"context_line":"* if VDU scale group could be modeled in TOSCA, then same has to be"},{"line_number":65,"context_line":"supported in heat template-traslator to convert in into heat scaling group."},{"line_number":66,"context_line":"* Make use of vnfd template parameterization to customize min_size, max_size,"},{"line_number":67,"context_line":"desired_capacity and flavor based on scaling need and same has to made as"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_f3ddd5e0","line":64,"in_reply_to":"dab17558_f9430f40","updated":"2016-05-17 12:16:51.000000000","message":"sure, i was in doubt. thanks.","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":13485,"name":"Sripriya Seetharam","email":"sseetha@brocade.com","username":"Sripriya"},"change_message_id":"5a1c2d094688926654e30f7909f32b84e77634dd","unresolved":false,"context_lines":[{"line_number":97,"context_line":"For those VDU with support of scaling, use this template while on-boarding"},{"line_number":98,"context_line":"them."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"To support monitoring CPU/memory usage of VDU:"},{"line_number":101,"context_line":"----------------------------------------------"},{"line_number":102,"context_line":"OpenStack ceilometer provides the monitoring feature to monitor a given"},{"line_number":103,"context_line":"OpenStack element or set of elements and same could be used to monitor the"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_1eccfab9","line":100,"range":{"start_line":100,"start_character":1,"end_line":100,"end_character":46},"updated":"2016-05-17 00:41:20.000000000","message":"i think the ceilometer driver should monitor beyond VDU resource and should include CP resources as well, it will be beneficial to monitor port resources since we are integrating ceilometer which has loads of capabilities. the scope for this spec is not just monitor and scale but in general monitor VNF resources","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"3abecc733fad8148c203eb6b2fc6bce702ba21ec","unresolved":false,"context_lines":[{"line_number":97,"context_line":"For those VDU with support of scaling, use this template while on-boarding"},{"line_number":98,"context_line":"them."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"To support monitoring CPU/memory usage of VDU:"},{"line_number":101,"context_line":"----------------------------------------------"},{"line_number":102,"context_line":"OpenStack ceilometer provides the monitoring feature to monitor a given"},{"line_number":103,"context_line":"OpenStack element or set of elements and same could be used to monitor the"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_53366103","line":100,"range":{"start_line":100,"start_character":1,"end_line":100,"end_character":46},"in_reply_to":"dab17558_1eccfab9","updated":"2016-05-17 12:16:51.000000000","message":"Ceilometer does support to monitor any resources in OpenStack in theory:) i used to the word vdu to be generic enough which would consist all required things for VNF.","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":16511,"name":"Bob Haddleton","email":"bob.haddleton@nokia.com","username":"bobh"},"change_message_id":"e968fc1c7c59d2a2782ec879fed32f394d35dee4","unresolved":false,"context_lines":[{"line_number":97,"context_line":"For those VDU with support of scaling, use this template while on-boarding"},{"line_number":98,"context_line":"them."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"To support monitoring CPU/memory usage of VDU:"},{"line_number":101,"context_line":"----------------------------------------------"},{"line_number":102,"context_line":"OpenStack ceilometer provides the monitoring feature to monitor a given"},{"line_number":103,"context_line":"OpenStack element or set of elements and same could be used to monitor the"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_39b8f729","line":100,"in_reply_to":"dab17558_1eccfab9","updated":"2016-05-17 02:13:27.000000000","message":"Ideally the ceilometer driver should be able to monitor any resource that ceilometer can monitor - it should be possible to pass parameters to the monitor driver and/or model the appropriate TOSCA resources.","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"355a0fe415982a88d1e0a7a73e1d3dbb0895139b","unresolved":false,"context_lines":[{"line_number":97,"context_line":"For those VDU with support of scaling, use this template while on-boarding"},{"line_number":98,"context_line":"them."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"To support monitoring CPU/memory usage of VDU:"},{"line_number":101,"context_line":"----------------------------------------------"},{"line_number":102,"context_line":"OpenStack ceilometer provides the monitoring feature to monitor a given"},{"line_number":103,"context_line":"OpenStack element or set of elements and same could be used to monitor the"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_997da36f","line":100,"range":{"start_line":100,"start_character":1,"end_line":100,"end_character":46},"in_reply_to":"dab17558_1eccfab9","updated":"2016-05-17 02:25:49.000000000","message":"good catch! Thanks Sripriya. I will think about this and update the spec as soon as possible.","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"3abecc733fad8148c203eb6b2fc6bce702ba21ec","unresolved":false,"context_lines":[{"line_number":97,"context_line":"For those VDU with support of scaling, use this template while on-boarding"},{"line_number":98,"context_line":"them."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"To support monitoring CPU/memory usage of VDU:"},{"line_number":101,"context_line":"----------------------------------------------"},{"line_number":102,"context_line":"OpenStack ceilometer provides the monitoring feature to monitor a given"},{"line_number":103,"context_line":"OpenStack element or set of elements and same could be used to monitor the"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_f32795c7","line":100,"in_reply_to":"dab17558_39b8f729","updated":"2016-05-17 12:16:51.000000000","message":"yes","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":16511,"name":"Bob Haddleton","email":"bob.haddleton@nokia.com","username":"bobh"},"change_message_id":"e968fc1c7c59d2a2782ec879fed32f394d35dee4","unresolved":false,"context_lines":[{"line_number":101,"context_line":"----------------------------------------------"},{"line_number":102,"context_line":"OpenStack ceilometer provides the monitoring feature to monitor a given"},{"line_number":103,"context_line":"OpenStack element or set of elements and same could be used to monitor the"},{"line_number":104,"context_line":"VNF VDU scaling group. There are two options available to consume this feature"},{"line_number":105,"context_line":"in tacker as below:"},{"line_number":106,"context_line":""},{"line_number":107,"context_line":"1. Use heat celilometer resource type: In this approach, tacker will create"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_5987bb60","line":104,"updated":"2016-05-17 02:13:27.000000000","message":"I would decouple this from scaling and focus on the generic ceilometer monitoring capabilities","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":16511,"name":"Bob Haddleton","email":"bob.haddleton@nokia.com","username":"bobh"},"change_message_id":"e968fc1c7c59d2a2782ec879fed32f394d35dee4","unresolved":false,"context_lines":[{"line_number":139,"context_line":"          threshold: 15"},{"line_number":140,"context_line":"          comparison_operator: lt"},{"line_number":141,"context_line":""},{"line_number":142,"context_line":"NOTE:"},{"line_number":143,"context_line":"* add alarm_actions to both of these alarm with either signal_url provided by"},{"line_number":144,"context_line":"heat or tacker monitoring websocket created per scaling VDU. In early case,"},{"line_number":145,"context_line":"heat will do scaling automatically, without the knowledge of tacker, which is"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_398f5776","line":142,"updated":"2016-05-17 02:13:27.000000000","message":"Also need to define the TOSCA modeling for the alarms","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"3abecc733fad8148c203eb6b2fc6bce702ba21ec","unresolved":false,"context_lines":[{"line_number":139,"context_line":"          threshold: 15"},{"line_number":140,"context_line":"          comparison_operator: lt"},{"line_number":141,"context_line":""},{"line_number":142,"context_line":"NOTE:"},{"line_number":143,"context_line":"* add alarm_actions to both of these alarm with either signal_url provided by"},{"line_number":144,"context_line":"heat or tacker monitoring websocket created per scaling VDU. In early case,"},{"line_number":145,"context_line":"heat will do scaling automatically, without the knowledge of tacker, which is"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_66280187","line":142,"in_reply_to":"dab17558_398f5776","updated":"2016-05-17 12:16:51.000000000","message":"yes.","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":16511,"name":"Bob Haddleton","email":"bob.haddleton@nokia.com","username":"bobh"},"change_message_id":"e968fc1c7c59d2a2782ec879fed32f394d35dee4","unresolved":false,"context_lines":[{"line_number":240,"context_line":"Work Items"},{"line_number":241,"context_line":"------------------"},{"line_number":242,"context_line":""},{"line_number":243,"context_line":"#. enable the on-boarding with sacling VDU"},{"line_number":244,"context_line":"#. Tosca monitoring elment model to Heat ceilometer monitoring element"},{"line_number":245,"context_line":"   translation"},{"line_number":246,"context_line":"#. Enable the new convention in vnfd for mentioning of scaling and alarm based"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_39e63744","line":243,"updated":"2016-05-17 02:13:27.000000000","message":"All scaling references should move to a separate bp","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"3abecc733fad8148c203eb6b2fc6bce702ba21ec","unresolved":false,"context_lines":[{"line_number":240,"context_line":"Work Items"},{"line_number":241,"context_line":"------------------"},{"line_number":242,"context_line":""},{"line_number":243,"context_line":"#. enable the on-boarding with sacling VDU"},{"line_number":244,"context_line":"#. Tosca monitoring elment model to Heat ceilometer monitoring element"},{"line_number":245,"context_line":"   translation"},{"line_number":246,"context_line":"#. Enable the new convention in vnfd for mentioning of scaling and alarm based"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_a61e695c","line":243,"in_reply_to":"dab17558_39e63744","updated":"2016-05-17 12:16:51.000000000","message":"ok","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":16511,"name":"Bob Haddleton","email":"bob.haddleton@nokia.com","username":"bobh"},"change_message_id":"e968fc1c7c59d2a2782ec879fed32f394d35dee4","unresolved":false,"context_lines":[{"line_number":244,"context_line":"#. Tosca monitoring elment model to Heat ceilometer monitoring element"},{"line_number":245,"context_line":"   translation"},{"line_number":246,"context_line":"#. Enable the new convention in vnfd for mentioning of scaling and alarm based"},{"line_number":247,"context_line":"   monitoring parameters"},{"line_number":248,"context_line":"#. create a new monitoring driver for alarm based monitoring with configurable"},{"line_number":249,"context_line":"   parameter to use either of the apporach mentioned above."},{"line_number":250,"context_line":"#. create an websocket/ equivalent REST API to make celilometer to signal it"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_f9c66f98","line":247,"updated":"2016-05-17 02:13:27.000000000","message":"This is the same as the TOSCA modeling","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"3abecc733fad8148c203eb6b2fc6bce702ba21ec","unresolved":false,"context_lines":[{"line_number":244,"context_line":"#. Tosca monitoring elment model to Heat ceilometer monitoring element"},{"line_number":245,"context_line":"   translation"},{"line_number":246,"context_line":"#. Enable the new convention in vnfd for mentioning of scaling and alarm based"},{"line_number":247,"context_line":"   monitoring parameters"},{"line_number":248,"context_line":"#. create a new monitoring driver for alarm based monitoring with configurable"},{"line_number":249,"context_line":"   parameter to use either of the apporach mentioned above."},{"line_number":250,"context_line":"#. create an websocket/ equivalent REST API to make celilometer to signal it"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_062e558b","line":247,"in_reply_to":"dab17558_f9c66f98","updated":"2016-05-17 12:16:51.000000000","message":"yes","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":16511,"name":"Bob Haddleton","email":"bob.haddleton@nokia.com","username":"bobh"},"change_message_id":"e968fc1c7c59d2a2782ec879fed32f394d35dee4","unresolved":false,"context_lines":[{"line_number":245,"context_line":"   translation"},{"line_number":246,"context_line":"#. Enable the new convention in vnfd for mentioning of scaling and alarm based"},{"line_number":247,"context_line":"   monitoring parameters"},{"line_number":248,"context_line":"#. create a new monitoring driver for alarm based monitoring with configurable"},{"line_number":249,"context_line":"   parameter to use either of the apporach mentioned above."},{"line_number":250,"context_line":"#. create an websocket/ equivalent REST API to make celilometer to signal it"},{"line_number":251,"context_line":"   on the event of alarm. Make this API with required RBAC. if this could be"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_593cdb92","line":248,"updated":"2016-05-17 02:13:27.000000000","message":"This should be the focus of this BP and probably needs to be decomposed into smaller work items","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"3abecc733fad8148c203eb6b2fc6bce702ba21ec","unresolved":false,"context_lines":[{"line_number":245,"context_line":"   translation"},{"line_number":246,"context_line":"#. Enable the new convention in vnfd for mentioning of scaling and alarm based"},{"line_number":247,"context_line":"   monitoring parameters"},{"line_number":248,"context_line":"#. create a new monitoring driver for alarm based monitoring with configurable"},{"line_number":249,"context_line":"   parameter to use either of the apporach mentioned above."},{"line_number":250,"context_line":"#. create an websocket/ equivalent REST API to make celilometer to signal it"},{"line_number":251,"context_line":"   on the event of alarm. Make this API with required RBAC. if this could be"}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_264a7955","line":248,"in_reply_to":"dab17558_593cdb92","updated":"2016-05-17 12:16:51.000000000","message":"i assumed most of the impl will fall in monitor_call(), but now i see, its better to define all other methods as well.","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":13485,"name":"Sripriya Seetharam","email":"sseetha@brocade.com","username":"Sripriya"},"change_message_id":"5a1c2d094688926654e30f7909f32b84e77634dd","unresolved":false,"context_lines":[{"line_number":276,"context_line":"          param0: key1"},{"line_number":277,"context_line":"          param1: key2"},{"line_number":278,"context_line":"        monitoring_policy:"},{"line_number":279,"context_line":"          name: cpu_util"},{"line_number":280,"context_line":"          parameters:"},{"line_number":281,"context_line":"            statistic: avg"},{"line_number":282,"context_line":"            period: \"60\""}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_c3f9fb4f","line":279,"range":{"start_line":279,"start_character":10,"end_line":279,"end_character":24},"updated":"2016-05-17 00:41:20.000000000","message":"we could provide multiple monitoring_policies here, we should plan to accommodate this as well in the driver","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"355a0fe415982a88d1e0a7a73e1d3dbb0895139b","unresolved":false,"context_lines":[{"line_number":276,"context_line":"          param0: key1"},{"line_number":277,"context_line":"          param1: key2"},{"line_number":278,"context_line":"        monitoring_policy:"},{"line_number":279,"context_line":"          name: cpu_util"},{"line_number":280,"context_line":"          parameters:"},{"line_number":281,"context_line":"            statistic: avg"},{"line_number":282,"context_line":"            period: \"60\""}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_d93c4b31","line":279,"range":{"start_line":279,"start_character":10,"end_line":279,"end_character":24},"in_reply_to":"dab17558_c3f9fb4f","updated":"2016-05-17 02:25:49.000000000","message":"I have already thought about this. However, in real implementation it may be complicated to deploy multiple policies at the same time.","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"3abecc733fad8148c203eb6b2fc6bce702ba21ec","unresolved":false,"context_lines":[{"line_number":276,"context_line":"          param0: key1"},{"line_number":277,"context_line":"          param1: key2"},{"line_number":278,"context_line":"        monitoring_policy:"},{"line_number":279,"context_line":"          name: cpu_util"},{"line_number":280,"context_line":"          parameters:"},{"line_number":281,"context_line":"            statistic: avg"},{"line_number":282,"context_line":"            period: \"60\""}],"source_content_type":"text/x-rst","patch_set":5,"id":"dab17558_a67ae974","line":279,"range":{"start_line":279,"start_character":10,"end_line":279,"end_character":24},"in_reply_to":"dab17558_d93c4b31","updated":"2016-05-17 12:16:51.000000000","message":"I assume policy means the definition of threshold for alarm and its possible to define multiple alarms as aggregate alarm in heat/ceilometer.","commit_id":"94371fec7281135cecc31230b92d9f1fa6fcde1e"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"39fee8a1f0c933e76e19ccf3ab4252e9cce0737b","unresolved":false,"context_lines":[{"line_number":1,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":2,"context_line":"Add alarm-based monitoring driver to Tacker"},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":"https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver"},{"line_number":5,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_3b7db9b1","line":2,"range":{"start_line":2,"start_character":34,"end_line":2,"end_character":36},"updated":"2016-05-20 09:38:57.000000000","message":"nit:for","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"cb25daeafc3c9688797c61416558c0189cda2db6","unresolved":false,"context_lines":[{"line_number":1,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":2,"context_line":"Add alarm-based monitoring driver to Tacker"},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":"https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver"},{"line_number":5,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_3cb2cc4c","line":2,"range":{"start_line":2,"start_character":34,"end_line":2,"end_character":36},"in_reply_to":"bab6814e_3b7db9b1","updated":"2016-05-20 18:49:22.000000000","message":"Done","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"39fee8a1f0c933e76e19ccf3ab4252e9cce0737b","unresolved":false,"context_lines":[{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":"https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"This spec describes the plan to introduce an alarm-based monitoring driver in Tacker"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Problem description"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_9b1ae57b","line":6,"range":{"start_line":6,"start_character":20,"end_line":6,"end_character":41},"updated":"2016-05-20 09:38:57.000000000","message":"nit:kindly remove this, as this spec has the details on impl than the plan.","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"cb25daeafc3c9688797c61416558c0189cda2db6","unresolved":false,"context_lines":[{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":"https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"This spec describes the plan to introduce an alarm-based monitoring driver in Tacker"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Problem description"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_7cb8d42a","line":6,"range":{"start_line":6,"start_character":20,"end_line":6,"end_character":41},"in_reply_to":"bab6814e_9b1ae57b","updated":"2016-05-20 18:49:22.000000000","message":"Done","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"a788583db4a5e28655ccfecadc2d23862c011ecd","unresolved":false,"context_lines":[{"line_number":14,"context_line":"reaches the threshold, some actions can be considered:"},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"* report to NFV users. The main focus in this spec is on \"log\" action in the"},{"line_number":17,"context_line":"  alarm-based monitoring. Accordingly, the alarm-based monitoring drivers should"},{"line_number":18,"context_line":"  have capability to monitor whatever Ceilometer can support.Forcibly, these"},{"line_number":19,"context_line":"  resources have to be modelized in the monitoring policy of TOSCA template. For"},{"line_number":20,"context_line":"  example, the alarm-based monitoring driver could monitor both VNF resources"},{"line_number":21,"context_line":"  and network resources."}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_8c2126ff","line":18,"range":{"start_line":17,"start_character":39,"end_line":18,"end_character":60},"updated":"2016-05-25 18:28:40.000000000","message":"While agree leveraging Ceilometer is the right approach, please ensure Tacker\u0027s alarm based monitoring feature is NOT hard coded to only work with Ceilometer. Down the line, we might need to consider getting alarms from Monasca or even some custom systems already in place in the operator\u0027s network.","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":12525,"name":"vishwanath jayaraman","email":"vishwanathj@hotmail.com","username":"vish"},"change_message_id":"46dfc1f2045b4ab29df24c17b0220a5d6a830085","unresolved":false,"context_lines":[{"line_number":15,"context_line":""},{"line_number":16,"context_line":"* report to NFV users. The main focus in this spec is on \"log\" action in the"},{"line_number":17,"context_line":"  alarm-based monitoring. Accordingly, the alarm-based monitoring drivers should"},{"line_number":18,"context_line":"  have capability to monitor whatever Ceilometer can support.Forcibly, these"},{"line_number":19,"context_line":"  resources have to be modelized in the monitoring policy of TOSCA template. For"},{"line_number":20,"context_line":"  example, the alarm-based monitoring driver could monitor both VNF resources"},{"line_number":21,"context_line":"  and network resources."}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_c6853b5a","line":18,"updated":"2016-05-24 02:19:46.000000000","message":"clarify: can you elaborate on what you mean by \"whatever ceilometer supports\"?","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"1dedf11df37fc1ec2f8fa585f7c851a749c8973c","unresolved":false,"context_lines":[{"line_number":14,"context_line":"reaches the threshold, some actions can be considered:"},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"* report to NFV users. The main focus in this spec is on \"log\" action in the"},{"line_number":17,"context_line":"  alarm-based monitoring. Accordingly, the alarm-based monitoring drivers should"},{"line_number":18,"context_line":"  have capability to monitor whatever Ceilometer can support.Forcibly, these"},{"line_number":19,"context_line":"  resources have to be modelized in the monitoring policy of TOSCA template. For"},{"line_number":20,"context_line":"  example, the alarm-based monitoring driver could monitor both VNF resources"},{"line_number":21,"context_line":"  and network resources."}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_fb1e910a","line":18,"range":{"start_line":17,"start_character":39,"end_line":18,"end_character":60},"in_reply_to":"bab6814e_7183e756","updated":"2016-05-26 06:58:44.000000000","message":"Hi all,\nI agree that a generic monitoring framework need to be considered in Tacker.\nOnce the alarm-based monitoring driver works fine with the support of Ceilometer, it is possible to leverage Monasca as well. IMHO, leveraging Ceilonmeter or Monasca is the same way in terms of the alarm-based monitoring driver. We could get alarms triggered by Monasca as well. I also believed that the alarm monitoring driver itself is generic enough to cover both Ceilometer and Monasca. However, we need to choose a specific monitoring driver to go. That\u0027s why I mention to Ceilometer in this spec.","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":8246,"name":"Qiming Teng","email":"tengqm@outlook.com","username":"tengqm"},"change_message_id":"ca9aa685ee212cd08c7b87493af8b957379c4132","unresolved":false,"context_lines":[{"line_number":14,"context_line":"reaches the threshold, some actions can be considered:"},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"* report to NFV users. The main focus in this spec is on \"log\" action in the"},{"line_number":17,"context_line":"  alarm-based monitoring. Accordingly, the alarm-based monitoring drivers should"},{"line_number":18,"context_line":"  have capability to monitor whatever Ceilometer can support.Forcibly, these"},{"line_number":19,"context_line":"  resources have to be modelized in the monitoring policy of TOSCA template. For"},{"line_number":20,"context_line":"  example, the alarm-based monitoring driver could monitor both VNF resources"},{"line_number":21,"context_line":"  and network resources."}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_7183e756","line":18,"range":{"start_line":17,"start_character":39,"end_line":18,"end_character":60},"in_reply_to":"bab6814e_8c2126ff","updated":"2016-05-26 03:19:21.000000000","message":"+2, maybe what is needed is an abstraction of \u0027alarm\u0027 or \u0027trigger\u0027. Ceilometer can be one of the drivers. If needed, users/developers can contribute their own drivers.","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"c3112b6ebdd310dc6bb2f5296887b270c849b344","unresolved":false,"context_lines":[{"line_number":15,"context_line":""},{"line_number":16,"context_line":"* report to NFV users. The main focus in this spec is on \"log\" action in the"},{"line_number":17,"context_line":"  alarm-based monitoring. Accordingly, the alarm-based monitoring drivers should"},{"line_number":18,"context_line":"  have capability to monitor whatever Ceilometer can support.Forcibly, these"},{"line_number":19,"context_line":"  resources have to be modelized in the monitoring policy of TOSCA template. For"},{"line_number":20,"context_line":"  example, the alarm-based monitoring driver could monitor both VNF resources"},{"line_number":21,"context_line":"  and network resources."}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_13f918c9","line":18,"in_reply_to":"bab6814e_c6853b5a","updated":"2016-05-24 16:18:58.000000000","message":"The alarm-based monitoring driver collects alarms triggered by Ceilometer. These alarms are not only about CPU usage and memory usage. As long as Ceilometer could monitor, everything which makes VNFs fault are very good inputs in Tacker.","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"56071edad4929208aabf3f1c70a15a43c7dc062b","unresolved":false,"context_lines":[{"line_number":14,"context_line":"reaches the threshold, some actions can be considered:"},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"* report to NFV users. The main focus in this spec is on \"log\" action in the"},{"line_number":17,"context_line":"  alarm-based monitoring. Accordingly, the alarm-based monitoring drivers should"},{"line_number":18,"context_line":"  have capability to monitor whatever Ceilometer can support.Forcibly, these"},{"line_number":19,"context_line":"  resources have to be modelized in the monitoring policy of TOSCA template. For"},{"line_number":20,"context_line":"  example, the alarm-based monitoring driver could monitor both VNF resources"},{"line_number":21,"context_line":"  and network resources."}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_1b2ec78b","line":18,"range":{"start_line":17,"start_character":39,"end_line":18,"end_character":60},"in_reply_to":"bab6814e_fb1e910a","updated":"2016-05-26 21:03:39.000000000","message":"Sure. I\u0027d say we need two deliverables,\n\n(a) tacker alarm framework - generic layer to handle alarm request and responses from underlying alarm drivers.\n(b) one alarm driver using Ceilometer for the above framework - that handles the creation of ceilometer alarms and handles callbacks/webhooks from ceilometer.","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"39fee8a1f0c933e76e19ccf3ab4252e9cce0737b","unresolved":false,"context_lines":[{"line_number":18,"context_line":"  have capability to monitor whatever Ceilometer can support.Forcibly, these"},{"line_number":19,"context_line":"  resources have to be modelized in the monitoring policy of TOSCA template. For"},{"line_number":20,"context_line":"  example, the alarm-based monitoring driver could monitor both VNF resources"},{"line_number":21,"context_line":"  and network resources."},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"* automatically it needs to be scaled out and vice-versa. This action is out of"},{"line_number":24,"context_line":"  scope in the spec. In fact, the alarm-based monitoring driver does not directly"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_2647604c","line":21,"updated":"2016-05-20 09:38:57.000000000","message":"kindly separate this paragraph and keep only the problem space here while the solution you have mentioned here could be moved to below section.","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"cb25daeafc3c9688797c61416558c0189cda2db6","unresolved":false,"context_lines":[{"line_number":18,"context_line":"  have capability to monitor whatever Ceilometer can support.Forcibly, these"},{"line_number":19,"context_line":"  resources have to be modelized in the monitoring policy of TOSCA template. For"},{"line_number":20,"context_line":"  example, the alarm-based monitoring driver could monitor both VNF resources"},{"line_number":21,"context_line":"  and network resources."},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"* automatically it needs to be scaled out and vice-versa. This action is out of"},{"line_number":24,"context_line":"  scope in the spec. In fact, the alarm-based monitoring driver does not directly"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_d2e0c7fc","line":21,"in_reply_to":"bab6814e_2647604c","updated":"2016-05-20 18:49:22.000000000","message":"Done","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"39fee8a1f0c933e76e19ccf3ab4252e9cce0737b","unresolved":false,"context_lines":[{"line_number":20,"context_line":"  example, the alarm-based monitoring driver could monitor both VNF resources"},{"line_number":21,"context_line":"  and network resources."},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"* automatically it needs to be scaled out and vice-versa. This action is out of"},{"line_number":24,"context_line":"  scope in the spec. In fact, the alarm-based monitoring driver does not directly"},{"line_number":25,"context_line":"  support auto-scaling. However, it totally could be considered as an important"},{"line_number":26,"context_line":"  addition to auto-scaling. Accordingly, a user of NFV can change parameters in"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_265120d9","line":23,"updated":"2016-05-20 09:38:57.000000000","message":"as you have mentioned, its not part of this spec and instead, you could define the problem something below:\n\nWhen CPU threshold reaches the bounndry limit, alarm-based-monitor driver should be able to trigger the scaling of deployed VNF. ( in the other spec, i have cpatured the actions for scaling, so proably could mentioned in below section while you define the solution for this problem)","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"cb25daeafc3c9688797c61416558c0189cda2db6","unresolved":false,"context_lines":[{"line_number":20,"context_line":"  example, the alarm-based monitoring driver could monitor both VNF resources"},{"line_number":21,"context_line":"  and network resources."},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"* automatically it needs to be scaled out and vice-versa. This action is out of"},{"line_number":24,"context_line":"  scope in the spec. In fact, the alarm-based monitoring driver does not directly"},{"line_number":25,"context_line":"  support auto-scaling. However, it totally could be considered as an important"},{"line_number":26,"context_line":"  addition to auto-scaling. Accordingly, a user of NFV can change parameters in"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_b2a383b1","line":23,"in_reply_to":"bab6814e_265120d9","updated":"2016-05-20 18:49:22.000000000","message":"Done","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"39fee8a1f0c933e76e19ccf3ab4252e9cce0737b","unresolved":false,"context_lines":[{"line_number":36,"context_line":"cannot work well. In order to detect hardware failure, alarm"},{"line_number":37,"context_line":"configuration related to CPU usage and memory usage could be created by Heat"},{"line_number":38,"context_line":"in terms of Heat auto-scaling. However, a user of NFV could hardly change"},{"line_number":39,"context_line":"alarm parameters like threshold, period and actions."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Proposed change"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_26eda0ef","line":39,"updated":"2016-05-20 09:38:57.000000000","message":"same here, kindly move the solution part described here to below section","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"cb25daeafc3c9688797c61416558c0189cda2db6","unresolved":false,"context_lines":[{"line_number":36,"context_line":"cannot work well. In order to detect hardware failure, alarm"},{"line_number":37,"context_line":"configuration related to CPU usage and memory usage could be created by Heat"},{"line_number":38,"context_line":"in terms of Heat auto-scaling. However, a user of NFV could hardly change"},{"line_number":39,"context_line":"alarm parameters like threshold, period and actions."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Proposed change"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_12952f3e","line":39,"in_reply_to":"bab6814e_26eda0ef","updated":"2016-05-20 18:49:22.000000000","message":"Done","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"a788583db4a5e28655ccfecadc2d23862c011ecd","unresolved":false,"context_lines":[{"line_number":42,"context_line":"Proposed change"},{"line_number":43,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"OpenStack ceilometer provides the monitoring feature to monitor a given"},{"line_number":46,"context_line":"OpenStack element or set of elements and same could be used to monitor VNF resources."},{"line_number":47,"context_line":"There are two options available to consume this feature in tacker as below:"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"1. Use heat celilometer resource type: In this approach, tacker will create"},{"line_number":50,"context_line":"OS::Ceilometer::Alarm resource by making use of either the same template"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_e7f1ebce","line":47,"range":{"start_line":45,"start_character":0,"end_line":47,"end_character":75},"updated":"2016-05-25 18:28:40.000000000","message":"Similar comment as in auto-scaling spec [1]. So far, tacker monitoring framework always involves polling external things at regular interval. That\u0027s how ping, http-ping and custom monitoring drivers are expected. \n\nNow,IMO, the single biggest thing to be delivered in this spec is a Tacker component that can listen to *external* events / alarms and do some local workflow actions like log, respawn, scale-out, scale-in. This needs to be described without going directly into Ceilometer details.\n\nWhat do you think ?\n\n[1] https://review.openstack.org/#/c/318577/1/specs/newton/manual-and-auto-scaling.rst@21","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"56071edad4929208aabf3f1c70a15a43c7dc062b","unresolved":false,"context_lines":[{"line_number":42,"context_line":"Proposed change"},{"line_number":43,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"OpenStack ceilometer provides the monitoring feature to monitor a given"},{"line_number":46,"context_line":"OpenStack element or set of elements and same could be used to monitor VNF resources."},{"line_number":47,"context_line":"There are two options available to consume this feature in tacker as below:"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"1. Use heat celilometer resource type: In this approach, tacker will create"},{"line_number":50,"context_line":"OS::Ceilometer::Alarm resource by making use of either the same template"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_983c7de2","line":47,"range":{"start_line":45,"start_character":0,"end_line":47,"end_character":75},"in_reply_to":"bab6814e_5b9d1d65","updated":"2016-05-26 21:03:39.000000000","message":"@Tung - totally, we can just talk in abstract. We need real implementation and Ceilometer is the way to go for this first iteration.\n\nPerhaps we need a bit more low-level design captured in this spec. We also need to come up w/ some new component name for this alarm-listener and see how it slides into existing monitoring framework already in place at [1]. I drew something quick here [2] to orient ourselves. How does it look ?\n\n\n[1] http://git.openstack.org/cgit/openstack/tacker/tree/tacker/vm/monitor.py#n44\n[2] http://paste.openstack.org/show/505741/","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"1dedf11df37fc1ec2f8fa585f7c851a749c8973c","unresolved":false,"context_lines":[{"line_number":42,"context_line":"Proposed change"},{"line_number":43,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"OpenStack ceilometer provides the monitoring feature to monitor a given"},{"line_number":46,"context_line":"OpenStack element or set of elements and same could be used to monitor VNF resources."},{"line_number":47,"context_line":"There are two options available to consume this feature in tacker as below:"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"1. Use heat celilometer resource type: In this approach, tacker will create"},{"line_number":50,"context_line":"OS::Ceilometer::Alarm resource by making use of either the same template"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_5b9d1d65","line":47,"range":{"start_line":45,"start_character":0,"end_line":47,"end_character":75},"in_reply_to":"bab6814e_713807a1","updated":"2016-05-26 06:58:44.000000000","message":"+1 Agree. My thinking is that using Ceilometer is a way to go in the real implementation.","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"56071edad4929208aabf3f1c70a15a43c7dc062b","unresolved":false,"context_lines":[{"line_number":42,"context_line":"Proposed change"},{"line_number":43,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"OpenStack ceilometer provides the monitoring feature to monitor a given"},{"line_number":46,"context_line":"OpenStack element or set of elements and same could be used to monitor VNF resources."},{"line_number":47,"context_line":"There are two options available to consume this feature in tacker as below:"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"1. Use heat celilometer resource type: In this approach, tacker will create"},{"line_number":50,"context_line":"OS::Ceilometer::Alarm resource by making use of either the same template"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_385471c8","line":47,"range":{"start_line":45,"start_character":0,"end_line":47,"end_character":75},"in_reply_to":"bab6814e_713807a1","updated":"2016-05-26 21:03:39.000000000","message":"@Qiming - exactly!","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"425d7ee8ae98cfe31864288cdffe9e66abd06588","unresolved":false,"context_lines":[{"line_number":42,"context_line":"Proposed change"},{"line_number":43,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"OpenStack ceilometer provides the monitoring feature to monitor a given"},{"line_number":46,"context_line":"OpenStack element or set of elements and same could be used to monitor VNF resources."},{"line_number":47,"context_line":"There are two options available to consume this feature in tacker as below:"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"1. Use heat celilometer resource type: In this approach, tacker will create"},{"line_number":50,"context_line":"OS::Ceilometer::Alarm resource by making use of either the same template"}],"source_content_type":"text/x-rst","patch_set":8,"id":"9abb7d3a_a0572401","line":47,"range":{"start_line":45,"start_character":0,"end_line":47,"end_character":75},"in_reply_to":"bab6814e_983c7de2","updated":"2016-05-27 19:47:59.000000000","message":"Ouch, a typo .. I meant to say,\n\n\"@Tung - totally, we *cannot* just talk in abstract. We need real implementation ...\"","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":8246,"name":"Qiming Teng","email":"tengqm@outlook.com","username":"tengqm"},"change_message_id":"ca9aa685ee212cd08c7b87493af8b957379c4132","unresolved":false,"context_lines":[{"line_number":42,"context_line":"Proposed change"},{"line_number":43,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"OpenStack ceilometer provides the monitoring feature to monitor a given"},{"line_number":46,"context_line":"OpenStack element or set of elements and same could be used to monitor VNF resources."},{"line_number":47,"context_line":"There are two options available to consume this feature in tacker as below:"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"1. Use heat celilometer resource type: In this approach, tacker will create"},{"line_number":50,"context_line":"OS::Ceilometer::Alarm resource by making use of either the same template"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_713807a1","line":47,"range":{"start_line":45,"start_character":0,"end_line":47,"end_character":75},"in_reply_to":"bab6814e_e7f1ebce","updated":"2016-05-26 03:19:21.000000000","message":"sounds the right thing to do. maybe Tacker can start building a basic workflow to make things just work. while doing this, the interfaces should be generalized and publicized so that users can customize it easily.","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"39fee8a1f0c933e76e19ccf3ab4252e9cce0737b","unresolved":false,"context_lines":[{"line_number":50,"context_line":"OS::Ceilometer::Alarm resource by making use of either the same template"},{"line_number":51,"context_line":"used for scale-group or seprate template, which gives the option to enable or"},{"line_number":52,"context_line":"disable the monitoring for a given scalegroup easily also it helps to separate"},{"line_number":53,"context_line":"the concern on on-boarding vs monitoring.  It can be made as"},{"line_number":54,"context_line":"configurable parameter in tacker.conf."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"create an ceilometer resource as below with required alarm criteria:"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_067fbc15","line":53,"updated":"2016-05-20 09:38:57.000000000","message":"it needs to be decided and if we plan to go with this approach, its better to mention about the new configuration parameter here. while i was writing the previous patch, it was my intention :)","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"cb25daeafc3c9688797c61416558c0189cda2db6","unresolved":false,"context_lines":[{"line_number":50,"context_line":"OS::Ceilometer::Alarm resource by making use of either the same template"},{"line_number":51,"context_line":"used for scale-group or seprate template, which gives the option to enable or"},{"line_number":52,"context_line":"disable the monitoring for a given scalegroup easily also it helps to separate"},{"line_number":53,"context_line":"the concern on on-boarding vs monitoring.  It can be made as"},{"line_number":54,"context_line":"configurable parameter in tacker.conf."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"create an ceilometer resource as below with required alarm criteria:"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_117b588d","line":53,"in_reply_to":"bab6814e_067fbc15","updated":"2016-05-20 18:49:22.000000000","message":"Ok.. I just did not pay attention this. :)\nIt will be fixed in the next patchset. Thanks","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"39fee8a1f0c933e76e19ccf3ab4252e9cce0737b","unresolved":false,"context_lines":[{"line_number":82,"context_line":"          comparison_operator: lt"},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"NOTE:"},{"line_number":85,"context_line":"* add alarm_actions to both of these alarm with either signal_url provided by"},{"line_number":86,"context_line":"heat or tacker monitoring websocket created per scaling VDU. In early case,"},{"line_number":87,"context_line":"heat will do scaling automatically, without the knowledge of tacker, which is"},{"line_number":88,"context_line":"not appropriate, so later case would be the right choice."}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_e6c9d85a","line":85,"updated":"2016-05-20 09:38:57.000000000","message":"using heat singal url needs to be decided, this is one of the fact discussed in last meeting.","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":8246,"name":"Qiming Teng","email":"tengqm@outlook.com","username":"tengqm"},"change_message_id":"c16317d26f42faa6682b7034166864b079f29f1a","unresolved":false,"context_lines":[{"line_number":82,"context_line":"          comparison_operator: lt"},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"NOTE:"},{"line_number":85,"context_line":"* add alarm_actions to both of these alarm with either signal_url provided by"},{"line_number":86,"context_line":"heat or tacker monitoring websocket created per scaling VDU. In early case,"},{"line_number":87,"context_line":"heat will do scaling automatically, without the knowledge of tacker, which is"},{"line_number":88,"context_line":"not appropriate, so later case would be the right choice."}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_32d4b3ea","line":85,"in_reply_to":"bab6814e_472edea5","updated":"2016-05-20 11:58:41.000000000","message":"if you are sending a POST to the alarm URL, that is fine, because the URL has been manipulated with some signing credentials. however, if you are doing signal, you got to tell heat who you are so heat can authenticate your request. there has been a long debate between heat and ceilometer on this. I\u0027m not sure that has been solved. Another factor you may want to consider is that a POST request send to the alarm url doesn\u0027t allow you to specify any body. I believe you will realize how useful/useless that is.","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"cb000cb7e02ba40face11ceba8902636e3e22caf","unresolved":false,"context_lines":[{"line_number":82,"context_line":"          comparison_operator: lt"},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"NOTE:"},{"line_number":85,"context_line":"* add alarm_actions to both of these alarm with either signal_url provided by"},{"line_number":86,"context_line":"heat or tacker monitoring websocket created per scaling VDU. In early case,"},{"line_number":87,"context_line":"heat will do scaling automatically, without the knowledge of tacker, which is"},{"line_number":88,"context_line":"not appropriate, so later case would be the right choice."}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_472edea5","line":85,"in_reply_to":"bab6814e_ccfcb574","updated":"2016-05-20 10:37:05.000000000","message":"via tacker VIM. and VIM is the owner of the scaling stack created in heat and it should not be an issue on signaling","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":8246,"name":"Qiming Teng","email":"tengqm@outlook.com","username":"tengqm"},"change_message_id":"9bb343af4549ab75e673e15162af53dfe3047484","unresolved":false,"context_lines":[{"line_number":82,"context_line":"          comparison_operator: lt"},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"NOTE:"},{"line_number":85,"context_line":"* add alarm_actions to both of these alarm with either signal_url provided by"},{"line_number":86,"context_line":"heat or tacker monitoring websocket created per scaling VDU. In early case,"},{"line_number":87,"context_line":"heat will do scaling automatically, without the knowledge of tacker, which is"},{"line_number":88,"context_line":"not appropriate, so later case would be the right choice."}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_ccfcb574","line":85,"in_reply_to":"bab6814e_e6c9d85a","updated":"2016-05-20 10:12:33.000000000","message":"how would you authenticate to heat if you are invoking the signal APIs directly?","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"a788583db4a5e28655ccfecadc2d23862c011ecd","unresolved":false,"context_lines":[{"line_number":83,"context_line":""},{"line_number":84,"context_line":"NOTE:"},{"line_number":85,"context_line":"* add alarm_actions to both of these alarm with either signal_url provided by"},{"line_number":86,"context_line":"heat or tacker monitoring websocket created per scaling VDU. In early case,"},{"line_number":87,"context_line":"heat will do scaling automatically, without the knowledge of tacker, which is"},{"line_number":88,"context_line":"not appropriate, so later case would be the right choice."},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"Pros: We can leverage Heat resources. The short-term goal is to support for"},{"line_number":91,"context_line":"auto-scaling using Heat auto-scaling."}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_a741a33b","line":88,"range":{"start_line":86,"start_character":61,"end_line":88,"end_character":57},"updated":"2016-05-25 18:28:40.000000000","message":"Agree. We have clearly heard from NFV operators that their scaling operators involve some custom steps and it is better to keep Tacker in the loop for any scale-workflow needs. \n\nHeat\u0027s set-and-forget autoscaling might work okay for some workloads like load-balancer (LBaaS) but NFV needs are a bit eclectic.","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"39fee8a1f0c933e76e19ccf3ab4252e9cce0737b","unresolved":false,"context_lines":[{"line_number":134,"context_line":"When alarms are triggered directly by Ceilometer, it is flexible and easy"},{"line_number":135,"context_line":"to control in Tacker."},{"line_number":136,"context_line":"In the view of user, a user of NFV totally can use Ceilometer alarms to"},{"line_number":137,"context_line":"perform custom actions without heat dependency."},{"line_number":138,"context_line":"In the view of operator, multiple policies can be used for VDU. It implies"},{"line_number":139,"context_line":"that different actions can be applied for each VDU. Meanwhile, putting so"},{"line_number":140,"context_line":"many policies makes HOT template complicated. In addition, it is"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_a6d4f0bc","line":137,"updated":"2016-05-20 09:38:57.000000000","message":"strongly disagree here. Whether we create alarm via heat or directly, ceilometer is the one going to trigger the given action and user does not get control.","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"cb000cb7e02ba40face11ceba8902636e3e22caf","unresolved":false,"context_lines":[{"line_number":134,"context_line":"When alarms are triggered directly by Ceilometer, it is flexible and easy"},{"line_number":135,"context_line":"to control in Tacker."},{"line_number":136,"context_line":"In the view of user, a user of NFV totally can use Ceilometer alarms to"},{"line_number":137,"context_line":"perform custom actions without heat dependency."},{"line_number":138,"context_line":"In the view of operator, multiple policies can be used for VDU. It implies"},{"line_number":139,"context_line":"that different actions can be applied for each VDU. Meanwhile, putting so"},{"line_number":140,"context_line":"many policies makes HOT template complicated. In addition, it is"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_39e01e29","line":137,"in_reply_to":"bab6814e_2ce1019b","updated":"2016-05-20 10:37:05.000000000","message":"ceilometer does provide all sort of monitoring like cpu and memory usage ofcourse the aodh.","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":8246,"name":"Qiming Teng","email":"tengqm@outlook.com","username":"tengqm"},"change_message_id":"c16317d26f42faa6682b7034166864b079f29f1a","unresolved":false,"context_lines":[{"line_number":134,"context_line":"When alarms are triggered directly by Ceilometer, it is flexible and easy"},{"line_number":135,"context_line":"to control in Tacker."},{"line_number":136,"context_line":"In the view of user, a user of NFV totally can use Ceilometer alarms to"},{"line_number":137,"context_line":"perform custom actions without heat dependency."},{"line_number":138,"context_line":"In the view of operator, multiple policies can be used for VDU. It implies"},{"line_number":139,"context_line":"that different actions can be applied for each VDU. Meanwhile, putting so"},{"line_number":140,"context_line":"many policies makes HOT template complicated. In addition, it is"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_12db6fed","line":137,"in_reply_to":"bab6814e_39e01e29","updated":"2016-05-20 11:58:41.000000000","message":"there has been an issue with cpu utilization metric (which was not a ceilometer bug) -- when CPU over-commit happens, there is no way to get an accurate number for it.\n\nas for memory utilization, a guest kernel usually claims all memory for file/page caches upon startup. from outside a VM, you will never get a usable number for that, unless you install some balloon drivers into the guest.\n\nit could be that my knowledge need to be refreshed, but anyway, these are just some reminders.","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":8246,"name":"Qiming Teng","email":"tengqm@outlook.com","username":"tengqm"},"change_message_id":"9bb343af4549ab75e673e15162af53dfe3047484","unresolved":false,"context_lines":[{"line_number":134,"context_line":"When alarms are triggered directly by Ceilometer, it is flexible and easy"},{"line_number":135,"context_line":"to control in Tacker."},{"line_number":136,"context_line":"In the view of user, a user of NFV totally can use Ceilometer alarms to"},{"line_number":137,"context_line":"perform custom actions without heat dependency."},{"line_number":138,"context_line":"In the view of operator, multiple policies can be used for VDU. It implies"},{"line_number":139,"context_line":"that different actions can be applied for each VDU. Meanwhile, putting so"},{"line_number":140,"context_line":"many policies makes HOT template complicated. In addition, it is"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_2ce1019b","line":137,"in_reply_to":"bab6814e_a6d4f0bc","updated":"2016-05-20 10:12:33.000000000","message":"em ... maybe we should take a step back here. Does it really make sense to have the infrastructure to scale VDUs? How much useful information can ceilometer get for a VDU? Can it get an accurate number of CPU utilization at all? Can it get an good assumption of memory usage?","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"39fee8a1f0c933e76e19ccf3ab4252e9cce0737b","unresolved":false,"context_lines":[{"line_number":140,"context_line":"many policies makes HOT template complicated. In addition, it is"},{"line_number":141,"context_line":"inconvenient to change monitoring policies in HOT as well."},{"line_number":142,"context_line":"Please note that using directly Ceilometer is an ideal solution which can"},{"line_number":143,"context_line":"adapt to any changes in Tacker in the future."},{"line_number":144,"context_line":"Cons: To auto-scale VNFs using heat auto-scaling, using directly Ceilometer"},{"line_number":145,"context_line":"can show little redundancy."},{"line_number":146,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_c610145c","line":143,"updated":"2016-05-20 09:38:57.000000000","message":"Heat does support all kind of alarms supported by ceilometer and as tacker does make use of heat for all kind of orchestration, its better to go with heat for handling the monitoring. Main reason is, it reduces the many dependencies on the projects, tomorrow if we need load-balancer, no need to depends on the neutron lbass, instead, make use of heat to do as heat already has integration with all official openstack projects and it was one of the intention of heat to orchestrate. so i would suggest to leverage it to get the advantage.","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"cb000cb7e02ba40face11ceba8902636e3e22caf","unresolved":false,"context_lines":[{"line_number":140,"context_line":"many policies makes HOT template complicated. In addition, it is"},{"line_number":141,"context_line":"inconvenient to change monitoring policies in HOT as well."},{"line_number":142,"context_line":"Please note that using directly Ceilometer is an ideal solution which can"},{"line_number":143,"context_line":"adapt to any changes in Tacker in the future."},{"line_number":144,"context_line":"Cons: To auto-scale VNFs using heat auto-scaling, using directly Ceilometer"},{"line_number":145,"context_line":"can show little redundancy."},{"line_number":146,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_d9a8f2dd","line":143,"in_reply_to":"bab6814e_0c7a3dbd","updated":"2016-05-20 10:37:05.000000000","message":"can you please elloborate on ops. support issue in heat?","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":8246,"name":"Qiming Teng","email":"tengqm@outlook.com","username":"tengqm"},"change_message_id":"9bb343af4549ab75e673e15162af53dfe3047484","unresolved":false,"context_lines":[{"line_number":140,"context_line":"many policies makes HOT template complicated. In addition, it is"},{"line_number":141,"context_line":"inconvenient to change monitoring policies in HOT as well."},{"line_number":142,"context_line":"Please note that using directly Ceilometer is an ideal solution which can"},{"line_number":143,"context_line":"adapt to any changes in Tacker in the future."},{"line_number":144,"context_line":"Cons: To auto-scale VNFs using heat auto-scaling, using directly Ceilometer"},{"line_number":145,"context_line":"can show little redundancy."},{"line_number":146,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_0c7a3dbd","line":143,"in_reply_to":"bab6814e_c610145c","updated":"2016-05-20 10:12:33.000000000","message":"well ... I have been telling users some different stories, time and again. It is good to use Heat for deploying a composite application because it does integrate a lot of resource types. However, Heat\u0027s weakness is about operation support and Heat is not designed to do operation support.","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":8246,"name":"Qiming Teng","email":"tengqm@outlook.com","username":"tengqm"},"change_message_id":"c16317d26f42faa6682b7034166864b079f29f1a","unresolved":false,"context_lines":[{"line_number":140,"context_line":"many policies makes HOT template complicated. In addition, it is"},{"line_number":141,"context_line":"inconvenient to change monitoring policies in HOT as well."},{"line_number":142,"context_line":"Please note that using directly Ceilometer is an ideal solution which can"},{"line_number":143,"context_line":"adapt to any changes in Tacker in the future."},{"line_number":144,"context_line":"Cons: To auto-scale VNFs using heat auto-scaling, using directly Ceilometer"},{"line_number":145,"context_line":"can show little redundancy."},{"line_number":146,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_d2b9e77a","line":143,"in_reply_to":"bab6814e_d9a8f2dd","updated":"2016-05-20 11:58:41.000000000","message":"it is not heat\u0027s fault, it is just that heat was not designed to be a operation tool. when you are really managing a group of VMs and the only verb you can use to operate that group is \u0027stack-update\u0027, you will understand what I mean.","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"a788583db4a5e28655ccfecadc2d23862c011ecd","unresolved":false,"context_lines":[{"line_number":216,"context_line":"#. Enahnce the horizon to show the live monitoring parameters."},{"line_number":217,"context_line":"#. create a sample TOSCA template with below details"},{"line_number":218,"context_line":""},{"line_number":219,"context_line":".. code-block:: ini"},{"line_number":220,"context_line":""},{"line_number":221,"context_line":" tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0"},{"line_number":222,"context_line":""},{"line_number":223,"context_line":" description: Demo example with alarm-based monitoring"},{"line_number":224,"context_line":""},{"line_number":225,"context_line":" metadata:"},{"line_number":226,"context_line":"  template_name: sample-tosca-vnfd-hcpu-monitor.yaml"},{"line_number":227,"context_line":""},{"line_number":228,"context_line":" topology_template:"},{"line_number":229,"context_line":"  node_templates:"},{"line_number":230,"context_line":"    VDU1:"},{"line_number":231,"context_line":"      type: tosca.nodes.nfv.VDU.Tacker"},{"line_number":232,"context_line":""},{"line_number":233,"context_line":"      properties:"},{"line_number":234,"context_line":"        image: cirros-0.3.4-x86_64-uec"},{"line_number":235,"context_line":"        flavor: m1.tiny"},{"line_number":236,"context_line":"        availability_zone: nova"},{"line_number":237,"context_line":"        mgmt_driver: noop"},{"line_number":238,"context_line":"        config: |"},{"line_number":239,"context_line":"          param0: key1"},{"line_number":240,"context_line":"          param1: key2"},{"line_number":241,"context_line":"        monitoring_policy:"},{"line_number":242,"context_line":"          name: cpu_util"},{"line_number":243,"context_line":"          parameters:"},{"line_number":244,"context_line":"            statistic: avg"},{"line_number":245,"context_line":"            period: \"60\""},{"line_number":246,"context_line":"            evaluation_periods: \"1\""},{"line_number":247,"context_line":"            threshold: \"70\""},{"line_number":248,"context_line":"          actions:"},{"line_number":249,"context_line":"            failure: log"},{"line_number":250,"context_line":""},{"line_number":251,"context_line":""},{"line_number":252,"context_line":"Dependencies"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_e79f2b5d","line":249,"range":{"start_line":219,"start_character":0,"end_line":249,"end_character":24},"updated":"2016-05-25 18:28:40.000000000","message":"I think this whole section needs to be brought to the front of this spec, say around L44.","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"1dedf11df37fc1ec2f8fa585f7c851a749c8973c","unresolved":false,"context_lines":[{"line_number":216,"context_line":"#. Enahnce the horizon to show the live monitoring parameters."},{"line_number":217,"context_line":"#. create a sample TOSCA template with below details"},{"line_number":218,"context_line":""},{"line_number":219,"context_line":".. code-block:: ini"},{"line_number":220,"context_line":""},{"line_number":221,"context_line":" tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0"},{"line_number":222,"context_line":""},{"line_number":223,"context_line":" description: Demo example with alarm-based monitoring"},{"line_number":224,"context_line":""},{"line_number":225,"context_line":" metadata:"},{"line_number":226,"context_line":"  template_name: sample-tosca-vnfd-hcpu-monitor.yaml"},{"line_number":227,"context_line":""},{"line_number":228,"context_line":" topology_template:"},{"line_number":229,"context_line":"  node_templates:"},{"line_number":230,"context_line":"    VDU1:"},{"line_number":231,"context_line":"      type: tosca.nodes.nfv.VDU.Tacker"},{"line_number":232,"context_line":""},{"line_number":233,"context_line":"      properties:"},{"line_number":234,"context_line":"        image: cirros-0.3.4-x86_64-uec"},{"line_number":235,"context_line":"        flavor: m1.tiny"},{"line_number":236,"context_line":"        availability_zone: nova"},{"line_number":237,"context_line":"        mgmt_driver: noop"},{"line_number":238,"context_line":"        config: |"},{"line_number":239,"context_line":"          param0: key1"},{"line_number":240,"context_line":"          param1: key2"},{"line_number":241,"context_line":"        monitoring_policy:"},{"line_number":242,"context_line":"          name: cpu_util"},{"line_number":243,"context_line":"          parameters:"},{"line_number":244,"context_line":"            statistic: avg"},{"line_number":245,"context_line":"            period: \"60\""},{"line_number":246,"context_line":"            evaluation_periods: \"1\""},{"line_number":247,"context_line":"            threshold: \"70\""},{"line_number":248,"context_line":"          actions:"},{"line_number":249,"context_line":"            failure: log"},{"line_number":250,"context_line":""},{"line_number":251,"context_line":""},{"line_number":252,"context_line":"Dependencies"}],"source_content_type":"text/x-rst","patch_set":8,"id":"bab6814e_fbdcd8e5","line":249,"range":{"start_line":219,"start_character":0,"end_line":249,"end_character":24},"in_reply_to":"bab6814e_e79f2b5d","updated":"2016-05-26 06:58:44.000000000","message":"Done","commit_id":"c6177720f5e0f1bea7d13a5862b446335daf0277"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"a0c9ee790fb134c080253eaa46ac9271b901f354","unresolved":false,"context_lines":[{"line_number":56,"context_line":"            |      | alarm-framework \u003c-----+    |"},{"line_number":57,"context_line":"            |      |                 +---+ |    |"},{"line_number":58,"context_line":"            |      +-+-^-------+-^---+   | |    |"},{"line_number":59,"context_line":"            |        | |       | |       | |    |"},{"line_number":60,"context_line":"            | +------v-++  +---v-+-+  +--v-+-+  |"},{"line_number":61,"context_line":"            | |         |  |       |  |      |  |"},{"line_number":62,"context_line":"            | |         |  |       |  |      |  |"}],"source_content_type":"text/x-rst","patch_set":9,"id":"7aa08908_84ee8fea","line":59,"range":{"start_line":59,"start_character":16,"end_line":59,"end_character":48},"updated":"2016-06-04 20:42:48.000000000","message":"@Sridhar,\nLet\u0027s consider the interface between alarm-framework and low-level designs (Ceilometer, Monasca, or even custom driver). I agree that leveraging Heat resource to get Ceilometer (Monasca) alarms/events brings benefits so that we can go in the first iteration. But it is not what this framework describes. My concern is about custom driver. In the future, it really makes sense to welcome any custom driver if possible. I just wonder whether it will still make sense to leverage Heat resources.\nThanks","commit_id":"8441d46c3e1f4a569bd34bb409b8444555c03dbe"},{"author":{"_account_id":16511,"name":"Bob Haddleton","email":"bob.haddleton@nokia.com","username":"bobh"},"change_message_id":"96898909511164001cea393875f01173d7e373a6","unresolved":false,"context_lines":[{"line_number":94,"context_line":"          param0: key1"},{"line_number":95,"context_line":"          param1: key2"},{"line_number":96,"context_line":"        monitoring_policy:"},{"line_number":97,"context_line":"          driver: ceilometer, monasca, custom driver"},{"line_number":98,"context_line":"          name: cpu_util"},{"line_number":99,"context_line":"          parameters:"},{"line_number":100,"context_line":"            statistic: avg"}],"source_content_type":"text/x-rst","patch_set":9,"id":"7aa08908_57bbc60e","line":97,"updated":"2016-06-04 03:54:52.000000000","message":"Are these options available to specify?  I assume this would only be a single driver per policy.  It might be better to put the options in a comment and only pick one for the driver","commit_id":"8441d46c3e1f4a569bd34bb409b8444555c03dbe"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"7391b54429200054eaeda0f638f5e8aa920c3eb8","unresolved":false,"context_lines":[{"line_number":94,"context_line":"          param0: key1"},{"line_number":95,"context_line":"          param1: key2"},{"line_number":96,"context_line":"        monitoring_policy:"},{"line_number":97,"context_line":"          driver: ceilometer, monasca, custom driver"},{"line_number":98,"context_line":"          name: cpu_util"},{"line_number":99,"context_line":"          parameters:"},{"line_number":100,"context_line":"            statistic: avg"}],"source_content_type":"text/x-rst","patch_set":9,"id":"7aa08908_ce2a78e7","line":97,"in_reply_to":"7aa08908_57bbc60e","updated":"2016-06-04 17:22:33.000000000","message":"Done","commit_id":"8441d46c3e1f4a569bd34bb409b8444555c03dbe"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"34155c2b4055c129d3523fe9a5cfb9462d602f27","unresolved":false,"context_lines":[{"line_number":93,"context_line":"        config: |"},{"line_number":94,"context_line":"          param0: key1"},{"line_number":95,"context_line":"          param1: key2"},{"line_number":96,"context_line":"        monitoring_policy:"},{"line_number":97,"context_line":"          driver: ceilometer, monasca, custom driver"},{"line_number":98,"context_line":"          name: cpu_util"},{"line_number":99,"context_line":"          parameters:"},{"line_number":100,"context_line":"            statistic: avg"},{"line_number":101,"context_line":"            period: \"60\""},{"line_number":102,"context_line":"            evaluation_periods: \"1\""},{"line_number":103,"context_line":"            threshold: \"70\""},{"line_number":104,"context_line":"          actions:"},{"line_number":105,"context_line":"            failure: log"},{"line_number":106,"context_line":""},{"line_number":107,"context_line":""},{"line_number":108,"context_line":"There are two ways to enforce the monitoring policy. In case of OpenStack Ceilometer,"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9abb7d3a_3c622ad9","line":105,"range":{"start_line":96,"start_character":0,"end_line":105,"end_character":24},"updated":"2016-06-03 02:47:16.000000000","message":"We need to move away from monitoring policy embedded within VDU to something standalone. This is in-line with our transition to the new TOSCA node and policy type structure.\n\nPlease see the sample TOSCA node type for monitoring in  http://paste.openstack.org/show/507466/\n\nSpecifically L23-L37","commit_id":"8441d46c3e1f4a569bd34bb409b8444555c03dbe"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"eb7a2c775fdb76c1c45a91633679df975048c3e3","unresolved":false,"context_lines":[{"line_number":93,"context_line":"        config: |"},{"line_number":94,"context_line":"          param0: key1"},{"line_number":95,"context_line":"          param1: key2"},{"line_number":96,"context_line":"        monitoring_policy:"},{"line_number":97,"context_line":"          driver: ceilometer, monasca, custom driver"},{"line_number":98,"context_line":"          name: cpu_util"},{"line_number":99,"context_line":"          parameters:"},{"line_number":100,"context_line":"            statistic: avg"},{"line_number":101,"context_line":"            period: \"60\""},{"line_number":102,"context_line":"            evaluation_periods: \"1\""},{"line_number":103,"context_line":"            threshold: \"70\""},{"line_number":104,"context_line":"          actions:"},{"line_number":105,"context_line":"            failure: log"},{"line_number":106,"context_line":""},{"line_number":107,"context_line":""},{"line_number":108,"context_line":"There are two ways to enforce the monitoring policy. In case of OpenStack Ceilometer,"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9abb7d3a_4a911b9a","line":105,"range":{"start_line":96,"start_character":0,"end_line":105,"end_character":24},"in_reply_to":"9abb7d3a_3c622ad9","updated":"2016-06-03 06:04:51.000000000","message":"nice suggestion... It will be changed in the next patchset.\nThanks Sridhar!","commit_id":"8441d46c3e1f4a569bd34bb409b8444555c03dbe"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"e452824c965bd2c6a26eb9b438175cbe7f64065d","unresolved":false,"context_lines":[{"line_number":93,"context_line":"        config: |"},{"line_number":94,"context_line":"          param0: key1"},{"line_number":95,"context_line":"          param1: key2"},{"line_number":96,"context_line":"        monitoring_policy:"},{"line_number":97,"context_line":"          driver: ceilometer, monasca, custom driver"},{"line_number":98,"context_line":"          name: cpu_util"},{"line_number":99,"context_line":"          parameters:"},{"line_number":100,"context_line":"            statistic: avg"},{"line_number":101,"context_line":"            period: \"60\""},{"line_number":102,"context_line":"            evaluation_periods: \"1\""},{"line_number":103,"context_line":"            threshold: \"70\""},{"line_number":104,"context_line":"          actions:"},{"line_number":105,"context_line":"            failure: log"},{"line_number":106,"context_line":""},{"line_number":107,"context_line":""},{"line_number":108,"context_line":"There are two ways to enforce the monitoring policy. In case of OpenStack Ceilometer,"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9abb7d3a_8a714347","line":105,"range":{"start_line":96,"start_character":0,"end_line":105,"end_character":24},"in_reply_to":"9abb7d3a_4a911b9a","updated":"2016-06-03 06:14:47.000000000","message":"I still follow Kanagaraj\u0027s spec. Actually, I recognized this problem when we want to deploy multiple VDUs and apply scaling policy to them.","commit_id":"8441d46c3e1f4a569bd34bb409b8444555c03dbe"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"34155c2b4055c129d3523fe9a5cfb9462d602f27","unresolved":false,"context_lines":[{"line_number":146,"context_line":"heat will do scaling automatically, without the knowledge of tacker, which is"},{"line_number":147,"context_line":"not appropriate, so later case would be the right choice."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"Pros: We can leverage Heat resources. The short-term goal is to support for"},{"line_number":150,"context_line":"auto-scaling using Heat auto-scaling."},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"Cons: The flexibility of NFV user could be limited."}],"source_content_type":"text/x-rst","patch_set":9,"id":"9abb7d3a_3a1d0a67","line":149,"range":{"start_line":149,"start_character":6,"end_line":149,"end_character":36},"updated":"2016-06-03 02:47:16.000000000","message":"My vote would be for this option - to leverage Heat / HOT to define the necessary alarms to avoid direct API interaction with Ceilometer.","commit_id":"8441d46c3e1f4a569bd34bb409b8444555c03dbe"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"7391b54429200054eaeda0f638f5e8aa920c3eb8","unresolved":false,"context_lines":[{"line_number":146,"context_line":"heat will do scaling automatically, without the knowledge of tacker, which is"},{"line_number":147,"context_line":"not appropriate, so later case would be the right choice."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"Pros: We can leverage Heat resources. The short-term goal is to support for"},{"line_number":150,"context_line":"auto-scaling using Heat auto-scaling."},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"Cons: The flexibility of NFV user could be limited."}],"source_content_type":"text/x-rst","patch_set":9,"id":"7aa08908_c2d25234","line":149,"in_reply_to":"7aa08908_5700e6aa","updated":"2016-06-04 17:22:33.000000000","message":"Done","commit_id":"8441d46c3e1f4a569bd34bb409b8444555c03dbe"},{"author":{"_account_id":16511,"name":"Bob Haddleton","email":"bob.haddleton@nokia.com","username":"bobh"},"change_message_id":"96898909511164001cea393875f01173d7e373a6","unresolved":false,"context_lines":[{"line_number":146,"context_line":"heat will do scaling automatically, without the knowledge of tacker, which is"},{"line_number":147,"context_line":"not appropriate, so later case would be the right choice."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"Pros: We can leverage Heat resources. The short-term goal is to support for"},{"line_number":150,"context_line":"auto-scaling using Heat auto-scaling."},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"Cons: The flexibility of NFV user could be limited."}],"source_content_type":"text/x-rst","patch_set":9,"id":"7aa08908_5700e6aa","line":149,"in_reply_to":"9abb7d3a_3a1d0a67","updated":"2016-06-04 03:54:52.000000000","message":"I agree.  Start by taking advantage of existing functionality in Heat, and then later expand it as needed with additional functionality in Tacker","commit_id":"8441d46c3e1f4a569bd34bb409b8444555c03dbe"},{"author":{"_account_id":16511,"name":"Bob Haddleton","email":"bob.haddleton@nokia.com","username":"bobh"},"change_message_id":"96898909511164001cea393875f01173d7e373a6","unresolved":false,"context_lines":[{"line_number":237,"context_line":"   monitoring parameters"},{"line_number":238,"context_line":"#. create a new monitoring driver for alarm based monitoring with configurable"},{"line_number":239,"context_line":"   parameter to use either of the apporach mentioned above."},{"line_number":240,"context_line":"#. create an websocket/ equivalent REST API to make celilometer to signal it"},{"line_number":241,"context_line":"   on the event of alarm. Make this API with required RBAC. if this could be"},{"line_number":242,"context_line":"   achieved using the notification, then its better option than using REST api."},{"line_number":243,"context_line":"#. Enahnce the horizon to show the live monitoring parameters."}],"source_content_type":"text/x-rst","patch_set":9,"id":"7aa08908_d7e17600","line":240,"updated":"2016-06-04 03:54:52.000000000","message":"Is this needed if option (1) above is chosen so that Heat is signaled directly by Ceilometer?","commit_id":"8441d46c3e1f4a569bd34bb409b8444555c03dbe"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"7391b54429200054eaeda0f638f5e8aa920c3eb8","unresolved":false,"context_lines":[{"line_number":237,"context_line":"   monitoring parameters"},{"line_number":238,"context_line":"#. create a new monitoring driver for alarm based monitoring with configurable"},{"line_number":239,"context_line":"   parameter to use either of the apporach mentioned above."},{"line_number":240,"context_line":"#. create an websocket/ equivalent REST API to make celilometer to signal it"},{"line_number":241,"context_line":"   on the event of alarm. Make this API with required RBAC. if this could be"},{"line_number":242,"context_line":"   achieved using the notification, then its better option than using REST api."},{"line_number":243,"context_line":"#. Enahnce the horizon to show the live monitoring parameters."}],"source_content_type":"text/x-rst","patch_set":9,"id":"7aa08908_2ea05c90","line":240,"in_reply_to":"7aa08908_d7e17600","updated":"2016-06-04 17:22:33.000000000","message":"It will be removed.","commit_id":"8441d46c3e1f4a569bd34bb409b8444555c03dbe"},{"author":{"_account_id":16511,"name":"Bob Haddleton","email":"bob.haddleton@nokia.com","username":"bobh"},"change_message_id":"96898909511164001cea393875f01173d7e373a6","unresolved":false,"context_lines":[{"line_number":257,"context_line":"- Create vnf from the vnfd"},{"line_number":258,"context_line":"- Stress VM which VNF is running on. The purpose is to make CPU usage reach"},{"line_number":259,"context_line":"  threshold."},{"line_number":260,"context_line":"- Check CPU usage inside VNF."},{"line_number":261,"context_line":""},{"line_number":262,"context_line":""},{"line_number":263,"context_line":"Reference"}],"source_content_type":"text/x-rst","patch_set":9,"id":"7aa08908_57c58659","line":260,"updated":"2016-06-04 03:54:52.000000000","message":"What is supposed to happen when the CPU usage reaches the specified threshold?","commit_id":"8441d46c3e1f4a569bd34bb409b8444555c03dbe"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"7391b54429200054eaeda0f638f5e8aa920c3eb8","unresolved":false,"context_lines":[{"line_number":257,"context_line":"- Create vnf from the vnfd"},{"line_number":258,"context_line":"- Stress VM which VNF is running on. The purpose is to make CPU usage reach"},{"line_number":259,"context_line":"  threshold."},{"line_number":260,"context_line":"- Check CPU usage inside VNF."},{"line_number":261,"context_line":""},{"line_number":262,"context_line":""},{"line_number":263,"context_line":"Reference"}],"source_content_type":"text/x-rst","patch_set":9,"id":"7aa08908_6eaa6472","line":260,"in_reply_to":"7aa08908_57c58659","updated":"2016-06-04 17:22:33.000000000","message":"IMHO, this only makes sense when monitoring driver has autoscaling function. For log, this sentence should be replaced. I suggest that we should use CLI to show the VNF status. Something be like:\ntacker vnf-status [vnf-id]\nThis command will show alarm/events with the corresponding VNF.","commit_id":"8441d46c3e1f4a569bd34bb409b8444555c03dbe"},{"author":{"_account_id":18955,"name":"dharmendra","email":"dharmendra.kushwaha@gmail.com","username":"dharmendra"},"change_message_id":"78b4509229d5a480f6a386089e49f3229048c193","unresolved":false,"context_lines":[{"line_number":1,"context_line":""},{"line_number":2,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":3,"context_line":"Add alarm-based monitoring driver to Tacker"},{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":"https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"This spec describes an alarm-based monitoring driver in Tacker"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_2b5d3c79","line":4,"range":{"start_line":4,"start_character":43,"end_line":4,"end_character":46},"updated":"2016-06-08 10:55:15.000000000","message":"Redundant","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"56857e6ec7e72fab99d4357eabee554fc452b07a","unresolved":false,"context_lines":[{"line_number":1,"context_line":""},{"line_number":2,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":3,"context_line":"Add alarm-based monitoring driver to Tacker"},{"line_number":4,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":5,"context_line":"https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"This spec describes an alarm-based monitoring driver in Tacker"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_19508131","line":4,"range":{"start_line":4,"start_character":43,"end_line":4,"end_character":46},"in_reply_to":"7aa08908_2b5d3c79","updated":"2016-06-08 16:26:24.000000000","message":"Done","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":18955,"name":"dharmendra","email":"dharmendra.kushwaha@gmail.com","username":"dharmendra"},"change_message_id":"78b4509229d5a480f6a386089e49f3229048c193","unresolved":false,"context_lines":[{"line_number":9,"context_line":"Problem description"},{"line_number":10,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"ETSI MANO atchitecture describes to monitor the VNF to take appropriate action"},{"line_number":13,"context_line":"such as fault management, performance management. Monitoring became as"},{"line_number":14,"context_line":"important aspect in MANO architecture."},{"line_number":15,"context_line":"Currently, Tacker provides a very minimal support for check the liveliness"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_8b8b90c2","line":12,"range":{"start_line":12,"start_character":10,"end_line":12,"end_character":22},"updated":"2016-06-08 10:55:15.000000000","message":"atchitecture --\u003e architecture","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"56857e6ec7e72fab99d4357eabee554fc452b07a","unresolved":false,"context_lines":[{"line_number":9,"context_line":"Problem description"},{"line_number":10,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"ETSI MANO atchitecture describes to monitor the VNF to take appropriate action"},{"line_number":13,"context_line":"such as fault management, performance management. Monitoring became as"},{"line_number":14,"context_line":"important aspect in MANO architecture."},{"line_number":15,"context_line":"Currently, Tacker provides a very minimal support for check the liveliness"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_b9616d07","line":12,"range":{"start_line":12,"start_character":10,"end_line":12,"end_character":22},"in_reply_to":"7aa08908_8b8b90c2","updated":"2016-06-08 16:26:24.000000000","message":"Done","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":17952,"name":"Santosh Kodicherla","email":"ksantosh.cs@gmail.com","username":"santoshkumar"},"change_message_id":"5a4e7ae6767f3bfe2b4b3b984672c6510ebba964","unresolved":false,"context_lines":[{"line_number":14,"context_line":"important aspect in MANO architecture."},{"line_number":15,"context_line":"Currently, Tacker provides a very minimal support for check the liveliness"},{"line_number":16,"context_line":"of VNF elements by means of ping or curl which helps to recover the element"},{"line_number":17,"context_line":"in case element is not pinging. But Tacker does not support to monitor"},{"line_number":18,"context_line":"VNF elements CPU/memory usage. Further, it is necessary for Tacker to monitor all"},{"line_number":19,"context_line":"VNF resources as well. The reason is that the failure of VNFs happen too diversely."},{"line_number":20,"context_line":""}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_3bf4e3f0","line":17,"updated":"2016-06-06 18:25:01.000000000","message":"element is not pinging or reachable you mean...??","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"410a5ea9c57de62c54bfba51417caae467333c30","unresolved":false,"context_lines":[{"line_number":14,"context_line":"important aspect in MANO architecture."},{"line_number":15,"context_line":"Currently, Tacker provides a very minimal support for check the liveliness"},{"line_number":16,"context_line":"of VNF elements by means of ping or curl which helps to recover the element"},{"line_number":17,"context_line":"in case element is not pinging. But Tacker does not support to monitor"},{"line_number":18,"context_line":"VNF elements CPU/memory usage. Further, it is necessary for Tacker to monitor all"},{"line_number":19,"context_line":"VNF resources as well. The reason is that the failure of VNFs happen too diversely."},{"line_number":20,"context_line":""}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_c7602404","line":17,"in_reply_to":"7aa08908_3bf4e3f0","updated":"2016-06-07 15:44:32.000000000","message":"This means Tacker currently supports ping driver. By pinging, if element is unreachable, it will be respawned.","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":13485,"name":"Sripriya Seetharam","email":"sseetha@brocade.com","username":"Sripriya"},"change_message_id":"ffafff6ee0645e129e44628527cb2741adf7bb66","unresolved":false,"context_lines":[{"line_number":49,"context_line":"            |               |                   |"},{"line_number":50,"context_line":"            |      +--------v--------+          |"},{"line_number":51,"context_line":"            |      |                 |          |"},{"line_number":52,"context_line":"            |      | alarm-framework \u003c-----+    |"},{"line_number":53,"context_line":"            |      |                 +---+ |    |"},{"line_number":54,"context_line":"            |      +-+-^-------+-^---+   | |    |"},{"line_number":55,"context_line":"            |        | |       | |       | |    |"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_8949b133","line":52,"range":{"start_line":52,"start_character":21,"end_line":52,"end_character":36},"updated":"2016-06-08 21:50:26.000000000","message":"are you creating a new plugin for alarm based drivers?can you clarify what would be the scope of the framework? is there a plugin-driver framework involved for alarms? if yes, please specify what would be the role of the plugin?\n\n\nExample: plugin could handle callbacks via web hooks and invoke backends appropriately to post process the events in custom drivers.","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"6b9504283e4abb307032bcfd638743528169f37f","unresolved":false,"context_lines":[{"line_number":49,"context_line":"            |               |                   |"},{"line_number":50,"context_line":"            |      +--------v--------+          |"},{"line_number":51,"context_line":"            |      |                 |          |"},{"line_number":52,"context_line":"            |      | alarm-framework \u003c-----+    |"},{"line_number":53,"context_line":"            |      |                 +---+ |    |"},{"line_number":54,"context_line":"            |      +-+-^-------+-^---+   | |    |"},{"line_number":55,"context_line":"            |        | |       | |       | |    |"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_b6563304","line":52,"range":{"start_line":52,"start_character":21,"end_line":52,"end_character":36},"in_reply_to":"7aa08908_8949b133","updated":"2016-06-10 13:13:22.000000000","message":"Hi Sripriya. Thanks alot for nice comments.\n#1. are you creating a new plugin for alarm based drivers?\nYes. \n#2. can you clarify what would be the scope of the framework?\nAlarm-framework handles the creation of Ceilometer alarm and handles callbacks/webhooks from low-level designs (ceilomater, monasca,..). Regarding to callback processing, I already responded to the last comment in this spec.","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":13485,"name":"Sripriya Seetharam","email":"sseetha@brocade.com","username":"Sripriya"},"change_message_id":"ffafff6ee0645e129e44628527cb2741adf7bb66","unresolved":false,"context_lines":[{"line_number":56,"context_line":"            | +------v-++  +---v-+-+  +--v-+-+  |"},{"line_number":57,"context_line":"            | |         |  |       |  |      |  |"},{"line_number":58,"context_line":"            | |         |  |       |  |      |  |"},{"line_number":59,"context_line":"            | |Ceilometer  |Monasca|  |Custom|  |"},{"line_number":60,"context_line":"            | |         |  |       |  |      |  |"},{"line_number":61,"context_line":"            | |         |  |       |  |      |  |"},{"line_number":62,"context_line":"            | |         |  |       |  |      |  |"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_10932bfb","line":59,"range":{"start_line":59,"start_character":15,"end_line":59,"end_character":45},"updated":"2016-06-08 21:50:26.000000000","message":"these are yet another set of \u0027alarm\u0027 based drivers under tacker\u0027s\u0027monitor\u0027 framework which will mostly handle the processing of alarm events. the abstract_driver [1] will be need to be revisited to handle these new interface methods for alarm based drivers, it is worth specifying the new abstractions to scope the design.\n\n[1] https://github.com/openstack/tacker/blob/master/tacker/vm/monitor_drivers/abstract_driver.py","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"6b9504283e4abb307032bcfd638743528169f37f","unresolved":false,"context_lines":[{"line_number":56,"context_line":"            | +------v-++  +---v-+-+  +--v-+-+  |"},{"line_number":57,"context_line":"            | |         |  |       |  |      |  |"},{"line_number":58,"context_line":"            | |         |  |       |  |      |  |"},{"line_number":59,"context_line":"            | |Ceilometer  |Monasca|  |Custom|  |"},{"line_number":60,"context_line":"            | |         |  |       |  |      |  |"},{"line_number":61,"context_line":"            | |         |  |       |  |      |  |"},{"line_number":62,"context_line":"            | |         |  |       |  |      |  |"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_165f470f","line":59,"range":{"start_line":59,"start_character":15,"end_line":59,"end_character":45},"in_reply_to":"7aa08908_10932bfb","updated":"2016-06-10 13:13:22.000000000","message":"Thanks. Modifying the abstract_driver was my work. Actually, we have other things to modify as well.","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":13485,"name":"Sripriya Seetharam","email":"sseetha@brocade.com","username":"Sripriya"},"change_message_id":"ffafff6ee0645e129e44628527cb2741adf7bb66","unresolved":false,"context_lines":[{"line_number":94,"context_line":"        type: tosca.policies.monitoring"},{"line_number":95,"context_line":"        targets: [vdu1]"},{"line_number":96,"context_line":"        triggers:"},{"line_number":97,"context_line":"            resize_compute:"},{"line_number":98,"context_line":"                event:"},{"line_number":99,"context_line":"                    type: tosca.events.resource.utilization"},{"line_number":100,"context_line":"                    driver: Ceilometer"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_a90f4d35","line":97,"range":{"start_line":97,"start_character":12,"end_line":97,"end_character":26},"updated":"2016-06-08 21:50:26.000000000","message":"is this the name of the trigger?","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"6b9504283e4abb307032bcfd638743528169f37f","unresolved":false,"context_lines":[{"line_number":94,"context_line":"        type: tosca.policies.monitoring"},{"line_number":95,"context_line":"        targets: [vdu1]"},{"line_number":96,"context_line":"        triggers:"},{"line_number":97,"context_line":"            resize_compute:"},{"line_number":98,"context_line":"                event:"},{"line_number":99,"context_line":"                    type: tosca.events.resource.utilization"},{"line_number":100,"context_line":"                    driver: Ceilometer"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_295821fa","line":97,"range":{"start_line":97,"start_character":12,"end_line":97,"end_character":26},"in_reply_to":"7aa08908_a90f4d35","updated":"2016-06-10 13:13:22.000000000","message":"right!","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":13485,"name":"Sripriya Seetharam","email":"sseetha@brocade.com","username":"Sripriya"},"change_message_id":"ffafff6ee0645e129e44628527cb2741adf7bb66","unresolved":false,"context_lines":[{"line_number":96,"context_line":"        triggers:"},{"line_number":97,"context_line":"            resize_compute:"},{"line_number":98,"context_line":"                event:"},{"line_number":99,"context_line":"                    type: tosca.events.resource.utilization"},{"line_number":100,"context_line":"                    driver: Ceilometer"},{"line_number":101,"context_line":"                metrics: cpu_util"},{"line_number":102,"context_line":"                condition: utilization greater_than 70%"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_afc74d94","line":99,"range":{"start_line":99,"start_character":26,"end_line":99,"end_character":59},"updated":"2016-06-08 21:50:26.000000000","message":"curious to know what are possible valid event types here","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"6b9504283e4abb307032bcfd638743528169f37f","unresolved":false,"context_lines":[{"line_number":96,"context_line":"        triggers:"},{"line_number":97,"context_line":"            resize_compute:"},{"line_number":98,"context_line":"                event:"},{"line_number":99,"context_line":"                    type: tosca.events.resource.utilization"},{"line_number":100,"context_line":"                    driver: Ceilometer"},{"line_number":101,"context_line":"                metrics: cpu_util"},{"line_number":102,"context_line":"                condition: utilization greater_than 70%"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_f0bef562","line":99,"range":{"start_line":99,"start_character":26,"end_line":99,"end_character":59},"in_reply_to":"7aa08908_afc74d94","updated":"2016-06-10 13:13:22.000000000","message":"As far as I know, TOSCA group currently focuses on events types for Health, Scaling and Performance. Ceilometer and Monasca are mentioned here.","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":13485,"name":"Sripriya Seetharam","email":"sseetha@brocade.com","username":"Sripriya"},"change_message_id":"ffafff6ee0645e129e44628527cb2741adf7bb66","unresolved":false,"context_lines":[{"line_number":98,"context_line":"                event:"},{"line_number":99,"context_line":"                    type: tosca.events.resource.utilization"},{"line_number":100,"context_line":"                    driver: Ceilometer"},{"line_number":101,"context_line":"                metrics: cpu_util"},{"line_number":102,"context_line":"                condition: utilization greater_than 70%"},{"line_number":103,"context_line":"                    period: 60"},{"line_number":104,"context_line":"                    evaluations: 1"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_740edce5","line":101,"range":{"start_line":101,"start_character":16,"end_line":101,"end_character":33},"updated":"2016-06-08 21:50:26.000000000","message":"having more examples of possible options will help understand. one for for port would be good example.","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"6b9504283e4abb307032bcfd638743528169f37f","unresolved":false,"context_lines":[{"line_number":98,"context_line":"                event:"},{"line_number":99,"context_line":"                    type: tosca.events.resource.utilization"},{"line_number":100,"context_line":"                    driver: Ceilometer"},{"line_number":101,"context_line":"                metrics: cpu_util"},{"line_number":102,"context_line":"                condition: utilization greater_than 70%"},{"line_number":103,"context_line":"                    period: 60"},{"line_number":104,"context_line":"                    evaluations: 1"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_76368bb5","line":101,"range":{"start_line":101,"start_character":16,"end_line":101,"end_character":33},"in_reply_to":"7aa08908_740edce5","updated":"2016-06-10 13:13:22.000000000","message":"nice suggestion :) I am glad to hear that you\u0027re interested in port monitoring. At least the corresponding action here is \"Log\". In the future, my thinking is about another action. For example, based on the port status, Tacker SFC can automatically change port in chain.","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":17952,"name":"Santosh Kodicherla","email":"ksantosh.cs@gmail.com","username":"santoshkumar"},"change_message_id":"5a4e7ae6767f3bfe2b4b3b984672c6510ebba964","unresolved":false,"context_lines":[{"line_number":99,"context_line":"                    type: tosca.events.resource.utilization"},{"line_number":100,"context_line":"                    driver: Ceilometer"},{"line_number":101,"context_line":"                metrics: cpu_util"},{"line_number":102,"context_line":"                condition: utilization greater_than 70%"},{"line_number":103,"context_line":"                    period: 60"},{"line_number":104,"context_line":"                    evaluations: 1"},{"line_number":105,"context_line":"                    statistics: average"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_fb5edbe7","line":102,"updated":"2016-06-06 18:25:01.000000000","message":"what are other options other than \u0027greater_than\u0027, Is it possible to add \u003e , \u003c or \u003e\u003d  or like gt,lt as mentioned in ceilometer resource type below.","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"410a5ea9c57de62c54bfba51417caae467333c30","unresolved":false,"context_lines":[{"line_number":99,"context_line":"                    type: tosca.events.resource.utilization"},{"line_number":100,"context_line":"                    driver: Ceilometer"},{"line_number":101,"context_line":"                metrics: cpu_util"},{"line_number":102,"context_line":"                condition: utilization greater_than 70%"},{"line_number":103,"context_line":"                    period: 60"},{"line_number":104,"context_line":"                    evaluations: 1"},{"line_number":105,"context_line":"                    statistics: average"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_b2c39888","line":102,"in_reply_to":"7aa08908_fb5edbe7","updated":"2016-06-07 15:44:32.000000000","message":"Sure. It should be like that. We need to map these to Ceilometer resource in HOT template as defined in line 119-143","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":13485,"name":"Sripriya Seetharam","email":"sseetha@brocade.com","username":"Sripriya"},"change_message_id":"ffafff6ee0645e129e44628527cb2741adf7bb66","unresolved":false,"context_lines":[{"line_number":103,"context_line":"                    period: 60"},{"line_number":104,"context_line":"                    evaluations: 1"},{"line_number":105,"context_line":"                    statistics: average"},{"line_number":106,"context_line":"                action:"},{"line_number":107,"context_line":"                    resize: vdu1_scaling_policy"},{"line_number":108,"context_line":""},{"line_number":109,"context_line":""}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_21a1b146","line":106,"range":{"start_line":106,"start_character":16,"end_line":106,"end_character":22},"updated":"2016-06-08 21:50:26.000000000","message":"can actions be web_hooks? how do we provide this in tosca template?","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"6b9504283e4abb307032bcfd638743528169f37f","unresolved":false,"context_lines":[{"line_number":103,"context_line":"                    period: 60"},{"line_number":104,"context_line":"                    evaluations: 1"},{"line_number":105,"context_line":"                    statistics: average"},{"line_number":106,"context_line":"                action:"},{"line_number":107,"context_line":"                    resize: vdu1_scaling_policy"},{"line_number":108,"context_line":""},{"line_number":109,"context_line":""}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_9613370d","line":106,"range":{"start_line":106,"start_character":16,"end_line":106,"end_character":22},"in_reply_to":"7aa08908_21a1b146","updated":"2016-06-10 13:13:22.000000000","message":"totally possible. we already discussed this in the last meeting. I also prepared for the new patchset.","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":17952,"name":"Santosh Kodicherla","email":"ksantosh.cs@gmail.com","username":"santoshkumar"},"change_message_id":"5a4e7ae6767f3bfe2b4b3b984672c6510ebba964","unresolved":false,"context_lines":[{"line_number":104,"context_line":"                    evaluations: 1"},{"line_number":105,"context_line":"                    statistics: average"},{"line_number":106,"context_line":"                action:"},{"line_number":107,"context_line":"                    resize: vdu1_scaling_policy"},{"line_number":108,"context_line":""},{"line_number":109,"context_line":""},{"line_number":110,"context_line":"There are two options to enforce the monitoring policy. In case of OpenStack Ceilometer,"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_7bfaebbe","line":107,"updated":"2016-06-06 18:25:01.000000000","message":"what are options for \u0027vdu1_scaling_policy\u0027 look like in template..??\nI mean once cpu utilization is greater than 70%, what are actions user can request here.Any examples..??","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":13485,"name":"Sripriya Seetharam","email":"sseetha@brocade.com","username":"Sripriya"},"change_message_id":"ffafff6ee0645e129e44628527cb2741adf7bb66","unresolved":false,"context_lines":[{"line_number":104,"context_line":"                    evaluations: 1"},{"line_number":105,"context_line":"                    statistics: average"},{"line_number":106,"context_line":"                action:"},{"line_number":107,"context_line":"                    resize: vdu1_scaling_policy"},{"line_number":108,"context_line":""},{"line_number":109,"context_line":""},{"line_number":110,"context_line":"There are two options to enforce the monitoring policy. In case of OpenStack Ceilometer,"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_c1926df5","line":107,"range":{"start_line":107,"start_character":20,"end_line":107,"end_character":26},"updated":"2016-06-08 21:50:26.000000000","message":"what are possible action types here?","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"410a5ea9c57de62c54bfba51417caae467333c30","unresolved":false,"context_lines":[{"line_number":104,"context_line":"                    evaluations: 1"},{"line_number":105,"context_line":"                    statistics: average"},{"line_number":106,"context_line":"                action:"},{"line_number":107,"context_line":"                    resize: vdu1_scaling_policy"},{"line_number":108,"context_line":""},{"line_number":109,"context_line":""},{"line_number":110,"context_line":"There are two options to enforce the monitoring policy. In case of OpenStack Ceilometer,"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_12f0acc8","line":107,"in_reply_to":"7aa08908_7bfaebbe","updated":"2016-06-07 15:44:32.000000000","message":"Here is an example of actions. When cpu utilization reaches to threshold, we totally consider some actions like \"log\", \"respawn\".","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":13485,"name":"Sripriya Seetharam","email":"sseetha@brocade.com","username":"Sripriya"},"change_message_id":"ffafff6ee0645e129e44628527cb2741adf7bb66","unresolved":false,"context_lines":[{"line_number":215,"context_line":"#. Enable the new convention in vnfd for mentioning to the alarm based"},{"line_number":216,"context_line":"   monitoring parameters"},{"line_number":217,"context_line":"#. create a sample TOSCA template"},{"line_number":218,"context_line":"#. Create a new monitoring driver for alarm based monitoring with configurable"},{"line_number":219,"context_line":"   parameter to use either of the approach mentioned above."},{"line_number":220,"context_line":"#. Enable to log Ceilometer alarms and report to users."},{"line_number":221,"context_line":"#. Enhance the horizon to show the live monitoring parameters."},{"line_number":222,"context_line":""}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_5015b399","line":219,"range":{"start_line":218,"start_character":3,"end_line":219,"end_character":59},"updated":"2016-06-08 21:50:26.000000000","message":"can you elaborate more on the functionality of ceilometer driver. I believe it will be used for processing the call backs from ceilometer alarms to invoke appropriate actions which can include log, scaling, etc.","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"6b9504283e4abb307032bcfd638743528169f37f","unresolved":false,"context_lines":[{"line_number":215,"context_line":"#. Enable the new convention in vnfd for mentioning to the alarm based"},{"line_number":216,"context_line":"   monitoring parameters"},{"line_number":217,"context_line":"#. create a sample TOSCA template"},{"line_number":218,"context_line":"#. Create a new monitoring driver for alarm based monitoring with configurable"},{"line_number":219,"context_line":"   parameter to use either of the approach mentioned above."},{"line_number":220,"context_line":"#. Enable to log Ceilometer alarms and report to users."},{"line_number":221,"context_line":"#. Enhance the horizon to show the live monitoring parameters."},{"line_number":222,"context_line":""}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_ece62a15","line":219,"range":{"start_line":218,"start_character":3,"end_line":219,"end_character":59},"in_reply_to":"7aa08908_5015b399","updated":"2016-06-10 13:13:22.000000000","message":"I need to carefully consider. But here is some things in my mind now. New patchset has capability to show below contents.\nActually, different actions have different callbacks. I am preparing some material for the next patchset.\nBased on the type of callbacks, we have the corresponding actions.\n#1. if action is \"Log\", the monitoring driver will restore alarms into database. We have two options to display these information:\n1. Use CLI.\n2. Modify Tacker-Horizon. My suggestion here is that we should have one tab, namely \"Alarm Collection\". This tab need to have some information like:\n[VDU-ID]-----[Kind of Alarm (CPU, MEMORY, PORT,...)]--- [Status (HIGH, LOW, DELETED,..)]\n#2. If action is \"Scaling\", we can call API to trigger scaling to Heat. I would like to refer to Kanagaraj\u0027s spec.\n#3. If action is \"respawn\", new trigger to Heat need be defined.\nex: v1.0/vnfs/\u003cvnf1\u003e/respawn...","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":13485,"name":"Sripriya Seetharam","email":"sseetha@brocade.com","username":"Sripriya"},"change_message_id":"ffafff6ee0645e129e44628527cb2741adf7bb66","unresolved":false,"context_lines":[{"line_number":223,"context_line":""},{"line_number":224,"context_line":"Dependencies"},{"line_number":225,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":226,"context_line":"None"},{"line_number":227,"context_line":""},{"line_number":228,"context_line":"Testing"},{"line_number":229,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_dde6db42","line":226,"range":{"start_line":226,"start_character":0,"end_line":226,"end_character":4},"updated":"2016-06-08 21:50:26.000000000","message":"Ceilometer?","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"6b9504283e4abb307032bcfd638743528169f37f","unresolved":false,"context_lines":[{"line_number":223,"context_line":""},{"line_number":224,"context_line":"Dependencies"},{"line_number":225,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":226,"context_line":"None"},{"line_number":227,"context_line":""},{"line_number":228,"context_line":"Testing"},{"line_number":229,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":10,"id":"7aa08908_113111ed","line":226,"range":{"start_line":226,"start_character":0,"end_line":226,"end_character":4},"in_reply_to":"7aa08908_dde6db42","updated":"2016-06-10 13:13:22.000000000","message":"Done","commit_id":"5ebbdb0ff0084826913960904536f15fc57d12b5"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"a8fd17e0ccfffd617b25f8eff6614ed4b90145e8","unresolved":false,"context_lines":[{"line_number":99,"context_line":"                event:"},{"line_number":100,"context_line":"                    type: tosca.events.resource.utilization"},{"line_number":101,"context_line":"                    implementation: Ceilometer"},{"line_number":102,"context_line":"                metrics: cpu_util"},{"line_number":103,"context_line":"                condition: utilization greater_than 70%"},{"line_number":104,"context_line":"                    period: 60"},{"line_number":105,"context_line":"                    evaluations: 1"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7aa08908_b12de8a9","line":102,"range":{"start_line":102,"start_character":16,"end_line":102,"end_character":33},"updated":"2016-06-14 23:03:03.000000000","message":"Which metrics are we going to support ? Is that going to be a subset of the Ceilometer alarm list ?","commit_id":"ed63462b2c1cd6b75c505dbccd617926c20406b3"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"025a6c1b81ae713a3d07ff73d11bfe7fe47cb3a6","unresolved":false,"context_lines":[{"line_number":99,"context_line":"                event:"},{"line_number":100,"context_line":"                    type: tosca.events.resource.utilization"},{"line_number":101,"context_line":"                    implementation: Ceilometer"},{"line_number":102,"context_line":"                metrics: cpu_util"},{"line_number":103,"context_line":"                condition: utilization greater_than 70%"},{"line_number":104,"context_line":"                    period: 60"},{"line_number":105,"context_line":"                    evaluations: 1"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7aa08908_29bbc476","line":102,"range":{"start_line":102,"start_character":16,"end_line":102,"end_character":33},"in_reply_to":"7aa08908_b12de8a9","updated":"2016-06-17 17:31:44.000000000","message":"Hi sridhar, \nActually, many things are coming. We have compute resources (memory usage, cpu usage, ...), network resources (Neutron port,..), Storage. Corresponding to the different kinds of resource, i believe that we have some things to do in the future. For example, we will need monitoring solutions for SFC, automatic resource creation... \n\nIMO, each metric might have different conditions and therefore has different actions. So, it should have different triggers in place.","commit_id":"ed63462b2c1cd6b75c505dbccd617926c20406b3"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"a8fd17e0ccfffd617b25f8eff6614ed4b90145e8","unresolved":false,"context_lines":[{"line_number":111,"context_line":""},{"line_number":112,"context_line":"alarm_url will be created by webhook in Tacker as the following:"},{"line_number":113,"context_line":""},{"line_number":114,"context_line":"v1.0/vnfs/\u003cvnf1\u003e/\u003cmonitoring-policy\u003e/\u003caction-id\u003e"},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"Where:"},{"line_number":117,"context_line":"monitoring-policy is the name of monitoring policy which is described in VNFD."}],"source_content_type":"text/x-rst","patch_set":12,"id":"7aa08908_710ee03b","line":114,"range":{"start_line":114,"start_character":38,"end_line":114,"end_character":47},"updated":"2016-06-14 23:03:03.000000000","message":"based on today\u0027s discussion this should be \u0027action-name\u0027 here and in the paragraph below.","commit_id":"ed63462b2c1cd6b75c505dbccd617926c20406b3"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"025a6c1b81ae713a3d07ff73d11bfe7fe47cb3a6","unresolved":false,"context_lines":[{"line_number":111,"context_line":""},{"line_number":112,"context_line":"alarm_url will be created by webhook in Tacker as the following:"},{"line_number":113,"context_line":""},{"line_number":114,"context_line":"v1.0/vnfs/\u003cvnf1\u003e/\u003cmonitoring-policy\u003e/\u003caction-id\u003e"},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"Where:"},{"line_number":117,"context_line":"monitoring-policy is the name of monitoring policy which is described in VNFD."}],"source_content_type":"text/x-rst","patch_set":12,"id":"7aa08908_a610da5a","line":114,"range":{"start_line":114,"start_character":38,"end_line":114,"end_character":47},"in_reply_to":"7aa08908_710ee03b","updated":"2016-06-17 17:31:44.000000000","message":"Done","commit_id":"ed63462b2c1cd6b75c505dbccd617926c20406b3"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"a8fd17e0ccfffd617b25f8eff6614ed4b90145e8","unresolved":false,"context_lines":[{"line_number":127,"context_line":""},{"line_number":128,"context_line":"Based on the different types of callbacks, we have the appropriate actions as following:"},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"#1. if action is \"Log\", the monitoring driver will restore alarms into database."},{"line_number":131,"context_line":"We have two options to display these information:"},{"line_number":132,"context_line":""},{"line_number":133,"context_line":" * Use CLI. The status of alarm could be defined in the existing CLI as the following:"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7aa08908_fc7c6772","line":130,"range":{"start_line":130,"start_character":59,"end_line":130,"end_character":65},"updated":"2016-06-14 23:03:03.000000000","message":"This sounds a bit like \"events\" proposed in the audit log support [1]. Instead of creating a new \"alarm\" construct in tacker can we just reuse a special \"event\" in the audit-log of type alarm ?\n\n[1] https://review.openstack.org/321370","commit_id":"ed63462b2c1cd6b75c505dbccd617926c20406b3"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"025a6c1b81ae713a3d07ff73d11bfe7fe47cb3a6","unresolved":false,"context_lines":[{"line_number":127,"context_line":""},{"line_number":128,"context_line":"Based on the different types of callbacks, we have the appropriate actions as following:"},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"#1. if action is \"Log\", the monitoring driver will restore alarms into database."},{"line_number":131,"context_line":"We have two options to display these information:"},{"line_number":132,"context_line":""},{"line_number":133,"context_line":" * Use CLI. The status of alarm could be defined in the existing CLI as the following:"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7aa08908_7690efed","line":130,"range":{"start_line":130,"start_character":59,"end_line":130,"end_character":65},"in_reply_to":"7aa08908_fc7c6772","updated":"2016-06-17 17:31:44.000000000","message":"if we want to have a generic solution, that is a way to go. But actually, alarm and event in some cases are totally different. IMHO, it still need a separate treatment for alarm. For instance, we should have one \"alarm\" tab  in Horizon.","commit_id":"ed63462b2c1cd6b75c505dbccd617926c20406b3"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"a8fd17e0ccfffd617b25f8eff6614ed4b90145e8","unresolved":false,"context_lines":[{"line_number":187,"context_line":"Based on these alarms, Tacker can invoke appropriate actions such as Log or Scaling."},{"line_number":188,"context_line":""},{"line_number":189,"context_line":"Indeed, it is necessary so that the monitoring driver could monitor beyond VDU resources."},{"line_number":190,"context_line":"CP resources should be monitored as well. Especially, it is necessary when we have SFC"},{"line_number":191,"context_line":"in the future. The reason is that each CP will need to assign to a Neutron port."},{"line_number":192,"context_line":"SFC is created based on the connection of Neutron ports, therefore port monitoring is"},{"line_number":193,"context_line":"necessary for high availability in SFC. Here is an example related to port monitoring in"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7aa08908_bc62dfaa","line":190,"range":{"start_line":190,"start_character":0,"end_line":190,"end_character":41},"updated":"2016-06-14 23:03:03.000000000","message":"This is a good idea, but my suggestion is to take this in a follow-on spec after we land the basic alarm-based monitoring. Otherwise this spec\u0027s scope will be too wide to address in one series of patchsets.","commit_id":"ed63462b2c1cd6b75c505dbccd617926c20406b3"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"025a6c1b81ae713a3d07ff73d11bfe7fe47cb3a6","unresolved":false,"context_lines":[{"line_number":187,"context_line":"Based on these alarms, Tacker can invoke appropriate actions such as Log or Scaling."},{"line_number":188,"context_line":""},{"line_number":189,"context_line":"Indeed, it is necessary so that the monitoring driver could monitor beyond VDU resources."},{"line_number":190,"context_line":"CP resources should be monitored as well. Especially, it is necessary when we have SFC"},{"line_number":191,"context_line":"in the future. The reason is that each CP will need to assign to a Neutron port."},{"line_number":192,"context_line":"SFC is created based on the connection of Neutron ports, therefore port monitoring is"},{"line_number":193,"context_line":"necessary for high availability in SFC. Here is an example related to port monitoring in"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7aa08908_6199bcd0","line":190,"range":{"start_line":190,"start_character":0,"end_line":190,"end_character":41},"in_reply_to":"7aa08908_bc62dfaa","updated":"2016-06-17 17:31:44.000000000","message":"OK. Actually future works reated to this spec are interesting to me.","commit_id":"ed63462b2c1cd6b75c505dbccd617926c20406b3"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"a8fd17e0ccfffd617b25f8eff6614ed4b90145e8","unresolved":false,"context_lines":[{"line_number":262,"context_line":"Security"},{"line_number":263,"context_line":"------------------"},{"line_number":264,"context_line":""},{"line_number":265,"context_line":"Need security between OpenStack Ceilometer and Tacker."},{"line_number":266,"context_line":""},{"line_number":267,"context_line":"Notifications impact"},{"line_number":268,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7aa08908_bca5bfb5","line":265,"range":{"start_line":265,"start_character":0,"end_line":265,"end_character":54},"updated":"2016-06-14 23:03:03.000000000","message":"We need to figure out a solution to make this secure. One option is to make this webhook unique and stateful. Meaning, create a unique url per alarm,\n\n/v1.0/vnfs/\u003cvnf1\u003e/2w3r40-34c2d2/\u003cmonitoring-policy\u003e/\u003caction-id\u003e\n\n... store this in tacker db and entertain only these unique webhook callbacks.\n\nThoughts?","commit_id":"ed63462b2c1cd6b75c505dbccd617926c20406b3"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"025a6c1b81ae713a3d07ff73d11bfe7fe47cb3a6","unresolved":false,"context_lines":[{"line_number":262,"context_line":"Security"},{"line_number":263,"context_line":"------------------"},{"line_number":264,"context_line":""},{"line_number":265,"context_line":"Need security between OpenStack Ceilometer and Tacker."},{"line_number":266,"context_line":""},{"line_number":267,"context_line":"Notifications impact"},{"line_number":268,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":12,"id":"7aa08908_a982f84f","line":265,"range":{"start_line":265,"start_character":0,"end_line":265,"end_character":54},"in_reply_to":"7aa08908_bca5bfb5","updated":"2016-06-17 17:31:44.000000000","message":"Right... I will mention to new security solution for this in the next patchset.","commit_id":"ed63462b2c1cd6b75c505dbccd617926c20406b3"},{"author":{"_account_id":20873,"name":"Laszlo Hegedus","email":"hegedues.laszlo@gmail.com","username":"laszloh"},"change_message_id":"8fa12b8f929f3a1207b102237c4e2a9427649b1b","unresolved":false,"context_lines":[{"line_number":10,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"ETSI MANO architecture describes to monitor the VNF to take appropriate action"},{"line_number":13,"context_line":"such as fault management, performance management. Monitoring became as"},{"line_number":14,"context_line":"important aspect in MANO architecture."},{"line_number":15,"context_line":"Currently, Tacker provides a very minimal support for check the liveliness"},{"line_number":16,"context_line":"of VNF elements by means of ping or curl which helps to recover the element"}],"source_content_type":"text/x-rst","patch_set":14,"id":"3aaa91ec_03c82721","line":13,"range":{"start_line":13,"start_character":68,"end_line":13,"end_character":70},"updated":"2016-06-30 12:49:42.000000000","message":"an","commit_id":"1cafbee90aeb0db21e2b7abf094fa7d9503f5afd"},{"author":{"_account_id":20873,"name":"Laszlo Hegedus","email":"hegedues.laszlo@gmail.com","username":"laszloh"},"change_message_id":"8fa12b8f929f3a1207b102237c4e2a9427649b1b","unresolved":false,"context_lines":[{"line_number":12,"context_line":"ETSI MANO architecture describes to monitor the VNF to take appropriate action"},{"line_number":13,"context_line":"such as fault management, performance management. Monitoring became as"},{"line_number":14,"context_line":"important aspect in MANO architecture."},{"line_number":15,"context_line":"Currently, Tacker provides a very minimal support for check the liveliness"},{"line_number":16,"context_line":"of VNF elements by means of ping or curl which helps to recover the element"},{"line_number":17,"context_line":"in case element is unreachable. But Tacker does not support to monitor"},{"line_number":18,"context_line":"VNF elements CPU/memory usage. Further, it is necessary for Tacker to monitor all"}],"source_content_type":"text/x-rst","patch_set":14,"id":"3aaa91ec_43e50fa2","line":15,"range":{"start_line":15,"start_character":54,"end_line":15,"end_character":59},"updated":"2016-06-30 12:49:42.000000000","message":"checking","commit_id":"1cafbee90aeb0db21e2b7abf094fa7d9503f5afd"},{"author":{"_account_id":20873,"name":"Laszlo Hegedus","email":"hegedues.laszlo@gmail.com","username":"laszloh"},"change_message_id":"8fa12b8f929f3a1207b102237c4e2a9427649b1b","unresolved":false,"context_lines":[{"line_number":14,"context_line":"important aspect in MANO architecture."},{"line_number":15,"context_line":"Currently, Tacker provides a very minimal support for check the liveliness"},{"line_number":16,"context_line":"of VNF elements by means of ping or curl which helps to recover the element"},{"line_number":17,"context_line":"in case element is unreachable. But Tacker does not support to monitor"},{"line_number":18,"context_line":"VNF elements CPU/memory usage. Further, it is necessary for Tacker to monitor all"},{"line_number":19,"context_line":"VNF resources as well. The reason is that the failure of VNFs happen too diversely."},{"line_number":20,"context_line":""}],"source_content_type":"text/x-rst","patch_set":14,"id":"3aaa91ec_c37e1fae","line":17,"range":{"start_line":17,"start_character":60,"end_line":17,"end_character":70},"updated":"2016-06-30 12:49:42.000000000","message":"monitoring of","commit_id":"1cafbee90aeb0db21e2b7abf094fa7d9503f5afd"},{"author":{"_account_id":20873,"name":"Laszlo Hegedus","email":"hegedues.laszlo@gmail.com","username":"laszloh"},"change_message_id":"8fa12b8f929f3a1207b102237c4e2a9427649b1b","unresolved":false,"context_lines":[{"line_number":14,"context_line":"important aspect in MANO architecture."},{"line_number":15,"context_line":"Currently, Tacker provides a very minimal support for check the liveliness"},{"line_number":16,"context_line":"of VNF elements by means of ping or curl which helps to recover the element"},{"line_number":17,"context_line":"in case element is unreachable. But Tacker does not support to monitor"},{"line_number":18,"context_line":"VNF elements CPU/memory usage. Further, it is necessary for Tacker to monitor all"},{"line_number":19,"context_line":"VNF resources as well. The reason is that the failure of VNFs happen too diversely."},{"line_number":20,"context_line":""}],"source_content_type":"text/x-rst","patch_set":14,"id":"3aaa91ec_436a2fee","line":17,"range":{"start_line":17,"start_character":8,"end_line":17,"end_character":15},"updated":"2016-06-30 12:49:42.000000000","message":"the word \u0027element\u0027 is repeated here. You can just write \u0027it\u0027.","commit_id":"1cafbee90aeb0db21e2b7abf094fa7d9503f5afd"},{"author":{"_account_id":20873,"name":"Laszlo Hegedus","email":"hegedues.laszlo@gmail.com","username":"laszloh"},"change_message_id":"8fa12b8f929f3a1207b102237c4e2a9427649b1b","unresolved":false,"context_lines":[{"line_number":15,"context_line":"Currently, Tacker provides a very minimal support for check the liveliness"},{"line_number":16,"context_line":"of VNF elements by means of ping or curl which helps to recover the element"},{"line_number":17,"context_line":"in case element is unreachable. But Tacker does not support to monitor"},{"line_number":18,"context_line":"VNF elements CPU/memory usage. Further, it is necessary for Tacker to monitor all"},{"line_number":19,"context_line":"VNF resources as well. The reason is that the failure of VNFs happen too diversely."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Proposed change"}],"source_content_type":"text/x-rst","patch_set":14,"id":"3aaa91ec_c3557f1e","line":18,"range":{"start_line":18,"start_character":0,"end_line":18,"end_character":29},"updated":"2016-06-30 12:49:42.000000000","message":"the CPU/memory usage of VNF elements","commit_id":"1cafbee90aeb0db21e2b7abf094fa7d9503f5afd"},{"author":{"_account_id":15755,"name":"Martin Oemke","email":"zeih@zeih.eu","username":"zeih"},"change_message_id":"013e2099b63347de48f8f0525d665d87cc67347b","unresolved":false,"context_lines":[{"line_number":25,"context_line":""},{"line_number":26,"context_line":"* designing a generic monitoring framework. Whereby, an alarm-based monitoring driver"},{"line_number":27,"context_line":"  in Tacker is designed to collect alarms/events triggered by the low-level designs"},{"line_number":28,"context_line":"  (Ceilometer, Monasca, custom driver). In this psec, the alarm-based monitoring"},{"line_number":29,"context_line":"  driver can totally monitor any resources in OpenStack that Ceilometer can support."},{"line_number":30,"context_line":"  In real implementation, this spec aims to leverage Ceilometer to monitor CPU/memory"},{"line_number":31,"context_line":"  usage inside VNF."}],"source_content_type":"text/x-rst","patch_set":14,"id":"3aaa91ec_5e727de4","line":28,"updated":"2016-06-28 13:25:57.000000000","message":"typo spec","commit_id":"1cafbee90aeb0db21e2b7abf094fa7d9503f5afd"},{"author":{"_account_id":20873,"name":"Laszlo Hegedus","email":"hegedues.laszlo@gmail.com","username":"laszloh"},"change_message_id":"8fa12b8f929f3a1207b102237c4e2a9427649b1b","unresolved":false,"context_lines":[{"line_number":26,"context_line":"* designing a generic monitoring framework. Whereby, an alarm-based monitoring driver"},{"line_number":27,"context_line":"  in Tacker is designed to collect alarms/events triggered by the low-level designs"},{"line_number":28,"context_line":"  (Ceilometer, Monasca, custom driver). In this psec, the alarm-based monitoring"},{"line_number":29,"context_line":"  driver can totally monitor any resources in OpenStack that Ceilometer can support."},{"line_number":30,"context_line":"  In real implementation, this spec aims to leverage Ceilometer to monitor CPU/memory"},{"line_number":31,"context_line":"  usage inside VNF."},{"line_number":32,"context_line":""}],"source_content_type":"text/x-rst","patch_set":14,"id":"3aaa91ec_3e6bb8ba","line":29,"range":{"start_line":29,"start_character":13,"end_line":29,"end_character":20},"updated":"2016-06-30 12:49:42.000000000","message":"completely?","commit_id":"1cafbee90aeb0db21e2b7abf094fa7d9503f5afd"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"20811913f4aaf6e106c48ae29379d1faa0f3b96c","unresolved":false,"context_lines":[{"line_number":115,"context_line":""},{"line_number":116,"context_line":".. code-block:: ini"},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"    v1.0/vnfs/\u003cvnf-uuid\u003e/\u003cmonitoring-policy-name\u003e/\u003caction-name\u003e/\u003cparams\u003e"},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"Where:"},{"line_number":121,"context_line":"monitoring-policy is the name of monitoring policy which is described in VNFD."}],"source_content_type":"text/x-rst","patch_set":14,"id":"3aaa91ec_9fb855c9","line":118,"updated":"2016-06-28 16:26:06.000000000","message":"i am just thining whether we could go with scaling REST API instead of going with new api, but that will be limited to only scaling...","commit_id":"1cafbee90aeb0db21e2b7abf094fa7d9503f5afd"},{"author":{"_account_id":13485,"name":"Sripriya Seetharam","email":"sseetha@brocade.com","username":"Sripriya"},"change_message_id":"2696d8fe60f5b76c7a9f7536081fafa8d7010183","unresolved":false,"context_lines":[{"line_number":115,"context_line":""},{"line_number":116,"context_line":".. code-block:: ini"},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"    v1.0/vnfs/\u003cvnf-uuid\u003e/\u003cmonitoring-policy-name\u003e/\u003caction-name\u003e/\u003cparams\u003e"},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"Where:"},{"line_number":121,"context_line":"monitoring-policy is the name of monitoring policy which is described in VNFD."}],"source_content_type":"text/x-rst","patch_set":14,"id":"3aaa91ec_c5a7ae09","line":118,"in_reply_to":"3aaa91ec_9fb855c9","updated":"2016-06-28 16:56:38.000000000","message":"yes, we do not want the actions to be just scale out/scale in, good to keep the alarm_url generic and the driver internally in Tacker will decide what to do with the url based on the policy","commit_id":"1cafbee90aeb0db21e2b7abf094fa7d9503f5afd"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"4d6eb37ed927f5f59785fb350b1144ab09a66f88","unresolved":false,"context_lines":[{"line_number":92,"context_line":"        availability_zone: nova"},{"line_number":93,"context_line":""},{"line_number":94,"context_line":"    vdu1_cpu_usage_monitoring_policy:"},{"line_number":95,"context_line":"        type: tosca.policies.monitoring"},{"line_number":96,"context_line":"        targets: [vdu1]"},{"line_number":97,"context_line":"        triggers:"},{"line_number":98,"context_line":"            resize_compute:"}],"source_content_type":"text/x-rst","patch_set":16,"id":"1aa78d24_449cf90d","line":95,"updated":"2016-07-12 17:05:15.000000000","message":"kindly add TOSCA schema for this new type","commit_id":"2e39e0987bbeae91a99804be03ae67ab6c1fa49d"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"709a99e7d1d96a10cc2ab357ce917fa10485de31","unresolved":false,"context_lines":[{"line_number":92,"context_line":"        availability_zone: nova"},{"line_number":93,"context_line":""},{"line_number":94,"context_line":"    vdu1_cpu_usage_monitoring_policy:"},{"line_number":95,"context_line":"        type: tosca.policies.monitoring"},{"line_number":96,"context_line":"        targets: [vdu1]"},{"line_number":97,"context_line":"        triggers:"},{"line_number":98,"context_line":"            resize_compute:"}],"source_content_type":"text/x-rst","patch_set":16,"id":"1aa78d24_12b778f6","line":95,"in_reply_to":"1aa78d24_449cf90d","updated":"2016-07-16 08:07:37.000000000","message":"Oh, sorry. I missed this one. I will update in the next patchset. Thanks.","commit_id":"2e39e0987bbeae91a99804be03ae67ab6c1fa49d"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"2be67a31e3267fba0271479aaa75ee5ba3e63c63","unresolved":false,"context_lines":[{"line_number":108,"context_line":"                    comparison: gt"},{"line_number":109,"context_line":"                action:"},{"line_number":110,"context_line":"                    resize: vdu1_scaling_policy"},{"line_number":111,"context_line":"                     implementation: Tacker.webhook()"},{"line_number":112,"context_line":""},{"line_number":113,"context_line":""},{"line_number":114,"context_line":"alarm_url will be created by webhook in Tacker as the following:"}],"source_content_type":"text/x-rst","patch_set":16,"id":"1aa78d24_9db0f844","line":111,"range":{"start_line":111,"start_character":21,"end_line":111,"end_character":53},"updated":"2016-07-12 15:44:05.000000000","message":"I\u0027m guessing this will be the implicit default implementation that will be picked when \"implementation: Ceilometer\" is used in L101 ? If yes, can this line be removed. I\u0027m trying to avoid having VNFD author write these lines can be safely assumed being the defaults.","commit_id":"2e39e0987bbeae91a99804be03ae67ab6c1fa49d"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"8673ec3d6ba93010f3c5768356aa2e5934b7b9be","unresolved":false,"context_lines":[{"line_number":108,"context_line":"                    comparison: gt"},{"line_number":109,"context_line":"                action:"},{"line_number":110,"context_line":"                    resize: vdu1_scaling_policy"},{"line_number":111,"context_line":"                     implementation: Tacker.webhook()"},{"line_number":112,"context_line":""},{"line_number":113,"context_line":""},{"line_number":114,"context_line":"alarm_url will be created by webhook in Tacker as the following:"}],"source_content_type":"text/x-rst","patch_set":16,"id":"dada55a8_585f690e","line":111,"range":{"start_line":111,"start_character":21,"end_line":111,"end_character":53},"in_reply_to":"1aa78d24_9db0f844","updated":"2016-07-17 22:44:54.000000000","message":"Done","commit_id":"2e39e0987bbeae91a99804be03ae67ab6c1fa49d"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"2be67a31e3267fba0271479aaa75ee5ba3e63c63","unresolved":false,"context_lines":[{"line_number":128,"context_line":"automatically. The detailed scaling mechanism using the monitoring driver is defined by"},{"line_number":129,"context_line":"the scaling spec: https://review.openstack.org/#/c/318577/"},{"line_number":130,"context_line":""},{"line_number":131,"context_line":"params contains the information related to alarm-actions. For example,"},{"line_number":132,"context_line":"it can be used for user authentication. Whereby, Webhook handler will generate"},{"line_number":133,"context_line":"randomly a key. This helps to make sure that we have a unique url for each alarm."},{"line_number":134,"context_line":"Alarm url will be stored in Tacker db and only these unique callbacks will be"},{"line_number":135,"context_line":"used. The expression showm below is an example of alarm url which contains user authentication"},{"line_number":136,"context_line":""},{"line_number":137,"context_line":".. code-block:: ini"},{"line_number":138,"context_line":""},{"line_number":139,"context_line":"    v1.0/vnfs/\u003cvnf-uuid\u003e/\u003cmonitoring-policy-name\u003e/\u003caction-name\u003e/2w3r40-34c2d2"},{"line_number":140,"context_line":""},{"line_number":141,"context_line":""},{"line_number":142,"context_line":"In addition, it is important so that Tacker user can update alarm configuration like threshold."}],"source_content_type":"text/x-rst","patch_set":16,"id":"1aa78d24_3dcc64ba","line":139,"range":{"start_line":131,"start_character":0,"end_line":139,"end_character":77},"updated":"2016-07-12 15:44:05.000000000","message":"Nice ! I like this approach.","commit_id":"2e39e0987bbeae91a99804be03ae67ab6c1fa49d"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"709a99e7d1d96a10cc2ab357ce917fa10485de31","unresolved":false,"context_lines":[{"line_number":128,"context_line":"automatically. The detailed scaling mechanism using the monitoring driver is defined by"},{"line_number":129,"context_line":"the scaling spec: https://review.openstack.org/#/c/318577/"},{"line_number":130,"context_line":""},{"line_number":131,"context_line":"params contains the information related to alarm-actions. For example,"},{"line_number":132,"context_line":"it can be used for user authentication. Whereby, Webhook handler will generate"},{"line_number":133,"context_line":"randomly a key. This helps to make sure that we have a unique url for each alarm."},{"line_number":134,"context_line":"Alarm url will be stored in Tacker db and only these unique callbacks will be"},{"line_number":135,"context_line":"used. The expression showm below is an example of alarm url which contains user authentication"},{"line_number":136,"context_line":""},{"line_number":137,"context_line":".. code-block:: ini"},{"line_number":138,"context_line":""},{"line_number":139,"context_line":"    v1.0/vnfs/\u003cvnf-uuid\u003e/\u003cmonitoring-policy-name\u003e/\u003caction-name\u003e/2w3r40-34c2d2"},{"line_number":140,"context_line":""},{"line_number":141,"context_line":""},{"line_number":142,"context_line":"In addition, it is important so that Tacker user can update alarm configuration like threshold."}],"source_content_type":"text/x-rst","patch_set":16,"id":"1aa78d24_f2b90c7e","line":139,"range":{"start_line":131,"start_character":0,"end_line":139,"end_character":77},"in_reply_to":"1aa78d24_3dcc64ba","updated":"2016-07-16 08:07:37.000000000","message":"thanks","commit_id":"2e39e0987bbeae91a99804be03ae67ab6c1fa49d"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"2be67a31e3267fba0271479aaa75ee5ba3e63c63","unresolved":false,"context_lines":[{"line_number":139,"context_line":"    v1.0/vnfs/\u003cvnf-uuid\u003e/\u003cmonitoring-policy-name\u003e/\u003caction-name\u003e/2w3r40-34c2d2"},{"line_number":140,"context_line":""},{"line_number":141,"context_line":""},{"line_number":142,"context_line":"In addition, it is important so that Tacker user can update alarm configuration like threshold."},{"line_number":143,"context_line":""},{"line_number":144,"context_line":".. code-block:: ini"},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"    tacker vnf-update --vnf-id \u003cvnf-id\u003e --monitoring-policy-name \u003cmonitoring policy\u003e"},{"line_number":147,"context_line":"                                        --threshold [threshold-value]"},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"Here, monitoring-policy-name is the name of  monitoring policy and threshold is a value"},{"line_number":150,"context_line":"which user wants to update."}],"source_content_type":"text/x-rst","patch_set":16,"id":"1aa78d24_bd705441","line":147,"range":{"start_line":142,"start_character":0,"end_line":147,"end_character":69},"updated":"2016-07-12 15:44:05.000000000","message":"How important is this update-threshold capability ?\n\nSo far in Tacker, VNFD + its params at the creation time is the source of truth - meaning, whatever limits, min-max range set during VNF instantiation stays through the life-cycle of VNF.\n\nNow L146, will set a new precedence where the policy values can be altered in the middle. This has implications in how we digest the VNFD template data (it needs to go into the DB instead of being in-time parsed) and how we manipulate the threshold - again in the DB and in the runtime data-structs. We also need to factor in tacker-server restarts.\n\nI\u0027d suggest we differ this aspect of this spec to a follow on effort.","commit_id":"2e39e0987bbeae91a99804be03ae67ab6c1fa49d"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"4d6eb37ed927f5f59785fb350b1144ab09a66f88","unresolved":false,"context_lines":[{"line_number":139,"context_line":"    v1.0/vnfs/\u003cvnf-uuid\u003e/\u003cmonitoring-policy-name\u003e/\u003caction-name\u003e/2w3r40-34c2d2"},{"line_number":140,"context_line":""},{"line_number":141,"context_line":""},{"line_number":142,"context_line":"In addition, it is important so that Tacker user can update alarm configuration like threshold."},{"line_number":143,"context_line":""},{"line_number":144,"context_line":".. code-block:: ini"},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"    tacker vnf-update --vnf-id \u003cvnf-id\u003e --monitoring-policy-name \u003cmonitoring policy\u003e"},{"line_number":147,"context_line":"                                        --threshold [threshold-value]"},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"Here, monitoring-policy-name is the name of  monitoring policy and threshold is a value"},{"line_number":150,"context_line":"which user wants to update."}],"source_content_type":"text/x-rst","patch_set":16,"id":"1aa78d24_a4295d9d","line":147,"range":{"start_line":142,"start_character":0,"end_line":147,"end_character":69},"in_reply_to":"1aa78d24_bd705441","updated":"2016-07-12 17:05:15.000000000","message":"kindly add note here that thersold should be parameterized in the template in order to make it as update-able.","commit_id":"2e39e0987bbeae91a99804be03ae67ab6c1fa49d"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"4d6eb37ed927f5f59785fb350b1144ab09a66f88","unresolved":false,"context_lines":[{"line_number":163,"context_line":"   [VDU-ID]-----[Alarms (CPU, MEMORY, PORT,...)]--- [Status (HIGH, LOW, DELETED,..)]."},{"line_number":164,"context_line":""},{"line_number":165,"context_line":"#2. If action is \"Scaling\", we can call API to trigger scaling. The detailed scaling"},{"line_number":166,"context_line":"    mechanism could be found in scaling spec."},{"line_number":167,"context_line":""},{"line_number":168,"context_line":"#3. If action is \"respawn\", this action is the same in case of ping driver."},{"line_number":169,"context_line":""}],"source_content_type":"text/x-rst","patch_set":16,"id":"1aa78d24_3f1d7462","line":166,"updated":"2016-07-12 17:05:15.000000000","message":"kindly add ref to scaling spec.","commit_id":"2e39e0987bbeae91a99804be03ae67ab6c1fa49d"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"709a99e7d1d96a10cc2ab357ce917fa10485de31","unresolved":false,"context_lines":[{"line_number":163,"context_line":"   [VDU-ID]-----[Alarms (CPU, MEMORY, PORT,...)]--- [Status (HIGH, LOW, DELETED,..)]."},{"line_number":164,"context_line":""},{"line_number":165,"context_line":"#2. If action is \"Scaling\", we can call API to trigger scaling. The detailed scaling"},{"line_number":166,"context_line":"    mechanism could be found in scaling spec."},{"line_number":167,"context_line":""},{"line_number":168,"context_line":"#3. If action is \"respawn\", this action is the same in case of ping driver."},{"line_number":169,"context_line":""}],"source_content_type":"text/x-rst","patch_set":16,"id":"1aa78d24_92a52849","line":166,"in_reply_to":"1aa78d24_3f1d7462","updated":"2016-07-16 08:07:37.000000000","message":"will do.. thanks","commit_id":"2e39e0987bbeae91a99804be03ae67ab6c1fa49d"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"2be67a31e3267fba0271479aaa75ee5ba3e63c63","unresolved":false,"context_lines":[{"line_number":205,"context_line":"             - {get_attr: [heat_alarm_url, tacker_alarm_url]}"},{"line_number":206,"context_line":""},{"line_number":207,"context_line":""},{"line_number":208,"context_line":"Regarding to auto-scaling, tacker_alarm_url will be added to alarm-actions."},{"line_number":209,"context_line":"Whereby, Ceilometer uses heat_alarm_url to trigger alarms to Heat, then Heat will do"},{"line_number":210,"context_line":"auuto-scaling. Ceilometer also uses tacker_alarm_url to trigger alarms to Tacker."},{"line_number":211,"context_line":"Based on these alarms, Tacker can invoke appropriate actions such as Log or Scaling."},{"line_number":212,"context_line":""},{"line_number":213,"context_line":"Indeed, it is necessary so that the monitoring driver could monitor beyond VDU resources."},{"line_number":214,"context_line":"CP resources should be monitored as well. Especially, it is necessary when we have SFC"}],"source_content_type":"text/x-rst","patch_set":16,"id":"1aa78d24_30700ba4","line":211,"range":{"start_line":208,"start_character":0,"end_line":211,"end_character":84},"updated":"2016-07-12 15:44:05.000000000","message":"Kanagaraj - is this inline with the recently merged scaling spec ?","commit_id":"2e39e0987bbeae91a99804be03ae67ab6c1fa49d"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"4d6eb37ed927f5f59785fb350b1144ab09a66f88","unresolved":false,"context_lines":[{"line_number":205,"context_line":"             - {get_attr: [heat_alarm_url, tacker_alarm_url]}"},{"line_number":206,"context_line":""},{"line_number":207,"context_line":""},{"line_number":208,"context_line":"Regarding to auto-scaling, tacker_alarm_url will be added to alarm-actions."},{"line_number":209,"context_line":"Whereby, Ceilometer uses heat_alarm_url to trigger alarms to Heat, then Heat will do"},{"line_number":210,"context_line":"auuto-scaling. Ceilometer also uses tacker_alarm_url to trigger alarms to Tacker."},{"line_number":211,"context_line":"Based on these alarms, Tacker can invoke appropriate actions such as Log or Scaling."},{"line_number":212,"context_line":""},{"line_number":213,"context_line":"Indeed, it is necessary so that the monitoring driver could monitor beyond VDU resources."},{"line_number":214,"context_line":"CP resources should be monitored as well. Especially, it is necessary when we have SFC"}],"source_content_type":"text/x-rst","patch_set":16,"id":"1aa78d24_9f458844","line":211,"range":{"start_line":208,"start_character":0,"end_line":211,"end_character":84},"in_reply_to":"1aa78d24_30700ba4","updated":"2016-07-12 17:05:15.000000000","message":"please remove the heat_alarm_url, as tacker wants to take the control on the scaling being triggered on heat.","commit_id":"2e39e0987bbeae91a99804be03ae67ab6c1fa49d"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"709a99e7d1d96a10cc2ab357ce917fa10485de31","unresolved":false,"context_lines":[{"line_number":205,"context_line":"             - {get_attr: [heat_alarm_url, tacker_alarm_url]}"},{"line_number":206,"context_line":""},{"line_number":207,"context_line":""},{"line_number":208,"context_line":"Regarding to auto-scaling, tacker_alarm_url will be added to alarm-actions."},{"line_number":209,"context_line":"Whereby, Ceilometer uses heat_alarm_url to trigger alarms to Heat, then Heat will do"},{"line_number":210,"context_line":"auuto-scaling. Ceilometer also uses tacker_alarm_url to trigger alarms to Tacker."},{"line_number":211,"context_line":"Based on these alarms, Tacker can invoke appropriate actions such as Log or Scaling."},{"line_number":212,"context_line":""},{"line_number":213,"context_line":"Indeed, it is necessary so that the monitoring driver could monitor beyond VDU resources."},{"line_number":214,"context_line":"CP resources should be monitored as well. Especially, it is necessary when we have SFC"}],"source_content_type":"text/x-rst","patch_set":16,"id":"1aa78d24_b27f84aa","line":211,"range":{"start_line":208,"start_character":0,"end_line":211,"end_character":84},"in_reply_to":"1aa78d24_9f458844","updated":"2016-07-16 08:07:37.000000000","message":"Oh, sorry. it is my mistake.","commit_id":"2e39e0987bbeae91a99804be03ae67ab6c1fa49d"},{"author":{"_account_id":13380,"name":"Sridhar Ramaswamy","email":"srics.r@gmail.com","username":"srics-r"},"change_message_id":"2be67a31e3267fba0271479aaa75ee5ba3e63c63","unresolved":false,"context_lines":[{"line_number":210,"context_line":"auuto-scaling. Ceilometer also uses tacker_alarm_url to trigger alarms to Tacker."},{"line_number":211,"context_line":"Based on these alarms, Tacker can invoke appropriate actions such as Log or Scaling."},{"line_number":212,"context_line":""},{"line_number":213,"context_line":"Indeed, it is necessary so that the monitoring driver could monitor beyond VDU resources."},{"line_number":214,"context_line":"CP resources should be monitored as well. Especially, it is necessary when we have SFC"},{"line_number":215,"context_line":"in the future. The reason is that each CP will need to assign to a Neutron port."},{"line_number":216,"context_line":"SFC is created based on the connection of Neutron ports, therefore port monitoring is"},{"line_number":217,"context_line":"necessary for high availability in SFC. The below example show port monitoring which"},{"line_number":218,"context_line":"could be done by the alarm-based monitoring driver:"},{"line_number":219,"context_line":""},{"line_number":220,"context_line":""},{"line_number":221,"context_line":".. code-block:: ini"},{"line_number":222,"context_line":""},{"line_number":223,"context_line":"    tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0"},{"line_number":224,"context_line":""},{"line_number":225,"context_line":"    description: Demo example"},{"line_number":226,"context_line":""},{"line_number":227,"context_line":"    metadata:"},{"line_number":228,"context_line":"    template_name: sample-tosca-vnfd"},{"line_number":229,"context_line":""},{"line_number":230,"context_line":"    topology_template:"},{"line_number":231,"context_line":"    node_templates:"},{"line_number":232,"context_line":"       VDU1:"},{"line_number":233,"context_line":"         type: tosca.nodes.nfv.VDU.Tacker"},{"line_number":234,"context_line":"         properties:"},{"line_number":235,"context_line":"           image: cirros-0.3.4-x86_64-uec"},{"line_number":236,"context_line":"           flavor: m1.tiny"},{"line_number":237,"context_line":"           availability_zone: nova"},{"line_number":238,"context_line":"           mgmt_driver: noop"},{"line_number":239,"context_line":"           config: |"},{"line_number":240,"context_line":"             param0: key1"},{"line_number":241,"context_line":"             param1: key2"},{"line_number":242,"context_line":""},{"line_number":243,"context_line":"       CP1:"},{"line_number":244,"context_line":"        type: tosca.nodes.nfv.CP.Tacker"},{"line_number":245,"context_line":"        properties:"},{"line_number":246,"context_line":"           management: true"},{"line_number":247,"context_line":"           anti_spoofing_protection: false"},{"line_number":248,"context_line":"        requirements:"},{"line_number":249,"context_line":"           - virtualLink:"},{"line_number":250,"context_line":"              node: VL1"},{"line_number":251,"context_line":"           - virtualBinding:"},{"line_number":252,"context_line":"              node: VDU1"},{"line_number":253,"context_line":"       CP_monitoring_policy:"},{"line_number":254,"context_line":"         type: tosca.policies.Monitoring"},{"line_number":255,"context_line":"         targets: [CP1]"},{"line_number":256,"context_line":"          triggers:"},{"line_number":257,"context_line":"            port_monitoring:"},{"line_number":258,"context_line":"              event:"},{"line_number":259,"context_line":"                type: tosca.events.resource.utilization"},{"line_number":260,"context_line":"                implementation: Ceilometer"},{"line_number":261,"context_line":"                metrics: port_bandwidth"},{"line_number":262,"context_line":"                condition: load greater_than 80%"},{"line_number":263,"context_line":"                period: 60"},{"line_number":264,"context_line":"                evaluations: 1"},{"line_number":265,"context_line":"                statistics: average"},{"line_number":266,"context_line":"                action:"},{"line_number":267,"context_line":"                 trigger: vnffg1-ha-policy"},{"line_number":268,"context_line":"                   implementation: Tacker.webhook()"},{"line_number":269,"context_line":""},{"line_number":270,"context_line":""},{"line_number":271,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":16,"id":"1aa78d24_90973f8f","line":268,"range":{"start_line":213,"start_character":0,"end_line":268,"end_character":51},"updated":"2016-07-12 15:44:05.000000000","message":"Please mark this section as \"Future considerations\" as this is something that is clearly out of scope for this spec.","commit_id":"2e39e0987bbeae91a99804be03ae67ab6c1fa49d"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"709a99e7d1d96a10cc2ab357ce917fa10485de31","unresolved":false,"context_lines":[{"line_number":210,"context_line":"auuto-scaling. Ceilometer also uses tacker_alarm_url to trigger alarms to Tacker."},{"line_number":211,"context_line":"Based on these alarms, Tacker can invoke appropriate actions such as Log or Scaling."},{"line_number":212,"context_line":""},{"line_number":213,"context_line":"Indeed, it is necessary so that the monitoring driver could monitor beyond VDU resources."},{"line_number":214,"context_line":"CP resources should be monitored as well. Especially, it is necessary when we have SFC"},{"line_number":215,"context_line":"in the future. The reason is that each CP will need to assign to a Neutron port."},{"line_number":216,"context_line":"SFC is created based on the connection of Neutron ports, therefore port monitoring is"},{"line_number":217,"context_line":"necessary for high availability in SFC. The below example show port monitoring which"},{"line_number":218,"context_line":"could be done by the alarm-based monitoring driver:"},{"line_number":219,"context_line":""},{"line_number":220,"context_line":""},{"line_number":221,"context_line":".. code-block:: ini"},{"line_number":222,"context_line":""},{"line_number":223,"context_line":"    tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0"},{"line_number":224,"context_line":""},{"line_number":225,"context_line":"    description: Demo example"},{"line_number":226,"context_line":""},{"line_number":227,"context_line":"    metadata:"},{"line_number":228,"context_line":"    template_name: sample-tosca-vnfd"},{"line_number":229,"context_line":""},{"line_number":230,"context_line":"    topology_template:"},{"line_number":231,"context_line":"    node_templates:"},{"line_number":232,"context_line":"       VDU1:"},{"line_number":233,"context_line":"         type: tosca.nodes.nfv.VDU.Tacker"},{"line_number":234,"context_line":"         properties:"},{"line_number":235,"context_line":"           image: cirros-0.3.4-x86_64-uec"},{"line_number":236,"context_line":"           flavor: m1.tiny"},{"line_number":237,"context_line":"           availability_zone: nova"},{"line_number":238,"context_line":"           mgmt_driver: noop"},{"line_number":239,"context_line":"           config: |"},{"line_number":240,"context_line":"             param0: key1"},{"line_number":241,"context_line":"             param1: key2"},{"line_number":242,"context_line":""},{"line_number":243,"context_line":"       CP1:"},{"line_number":244,"context_line":"        type: tosca.nodes.nfv.CP.Tacker"},{"line_number":245,"context_line":"        properties:"},{"line_number":246,"context_line":"           management: true"},{"line_number":247,"context_line":"           anti_spoofing_protection: false"},{"line_number":248,"context_line":"        requirements:"},{"line_number":249,"context_line":"           - virtualLink:"},{"line_number":250,"context_line":"              node: VL1"},{"line_number":251,"context_line":"           - virtualBinding:"},{"line_number":252,"context_line":"              node: VDU1"},{"line_number":253,"context_line":"       CP_monitoring_policy:"},{"line_number":254,"context_line":"         type: tosca.policies.Monitoring"},{"line_number":255,"context_line":"         targets: [CP1]"},{"line_number":256,"context_line":"          triggers:"},{"line_number":257,"context_line":"            port_monitoring:"},{"line_number":258,"context_line":"              event:"},{"line_number":259,"context_line":"                type: tosca.events.resource.utilization"},{"line_number":260,"context_line":"                implementation: Ceilometer"},{"line_number":261,"context_line":"                metrics: port_bandwidth"},{"line_number":262,"context_line":"                condition: load greater_than 80%"},{"line_number":263,"context_line":"                period: 60"},{"line_number":264,"context_line":"                evaluations: 1"},{"line_number":265,"context_line":"                statistics: average"},{"line_number":266,"context_line":"                action:"},{"line_number":267,"context_line":"                 trigger: vnffg1-ha-policy"},{"line_number":268,"context_line":"                   implementation: Tacker.webhook()"},{"line_number":269,"context_line":""},{"line_number":270,"context_line":""},{"line_number":271,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":16,"id":"1aa78d24_93faa9bb","line":268,"range":{"start_line":213,"start_character":0,"end_line":268,"end_character":51},"in_reply_to":"1aa78d24_90973f8f","updated":"2016-07-16 08:07:37.000000000","message":"Done","commit_id":"2e39e0987bbeae91a99804be03ae67ab6c1fa49d"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"4d6eb37ed927f5f59785fb350b1144ab09a66f88","unresolved":false,"context_lines":[{"line_number":281,"context_line":"REST API impact"},{"line_number":282,"context_line":"------------------"},{"line_number":283,"context_line":""},{"line_number":284,"context_line":"POST on  /v1.0/vnfs/\u003cvnf-uuid\u003e/\u003cmonitoring-policy\u003e/\u003caction-name\u003e/\u003cparams\u003e"},{"line_number":285,"context_line":""},{"line_number":286,"context_line":"Security"},{"line_number":287,"context_line":"------------------"}],"source_content_type":"text/x-rst","patch_set":16,"id":"1aa78d24_3ff0d4fc","line":284,"updated":"2016-07-12 17:05:15.000000000","message":"kindly mention about the POST body , how it looks like","commit_id":"2e39e0987bbeae91a99804be03ae67ab6c1fa49d"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"8673ec3d6ba93010f3c5768356aa2e5934b7b9be","unresolved":false,"context_lines":[{"line_number":281,"context_line":"REST API impact"},{"line_number":282,"context_line":"------------------"},{"line_number":283,"context_line":""},{"line_number":284,"context_line":"POST on  /v1.0/vnfs/\u003cvnf-uuid\u003e/\u003cmonitoring-policy\u003e/\u003caction-name\u003e/\u003cparams\u003e"},{"line_number":285,"context_line":""},{"line_number":286,"context_line":"Security"},{"line_number":287,"context_line":"------------------"}],"source_content_type":"text/x-rst","patch_set":16,"id":"dada55a8_836212d7","line":284,"in_reply_to":"1aa78d24_3ff0d4fc","updated":"2016-07-17 22:44:54.000000000","message":"When I checked notifier function in Ceilometer, it already defined the POST body with alarm information [1]. Once Ceilometer hits alarm url, the alarm information contained in the POST body then will be handled by Heat in [1].\n\n[1] https://github.com/openstack/ceilometer/blob/stable/liberty/ceilometer/alarm/notifier/rest.py#L76\n\n[2] https://github.com/openstack/heat/blob/master/heat/engine/resources/openstack/heat/scaling_policy.py#L145","commit_id":"2e39e0987bbeae91a99804be03ae67ab6c1fa49d"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"4d6eb37ed927f5f59785fb350b1144ab09a66f88","unresolved":false,"context_lines":[{"line_number":286,"context_line":"Security"},{"line_number":287,"context_line":"------------------"},{"line_number":288,"context_line":""},{"line_number":289,"context_line":"Need security between OpenStack Ceilometer and Tacker."},{"line_number":290,"context_line":""},{"line_number":291,"context_line":"Notifications impact"},{"line_number":292,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":16,"id":"1aa78d24_9fb8e812","line":289,"updated":"2016-07-12 17:05:15.000000000","message":"is this possible today with ceiloemeter?","commit_id":"2e39e0987bbeae91a99804be03ae67ab6c1fa49d"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"8673ec3d6ba93010f3c5768356aa2e5934b7b9be","unresolved":false,"context_lines":[{"line_number":286,"context_line":"Security"},{"line_number":287,"context_line":"------------------"},{"line_number":288,"context_line":""},{"line_number":289,"context_line":"Need security between OpenStack Ceilometer and Tacker."},{"line_number":290,"context_line":""},{"line_number":291,"context_line":"Notifications impact"},{"line_number":292,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":16,"id":"dada55a8_434bfa2b","line":289,"in_reply_to":"1aa78d24_9fb8e812","updated":"2016-07-17 22:44:54.000000000","message":"As I know, this is supported in Ceilometer.","commit_id":"2e39e0987bbeae91a99804be03ae67ab6c1fa49d"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"720e086cfc4b54813b5a510227c760c7607d2df0","unresolved":false,"context_lines":[{"line_number":80,"context_line":"      description: List of monitored VDUs"},{"line_number":81,"context_line":"    triggers:"},{"line_number":82,"context_line":"      resize_compute:"},{"line_number":83,"context_line":"        event:"},{"line_number":84,"context_line":"          type: map"},{"line_number":85,"context_line":"          entry_schema:"},{"line_number":86,"context_line":"            type: string"}],"source_content_type":"text/x-rst","patch_set":18,"id":"dada55a8_881d0a69","line":83,"updated":"2016-07-18 04:25:02.000000000","message":"there is an mismatch here. event vs event_type defined at line 133","commit_id":"24b329fe23f5640e83c1d02d6e30dbcb942019af"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"f91754819509e397ad39b35892e0fa38d5a97191","unresolved":false,"context_lines":[{"line_number":80,"context_line":"      description: List of monitored VDUs"},{"line_number":81,"context_line":"    triggers:"},{"line_number":82,"context_line":"      resize_compute:"},{"line_number":83,"context_line":"        event:"},{"line_number":84,"context_line":"          type: map"},{"line_number":85,"context_line":"          entry_schema:"},{"line_number":86,"context_line":"            type: string"}],"source_content_type":"text/x-rst","patch_set":18,"id":"dada55a8_b94bf4af","line":83,"in_reply_to":"dada55a8_881d0a69","updated":"2016-07-18 12:19:14.000000000","message":"Done","commit_id":"24b329fe23f5640e83c1d02d6e30dbcb942019af"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"720e086cfc4b54813b5a510227c760c7607d2df0","unresolved":false,"context_lines":[{"line_number":131,"context_line":"        triggers:"},{"line_number":132,"context_line":"            resize_compute:"},{"line_number":133,"context_line":"                event_type:"},{"line_number":134,"context_line":"                    type: tosca.events.resource.utilization"},{"line_number":135,"context_line":"                    implementation: Ceilometer"},{"line_number":136,"context_line":"                metrics: cpu_util"},{"line_number":137,"context_line":"                condition: utilization greater_than 70%"}],"source_content_type":"text/x-rst","patch_set":18,"id":"dada55a8_a82a8e7c","line":134,"updated":"2016-07-18 04:25:02.000000000","message":"is this type already defined by tosca profile, if so pls add reference to it.","commit_id":"24b329fe23f5640e83c1d02d6e30dbcb942019af"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"f91754819509e397ad39b35892e0fa38d5a97191","unresolved":false,"context_lines":[{"line_number":131,"context_line":"        triggers:"},{"line_number":132,"context_line":"            resize_compute:"},{"line_number":133,"context_line":"                event_type:"},{"line_number":134,"context_line":"                    type: tosca.events.resource.utilization"},{"line_number":135,"context_line":"                    implementation: Ceilometer"},{"line_number":136,"context_line":"                metrics: cpu_util"},{"line_number":137,"context_line":"                condition: utilization greater_than 70%"}],"source_content_type":"text/x-rst","patch_set":18,"id":"dada55a8_a6763f3c","line":134,"in_reply_to":"dada55a8_a82a8e7c","updated":"2016-07-18 12:19:14.000000000","message":"Done","commit_id":"24b329fe23f5640e83c1d02d6e30dbcb942019af"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"720e086cfc4b54813b5a510227c760c7607d2df0","unresolved":false,"context_lines":[{"line_number":321,"context_line":"Security"},{"line_number":322,"context_line":"------------------"},{"line_number":323,"context_line":""},{"line_number":324,"context_line":"Need security between OpenStack Ceilometer and Tacker."},{"line_number":325,"context_line":""},{"line_number":326,"context_line":"Notifications impact"},{"line_number":327,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":18,"id":"dada55a8_08091a2d","line":324,"updated":"2016-07-18 04:25:02.000000000","message":"please add reference to the ceilometer details on how the security is achieved","commit_id":"24b329fe23f5640e83c1d02d6e30dbcb942019af"},{"author":{"_account_id":20560,"name":"Tung Doan","email":"doantungbk.203@gmail.com","username":"doantungbk"},"change_message_id":"f91754819509e397ad39b35892e0fa38d5a97191","unresolved":false,"context_lines":[{"line_number":321,"context_line":"Security"},{"line_number":322,"context_line":"------------------"},{"line_number":323,"context_line":""},{"line_number":324,"context_line":"Need security between OpenStack Ceilometer and Tacker."},{"line_number":325,"context_line":""},{"line_number":326,"context_line":"Notifications impact"},{"line_number":327,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":18,"id":"dada55a8_59d118cd","line":324,"in_reply_to":"dada55a8_08091a2d","updated":"2016-07-18 12:19:14.000000000","message":"Done","commit_id":"24b329fe23f5640e83c1d02d6e30dbcb942019af"},{"author":{"_account_id":10487,"name":"Kanagaraj Manickam","email":"mkr1481@gmail.com","username":"kanagarajm"},"change_message_id":"1d3cc4135ea0d4a13e0e0de8c1e4641edccf373e","unresolved":false,"context_lines":[{"line_number":143,"context_line":"                action:"},{"line_number":144,"context_line":"                    resize: vdu1_scaling_policy"},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"In the above template, event type is described in [3]_ and used in [4]_."},{"line_number":147,"context_line":""},{"line_number":148,"context_line":"alarm_url will be created by webhook in Tacker as the following:"},{"line_number":149,"context_line":""}],"source_content_type":"text/x-rst","patch_set":20,"id":"dada55a8_7afae5be","line":146,"range":{"start_line":146,"start_character":49,"end_line":146,"end_character":54},"updated":"2016-07-19 04:32:58.000000000","message":"I believe its not an reference from TOSCA spec and should we define in the schema instead?","commit_id":"7ac9ce4e686ac217dbb0387238d8b32a10f13a62"}]}