)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":36998,"name":"Ilia Baikov","display_name":"Ilia Baikov","email":"ilia.baikov@ib.systems","username":"frct1"},"change_message_id":"ef41ab4263c443dfe913e99e1dcc3f7a06a69dee","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"e34e9383_a8079e86","updated":"2024-04-26 03:51:32.000000000","message":"As this is my first contribution to OpenStack i\u0027m highly waiting for review on this blueprint. Long story short: currently there is no way for vendor to provide cloud-config. I have a case when i forcibly need to tell cloud-config to update packages to new releases because of vulnerabilities. Currently this case is solved by user-data, but users are not able to pass their own user-data. That\u0027s why i decided to create open source service that allow vendors to fetch cloud-config from Consul KV but it is not working at this moment because of hard-coded metadata logics.","commit_id":"4942c9328754ffc65f9cc46aad051012df369039"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"29981506b887cff43e9620b3169da7487081c54e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"9feba269_0b14d930","updated":"2024-05-01 18:16:59.000000000","message":"-1 in its current form but we could add functionality like this or jsut document and add test coverage for the existing functionality.","commit_id":"975440ad0ee755ff065f190126ec8619b01230d6"}],"specs/2024.2/approved/dynamicjson-vendordata-cloud-config.rst":[{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"29981506b887cff43e9620b3169da7487081c54e","unresolved":true,"context_lines":[{"line_number":23,"context_line":"https://github.com/ib-systems/openstack-consul-dynamic-vendordata"},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"There is old abandoned issue:"},{"line_number":26,"context_line":"[1](https://bugs.launchpad.net/cloud-init/+bug/1841104)"},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"Use Cases"},{"line_number":29,"context_line":"---------"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9e880d2a_fcdd06c5","line":26,"updated":"2024-05-01 18:16:59.000000000","message":"so we disucss this a bit on irc and what is docujmentne in the cloudinit docs has never been supproted in nova.\n\nwith enough hacks it would be posible to force the vender data feature to work but\nas we dicussed on irc","commit_id":"975440ad0ee755ff065f190126ec8619b01230d6"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"29981506b887cff43e9620b3169da7487081c54e","unresolved":true,"context_lines":[{"line_number":49,"context_line":"if res and res.text:"},{"line_number":50,"context_line":"    # TODO(mikal): Use the Cache-Control response header to do some # sensible"},{"line_number":51,"context_line":"    form of caching here. return jsonutils.loads(res.text)"},{"line_number":52,"context_line":"```"},{"line_number":53,"context_line":""},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":6,"id":"44fb1da3_304ae4bd","line":52,"updated":"2024-05-01 18:16:59.000000000","message":"as noted on irc thisis not ap direction i think we should take.\n\n\nim porteitnally open to the idea fo modifying the \n\nvendordata_dynamic_targets config option to optionally allow speicying a respocne format to expect form the backend\n\ni belive the format that was suggested is\n\nvendordata_dynamic_targets \u003d \u0027cloud-init:string@http://10.10.10.10:8000/ocdv\n\nthis specifies that the response should be a raw/binary string.\nwe could also supprot other formats like base64 encoded strings to avoid abiguity over if the string data is utf8 encoded ectra.\n\nthat said if the backend returns a json documet containing a string to day and you name the backedn  cloud-init you shoudl be able to make this work today even if its bluring the lines between unsupprroted and technially valid.\n\n\nthe json standard define that a document that contains a single vlaue that is a vlaid json string is a valid json document \n\n\nso if the context of the respocen is lirtally\n\n```\n\"a string of data\"\n```\nnote the ```\"``` are required for ti to be a valid json document contianing a single sting value.\n\nand that string of data is a valid cloud-init document \ni.e.\n\n```\n\"#cloud-config\\npackage_upgrade: True\\npackages:\\n - htop\"\n```\n\n\nthen if you call the backend cloud-init you shoudl be able to make this work.\n\nsee the converstation starting here \n\nhttps://meetings.opendev.org/irclogs/%23openstack-nova/%23openstack-nova.2024-04-30.log.html#t2024-04-30T17:20:52\n\n\nthe respocne of the \"cloud-init\" backend need to be a binary sting containing a valid cloud-init cloud-config document as the contet fo the string will be writeen to a locathion that is later pasrsed as a binary sring\n\n\nthat is why the example in https://cloudinit.readthedocs.io/en/latest/reference/datasources/openstack.html#vendor-data\n\nescaple the new lines\n\n{\"cloud-init\": \"#cloud-config\\npackage_upgrade: True\\npackages:\\n - htop\"}\n\nwhen that get written to a file it will look like this\n\n```\n#cloud-config\npackage_upgrade: True\npackages:\n - htop\n```\n\n\nbased on the converstaion we had i think its tecnially possibel to do this today and we could isntead just add test coverave and documenation \nbut we also coudl officaly supprot","commit_id":"975440ad0ee755ff065f190126ec8619b01230d6"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"29981506b887cff43e9620b3169da7487081c54e","unresolved":true,"context_lines":[{"line_number":126,"context_line":"----------"},{"line_number":127,"context_line":""},{"line_number":128,"context_line":"- Create patch that handle `cloud-init` service name and bypass json parse"},{"line_number":129,"context_line":"  stage;"},{"line_number":130,"context_line":"- Look on members review to add fixes if needed;"},{"line_number":131,"context_line":"- Merge to other releases;"},{"line_number":132,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"0df696ac_de6447db","line":129,"updated":"2024-05-01 18:16:59.000000000","message":"we should not do that unless we agree on a way to delcare the responce format to b esomething other then json\nand it should not be speical cased based on the backend name","commit_id":"975440ad0ee755ff065f190126ec8619b01230d6"}]}