| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-05-21 | |||
| 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 | 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:27 | gibi | we need to group the bw and pps resource provided by the same path under the same subtree | |
| 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) | |
| 10:12:12 | sean-k-mooney | gibi: yes it is | |
| 10:12:12 | sean-k-mooney | gibi: yes it is | |
| 10:12:18 | bauzas | br-int is a neutron notion | |
| 10:12:18 | bauzas | br-int is a neutron notion | |
| 10:12:25 | bauzas | (well, a nova-net too but...) | |
| 10:12:25 | bauzas | (well, a nova-net too but...) | |
| 10:12:40 | sean-k-mooney | its the default name of the bridge we plug all the vms into | |
| 10:12:40 | sean-k-mooney | its the default name of the bridge we plug all the vms into | |
| 10:12:59 | bauzas | the neutron-agent seems to me more understandable from a x-project perspective | |
| 10:12:59 | sean-k-mooney | its also the name used with ovn and odl for what ites workth but its technically configurable | |
| 10:12:59 | bauzas | the neutron-agent seems to me more understandable from a x-project perspective | |
| 10:12:59 | sean-k-mooney | its also the name used with ovn and odl for what ites workth but its technically configurable | |
| 10:13:18 | sean-k-mooney | ack | |
| 10:13:18 | sean-k-mooney | ack | |
| 10:13:34 | sean-k-mooney | i said it was a slight crazy idea :) | |
| 10:13:34 | sean-k-mooney | i said it was a slight crazy idea :) | |
| 10:13:58 | gibi | interestingly we don't have a similar structure for the sriov side. There we have independent PFs managed by the same agent | |
| 10:13:58 | gibi | interestingly we don't have a similar structure for the sriov side. There we have independent PFs managed by the same agent | |
| 10:14:31 | sean-k-mooney | we could if we moded indevuate pci cards | |
| 10:14:31 | sean-k-mooney | we could if we moded indevuate pci cards | |
| 10:15:01 | sean-k-mooney | eg grouped PF together if they were on the same add in card but that has limited usefullness | |
| 10:15:01 | sean-k-mooney | eg grouped PF together if they were on the same add in card but that has limited usefullness | |
| 10:15:17 | sean-k-mooney | the main one woudl be pcie bandwith really | |
| 10:15:17 | sean-k-mooney | the main one woudl be pcie bandwith really | |
| 10:15:27 | bauzas | did I open a can of worms ? | |
| 10:15:27 | bauzas | did I open a can of worms ? | |
| 10:15:35 | sean-k-mooney | no | |
| 10:15:36 | sean-k-mooney | no | |
| 10:15:57 | sean-k-mooney | well its netwrokign so yes by default | |
| 10:15:57 | sean-k-mooney | well its netwrokign so yes by default | |
| 10:16:17 | bauzas | lol | |
| 10:16:17 | bauzas | lol | |
| 10:16:37 | bauzas | just trying to wrap up things in my mind | |
| 10:16:37 | bauzas | just trying to wrap up things in my mind | |
| 10:17:19 | sean-k-mooney | perhaps a call would also help? | |
| 10:17:19 | sean-k-mooney | perhaps a call would also help? | |
| 10:17:42 | bauzas | with the minimum bandwidth model, we said "heh, we have an agent which has bridges for inter-node communication' so we are going to put resources to track on those bridges | |
| 10:17:42 | bauzas | with the minimum bandwidth model, we said "heh, we have an agent which has bridges for inter-node communication' so we are going to put resources to track on those bridges | |
| 10:18:31 | bauzas | correct ? | |
| 10:18:31 | bauzas | correct ? | |
| 10:18:32 | sean-k-mooney | yes mainly because the bandwith is an aspect of a nic which is attached to at most 1 of thoes briges | |