Earlier  
Posted Nick Remark
#openstack-nova - 2019-04-22
21:44:51 efried thankyousir
21:45:49 jaypipes npsir
22:06:15 efried mriedem: https://review.opendev.org/#/c/645316/ is related to https://bugs.launchpad.net/nova/+bug/1817927 yah?
22:06:16 openstack Launchpad bug 1817927 in OpenStack Compute (nova) "device tagging support is not checked during move operations" [Undecided,New]
22:58:45 openstackgerrit Michael Still proposed openstack/nova master: Remove fake_libvirt_utils from snapshot tests. https://review.opendev.org/642558
22:58:45 openstackgerrit Michael Still proposed openstack/nova master: Remove fake_libvirt_utils from connection tests. https://review.opendev.org/642557
22:58:46 openstackgerrit Michael Still proposed openstack/nova master: Remove fake_libvirt_utils from libvirt imagebackend tests. https://review.opendev.org/643895
22:58:46 openstackgerrit Michael Still proposed openstack/nova master: Remove fake_libvirt_utils from virt driver tests. https://review.opendev.org/643894
22:58:47 openstackgerrit Michael Still proposed openstack/nova master: Remove fake_libvirt_utils users in functional testing. https://review.opendev.org/644793
22:58:47 openstackgerrit Michael Still proposed openstack/nova master: Remove remaining vestiges of fake_libvirt_utils from unit tests. https://review.opendev.org/643896
23:13:31 openstackgerrit Ghanshyam Mann proposed openstack/os-traits master: Dropping the py35 testing https://review.opendev.org/654651
23:16:39 openstackgerrit Ghanshyam Mann proposed openstack/os-resource-classes master: Dropping the py35 testing https://review.opendev.org/654653
23:18:31 openstackgerrit Merged openstack/nova stable/queens: Fix legacy-grenade-dsvm-neutron-multinode-live-migration https://review.opendev.org/640197
23:24:22 mriedem efried: yeah somewhat
23:24:44 mriedem tonyb[m]: can you get this queens backport? https://review.opendev.org/#/c/640198/2
23:27:01 mriedem efried: unfortunately because i changed nova/test.py in https://review.opendev.org/#/c/654468/ it runs a full tempest run and all so i'm sitting in the check queue for 3.5 hours waiting to see if that makes any difference in the output
23:31:08 mriedem maybe i can speed that up
23:31:20 openstackgerrit Matt Riedemann proposed openstack/nova master: DNM: debug config opts infinite recursion https://review.opendev.org/654468
23:32:37 sean-k-mooney mriedem: so.... if i just run the compute and networking senario test and dont run all the api test in the nfv job do you think that is enough?
23:32:59 sean-k-mooney run with concurancy 1 is... slow
23:33:35 mriedem sean-k-mooney: those don't test nfv things do they? or are you making the ports sriov ports or something?
23:34:15 sean-k-mooney im using flavors that enable hugepage pinning realtime eumlator thread polices a cpu topolgies
23:34:49 sean-k-mooney i can also add custom tests but i wanted a baseline of tests we know work as a base and add to it if needed.
23:36:10 sean-k-mooney but ya its still rung the tests but the job has been running for a little over 5 hours and 20 minutes. if i just run the senario test that will drop back to about an hour
23:37:02 sean-k-mooney its multinode so the senario test will also chack migrations/resize.
23:39:55 sean-k-mooney i was expecting concurancy 1 to take maybe 3 hours with current tests set but 5+ is stupidly slow. ill let this finish and go back to the smaller test set. we can always add more after if there are specific test that make sense
23:40:06 sean-k-mooney anyway goodnight o/
23:43:28 mriedem yes just start with scenario tests in --serial or --concurrency=2 if you can
23:44:35 sean-k-mooney concurrency=2 was ocationally resulting in no valid host errors
23:45:04 sean-k-mooney pinning disable over subsription so its easy to end up running out for free cores
#openstack-nova - 2019-04-23
00:59:12 openstackgerrit Takashi NATSUME proposed openstack/python-novaclient master: Fix a description for config_drive parameter https://review.opendev.org/653683
01:14:13 openstackgerrit ya.wang proposed openstack/nova-specs master: Expose auto converge and post copy https://review.opendev.org/651681
01:20:45 openstackgerrit Takashi NATSUME proposed openstack/python-novaclient master: Updates for OpenDev transition https://review.opendev.org/654429
01:49:16 mnaser shopping an idea
01:49:22 mnaser how do you feel about killing devstack.
01:49:43 mnaser and replacing it by a deployment tool
02:08:19 openstackgerrit zhongshengping proposed openstack/nova master: Replace git.openstack.org URLs with opendev.org URLs https://review.opendev.org/654398
02:40:22 lbragstad efried get it figured out?
02:41:48 lbragstad efried as far as i know, the duplicated sessions were completely removed from the schedule
02:43:06 lbragstad https://www.openstack.org/summit/denver-2019/summit-schedule/events/23642/increasing-api-accessibility-with-granular-policy-and-default-roles is the one i have on my schedule
04:15:35 openstackgerrit Erik Olof Gunnar Andersson proposed openstack/nova master: Pass on region when we don't have a valid ironic endpoint https://review.opendev.org/654692
04:16:25 openstackgerrit Merged openstack/nova stable/rocky: libvirt: set device address tag only if setting disk unit https://review.opendev.org/653511
04:16:55 eandersson efried, ^ we could honestly just pass on the region, since region_name is only actually consumed if endpoint or session is missing.
04:17:06 eandersson But I am fine just passing it on when we don't have an endpoint.
07:37:47 openstackgerrit Boxiang Zhu proposed openstack/python-novaclient master: Add host and hypervisor_hostname to create servers https://review.opendev.org/647671
07:52:02 kashyap efried: Was on PTO yesterday. Just saw the scroll. I will address yours and mriedem's questions on that "CPU selection..." spec.
07:54:09 kashyap efried: I tried to be conscious to "not assume anything", _still_ my phrasing seems to be not sufficiently clear enough. Will rework.
07:55:58 sean-k-mooney kashyap: i think the issue is you assumed people understand and follow libvirt and did not present the usecase in terms of nova but instead present it as libvirt has this new api we shoudl use it with the assumtion people knew what libvirt api we currently use and what features it is used for
07:56:31 kashyap sean-k-mooney: I partly disagree. I didn't "assume" it that way.
07:56:49 kashyap How much more clearer can you phrase this:
07:56:52 kashyap [quote]
07:57:20 kashyap [/quote]
07:57:31 kashyap sean-k-mooney: My comment on PS-4, on: Apr 9 6:38 PM
07:57:43 sean-k-mooney that did not rendeer from me
07:58:08 sean-k-mooney i just see open and close quotes
07:58:14 kashyap I can add additional details and answer questions -- sure. But what is already there is sufficiently clear enough, no?
07:58:24 kashyap sean-k-mooney: Yeah, that was intentional; sorry :-) I didn't paste anything
07:58:33 kashyap (Because I didn't wanted to paste the large comment from the change)
07:58:46 kashyap sean-k-mooney: See my comment on PS-4: https://review.opendev.org/#/c/645814/4
08:00:15 sean-k-mooney ya but the poblem with that comment is you dont say how nova will handel it
08:00:18 kashyap sean-k-mooney: I told Nova's guest CPU selection is lacking. And even provided a rough example like:
08:00:21 kashyap "Is this combination of IvyBridge + 'pcid' & 'pdpe1gb' supported by KVM, QEMU and libvirt on the host?"
08:00:26 kashyap sean-k-mooney: Yes, that part, I will addres.
08:00:28 sean-k-mooney e.g. will the agent refuse to start
08:00:54 kashyap Right, will address them, once I finish addressing comments on the Secure Boot spec.
08:01:39 sean-k-mooney by the way nova has no cpu selection logic outside of host-model so its not really lacking as non existent
08:02:57 sean-k-mooney i just found out that weechat has mouse support and gesture ...
08:03:04 sean-k-mooney i dont think i like them
08:04:05 kashyap sean-k-mooney: I'm of course aware that we default to 'host-model'. That's not the point. When I say "CPU selection", it also means CPU model + features (obviously).
08:04:11 sean-k-mooney kashyap: for what its worth i only barely followed what you were proposing in that spec.
08:04:17 kashyap https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L3948,#L3957
08:04:30 sean-k-mooney kashyap: yes but that is hardcoded effectivly via the config
08:04:40 sean-k-mooney its not nova making the selection in this case its the operator
08:04:50 kashyap (I will rephrase the spec with a couple more examples.)
08:05:04 kashyap (Not entirely, some bits. While adding additional details.)
08:05:13 openstackgerrit Boxiang Zhu proposed openstack/nova master: Add host and hypervisor_hostname flag to create server https://review.opendev.org/645520
08:06:08 sean-k-mooney one thing i was wondering is do you want to merge this spec with https://review.opendev.org/#/c/642030/
08:06:32 sean-k-mooney the current one has no end user visable impact
08:06:32 kashyap No, I want to keep it separate.
08:06:38 sean-k-mooney ok
08:06:45 kashyap As I'm not even sure if we should do: https://review.opendev.org/#/c/642030/
08:06:57 sean-k-mooney ya i guessed that is why
08:07:21 sean-k-mooney if we do implment the second spec https://review.opendev.org/#/c/642030/ it will depend on this new api
08:07:26 sean-k-mooney or it should use the new api
08:07:39 kashyap Also, not every spec needs to be "user visible". (That said, in this case, it _is_ "operator visible" in a way. Will save the write-up for the spec)
08:08:06 sean-k-mooney well its not other then the agent will stop if its not compatible
08:08:31 sean-k-mooney there is not rest api changes
08:08:40 sean-k-mooney or traits changes
08:09:34 kashyap sean-k-mooney: It is not just about 'compat check'. The resulting CPU + flags will be more _useful_ and _useable_
08:09:46 sean-k-mooney how
08:10:22 kashyap I explained it in the spec. I wonder if you even read that.
08:10:24 sean-k-mooney the set of flag we get back for what the host support wont change
08:10:30 sean-k-mooney yes i did
08:10:36 sean-k-mooney you did not explain it well
08:10:44 sean-k-mooney in terms of how its more useful to nova
08:10:57 sean-k-mooney beyond we can as if the value in the config are valid
08:12:09 kashyap sean-k-mooney: Did you read this at all?
08:12:11 kashyap [quote]
08:12:12 kashyap - While determining guest CPU models, Nova can take into account several other aspects, e.g. the type of virtualization (pure emulation vs. hardware-accelerated), QEMU binary's capabilities, guest machine type, and CPU architcture to construct a better-informed guest CPU.
08:12:16 kashyap [/quote]

Earlier   Later