Earlier  
Posted Nick Remark
#openstack-nova - 2018-02-19
22:14:01 jaypipes efried: I thought all API changes required a spec?
22:14:20 efried jaypipes: Apparently that's true; see above.
22:43:26 openstackgerrit Merged openstack/nova master: Remove deprecated aggregate DB compatibility https://review.openstack.org/544698
22:54:44 openstackgerrit Merged openstack/nova master: Lazy-load instance attributes with read_deleted=yes https://review.openstack.org/543970
23:03:55 mriedem mdbooth: you should take a look at this https://review.openstack.org/#/c/542646/
23:19:05 tetsuro is avolkov around?
23:20:12 tetsuro I’d like you to answer the question in https://review.openstack.org/#/c/539865/. … or anyone who can help me.
23:47:44 mnaser is there any way i can do something to get output from nova-compute about memory usage
23:47:53 mnaser i have a nova-compute process sitting on 13gb of ram.
23:48:21 mnaser (before i restart it, just to get helpful information out)
23:49:30 melwitt mriedem: these comments aren't related to the patch, are they? just a suggestion on some better cleanup we could do in a separate patch? https://review.openstack.org/#/c/520158/3/nova/compute/api.py@2826
23:50:14 mnaser wow... actually almost every nova-compute process is using 13g of memory..
#openstack-nova - 2018-02-20
00:00:02 openstackgerrit Eric Fried proposed openstack/nova-specs master: Filter Resource Provider List for Traits https://review.openstack.org/546009
00:00:21 efried edleafe, mriedem, melwitt, jaypipes, cdent: ^
00:04:28 melwitt mnaser: the only thing I know of is the hypervisor-stats type of things e.g. https://docs.openstack.org/nova/pike/admin/common/nova-show-usage-statistics-for-hosts-instances.html
00:04:45 melwitt mnaser: but you may be able to use something like this to dig deeper https://github.com/rogerhu/gdb-heap
00:05:10 mnaser melwitt: looks like a bunch of reading but i'll look into it because it seems a bit (very) high
00:05:19 mnaser melwitt: thank you for that information
00:08:37 melwitt the only other thing could be a GMR (guru meditation report)
00:09:32 melwitt I'm not sure that would help too much https://docs.openstack.org/nova/latest/reference/gmr.html
00:10:21 mmedvede mriedem: ok, I'll change that
00:10:49 melwitt but it should be simple to try, send USR2 to the nova-compute pid
00:39:02 openstackgerrit Merged openstack/nova master: Fix PatternPropertiesTestCase for py 3.6 https://review.openstack.org/545798
00:39:22 openstackgerrit Merged openstack/nova master: Do not multiply megabytes with 1024 to get gigabytes. https://review.openstack.org/536335
00:42:09 openstackgerrit Merged openstack/nova master: libvirt: add Linux distribution guest only description for inject_xxx options https://review.openstack.org/528441
00:51:38 openstackgerrit Merged openstack/nova master: Update docstring for get_traits virt driver method https://review.openstack.org/539505
00:51:53 openstackgerrit Merged openstack/nova master: Add resource_class to fields in ironic node cache https://review.openstack.org/539506
00:52:11 openstackgerrit Merged openstack/nova master: trivial: Don't use 'Test' prefix for non-TestCase classes https://review.openstack.org/539251
01:02:13 openstackgerrit Merged openstack/nova master: trivial: Resolve "X is renamed to Y" warnings https://review.openstack.org/539252
01:02:32 openstackgerrit Merged openstack/nova master: Don't modify objects directly https://review.openstack.org/539253
01:04:31 tetsuro could anyone review https://review.openstack.org/#/c/531347/? It got one +2 a month ago.
01:35:51 mriedem melwitt: yeah i guess, i probably hadn't noticed that when rebasing it last time
01:36:04 mriedem mnaser: my guess would be any caching done in the nova.compute.manager.resource_tracker
01:36:15 mriedem mnaser: we cache some placement-related stuff in there now
01:36:32 mriedem but it shouldn't be much..
01:37:13 mriedem https://github.com/openstack/nova/blob/master/nova/compute/resource_tracker.py#L133
01:37:25 melwitt mriedem: okay, just wanted to confirm whether there's more to do on that patch before I +W
01:37:57 mriedem melwitt: as far as i know, not tracking the created snapshots and cleaning them up is latent behavior
01:38:13 melwitt mriedem: that's what it looked like to me too
01:38:52 mriedem mnaser: and the RT has an in-memory report client that has a cache of its own https://github.com/openstack/nova/blob/stable/pike/nova/scheduler/client/report.py#L233
01:51:36 openstackgerrit Merged openstack/nova master: Remove unused method _parse_node_instance_info https://review.openstack.org/539507
02:12:15 openstackgerrit Merged openstack/nova master: Add the ability to get absolute limits from Cinder https://review.openstack.org/520122
02:38:48 tetsuro melwitt: responsed on https://review.openstack.org/#/c/531328/4, thank you for the review.
03:18:39 openstackgerrit Takashi NATSUME proposed openstack/nova master: Transform aggregate.update_metadata notification https://review.openstack.org/460625
05:50:50 openstackgerrit Rajesh Tailor proposed openstack/nova master: Return 400 when compute host is not found https://review.openstack.org/447355
05:55:50 openstackgerrit Rajesh Tailor proposed openstack/nova master: Return 400 when compute host is not found https://review.openstack.org/447355
05:59:56 openstackgerrit Rajesh Tailor proposed openstack/nova master: Return 400 when compute host is not found https://review.openstack.org/447355
07:12:28 akki__ Hello, I have a running OpenStack setup on which I was able to launch VMs. But I want to move to use LXC instantiation. So, for that, I have installed nova-compute-lxd on my current setup of OpenStack with basic services installed in it. I have installed nova-compute-lxd on my compute node (Ubuntu 16.04), changed the virt-type to 'lxc' in my nova.conf and then restarted the nova-compute service.
07:12:52 akki__ After this, I launched an instance and it failed after some time and gives the following error: [Error: No valid host was found. There are not enough hosts available.]. Could you please guide what else is required to launch container on OpenStack setup? What configurations will I need to configure LXD and my nova user to see the LXD daemon. I am new to this, every help appreciated.
09:00:46 hrw morning
09:13:23 openstackgerrit Mark Goddard proposed openstack/nova stable/queens: Add resource_class to fields in ironic node cache https://review.openstack.org/546085
09:29:28 openstackgerrit Dinesh Bhor proposed openstack/nova-specs master: Strict isolation of group of hosts for images https://review.openstack.org/381912
09:34:51 lyarwood mdbooth: https://review.openstack.org/#/c/543569/ - would you mind taking a look at this change for https://bugs.launchpad.net/nova/+bug/1739593
09:34:52 openstack Launchpad bug 1739593 in OpenStack Security Advisory "Swapping encrypted volumes can lead to data loss and a possible compute host DOS attack (CVE-2017-18191)" [Undecided,Incomplete]
09:39:25 openstackgerrit Merged openstack/nova master: Test websocketproxy with TLS in the nova-next job https://review.openstack.org/513160
09:58:06 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove unused LOG variables https://review.openstack.org/546097
09:59:16 kashyap Hi, can someone point to PTG Nova agenda etherpad?
09:59:31 cdent kashyap: https://etherpad.openstack.org/p/nova-ptg-rocky
09:59:39 kashyap cdent: Thank you
10:01:27 bauzas meh, LP timeout :(
10:01:33 bauzas hello folks, btw.
10:01:42 openstackgerrit Chris Dent proposed openstack/nova master: WIP: Use nova.db.api directly https://review.openstack.org/543262
10:01:42 openstackgerrit Chris Dent proposed openstack/nova master: Move db MAX constants to own file https://review.openstack.org/543469
10:03:08 cdent brb
10:19:01 openstackgerrit Surya Seetharaman proposed openstack/nova master: Extending delete_cell --force to delete instance_mappings https://review.openstack.org/540073
10:34:49 bauzas mdbooth: others, I need to disappear, but I'm tempted to set https://bugs.launchpad.net/nova/+bug/1740025 as Wontfix
10:34:50 openstack Launchpad bug 1740025 in OpenStack Compute (nova) "LVM Sparse Volumes broken" [Undecided,New]
10:34:51 bauzas agreed ?
10:35:34 mdbooth bauzas: Reading
10:36:22 mdbooth bauzas: Why wontfix?
10:36:55 mdbooth I recall there being severe problems with sparse lvm
10:37:03 mdbooth Not the specifics, though
10:38:53 bauzas mdbooth: because it looks like a feature
10:39:21 bauzas mdbooth: tbc, you can do thin provisioning with Cinder
10:39:23 kashyap I don't know, would you want the reporter to do the whole spec dance?
10:39:36 bauzas but here, the reporter only uses raw LVM
10:39:37 kashyap It's okay to flesh out the details on the bug, without hurrying to close it
10:39:47 mdbooth bauzas: It reads like a bug to me.
10:39:51 kashyap Yeah, to me too.
10:40:05 bauzas so, in case you create LVM volumes having X size
10:40:08 bauzas then, meh
10:40:15 mdbooth Sparse LVM is a thing, and if we were using it correctly, I would expect the scenario described to work.
10:40:39 bauzas mdbooth: why can't the reporter create LVs that are more than 64MB ?
10:41:01 bauzas that's something I don't understand
10:41:02 mdbooth bauzas: I'm guessing because we didn't create the sparse lv correctly.
10:41:20 mdbooth bauzas: As I said, though, I'm pretty sure I recall severe problems in our implementation of sparse lvm.
10:41:20 lyarwood yeah that's not up to the user, n-cpu is creating the lv's
10:41:29 bauzas ah ok
10:41:34 mdbooth severe == How could it ever possibly have worked
10:41:41 bauzas so when nova creates the lv, it asks for a size
10:41:48 bauzas that's not the image
10:41:48 bauzas meh
10:42:04 mdbooth bauzas: It's like creating a sparse file, except lvm
10:42:12 bauzas and then tries to thin provision by itself, while cinder can do that far better
10:42:31 mdbooth It creates a sparse block device, which only allocated blocks from the lvm block pool when they're used
10:42:35 mdbooth Or it's supposed to, anyway
10:42:36 bauzas looks to me we barely support it
10:42:44 mdbooth bauzas: Right.
10:42:54 bauzas yeah I understand the purpose of sparse LVs
10:42:59 mdbooth bauzas: I'm not convinced this has ever worked. However, I'm pretty sure that it was intended to work.

Earlier   Later