Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2017-10-24
11:46:12 bauzas efried: let's provide your thoughts in the series, and see if we have a consensus here
11:46:15 efried bauzas Yes, long term everything from [pci] should move to [devices]. I suppose we could put this VGPU stuff into [pci] for now - but I don't see any reason not to start as we mean to go on.
11:46:30 bauzas efried: please, no
11:46:36 efried bauzas I did leave comments on the change you just uploaded, at PS9
11:46:47 bauzas efried: I mean, PCI != vGPUs
11:46:51 bauzas don't open the wounds :p
11:46:56 efried Totally
11:46:58 openstackgerrit Merged openstack/nova stable/pike: Account for compute.metrics.update in legacy notification whitelist https://review.openstack.org/509439
11:47:22 bauzas honestly, I don't really where it lands, I just want to make sure people agree on it
11:47:37 bauzas really *care
11:47:39 bauzas meh
11:47:52 efried bauzas Yeah, I'd like Jay to weigh in on this.
11:48:12 bauzas also, I did made a compromise, I had to add that option before we're going to use it
11:48:20 efried saw that.
11:48:25 openstackgerrit Merged openstack/nova master: Add alternate hosts https://review.openstack.org/486215
11:48:27 efried Not sure why
11:48:35 openstackgerrit Merged openstack/nova stable/pike: Add functional migrate force_complete test https://review.openstack.org/509924
11:48:41 efried but don't see any reason to object
11:48:44 bauzas I thought oslo.config was somehow having an "experimental" or "next" attribute for the opt, but no
11:48:48 openstackgerrit Merged openstack/nova stable/pike: Add functional for live migrate delete https://review.openstack.org/509925
11:48:55 bauzas efried: because libvirt and xen will both use it
11:49:07 bauzas of course we could just have it in one set
11:49:14 bauzas and wait the set to be merged
11:49:24 bauzas but that could take much longer
11:49:37 efried bauzas Naw, you can just base both of those changes on this one.
11:49:51 bauzas efried: that's correct, hence my commit msgh
11:49:57 bauzas anyway
11:50:00 bauzas let's wait for reviews
11:50:15 bauzas I'm just writing the yippikay libvirt side
11:50:18 efried There's nothing stopping you from having branches in a series.
11:50:31 efried My ksa-adapter series has several
11:50:36 efried :)
11:54:37 efried bauzas Okay, left review. Thanks for the talk.
12:02:02 efried johnthetubaguy yt?
12:24:21 openstackgerrit Sean Dague proposed openstack/nova master: Move kpartx calls to privsep. https://review.openstack.org/500354
12:49:51 openstackgerrit Merged openstack/nova stable/pike: Remove dest node allocations during live migration rollback https://review.openstack.org/509926
12:57:46 cdent efried: did you resolve your resources= thing satisfactorily?
12:58:04 efried cdent Sorry, which resources= thing was that?
12:58:18 cdent [t 2wmI]
12:58:19 purplerbot <efried> Anyone know if we're supposed to handle queryparams with multiple values in the placement API? [2017-10-23 20:04:11.392701] [n 2wmI]
12:58:20 efried cdent Oh, whether you could specify a key multiple times in a querystring?
12:58:36 efried Yeah, the answer was "no", but edleafe thought you would remember why it was decided that way.
12:58:41 cdent the defacto standards with query params is that multiple of the same param should work, but it is not something we really do in nova
12:59:06 mriedem only for sort key/dir i think
12:59:47 efried cdent Well, at least for GET /allocation_candidates and GET /resource_providers?resources= it doesn't work.
12:59:50 efried You'll only get the last one.
13:00:28 cdent yes, that’s a) intentional b) because of the way it is coded c) a fairly arbitrary choice
13:01:05 efried Okay, wfm
13:01:07 cdent the confusion being avoided is whether a list is created by commas or multiple params, and since most people didn’t feel comfy with multiple params, commas was chosen, exclusively
13:01:50 openstackgerrit Merged openstack/nova master: Remove duplicate error info https://review.openstack.org/510719
13:02:39 openstackgerrit Andrey Volkov proposed openstack/osc-placement master: CLI for allocations https://review.openstack.org/457534
13:02:39 openstackgerrit Andrey Volkov proposed openstack/osc-placement master: CLI for inventories https://review.openstack.org/457533
13:02:40 openstackgerrit Andrey Volkov proposed openstack/osc-placement master: CLI for aggregates (v1.1) https://review.openstack.org/505643
13:02:40 openstackgerrit Andrey Volkov proposed openstack/osc-placement master: CLI for usages https://review.openstack.org/457535
13:02:41 openstackgerrit Andrey Volkov proposed openstack/osc-placement master: RP list: member_of and resources parameters (v1.3, v1.4) https://review.openstack.org/511183
13:02:41 openstackgerrit Andrey Volkov proposed openstack/osc-placement master: CLI for resource classes (v1.2) https://review.openstack.org/511182
13:02:42 openstackgerrit Andrey Volkov proposed openstack/osc-placement master: [WIP] CLI for traits (v1.6) https://review.openstack.org/514643
13:02:42 openstackgerrit Andrey Volkov proposed openstack/osc-placement master: [WIP] RP delete inventories (v1.5) https://review.openstack.org/514642
13:02:43 openstackgerrit Andrey Volkov proposed openstack/osc-placement master: [WIP] Allocations set: add project_id and user_id (v1.8) https://review.openstack.org/514645
13:02:43 openstackgerrit Andrey Volkov proposed openstack/osc-placement master: [WIP] Resource class set (v1.7) https://review.openstack.org/514644
13:02:44 openstackgerrit Andrey Volkov proposed openstack/osc-placement master: [WIP] CLI allocation candidates (v1.10) https://review.openstack.org/514647
13:02:44 openstackgerrit Andrey Volkov proposed openstack/osc-placement master: [WIP] Usages per project and user (v1.9) https://review.openstack.org/514646
13:02:45 openstackgerrit priyaduggirala proposed openstack/nova master: Rename parameters in call() of nova/image/glance.py https://review.openstack.org/508533
13:04:43 openstackgerrit Alex Xu proposed openstack/nova master: Add _get_provider_ids_with_any_resource method https://review.openstack.org/514197
13:04:44 openstackgerrit Alex Xu proposed openstack/nova master: Add ProviderSummaryList object https://review.openstack.org/514198
13:04:44 openstackgerrit Alex Xu proposed openstack/nova master: Add _get_traits_by_rp_ids method https://review.openstack.org/511184
13:04:45 openstackgerrit Alex Xu proposed openstack/nova master: Add AggregatedProviderSummary and AggregatedProviderSummaryList objects https://review.openstack.org/514200
13:04:45 openstackgerrit Alex Xu proposed openstack/nova master: Add more caches for the ProviderSummary https://review.openstack.org/514199
13:04:46 openstackgerrit Alex Xu proposed openstack/nova master: Enable _get_usages_by_provider_and_rc not filter on the resource class id https://review.openstack.org/514649
13:04:46 openstackgerrit Alex Xu proposed openstack/nova master: placement: rewrite AllocationCandidates.get_by_filters https://review.openstack.org/479766
13:04:47 openstackgerrit Alex Xu proposed openstack/nova master: Add as_allocation_request_obj method to AggregatedProvierSummary obj https://review.openstack.org/514651
13:04:47 openstackgerrit Alex Xu proposed openstack/nova master: Add has_resources method to the AggregatedProviderSummary object https://review.openstack.org/514650
13:11:09 mriedem sdague: at the ptg you said you were good with getting this az name schema fix into stable https://review.openstack.org/#/q/I9b0d8e8d4b3ab2cb3d578c22fa259e0e7c0d325b
13:12:39 belmoreira dansmith: mriedem: I'm looking on how to have placement with cellsV1. Need some guidance.
13:15:13 belmoreira My understanding is that I will need to have a separated placement service + nova_api DB + keystone for each child cell. Is this correct?
13:22:40 mriedem belmoreira: i've always thought of placement as global to nova, but it's only used by the "cell" filter scheduler i guess, so it might make sense to only be per-child cell with cells v1
13:22:50 mriedem the global api parent cell scheduler won't rely on placement
13:23:13 mriedem belmoreira: i don't know about keystone being per child cell
13:23:23 mriedem is that what you already do today?
13:23:51 mriedem nova_api db should be global
13:24:01 mriedem since build requests are created in the api cell
13:24:22 mriedem belmoreira: which release are you targeting here?
13:24:40 belmoreira mriedem: let me clarify
13:25:36 belmoreira I'm running nova newton release. We have one nova_api DB (requirement in newton) that is global
13:26:16 belmoreira when upgraded I didn't enable placement but it's a requirement before moving to Ocata/Pike
13:27:07 mriedem belmoreira: yeah so in ocata, the only things that talk to placement are nova-scheduler in the cell and nova-compute
13:27:52 bauzas we always thought placement as being global, like we also said for the scheduler
13:27:53 mriedem so placement could be deployed per-cell, but if you can, it's probably smart to deploy it globally to make the transition easier to cells v2
13:28:00 belmoreira because nova-scheduler is per cell in cellsV1 do I need a placement per cell?
13:28:23 mriedem bauzas: with cells v1 there are 2 levels of scheduling
13:28:27 bauzas mriedem: if placement would be per cell, that would mean 2 layer of scheduling, which I disagree
13:28:33 bauzas mriedem: yup I know and I don't like it :)
13:28:34 mriedem there already is
13:28:48 mriedem like i said, if you deploy placement globally, i think it'll be easier in the long-run
13:28:53 mriedem to transition to cells v2
13:28:56 belmoreira I was always thinking in the placement as global... but I'm not seeing how to make it work with cellsV1
13:29:00 bauzas mriedem: but the consensus we had long in the past with alaski and dansmith was that 2 scheduling layers was a terrible idea
13:29:01 mriedem b/c with cells v2 there is only 1 scheduler
13:29:25 dansmith belmoreira: why can't you point all the child cells at the global api?
13:29:26 mriedem belmoreira: just think of it like any other global service

Earlier   Later