91 lines
4.0 KiB
Plaintext
91 lines
4.0 KiB
Plaintext
{
|
|
"comments": [
|
|
{
|
|
"key": {
|
|
"uuid": "1a6eadb0_ed2964e7",
|
|
"filename": "proposals/nova-compute-api.rst",
|
|
"patchSetId": 1
|
|
},
|
|
"lineNbr": 24,
|
|
"author": {
|
|
"id": 10511
|
|
},
|
|
"writtenOn": "2016-12-16T05:15:05Z",
|
|
"side": 1,
|
|
"message": "This is quite ambitious and I love this idea!\nBut before we do that, we might need to evaluate benefits that we can gains and efforts that are required to do that carefully.",
|
|
"range": {
|
|
"startLine": 24,
|
|
"startChar": 16,
|
|
"endLine": 24,
|
|
"endChar": 17
|
|
},
|
|
"revId": "7086083711b0c1ecdb66d62429aa986220dd2602",
|
|
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
|
|
"unresolved": false
|
|
},
|
|
{
|
|
"key": {
|
|
"uuid": "1a6eadb0_950b8523",
|
|
"filename": "proposals/nova-compute-api.rst",
|
|
"patchSetId": 1
|
|
},
|
|
"lineNbr": 30,
|
|
"author": {
|
|
"id": 2750
|
|
},
|
|
"writtenOn": "2016-12-16T12:31:48Z",
|
|
"side": 1,
|
|
"message": "For what it\u0027s worth, this has popped up as a beer conversation from time to time even inside the Nova team. Especially when there was a drumbeat about breaking out virt drivers, as the virt/compute interface is a lot more fluid (and not versioned) than the compute \u003c-\u003e rest of nova interface (noting you can run old computes with new rest of infrastructure for a few releases now).\n\nThe fact that computes report their resources to the placement-api make this a bit easier now (one less thing that nova-compute in RPC).\n\nBig questions that need answers:\n\n1) What is the communication between nova-compute \u003c-\u003e conductor in a world where nova-compute would be a dedicated effort.\n\n2) In tree vs. out of tree drivers. The nova team has been pretty clear that in tree drivers are the only supported model. On neutron more has moved out. A consolidated compute worker that needs to plug / bind things on the compute is going to need to know how to do that with all backends.\n\n3) How much more complicated is the live-migration workflow in a scenario where you can\u0027t fix things at the same time in nova-api/conductor and compute. Live migration is dicey enough as it is, so making sure that has a path would be good.\n\n\nI think the analysis step would be good regardless. Especially fresh eyes coming in, looking, asking questions, writing down the picture.",
|
|
"revId": "7086083711b0c1ecdb66d62429aa986220dd2602",
|
|
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
|
|
"unresolved": false
|
|
},
|
|
{
|
|
"key": {
|
|
"uuid": "1a6eadb0_b7b5fb7e",
|
|
"filename": "proposals/nova-compute-api.rst",
|
|
"patchSetId": 1
|
|
},
|
|
"lineNbr": 33,
|
|
"author": {
|
|
"id": 2243
|
|
},
|
|
"writtenOn": "2016-12-16T03:42:41Z",
|
|
"side": 1,
|
|
"message": "Interesting idea, I\u0027d like to seem some more elaboration on what you\u0027re thinking of here.",
|
|
"range": {
|
|
"startLine": 33,
|
|
"startChar": 0,
|
|
"endLine": 33,
|
|
"endChar": 73
|
|
},
|
|
"revId": "7086083711b0c1ecdb66d62429aa986220dd2602",
|
|
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
|
|
"unresolved": false
|
|
},
|
|
{
|
|
"key": {
|
|
"uuid": "1a6eadb0_6dd63429",
|
|
"filename": "proposals/nova-compute-api.rst",
|
|
"patchSetId": 1
|
|
},
|
|
"lineNbr": 33,
|
|
"author": {
|
|
"id": 11819
|
|
},
|
|
"writtenOn": "2016-12-16T04:59:06Z",
|
|
"side": 1,
|
|
"message": "+1 to John, at least need rough idea on what do you want to do for the nova-compute API, and how it\u0027ll interact with Cinder/Neutron back-end if you don\u0027t want to leak some detail into public API.",
|
|
"parentUuid": "1a6eadb0_b7b5fb7e",
|
|
"range": {
|
|
"startLine": 33,
|
|
"startChar": 0,
|
|
"endLine": 33,
|
|
"endChar": 73
|
|
},
|
|
"revId": "7086083711b0c1ecdb66d62429aa986220dd2602",
|
|
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
|
|
"unresolved": false
|
|
}
|
|
]
|
|
} |