Earlier  
Posted Nick Remark
#openstack-nova - 2021-05-11
10:31:59 bauzas sean-k-mooney: we try to reboot the instance first
10:32:09 bauzas and then we also try to restart it
10:32:09 bauzas and then we also try to restart it
10:32:19 bauzas *before we plug the vifs*
10:32:19 bauzas *before we plug the vifs*
10:32:27 sean-k-mooney we might be trying to plug wtice but i dont see any reason not to plug first
10:32:27 sean-k-mooney we might be trying to plug wtice but i dont see any reason not to plug first
10:32:32 sean-k-mooney that would be more correct i think
10:32:32 sean-k-mooney that would be more correct i think
10:32:55 bauzas ok, I'm asking this because I'd prefer to pass the allocations to the new driver method I created *before* the two above calls
10:32:55 bauzas ok, I'm asking this because I'd prefer to pass the allocations to the new driver method I created *before* the two above calls
10:33:23 sean-k-mooney ya i also think that proably makes sense
10:33:23 sean-k-mooney ya i also think that proably makes sense
10:33:29 bauzas if you reboot the instance with not the mdevs, then you got a qemu exception
10:33:29 bauzas if you reboot the instance with not the mdevs, then you got a qemu exception
10:33:50 sean-k-mooney yep so it should be create mdevs then plug vifs then reboot
10:33:51 sean-k-mooney yep so it should be create mdevs then plug vifs then reboot
10:33:53 bauzas * bauzas also needs to find a vGPU env, btw. :)
10:35:14 sean-k-mooney maybe see if you can borrow one form james if they are not using it for qe tests
10:35:14 sean-k-mooney maybe see if you can borrow one form james if they are not using it for qe tests
10:36:16 sean-k-mooney bauzas: so ya just checked the code
10:36:16 sean-k-mooney bauzas: so ya just checked the code
10:36:30 sean-k-mooney that is litgimatly a bug that plug vifs is after the vm start
10:36:30 sean-k-mooney that is litgimatly a bug that plug vifs is after the vm start
10:36:52 sean-k-mooney the reboot code path is assumign its done before
10:36:52 sean-k-mooney the reboot code path is assumign its done before
10:37:10 bauzas kk
10:37:10 bauzas kk
10:37:24 sean-k-mooney it wont break things entirly in that we will fix it after but we should move it earlier
10:37:24 sean-k-mooney it wont break things entirly in that we will fix it after but we should move it earlier
10:37:25 bauzas ok, so I'll write the code
10:37:25 bauzas ok, so I'll write the code
10:37:41 bauzas sean-k-mooney: do you want me to write the bug report for the vifs one ?
10:37:41 bauzas sean-k-mooney: do you want me to write the bug report for the vifs one ?
10:37:43 bauzas or you ?
10:37:43 bauzas or you ?
10:38:04 sean-k-mooney hehe i mean if you feel like it go for it
10:38:04 sean-k-mooney hehe i mean if you feel like it go for it
10:38:17 sean-k-mooney you can point to https://github.com/openstack/nova/blob/7953c0197d1a4466cb5b78070d47626c92f9db6e/nova/virt/libvirt/driver.py#L3773-L3775
10:38:17 sean-k-mooney you can point to https://github.com/openstack/nova/blob/7953c0197d1a4466cb5b78070d47626c92f9db6e/nova/virt/libvirt/driver.py#L3773-L3775
10:38:29 sean-k-mooney as evidnce that we expect ti to be alredy plugged
10:38:29 sean-k-mooney as evidnce that we expect ti to be alredy plugged
10:38:31 bauzas ok, gotta go lunching but I'll write it later
10:38:31 bauzas ok, gotta go lunching but I'll write it later
10:38:49 bauzas * bauzas already has a shit ton of open tabs
10:39:07 bauzas hopefully, my new laptop would arrive...
10:39:07 bauzas hopefully, my new laptop would arrive...
10:39:29 sean-k-mooney did you get a ship date or just hoping its on its way
10:39:29 sean-k-mooney did you get a ship date or just hoping its on its way
10:39:37 bauzas I asked
10:39:37 bauzas I asked
10:39:58 bauzas "I just checked with our vendor and the laptop is currently in the status 'Allocated', which means that it should be sent soon (in a matter of days)."
10:39:58 bauzas "I just checked with our vendor and the laptop is currently in the status 'Allocated', which means that it should be sent soon (in a matter of days)."
10:40:20 bauzas (I know we are in an upstream channel, but that's not a secret phrase ;) )
10:40:20 bauzas (I know we are in an upstream channel, but that's not a secret phrase ;) )
10:40:44 bauzas this was 7 days ago, so I'm not against a delivery surprise
10:40:44 bauzas this was 7 days ago, so I'm not against a delivery surprise
10:41:28 bauzas context : CPU shortages on vendors, leaving my refreshment order open for 6 months, craziness of the post-covid economy
10:41:28 bauzas context : CPU shortages on vendors, leaving my refreshment order open for 6 months, craziness of the post-covid economy
10:42:13 bauzas (also the fact that most of the vendors are fabless...)
10:42:13 bauzas (also the fact that most of the vendors are fabless...)
10:45:47 sean-k-mooney well hopefully you will get it sooner then your broadband upgrade
10:45:47 sean-k-mooney well hopefully you will get it sooner then your broadband upgrade
11:06:27 openstackgerrit Lee Yarwood proposed openstack/nova master: WIP compute: Persist image id within the system_metadata of an instance https://review.opendev.org/c/openstack/nova/+/790659
11:06:28 openstackgerrit Lee Yarwood proposed openstack/nova master: WIP hardware: Use image_meta.id within get_mem_encryption_constraint https://review.opendev.org/c/openstack/nova/+/790660
11:06:29 openstack bug 1928063 in OpenStack Compute (nova) "SEV enabled instance unable to hard reboot" [Undecided,New] https://launchpad.net/bugs/1928063 - Assigned to Lee Yarwood (lyarwood)
11:06:29 openstackgerrit Lee Yarwood proposed openstack/nova master: WIP hardware: Use image_meta.id within get_mem_encryption_constraint https://review.opendev.org/c/openstack/nova/+/790660
11:06:29 openstackgerrit Lee Yarwood proposed openstack/nova master: WIP compute: Persist image id within the system_metadata of an instance https://review.opendev.org/c/openstack/nova/+/790659
11:06:29 openstack bug 1928063 in OpenStack Compute (nova) "SEV enabled instance unable to hard reboot" [Undecided,New] https://launchpad.net/bugs/1928063 - Assigned to Lee Yarwood (lyarwood)
11:06:29 openstackgerrit Lee Yarwood proposed openstack/nova master: Add regression test for bug #1928063 https://review.opendev.org/c/openstack/nova/+/790658
11:07:03 lyarwood stephenfin: ack I'll review the mypy stuff this week, apologies for not getting to it before PTO
11:07:03 lyarwood stephenfin: ack I'll review the mypy stuff this week, apologies for not getting to it before PTO
11:14:10 stephenfin ta
11:14:10 stephenfin ta
11:38:44 gibi sean-k-mooney: thanks for trying to cover some part of the ELK stack.
11:38:44 gibi sean-k-mooney: thanks for trying to cover some part of the ELK stack.
11:44:12 sean-k-mooney gibi: ill be reinstalling my home system later in the week so ill try and see if i can get something working at the weekend
11:44:12 sean-k-mooney gibi: ill be reinstalling my home system later in the week so ill try and see if i can get something working at the weekend
11:45:31 sean-k-mooney im hoping i can just use kolla's supprot for deploying elk or efk technically to maintian the stack
11:45:31 sean-k-mooney im hoping i can just use kolla's supprot for deploying elk or efk technically to maintian the stack
11:46:10 sean-k-mooney what i need to figure out is what is the best way to upload the logs to it form the upstream jobs
11:46:10 sean-k-mooney what i need to figure out is what is the best way to upload the logs to it form the upstream jobs
11:49:02 sean-k-mooney im thinking of trying the http plugin for fluentd to submit the logs with basically curl.
11:49:02 sean-k-mooney im thinking of trying the http plugin for fluentd to submit the logs with basically curl.
11:49:04 sean-k-mooney https://docs.fluentd.org/input/http
11:49:04 sean-k-mooney https://docs.fluentd.org/input/http
12:19:11 admin0 hi guys .. is it possible to add bus and slot on pci_passthrough alias whitelist ?
12:19:11 admin0 hi guys .. is it possible to add bus and slot on pci_passthrough alias whitelist ?
12:19:22 admin0 alias = { "vendor_id":"8086", "product_id":"154d", "device_type":"type-PF", "name":"a1", "numa_policy":"preferred" }
12:19:22 admin0 alias = { "vendor_id":"8086", "product_id":"154d", "device_type":"type-PF", "name":"a1", "numa_policy":"preferred" }
12:19:41 admin0 if there is multiple network-cards or multiple pci cards or the same vendor and product-id , how do I differencitate it
12:19:41 admin0 if there is multiple network-cards or multiple pci cards or the same vendor and product-id , how do I differencitate it
12:22:57 admin0 in whitelist we can specify the bus slot and function .. but how to do it in alias ?
12:22:57 admin0 in whitelist we can specify the bus slot and function .. but how to do it in alias ?
12:23:09 admin0 https://docs.openstack.org/nova/latest/configuration/config.html#pci.alias -- does not show this feature
12:23:09 admin0 https://docs.openstack.org/nova/latest/configuration/config.html#pci.alias -- does not show this feature
12:27:58 admin0 the use case is this ... say i have 4 devices, and i want to pick device 1 and 4 for vm1 and 2 and 3 for vm2 .. what happens is since i cannot pass the bus/slot on alias, it picks up device 1 and 2 for first vm and 3 and 4 for 2nd vm .. if its possible to pass the exact in alias somehow, it might solve that issue
12:27:59 admin0 the use case is this ... say i have 4 devices, and i want to pick device 1 and 4 for vm1 and 2 and 3 for vm2 .. what happens is since i cannot pass the bus/slot on alias, it picks up device 1 and 2 for first vm and 3 and 4 for 2nd vm .. if its possible to pass the exact in alias somehow, it might solve that issue
12:30:32 sean-k-mooney admin0: no
12:30:32 sean-k-mooney admin0: no

Earlier   Later