nova-specs/8162e70bd3b15f6ba34b5c661f8...

110 lines
6.3 KiB
Plaintext

{
"comments": [
{
"unresolved": true,
"key": {
"uuid": "2dd0d081_fb7a2c7f",
"filename": "specs/2024.2/approved/update-userdata.rst",
"patchSetId": 7
},
"lineNbr": 48,
"author": {
"id": 2271
},
"writtenOn": "2024-04-05T23:02:25Z",
"side": 1,
"message": "To my current understanding, cloud-init only expects to run once on first boot -- it records that it has run and unless the instance \"changes\" (changed UUID etc) it wont reconfigure the instance. So if the user-data is updated, what would trigger cloud-init to rerun, especially if a reboot is not initiated as part of the process?",
"revId": "8162e70bd3b15f6ba34b5c661f867480df71ca76",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
"uuid": "d0580207_6ba29bc9",
"filename": "specs/2024.2/approved/update-userdata.rst",
"patchSetId": 7
},
"lineNbr": 48,
"author": {
"id": 11604
},
"writtenOn": "2024-04-07T05:29:55Z",
"side": 1,
"message": "we disccused this in the past.\n\ni dont recally the deatails but apprenntly you can dconfigure cloud-init to run some configuration on every boot vs first boot.\n\nits been a few years at this point to the details are fuzzy but for those not using config drive espically we anted to decouple the reboot form the updating of the userdata avaiable form the metadata api so that the user could initia the reboot seperatly when convienent to do so or configure there workload to pool for updates asycronoshly vai another means.\n\n\nif i recall correctly the orginal user didnt use config drive an only used the metadat api but obviouly we would want any solution to be functionally equivlent even if it was delayed in the config drive case.",
"parentUuid": "2dd0d081_fb7a2c7f",
"revId": "8162e70bd3b15f6ba34b5c661f867480df71ca76",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
"uuid": "23d9761b_844b089b",
"filename": "specs/2024.2/approved/update-userdata.rst",
"patchSetId": 7
},
"lineNbr": 48,
"author": {
"id": 2271
},
"writtenOn": "2024-04-08T04:38:27Z",
"side": 1,
"message": "Its also possible to read this metadata with something other than cloud-init, but the reality is that _most_ people simply use cloud-init. I think if we\u0027re going to add things which can change post first boot, it would also be reasonable to ask if the cloud-init team has been consulted or informed of the plan.",
"parentUuid": "d0580207_6ba29bc9",
"revId": "8162e70bd3b15f6ba34b5c661f867480df71ca76",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
"uuid": "0e2a0a6d_40a4684e",
"filename": "specs/2024.2/approved/update-userdata.rst",
"patchSetId": 7
},
"lineNbr": 66,
"author": {
"id": 2271
},
"writtenOn": "2024-04-05T23:02:25Z",
"side": 1,
"message": "Both the metadata server and the config drive are versioned. Are you proposing bumping the version of the openstack metadata in order to indicate to clients that this functionality is now available? That\u0027s happened a bunch in the past, so it should be a relatively well trod path, but its still important I think.",
"revId": "8162e70bd3b15f6ba34b5c661f867480df71ca76",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
"uuid": "a5c92e0a_85d1217e",
"filename": "specs/2024.2/approved/update-userdata.rst",
"patchSetId": 7
},
"lineNbr": 66,
"author": {
"id": 11604
},
"writtenOn": "2024-04-07T05:29:55Z",
"side": 1,
"message": "we have not modifed the metadata in a long time.\nim not sure if we have continued bumping the version in the meatadata the last few time we did change them or not.\n\nthe version we have however is not a microverions \nwe only changed it in the past if we added new files/fileds or change the over all layout.\n\ni dont think we have bumped it for behaivoral change before.\n\nim not nessisaly agains that but i dont think we have an api contract today that say we should do that.\n\nfor example at one point we added the ablity for the admin passwored to be set once by the instance writhing back to the metadata api when cloudbase-init generated a password on windwos. i dont know if we singled that via a version bump or not\n\nnon of the api versioning rule we have for the main api apply to the metadata api\nso other then inspcating t he data based directory structure for specific files and there content there isnt really any client discorvableiyt built into the metadata api content.",
"parentUuid": "0e2a0a6d_40a4684e",
"revId": "8162e70bd3b15f6ba34b5c661f867480df71ca76",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
"uuid": "e4c67c1a_5aa94712",
"filename": "specs/2024.2/approved/update-userdata.rst",
"patchSetId": 7
},
"lineNbr": 66,
"author": {
"id": 2271
},
"writtenOn": "2024-04-08T04:38:27Z",
"side": 1,
"message": "Here are the previous versions:\n\nFOLSOM \u003d \u00272012-08-10\u0027\nGRIZZLY \u003d \u00272013-04-04\u0027\nHAVANA \u003d \u00272013-10-17\u0027\nLIBERTY \u003d \u00272015-10-15\u0027\nNEWTON_ONE \u003d \u00272016-06-30\u0027\nNEWTON_TWO \u003d \u00272016-10-06\u0027\nOCATA \u003d \u00272017-02-22\u0027\nROCKY \u003d \u00272018-08-27\u0027\nVICTORIA \u003d \u00272020-10-14\u0027\n\nWe certainly _used_ to bump the version when we changed something. I don\u0027t see any changes since commit 916ffddca8d41daa367cf819e14827cf4b4180a5 (when the Victoria version was added) that weren\u0027t internal only with the exception of perhaps 1bf45c47205057801129dc20153de0a98d9c4e08.\n\nThat is, these have previously been versioned. Maybe one change has escaped versioning, but that doesn\u0027t seem like a strong reason to give up on versioning entirely.",
"parentUuid": "a5c92e0a_85d1217e",
"revId": "8162e70bd3b15f6ba34b5c661f867480df71ca76",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
}
]
}