Earlier  
Posted Nick Remark
#openstack-nova - 2017-05-31
21:59:39 mriedem it's excellent
21:59:47 mriedem fabulous
21:59:48 mriedem the best
22:02:23 mriedem jaypipes: here you go https://review.openstack.org/469670
22:04:53 jaypipes mriedem: danke
22:24:18 mriedem efried: does https://review.openstack.org/#/c/443189/ mean we can close that bp for pike?
22:24:23 mriedem or is it carte blanche?
22:25:11 efried mriedem I wouldn't mind getting more function in; does closing the bp preclude that?
22:25:57 efried mriedem Also, there will be some small followup work on the already-merged codebase (from code comments in previous changes, following community stuff like resource provider work, etc.) - assume that stuff just gets to be regular non-bp-linked change sets.
22:27:01 mriedem the follow up cleanups are fine to be separate from the bp,
22:27:18 mriedem and i think the get_inventory() stuff can be tracked under whatever was used for the same thing in the libvirt driver
22:29:45 efried mriedem So if we want to propose more function, and the bp is closed, will those changes automatically get -2ed and punted to queens? (By "automatically" I of course refer to the turd in your pocket.)
22:32:58 mriedem i wouldn't close it then, but i'd rather it not churn on forever either
22:33:18 mriedem i want to close things out so we can focus reviews on stuff that's not done yet
22:40:26 efried mriedem Okay, let me go back to the team and see if we want to shoot for more function in pike (config drive is small; and OVS would give us an actual usable VM). Tomorrow soon enough for me to get back to you on this?
22:40:57 mriedem efried: yeah i'm not in a rush
22:41:01 efried k
22:45:57 openstackgerrit Matt Riedemann proposed openstack/nova master: WIP: Default AZ for instance if cross_az_attach=False and checking from API https://review.openstack.org/469675
22:48:02 mriedem god cross_az_attach is terrible
22:48:07 mriedem woe to anyone that ever sets it to False
22:50:51 openstackgerrit Matt Riedemann proposed openstack/nova master: WIP: Default AZ for instance if cross_az_attach=False and checking from API https://review.openstack.org/469675
23:24:11 tasker I'm having a problem with freezing the filesystem using the libvirt modules. I keep getting "AttributeError: 'virDomain' has no attribute 'fsFreeze'". I'm using Nova Mitaka (13.1.2), and a full grep for 'fsFreeze' only shows the failing call at line 440, the definition in the mocklibvirt driver for the test, and a couple of comments. The libvirt driver itself (1.3.2) has no definition for a
23:24:17 tasker function named 'fsFreeze'. The only bug report I've found referencing is from last May and says to use libvirt >= 1.2.5.. what am I missing? anyone have any ideas?
23:27:07 clarkb tasker: what version of libvirt and what version of libvirt-python?
23:27:48 tasker using OSA, the venv has 1.3.2, the dpkg for the system wide is 1.3.1
23:28:18 mriedem you need at least libvirt 1.2.5
23:28:35 cfriesen_ can you run "virsh domfsfreeze" manually on the compute node?
23:28:39 mriedem fsFreeze is a function on libvirt-python i believe
23:28:40 tasker nova calls oslo_utils.importutils.import_module("libvirt") which pulls in the 1.3.2 found in /openstack/venvs/nova/lib/python2.7/site-packages/libvirt.py
23:29:04 cfriesen_ what version is your actual libvirt though?
23:29:14 mriedem you also need hw_qemu_guest_agent in the image
23:29:52 cfriesen_ tasker: what does "virsh --version" give?
23:30:13 tasker 'virsh --version' reports "1.3.1"
23:30:25 tasker and I can call and issue domfsfreeze manually.
23:30:55 mriedem seems like a problem with the libvirt-python package,
23:31:03 tasker myproblem is that there is no function called fsFreeze.
23:31:19 mriedem people have reported issues like this before where libvirt and the libvirt-python package say they are at a certain version but the python binding is actually old or missing some things
23:31:34 clarkb the way libvirt-python works is it exposes the features of libvirt that it was built against
23:31:36 cfriesen_ tasker: what's your "virt_type"?
23:31:36 mriedem i'm not really sure how
23:31:48 clarkb so if you installed via a wheel or similar that was built against an old version of libvirt that could explain it
23:31:54 tasker virt_type = 'kvm'
23:32:12 tasker clarkb: i like that explanation. it makes a lot of sense.
23:32:29 clarkb pip install --no-binary -U libvirt-python should force it to rebuild though that will affect whatever system you build against
23:32:36 openstack Launchpad bug 1539506 in Ubuntu Cloud Archive liberty "AttributeError: 'virDomain' object has no attribute 'fsFreeze" [Medium,Fix committed]
23:32:36 mriedem https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1539506
23:33:25 tasker mriedem: that bug only says what you've mentioned regarding libvirt versions and where to get updated ones. I did not find it helpful.
23:33:42 mriedem ok i can't tell if they put out an updated libvirt-python for mitaka or not
23:33:50 tasker your's and clark's mention of misbuilt packages makes a lot more sense.
23:34:06 tasker neither could I; hence my coming here.
23:34:29 tasker clarkb: I'll give that pip incantation a shot.
23:35:24 tasker could you explain how doing that would affect "whatever system you bulid against" in some more detail?
23:35:58 clarkb tasker: it will overwrite any existing libvirt-python install potentially breaking other working functionality :)
23:36:04 clarkb It should be safe though
23:36:17 tasker ahh .. ok. so backups for everyone!
23:37:10 tasker now, I use OSA which puts a lot of the bits into virtual environments. I'm thinking I want to do this there (in the venv) and not for the system-wide libvirt-python.
23:37:38 mriedem i can only find https://launchpadlibrarian.net/242454264/libvirt-python_1.3.1-1ubuntu1~cloud0_source.changes
23:37:49 mriedem for the change log for libvirt-python in mitaka UCA
23:38:07 tasker mriedem: thanks! I"ll take a look.
23:38:19 mriedem jamespage is probably the person you need to reach out to,
23:38:25 mriedem he's in the UK so you'll have to try later
23:39:03 tasker right. I'll try clarkb's method first and come back to let you know of success / disaster.
23:40:15 tasker b'ah -- "Requirement already up-to-date". this is going to be a bit trickier.
#openstack-nova - 2017-06-01
00:01:38 openstackgerrit melanie witt proposed openstack/nova master: Add FixedIP.get_count_by_project() https://review.openstack.org/446246
00:01:39 openstackgerrit melanie witt proposed openstack/nova master: Add FloatingIP.get_count_by_project() https://review.openstack.org/446247
00:01:40 openstackgerrit melanie witt proposed openstack/nova master: Add get_count_by_vm_state() to Instance object https://review.openstack.org/446244
00:01:42 openstackgerrit melanie witt proposed openstack/nova master: Add SecurityGroup.get_counts() https://review.openstack.org/446245
00:01:43 openstackgerrit melanie witt proposed openstack/nova master: Remove 'reserved' count from used limits https://review.openstack.org/446242
00:01:44 openstackgerrit melanie witt proposed openstack/nova master: Remove useless quota_usage_refresh from nova-manage https://review.openstack.org/446243
00:01:45 openstackgerrit melanie witt proposed openstack/nova master: Count server groups to check quota https://review.openstack.org/446240
00:01:46 openstackgerrit melanie witt proposed openstack/nova master: Count networks to check quota https://review.openstack.org/446241
00:01:49 openstackgerrit melanie witt proposed openstack/nova master: Count instances to check quota https://review.openstack.org/416521
00:01:53 openstackgerrit melanie witt proposed openstack/nova master: Add InstanceGroup.get_counts() https://review.openstack.org/457857
00:01:54 openstackgerrit melanie witt proposed openstack/nova master: Add InstanceGroup._remove_members_in_db https://review.openstack.org/457858
00:01:59 openstackgerrit melanie witt proposed openstack/nova master: Count server group members to check quota https://review.openstack.org/457859
00:02:00 openstackgerrit melanie witt proposed openstack/nova master: Count security groups to check quota https://review.openstack.org/457860
00:02:06 openstackgerrit melanie witt proposed openstack/nova master: Make Quotas object favor the API database https://review.openstack.org/410945
00:02:07 openstackgerrit melanie witt proposed openstack/nova master: Count fixed ips to check quota https://review.openstack.org/457861
00:02:09 openstackgerrit melanie witt proposed openstack/nova master: Add online migration to move quotas to API database https://review.openstack.org/410946
00:02:12 openstackgerrit melanie witt proposed openstack/nova master: Count floating ips to check quota https://review.openstack.org/457862
00:11:27 cfriesen_ anyone know offhand of reported issues with upgrading from kilo but the service version being stuck at 0?
00:13:26 masber good morning all, to which nova config file do I need to add the parameter dhcp_domain?
00:14:36 melwitt cfriesen_: are you using the nova-api wsgi script? it doesn't work properly with service records so it will always see service version 0 https://github.com/openstack/nova/blob/master/nova/wsgi/nova-api.py
00:15:12 cburgess @masbar it needs to be read by the metadata service. So usually just nova.conf
00:15:20 cburgess @masber ^^^^
00:16:42 cfriesen_ melwitt: we did a kilo->mitaka upgrade, and all the services except for nova-osapi_compute and nova-metadata are stuck on version 0 even if I do things like disable/enable them. I'm trying to figure out why we're not writing the new service version of 9 to the DB
00:17:22 cfriesen_ this has run fine for a long time, but now I can't run the online migrations script in Mitaka since it fails the minimum version check
00:17:47 cfriesen_ I'm guessing we missed something from liberty since we skipped it, but not sure what
00:18:51 melwitt by skipped it do you mean you didn't run "nova-manage db sync" with the liberty code?
00:19:25 melwitt and "nova-manage db online_data_migrations"
00:19:26 cfriesen_ melwitt: no, we ran that from mitaka
00:19:45 cfriesen_ and I dont' think there was an online_data_migrations for liberty
00:19:46 tasker some victory. I was unable to use clarkb's 'pip' incantantion, but I did uninstall the libvirt-python from the venv and link in the libvirt files from the system-wide libivrt-python installed via the package manager.
00:19:55 melwitt okay. that might be a problem. would have to read through the liberty relnotes to see what, if anything was missed
00:20:15 cfriesen_ I did read the relnotes and didn't see anything suspicious, but will check again
00:20:19 tasker so, the idea that the libvirt module I'm using is incomplete has some evidence to back it up. now I need to figure out what happened where it came from.
00:20:41 melwitt I don't know off the top of my head details about how the service version stuff got set up when it was introduced
00:20:48 tasker clarkb: and mriedem: thank you for your help.
00:22:10 tasker I wonder if OSA is responsible for building the libvirt binary module itself or if it pulls in a pre-compiled module from some central repo.
00:22:11 clarkb tasker: fwiw you can also create virtualenvs wit system libs with a flag

Earlier   Later