)]}'
{"environments/enable-stf.yaml":[{"author":{"_account_id":4264,"name":"Matthias Runge","email":"mrunge@redhat.com","username":"mrunge"},"change_message_id":"6b4263c78cd21fccc63518c0b577beb5024bf0c1","unresolved":true,"context_lines":[{"line_number":3,"context_line":"# Recommended:"},{"line_number":4,"context_line":"# - environments/metrics/ceilometer-qdr-write.yaml"},{"line_number":5,"context_line":"# - environments/metrics/collectd-qdr-write.yaml"},{"line_number":6,"context_line":"# - environments/metrics/qdr-edge-only.yaml"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"parameter_defaults:"},{"line_number":9,"context_line":"    # only send to STF, not other publishers"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"b961bc02_afca368f","line":6,"updated":"2021-06-09 20:18:33.000000000","message":"The idea behind enable-stf was to have only one environment file to pull in for enabling STF. If that changed, we should probably have a documentation note","commit_id":"a272de5c6fbb8c75b349ae21e9aa0679a8773274"},{"author":{"_account_id":4264,"name":"Matthias Runge","email":"mrunge@redhat.com","username":"mrunge"},"change_message_id":"0233a3f36081967c61117cfd2d04d8d8f6a3c56f","unresolved":true,"context_lines":[{"line_number":3,"context_line":"# Recommended:"},{"line_number":4,"context_line":"# - environments/metrics/ceilometer-qdr-write.yaml"},{"line_number":5,"context_line":"# - environments/metrics/collectd-qdr-write.yaml"},{"line_number":6,"context_line":"# - environments/metrics/qdr-edge-only.yaml"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"parameter_defaults:"},{"line_number":9,"context_line":"    # only send to STF, not other publishers"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"8003f635_30fbb9e2","line":6,"in_reply_to":"0e2a83bd_b918ecad","updated":"2021-06-10 10:18:14.000000000","message":"Since you are changing a feature in a way that users should notice, it should have a releasenote here for tht.","commit_id":"a272de5c6fbb8c75b349ae21e9aa0679a8773274"},{"author":{"_account_id":13177,"name":"Emma Foley","email":"efoley@redhat.com","username":"emma-l-foley"},"change_message_id":"4c0bf0cd0f34d2daaf2015f50f4a1694db8f9107","unresolved":true,"context_lines":[{"line_number":3,"context_line":"# Recommended:"},{"line_number":4,"context_line":"# - environments/metrics/ceilometer-qdr-write.yaml"},{"line_number":5,"context_line":"# - environments/metrics/collectd-qdr-write.yaml"},{"line_number":6,"context_line":"# - environments/metrics/qdr-edge-only.yaml"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"parameter_defaults:"},{"line_number":9,"context_line":"    # only send to STF, not other publishers"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"bdfce4dd_46bc9e8f","line":6,"in_reply_to":"2bd918af_fb9bf893","updated":"2021-06-14 13:23:31.000000000","message":"IIRC, you use reno[1]\n\nFor content, I\u0027d probably take the information that you have in the comments and include that in the note. IMHO the ``prelude`` and ``other`` section should be populated, as I don\u0027t think this fits in the other sections.\n\n[1] https://docs.openstack.org/reno/2.5.0/user/usage.html","commit_id":"a272de5c6fbb8c75b349ae21e9aa0679a8773274"},{"author":{"_account_id":7294,"name":"Leif Madsen","email":"lmadsen@redhat.com","username":"leifmadsen"},"change_message_id":"d2031edbcb5ae6298fe81d6066aa15880524f47b","unresolved":true,"context_lines":[{"line_number":3,"context_line":"# Recommended:"},{"line_number":4,"context_line":"# - environments/metrics/ceilometer-qdr-write.yaml"},{"line_number":5,"context_line":"# - environments/metrics/collectd-qdr-write.yaml"},{"line_number":6,"context_line":"# - environments/metrics/qdr-edge-only.yaml"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"parameter_defaults:"},{"line_number":9,"context_line":"    # only send to STF, not other publishers"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"2bd918af_fb9bf893","line":6,"in_reply_to":"8003f635_30fbb9e2","updated":"2021-06-10 18:17:28.000000000","message":"How is a releasenote created for that?","commit_id":"a272de5c6fbb8c75b349ae21e9aa0679a8773274"},{"author":{"_account_id":7294,"name":"Leif Madsen","email":"lmadsen@redhat.com","username":"leifmadsen"},"change_message_id":"8e53e33b52e21e303e0d4448bfd61dc95d6183b2","unresolved":true,"context_lines":[{"line_number":3,"context_line":"# Recommended:"},{"line_number":4,"context_line":"# - environments/metrics/ceilometer-qdr-write.yaml"},{"line_number":5,"context_line":"# - environments/metrics/collectd-qdr-write.yaml"},{"line_number":6,"context_line":"# - environments/metrics/qdr-edge-only.yaml"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"parameter_defaults:"},{"line_number":9,"context_line":"    # only send to STF, not other publishers"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"0e2a83bd_b918ecad","line":6,"in_reply_to":"b961bc02_afca368f","updated":"2021-06-09 21:33:01.000000000","message":"That\u0027s fine. Documentation can be adjusted, but won\u0027t be related to this PR. Documentation lives with the STF project. The idea of not including all the services here is that it will allow for set up of the data collection, but not be biased strongly towards the data collectors and transport architecture. For example, in the future this file could be used with qdr-mesh-mode and not require an enable-stf-mesh.yaml.","commit_id":"a272de5c6fbb8c75b349ae21e9aa0679a8773274"},{"author":{"_account_id":7294,"name":"Leif Madsen","email":"lmadsen@redhat.com","username":"leifmadsen"},"change_message_id":"c3f8965a873a835021c9d30e18ee64f8f2b29271","unresolved":true,"context_lines":[{"line_number":3,"context_line":"# Recommended:"},{"line_number":4,"context_line":"# - environments/metrics/ceilometer-qdr-write.yaml"},{"line_number":5,"context_line":"# - environments/metrics/collectd-qdr-write.yaml"},{"line_number":6,"context_line":"# - environments/metrics/qdr-edge-only.yaml"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"parameter_defaults:"},{"line_number":9,"context_line":"    # only send to STF, not other publishers"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"4fc9f77a_efea963f","line":6,"in_reply_to":"bdfce4dd_46bc9e8f","updated":"2021-06-14 20:36:03.000000000","message":"I\u0027ll probably just put the resources back in to this file to make this all much simpler. I\u0027m just afraid it will box us in to a corner in the future if we decide to change the deployment model (or provide flexibility around deployment models).","commit_id":"a272de5c6fbb8c75b349ae21e9aa0679a8773274"},{"author":{"_account_id":4264,"name":"Matthias Runge","email":"mrunge@redhat.com","username":"mrunge"},"change_message_id":"6b4263c78cd21fccc63518c0b577beb5024bf0c1","unresolved":true,"context_lines":[{"line_number":33,"context_line":"    - vmem"},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"    ExtraConfig:"},{"line_number":36,"context_line":"        ceilometer::agent::polling::polling_interval: 5"},{"line_number":37,"context_line":"        ceilometer::agent::polling::polling_meters:"},{"line_number":38,"context_line":"        - cpu"},{"line_number":39,"context_line":"        - disk.*"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"ef352e02_68514d51","line":36,"updated":"2021-06-09 20:18:33.000000000","message":"In connection with legacy telemetry, using such a low polling interval is a recipe for disaster. Can you make that 60 instead of 5?","commit_id":"a272de5c6fbb8c75b349ae21e9aa0679a8773274"},{"author":{"_account_id":4264,"name":"Matthias Runge","email":"mrunge@redhat.com","username":"mrunge"},"change_message_id":"0233a3f36081967c61117cfd2d04d8d8f6a3c56f","unresolved":true,"context_lines":[{"line_number":33,"context_line":"    - vmem"},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"    ExtraConfig:"},{"line_number":36,"context_line":"        ceilometer::agent::polling::polling_interval: 5"},{"line_number":37,"context_line":"        ceilometer::agent::polling::polling_meters:"},{"line_number":38,"context_line":"        - cpu"},{"line_number":39,"context_line":"        - disk.*"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"bd3facb0_cc3ad1c5","line":36,"in_reply_to":"0c81ebd0_93088951","updated":"2021-06-10 10:18:14.000000000","message":"Gnocchi can not handle 5 secs polling interval. But also collecting info from polled services may take longer. Not sure how loaded your test env. has been. While I am thinking about this, that may also be a reason for Leonids large gaps, because polling and answers are colliding. It would be worth a try to change that, or to try to see if increasing the interval has a positive effect on gaps i ceilometer metrics.","commit_id":"a272de5c6fbb8c75b349ae21e9aa0679a8773274"},{"author":{"_account_id":7294,"name":"Leif Madsen","email":"lmadsen@redhat.com","username":"leifmadsen"},"change_message_id":"d2031edbcb5ae6298fe81d6066aa15880524f47b","unresolved":true,"context_lines":[{"line_number":33,"context_line":"    - vmem"},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"    ExtraConfig:"},{"line_number":36,"context_line":"        ceilometer::agent::polling::polling_interval: 5"},{"line_number":37,"context_line":"        ceilometer::agent::polling::polling_meters:"},{"line_number":38,"context_line":"        - cpu"},{"line_number":39,"context_line":"        - disk.*"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"c96097cf_4e56a9ac","line":36,"in_reply_to":"bd3facb0_cc3ad1c5","updated":"2021-06-10 18:17:28.000000000","message":"I feel like 60 seconds is too long, so maybe I\u0027ll split it and make it 30 seconds to start. I don\u0027t know, whatever we pick here is basically just a random pick out of the air regardless.","commit_id":"a272de5c6fbb8c75b349ae21e9aa0679a8773274"},{"author":{"_account_id":7294,"name":"Leif Madsen","email":"lmadsen@redhat.com","username":"leifmadsen"},"change_message_id":"8e53e33b52e21e303e0d4448bfd61dc95d6183b2","unresolved":true,"context_lines":[{"line_number":33,"context_line":"    - vmem"},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"    ExtraConfig:"},{"line_number":36,"context_line":"        ceilometer::agent::polling::polling_interval: 5"},{"line_number":37,"context_line":"        ceilometer::agent::polling::polling_meters:"},{"line_number":38,"context_line":"        - cpu"},{"line_number":39,"context_line":"        - disk.*"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"0c81ebd0_93088951","line":36,"in_reply_to":"ef352e02_68514d51","updated":"2021-06-09 21:33:01.000000000","message":"Is it a disaster because Gnocchi couldn\u0027t deal with that level of interval, or because of other reasons? I\u0027ve been running this polling interval for a few months now and not noticed any issues on the OSP deployment, and my deployments are virtualized with limited resources.","commit_id":"a272de5c6fbb8c75b349ae21e9aa0679a8773274"},{"author":{"_account_id":4264,"name":"Matthias Runge","email":"mrunge@redhat.com","username":"mrunge"},"change_message_id":"6b4263c78cd21fccc63518c0b577beb5024bf0c1","unresolved":true,"context_lines":[{"line_number":34,"context_line":""},{"line_number":35,"context_line":"    ExtraConfig:"},{"line_number":36,"context_line":"        ceilometer::agent::polling::polling_interval: 5"},{"line_number":37,"context_line":"        ceilometer::agent::polling::polling_meters:"},{"line_number":38,"context_line":"        - cpu"},{"line_number":39,"context_line":"        - disk.*"},{"line_number":40,"context_line":"        - ip.*"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"b0558624_afd61e73","line":37,"updated":"2021-06-09 20:18:33.000000000","message":"since this should not be different from settings without stf, can we make sure these are updated for ceilometer directly, please?\n\nThere is https://github.com/openstack/puppet-ceilometer/blob/master/manifests/params.pp#L19-L50","commit_id":"a272de5c6fbb8c75b349ae21e9aa0679a8773274"},{"author":{"_account_id":7294,"name":"Leif Madsen","email":"lmadsen@redhat.com","username":"leifmadsen"},"change_message_id":"d2031edbcb5ae6298fe81d6066aa15880524f47b","unresolved":true,"context_lines":[{"line_number":34,"context_line":""},{"line_number":35,"context_line":"    ExtraConfig:"},{"line_number":36,"context_line":"        ceilometer::agent::polling::polling_interval: 5"},{"line_number":37,"context_line":"        ceilometer::agent::polling::polling_meters:"},{"line_number":38,"context_line":"        - cpu"},{"line_number":39,"context_line":"        - disk.*"},{"line_number":40,"context_line":"        - ip.*"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"489304cb_0922e4ef","line":37,"in_reply_to":"56b9bd51_f9bafa6e","updated":"2021-06-10 18:17:28.000000000","message":"Well we\u0027re already overriding defaults for functionality to support STF, and this file is specifically for enabling STF data collection, so I\u0027m not sure why this would be different from overriding different defaults.\n\nAlso changing defaults have other complications that could break systems, so backporting them will be much more complicated than keeping our specific expected configuration for STF delivery where someone opts in to that configuration rather than forcing it on everyone regardless of STF usage or not.\n\nThese values could also further change in the future as we gather more information and build dashboards etc in our external application. I\u0027m not sure I feel comfortable changing the defaults.","commit_id":"a272de5c6fbb8c75b349ae21e9aa0679a8773274"},{"author":{"_account_id":4264,"name":"Matthias Runge","email":"mrunge@redhat.com","username":"mrunge"},"change_message_id":"0233a3f36081967c61117cfd2d04d8d8f6a3c56f","unresolved":true,"context_lines":[{"line_number":34,"context_line":""},{"line_number":35,"context_line":"    ExtraConfig:"},{"line_number":36,"context_line":"        ceilometer::agent::polling::polling_interval: 5"},{"line_number":37,"context_line":"        ceilometer::agent::polling::polling_meters:"},{"line_number":38,"context_line":"        - cpu"},{"line_number":39,"context_line":"        - disk.*"},{"line_number":40,"context_line":"        - ip.*"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"56b9bd51_f9bafa6e","line":37,"in_reply_to":"5cfcc69e_7f8565aa","updated":"2021-06-10 10:18:14.000000000","message":"If there is a bugfix or a change to improve settings, they should be changed in general imho, and not just for the case of using stf. I would also prefer only one location instead of having multiple locations for configuration.","commit_id":"a272de5c6fbb8c75b349ae21e9aa0679a8773274"},{"author":{"_account_id":7294,"name":"Leif Madsen","email":"lmadsen@redhat.com","username":"leifmadsen"},"change_message_id":"8e53e33b52e21e303e0d4448bfd61dc95d6183b2","unresolved":true,"context_lines":[{"line_number":34,"context_line":""},{"line_number":35,"context_line":"    ExtraConfig:"},{"line_number":36,"context_line":"        ceilometer::agent::polling::polling_interval: 5"},{"line_number":37,"context_line":"        ceilometer::agent::polling::polling_meters:"},{"line_number":38,"context_line":"        - cpu"},{"line_number":39,"context_line":"        - disk.*"},{"line_number":40,"context_line":"        - ip.*"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5cfcc69e_7f8565aa","line":37,"in_reply_to":"b0558624_afd61e73","updated":"2021-06-09 21:33:01.000000000","message":"Why should these not be different?","commit_id":"a272de5c6fbb8c75b349ae21e9aa0679a8773274"},{"author":{"_account_id":7294,"name":"Leif Madsen","email":"lmadsen@redhat.com","username":"leifmadsen"},"change_message_id":"c3f8965a873a835021c9d30e18ee64f8f2b29271","unresolved":true,"context_lines":[{"line_number":1,"context_line":"# Enable data collection that is compatible with the STF data model."},{"line_number":2,"context_line":"# Enablement of the collectors and transport are done with separate enviroment files."},{"line_number":3,"context_line":"# Recommended:"},{"line_number":4,"context_line":"# - environments/metrics/ceilometer-qdr-write.yaml"},{"line_number":5,"context_line":"# - environments/metrics/collectd-qdr-write.yaml"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"b5f572fd_42734875","line":2,"updated":"2021-06-14 20:36:03.000000000","message":"There has been a suggestion that we should actually keep the resource_registry here instead of using existing environment files because this could potentially cause a regression and we should note that some how.\n\nPersonally I feel like no one is going to be using this unless they are using STF, and we\u0027re not referencing this file in STF documentation, so I\u0027m not sure why anyone would be using this at all currently.\n\nSo I\u0027m not really sure what to do here. Leave it how I have it now for better flexibility about the data transmission vs how we collect data (this file), or put the resources back in to be specific and avoid a (low probability?) regression?","commit_id":"e50874047c787ef4ba73e403301c0a16bd7247b7"},{"author":{"_account_id":7294,"name":"Leif Madsen","email":"lmadsen@redhat.com","username":"leifmadsen"},"change_message_id":"24cb855ca451185916a4291e7cf81db11fcfbbec","unresolved":true,"context_lines":[{"line_number":1,"context_line":"# Enable data collection that is compatible with the STF data model."},{"line_number":2,"context_line":"# Enablement of the collectors and transport are done with separate enviroment files."},{"line_number":3,"context_line":"# Recommended:"},{"line_number":4,"context_line":"# - environments/metrics/ceilometer-qdr-write.yaml"},{"line_number":5,"context_line":"# - environments/metrics/collectd-qdr-write.yaml"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"cf62b37c_18c4e4e3","line":2,"in_reply_to":"b5f572fd_42734875","updated":"2021-06-16 18:35:42.000000000","message":"I think I\u0027ve convinced myself that I\u0027m going to remove the resource_registry like I have done here and add a release note","commit_id":"e50874047c787ef4ba73e403301c0a16bd7247b7"},{"author":{"_account_id":7294,"name":"Leif Madsen","email":"lmadsen@redhat.com","username":"leifmadsen"},"change_message_id":"ed243f9d02ef563540a4403dc1df1a0154de5b83","unresolved":true,"context_lines":[{"line_number":28,"context_line":"    # to load"},{"line_number":29,"context_line":"    CollectdConnectionType: amqp1"},{"line_number":30,"context_line":"    CollectdAmqpInterval: 5"},{"line_number":31,"context_line":"    CollectdDefaultPollingInterval: 5"},{"line_number":32,"context_line":"    CollectdAmqpSendQueueLimit: 50"},{"line_number":33,"context_line":"    CollectdExtraPlugins:"},{"line_number":34,"context_line":"    - vmem"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"c95e5dd5_e8d87763","line":31,"updated":"2021-06-10 18:28:25.000000000","message":"Should we stop collecting at 5 second intervals on collectd and bump this to 30 seconds as well?","commit_id":"e50874047c787ef4ba73e403301c0a16bd7247b7"},{"author":{"_account_id":7294,"name":"Leif Madsen","email":"lmadsen@redhat.com","username":"leifmadsen"},"change_message_id":"24cb855ca451185916a4291e7cf81db11fcfbbec","unresolved":true,"context_lines":[{"line_number":28,"context_line":"    # to load"},{"line_number":29,"context_line":"    CollectdConnectionType: amqp1"},{"line_number":30,"context_line":"    CollectdAmqpInterval: 5"},{"line_number":31,"context_line":"    CollectdDefaultPollingInterval: 5"},{"line_number":32,"context_line":"    CollectdAmqpSendQueueLimit: 50"},{"line_number":33,"context_line":"    CollectdExtraPlugins:"},{"line_number":34,"context_line":"    - vmem"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"a6bf5840_beff1901","line":31,"in_reply_to":"0e5ba976_691004b7","updated":"2021-06-16 18:35:42.000000000","message":"Ack","commit_id":"e50874047c787ef4ba73e403301c0a16bd7247b7"},{"author":{"_account_id":7294,"name":"Leif Madsen","email":"lmadsen@redhat.com","username":"leifmadsen"},"change_message_id":"c3f8965a873a835021c9d30e18ee64f8f2b29271","unresolved":true,"context_lines":[{"line_number":28,"context_line":"    # to load"},{"line_number":29,"context_line":"    CollectdConnectionType: amqp1"},{"line_number":30,"context_line":"    CollectdAmqpInterval: 5"},{"line_number":31,"context_line":"    CollectdDefaultPollingInterval: 5"},{"line_number":32,"context_line":"    CollectdAmqpSendQueueLimit: 50"},{"line_number":33,"context_line":"    CollectdExtraPlugins:"},{"line_number":34,"context_line":"    - vmem"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"f2d78c31_8e7045c2","line":31,"in_reply_to":"27123745_fdca2a3d","updated":"2021-06-14 20:36:03.000000000","message":"I originally had the ceilometer polling interval at 5s, then Matthias suggested it should be 60s, so I picked something in the middle since we were just picking random numbers anyways. Suggestion was only to pick something consistent.\n\nWe could actually have a high polling frequency in collectd and only transmit every 30s (or some other random number) which we could make use of with the threshold plugin for localized events that would react faster than the full northbound loop through storage, threshold, and alert via Alertmanager, but that\u0027s a whole different discussion.\n\nSo mostly it\u0027s an open question. Only reason I thought about raising it was because we\u0027re not really doing anything with the fast sampling AMQP interval, so we could potentially scale to more nodes by reducing the number of sent messages.\n\nFor ceilometer I don\u0027t actually know what value to set this to since there hasn\u0027t been any benchmarking against ceilometer polling intervals and the possible straight it might put on rabbitmq. Since we\u0027re using sg-core everywhere as of STF 1.3, the slower polling interval on ceilometer doesn\u0027t seem to to bother sg-core even though it is scraped every 10s on the data store side.\n\nEmma did note how a release note could be created, but I\u0027m not sure how to backport release notes (or if that\u0027s a thing?). I\u0027d like to backport this all the way to Train to align with the target OSP version we\u0027re using with STF.","commit_id":"e50874047c787ef4ba73e403301c0a16bd7247b7"},{"author":{"_account_id":30893,"name":"Chris Sibbitt","email":"csibbitt@redhat.com","username":"csibbitt"},"change_message_id":"803bc4037cfed080bec165fa57e18e062b80d65c","unresolved":true,"context_lines":[{"line_number":28,"context_line":"    # to load"},{"line_number":29,"context_line":"    CollectdConnectionType: amqp1"},{"line_number":30,"context_line":"    CollectdAmqpInterval: 5"},{"line_number":31,"context_line":"    CollectdDefaultPollingInterval: 5"},{"line_number":32,"context_line":"    CollectdAmqpSendQueueLimit: 50"},{"line_number":33,"context_line":"    CollectdExtraPlugins:"},{"line_number":34,"context_line":"    - vmem"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"27123745_fdca2a3d","line":31,"in_reply_to":"c95e5dd5_e8d87763","updated":"2021-06-14 19:23:58.000000000","message":"Is there a particular reason you are suggesting that? If it\u0027s to match the ceilometer polling interval - is there a compelling reason its 30s and not 5s?","commit_id":"e50874047c787ef4ba73e403301c0a16bd7247b7"},{"author":{"_account_id":13177,"name":"Emma Foley","email":"efoley@redhat.com","username":"emma-l-foley"},"change_message_id":"844f97b5f9876fa70d346ebb4b42914144937c54","unresolved":true,"context_lines":[{"line_number":28,"context_line":"    # to load"},{"line_number":29,"context_line":"    CollectdConnectionType: amqp1"},{"line_number":30,"context_line":"    CollectdAmqpInterval: 5"},{"line_number":31,"context_line":"    CollectdDefaultPollingInterval: 5"},{"line_number":32,"context_line":"    CollectdAmqpSendQueueLimit: 50"},{"line_number":33,"context_line":"    CollectdExtraPlugins:"},{"line_number":34,"context_line":"    - vmem"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"0e5ba976_691004b7","line":31,"in_reply_to":"f2d78c31_8e7045c2","updated":"2021-06-15 12:43:39.000000000","message":"\u003e Emma did note how a release note could be created, but I\u0027m not sure how to backport release notes (or if that\u0027s a thing?). I\u0027d like to backport this all the way to Train to align with the target OSP version we\u0027re using with STF.\n\nThe release note is created as a text file that you add to the commit. Once you backport this change that will go with it.","commit_id":"e50874047c787ef4ba73e403301c0a16bd7247b7"}]}