openstack
/
ironic-specs
Code Issues Proposed changes

Update patch set 4 

Patch Set 4:

(1 comment)

Patch-set: 4
Attention: {"person_ident":"Gerrit User 24828 \u003c24828@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"REMOVE","reason":"\u003cGERRIT_ACCOUNT_24828\u003e replied on the change"}
This commit is contained in:
Gerrit User 24828 2024-04-24 01:14:18 +00:00 committed by Gerrit Code Review
parent 4ee152f507
commit 841c671557
1 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
6aeec08df09662a289b7ef8a59d79a3c00dd3d8d Normal file
View File

@ -0,0 +1,21 @@
{
"comments": [
{
"unresolved": true,
"key": {
"uuid": "e47ca181_a98b55dc",
"filename": "specs/approved/mercury.rst",
"patchSetId": 4
},
"lineNbr": 56,
"author": {
"id": 24828
},
"writtenOn": "2024-04-24T01:14:18Z",
"side": 1,
"message": "Hi Julia, it\u0027s an exciting idea!\nIt looks like we will have a new rpc service which is mainly responsible for the switch configuration, I wonder how it relates with the ngs?\nIf it\u0027s not function as an IPAM, do we have other mechanisms to land the network configuration like ip assignment, dhcp service, in case neutron is not available?\nAlso, in the openstack scenario, the \"network\" team may provide ml2 plugin into neutron service so they act as the sole entry to the network complexity from the ironic perspective. I wonder how the new service would cope in 😊",
"revId": "6aeec08df09662a289b7ef8a59d79a3c00dd3d8d",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
}
]
}