| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-05-21 | |||
| 10:00:16 | sean-k-mooney | similar to the physnet net which is scoped to the bridge | |
| 10:00:35 | sean-k-mooney | well the segment is mapped to a physnet | |
| 10:00:35 | sean-k-mooney | well the segment is mapped to a physnet | |
| 10:00:45 | sean-k-mooney | so perhaps | |
| 10:00:46 | sean-k-mooney | so perhaps | |
| 10:01:09 | gibi | yeah then it make more sense to share the IP with the physnet birdge | |
| 10:01:09 | gibi | yeah then it make more sense to share the IP with the physnet birdge | |
| 10:01:23 | bauzas | * bauzas was distracted by https://specs.openstack.org/openstack/neutron-specs/specs/rocky/minimum-bandwidth-allocation-placement-api.html#reporting-available-resources | |
| 10:01:30 | sean-k-mooney | oh br-tun for vxlan ectra | |
| 10:01:31 | sean-k-mooney | oh br-tun for vxlan ectra | |
| 10:01:57 | bauzas | so, we model a tree of an agent RP and the bridge RP | |
| 10:01:57 | bauzas | so, we model a tree of an agent RP and the bridge RP | |
| 10:02:08 | sean-k-mooney | yes | |
| 10:03:01 | bauzas | and since mimimum bandwidth SLAs are on the bridge, we have the egress/ingress RCs attached to the bridge RP | |
| 10:03:01 | bauzas | and since mimimum bandwidth SLAs are on the bridge, we have the egress/ingress RCs attached to the bridge RP | |
| 10:03:11 | gibi | yes | |
| 10:03:11 | gibi | yes | |
| 10:03:17 | sean-k-mooney | one of the reason for havign the agent RP was also quick lookup of the RP by using the agent uuid | |
| 10:03:17 | sean-k-mooney | one of the reason for havign the agent RP was also quick lookup of the RP by using the agent uuid | |
| 10:03:21 | bauzas | gibi: then, I don't get the need of reparenting you mentioned | |
| 10:03:21 | bauzas | gibi: then, I don't get the need of reparenting you mentioned | |
| 10:03:35 | bauzas | oh | |
| 10:03:35 | bauzas | oh | |
| 10:03:38 | bauzas | the bug | |
| 10:03:38 | bauzas | the bug | |
| 10:03:40 | sean-k-mooney | bauzas: due to a bug they were moved to the root rp | |
| 10:03:40 | sean-k-mooney | bauzas: due to a bug they were moved to the root rp | |
| 10:03:47 | lyarwood | stephenfin: https://review.opendev.org/q/topic:bug/1928063 - could you hit this again? | |
| 10:03:47 | lyarwood | stephenfin: https://review.opendev.org/q/topic:bug/1928063 - could you hit this again? | |
| 10:03:48 | gibi | agent RP -> OVS RP -> bridge RP would be the tree | |
| 10:03:48 | gibi | agent RP -> OVS RP -> bridge RP would be the tree | |
| 10:04:00 | bauzas | gotcha | |
| 10:04:00 | bauzas | gotcha | |
| 10:04:04 | gibi | and therefore the bridge would need to move under a new parent | |
| 10:04:04 | gibi | and therefore the bridge would need to move under a new parent | |
| 10:04:13 | bauzas | yeah | |
| 10:04:13 | bauzas | yeah | |
| 10:04:19 | bauzas | well | |
| 10:04:19 | bauzas | well | |
| 10:05:13 | sean-k-mooney | gibi: i still come back to could we model the invetory on br-int and perhap even remvoe the agent rp | |
| 10:05:14 | sean-k-mooney | gibi: i still come back to could we model the invetory on br-int and perhap even remvoe the agent rp | |
| 10:05:20 | bauzas | * bauzas wonders whether it's just simplier to consider that the existing agent RP we created for the purpose of the bandwidth spec is just a OVS RP | |
| 10:05:31 | sean-k-mooney | gibi: to avoid needing to move the bridge that were moved by the bug in neutorn | |
| 10:05:31 | sean-k-mooney | gibi: to avoid needing to move the bridge that were moved by the bug in neutorn | |
| 10:05:58 | bauzas | and we would defer the creation of a parent RP, be the agent, if someone comes by with a plan of providing inventories of ports | |
| 10:05:58 | bauzas | and we would defer the creation of a parent RP, be the agent, if someone comes by with a plan of providing inventories of ports | |
| 10:06:04 | gibi | bauzas: basically that was sean-k-mooney does when mentally map the agent to the ovs process | |
| 10:06:04 | gibi | bauzas: basically that was sean-k-mooney does when mentally map the agent to the ovs process | |
| 10:06:08 | sean-k-mooney | although the main problem with that is we cant use same subtree | |
| 10:06:08 | sean-k-mooney | although the main problem with that is we cant use same subtree | |
| 10:06:37 | gibi | sean-k-mooney: we need to move the bridges due to the bug as they are under the root RP now | |
| 10:06:37 | gibi | sean-k-mooney: we need to move the bridges due to the bug as they are under the root RP now | |
| 10:06:46 | sean-k-mooney | right | |
| 10:06:54 | sean-k-mooney | i was suggesting maybe we leave them there | |
| 10:06:54 | sean-k-mooney | i was suggesting maybe we leave them there | |
| 10:07:00 | gibi | sean-k-mooney: you are correct with the same_subtree issue too | |
| 10:07:00 | gibi | sean-k-mooney: you are correct with the same_subtree issue too | |
| 10:07:27 | gibi | we need to group the bw and pps resource provided by the same path under the same subtree | |
| 10:07:27 | sean-k-mooney | crazy idea... | |
| 10:07:27 | gibi | we need to group the bw and pps resource provided by the same path under the same subtree | |
| 10:07:27 | sean-k-mooney | crazy idea... | |
| 10:07:52 | sean-k-mooney | we could have the br-int under the root rp and the other bridge under br-int | |
| 10:07:52 | sean-k-mooney | we could have the br-int under the root rp and the other bridge under br-int | |
| 10:07:58 | sean-k-mooney | to model the bridge toplogy | |
| 10:07:58 | sean-k-mooney | to model the bridge toplogy | |
| 10:08:45 | gibi | or in other words rename the agent rp to be the br-int | |
| 10:08:45 | gibi | or in other words rename the agent rp to be the br-int | |
| 10:08:55 | sean-k-mooney | more or less | |
| 10:08:55 | sean-k-mooney | more or less | |
| 10:09:28 | sean-k-mooney | if you had 2 ovs in that case you woudl have 2 paralle trees of bridges | |
| 10:09:28 | sean-k-mooney | if you had 2 ovs in that case you woudl have 2 paralle trees of bridges | |
| 10:09:32 | bauzas | to be the switch | |
| 10:09:32 | bauzas | to be the switch | |
| 10:09:50 | bauzas | not the bridge | |
| 10:09:50 | bauzas | not the bridge | |
| 10:10:02 | sean-k-mooney | bauzas: no i mean the bridge | |
| 10:10:02 | sean-k-mooney | bauzas: no i mean the bridge | |
| 10:10:07 | bauzas | you lost me | |
| 10:10:07 | bauzas | you lost me | |
| 10:10:16 | sean-k-mooney | i know | |
| 10:10:16 | sean-k-mooney | i know | |
| 10:10:32 | sean-k-mooney | all data too and from the vm passes through br-int | |
| 10:10:32 | sean-k-mooney | all data too and from the vm passes through br-int | |
| 10:10:45 | sean-k-mooney | regarless of if its vm to vm on same host or vxlan or vlan | |
| 10:10:45 | sean-k-mooney | regarless of if its vm to vm on same host or vxlan or vlan | |
| 10:11:03 | sean-k-mooney | so if we model the inventory there it models the datalane capsity | |
| 10:11:03 | sean-k-mooney | so if we model the inventory there it models the datalane capsity | |
| 10:11:12 | sean-k-mooney | by puttign the other bridge under it | |
| 10:11:13 | sean-k-mooney | by puttign the other bridge under it | |
| 10:11:21 | sean-k-mooney | we can model the actully bridge toplogy | |
| 10:11:21 | sean-k-mooney | we can model the actully bridge toplogy | |
| 10:11:28 | sean-k-mooney | and make same subtree work | |
| 10:11:28 | sean-k-mooney | and make same subtree work | |
| 10:11:39 | bauzas | ah | |
| 10:11:49 | sean-k-mooney | if you want 3 ovs instaces just create a second tree | |
| 10:11:49 | sean-k-mooney | if you want 3 ovs instaces just create a second tree | |
| 10:11:57 | sean-k-mooney | fo the second set of bridges and resrouses | |
| 10:11:57 | sean-k-mooney | fo the second set of bridges and resrouses | |
| 10:12:02 | gibi | (still it is technically equivalent to rename agent RP to br-int today) | |
| 10:12:02 | gibi | (still it is technically equivalent to rename agent RP to br-int today) | |