| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-11-04 | |||
| 15:25:44 | sean-k-mooney | https://github.com/openstack/nova/blob/fded762f4df26ff5706438a66da33ff966f833c6/nova/virt/ironic/driver.py#L1492-L1525 | |
| 15:26:10 | sean-k-mooney | we are just callign the node.vif_attach api | |
| 15:26:14 | TheJulia | sean-k-mooney: it must because of a security lifecycle must be enforced | |
| 15:26:19 | sean-k-mooney | so this looks like there is an existing race | |
| 15:26:23 | TheJulia | and it knows the state of the lifecycle | |
| 15:27:25 | EugenMayer | Anybody in here got novnc working with kolla when using TLS? TLS is working on all sub-systems except when using TLS. lyarwood it seems like they use a haproxy (i got told) which does the SSL offloading, which might be the reason it is not configured. But this would not explain the error message | |
| 15:27:46 | opendevreview | Balazs Gibizer proposed openstack/nova master: Add a WA flag waiting for vif-plugged event during reboot https://review.opendev.org/c/openstack/nova/+/813419 | |
| 15:29:47 | TheJulia | sean-k-mooney: on start, but if the vif recrods are already on file, on start it doesn't matter, the nova-compute spins for quite a long time. | |
| 15:30:02 | TheJulia | for running state, that is a separate path and that has been the case for a while, I think. | |
| 15:50:42 | TheJulia | so I think I grok sean-k-mooney's concerns, and just to be on the safe side, I'll go change my "test nova-y tings patch in the ironic repo to pull that vif plug patch in and just make sure that it passes happily again. I believe it did so before, but there is the BFV use case which is a little different | |
| 15:54:15 | opendevreview | Alexey Stupnikov proposed openstack/nova master: WIP: Test aborting queued live migration https://review.opendev.org/c/openstack/nova/+/776250 | |
| 15:55:03 | TheJulia | artom: that hash ring handling wip seems to work, which is a good sign. Likely just need to go see if the devstack plugin forces a rebalance... and maybe make it force a rebalance :) | |
| 15:55:51 | artom | TheJulia, yeah, I need to look at it again and properly wrap my head around it | |
| 15:57:10 | TheJulia | artom: yeah, a little different by just reconciling "what is running/active" versuse explicit record checks for each instance, but I'd hate to trigger a few thousand extra DB queries upon rebalance | |
| 15:59:04 | TheJulia | changed https://review.opendev.org/c/openstack/ironic/+/813264 to run the vif plug change | |
| 15:59:26 | TheJulia | sean-k-mooney: ^^ if the ironic bfv job passes, I suspect we're safe and happy for the time being | |
| 16:03:16 | sean-k-mooney | ack tahnks | |
| 16:27:01 | opendevreview | Balazs Gibizer proposed openstack/nova master: Remove SESSION_CONFIGURED global from DB fixture https://review.opendev.org/c/openstack/nova/+/815689 | |
| 16:27:01 | opendevreview | Balazs Gibizer proposed openstack/nova master: Refactor Database fixture https://review.opendev.org/c/openstack/nova/+/815690 | |
| 16:29:50 | opendevreview | Balazs Gibizer proposed openstack/nova master: Fix interference in db unit test https://review.opendev.org/c/openstack/nova/+/814735 | |
| 16:32:36 | melwitt | gibi: just read your comments, I might be wrong but if I am then I don't understand why it's needed. I'll look at it some more | |
| 16:33:19 | gibi | melwitt: I followed your suggestion and things are still passing, so I think you are right | |
| 16:33:49 | melwitt | oh ok | |
| 16:34:07 | gibi | so you were right that I don't need to patch the per connection case | |
| 16:34:34 | melwitt | ack | |
| 18:00:55 | EugenMayer | lyarwood FYI - kolla supports tls for novnc but uses a haproxy as SSL offloaded and LB in front of it. My issues was an internal vs external VIP IP. So kolla has support for it | |
| 18:01:19 | lyarwood | cool cool | |
| 18:34:34 | opendevreview | Lee Yarwood proposed openstack/nova master: nova-next: Deploy noVNC from source instead of packages https://review.opendev.org/c/openstack/nova/+/816738 | |
| 18:41:56 | opendevreview | Lee Yarwood proposed openstack/nova master: nova-next: Drop NOVA_USE_SERVICE_TOKEN from subnode https://review.opendev.org/c/openstack/nova/+/816740 | |
| 20:31:31 | opendevreview | Gustavo Santos proposed openstack/nova master: Reattach mdevs to guest on resume https://review.opendev.org/c/openstack/nova/+/815373 | |
| 22:07:36 | opendevreview | sean mooney proposed openstack/nova master: [WIP] Add extra tests for pinning with partial siblings https://review.opendev.org/c/openstack/nova/+/816758 | |
| 23:30:48 | opendevreview | Merged openstack/nova stable/wallaby: Store old_flavor already on source host during resize https://review.opendev.org/c/openstack/nova/+/810913 | |
| #openstack-nova - 2021-11-05 | |||
| 01:46:46 | opendevreview | Brin Zhang proposed openstack/nova master: Replaces tenant_id with project_id from List/Update Servers APIs https://review.opendev.org/c/openstack/nova/+/764292 | |
| 02:01:38 | opendevreview | Brin Zhang proposed openstack/nova master: Replaces tenant_id with project_id from List/Update Servers APIs https://review.opendev.org/c/openstack/nova/+/764292 | |
| 02:12:37 | opendevreview | Brin Zhang proposed openstack/nova master: [Trival] Fix wrong microversion in TestClass name https://review.opendev.org/c/openstack/nova/+/816778 | |
| 02:47:30 | opendevreview | Brin Zhang proposed openstack/nova master: Replace all_tenants with all_projects in List Server APIs https://review.opendev.org/c/openstack/nova/+/765311 | |
| 02:58:25 | opendevreview | Brin Zhang proposed openstack/nova master: Replaces tenant_id with project_id from Rebuild Server API https://review.opendev.org/c/openstack/nova/+/766380 | |
| 05:59:25 | opendevreview | Brin Zhang proposed openstack/nova master: Replaces tenant_id with project_id from List/Update Servers APIs https://review.opendev.org/c/openstack/nova/+/764292 | |
| 05:59:26 | opendevreview | Brin Zhang proposed openstack/nova master: Replace all_tenants with all_projects in List Server APIs https://review.opendev.org/c/openstack/nova/+/765311 | |
| 05:59:26 | opendevreview | Brin Zhang proposed openstack/nova master: Replaces tenant_id with project_id from Rebuild Server API https://review.opendev.org/c/openstack/nova/+/766380 | |
| 07:33:22 | kashyap | frickler: Morning: https://listman.redhat.com/archives/libvir-list/2021-November/msg00171.html | |
| 08:17:50 | frickler | kashyap: nice, thx for that. we did change the bullseye job to use swap for now, that seems rather stable and is still faster than the serial variant | |
| 08:19:01 | kashyap | No problem; I think the series will be respun to use -accel for accelerator in general. (https://gitlab.com/libvirt/libvirt/-/issues/233) | |
| 09:46:41 | gibi | elodilles: hi! you can upgrade your vote ;) on the victoria part of https://review.opendev.org/q/topic:bug/1944759 as the wallaby patches have landed | |
| 10:00:33 | elodilles | gibi: \o/ | |
| 10:00:37 | elodilles | gibi: done | |
| 10:00:41 | gibi | thanks a lot | |
| 10:00:54 | elodilles | no problem :) | |
| 10:10:50 | frickler | kashyap: already there. nice monster patch updating umpteen tests ;) | |
| 10:11:35 | kashyap | frickler: Yep, v2 (from Michal) is large because of the test noise - https://listman.redhat.com/archives/libvir-list/2021-November/msg00194.html | |
| 10:11:59 | kashyap | frickler: I'm just wiring up the XML config class in Nova. And writing a commit message | |
| 10:45:39 | EugenMayer | is there really no better way or even usual default to start vms after a node reboot then adding resume_guests_state_on_host_boot to the nova conf and/or using virsh to add the autostart flag? There is no GUI nor nova API flag (openstack server create) flag to automatically create an instance with autostart? | |
| 10:50:55 | opendevreview | Balazs Gibizer proposed openstack/nova master: Use ReplaceEngineFacade fixture https://review.opendev.org/c/openstack/nova/+/816820 | |
| 10:52:08 | opendevreview | Balazs Gibizer proposed openstack/nova master: Fix interference in db unit test https://review.opendev.org/c/openstack/nova/+/814735 | |
| 10:53:39 | gibi | EugenMayer: I think nova considers such automatic recovery as mostly outside of nova scope. An external service can detect the compute host failre and can implement automatic evacuation for some VMs while for others it can wait for the compute host recovery and implement auto startup. | |
| 10:55:17 | EugenMayer | gibi interesting. I understand that this is an good option, but it would be somewhat nice to have this as a possible build in default to, or? | |
| 10:55:53 | EugenMayer | but i understand, if you run hundreds of VMs the strategy to recover could be more suffistacted | |
| 10:56:04 | gibi | EugenMayer: OpenStack has tools to build such behavior top of nova. I.e. https://docs.openstack.org/self-healing-sig/latest/use-cases/heat-mistral-aodh.html | |
| 10:56:56 | gibi | the use case is vaild, I just don't think the implementation needs to be inside nova | |
| 10:58:00 | EugenMayer | thank you for that article, will look into that. | |
| 11:07:23 | opendevreview | Lee Yarwood proposed openstack/nova master: nova-next: Deploy noVNC from source instead of packages https://review.opendev.org/c/openstack/nova/+/816738 | |
| 11:09:56 | opendevreview | Kashyap Chamarthy proposed openstack/nova master: libvirt: Introduce config classes for QEMU's "tb-cache" https://review.opendev.org/c/openstack/nova/+/816823 | |
| 11:10:27 | kashyap | Huh, plural; it's a single class | |
| 11:12:05 | opendevreview | Kashyap Chamarthy proposed openstack/nova master: libvirt: Introduce config class for QEMU's "tb-cache" https://review.opendev.org/c/openstack/nova/+/816823 | |
| 11:14:10 | kashyap | Not sure if the above WIP requires a bp yet ... but I filed one prememptively (https://blueprints.launchpad.net/nova/+spec/control-qemu-tb-cache) | |
| 11:35:54 | gibi | kashyap: I think a specless bp is enough | |
| 11:36:44 | kashyap | gibi: Cool; guessed as much. :) | |
| 11:41:54 | sean-k-mooney | EugenMayer: https://docs.openstack.org/masakari/latest/ is really the service you likely want to have automatic evacuation of ha instnaces | |
| 11:42:31 | sean-k-mooney | you can manually do it with mistal heat and aodh but masakari is a single service desinged to provide instance ha | |
| 11:43:09 | EugenMayer | migrating from proxmox to openstack, i have VMs with multiple disks. I understand that i can import disks as images using 'openstack image create --import' - but how to create a multi-disk VM? | |
| 11:43:44 | EugenMayer | sean-k-mooney interesting. Currently, since we are not planning in cinder, auto-evacuation is not possible anyway | |
| 11:44:19 | sean-k-mooney | EugenMayer: the imporant thing to remember however for the "core" service like nova is that openstack design principal is not based on a declaritve model its inparitive. e.g. it is not intend to take action autonomusly only when you interact with the system. so nova should never alter the state of a vm unless you make an api call | |
| 11:44:19 | EugenMayer | sean-k-mooney beside doing it from backup, which is rather a manual decision to do so. So not as cloudish as masakari would do it | |
| 11:45:02 | sean-k-mooney | EugenMayer: i hesitate to say this cause i dislike this code path but without cinder you can use masikari if you put the instnace state dir on an nfs share | |
| 11:45:04 | EugenMayer | sean-k-mooney understood. So it is more an API wrapper with high-level tasks, but it does not just act, that is for others to implement | |
| 11:45:17 | sean-k-mooney | EugenMayer: correct | |
| 11:45:25 | EugenMayer | sean-k-mooney nfs share is nothing else as cinder on horrible storage :) | |
| 11:45:59 | sean-k-mooney | yep and it used a diffeent code path then the one we normally use so less well tested | |
| 11:46:05 | sean-k-mooney | which is why its better to avoid it | |
| 11:46:15 | EugenMayer | right now, we go for local disks only, at least for the legacy VMs. K8s cluster is not yet decided. So most of the evacuate features / hot/live migration are not for us with the legacy vms | |
| 11:46:22 | sean-k-mooney | and the performance sucks vs a real shared stoage system | |
| 11:46:35 | sean-k-mooney | so back to your multi disk question | |
| 11:46:54 | sean-k-mooney | you can create multi disk vms but its not how nova is typically used | |
| 11:46:54 | EugenMayer | the performance is the main / only reason we are not jumping on ceph or similiar. We have to be realistic, our network is 1GB | |
| 11:47:08 | EugenMayer | with an MTU of 1400, no jumbo or anything | |
| 11:47:16 | sean-k-mooney | in the falvor there are 3 storage options disk, ephemeral and swap | |
| 11:47:32 | sean-k-mooney | disk is the root disk size | |
| 11:48:30 | EugenMayer | can i create VMs manually with any amount of disks since it's virsh in the end? I will only need this for the VMs i migrate - the ones i create from scratch are based on cloud-init and the proper disks you get using nova directly | |
| 11:48:32 | sean-k-mooney | ephemeral is the total amount of addtional ephemeral storage, i belive by default if you dont otherwise say all the ephemeral storage will be created as a singel addtional disk | |
| 11:48:52 | sean-k-mooney | you can however subdevide the ephemeral storage into multiple disk on the command line when you create the vm | |
| 11:49:15 | EugenMayer | using ephemeral storage we stopped, since the bug from 2016 that it cannot be resized :) | |
| 11:49:25 | sean-k-mooney | EugenMayer: no, as an end use you are not allowed to know the hypervior in use | |
| 11:49:29 | EugenMayer | nice, openstack server create is not the tool to go with here i guess | |
| 11:49:32 | sean-k-mooney | so you can just assume its virsh in the end | |
| 11:50:22 | EugenMayer | so using 'nova' is still hyperevisor agnostic, so it would be somewhat right? using virsh is discourage - that's what you mean, right? | |
| 11:51:40 | sean-k-mooney | openstack provides an abstration api over multiple hyperviors like libvirt/kvm, hyperv, vmware so yes the api is hypervior agnostic mostly | |
| 11:51:48 | sean-k-mooney | EugenMayer: using virsh is entirely unsupported | |
| 11:52:02 | sean-k-mooney | with opentask you can use virsh to inspect the xml for debugging | |
| 11:52:17 | EugenMayer | right now, i'am planing on how to migrate my old VMs which might have 1-3 disks. I know how to do it with one-disk setups. openstack image create --import .. the launch from snapshot. With multiple disks it all seems more complicated | |
| 11:52:22 | sean-k-mooney | but beyond that you shoudl never use virsh to modify any vm created by nova | |