Earlier  
Posted Nick Remark
#openstack-nova - 2021-05-21
09:55:08 elod thanks o/
09:55:08 elod thanks o/
09:55:10 bauzas sean-k-mooney: good question
09:55:10 bauzas sean-k-mooney: good question
09:55:12 lyarwood elod: looking
09:55:12 lyarwood elod: looking
09:55:43 bauzas sean-k-mooney: your last sentence on the fact that an agent RP seems irrelevant puzzles me
09:55:43 bauzas sean-k-mooney: your last sentence on the fact that an agent RP seems irrelevant puzzles me
09:56:02 bauzas sean-k-mooney: what exact resource classes do we have on the agent ?
09:56:03 bauzas sean-k-mooney: what exact resource classes do we have on the agent ?
09:56:07 bauzas the qos ones I guess ?
09:56:07 bauzas the qos ones I guess ?
09:56:16 bauzas gibi: ?
09:56:16 bauzas gibi: ?
09:56:27 sean-k-mooney it was planned to have an inventory of PORTs there at one point
09:56:28 sean-k-mooney it was planned to have an inventory of PORTs there at one point
09:56:58 gibi bauzas: pps is on the agent as per the current proposal
09:56:58 gibi bauzas: pps is on the agent as per the current proposal
09:57:09 bauzas gibi: sure, that and what else ?
09:57:09 bauzas gibi: sure, that and what else ?
09:57:10 sean-k-mooney ovs for stp reasons i belive normally has a limit of 4096 ports per bridge
09:57:10 sean-k-mooney ovs for stp reasons i belive normally has a limit of 4096 ports per bridge
09:57:31 sean-k-mooney ovs dpdk used to be 1024 and at one point that was going to reduce to 32
09:57:31 sean-k-mooney ovs dpdk used to be 1024 and at one point that was going to reduce to 32
09:57:35 gibi bauzas: I have no more plans :) but I defer to sean-k-mooney
09:57:35 gibi bauzas: I have no more plans :) but I defer to sean-k-mooney
09:58:30 sean-k-mooney bauzas: that was the orgin resouce class that the agent was coing to model. on the traits side it was hopped we would report the network types suspported
09:58:30 sean-k-mooney bauzas: that was the orgin resouce class that the agent was coing to model. on the traits side it was hopped we would report the network types suspported
09:58:31 gibi bauzas: I also imagine that the segment RP providign IP resources should be sharing the IP resource to the agent RP, but technically sharing with the compute RP is OK too I guess
09:58:31 gibi bauzas: I also imagine that the segment RP providign IP resources should be sharing the IP resource to the agent RP, but technically sharing with the compute RP is OK too I guess
09:58:46 sean-k-mooney the final case was incluing the agent RP in ^
09:58:46 sean-k-mooney the final case was incluing the agent RP in ^
09:59:06 sean-k-mooney gibi: ya the root RP woudl work
09:59:07 sean-k-mooney gibi: ya the root RP woudl work
09:59:26 sean-k-mooney althoguh
09:59:26 sean-k-mooney althoguh
09:59:30 sean-k-mooney maybe not in all cases
09:59:30 sean-k-mooney maybe not in all cases
09:59:36 sean-k-mooney if you have sriov and ovs for example
09:59:36 sean-k-mooney if you have sriov and ovs for example
09:59:46 sean-k-mooney you might want to scope it to the agent?
09:59:46 sean-k-mooney you might want to scope it to the agent?
10:00:01 gibi sean-k-mooney: I havent thought it through
10:00:01 gibi sean-k-mooney: I havent thought it through
10:00:15 gibi sean-k-mooney: maybe it belongs to the physnet bridge?
10:00:15 gibi sean-k-mooney: maybe it belongs to the physnet bridge?
10:00:16 sean-k-mooney similar to the physnet net which is scoped to the bridge
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

Earlier   Later