Tuesday, 2018-06-05

openstackgerritTsuyoshi Nagata proposed openstack/nova master: openstack server add volume fails over 26vols  https://review.openstack.org/56747200:09
openstackgerritChris Dent proposed openstack/nova master: [placement] Do not import oslo_service for log_options  https://review.openstack.org/57223100:14
*** cdent has quit IRC00:20
*** tetsuro has joined #openstack-placement00:42
openstackgerrittianhui proposed openstack/nova master: Fix bug for hypervisors  https://review.openstack.org/57206301:31
*** cdent has joined #openstack-placement01:56
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Fix wrong commands in launch-from-volume doc  https://review.openstack.org/57224102:16
*** cdent has quit IRC02:27
openstackgerritZhenyu Zheng proposed openstack/nova master: Use ThreadPoolExecutor for max_concurrent_live_migrations  https://review.openstack.org/56350502:48
*** alex_xu has quit IRC03:00
*** alex_xu has joined #openstack-placement03:01
openstackgerritBhagyashri Shewale proposed openstack/nova master: libvirt: Don't report DISK_GB if sharing  https://review.openstack.org/56045904:47
openstackgerritChris Dent proposed openstack/nova master: [placement] Do not import oslo_service for log_options  https://review.openstack.org/57223105:10
openstackgerritMerged openstack/nova stable/ocata: libvirt: Report the virtual size of RAW disks  https://review.openstack.org/56838205:38
openstackgerritZhenyu Zheng proposed openstack/nova master: WIP abort live migration in queue.  https://review.openstack.org/56854206:30
*** tssurya has joined #openstack-placement06:45
openstackgerrittianhui proposed openstack/nova master: Fix bug to doc  https://review.openstack.org/57226806:47
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Microversion 2.63 - Use new format policy in server group  https://review.openstack.org/56753407:11
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: Initial change set of z/VM driver  https://review.openstack.org/52338707:12
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: Spawn and destroy function of z/VM driver  https://review.openstack.org/52765807:12
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: add snapshot function  https://review.openstack.org/53424007:12
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: add power actions  https://review.openstack.org/54334007:12
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: add get console output  https://review.openstack.org/54334407:12
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Fix wrong commands in launch-from-volume doc  https://review.openstack.org/57224107:20
openstackgerritChris Dent proposed openstack/nova master: Re-base placement object unit tests on NoDBTestCase  https://review.openstack.org/57227907:28
openstackgerritChris Dent proposed openstack/nova master: Move db using provider unit tests to functional  https://review.openstack.org/57228007:28
openstackgerritChris Dent proposed openstack/nova master: Move db using allocation unit tests to functional  https://review.openstack.org/57228107:28
openstackgerritChris Dent proposed openstack/nova master: Remove nova dependencies from test_resource_provider  https://review.openstack.org/57228207:28
openstackgerritNaichuan Sun proposed openstack/nova master: xenapi(N-R-P): Add API to support vgpu resource provider create  https://review.openstack.org/52031307:56
*** ttsiouts has joined #openstack-placement08:09
*** ttsiouts has quit IRC08:22
*** ttsiouts has joined #openstack-placement08:31
*** ttsiouts has quit IRC08:32
openstackgerritjichenjc proposed openstack/nova master: Enhance api-guide general info some updates  https://review.openstack.org/56177308:34
*** ttsiouts has joined #openstack-placement08:35
*** e0ne has joined #openstack-placement08:37
openstackgerritjichenjc proposed openstack/nova master: Trivial: let internal use only func has _ prefix  https://review.openstack.org/57230408:37
*** bhagyashri_s has joined #openstack-placement08:38
openstackgerritGhanshyam Mann proposed openstack/nova master: Fix some wrong urls in doc  https://review.openstack.org/57114708:39
openstackgerritjichenjc proposed openstack/nova master: Enhance api-guide general info some updates  https://review.openstack.org/56177308:54
*** ttsiouts has quit IRC09:10
*** takashin has left #openstack-placement09:30
openstackgerritLee Yarwood proposed openstack/nova stable/queens: Allow cinderv2 endpoints within the request context catalog  https://review.openstack.org/57221309:41
*** ttsiouts has joined #openstack-placement09:47
*** ttsiouts has quit IRC09:52
openstackgerritStephen Finucane proposed openstack/nova-specs master: Add 'numa-aware-vswitches' spec  https://review.openstack.org/54129009:56
*** ttsiouts has joined #openstack-placement10:04
openstackgerritTheodoros Tsioutsias proposed openstack/nova-specs master: Add PENDING vm state  https://review.openstack.org/55421210:08
openstackgerritTheodoros Tsioutsias proposed openstack/nova-specs master: Enable rebuild for instances in cell0  https://review.openstack.org/55421810:27
openstackgerritBrianna Poulos proposed openstack/nova master: Implement certificate_utils  https://review.openstack.org/47994910:37
openstackgerritBrianna Poulos proposed openstack/nova master: Plumb trusted_certs through libvirt driver image paths  https://review.openstack.org/56126210:37
openstackgerritBrianna Poulos proposed openstack/nova master: Add trusted_image_certificates to REST API  https://review.openstack.org/48620410:37
openstackgerritBrianna Poulos proposed openstack/nova master: Add notification support for trusted_certs  https://review.openstack.org/56326910:37
openstackgerritBrianna Poulos proposed openstack/nova master: Add certificate validation docs  https://review.openstack.org/56015810:37
openstackgerritBrianna Poulos proposed openstack/nova master: Plumb trusted_certs through libvirt driver image paths  https://review.openstack.org/56126210:42
openstackgerritBrianna Poulos proposed openstack/nova master: Add trusted_image_certificates to REST API  https://review.openstack.org/48620410:42
openstackgerritBrianna Poulos proposed openstack/nova master: Add notification support for trusted_certs  https://review.openstack.org/56326910:42
openstackgerritBrianna Poulos proposed openstack/nova master: Add certificate validation docs  https://review.openstack.org/56015810:42
openstackgerritLee Yarwood proposed openstack/nova stable/pike: libvirt: slow live-migration to ensure network is ready  https://review.openstack.org/55903210:46
*** ttsiouts has quit IRC10:55
openstackgerritLee Yarwood proposed openstack/nova stable/ocata: libvirt: slow live-migration to ensure network is ready  https://review.openstack.org/55903411:04
*** bhagyashri_s has quit IRC11:16
*** bhagyashri_s has joined #openstack-placement11:17
*** edmondsw has joined #openstack-placement11:19
openstackgerritChen Hanxiao proposed openstack/nova master: sync_guest_time: use the proper errno  https://review.openstack.org/57234611:26
*** tetsuro has quit IRC11:26
*** ttsiouts has joined #openstack-placement11:37
*** finucannot is now known as stephenfin12:44
*** mriedem has joined #openstack-placement12:46
*** ttsiouts has quit IRC12:48
*** ttsiouts has joined #openstack-placement12:49
openstackgerritMatt Riedemann proposed openstack/nova master: Transform instance.exists notification  https://review.openstack.org/40366012:51
openstackgerritJay Pipes proposed openstack/nova-specs master: Standardize CPU resource tracking  https://review.openstack.org/55508113:00
*** ttsiouts has quit IRC13:45
*** ttsiouts has joined #openstack-placement13:58
openstackgerritMatt Riedemann proposed openstack/nova-specs master: Add 'numa-aware-vswitches' spec  https://review.openstack.org/54129014:09
openstackgerritNaichuan Sun proposed openstack/nova master: xenapi(N-R-P): Add API to support vgpu resource provider create  https://review.openstack.org/52031314:11
openstackgerritNaichuan Sun proposed openstack/nova master: xenapi(N-R-P): Add API to support vgpu resource provider create  https://review.openstack.org/52031314:23
openstackgerritNaichuan Sun proposed openstack/nova master: xenapi(N-R-P):Get vgpu info from `allocations`  https://review.openstack.org/52171714:26
openstackgerritNaichuan Sun proposed openstack/nova master: xenapi(N-R-P): support compute node resource provider update  https://review.openstack.org/52104114:27
*** mriedem has quit IRC14:53
*** mriedem has joined #openstack-placement14:53
efriedjaypipes: I've been assuming you're going to be the one to host the hangout, yah?14:53
* gibi will try to call in as well14:55
*** cdent has joined #openstack-placement14:58
jaypipesefried, gibi, cdent, edleafe, dansmith, mriedem, melwitt, bauzas, alex_xu: hangout for the "migration API" in placement: https://hangouts.google.com/call/N7Pb0gg01m30ep7hHzCNAAEE15:01
bauzasnow ?15:01
bauzasjaypipes: now ?15:01
cdentyes now15:01
jaypipescdent: coming back?15:03
cdentyeah, my sound is busted, so gotta fix that15:03
dansmithcdent: nice.15:08
openstackgerritSurya Seetharaman proposed openstack/nova-specs master: Handling a down cell  https://review.openstack.org/55736915:08
openstackgerritTheodoros Tsioutsias proposed openstack/nova-specs master: Add PENDING vm state  https://review.openstack.org/55421215:19
jaypipescdent: you speaking? can't hear you...15:22
cdentjaypipes: nope, not yet, everybody else keeps saying what I would say15:22
jaypipes:)15:22
edleafe /win 1615:24
*** ttsiouts has quit IRC15:39
*** ttsiouts has joined #openstack-placement15:44
mriedemif you can't change the parent provider uuid on an RP, we should probably call that out in the api reference https://developer.openstack.org/api-ref/placement/#update-resource-provider15:50
mriedemsince it's not clear to me15:50
*** e0ne has quit IRC15:52
mriedembtw, i don't see anything in the handler code that prevents you from updating the parent_provider_uuid on an existing rp15:53
*** tssurya has quit IRC15:57
edleafemriedem: yeah, I just looked too. Looks like can reparent an RP with PUT15:57
openstackgerritMerged openstack/nova-specs master: Follow the new PTI for document build  https://review.openstack.org/55180216:13
*** ttsiouts has quit IRC16:15
efriededleafe, mriedem: https://github.com/openstack/nova/blob/master/nova/tests/functional/api/openstack/placement/gabbits/resource-provider.yaml#L58816:23
mriedemefried: ok that's way down in the db update code16:26
mriedemwould have been much more easy to find if it were controlled in the API16:26
efriedI didn't look, but iirc it's an arbitrary check, not there for any technical reason.16:27
efriedi.e. something we could remove easily (with a microversion)16:27
mriedemhttp://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/placement/objects/resource_provider.py#n102616:27
mriedemsure, just need to call it out in the api-ref as a limitation i think; i'll push a patch16:27
efriedight16:28
openstackgerritMerged openstack/nova master: Fix bug for hypervisors  https://review.openstack.org/57206316:35
openstackgerritMerged openstack/nova master: Fix bug to doc  https://review.openstack.org/57226816:36
gibiefried: as soon as you allow reparenting you allow moving RPs inbetween trees and that might break existing allocations that requires to have the provider within the same tree16:36
cdentjaypipes: this is the start of a series which cleans out db stuff from the test_resource_provider unit test. https://review.openstack.org/#/c/572279/  That ought to lessen some of the test changes you needed to make in the consumer gen tree.16:39
edleafegibi: what about allowing reparenting within the same tree?16:40
efriedgibi: What about existing allocations requires them to be in the same tree?16:40
efriedThat was weird, I was like, "did I press Enter?  I didn't *think* I pressed Enter.  Enter.  Oh.  Hi Ed."16:41
jaypipescdent: ooh, cool, ty sir!16:41
gibiedleafe, efried: yeah, if we limit that the new parent can only be in the same tree as the old that might help16:43
efriedgibi: I'm asking why it's a limitation that you can't move an allocation from one tree to another.16:43
efriedI mean, makes sense in the nova universe (for now).  But purely from a placement standpoint... why?16:44
gibiefried: because the server create request which resulted in the allocations  assumes that the resources are from the same compute tree16:44
gibiefried: ahh, gotcha16:44
gibiefried: so nova needs to make sure that the reparenting of a server allocation does not break the assumptions of nova having resources from a single tree16:45
efriedgibi: I don't think we're considering removing the restriction; just kind of noticing that it's there and reevaluating it.  The path of least resistance will be to leave it alone until we hear some use case that needs to do it.16:47
gibistill I feel that when the placement was called to provide allocation candidates placement made the same assumption, i.e. unnumbered group expected to be fulfilled from the same tree16:47
gibiefried: OK, that sound enough for me now :)16:47
*** e0ne has joined #openstack-placement16:48
*** e0ne_ has joined #openstack-placement16:50
openstackgerritMerged openstack/nova stable/queens: Allow cinderv2 endpoints within the request context catalog  https://review.openstack.org/57221316:52
*** e0ne has quit IRC16:54
openstackgerritMerged openstack/nova-specs master: Add 'numa-aware-vswitches' spec  https://review.openstack.org/54129016:56
*** cdent has quit IRC16:59
*** cdent_ has joined #openstack-placement16:59
*** e0ne_ has quit IRC17:08
edleafeefried: I definitely think we should remove (or at least relax) that restriction17:11
efriededleafe: I don't disagree, but until we have a compelling use case for it, that's just work on already-full plates.17:11
efriedneeds to be a microversion regardless - we can't ex-post-facto it - so...17:12
* cdent_ suddenly hungry17:12
*** cdent_ is now known as cdent17:13
edleafeefried: well, the use case discussed in the hangout is a potential reality. IAC, I'm not saying do it now, but just keep in mind that it's certainly possible17:13
*** e0ne has joined #openstack-placement17:14
efriednod17:20
*** tssurya has joined #openstack-placement17:22
openstackgerritChris Friesen proposed openstack/nova-specs master: Add support for emulated virtual TPM  https://review.openstack.org/57111117:31
openstackgerritMatt Riedemann proposed openstack/nova master: api-ref: mention that you can't re-parent a resource provider  https://review.openstack.org/57250117:45
openstackgerritDan Smith proposed openstack/nova master: Change consecutive build failure limit to a weigher  https://review.openstack.org/57219518:18
*** edmondsw has quit IRC18:41
*** edmondsw has joined #openstack-placement19:07
*** edmondsw_ has joined #openstack-placement19:12
*** edmondsw has quit IRC19:15
openstackgerritDan Smith proposed openstack/nova master: Change consecutive build failure limit to a weigher  https://review.openstack.org/57219519:38
jaypipesefried: still working on tetsuro's patches...19:42
jaypipesefried: just letting you know.19:42
*** e0ne has quit IRC19:54
efriedjaypipes: ack, thx.  Still working on that spec :P20:09
*** e0ne has joined #openstack-placement20:10
*** edmondsw_ is now known as edmondsw20:10
jaypipesefried: thx20:11
*** e0ne has quit IRC20:14
*** e0ne has joined #openstack-placement20:21
*** e0ne has quit IRC20:25
efriedjaypipes: how is the virt driver getting allocation data?  Is he allowed to query placement, or does update_provider_tree get a new arg?20:25
jaypipesefried: see my review on https://review.openstack.org/#/c/567113/. I have modified that patch locally with tested code from my review comments. I'm happy to rebase that patch series and fix up what I believe are mistakes in it to get it going. Please check it out.20:35
efried...20:35
jaypipesefried: good question. :)20:36
jaypipesefried: we could provide them as part of the ProviderTree I guess..20:37
jaypipesefried: though we're already getting long in the tooth for that object, IMHO.20:37
efriedjaypipes: Enhancing ProviderTree or a separate arg to upt, either would wfm, and I think that's better than upt doing placement GETs.20:39
efriedjaypipes: separate arg, methinks.  ProviderTree is organized by provider.  We want the allocs organized by consumer (even though the allocs we want are the ones related to the providers in the tree)20:41
jaypipesefried: ack, makes sense to me.20:43
efriedjaypipes: Without a new query, the alloc info is going to be kind of tricky/expensive to get.  We need to GET /resource_providers/{rp_uuid}/allocations for all rps in the local tree (not sharing providers), and *then* create a set of all consumers from that so we can GET /allocations/{consumer_uuid} for each.20:44
jaypipesefried: we really only need to do the GET /resource_providers/{uuid}/allocations I think.20:47
jaypipesefried: and pass a dict of those (keyed by rp_uuid) to the upt.20:47
efriedjaypipes: We would have to do that for all associated providers, including sharing, else we would be missing the sharing providers' allocations.  BUT that means we're also getting sharing provider allocations against consumers on other hosts.20:48
efriedhence the two-step.20:48
jaypipesefried: yeah, eww.20:49
efriedjaypipes: Re https://review.openstack.org/#/c/567113/ -- it's not clear to me whether your reworked sql actually fixes a bug or is just more efficient.  If there's an actual problem with forbidden traits, we should have a test case to demonstrate it.20:55
jaypipesefried: we do have test cases that hit it. test_all_local(), after tetsuro's patch links up get_trees_matching_all() into AllocationCandidates.get_by_requests() actually tickles the SQL code there. Tetsuro just changed the INNER JOIN to a LEFT JOIN thinking that was appropriate, but it isn't (as I tried to explain in the review there).21:04
efriedjaypipes: Okay, so if it's not functionally wrong, for the sake of expediency, could we do the sql rejigger in a fup?21:05
efriedjaypipes: and the other nits21:05
jaypipesefried: you mean all the changes that aren't relevant to the actual patch?21:05
efriedjaypipes: I didn't look too closely; if that's all they are, then again, would it be possible to let 'em slide for the sake of getting this merged today?21:06
efriednits like doc rewords, param switch on _get_usages_by_provider...21:07
jaypipesefried: the "param switch" changed the behaviour of the method entirely, and for no reason.21:08
jaypipesefried: I might be willing to "let this slide", but I need to check the following patches first, ok? I am currently reviewing them.21:08
efriedjaypipes: Roger that.21:09
efriedI'm just worried about finding someone competent to review a massive sqla block.  If we get it merged and functionally working, then it's okay if that takes a few days.21:10
*** tssurya has quit IRC21:10
jaypipesefried: and I am worried that s/join/outerjoin/ is really just a kludge to fix something further down this patch stack.21:11
efriedack21:11
jaypipesefried: so as soon as I verify that isn't the case, I'll push it through.21:11
efriedcool beans21:11
*** tssurya has joined #openstack-placement21:12
jaypipesefried: heh, so pretty much as I suspected... https://review.openstack.org/#/c/567150/15/nova/api/openstack/placement/objects/resource_provider.py21:12
jaypipes^^ the _check_traits_for_alloc_requests() method isn't necessary if the SQL is done correctly in get_trees_matching_all().21:13
efriedahh21:13
efriedjaypipes: Okay, so two choices:  1) You fix it up, and we have to find a third reviewer; 2) Tetsuro fixes it up, with time zone pain.21:14
efriedjaypipes: If it was anyone other than Tetsuro, I would shy away from #2, but I have faith that he'll turn it around correctly in one shot.21:15
jaypipesefried: lemme check one thing locally on the following patch.21:16
*** tssurya has quit IRC21:17
cdentdansmith, jaypipes, efried : when you have a minute I could do with some input on the desired interface to this non-http placement tool. Beacuse of the way policy is being handled now, deploying the full wsgi stack (with whatever conf you like) and intercepting it is pretty much the simplest thing. The question becomes: what interface do we want to provide to users? Some options:21:25
cdenta) just the url of the service they do the rest with requests21:26
cdentb) some stubbed out methods that themselves use requests21:26
cdentc) the ReportClient21:26
cdentd) your better idea21:26
cdent"do the rest with requests" is my new bumper sticker, tshirt, laptop decoration21:27
efriedcdent: Is it possible for it to look like the handler methods?21:27
efriedum, sorry, those guys take raw request/response thingies, don't they?21:27
cdentyes21:27
efriedWhich isn't what I was going for.21:27
cdentso something needs to mediate a bit21:27
efriedI like the idea of being able to call it basically the same way we call the REST APIs.21:28
efriedis that "do the rest with requests" ?21:28
cdentpretty much21:28
efriedin report client we do it via adapter, which is a pretty thin wrapper around requests.21:29
efriedIf there were a way to do it via adapter, then client code (like the report client) could run against either one just by changing out the setup.21:30
cdentthe reason to not do it with adapter is because we'd have to mock out keystone. not necessarily a bad thing, but maybe ugly21:30
dansmithcdent: personally, I would like something like placement.allocations.update(rp_uuid, body)21:30
efriedcdent: Well, right, I was thinking a thing that behaves like adapter, but doesn't have to mock out keystone.21:30
cdentdansmith: your suggestion maps to "b", yes?21:31
dansmithcdent: I don't think so21:32
dansmithcdent: you really mean open a socket and use requests to talk to localhost or something?21:32
cdentoh. how so?21:32
cdentdansmith: the wip is using wsgi-intercept (in the same way the funcitional tests do) so that it can host the entire wsgi stack (for sake of context handling). It doesn't have to do that, we can construct things more directly, but it was an easy option.21:34
*** edmondsw has quit IRC21:34
cdentso it's not a real socket21:34
cdentbut it's real http21:34
*** edmondsw has joined #openstack-placement21:34
dansmithokay I've never looked at how the fixture works, so I dunno,21:35
efriedNot as much a fan of placement.{noun(s)}.{verb}(identifiers, payload) because we're having to invent a whole set of method specs and map them to placement calls.  Do they map 1:1?  Maybe at first...  How hard will it be to keep them in sync moving forward?21:35
efriedIf we make it look just like actual REST calls, then (in addition to the drop-in-ability mentioned above) we get all updates for free in the shim.21:35
dansmithbut it's hard for me to wrap my brain around using it that directly internally21:35
dansmithefried: yeah, I guess I'd hope that if we have a library, we have a real library that provides a nice-to-use interface and not just "bindings"21:36
efrieddansmith: The "placement client" we've been trying to avoid...21:36
dansmiththat would be my preference.. something pythonic and not something , uh, webthonic21:36
dansmithefried: no, not really (IMHO)21:36
dansmithefried: it would be more like the abstraction that the http handlers sit on top of21:37
cdentdansmith: are you imagining that this might _actually_ (as opposed to just might) become a thing beyond its value for /migrator ?21:37
dansmithit's cool if everyone just uses requests for the actual api21:37
dansmithcdent: yeah?21:37
efriedI mean, the design of the pythonic front end would/could end up looking just like a hypothetical placement client.  Only difference is whether the HTTP layer is in front or behind.21:37
efriedcdent, dansmith: Oh, yeah, this is one of the things cinder wanted to have for their usage of standalone placement.21:38
dansmithright21:38
efrieddefinitely applicability beyond migrator21:38
cdentright, but that want is _very_ contingent21:38
*** edmondsw has quit IRC21:38
dansmithuntil we split you can play fast and loose with this a bit, and a wsgi hack to let us do what we need internally is permissable,21:39
dansmithpermissible?21:39
dansmithanyway21:39
cdentand I would hope that going down that road (in process use of placement) would result from quite a bit of consideration21:39
smcginniscdent: I do need to get the discussion going again.21:39
smcginnisCinder meeting is tomorrow, FWIW.21:39
dansmithif this becomes an external interface, which I kinda think will be useful for a variety of things (i.e. any nova-manage transitions we have to do in the future with placement), it would be nice to have a more programmatic api module, IMHO21:39
cdentsmcginnis: not sure there's a huge rush21:39
smcginnisThere certainly doesn't seem to be within the team.21:40
cdentdansmith: I think in order to do what you're suggesting in the right way is to do it as you say: a mediating layer underneath the http handlers21:40
cdentwhich would be cool and a nice layer to have21:41
cdentbut probably more effortful than what we want now?21:41
dansmithyeah, which is what I kinda expected:21:41
dansmiththe http layers would do the microversion bits, the policy bits, etc and then call this API, which you could call directly if you're nova-manage or something like that21:41
dansmithcdent: like I said, you have leeway while we're locked together I think, but once we split, I think we need to have the more formal thing21:41
cdentyeah, that would require got a lot of change, we're not super clean21:42
efriedeek, microversion handling.21:42
efriedin anything like a pythonic interface21:42
efriedwithout having actual microversion args21:42
dansmithefried: that's why I think doing it below that layer is better21:42
dansmithso you're not passing version=1.23 to a method21:43
cdentI'm not sure why would we _have_ to be more formal after the split. After the split you can still from placement import direct; with direct.PlacementDirect(Conf): $do some requests21:43
dansmithsure, but what version do you get?21:43
dansmithright now, we know.. it's the same version as the nova code21:43
openstackgerritMathieu Gagné proposed openstack/nova-specs master: Multiple Fixed-IPs support in network information  https://review.openstack.org/31262621:43
dansmithbut once they're separate packages, you have to be able to say "nova X requires placement Y" in order to be able to import and use it and have the things you expect to be there21:44
cdentthat's true without these proposed changes, based on the way we've been writing the report client21:44
dansmiththat's because we're calling across to another service,21:45
dansmithwhich could be on a different machine, running different stuff21:45
dansmithif we import the code directly from the python namespace, we know right now that we're getting the version from the same git hash we're on21:45
dansmithbut once you break that, then we're not21:45
cdentI don't really see that as an issue if "do some requests" includes microversions. If the versions not there, it doesn't work21:46
efriedyou're okay with these pythonic front end methods having a 'microversion' arg?21:47
dansmithefried: I'm not21:47
efriedYeah, that ooks me out too.21:47
dansmithcdent: if we speak http to it, then that's how we avoid a NameError, yes21:47
dansmithI just don't think we should do that :)21:47
dansmithI think speaking http over this fake adapter thing to just /migrator for the purposes of this transition is icky, but probably not the end of the world,21:48
cdentI guess I've not got as complete a view of this librarization as you dansmith . For me it is simply a way to avoid networked http, not http.21:48
dansmithI just don't think that you should expose that from a python library interface21:48
dansmithwell, that's certainly one way to approach it, for sure21:48
cdentBasically I don't think we should be writing services that except to use placement as a library, rather we should be writing them so they normally use placement as a service, and _can_ use it as a library is they have to21:49
cdentin which case, efried's adapter idea is useful21:49
cdents/except/expect/21:50
efriedI agree it's also a bit ookie to have a python lib that speaks http without going over http, but in this case I think it's the lesser evil, and certainly will be the easiest/fastest to implement.21:50
dansmithfor the /migrator thing, I've said I think you can do that for expediency21:50
* cdent nods21:50
cdentI think we should probably have a more in depth conversation at some point about the two different library models, because one of them is a lot of rope (not necessarily a bad thing, but usually worth some deeper chat)21:51
openstackgerritChris Dent proposed openstack/nova master: WIP: Spike a direct interface to placement  https://review.openstack.org/57257622:36
cdentjaypipes, dansmith, efried, edleafe: wippity wip wip ^22:36
efriedack22:37
mriedemi can't figure out what's going on with tetsuro's spec here https://review.openstack.org/#/c/545734/22:51
mriedemit was abandoned and then restored22:51
mriedemsame with https://review.openstack.org/#/c/543805/22:52
mriedemlooks like those are both superseded by https://review.openstack.org/#/c/555081/22:52
openstackgerritMerged openstack/nova stable/ocata: libvirt: handle DiskNotFound during update_available_resource  https://review.openstack.org/57143223:01
openstackgerritMerged openstack/nova master: Fix some wrong urls in doc  https://review.openstack.org/57114723:01
*** edmondsw has joined #openstack-placement23:03
*** edmondsw has quit IRC23:07
openstackgerritEric Fried proposed openstack/nova-specs master: WIP: Spec: Handling Reshaped Provider Trees  https://review.openstack.org/57258323:17
openstackgerritMerged openstack/nova master: [placement] Do not import oslo_service for log_options  https://review.openstack.org/57223123:21
*** mriedem is now known as mriedem_afk23:25
*** takashin has joined #openstack-placement23:31
openstackgerritChris Dent proposed openstack/nova master: Optional separate database for placement API  https://review.openstack.org/36276623:55
openstackgerritChris Dent proposed openstack/nova master: Isolate placement database config  https://review.openstack.org/54143523:55
openstackgerritChris Dent proposed openstack/nova master: Ensure that os-traits sync is attempted only at start of process  https://review.openstack.org/55385723:55
*** tetsuro has joined #openstack-placement23:56

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!