Earlier  
Posted Nick Remark
#openstack-nova - 2021-03-05
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
09:58:37 nautik ok cool, thank you
10:50:10 elod lyarwood: fyi, train and older branches are blocked until these aren't merged: https://review.opendev.org/q/Id62e91b1609db4b1d2fa425010bac1ce77e9fc51
10:50:32 lyarwood elod: ack was about to look at the failures of my earlier swap_volume instance.uuid backports
10:50:38 lyarwood elod: thanks for the heads up
10:50:45 elod np
10:53:12 lyarwood I guess it's yet another reverse order backport because of grenade?
10:59:46 elod only stein needs to be merged prior to train
10:59:57 elod stein can be merged directly
11:00:51 lyarwood ah of course, grenade doesn't vote prior to that
11:41:14 admin0 hi all .. what scheduler controls --property quota:disk_io_limit for a ceph backend in nova
11:41:24 admin0 so that io limits can be properly enforced
11:47:31 gibi admin0: based on the code it is only used by the vmware virt driver
11:49:42 sean-k-mooney admin0: the io filter limits the scudling based on higlevel io ops
11:49:49 sean-k-mooney like building a vm or snapshots
11:50:02 sean-k-mooney it does not look at disk iops or bandwith
11:50:39 sean-k-mooney i assume that is what you wanted to enforce or loadblance on?
12:09:26 sean-k-mooney admin0: disk_read_iops_sec disk_write_iops_sec and disk_total_iops_sec are supported in the libvirt driver by the way
12:09:57 sean-k-mooney admin0: e.g. --property quota:disk_total_iops_sec=500
12:10:37 sean-k-mooney admin0: there is no scheduling based on this and instead it enforece a limit on the amount of iops that a vm can do.
12:12:36 admin0 sean-k-mooney, https://gist.github.com/a1git/35020a03a3870741af463fc18e1e811c
12:12:39 admin0 i have the limit set at 800
12:12:47 admin0 but i am getting a lot and its not hitting any limit
12:12:54 admin0 or that i don't know how to test this using fio
12:13:02 sean-k-mooney what virt driver are you using
12:13:19 sean-k-mooney also you cant change that after the vm is booted
12:13:41 sean-k-mooney so after you do the flavor set you need to create a new vm with that flavor
12:14:24 sean-k-mooney "openstack flavor set g6 --property quota:disk_total_iops_sec=800" would be what you shoudl set if you are using libvirt
12:42:13 nightmare_unreal hello is there a way to get statistics of live-migration ? Like what was the avg disk transfer rate, how much time it took etc.
12:42:51 sean-k-mooney historical migrationg i dont think so but you can get stats form the ongoing migration at least form libvirt
12:43:08 sean-k-mooney posibly also form the api but im not sure how much detail we have in the migration status
12:46:48 lyarwood nightmare_unreal: https://docs.openstack.org/api-ref/compute/?expanded=show-migration-details-detail#show-migration-details
12:47:23 lyarwood nightmare_unreal: we don't list the average transfer rate etc
12:47:27 sean-k-mooney ah we do have disk_remaining_bytes etctra in that responce good
12:47:33 lyarwood nightmare_unreal: iirc it is dumped in the logs
12:47:39 nightmare_unreal ah then i can calculate i think
12:47:44 nightmare_unreal disk remaining / total disk
12:48:00 lyarwood yup
12:48:07 nightmare_unreal thanks :D
12:48:09 sean-k-mooney am not entirly
12:48:37 sean-k-mooney the byts migrated can be larger then total disk
12:49:02 lyarwood right and remaining can also move around
12:49:12 sean-k-mooney disk_processed_bytes can be larger then disk_total_bytes if the vm is wriging to the disk while its being migrated
12:51:09 sean-k-mooney you can get a microsoft style progress bar where it sometiems gose backwared or time remaing goes up as the persentage completeion increases if your try to use disk_remaining_bytes/disk_total_bytes to caulate things
12:51:29 sean-k-mooney the data is not meaning less but unless the guest is idel it wont be linear
12:51:31 lyarwood lol
12:53:18 nightmare_unreal ahah I see
12:53:28 nightmare_unreal i will keep that in mind.
13:06:00 sean-k-mooney gibi: i have a pe8 issue in my port numa policies patch so ill fix the doc issue when i repin it shortly
13:06:28 gibi sean-k-mooney: ack
13:07:01 sean-k-mooney by the way did you want me to add a new doc for this or just fix the comment
13:07:15 sean-k-mooney i could add a doc too but did you have a specific place in mind?
13:07:33 gibi sean-k-mooney: just add a doc to the function about the item in the returned tuple
13:08:24 sean-k-mooney ah cool. i was wondering if you wanted a user facing doc. i could add one of those as a followup but porbly need to think where that should go. ill fix the comment thanks:)
13:29:41 gibi sean-k-mooney: regarding the user facing doc, I hope neturon has at least an API doc for this port parameter
13:29:43 gibi :)
13:30:21 sean-k-mooney i was thinking maybe we should add something to the networking guide
13:30:43 gibi yeah that would be good to have ^^
13:30:44 sean-k-mooney they did not add the osc command but i submited a patch to do that
13:31:02 gibi the api ref is not missing but pretty short
13:31:04 sean-k-mooney so ill submit a follow up patch to the networkign guide to use that
13:31:12 gibi "The port NUMA affinity policy requested during the virtual machine scheduling. Values: None, requiered, preferred or legacy."

Earlier   Later