| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-05-21 | |||
| 09:19:28 | openstackgerrit | Qiu Fossen proposed openstack/nova-specs master: Allow migrating PMEM's data https://review.opendev.org/c/openstack/nova-specs/+/785563 | |
| 09:19:28 | openstackgerrit | Qiu Fossen proposed openstack/nova-specs master: Allow migrating PMEM's data https://review.opendev.org/c/openstack/nova-specs/+/785563 | |
| 09:22:25 | bauzas | hmmmm, YAGNI... /me googles for it | |
| 09:22:25 | bauzas | hmmmm, YAGNI... /me googles for it | |
| 09:26:53 | gibi | You arent gona needd it | |
| 09:26:53 | gibi | You arent gona needd it | |
| 09:27:10 | gibi | cdent used it a lot | |
| 09:27:10 | gibi | cdent used it a lot | |
| 09:27:47 | gibi | * gibi try not to go back to nostalgia land, yesterday was enough | |
| 09:32:31 | bauzas | gibi: OK, I think I captured the discussion | |
| 09:32:32 | bauzas | gibi: OK, I think I captured the discussion | |
| 09:33:10 | bauzas | aaaaand I don't know what to say | |
| 09:33:10 | bauzas | aaaaand I don't know what to say | |
| 09:34:12 | bauzas | the point is, I feel we are more and more designing our 'high-performance' features based on a couple of assumptions which are virt-specific | |
| 09:34:12 | bauzas | the point is, I feel we are more and more designing our 'high-performance' features based on a couple of assumptions which are virt-specific | |
| 09:34:59 | bauzas | which makes sense as we honestly only have one major configuration using a couple of knobs we know (ovs, libvirt-qemu for the least) | |
| 09:34:59 | bauzas | which makes sense as we honestly only have one major configuration using a couple of knobs we know (ovs, libvirt-qemu for the least) | |
| 09:35:29 | bauzas | but doing those shortcuts have a price to pay : we raise the barrier for newcomers | |
| 09:35:29 | bauzas | but doing those shortcuts have a price to pay : we raise the barrier for newcomers | |
| 09:36:18 | bauzas | if some company wants to develop a new neutron backend that would break the 1:1 mapping between the agent and the service itself, then this would require more work for them | |
| 09:36:18 | bauzas | if some company wants to develop a new neutron backend that would break the 1:1 mapping between the agent and the service itself, then this would require more work for them | |
| 09:36:51 | bauzas | for the moment, I'd say (except notably for QoS) that only the libvirt driver is impacted by such assumption | |
| 09:36:51 | bauzas | for the moment, I'd say (except notably for QoS) that only the libvirt driver is impacted by such assumption | |
| 09:37:24 | gibi | bauzas: isn't part of the state of the project, we are slowing down, maturing, solidifying. So we don't really expect big new things, like a new virt driver, coming | |
| 09:37:25 | gibi | bauzas: isn't part of the state of the project, we are slowing down, maturing, solidifying. So we don't really expect big new things, like a new virt driver, coming | |
| 09:37:34 | bauzas | when sean-k-mooney say "a lot of changes for nova and neutron" , this would mean for nova the libvirt driver only, as I could tell | |
| 09:37:34 | bauzas | when sean-k-mooney say "a lot of changes for nova and neutron" , this would mean for nova the libvirt driver only, as I could tell | |
| 09:37:43 | bauzas | gibi: right, I know | |
| 09:37:43 | bauzas | gibi: right, I know | |
| 09:37:54 | bauzas | gibi: and I'm pragmatic | |
| 09:37:54 | bauzas | gibi: and I'm pragmatic | |
| 09:38:02 | sean-k-mooney | bauzas: ovs is supported wiht hyperv too | |
| 09:38:02 | sean-k-mooney | bauzas: ovs is supported wiht hyperv too | |
| 09:38:14 | bauzas | but I just want everyone to feel the price of such shortcomings | |
| 09:38:14 | bauzas | but I just want everyone to feel the price of such shortcomings | |
| 09:38:50 | bauzas | but again, I'm not *that* opiniated to block on this | |
| 09:38:50 | bauzas | but again, I'm not *that* opiniated to block on this | |
| 09:38:55 | bauzas | so I'll just leave it go | |
| 09:38:55 | bauzas | so I'll just leave it go | |
| 09:39:26 | sean-k-mooney | yes it woudl require more work | |
| 09:39:26 | sean-k-mooney | yes it woudl require more work | |
| 09:39:29 | bauzas | gibi: fwiw, I wouldn't speak of a new virt driver | |
| 09:39:30 | bauzas | gibi: fwiw, I wouldn't speak of a new virt driver | |
| 09:39:44 | bauzas | gibi: that said, adding a new virt driver isn't a big deal in nova and you know | |
| 09:39:44 | bauzas | gibi: that said, adding a new virt driver isn't a big deal in nova and you know | |
| 09:40:31 | bauzas | gibi: I was more considering that some network people could think that multiple switches on an agent could be nice | |
| 09:40:31 | bauzas | gibi: I was more considering that some network people could think that multiple switches on an agent could be nice | |
| 09:40:46 | bauzas | for HA or whatever | |
| 09:40:46 | bauzas | for HA or whatever | |
| 09:41:06 | bauzas | I'm no longer surprised by the creativity of the community | |
| 09:41:06 | bauzas | I'm no longer surprised by the creativity of the community | |
| 09:41:16 | sean-k-mooney | ha | |
| 09:41:16 | sean-k-mooney | ha | |
| 09:41:50 | sean-k-mooney | last time i suggested adding a new virt driver it got shot down quicker then adding cellsv1 back | |
| 09:41:50 | sean-k-mooney | last time i suggested adding a new virt driver it got shot down quicker then adding cellsv1 back | |
| 09:42:13 | bauzas | (that being said, I'm up with sean-k-mooney on the fact that I also feel that modeling the agent itself is pointless if no resources are really offered by it) | |
| 09:42:14 | bauzas | (that being said, I'm up with sean-k-mooney on the fact that I also feel that modeling the agent itself is pointless if no resources are really offered by it) | |
| 09:42:47 | bauzas | sean-k-mooney: I was just mentioning this is *technically* easy to develop a new driver :) | |
| 09:42:47 | bauzas | sean-k-mooney: I was just mentioning this is *technically* easy to develop a new driver :) | |
| 09:42:50 | sean-k-mooney | what is the meaning of modelign the vswitch by the way | |
| 09:42:50 | sean-k-mooney | what is the meaning of modelign the vswitch by the way | |
| 09:43:13 | sean-k-mooney | give the packet procesing rate is an atribute of the datapath instnace | |
| 09:43:13 | sean-k-mooney | give the packet procesing rate is an atribute of the datapath instnace | |
| 09:43:25 | gibi | the agent RP was added originally to have a clear root RP for the agent to handle. | |
| 09:43:25 | gibi | the agent RP was added originally to have a clear root RP for the agent to handle. | |
| 09:43:27 | sean-k-mooney | and a singe ovs instance can have multipel datapath instances | |
| 09:43:27 | sean-k-mooney | and a singe ovs instance can have multipel datapath instances | |
| 09:44:04 | sean-k-mooney | yes we had form the start planned ot model packet rate on the agent rp | |
| 09:44:04 | sean-k-mooney | yes we had form the start planned ot model packet rate on the agent rp | |
| 09:44:14 | bauzas | sean-k-mooney: huh to what you say, you'd say that we could want to have multiple SLAs on different datapaths ? | |
| 09:44:14 | bauzas | sean-k-mooney: huh to what you say, you'd say that we could want to have multiple SLAs on different datapaths ? | |
| 09:44:18 | sean-k-mooney | among ohter things like port capasity | |
| 09:44:18 | sean-k-mooney | among ohter things like port capasity | |
| 09:44:43 | bauzas | either way, I don't want to bikeshed on this | |
| 09:44:43 | bauzas | either way, I don't want to bikeshed on this | |
| 09:44:49 | sean-k-mooney | bauzas: wehn you create ovs bridge you set a data path on them "system" or netdev | |
| 09:44:49 | sean-k-mooney | bauzas: wehn you create ovs bridge you set a data path on them "system" or netdev | |
| 09:44:58 | bauzas | this makes sens | |
| 09:44:58 | bauzas | this makes sens | |
| 09:45:00 | bauzas | sense* | |
| 09:45:00 | bauzas | sense* | |
| 09:45:21 | sean-k-mooney | so if you wanted you could have 1 bridge using dpdk and the other using the kernel datapath | |
| 09:45:21 | sean-k-mooney | so if you wanted you could have 1 bridge using dpdk and the other using the kernel datapath | |
| 09:45:25 | bauzas | exactly like a qemu instance I guess | |
| 09:45:25 | bauzas | exactly like a qemu instance I guess | |
| 09:45:30 | sean-k-mooney | and they woudl have indepent capsities | |
| 09:45:30 | sean-k-mooney | and they woudl have indepent capsities | |
| 09:45:47 | bauzas | yeah, i can imagine that | |
| 09:45:47 | bauzas | yeah, i can imagine that | |
| 09:46:04 | bauzas | exactly like you could have a nova-compute using different qemu endpoints | |
| 09:46:04 | bauzas | exactly like you could have a nova-compute using different qemu endpoints | |
| 09:46:05 | sean-k-mooney | there woudl still only be one ovs-vsiwwtch process in that case | |
| 09:46:05 | sean-k-mooney | there woudl still only be one ovs-vsiwwtch process in that case | |
| 09:46:27 | bauzas | but in this case, this would be easier to have one n-cpu per qemu endpoint, right? | |
| 09:46:27 | bauzas | but in this case, this would be easier to have one n-cpu per qemu endpoint, right? | |
| 09:46:40 | sean-k-mooney | yes it would | |
| 09:46:40 | sean-k-mooney | yes it would | |
| 09:46:56 | sean-k-mooney | if you wnated to run ovs and ovs-dpdk on the same host | |
| 09:46:56 | sean-k-mooney | if you wnated to run ovs and ovs-dpdk on the same host | |
| 09:47:07 | bauzas | okay, so making an analogy | |