openstack
/
tripleo-specs
Code Issues Proposed changes

Update patch set 4 

Patch Set 4: Code-Review-1

(1 comment)

Patch-set: 4
Reviewer: Gerrit User 11082 <11082@4a232e18-c5a9-48ee-94c0-e04e7cca6543>
Reviewer: Gerrit User 6681 <6681@4a232e18-c5a9-48ee-94c0-e04e7cca6543>
Label: Code-Review=-1
This commit is contained in:
Gerrit User 6681 2021-07-29 12:39:05 +00:00 committed by Gerrit Code Review
parent 3e2dc778bd
commit 2663daa01a
1 changed files with 24 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
287056bd6438116ab251aaae163db764fc9a3f9a
View File

@ -70,6 +70,30 @@
"revId": "287056bd6438116ab251aaae163db764fc9a3f9a",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": true
},
{
"key": {
"uuid": "7464d3af_ca374539",
"filename": "specs/xena/tripleo-next-container-pods.rst",
"patchSetId": 4
},
"lineNbr": 136,
"author": {
"id": 6681
},
"writtenOn": "2021-07-29T12:39:05Z",
"side": 1,
"message": "That depends, but I\u0027d be pleasantly surprised if there isn\u0027t something that will break the dataplane. Neutron sidecar containers are part of the dataplane and we will need to consider how sidecars employed by neutron are impacted. There will be some differences between ML2/OVN and ML2/OVS based deployments due to how much sidecars are used. The sidecars containers are managed by neutron through wrappers, and in the case of ML2/OVS, neutron managed network namespaces are part of how it all works - so probably some thought is required here as well. ML2/OVN is a bit different but we should work out how the OVNController container would be affected.",
"parentUuid": "928121b4_cd41fb3c",
"range": {
"startLine": 136,
"startChar": 17,
"endLine": 136,
"endChar": 46
},
"revId": "287056bd6438116ab251aaae163db764fc9a3f9a",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": true
}
]
}