Earlier  
Posted Nick Remark
#openstack-nova - 2019-07-23
21:46:48 efried mriedem: I have just emerged from the ironic-to-novaclient rabbit hole you sent me down.
21:46:55 mriedem haha
21:46:56 efried thanks (sincerely, no sarcasm) for that.
21:46:57 mriedem i knew it would happen
21:47:02 efried see https://review.opendev.org/#/c/672369/
22:01:43 dansmith mriedem: regarding my BFV comment?
22:02:12 mriedem yeah
22:02:46 dansmith yes, that's obviously old from the first WIPpy version of this where I was just taking shots against the caching scheduler
22:03:02 mriedem dustinc: efried: also some questions in the ironic driver + sdk patch https://review.opendev.org/#/c/642899/33 - looks like at least in our ci where nova-compute is started once before ironic, we now fail to start the service that first time unlike before where we'd swallow the VirtDriverNotReady error
22:03:03 efried mriedem: responded on https://review.opendev.org/#/c/643664/
22:03:23 dustinc mriedem: checking them out now, thanks
22:05:22 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (13) https://review.opendev.org/576020
22:05:32 efried mriedem: Note that the series forks; if you want an easy +Win, the placement one should be ready (zuul connection borkage notwithstanding) https://review.opendev.org/#/c/656023/
22:05:37 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (14) https://review.opendev.org/576027
22:05:54 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (15) https://review.opendev.org/576031
22:06:09 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (16) https://review.opendev.org/576299
22:06:14 mriedem dansmith: poor caching scheduler
22:06:23 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (17) https://review.opendev.org/576344
22:06:31 dansmith we could work up a remix of the office space printer scene with the caching scheduler
22:06:44 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (18) https://review.opendev.org/576673
22:07:04 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (19) https://review.opendev.org/576676
22:07:11 dansmith mriedem: https://imgflip.com/i/36cp5t
22:31:06 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (20) https://review.opendev.org/576689
22:31:19 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (21) https://review.opendev.org/576709
22:32:16 mriedem oh dan
22:32:26 mriedem there are things i've hated in nova more than that
22:34:22 redkrieg mriedem: I was looking at your blueprint for improving rescue mode and it's exactly what I need to offer ISO based OS installs for my clients. I see it's Abandoned for Train, but I was wondering if you knew off-hand what else needs to be done. https://blueprints.launchpad.net/nova/+spec/virt-rescue-stable-disk-devices
22:34:39 mriedem redkrieg: that's not mine
22:34:43 mriedem it's lyarwood's i think
22:34:55 redkrieg my apoligies, I just saw "Started by
22:35:00 redkrieg had your name
22:35:09 redkrieg I pinged him earlier but I think he's away today
22:35:40 mriedem he's in....UK timezone (can't remember if he's london or dublin, i know that's a grave error if i get it wrong)
22:35:45 mriedem dansmith: is lyarwood out this week? ^
22:36:09 dansmith mriedem: not according to the vacay calendar
22:36:38 mriedem ok i saw that he had re-proposed the spec for train https://review.opendev.org/#/c/651151/ but then abandoned it without any comment why, so idk
22:36:40 dansmith lyarwood is in angleand, not eye'r'land
22:36:42 mriedem but spec freeze is thursday
22:36:54 mriedem can i say he's in the "british isles"?
22:37:14 mriedem he's in a cold dark land of boiled meats and dark brews
22:38:57 redkrieg I pinged him earlier today with a similar message, hopefully he'll see it when he gets in tomorrow.
22:43:47 openstackgerrit Merged openstack/nova master: Drop delete_build_requests_with_no_instance_uuid online migration https://review.opendev.org/651001
22:43:57 openstackgerrit Merged openstack/nova master: Handle Invalid exceptions as expected in attach_interface https://review.opendev.org/650077
22:46:37 openstackgerrit Eric Fried proposed openstack/nova master: Remove fake_libvirt_utils users in functional testing. https://review.opendev.org/644793
22:48:28 efried stephenfin: I put that ^ back to PS10, which was passing tests, thereby resurrecting johnthetubaguy's +2. You were +2 at PS8; would you mind sending it? TIA.
22:49:12 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (22) https://review.opendev.org/576712
22:49:50 openstackgerrit Matt Riedemann proposed openstack/nova stable/stein: Handle Invalid exceptions as expected in attach_interface https://review.opendev.org/672384
23:23:13 openstackgerrit Takashi NATSUME proposed openstack/python-novaclient master: Deprecate the '--config-drive' option https://review.opendev.org/653683
23:24:17 openstackgerrit Takashi NATSUME proposed openstack/nova master: Add database schema upgrade check https://review.opendev.org/667047
23:36:07 openstackgerrit Merged openstack/nova master: Remove deprecated Core/Ram/DiskFilter https://review.opendev.org/672065
#openstack-nova - 2019-07-25
04:01:16 openstackgerrit ZHOU YAO proposed openstack/nova master: Preserve UEFI NVRAM variable store https://review.opendev.org/621646
05:05:24 openstackgerrit melanie witt proposed openstack/nova-specs master: Propose policy rule for host status UNKNOWN https://review.opendev.org/666181
07:04:52 openstackgerrit ZHOU YAO proposed openstack/nova master: Preserve UEFI NVRAM variable store https://review.opendev.org/621646
07:25:42 ChipOManiac Hi guys. We have an openstack cluster with three KVM compute hosts that we setup via openstack-ansible. We've set up a single Nova-LXD compute unit and then imported a tgz ubuntu cloud image into our images list.
07:26:07 ChipOManiac Our problem seems to be with launching any LXD instances on this new Nova-LXD compute host.
07:27:23 ChipOManiac If we try starting an LXD instance with this image. Nova creates a KVM instance and tries to boot the tgz with it.
07:27:31 ChipOManiac Obviously that won't work.
07:28:10 ChipOManiac Is there any way to make the LXD instance work here?
07:29:49 ChipOManiac I've seen Ubuntu charms deployments have a 'root-tar' image format. I don't see that here in our openstack-ansubile. Is there any way for me to add this disk format?
08:20:16 kashyap aspiers: Catching up with the long scroll here...buried in several things
08:58:06 openstackgerrit Merged openstack/nova master: Correct project/user id descriptions for os-instance-actions https://review.opendev.org/670027
09:01:19 stephenfin alex_xu: Would you be okay with me fixing this up in a follow-up?
09:01:20 stephenfin <mschuppert> kashyap: like I mentioned yesterday . the devnest pool is a shared pool for multiple DFGs. there are only 2 systems or so which are really exclusive for compute.
09:01:20 stephenfin <mschuppert> kashyap: yes. when you'd reserve one host per supported version and can not get multiple versions on one host.
09:01:21 stephenfin <kashyap> mschuppert: Hmm, didn't realize that fully
09:01:24 stephenfin whoops
09:01:33 stephenfin https://review.opendev.org/#/c/551026/
09:01:48 stephenfin HexChat's copy-paste behaviour is FUBAR
09:02:17 alex_xu stephenfin: ok, i'm cool with that
09:08:23 openstackgerrit Stephen Finucane proposed openstack/nova master: Follow-up for I2936ce8cb293dc80e1a426094fdae6e675461470 https://review.opendev.org/672669
09:08:27 stephenfin alex_xu: ^
09:08:59 alex_xu thanks
09:17:34 kashyap aspiers: On "what's wrong with option 1 -- do we need to pass virt_type?" -- if libvirt "knows" that KVM is available, then if you pass virt_type as None to getDomanCapabilities(), it defaults to KVM
09:17:46 kashyap I've done a bunch of quick tests
09:29:14 aspiers kashyap, sean-k-mooney: I got a reply from our libvirt guy
09:29:35 aspiers he said "domcapabilities should be the same with or without virttype"
09:29:45 aspiers so I'm not sure why it's a parameter in the API call
09:30:03 aspiers "default on a kvm host would be virttype=kvm"
09:31:53 kashyap aspiers: I'm getting you some diffs and results. 1 sec, uploading the files
09:32:13 kashyap https://kashyapc.fedorapeople.org/domCapabilities/domCapabilities_without_virt_type.txt
09:32:16 kashyap https://kashyapc.fedorapeople.org/domCapabilities/domCapabilities_with_virt_type_kvm.txt
09:32:43 kashyap aspiers: If you `diff` them, you'd see no `diff` (besides a one-line unrelated noise)
09:33:04 aspiers ok
09:33:13 kashyap aspiers: But ... as you guessed, if you explicitly supply virt_type as 'qemu', you would see siginificant difference
09:33:18 kashyap Here is the 'diff': https://kashyapc.fedorapeople.org/domCapabilities/diff_domCapabilities_of_virt_type_kvm_and_qemu.txt
09:35:16 kashyap aspiers: In other words, "your guy" is of course correct :-)
09:52:23 aspiers kashyap: thanks
09:53:27 kashyap aspiers: I'm still finishing something; but yes, option-4 is what I'd lean towards (at 'debug' level)
09:53:42 aspiers I think that's what sean-k-mooney's new PS implemented
09:54:04 kashyap And also yes to sean-k-mooney's we _do_ want to use the 'virt_type' when we know. As that will ensure the right CPU features are reported.
09:54:17 kashyap aspiers: Ah, okay. I'm lagging behind, as I was basing my comments on your IRC exchange linked in the review.
09:54:20 kashyap (Didn't refresh)
09:54:25 aspiers kashyap: https://review.opendev.org/#/c/670189/9..10/nova/virt/libvirt/host.py
09:54:35 kashyap Thank you
09:58:08 bhagyashris stephenfin: I gone through all you patches and also applied those in my environment and did some testing on it I have few observation with me
09:58:44 stephenfin shoot
09:59:13 bhagyashris stephenfin: 1. 1. I am able create the pinned instance using old way on your patches. you can see the details which steps I have followed to create the instance here http://paste.openstack.org/show/754840/
09:59:40 bhagyashris stephenfin: 2. I have also checked few scenarios and there I saw some issues. you can see here http://paste.openstack.org/show/754841/
10:01:09 stephenfin Yeah, I'd expect it to consume both VCPU and PCPU because I don't have the handling code you do. Your implementation is better in that regard
10:01:33 stephenfin The other two scenarios are interesting. I wonder what I'm hitting there

Earlier   Later