Earlier  
Posted Nick Remark
#openstack-nova - 2018-03-14
02:55:44 openstackgerrit Zhenyu Zheng proposed openstack/nova-specs master: Allow abort live migrations in queued status https://review.openstack.org/536722
02:56:39 Spaz-Home Moving my second commit back down to subteam review. I self -1'ed it for the moment. Will fix unit tests tomorrow.
05:46:41 openstackgerrit OpenStack Proposal Bot proposed openstack/nova master: Updated from global requirements https://review.openstack.org/552774
05:55:14 openstackgerrit OpenStack Proposal Bot proposed openstack/os-vif master: Updated from global requirements https://review.openstack.org/533918
06:17:36 openstackgerrit OpenStack Proposal Bot proposed openstack/nova master: Imported Translations from Zanata https://review.openstack.org/548772
06:34:25 openstackgerrit Zhenyu Zheng proposed openstack/nova master: nova-manage db archive_deleted_rows is not multi-cell aware https://review.openstack.org/507486
08:14:31 openstackgerrit sahid proposed openstack/nova master: libvirt: slow live-migration to ensure network is ready https://review.openstack.org/497457
08:27:43 openstackgerrit Jie Li proposed openstack/nova-specs master: Support volume-backed server rebuild https://review.openstack.org/532407
08:36:43 openstackgerrit sahid proposed openstack/nova-specs master: libvirt: add support for virtio-net rx/tx queue sizes https://review.openstack.org/539605
09:05:42 openstackgerrit Chris Dent proposed openstack/nova master: Optional separate database for placement API https://review.openstack.org/362766
09:05:43 openstackgerrit Chris Dent proposed openstack/nova master: Isolate placement database config https://review.openstack.org/541435
09:05:43 openstackgerrit Chris Dent proposed openstack/nova master: Move placement exceptions into the placement package https://review.openstack.org/549862
09:08:01 kashyap mdbooth: Saw the change last evening was letting Zuul go through its course.
09:20:34 openstackgerrit Chris Dent proposed openstack/nova master: Move placement exceptions into the placement package https://review.openstack.org/549862
09:20:35 openstackgerrit Chris Dent proposed openstack/nova master: Optional separate database for placement API https://review.openstack.org/362766
09:20:35 openstackgerrit Chris Dent proposed openstack/nova master: Isolate placement database config https://review.openstack.org/541435
09:27:18 bauzas man, I forgot my manners
09:27:25 bauzas good morning Nova
09:35:52 openstackgerrit Yikun Jiang (Kero) proposed openstack/nova-specs master: Complex (Anti)-Affinity Policies https://review.openstack.org/546925
09:37:40 pooja_jadhav cdent: Hi
09:38:24 cdent good morning pooja_jadhav
09:39:14 pooja_jadhav cdent: actually i want discuss with you regarding shared resource provider thing.
09:39:27 pooja_jadhav cdent: very gm :)
09:40:44 cdent pooja_jadhav: sure, but you should be aware that share providers are still a bit of a work in progress. Most of the functionality is nearly there, but nothing really uses it yet.
09:41:32 cdent What's your plan?
09:42:19 pooja_jadhav cdent: planning to test correct disk usage or not on shared storage
09:42:46 pooja_jadhav cdent : cdent: i have configured nfs backend, and created shared resource provider, but when i booted the instance it failing at line [1] https://github.com/openstack/nova/blob/master/nova/scheduler/manager.py#L138
09:43:41 cdent pooja_jadhav: is there an aggregate in place that associates the shared storage provider with one or more compute nodes that use it?
09:43:55 pooja_jadhav yes, aggregate is there
09:44:18 pooja_jadhav its not getting allocation request
09:44:52 pooja_jadhav when i create the instance, that instance going into error state
09:46:05 pooja_jadhav actually, where am i missing something, i am not getting :(
09:47:01 cdent tetsuro recently wrote an email with some updated information on the state of sharing providers, let me find that. It may be that what you're trying to do simply doesn't work in /allocation_candidates yet
09:47:36 cdent this message: http://lists.openstack.org/pipermail/openstack-dev/2018-March/128141.html
09:47:39 pooja_jadhav ohkk
09:48:47 cdent That first item he lists, about the resource class existing in both places, may be part of the problem? Is the compute node reporting disk inventory ?
09:52:38 pooja_jadhav i have checked the db, inventory record i have created that exists
09:52:58 pooja_jadhav but to check that compute node is reporting it or not?
09:53:38 pooja_jadhav but how to check that compute node is reporting that inventory or not?
09:55:17 cdent pooja_jadhav: there's an osc-placement client now, so you can use that if you like, or use curl or another tool to interact with the placement api, or look in the database (there will be inventory rows that are associated with resource providers by resource provider id)
09:56:50 pooja_jadhav yes, i have checked in the database, there is inventory which i have created with the resource provider which is created by me.
10:00:52 cdent pooja_jadhav: do you have disk inventory from both a compute node and the shared provider or only the shared provider?
10:01:33 openstackgerrit Chris Dent proposed openstack/nova master: Update contributor/placement.rst to contemporary reality https://review.openstack.org/552860
10:01:45 cdent stephenfin, gibi : quick doc improvement ^
10:03:52 cdent stephenfin: I also reordered some of the remaining placement-extraction code that you recently helped merge so that the current "next one" is ahead of the optional db stuff: https://review.openstack.org/#/c/549862/
10:04:10 pooja_jadhav cdebt : disk inventory from both a compute node and the shared provider (bcz I have created only one inventory record for resource provider id 2 but in that table already 3 more records exists means 3 inventory records from resource provider id 1)
10:05:17 cdent pooja_jadhav: in that case I think you're hitting the problem described here https://review.openstack.org/#/c/533396 it is possible for you try again with that code in place?
10:05:33 cdent I'm going to get some more coffee but will be back shortly
10:08:24 pooja_jadhav cdent: sure
10:10:04 pooja_jadhav i will try
10:18:24 cdent pooja_jadhav: let me know how it goes, I suspect there will be a few more issues, as shared providers hasn't received the same attention (yet) that other use cases have
10:25:53 openstackgerrit Chris Dent proposed openstack/nova master: Fix allocation_candidates not to ignore shared RPs https://review.openstack.org/533396
10:25:54 openstackgerrit Chris Dent proposed openstack/nova master: Test alloc_cands with indirectly sharing RPs https://review.openstack.org/519601
10:25:54 openstackgerrit Chris Dent proposed openstack/nova master: Support relay RP for allocation candidates https://review.openstack.org/533437
10:26:25 cdent pooja_jadhav: in that ^ stack is an update version that resolves the merge conflicts, which you'll want if you're working from today's master
10:27:26 pooja_jadhav cdent : i have applied the patch https://review.openstack.org/#/c/533396, but facing same issue
10:27:44 cdent :(
10:28:35 pooja_jadhav when i hit nova show then it shows error in fault section [1]http://paste.openstack.org/show/700903/
10:29:24 cdent If you can write up a bug that might be the best thing at this point. I havent got a clear picture of exactly what you're doing and having the replication strategy written down in a bug will make it easier to understand
10:30:08 cdent ah, I hadnt understood you were using a custom resource class, that's an important bit of data. Do you have a log of the requests made to the placement service, it would be useful to see what the GET /allocation_candidartes query is
10:31:23 cdent pooja_jadhav: this bug may be related: https://bugs.launchpad.net/nova/+bug/1705231
10:31:24 openstack Launchpad bug 1705231 in OpenStack Compute (nova) "Placement returns no allocation candidate for request that needs both compute resources and custom shared resources" [High,Fix released] - Assigned to Chris Dent (cdent)
10:43:25 openstackgerrit Stephen Finucane proposed openstack/nova master: conf: Correct documentation for '[pci] passthrough_whitelist' https://review.openstack.org/552874
10:43:27 stephenfin lyarwood, sean-k-mooney: ^
10:43:36 stephenfin I'll probably look for that to be backported if all is ok
10:46:11 lyarwood stephenfin: cool yeah that would be great, will need a bug if you have time, happy to quickly write one if not, I did mean to do this yesterday :|
10:47:19 stephenfin lyarwood: I'm working on the NUMA-aware vSwitch spec this morning, so if you're happy to write up said bug I'd appreciate it :)
11:39:05 gibi afternoon nova
11:39:48 gibi cdent: thanks for the placement doc update, I +2d it
11:57:05 openstackgerrit Merged openstack/nova master: Update contributor/placement.rst to contemporary reality https://review.openstack.org/552860
12:27:35 artom bauzas, sahid, could you take a look at https://review.openstack.org/#/c/552722/ when you get a chance? It's the infamouse live migration with CPU pinning spec
12:27:56 artom sahid, you weren't at PTG, but we basically agreed to start over, with a spec, since Nikola's patch is too hard to review/merge at this point
12:28:21 artom jaypipes, ^^ dunno if you're around this early, but your input would be appreciated as well
12:36:07 openstackgerrit Nguyen Hai proposed openstack/nova-specs master: Enhance nova-specs webpage and clean up repo https://review.openstack.org/551802
12:46:05 jaypipes artom: yep, will look shortly.
12:46:11 jaypipes thx for the heads up
12:47:14 artom jaypipes, cheers :)
13:11:09 openstackgerrit Eric Fried proposed openstack/nova master: placement: generation in provider aggregate APIs https://review.openstack.org/548249
13:11:10 openstackgerrit Eric Fried proposed openstack/nova master: placement: Return new provider from POST /rps https://review.openstack.org/548934
13:11:10 openstackgerrit Eric Fried proposed openstack/nova master: Stop assuming initial provider generation is 0 https://review.openstack.org/548975
13:12:01 jaypipes efried: ^ that ready to go now?
13:12:09 efried jaypipes: First two, yes.
13:12:17 efried jaypipes: Quick, before edleafe's!
13:22:12 edleafe efried: no rush, working on alex_xu_'s comments
13:44:55 alex_xu_ edleafe: the only help I can give is to review efried's patch :)
13:45:04 efried hah!
13:49:18 sar So I had an issue where i couldn't delete an instance attached to a previously migrated volume. I get an error where it says it can't find the volume id. Turns out it doesn't update the volume_id in the json stored in block_device_mapping during volume migration. Can someone help me verify if this can be considered a bug? See around line 5656 here: https://git.openstack.org/cgit/openstack/nova/tree/nova/compute/manager.py
13:49:18 sar Shouldn't there be a line such as this? : new_cinfo['volume_id'] = save_volume_id
14:01:49 edleafe alex_xu_: should have an update soon. Until then, have at efried!
14:04:01 mriedem gibi: i'm going through https://review.openstack.org/#/c/502306/ if you want to hold off on updating it
14:04:56 cdent thanks jaypipes for saying what you did on the low-level cache spec
14:05:41 jaypipes cdent: yw
14:06:16 cdent I tried to read that whitepaper that's reference before I made a judgement and dissolved in a sea of acronyms
14:06:38 cdent but my gut reaction was "oh, you've got to be kidding me"
14:10:21 openstackgerrit Dan Smith proposed openstack/nova master: Add --by-service to discover_hosts https://review.openstack.org/552691
14:15:46 stephenfin jaypipes: Low-level cache spec?
14:17:23 jaypipes stephenfin: https://review.openstack.org/#/c/502575/1/specs/pike/approved/cache-as-a-resource-with-rdt.rst@101
14:18:09 stephenfin eew
14:18:13 stephenfin I change my mind
14:18:14 dansmith I'm going tp propose a spec soon to let you reserve a single byte of physical memory

Earlier   Later