| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2022-05-02 | |||
| 13:10:02 | bauzas | https://github.com/openstack/nova/blob/b8cc5704558d3c08fda9db2f1bb7fecb2bcd985d/nova/virt/libvirt/driver.py#L8784 | |
| 13:10:14 | bauzas | eg. https://github.com/openstack/nova/blob/b8cc5704558d3c08fda9db2f1bb7fecb2bcd985d/nova/virt/libvirt/driver.py#L8756 | |
| 13:10:26 | bauzas | so yeah | |
| 13:11:52 | gibi | thanks | |
| 13:11:59 | bauzas | or https://github.com/openstack/nova/blob/master/nova/tests/functional/libvirt/test_vgpu.py#L362-L363 | |
| 13:12:24 | bauzas | gibi: ^ see the functest example | |
| 13:12:46 | gibi | ack | |
| 13:42:39 | artom_ | bauzas, when's the spec review day again? May 13? | |
| 13:42:59 | bauzas | artom: shit, forgot to send the email | |
| 13:43:31 | bauzas | artom: May the 10th https://meetings.opendev.org/meetings/nova/2022/nova.2022-04-26-16.00.html | |
| 13:43:54 | artom | Next Tuesday fsck me | |
| 16:08:06 | opendevreview | Balazs Gibizer proposed openstack/nova-specs master: PCI device tracking in Placement https://review.opendev.org/c/openstack/nova-specs/+/791047 | |
| 16:08:27 | gibi | sean-k-mooney, bauzas: ^^ this is a long but hopefully interesting read | |
| 16:51:42 | opendevreview | Sylvain Bauza proposed openstack/nova-specs master: Proposes to remove keypair generation https://review.opendev.org/c/openstack/nova-specs/+/840217 | |
| 16:53:07 | opendevreview | ribaudr proposed openstack/nova-specs master: libvirt: Allow Manila shares to be directly attached to instances https://review.opendev.org/c/openstack/nova-specs/+/833669 | |
| 17:04:49 | erlon | https://review.opendev.org/c/openstack/nova/+/836014 | |
| 17:04:49 | erlon | https://review.opendev.org/c/openstack/nova/+/838788 | |
| 17:04:49 | erlon | sean-k-mooney: hey Sean, can you give a look on this bugfix backport when you have a chance so I can continue the backporting throught the other releases? | |
| 19:37:05 | mnaser | sean-k-mooney: i feel like you might have some context on this -- but thoughts at isolcpus=X vs CPUAffinity+systemd? | |
| #openstack-nova - 2022-05-03 | |||
| 02:02:45 | opendevreview | melanie witt proposed openstack/nova master: Log the exception returned from a cell during API.get() https://review.opendev.org/c/openstack/nova/+/840260 | |
| 02:07:29 | opendevreview | melanie witt proposed openstack/nova master: Log the exception returned from a cell during API.get() https://review.opendev.org/c/openstack/nova/+/840260 | |
| 07:04:20 | gibi | o/ | |
| 07:46:48 | Uggla | o/ | |
| 07:50:59 | bauzas | \o | |
| 07:52:22 | opendevreview | Balazs Gibizer proposed openstack/nova-specs master: PCI device tracking in Placement https://review.opendev.org/c/openstack/nova-specs/+/791047 | |
| 07:52:46 | Uggla | gibi, bauzas if you have time, can you have a look at https://review.opendev.org/c/openstack/nova-specs/+/833669 and especially the proposed states. We discuss that with Artom and we thought that this naming is clearer. | |
| 07:53:28 | gibi | Uggla: added to my review list | |
| 07:55:16 | Uggla | thx, it will be interesting to have your thoughts, by the way I have out what we discussed regarding notifications. I hope that's clear enough. | |
| 07:58:00 | gibi | bauzas: btw, your feedback forum session got accepted too | |
| 07:58:22 | bauzas | gibi: ah ok, haven't seen the results yet | |
| 07:58:43 | gibi | you got a mail from the organizers askig for confirming the timing of the session | |
| 07:59:38 | bauzas | shit | |
| 07:59:43 | bauzas | can't see in my free.fr inbox | |
| 08:00:20 | gibi | you got it from Sarah Krawiecki | |
| 08:00:30 | gibi | with subject: OpenInfra Summit Berlin - Forum Session Accepted! | |
| 08:00:37 | bauzas | damn shit, neither in the spam folder | |
| 08:00:56 | bauzas | I know my free.fr ISP is having some problems | |
| 08:01:15 | gibi | I can forward it. should I try it to free.fr or your work mail address? | |
| 08:01:52 | bauzas | saw your reply to Sarah | |
| 08:02:40 | bauzas | confirmed, nothing got received. | |
| 08:03:10 | bauzas | I should ask Sarah whether she got a bot reply | |
| 08:03:25 | bauzas | thanks gibi for the notice | |
| 08:03:43 | gibi | OK, cool | |
| 08:09:03 | chayan | Hi everyone I recently joined the project and am looking for some beginner friendly issues to contribute to can you please help me ? | |
| 08:10:49 | kashyap | chayan: Hi, have you come acros this document yet? - https://docs.openstack.org/nova/latest/contributor/index.html | |
| 08:11:56 | kashyap | chayan: Are you familiar with Gerrit workflow? If not, you might want to check out the sandbox: https://docs.opendev.org/opendev/infra-manual/latest/sandbox.html | |
| 08:11:57 | bauzas | chayan: welcome | |
| 08:12:12 | bauzas | chayan: what kashyap said is a good starting point | |
| 08:12:28 | kashyap | And also this URL: https://docs.opendev.org/opendev/infra-manual/latest/gettingstarted.html | |
| 08:12:40 | bauzas | you would also want to familiarize with our code repository and all the managed services before going further | |
| 08:13:46 | chayan | sure, thanks kashyap and bauzas :) let me have a look | |
| 08:14:56 | bauzas | chayan: do you have any experience of OpenStack as an operator or player of its APIs, maybe ? | |
| 08:15:27 | chayan | no I do not have experience | |
| 08:16:40 | chayan | I have preliminary knowledge of python and was searching for python projects to contribute to ..... and came accross open stack | |
| 08:18:15 | bauzas | this then will be a challenging but interesting experience :) | |
| 08:19:49 | chayan | sure :) ..... Is there any design document which tells what openstack is ..... I was not able to understand much about it | |
| 08:20:02 | bauzas | chayan: as a starting point, I can't just but emphasize again the need for you to understand our tenets, including the different OpenStack service projects, and then within each of them, their distributed model | |
| 08:20:16 | bauzas | chayan: Nova is one of the many projects that OpenStack has | |
| 08:20:53 | bauzas | chayan: general onboarding docs are better if you directy look at our main OpenStack documentation and not the Nova project itself | |
| 08:21:00 | bauzas | sec, finding you some links | |
| 08:21:44 | chayan | sure | |
| 08:22:54 | bauzas | chayan: Upstream Institute is a good entrypoint https://docs.openstack.org/upstream-training/ | |
| 08:23:22 | bauzas | but this won't really dig into the architecture details | |
| 08:24:06 | bauzas | we also have a slidedeck named OpenStack 101 https://object-storage-ca-ymq-1.vexxhost.net/swift/v1/6e4619c416ff4bd19e1c087f27a43eea/www-assets-prod/marketing/OpenStack-101-Modular-Deck-1.pptx | |
| 08:25:51 | bauzas | and we also had a book which becomes a bit stale (last update is 2017) but can still be relevant for getting the overall idea https://docs.openstack.org/operations-guide/ | |
| 08:27:22 | bauzas | HTH | |
| 08:29:25 | chayan | yeah I went through the slides | |
| 08:30:01 | chayan | I think the links will be helpful... thanks | |
| 08:48:43 | songwenping_ | gibi: shall we put the pre-filter of owner_nova trait request to flavor? | |
| 08:50:06 | gibi | songwenping_: hi! sorry I don't understand the question. do you have a patch or other context I can look at? | |
| 08:52:15 | songwenping_ | oh, i'm sorry. the question is for the owner_nova trait usage spec:https://review.opendev.org/c/openstack/nova-specs/+/819510 | |
| 08:53:18 | songwenping_ | about the work item 3:Add pre-filter the trait for every Nova request group. | |
| 08:53:52 | gibi | songwenping_: ohh I see now. | |
| 08:54:35 | gibi | songwenping_: so what we really want is to add it to every request group that was create due to the flavor yes | |
| 08:55:33 | gibi | including the unnamed group containing the CPU and memory request, and including the group requesting GPU due to GPU was requested via the flavor | |
| 08:55:58 | gibi | but not including the group that was created from a neutron port, or from a cyborg resource request | |
| 08:58:28 | songwenping_ | so we should add 'owner_trait=nova' with pci_passthrough for the flavor property? | |
| 09:08:25 | gibi | I don't think the admin should add the trait manually to the flavor. I think nova should automatically add the trait to the request groups it creates | |
| 09:10:09 | songwenping_ | gibi: if flavor doesnot have the property, how do we check the compute minimum version? | |
| 09:13:22 | gibi | songwenping_: you can call service_obj.get_minimum_version_all_cells( context, ["nova-compute"]) | |
| 09:13:36 | gibi | to determine the global minimum of compute service versions | |
| 09:14:06 | gibi | but probably the current prefilter interface is not good to determine where the add the traits | |
| 09:15:12 | songwenping_ | yes, i'm wondering where to add the traits and check the version | |
| 09:17:05 | gibi | so prefilter runs on RequestSpec objects, but some of the flavor induced placement RequestGroups are create after the prefilters were run in the call of nova.scheduler.utils.ResourceRequest.from_request_spec | |
| 09:20:34 | gibi | songwenping_: you can try to think about changing ResourceRequest.from_request_spec and make RequestGroup creation explicit there | |
| 09:21:18 | songwenping_ | gibi: ok, thanks. | |
| 09:22:54 | gibi | songwenping_: currently nova.scheduler.utils.ResourceRequest._add_resource implicitly creates a new group if it is not exists | |
| 09:24:40 | gibi | songwenping_: feel free to propose a WIP patch playing with this idea and we can involve others to look at the problem and offer ideas | |
| 09:25:01 | gibi | I do thing that a pure prefilter will wont work due to some code structural challenges | |
| 09:25:38 | gibi | *think | |
| 09:25:42 | songwenping_ | ok thanks. i'll try to research. | |
| 09:25:46 | gibi | cool | |
| 11:17:53 | zigo | How comes libvirt / qemu tries to connect using the *IP ADDRESS* rather than the *HOSTNAME* which makes my PKI fail? | |
| 11:17:53 | zigo | Live Migration failure: operation failed: Failed to connect to remote libvirt URI qemu+tls://192.168.103.4/system: authentication failed: Failed to verify peer's certificate: libvirt.libvirtError: operation failed: Failed to connect to remote libvirt URI qemu+tls://192.168.103.4/system: authentication failed: Failed to verify peer's certificate | |
| 11:17:53 | zigo | Hi there! I have a problem with live migrations: | |
| 11:17:59 | zigo | Is there a way to fix that? | |
| 11:18:40 | sean-k-mooney | there is a config option for this i think | |
| 11:18:50 | zigo | sean-k-mooney: In where? In Nova ? | |
| 11:19:01 | sean-k-mooney | yes | |
| 11:19:38 | sean-k-mooney | https://docs.openstack.org/nova/latest/configuration/config.html#libvirt.live_migration_inbound_addr and https://docs.openstack.org/nova/latest/configuration/config.html#libvirt.live_migration_uri | |