)]}'
{"reference/programs.yaml":[{"author":{"_account_id":595,"name":"Nick Barcet","email":"nicolas@barcet.com","username":"nijaba"},"change_message_id":"bbdad976a3be15d2c34fc896e930aaa8d85999cd","unresolved":false,"context_lines":[{"line_number":90,"context_line":""},{"line_number":91,"context_line":"Telemetry:"},{"line_number":92,"context_line":"  codename: Ceilometer"},{"line_number":93,"context_line":"  ptl : Julien Danjou (jd__)"},{"line_number":94,"context_line":"  mission:"},{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAW3%2F%2FUGo%3D","line":93,"updated":"2014-04-15 12:28:21.000000000","message":"Hasn\u0027t the PTL changed?","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"615e12eb03cdbdb79ea7dd0a4bce0ab5c7d97453","unresolved":false,"context_lines":[{"line_number":90,"context_line":""},{"line_number":91,"context_line":"Telemetry:"},{"line_number":92,"context_line":"  codename: Ceilometer"},{"line_number":93,"context_line":"  ptl : Julien Danjou (jd__)"},{"line_number":94,"context_line":"  mission:"},{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAW3%2F%2FR4c%3D","line":93,"in_reply_to":"AAAAW3%2F%2FUGo%3D","updated":"2014-04-15 16:35:23.000000000","message":"Yep, that\u0027s addressed in a separate patch:\n\n  https://review.openstack.org/86896","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":9562,"name":"Ildiko Vancsa","email":"ildiko.vancsa@gmail.com","username":"ildikov"},"change_message_id":"f67196eb68dec2b46f9b13ea13c0de0fb7bfc36f","unresolved":false,"context_lines":[{"line_number":93,"context_line":"  ptl : Julien Danjou (jd__)"},{"line_number":94,"context_line":"  mission:"},{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"},{"line_number":97,"context_line":"    deployed at arbitrary scale, so as to provide insight over these"},{"line_number":98,"context_line":"    data to a wide variety of consumers."},{"line_number":99,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAW3%2F%2FT8o%3D","line":96,"updated":"2014-04-15 12:39:48.000000000","message":"I think a comma would be needed after resources, or if you don\u0027t agree with that, then after clouds. What do you think?","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"3965f988fbe82191d3b73b4854525f07e6280c30","unresolved":false,"context_lines":[{"line_number":93,"context_line":"  ptl : Julien Danjou (jd__)"},{"line_number":94,"context_line":"  mission:"},{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"},{"line_number":97,"context_line":"    deployed at arbitrary scale, so as to provide insight over these"},{"line_number":98,"context_line":"    data to a wide variety of consumers."},{"line_number":99,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAXH%2F%2Fdvw%3D","line":96,"updated":"2014-04-21 15:22:48.000000000","message":"Saying \"OpenStack\" is redundant, and we\u0027ve tried to avoid that in the other mission statements.","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"80e6042fbcfff939d358758c79c293f142f59f02","unresolved":false,"context_lines":[{"line_number":93,"context_line":"  ptl : Julien Danjou (jd__)"},{"line_number":94,"context_line":"  mission:"},{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"},{"line_number":97,"context_line":"    deployed at arbitrary scale, so as to provide insight over these"},{"line_number":98,"context_line":"    data to a wide variety of consumers."},{"line_number":99,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAXH%2F%2F7Mw%3D","line":96,"in_reply_to":"AAAAW3%2F%2FPYQ%3D","updated":"2014-04-16 13:33:08.000000000","message":"@jog0\n\n\u003e I thought ceilometer started at as something to collect data needed for billing ... It would be disappointing if ceilometer doesn\u0027t solve this use case anymore\n\nIt did, and it still does.\n\nThe word \"utilization\" in the mission statement was intended to connote \"to make use of\" or \"to put to use\", the sense of who is using what cloud resources for how long (such usage data being the basis for billing calculations).\n\nHowever perhaps we need to be more careful in our choice of words, given that utilization can also give the sense of metrics like CPU utilization % (which BTW ceilometer also collects for instances).\n\nWould for example \"existence\", \"ownership\", or \"consumption\" work better for you.\n\n\u003e Aren\u0027t there other solutions for collecting measurements about utilization and performance of machines\n\nYes there are, and ceilometer doesn\u0027t seek to displace those tools.\n\nHowever there is a place for an openstack-native collection of such metrics with an awareness of issues like tenant association \u0026 user metadata for example. This allows for example Heat autoscaling actions to be driven by threshold crossing of the average CPU utilization for instances owned by a certain tenant \u0026 with a certain piece of user metadata set to indicate membership of a particular autoscaling group.\n\nBut we do not claim that ceilometer will abrogate the need for say Nagios or Zabbix or \u003cinsert your favorite monitoring tool here\u003e.\n\n\u003e I would be interested in seeing what some of the non-goals of ceilometer are as well\n\nSure we can discuss non-goals, but I\u0027m not sure this file is the right place to define them, given that this is not the style followed by other projects\u0027 mission statements AFAICS.","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":9562,"name":"Ildiko Vancsa","email":"ildiko.vancsa@gmail.com","username":"ildikov"},"change_message_id":"2fb3e86472219150b9063235bda7605d04af58d1","unresolved":false,"context_lines":[{"line_number":93,"context_line":"  ptl : Julien Danjou (jd__)"},{"line_number":94,"context_line":"  mission:"},{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"},{"line_number":97,"context_line":"    deployed at arbitrary scale, so as to provide insight over these"},{"line_number":98,"context_line":"    data to a wide variety of consumers."},{"line_number":99,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAW3%2F%2FRK0%3D","line":96,"in_reply_to":"AAAAW3%2F%2FR3M%3D","updated":"2014-04-15 16:59:03.000000000","message":"This version is fine also, as it breaks the flow just as much as needed. It is a quite long sentence, so it is better to have some \"separators\" to keep it easily understandable, IMHO.","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"5679a637d8bb474a4ac494a38a40753a325f6fd8","unresolved":false,"context_lines":[{"line_number":93,"context_line":"  ptl : Julien Danjou (jd__)"},{"line_number":94,"context_line":"  mission:"},{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"},{"line_number":97,"context_line":"    deployed at arbitrary scale, so as to provide insight over these"},{"line_number":98,"context_line":"    data to a wide variety of consumers."},{"line_number":99,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAW3%2F%2FPYQ%3D","line":96,"in_reply_to":"AAAAW3%2F%2FRK0%3D","updated":"2014-04-15 20:50:28.000000000","message":"I am confused about this part.\n\nAren\u0027t there other solutions for collecting measurements about utilization and performance of machines? Why do we need our own.\n\nI thought ceilometer started at as something to collect data needed for billing. I don\u0027t see that anywhere in this new mission. It would be disappointing if ceilometer doesn\u0027t solve this use case anymore.\n\nI would be interested in seeing what some of the non-goals of ceilometer are as well, so we can help prevent feature creep.","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"615e12eb03cdbdb79ea7dd0a4bce0ab5c7d97453","unresolved":false,"context_lines":[{"line_number":93,"context_line":"  ptl : Julien Danjou (jd__)"},{"line_number":94,"context_line":"  mission:"},{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"},{"line_number":97,"context_line":"    deployed at arbitrary scale, so as to provide insight over these"},{"line_number":98,"context_line":"    data to a wide variety of consumers."},{"line_number":99,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAW3%2F%2FR3M%3D","line":96,"in_reply_to":"AAAAW3%2F%2FT8o%3D","updated":"2014-04-15 16:35:23.000000000","message":"Hmmm, commas seem to break the flow a bit.\n\nHow about?\n\n  ... for the virtual and physical resources that comprise OpenStack clouds deployed at scale","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"fba09ce6601e618fd12dfbe5c24be47ef40e798a","unresolved":false,"context_lines":[{"line_number":93,"context_line":"  ptl : Julien Danjou (jd__)"},{"line_number":94,"context_line":"  mission:"},{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"},{"line_number":97,"context_line":"    deployed at arbitrary scale, so as to provide insight over these"},{"line_number":98,"context_line":"    data to a wide variety of consumers."},{"line_number":99,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAXH%2F%2FRVM%3D","line":96,"in_reply_to":"AAAAXH%2F%2F7Mw%3D","updated":"2014-04-22 20:59:11.000000000","message":"Perhaps non goals don\u0027t fit in the mission statement, but this mission statement seems to be a little too wide.","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"3965f988fbe82191d3b73b4854525f07e6280c30","unresolved":false,"context_lines":[{"line_number":94,"context_line":"  mission:"},{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"},{"line_number":97,"context_line":"    deployed at arbitrary scale, so as to provide insight over these"},{"line_number":98,"context_line":"    data to a wide variety of consumers."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"  url: https://wiki.openstack.org/wiki/Ceilometer"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAXH%2F%2FdvI%3D","line":97,"updated":"2014-04-21 15:22:48.000000000","message":"Is \"deployed at arbitrary scale\" a significant aspect of the mission? It feels like something else we could leave out. Don\u0027t we assume the OpenStack components work together at similar scale?","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":595,"name":"Nick Barcet","email":"nicolas@barcet.com","username":"nijaba"},"change_message_id":"bbdad976a3be15d2c34fc896e930aaa8d85999cd","unresolved":false,"context_lines":[{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"},{"line_number":97,"context_line":"    deployed at arbitrary scale, so as to provide insight over these"},{"line_number":98,"context_line":"    data to a wide variety of consumers."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"  url: https://wiki.openstack.org/wiki/Ceilometer"},{"line_number":101,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAW3%2F%2FUE8%3D","line":98,"updated":"2014-04-15 12:28:21.000000000","message":"I would add a list of potential use cases, to be a little be more concrete.  For example: \"Common use cases are: \n* collecting data for rating and billing application\n* providing an alerting mechanisms for cloud applications and orchestrators\n* collecting data for monitoring tools\n* exposing usage data to end users\"","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"3965f988fbe82191d3b73b4854525f07e6280c30","unresolved":false,"context_lines":[{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"},{"line_number":97,"context_line":"    deployed at arbitrary scale, so as to provide insight over these"},{"line_number":98,"context_line":"    data to a wide variety of consumers."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"  url: https://wiki.openstack.org/wiki/Ceilometer"},{"line_number":101,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAXH%2F%2Fdt8%3D","line":98,"in_reply_to":"AAAAW3%2F%2FRdU%3D","updated":"2014-04-21 15:22:48.000000000","message":"Indeed, we have been trying to keep the mission statements short and flexible, so I don\u0027t think you want to go into too much detail about specific use cases.\n\nTo Gordon\u0027s point, you could consider shortening this to:\n\n  To collect measurements of utilization and performance\n  indicators for cloud resources.","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"615e12eb03cdbdb79ea7dd0a4bce0ab5c7d97453","unresolved":false,"context_lines":[{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"},{"line_number":97,"context_line":"    deployed at arbitrary scale, so as to provide insight over these"},{"line_number":98,"context_line":"    data to a wide variety of consumers."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"  url: https://wiki.openstack.org/wiki/Ceilometer"},{"line_number":101,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAW3%2F%2FRcc%3D","line":98,"in_reply_to":"AAAAW3%2F%2FT8s%3D","updated":"2014-04-15 16:35:23.000000000","message":"@nprivalova: detailed analytics are not currently in scope for the project. The statistical aggregates provided are still relatively simple, i.e. we can serve out an average or a standard deviation but not, say, a linear regression.","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":9562,"name":"Ildiko Vancsa","email":"ildiko.vancsa@gmail.com","username":"ildikov"},"change_message_id":"9af72a9dcad32941c2124f1bedbceb6215f1153a","unresolved":false,"context_lines":[{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"},{"line_number":97,"context_line":"    deployed at arbitrary scale, so as to provide insight over these"},{"line_number":98,"context_line":"    data to a wide variety of consumers."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"  url: https://wiki.openstack.org/wiki/Ceilometer"},{"line_number":101,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAW3%2F%2FTsM%3D","line":98,"in_reply_to":"AAAAW3%2F%2FT8s%3D","updated":"2014-04-15 13:04:06.000000000","message":"I assume \u0027exposing usage data\u0027 means only to make the collected information available to end users. In my opinion it is better to list less things that we mostly have currently, than more, which includes directions that is not implemented yet and therefore can be easily changed.\n\nAlso I\u0027m not sure how much it is the scope of Ceilometer itself to do complex analysis on the collected data. I would vote for that it is not, or at most, maybe it can be started here and then it will be a separate project like how Ironic became a standalone module, but I\u0027m not sure in this either.","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"541518e585f7ebbf1f2af97295eb55c0a8bc0c49","unresolved":false,"context_lines":[{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"},{"line_number":97,"context_line":"    deployed at arbitrary scale, so as to provide insight over these"},{"line_number":98,"context_line":"    data to a wide variety of consumers."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"  url: https://wiki.openstack.org/wiki/Ceilometer"},{"line_number":101,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAW3%2F%2FTw4%3D","line":98,"in_reply_to":"AAAAW3%2F%2FT8s%3D","updated":"2014-04-15 12:57:53.000000000","message":"i would maybe drop everything after the \u0027...comprising OpenStack clouds\u0027 but i\u0027m ok with keeping it.\n\nregarding data analysis, i believe that is outside the scope of Ceilometer.","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"615e12eb03cdbdb79ea7dd0a4bce0ab5c7d97453","unresolved":false,"context_lines":[{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"},{"line_number":97,"context_line":"    deployed at arbitrary scale, so as to provide insight over these"},{"line_number":98,"context_line":"    data to a wide variety of consumers."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"  url: https://wiki.openstack.org/wiki/Ceilometer"},{"line_number":101,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAW3%2F%2FRaQ%3D","line":98,"in_reply_to":"AAAAW3%2F%2FTsM%3D","updated":"2014-04-15 16:35:23.000000000","message":"@ildikov: agreed.","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"615e12eb03cdbdb79ea7dd0a4bce0ab5c7d97453","unresolved":false,"context_lines":[{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"},{"line_number":97,"context_line":"    deployed at arbitrary scale, so as to provide insight over these"},{"line_number":98,"context_line":"    data to a wide variety of consumers."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"  url: https://wiki.openstack.org/wiki/Ceilometer"},{"line_number":101,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAW3%2F%2FRc0%3D","line":98,"in_reply_to":"AAAAW3%2F%2FTw4%3D","updated":"2014-04-15 16:35:23.000000000","message":"@gordc: agreed.","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"615e12eb03cdbdb79ea7dd0a4bce0ab5c7d97453","unresolved":false,"context_lines":[{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"},{"line_number":97,"context_line":"    deployed at arbitrary scale, so as to provide insight over these"},{"line_number":98,"context_line":"    data to a wide variety of consumers."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"  url: https://wiki.openstack.org/wiki/Ceilometer"},{"line_number":101,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAW3%2F%2FRdU%3D","line":98,"in_reply_to":"AAAAW3%2F%2FUE8%3D","updated":"2014-04-15 16:35:23.000000000","message":"@nijaba: going by the mission statements for the other projects, I think it\u0027s a case of \"less is more\" ... i.e. the style skews towards very concise, open-ended statements.","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":7478,"name":"Nadya Shakhat","email":"nadmi4@gmail.com","username":"nprivalova"},"change_message_id":"13716bdf882400029a83e4b20de63db59a5075d3","unresolved":false,"context_lines":[{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"},{"line_number":97,"context_line":"    deployed at arbitrary scale, so as to provide insight over these"},{"line_number":98,"context_line":"    data to a wide variety of consumers."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"  url: https://wiki.openstack.org/wiki/Ceilometer"},{"line_number":101,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAW3%2F%2FT8s%3D","line":98,"in_reply_to":"AAAAW3%2F%2FUE8%3D","updated":"2014-04-15 12:39:25.000000000","message":"I\u0027m especially concerned about \u0027exposing data\u0027. We still don\u0027t have plans to add \u0027data analyze\u0027? We provide statistics, added complex queries...But still are not going to make complex analyse, aren\u0027t we? The question is not \u0027how are we going to do it?\" but \"are we going to?\"","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":7075,"name":"Swann Croiset","email":"scroiset@mirantis.com","username":"swann"},"change_message_id":"b35dc250c80c91a6c5d9c930f192f51bbe21de86","unresolved":false,"context_lines":[{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"},{"line_number":97,"context_line":"    deployed at arbitrary scale, so as to provide insight over these"},{"line_number":98,"context_line":"    data to a wide variety of consumers."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"  url: https://wiki.openstack.org/wiki/Ceilometer"},{"line_number":101,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAXH%2F%2FXvw%3D","line":98,"in_reply_to":"AAAAXH%2F%2Fdqw%3D","updated":"2014-04-22 09:05:34.000000000","message":"IMHO, alarm system should be mentioned. It\u0027s an important feature and will be enhanced in future releases IIUC and HEAT is dependant on it to bring up the OpenStack auto-scaling feature natively.\n\nOr may be Ceilometer is just a nursery before let it fly with its own wings .. ? (but I doubt because this way will be increasingly difficult/impossible when/if things in the pipe will be implemented, I think at least about bp alarm-on-notification and bp alarm-pipelines)","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"b9d8398984362ba6c2a30bb34c21866c61034794","unresolved":false,"context_lines":[{"line_number":95,"context_line":"    To collect measurements of utilization and performance indicators"},{"line_number":96,"context_line":"    for the virtual and physical resources comprising OpenStack clouds"},{"line_number":97,"context_line":"    deployed at arbitrary scale, so as to provide insight over these"},{"line_number":98,"context_line":"    data to a wide variety of consumers."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"  url: https://wiki.openstack.org/wiki/Ceilometer"},{"line_number":101,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"AAAAXH%2F%2Fdqw%3D","line":98,"in_reply_to":"AAAAXH%2F%2Fdt8%3D","updated":"2014-04-21 15:25:07.000000000","message":"Re-reading Eoghan\u0027s response to Joe, I realized my shorter version doesn\u0027t say anything about the alarms. That has become an important aspect of ceilometer\u0027s responsibilities, should it be listed?","commit_id":"5021bdfac4e6d02ce8e06d8f454471869a8c6291"},{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"d463b435f0813043a96ec4a2f6e43dec37e0974f","unresolved":false,"context_lines":[{"line_number":96,"context_line":"    To collect measurements of the consumption and performance of"},{"line_number":97,"context_line":"    the virtual and physical resources comprising deployed clouds,"},{"line_number":98,"context_line":"    triggering notifications when thresholds configured for such"},{"line_number":99,"context_line":"    metrics are crossed."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"  projects:"},{"line_number":102,"context_line":"    integrated:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"9ad9bd40_aa3d2e2d","line":99,"updated":"2014-05-06 20:23:09.000000000","message":"\"ceilometer is trying to replace nagios, right?\" ~mikal.\n\nThat is what this mission statement sounds like.\n\nAlso collecting measurements for monitoring have slightly different requirements that monitoring for billable data (http://stacktach.readthedocs.org/en/latest/usage.html). And because that was ceilometer\u0027s original goal, it would be a shame to see it not support that use case.","commit_id":"492863ee8b7b4bf6c53f299cbaad0083c021c7b1"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"da97a64689629ae5544b16475bc5a45ab8b7f6cb","unresolved":false,"context_lines":[{"line_number":96,"context_line":"    To collect measurements of the consumption and performance of"},{"line_number":97,"context_line":"    the virtual and physical resources comprising deployed clouds,"},{"line_number":98,"context_line":"    triggering notifications when thresholds configured for such"},{"line_number":99,"context_line":"    metrics are crossed."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"  projects:"},{"line_number":102,"context_line":"    integrated:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"9ad9bd40_0c4aad25","line":99,"in_reply_to":"9ad9bd40_0818e273","updated":"2014-05-07 07:18:35.000000000","message":"OK, so StackTach achieves a certain level of reliability by reconciling instantaneous notifications of resource state transitions against periodic notifications auditing resource existence.\n\nBut I don\u0027t think we should encode a particular implementation strategy in the mission statement. Rather the mission statement should be kept as general and high-level as possible IMO.\n\nHowever we could for example put more emphasis on the reliability requirement with respect to the measurements of resource consumption, e.g:\n\n  mission:\n    To collect *reliable* measurements of the consumption and performance\n    of the virtual and physical resources comprising deployed clouds,\n    triggering notifications when thresholds configured for such metrics\n    are crossed.","commit_id":"492863ee8b7b4bf6c53f299cbaad0083c021c7b1"},{"author":{"_account_id":1669,"name":"Julien Danjou","display_name":"jd","email":"julien@danjou.info","username":"jdanjou"},"change_message_id":"6d8f4916a8ddcd9815cd4551b865b4dae78d93f1","unresolved":false,"context_lines":[{"line_number":96,"context_line":"    To collect measurements of the consumption and performance of"},{"line_number":97,"context_line":"    the virtual and physical resources comprising deployed clouds,"},{"line_number":98,"context_line":"    triggering notifications when thresholds configured for such"},{"line_number":99,"context_line":"    metrics are crossed."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"  projects:"},{"line_number":102,"context_line":"    integrated:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"9ad9bd40_522fec87","line":99,"in_reply_to":"9ad9bd40_0c4aad25","updated":"2014-05-07 09:38:16.000000000","message":"I think I\u0027d also replace \"notifications\" by actions or something, since it\u0027s more close to what we do with alarming.\nThat also misses the store and provide the collected data part, which sounds important.","commit_id":"492863ee8b7b4bf6c53f299cbaad0083c021c7b1"},{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"a4a4c09a87e975c933d7e4e429933470d93d6c7d","unresolved":false,"context_lines":[{"line_number":96,"context_line":"    To collect measurements of the consumption and performance of"},{"line_number":97,"context_line":"    the virtual and physical resources comprising deployed clouds,"},{"line_number":98,"context_line":"    triggering notifications when thresholds configured for such"},{"line_number":99,"context_line":"    metrics are crossed."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"  projects:"},{"line_number":102,"context_line":"    integrated:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"9ad9bd40_0818e273","line":99,"in_reply_to":"9ad9bd40_4d567ccf","updated":"2014-05-06 21:10:00.000000000","message":"I don\u0027t think so, as billable data has additional requirements, mainly you have to be extra sure, see the link I included above). Just saying we collect consumption doesn\u0027t mean the data is reliable enough to bill off of.\n\nThat and this still sounds too much like a generic monitoring solution.","commit_id":"492863ee8b7b4bf6c53f299cbaad0083c021c7b1"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"82c1786a60523a9e186f9181eb5307547e8407e4","unresolved":false,"context_lines":[{"line_number":96,"context_line":"    To collect measurements of the consumption and performance of"},{"line_number":97,"context_line":"    the virtual and physical resources comprising deployed clouds,"},{"line_number":98,"context_line":"    triggering notifications when thresholds configured for such"},{"line_number":99,"context_line":"    metrics are crossed."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"  projects:"},{"line_number":102,"context_line":"    integrated:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"9ad9bd40_d2f69cf8","line":99,"in_reply_to":"9ad9bd40_522fec87","updated":"2014-05-07 10:01:42.000000000","message":"@jd: fair points, I\u0027ll take another crack at it.","commit_id":"492863ee8b7b4bf6c53f299cbaad0083c021c7b1"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"11b4d9aa63a82a1fd8caced7b8ba991702f7a4af","unresolved":false,"context_lines":[{"line_number":96,"context_line":"    To collect measurements of the consumption and performance of"},{"line_number":97,"context_line":"    the virtual and physical resources comprising deployed clouds,"},{"line_number":98,"context_line":"    triggering notifications when thresholds configured for such"},{"line_number":99,"context_line":"    metrics are crossed."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"  projects:"},{"line_number":102,"context_line":"    integrated:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"9ad9bd40_4d567ccf","line":99,"in_reply_to":"9ad9bd40_aa3d2e2d","updated":"2014-05-06 20:45:08.000000000","message":"@jogo: doesn\u0027t the following aspect cover the collect billable data use-case?\n\n  \"collect measurements of the consumption [...] of virtual [...] resources\"","commit_id":"492863ee8b7b4bf6c53f299cbaad0083c021c7b1"},{"author":{"_account_id":1669,"name":"Julien Danjou","display_name":"jd","email":"julien@danjou.info","username":"jdanjou"},"change_message_id":"df5d7e860ab811437eea979d4ddc310cc05d5e7d","unresolved":false,"context_lines":[{"line_number":95,"context_line":"  mission:"},{"line_number":96,"context_line":"    To reliably collect measurements of the consumption and performance"},{"line_number":97,"context_line":"    of the virtual and physical resources comprising deployed clouds,"},{"line_number":98,"context_line":"    persisting these data for subsequent aggregation, and triggering"},{"line_number":99,"context_line":"    actions when thresholds configured for such metrics are crossed."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"9ad9bd40_f20d603f","line":98,"updated":"2014-05-07 11:11:30.000000000","message":"I like that better, maybe I\u0027d say something like \"persisting these data for subsequent aggregation and retrieval\" – which indicates somehow we offer a public API to do so.","commit_id":"097d1a4651eb163acb84b25f595359d62aa8b385"},{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"81a5e99d61cd82bb3137f390523b9762d4ecd55f","unresolved":false,"context_lines":[{"line_number":93,"context_line":"  ptl : Eoghan Glynn (eglynn)"},{"line_number":94,"context_line":"  url: https://wiki.openstack.org/wiki/Ceilometer"},{"line_number":95,"context_line":"  mission:"},{"line_number":96,"context_line":"    To reliably collect measurements of the consumption and performance"},{"line_number":97,"context_line":"    of the virtual and physical resources comprising deployed clouds,"},{"line_number":98,"context_line":"    persisting these data for subsequent aggregation and retrieval,"},{"line_number":99,"context_line":"    in addition to triggering actions when thresholds configured for"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"7adec928_8fbf37d0","line":96,"updated":"2014-05-07 22:50:21.000000000","message":"\"reliably\"\n\nThat works for me, thanks","commit_id":"1ba87b7448774d5adab88897a9f5ae1df9f18164"},{"author":{"_account_id":2889,"name":"Aeva Black","email":"aeva.online@gmail.com","username":"tenbrae"},"change_message_id":"68182e7a2e292efd2451bd1a9b8ccd9d82baad10","unresolved":false,"context_lines":[{"line_number":93,"context_line":"  ptl : Eoghan Glynn (eglynn)"},{"line_number":94,"context_line":"  url: https://wiki.openstack.org/wiki/Ceilometer"},{"line_number":95,"context_line":"  mission:"},{"line_number":96,"context_line":"    To reliably collect measurements of the consumption and performance"},{"line_number":97,"context_line":"    of the virtual and physical resources comprising deployed clouds,"},{"line_number":98,"context_line":"    persisting these data for subsequent aggregation and retrieval,"},{"line_number":99,"context_line":"    in addition to triggering actions when thresholds configured for"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"7adec928_489450e8","line":96,"in_reply_to":"7adec928_249496e7","updated":"2014-05-20 20:59:23.000000000","message":"AIUI, ceilometer isn\u0027t only actively collecting measurements, it is also gathering notifications /about/ metrics which other projects collect and emit/expose. I\u0027d like to see wording to that effect as well.\n\nAlso, \"performance\" seems out of place here. I would rather say:\n\n  consumption of virtual and physical resources,\n  such as number of instances deployed and \n  amount of CPU consumed on a host.\n\nThis avoids the implication that ceilometer is measuring the performance of a specific resource, and focuses on the consumption of an available pool of resources.","commit_id":"1ba87b7448774d5adab88897a9f5ae1df9f18164"},{"author":{"_account_id":2889,"name":"Aeva Black","email":"aeva.online@gmail.com","username":"tenbrae"},"change_message_id":"c5523e4e223bfc113c90d48d2f819d788cacb230","unresolved":false,"context_lines":[{"line_number":93,"context_line":"  ptl : Eoghan Glynn (eglynn)"},{"line_number":94,"context_line":"  url: https://wiki.openstack.org/wiki/Ceilometer"},{"line_number":95,"context_line":"  mission:"},{"line_number":96,"context_line":"    To reliably collect measurements of the consumption and performance"},{"line_number":97,"context_line":"    of the virtual and physical resources comprising deployed clouds,"},{"line_number":98,"context_line":"    persisting these data for subsequent aggregation and retrieval,"},{"line_number":99,"context_line":"    in addition to triggering actions when thresholds configured for"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"3ae8d1ca_29e4580c","line":96,"in_reply_to":"7adec928_36f597cb","updated":"2014-05-27 19:34:46.000000000","message":"You both have a fair point regarding concrete examples being out of place here.\n\n@Eoghan, I like your last suggestion in that it makes clear that there are three separate functional domains:\n\n  1. collect measurements\n  2. persist and analyse measurements\n  3. initiate actions based on analysis of the measurements\n\nI\u0027d like to try to condense the various proposals that have come up on this thread into something slightly less verbose. I\u0027ve reviewed the discussion history and incorporated as much as I could into the following proposal.\n\n  To reliably collect measurements of the utilization of physical\n  and virtual resources comprising deployed clouds, persist\n  these data for subsequent retrieval and analysis, and trigger\n  actions when defined criteria are met.\n\nI\u0027ve intentionally left out the words \"performance\", \"activity\", etc, and returned to an earlier use of the word \"utilization\" -- I believe this is in line with the last suggestion that ceilometer collects \"data about how much stuff is happening\", not how fast it is happening. I\u0027ve also substituted \"criteria\" for \"thresholds\" as this is more generalizable and may include time-based criteria, not just resource-usage thresholds, and substituted \"analysis\" for \"aggregation\". Other than that, if I missed something someone feels is important along the way, it wasn\u0027t intentional.\n\nRegarding the side discussion on project scope, this isn\u0027t a vote one way or the other. I\u0027m merely attempting to clarify the wording of the mission statement.","commit_id":"1ba87b7448774d5adab88897a9f5ae1df9f18164"},{"author":{"_account_id":7478,"name":"Nadya Shakhat","email":"nadmi4@gmail.com","username":"nprivalova"},"change_message_id":"2a338f0284065d2caa14530145e3b4a1b773efa0","unresolved":false,"context_lines":[{"line_number":93,"context_line":"  ptl : Eoghan Glynn (eglynn)"},{"line_number":94,"context_line":"  url: https://wiki.openstack.org/wiki/Ceilometer"},{"line_number":95,"context_line":"  mission:"},{"line_number":96,"context_line":"    To reliably collect measurements of the consumption and performance"},{"line_number":97,"context_line":"    of the virtual and physical resources comprising deployed clouds,"},{"line_number":98,"context_line":"    persisting these data for subsequent aggregation and retrieval,"},{"line_number":99,"context_line":"    in addition to triggering actions when thresholds configured for"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"7adec928_61a03aa6","line":96,"in_reply_to":"7adec928_489450e8","updated":"2014-05-21 08:56:15.000000000","message":"IMHO, I don\u0027t like \u0027such as\u0027 here. The list of examples is not ok in mission statement. As for me (as for not-native speaker) \u0027performance\u0027 is ok here. Maybe it may be misplaced by another word (\u0027resource utilisation\u0027, not sure ) but it should be some term and not concrete example","commit_id":"1ba87b7448774d5adab88897a9f5ae1df9f18164"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"7cffe2c8d92841ddb16fe8e96723ed498dff6227","unresolved":false,"context_lines":[{"line_number":93,"context_line":"  ptl : Eoghan Glynn (eglynn)"},{"line_number":94,"context_line":"  url: https://wiki.openstack.org/wiki/Ceilometer"},{"line_number":95,"context_line":"  mission:"},{"line_number":96,"context_line":"    To reliably collect measurements of the consumption and performance"},{"line_number":97,"context_line":"    of the virtual and physical resources comprising deployed clouds,"},{"line_number":98,"context_line":"    persisting these data for subsequent aggregation and retrieval,"},{"line_number":99,"context_line":"    in addition to triggering actions when thresholds configured for"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"7adec928_36f597cb","line":96,"in_reply_to":"7adec928_61a03aa6","updated":"2014-05-21 10:17:40.000000000","message":"@devanada: I\u0027m in agreement with nprivalova, that enumerating actual use-cases isn\u0027t really an appropriate level of detail for a mission statement.\n\nHow about we address the unease about \"performance\" by sub\u0027ing in something like \"activity levels\" so as to capture the fact that we collect data about how much \"stuff\" (CPU util, disk I/O, network etc.) is happening on a resource.\n\n  To reliably collect measurements of the consumption of, and\n  activity levels on, the virtual and physical resources\n  comprising deployed clouds, persisting these data for\n  subsequent aggregation and retrieval, and triggering actions\n  when thresholds configured for such metrics are crossed.","commit_id":"1ba87b7448774d5adab88897a9f5ae1df9f18164"},{"author":{"_account_id":6699,"name":"Scott Devoid","email":"devoid@anl.gov","username":"scott-devoid"},"change_message_id":"053b7b35c59620ff71d91592504f2c149ad807f5","unresolved":false,"context_lines":[{"line_number":93,"context_line":"  ptl : Eoghan Glynn (eglynn)"},{"line_number":94,"context_line":"  url: https://wiki.openstack.org/wiki/Ceilometer"},{"line_number":95,"context_line":"  mission:"},{"line_number":96,"context_line":"    To reliably collect measurements of the consumption and performance"},{"line_number":97,"context_line":"    of the virtual and physical resources comprising deployed clouds,"},{"line_number":98,"context_line":"    persisting these data for subsequent aggregation and retrieval,"},{"line_number":99,"context_line":"    in addition to triggering actions when thresholds configured for"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"7adec928_f3651daf","line":96,"in_reply_to":"7adec928_8fbf37d0","updated":"2014-05-20 14:07:23.000000000","message":"I do not think the word \"performance\" should be used here.","commit_id":"1ba87b7448774d5adab88897a9f5ae1df9f18164"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"5b25f9bd1d48cf0345d9b921bbf172b0949eb3a3","unresolved":false,"context_lines":[{"line_number":93,"context_line":"  ptl : Eoghan Glynn (eglynn)"},{"line_number":94,"context_line":"  url: https://wiki.openstack.org/wiki/Ceilometer"},{"line_number":95,"context_line":"  mission:"},{"line_number":96,"context_line":"    To reliably collect measurements of the consumption and performance"},{"line_number":97,"context_line":"    of the virtual and physical resources comprising deployed clouds,"},{"line_number":98,"context_line":"    persisting these data for subsequent aggregation and retrieval,"},{"line_number":99,"context_line":"    in addition to triggering actions when thresholds configured for"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"7adec928_249496e7","line":96,"in_reply_to":"7adec928_f3651daf","updated":"2014-05-20 17:06:23.000000000","message":"@ Scott: can you suggest an alternative?\n\nThe intent was to capture the use-case whereby ceilometer gathers CPU utilization % metrics on instances, so that Heat autoscaling can use these to drive scaling decisions.\n\nGenerally this means ...\n* we scale up a group when the instances therein are on average running hot\n* we scale down a group when the instance therein  are on average running idle\n\nSo we\u0027re talking about how the instance are performing versus the load imposed. Or you could split hairs and say we\u0027re measuring the workload in a sense.","commit_id":"1ba87b7448774d5adab88897a9f5ae1df9f18164"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"f0bfe60f9a12c88b7e427f35a4604b13cb19e52c","unresolved":false,"context_lines":[{"line_number":96,"context_line":"    To reliably collect measurements of the consumption and performance"},{"line_number":97,"context_line":"    of the virtual and physical resources comprising deployed clouds,"},{"line_number":98,"context_line":"    persisting these data for subsequent aggregation and retrieval,"},{"line_number":99,"context_line":"    in addition to triggering actions when thresholds configured for"},{"line_number":100,"context_line":"    such metrics are crossed."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"  projects:"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"7adec928_1377e9a0","line":99,"updated":"2014-05-20 14:00:17.000000000","message":"I reckon this is a bit flowery. Consider s/in addition to/and/ to make it more straightforward.","commit_id":"1ba87b7448774d5adab88897a9f5ae1df9f18164"}]}