Update patch set 1

Patch Set 1:

(3 comments)

Patch-set: 1
Attention: {"person_ident":"Gerrit User 4393 \u003c4393@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"REMOVE","reason":"\u003cGERRIT_ACCOUNT_4393\u003e replied on the change"}
Attention: {"person_ident":"Gerrit User 11604 \u003c11604@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"ADD","reason":"\u003cGERRIT_ACCOUNT_4393\u003e replied on the change"}
This commit is contained in:
Gerrit User 4393 2024-01-24 16:28:18 +00:00 committed by Gerrit Code Review
parent 623f975add
commit e9af7e64b5
1 changed files with 54 additions and 0 deletions

View File

@ -566,6 +566,24 @@
"revId": "8487cb0bd57caf9f881457b38a5e77a6e88733cd",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
"uuid": "254e47ea_25dcb9e7",
"filename": "specs/backlog/nova-dynamic-cpus.rst",
"patchSetId": 1
},
"lineNbr": 465,
"author": {
"id": 4393
},
"writtenOn": "2024-01-24T16:28:18Z",
"side": 1,
"message": "There\u0027s a race today, yes, but it\u0027s present because placement has *correctly* identified a host with capacity, but without an appropriate topology, right? Expanding the race to include not only the potential for a topology mis-fit, but also a fundamental oversubscription of a set of resources that can\u0027t actually be oversubscribed.",
"parentUuid": "0e7e25ad_eda9110d",
"revId": "8487cb0bd57caf9f881457b38a5e77a6e88733cd",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
@ -601,6 +619,24 @@
"revId": "8487cb0bd57caf9f881457b38a5e77a6e88733cd",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
"uuid": "e363e7d7_a7c0eb0b",
"filename": "specs/backlog/nova-dynamic-cpus.rst",
"patchSetId": 1
},
"lineNbr": 477,
"author": {
"id": 4393
},
"writtenOn": "2024-01-24T16:28:18Z",
"side": 1,
"message": "Okay, I think it makes it worse ;)",
"parentUuid": "66712783_15d0671f",
"revId": "8487cb0bd57caf9f881457b38a5e77a6e88733cd",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
@ -636,6 +672,24 @@
"revId": "8487cb0bd57caf9f881457b38a5e77a6e88733cd",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
"uuid": "b41154b7_116bc906",
"filename": "specs/backlog/nova-dynamic-cpus.rst",
"patchSetId": 1
},
"lineNbr": 487,
"author": {
"id": 4393
},
"writtenOn": "2024-01-24T16:28:18Z",
"side": 1,
"message": "Perhaps I\u0027m forgetting something, but where does the scheduling operation in conductor call to the compute to see if something will fit before it has been assigned/allocated? My reading of this paragraph is that we would move the actual allocation step to the compute and have conductor call to compute to have _it_ do the allocation step synchronously before conductor considers an instance schedule complete.",
"parentUuid": "56b6f216_e1180280",
"revId": "8487cb0bd57caf9f881457b38a5e77a6e88733cd",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {