Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2021-03-05
16:59:06 openstackgerrit Stephen Finucane proposed openstack/nova master: hardware: Start parsing 'os_secure_boot' https://review.opendev.org/c/openstack/nova/+/682628
16:59:12 openstackgerrit Stephen Finucane proposed openstack/nova master: compute: Report COMPUTE_SECURITY_UEFI_SECURE_BOOT https://review.opendev.org/c/openstack/nova/+/776679
16:59:19 openstackgerrit Stephen Finucane proposed openstack/nova master: scheduler: Translate secure boot requests to trait https://review.opendev.org/c/openstack/nova/+/776680
16:59:26 openstackgerrit Stephen Finucane proposed openstack/nova master: libvirt: Switch to libvirt's firmware auto-selection https://review.opendev.org/c/openstack/nova/+/775691
16:59:31 openstackgerrit Stephen Finucane proposed openstack/nova master: libvirt: Wire up 'os_secure_boot' property https://review.opendev.org/c/openstack/nova/+/776681
16:59:35 openstackgerrit Stephen Finucane proposed openstack/nova master: libvirt: Report secure boot support to scheduler https://review.opendev.org/c/openstack/nova/+/775690
16:59:42 openstackgerrit Stephen Finucane proposed openstack/nova master: tests: Add functional tests for UEFI, secure boot https://review.opendev.org/c/openstack/nova/+/776682
16:59:48 openstackgerrit Stephen Finucane proposed openstack/nova master: tests: Remove duplicated 'start_compute' helper https://review.opendev.org/c/openstack/nova/+/776683
16:59:56 openstackgerrit Stephen Finucane proposed openstack/nova master: doc: Document UEFI secure boot feature https://review.opendev.org/c/openstack/nova/+/776684
17:00:31 stephenfin lyarwood: That's mostly merge conflict resolution. I'm working on undoing the firmware auto-selection changes now but it should free up everything below it to merge, at least
17:00:44 stephenfin just FYI
17:00:51 stephenfin bauzas also
17:01:03 lyarwood stephenfin: thanks, can we chat about the auto selection stuff on Monday just so I'm sure I get the direction?
17:01:16 stephenfin sure
17:01:18 lyarwood stephenfin: I'll also hit everything up to that first thing on Monday regardless
17:01:44 stephenfin in short though, I'm just going to drop that patch and go back to generating everything manually
17:01:50 stephenfin https://that.guru/blog/uefi-secure-boot-in-libvirt/
17:02:08 stephenfin that might help explain what it was supposed to do and why we can't use it (scroll to the bottom for that)
17:02:18 lyarwood kk I thought so, I couldn't get my head around all of the details in the bug
17:05:35 openstackgerrit Balazs Gibizer proposed openstack/nova master: Add device event constants to fakelibvirt https://review.opendev.org/c/openstack/nova/+/778887
17:20:01 kashyap stephenfin: That's quite some speed there.
17:20:11 kashyap I mean, in reworking the series.
17:52:48 openstackgerrit melanie witt proposed openstack/nova stable/ussuri: Add regression test for bug 1914777 https://review.opendev.org/c/openstack/nova/+/777218
17:52:51 openstack bug 1914777 in OpenStack Compute (nova) victoria "Possible race condition between n-cpu and n-api when deleting a building instance" [High,In progress] https://launchpad.net/bugs/1914777 - Assigned to melanie witt (melwitt)
17:52:52 openstackgerrit melanie witt proposed openstack/nova stable/ussuri: Handle instance = None in _local_delete_cleanup https://review.opendev.org/c/openstack/nova/+/777219
18:32:15 admin0 hi all openstack server show $uuid => hostId -- how do i check what hostId is which hypervisor ?
18:33:43 sean-k-mooney as a non admin you cant intntionally
18:33:55 sean-k-mooney ifyou are an admin you can check it differently
18:34:29 sean-k-mooney hostid is a hash of the hostname salted by your poject id
18:35:35 sean-k-mooney OS-EXT-SRV-ATTR:hypervisor_hostname should be avaiable as an admin
18:36:32 sean-k-mooney hostid: "An ID string representing the host. This is a hashed value so will not actually look like a hostname, and is hashed with data from the project_id, so the same physical host as seen by two different project_ids, will be different. It is useful when within the same project you need to determine if two instances are on the same or different physical hosts for the purposes of
18:36:34 sean-k-mooney availability or performance."
18:36:39 sean-k-mooney from the api ref ^
18:38:22 sean-k-mooney admin0: hopefully that helps. its considerd a security issue if vms can determin what host they are running on directly
18:38:40 sean-k-mooney assuming they can use that info to target another vm to the same host
18:39:12 sean-k-mooney that is why the hostid is hashed and different proejct will see different values for the same host
18:39:18 admin0 oh .. got it
18:49:43 openstackgerrit sean mooney proposed openstack/nova master: support per port numa policies with sriov https://review.opendev.org/c/openstack/nova/+/773792
19:27:44 dansmith has anyone noticed compute nodes getting 500 errors from placement?
19:27:45 dansmith https://zuul.opendev.org/t/openstack/build/19989232c4b94c848894c6e54d9fa49c/log/logs/subnode-2/screen-n-cpu.txt#9204
19:28:25 dansmith oh you know,
19:28:38 dansmith that might be during the upgrade part where the service is down
19:35:48 melwitt dansmith: I haven't noticed that before but can see the corresponding request doesn't show up in the placement logs, so that seems to support what you're thinking that it's when the service is down? I didn't know how/if the service can 500 while it is maybe partially up/in a state where it would not log the request in placement. timestamps match too
19:36:21 dansmith melwitt: because of the TLS proxies I expect
19:36:44 dansmith melwitt: after that in the log, conductor is down for a while when it's trying to update its service record, which I think is the key indicating we're in the upgrade phase
19:36:50 dansmith this is the left-behind node of the multinode upgrade
19:36:53 melwitt oh I didn't realize that job ran with TLS enabled
19:37:08 dansmith well, I guess I was assuming it did
19:37:55 melwitt it might, I had thought only nova-next did
19:38:24 dansmith oh, actually, what I mean is with the apache->uwsgi->nova bit
19:38:30 dansmith technically that's not the tls
19:39:06 dansmith lots of jobs do, this is the base tempest integrated job: https://zuul.opendev.org/t/openstack/build/266f30d8a31944ca8e391c2d67402582/log/controller/logs/local_conf.txt#34
19:39:10 dansmith not just nova-next
19:40:52 melwitt oh, TIL. cool
19:41:13 sean-k-mooney the tls proxy?
19:41:32 sean-k-mooney i think thats enabled by default
19:41:35 melwitt I was thinking of this jazz, since I've worked with it before https://github.com/openstack/nova/blob/master/.zuul.yaml#L229-L235
19:41:50 sean-k-mooney but that is quite different form tls everywhere as we normally thinkg of it
19:41:56 dansmith right
19:42:05 dansmith melwitt: yeah I think it's on in more base jobs we inherit from
19:42:26 dansmith melwitt: that nova-next job might not because it's multinode or something, but it's on in a lot of places now
19:42:43 dansmith "might not get it from inheritance" I mean
19:42:50 melwitt I see, cool
19:43:01 sean-k-mooney https://github.com/openstack/devstack/blob/master/.zuul.yaml#L485
19:43:09 sean-k-mooney its on by default in the base devstack job
19:44:36 sean-k-mooney which menas it on in all the tempest jobs by default https://github.com/openstack/tempest/blob/master/zuul.d/base.yaml#L2-L3
19:46:42 sean-k-mooney melwitt: i think setting it in nova-next is likely legacy form when that was zullv2 based
19:46:57 sean-k-mooney melwitt: i dont think the tls_proxy was enabeld in the legacy jobs
20:19:16 admin0 hi guys . my openstack ansible is stuck here: my nova is stuck at raise exceptions.VersionNotFoundError(", "migrate.exceptions.VersionNotFoundError: \"Database schema file with version 82 doesn't exist.\""]}
20:19:31 admin0 any ideas where to get this version 82 from ?
22:54:43 openstackgerrit melanie witt proposed openstack/nova master: Differentiate between InstanceNotFound and ConstraintNotMet https://review.opendev.org/c/openstack/nova/+/775309
#openstack-nova - 2021-03-06
14:32:11 openstackgerrit Merged openstack/nova master: nova-manage: Add libvirt update_machine_type command https://review.opendev.org/c/openstack/nova/+/774896
17:21:58 openstackgerrit Merged openstack/nova master: nova-manage: Add libvirt list_unset_machine_type command https://review.opendev.org/c/openstack/nova/+/774897
17:22:44 openstackgerrit Merged openstack/nova master: nova-status: Add hw_machine_type check for libvirt instances https://review.opendev.org/c/openstack/nova/+/770643
17:23:16 openstackgerrit Merged openstack/nova master: Fix ImageBackendFixture not to support direct_snapshot https://review.opendev.org/c/openstack/nova/+/778462
17:23:41 openstackgerrit Merged openstack/nova master: libvirt: Add a config update workflow test for [libvirt]hw_machine_type https://review.opendev.org/c/openstack/nova/+/774898
17:24:13 openstackgerrit Merged openstack/nova master: docs: Add admin docs for configuring and updating machine types https://review.opendev.org/c/openstack/nova/+/774899
17:34:43 openstackgerrit Merged openstack/nova master: apidb: Compact Ocata database migrations https://review.opendev.org/c/openstack/nova/+/759402
#openstack-nova - 2021-03-07
10:15:19 openstackgerrit Merged openstack/nova master: apidb: Compact Pike database migrations https://review.opendev.org/c/openstack/nova/+/759403
11:35:57 openstackgerrit Merged openstack/nova master: Drop support for custom schedulers https://review.opendev.org/c/openstack/nova/+/773637
12:28:19 openstackgerrit Merged openstack/nova master: conf: Drop '[scheduler] periodic_task_interval' https://review.opendev.org/c/openstack/nova/+/773638
14:24:34 openstackgerrit Merged openstack/nova master: libvirt: Add support for virtio-based input devices https://review.opendev.org/c/openstack/nova/+/756552
#openstack-nova - 2021-03-08
08:59:19 openstackgerrit Lee Yarwood proposed openstack/nova master: nova-next: Start testing the q35 machine type https://review.opendev.org/c/openstack/nova/+/708701
09:00:22 lyarwood stephenfin: thanks for asking for the release, I guess they sorted out their issues between each of us asking
09:00:46 lyarwood stephenfin: of Cirros that is, I've updated the nova-next change but it's going to depend on getting 0.5.2 cached first
09:40:47 bauzas (FTTH soldering)
09:50:56 openstackgerrit Lee Yarwood proposed openstack/nova stable/train: compute: Lock by instance.uuid lock during swap_volume https://review.opendev.org/c/openstack/nova/+/758733
09:51:18 openstackgerrit Lee Yarwood proposed openstack/nova stable/stein: compute: Lock by instance.uuid lock during swap_volume https://review.opendev.org/c/openstack/nova/+/758734
09:51:52 openstackgerrit Lee Yarwood proposed openstack/nova stable/queens: compute: Lock by instance.uuid lock during swap_volume https://review.opendev.org/c/openstack/nova/+/758736
09:52:16 openstackgerrit Lee Yarwood proposed openstack/nova stable/rocky: compute: Lock by instance.uuid lock during swap_volume https://review.opendev.org/c/openstack/nova/+/758735
09:53:15 nautik Hello guys, I have a quick question: I see keypair names only allow "_- " as special characters, and I have a lot of users trying to input a name with @ in it (default suggested by ssh-keygen I think)
09:53:25 nautik (code is here https://opendev.org/openstack/nova/src/branch/master/nova/compute/api.py#L6343)
09:53:54 nautik would anyone know if there is a reason not to allow the '@' character? Or could this be suggested?
09:54:37 nautik I found this commit introducing the check https://github.com/openstack/nova/commit/c8b0a9a3be7ca276d91d470a629fdd0209812993
09:54:58 nautik which fixes an issue about / (https://bugs.launchpad.net/nova/+bug/937408)
09:54:59 openstack Launchpad bug 937408 in OpenStack Compute (nova) "Can't delete keypair with a slash" [Medium,Fix released] - Assigned to Justin Shepherd (jshepher)
09:55:45 gibi bauzas: good for you :)
09:56:21 nautik but appearently users are commonly trying to put '@' in their key name
09:57:20 gibi nautik: based on the bug you linked the issue was forward slash in the name '/'. So we could try to see if we can make @ work
09:57:56 gibi nautik: if you have time to propose a patch that allows @ along with some functional test then I will be happy to review it

Earlier   Later