Monday, 2018-06-04

openstackgerrittianhui proposed openstack/nova master: Fix bug to filter_scheduler  https://review.openstack.org/57199802:20
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: Initial change set of z/VM driver  https://review.openstack.org/52338702:46
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: Spawn and destroy function of z/VM driver  https://review.openstack.org/52765802:46
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: add snapshot function  https://review.openstack.org/53424002:46
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: add power actions  https://review.openstack.org/54334002:46
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: add get console output  https://review.openstack.org/54334402:47
openstackgerrittianhui proposed openstack/nova master: Fix bug to filter_scheduler  https://review.openstack.org/57199803:49
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Add rules column to instance_group_policy table.  https://review.openstack.org/56083203:50
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Add policy to InstanceGroup object and api models.  https://review.openstack.org/56337503:50
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Add policy field to ServerGroup notification object  https://review.openstack.org/56340103:50
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Change the anti-affinity Filter to adapt to new policy  https://review.openstack.org/57116603:50
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Adapt _validate_instance_group_policy to new policy model  https://review.openstack.org/57146503:50
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (1)  https://review.openstack.org/57201805:06
openstackgerritMerged openstack/nova stable/pike: libvirt: handle DiskNotFound during update_available_resource  https://review.openstack.org/57142605:31
openstackgerritMerged openstack/nova stable/pike: libvirt: Skip fetching the virtual size of block devices  https://review.openstack.org/57142705:31
*** e0ne has joined #openstack-placement06:34
openstackgerritjichenjc proposed openstack/nova master: Remove unused _disk_qcow2_to_raw  https://review.openstack.org/57202506:48
openstackgerritjichenjc proposed openstack/nova master: Enhance api-guide general info some updates  https://review.openstack.org/56177306:53
*** sususuryashines has joined #openstack-placement07:04
openstackgerritjichenjc proposed openstack/nova master: Downgrade overquota warning  https://review.openstack.org/57202807:05
*** sususuryashines is now known as tssurya07:08
openstackgerritjichenjc proposed openstack/nova master: Enhance api-guide general info some updates  https://review.openstack.org/56177307:23
*** giblet is now known as gibi07:27
openstackgerritZhenyu Zheng proposed openstack/nova master: Use ThreadPoolExecutor for max_concurrent_live_migrations  https://review.openstack.org/56350507:27
*** e0ne has quit IRC07:30
*** e0ne_ has joined #openstack-placement07:30
openstackgerritZhenyu Zheng proposed openstack/nova master: Only run placement request filters when Placement will be called  https://review.openstack.org/56996907:33
*** ttsiouts has joined #openstack-placement07:50
*** ttsiouts has quit IRC07:53
*** ttsiouts has joined #openstack-placement07:57
openstackgerritTakashi NATSUME proposed openstack/nova-specs master: Change a validation in creating a server group  https://review.openstack.org/54648408:16
openstackgerritTakashi NATSUME proposed openstack/nova-specs master: Change a validation in creating a server group  https://review.openstack.org/54648408:16
*** ttsiouts has quit IRC08:16
*** ttsiouts has joined #openstack-placement08:46
openstackgerritChen proposed openstack/nova master: Fix a typo  https://review.openstack.org/57206109:33
openstackgerrittianhui proposed openstack/nova master: Fix bug for hypervisors  https://review.openstack.org/57206309:37
openstackgerritZhenyu Zheng proposed openstack/nova master: Use ThreadPoolExecutor for max_concurrent_live_migrations  https://review.openstack.org/56350509:47
*** ttsiouts has quit IRC09:50
*** ttsiouts has joined #openstack-placement09:51
*** ttsiouts has quit IRC09:55
*** alex_xu_ has joined #openstack-placement10:17
*** purplerbot has quit IRC10:20
*** alex_xu has quit IRC10:20
openstackgerritKashyap Chamarthy proposed openstack/nova master: libvirt: Remove usage of migrateToURI{2} APIs  https://review.openstack.org/56725810:30
*** ttsiouts has joined #openstack-placement10:32
*** jrollinhatin is now known as jroll11:20
*** rubasov has joined #openstack-placement11:24
*** gibi has quit IRC11:31
openstackgerritJan Gutter proposed openstack/nova-specs master: Spec to implement vRouter HW offloads  https://review.openstack.org/56714811:32
openstackgerritJan Gutter proposed openstack/nova master: Convert vrouter legacy plugging to os-vif  https://review.openstack.org/57132511:32
openstackgerritJan Gutter proposed openstack/nova master: [WIP] Add support for vrouter HW offloads  https://review.openstack.org/57208211:32
*** gibi has joined #openstack-placement11:43
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Add policy to InstanceGroup object and api models.  https://review.openstack.org/56337511:49
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Add policy field to ServerGroup notification object  https://review.openstack.org/56340111:49
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Change the anti-affinity Filter to adapt to new policy  https://review.openstack.org/57116611:49
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Adapt _validate_instance_group_policy to new policy model  https://review.openstack.org/57146511:49
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Microversion 2.63 - Use new format policy in server group  https://review.openstack.org/56753411:49
openstackgerritDamon Li proposed openstack/nova master: Remove minimum version check when save service  https://review.openstack.org/57208912:07
*** gibi has quit IRC12:10
*** gibi has joined #openstack-placement12:10
*** edmondsw has joined #openstack-placement12:12
openstackgerritDamon Li proposed openstack/nova master: Remove minimum version check when save service  https://review.openstack.org/57208912:13
*** jroll has quit IRC12:29
*** jroll has joined #openstack-placement12:30
*** gibi has quit IRC12:30
openstackgerritJan Gutter proposed openstack/nova-specs master: Spec to implement vRouter HW offloads  https://review.openstack.org/56714812:32
*** openstackgerrit has quit IRC12:34
*** gibi has joined #openstack-placement13:05
*** gibi has quit IRC13:14
*** jaypipes has joined #openstack-placement13:20
*** gibi has joined #openstack-placement13:20
*** tetsuro has joined #openstack-placement13:38
*** openstackgerrit has joined #openstack-placement13:44
openstackgerritChen proposed openstack/nova master: Fix some inconsistencies in doc  https://review.openstack.org/57040713:44
*** cdent has joined #openstack-placement13:54
*** mriedem has joined #openstack-placement14:00
openstackgerritMultipleCrashes proposed openstack/nova master: Retry decorator fix for autoscale delete  https://review.openstack.org/56341814:10
*** e0ne_ has quit IRC14:16
*** e0ne has joined #openstack-placement14:17
*** alex_xu_ has quit IRC14:20
*** alex_xu has joined #openstack-placement14:20
*** takashin has joined #openstack-placement14:29
*** tetsuro has quit IRC14:35
*** ttsiouts has quit IRC14:40
*** cdent has quit IRC14:44
*** ttsiouts has joined #openstack-placement14:46
*** alex_xu has quit IRC14:47
*** alex_xu has joined #openstack-placement14:49
gibiI've tried to add another alternative to the https://etherpad.openstack.org/p/placement-migrate-operations from line 10814:53
gibiIt is a lot less API heavy14:53
efriedgibi: responding14:59
gibiefried: looking15:00
*** takashin has left #openstack-placement15:01
*** cdent has joined #openstack-placement15:10
openstackgerritmelanie witt proposed openstack/nova stable/pike: zuul: Move legacy jobs to project  https://review.openstack.org/57213015:17
*** purplerbot has joined #openstack-placement15:17
*** e0ne has quit IRC15:19
*** ttsiouts has quit IRC15:19
openstackgerritmelanie witt proposed openstack/nova stable/ocata: zuul: Move legacy jobs to project  https://review.openstack.org/57213215:21
jaypipesfriggin etherpad...15:26
jaypipesI don't know wtf is going on with it.15:26
jaypipesefried: grabbing some nosh. back in about an hour.15:27
efriedack15:28
openstackgerritMatt Riedemann proposed openstack/nova-specs master: Spec for volume multiattach enhancements  https://review.openstack.org/55207815:40
openstackgerritDan Smith proposed openstack/nova master: Use oslo.messaging per-call monitoring  https://review.openstack.org/56669615:44
efriedjaypipes, cdent, gibi: We might be making this more complicated than it needs to be.  All we really need is an atomic transaction that can15:45
efried- set inventories on >1 RP15:45
efried- set multiple allocations.15:45
efriedWe already have a JSON payload format for setting an inventory.15:45
efriedWe already have a JSON payload format for setting multiple allocations.15:45
efriedSo let's just combine those.15:45
efriedWorking this up on the etherpad...15:45
*** tssurya has quit IRC15:48
cdentefried: are you sure? I'm not sure that I entirely understand the problem. There seemed to be some edge cases that made your description incomplete. However if it is possible to do what you're saying, that would be great15:48
efriedcdent: Which edge cases?15:48
efriedcdent: I don't think it's important for the payload to describe which units are *moving* from where to where.  I think we only need to know which units *are* where by the time we're done.15:49
cdentThat's the point: I don't know. But the etherpad, at least in its earliest forms seemed to suggest that splitting of some kind was required.15:49
cdentI agree that representing desired state, rather than the transformation, is better.15:49
cdentbut it wasn't clear to me if that was going to be suitable for the allocations15:50
cdentwhere "suitable" might mean "concise" (not that I'm really that concerned about concise, just trying to be fair to people who do care about such things)15:51
efriedsplitting still possible with this.15:52
openstackgerritMultipleCrashes proposed openstack/nova master: Retry decorator fix for autoscale delete  https://review.openstack.org/57037015:53
cdentthe concise form is "move these allocations for these consumers", but if we just say "make the allocations look like this" that achieves the same thing, so I'd be in favor of that15:53
efriedand in fact, the only additional bloat is having to include the full inv for the "source" RPs, I think.15:53
efriedalso having to include the proj/user id info in the allocations, I suppose.15:54
cdentfrom a RESTy standpoint expressing the full state of everything is nice15:54
efriedcdent: Have we not put RP gen into POST /allocations?15:58
efriedcdent: Was that part of what's happening in the consumer gen bp?15:58
cdentjust consumer, not rp, because there are^wcan be multiple rps involved.15:59
efriedcdent: Right, the rp gen would have to go in the allocation dict for each rp.16:01
efried{16:02
efried  "30328d13-e299-4a93-a102-61e4ccabe474": {16:02
efried    "project_id": "131d4efb-abc0-4872-9b92-8c8b9dc4320f",16:02
efried    "user_id": "131d4efb-abc0-4872-9b92-8c8b9dc4320f",16:02
efried    "allocations": {16:02
efried      "e10927c4-8bc9-465d-ac60-d2f79f7e4a00": {16:02
efried        "resources": {16:02
efried          "VCPU": 2,16:02
efried          "MEMORY_MB": 316:02
efried        }16:02
efried        "resource_provider_generation": <gen>,   <==== HERE - this is what we don't have today (at least in the docs)16:02
efried      }16:02
efried    }16:02
efried  },16:02
cdentwhy do you want to do that?16:03
efriedwant?16:03
efried:)16:03
cdentwhy do you want gen in the allocations?16:03
efriedI'm just spitballing here.  I noticed it's missing and I'm trying to figure out if we need it.16:03
efriedwe don't need it?16:03
efriedDon't we update rp gen when we allocate against the rp?16:03
* efried looks16:03
* cdent is on a call16:05
efriedanswer is yes.16:05
efriedhttps://github.com/openstack/nova/blob/master/nova/api/openstack/placement/objects/resource_provider.py#L228816:06
cdentyes, but why do you want to send it?16:06
cdents/you want/considering/16:07
efriedI think we discussed this in Dublin when we were conceiving the consumer gen work.16:07
efriedand came to the conclusion that we don't.16:07
efriedbut I don't remember why16:07
efriedIf something has changed about the provider, I want to re-evaluate whether I really want to allocate against it?16:08
efriedBut I guess that way lies thrashing in the scheduler.16:08
cdentwhat you care about with allocations is whether you can make the allocation or not, that's all16:09
cdentif we make it more complicated than that, that way lies madness16:09
efriedI can buy it.16:11
efriedjaypipes, cdent, edleafe, bauzas, gibi: Okay, finished proposal for "specify the end state".  See L67-98.  https://etherpad.openstack.org/p/placement-migrate-operations16:25
efriedplease do read the preamble16:26
cdentefried: superficial read (while on the phone) it seems sane and complete but it is hard for me to think about clearly without test cases. Will make some notes16:35
efriedcdent: ack, thanks for looking.16:35
jaypipesefried: ack. will do shortly. just wrapping up yet another revision on the cpu-resources spec.16:38
efriedthx16:38
efriedyou really should just get that thing merged already16:39
jaypipeslol16:40
*** edmondsw has quit IRC16:41
*** ttsiouts has joined #openstack-placement16:41
*** tssurya has joined #openstack-placement16:46
*** edmondsw has joined #openstack-placement16:46
*** e0ne has joined #openstack-placement16:47
*** ttsiouts has quit IRC16:49
*** ttsiouts has joined #openstack-placement17:24
*** ttsiouts has quit IRC17:41
*** ttsiouts has joined #openstack-placement17:46
*** tssurya has quit IRC18:20
*** tssurya has joined #openstack-placement18:37
*** mriedem has quit IRC18:40
*** mriedem has joined #openstack-placement18:43
openstackgerritMatt Riedemann proposed openstack/nova master: Fix typo in enable_certificate_validation config option help  https://review.openstack.org/57218518:51
openstackgerritJay Pipes proposed openstack/nova-specs master: Standardize CPU resource tracking  https://review.openstack.org/55508118:55
cdentmriedem, efried, jaypipes: wanted to get a sanity check on a desire: I'd like to set the default for the new [placement_database]/connection conf setting to an environment variable . That doesn't seem to be a thing that is commonly done in nova and derivatives, but makes containerisation happy. Is there a reason to not do it?18:56
jaypipescdent: you mean doing something like default=os.environ.get('PLACEMENT_DB_CONNECTION', DEFAULT_PLACEMENT_DB_CONNECTION) or something like that?18:59
cdentyeah18:59
mriedemwe don't have defaults on db connections do we?19:00
jaypipescdent: ++ I would definitely support that.19:00
mriedemso wouldn't the env var default to None?19:00
cdentmriedem: yes19:00
jaypipescdent: FTR, I've always written my python code like that. It's a pattern I think should be used in OpenStack. (see https://github.com/jaypipes/os-lively/blob/master/os_lively/conf.py for example...)19:01
cdentright, I'll make it happens. Also looking into seeing if it is doable for some of the keystone middleware settings19:01
cdentjaypipes: yeah, totally agree it is the right way to go19:01
*** ttsiouts has quit IRC19:04
* cdent lunches19:04
*** cdent has quit IRC19:05
jaypipescdent: would you be able to do 11am EST / 8am PST tomorrow morning for a decision-making hangout on the migration API endpoint thing?19:05
efriedjaypipes: Seen proposal at L67 yet?19:20
efriedegads, there's three of you on the etherpad now.19:20
efriedone of you is apparently old19:20
jaypipesefried: yeah, no idea why there's two of me on the damn thing :(19:25
efriedjaypipes: It's effectively the same as what you're proposing at the bottom - except it uses existing payload formats.19:27
openstackgerritDan Smith proposed openstack/nova master: Change consecutive build failure limit to a weigher  https://review.openstack.org/57219519:47
*** ttsiouts has joined #openstack-placement19:53
*** cdent has joined #openstack-placement19:57
openstackgerritMatt Riedemann proposed openstack/nova-specs master: Remove device from volume attach requests (spec)  https://review.openstack.org/45254620:06
jaypipesefried: gotta love etherpad "conversations" :)20:08
efriedjaypipes: ikr.  Especially with the colors, my eyes come back here and everythnig looks all washed out.20:08
jaypipesefried: still haven't figured out where "old jaypipes" is coming from :(20:09
efried"Ghost of Jay"20:09
jaypipesheh20:09
*** e0ne has quit IRC20:13
efriedcdent: 8am Pacific work for you tomorrow?20:13
efriededleafe: 10am Central work for you tomorrow?20:13
cdentefried: should be fine. free until 10, and can skip the thing at 10 if needed20:14
efriedcdent: What's the reason we've avoided PATCH thus far?20:15
cdentPATCH and PUT are supposed to have very specific meanings, PATCH moreso than PUT, but both are often usefully violated. In the most strict sense PATCH is supposed to use a diff-like or tranformattion-oriented syntax on a _single_ resource (a thing that can be identified by a URI)20:17
cdentso while we might consider PATCHing an inventory, resource provider, or allocation, doing that operation on a suite of things would be weird20:17
openstackgerritJay Pipes proposed openstack/nova-specs master: Standardize CPU resource tracking  https://review.openstack.org/55508120:18
efriedcdent: Mm, gotcha.20:18
efriedcdent: That said, what's the usual verb for an operation that *does* work on a suite of things?20:20
cdentPOST20:21
efriedight20:21
cdentPOST is the "transform state in arbitrary ways" method20:21
edleafeefried: I should be available at 10am CDT tomorrow20:23
* cdent is trying to decode the etherpad20:23
*** ttsiouts has quit IRC20:23
efriedcdent: I'm about to clean it up into a new pad.  Glad to get feedback in its current state if you can stomach it, but feel free to wait.20:24
cdentI think I've digested it. The one thing I'm missing is the positive justification for the PATCH format. I understand that it avoids some of the dangers and verbosity of the POST version, but interested what else.20:25
efriedjaypipes, cdent, edleafe, gibi, bauzas: Tuesday 1500 UTC for discussing "placement API to support upgrades".20:25
cdent20:25
efriedcdent: which POST?  The "additions+removals" one, or the "whole payload" one?20:26
cdentwhole payload20:26
jaypipesyup, efried ++20:27
efriedcdent: Okay, jaypipes's concerns there start on L10220:28
jaypipescdent: the PATCH format was added as an option. Not sure there's a positive justification for it, besides just being another possibility.20:28
efried(or for those of you with weird line numbers, right after the JSON for POST /inventories_and_allocations)20:28
jaypipescdent: I added it in response to gibi's statement earlier today that he was looking for "what we need is a series of existing placement API calls executed in an atomic way."20:29
jaypipescdent: and so I popped the PATCH stuff up as a possible thing that did that.20:30
jaypipescdent: or kind of did that ... :)20:30
*** ttsiouts has joined #openstack-placement20:31
cdentblargh, office talkers distracting me20:31
efriedjaypipes: https://tools.ietf.org/html/rfc7396 is another option for PATCH, less verbose than the http://tools.ietf.org/html/rfc6902 format.  Still has the ookiness of the fact that we're operating on multiple resources at once, which IIUC is going to be the objection to *any* PATCH.20:35
efried(I'm thinking maybe we're not quiiite ready yet to distill down to a smaller set of proposals :)20:35
efried(cause we're still in 'expand' mode, pretty much)20:35
cdentI'll be lightly -1 to any merge/diff/transform format simply because it is less scrutable (and thus, to me, less testable) than a full-state thing20:37
efriedsomething about cdent's scrutum...20:37
*** e0ne has joined #openstack-placement20:38
jaypipesefried: but merge patch has no ability to represent the removal of elements, right?20:39
efriedjaypipes: yeah: null20:39
jaypipesah.20:39
jaypipescdent: my personal opinion is that the list of operations in the JSON Patch is actually pretty easy to scrutinize. It's explicit about what is being added, removed, and tested for, as opposed to just "replace the representation of this thing with this other thing" (and needing to have the "test" actions represented in other ways (the generation checks, etc)20:41
cdentyeah, I see that, thus "lightly"20:41
jaypipescdent: but at the end of the day, we just need to settle on one of these methods and go with it. not having this functionality means not being able to do in-place compute upgrades which means a bunch of nested providers patch series are dead in the water...20:42
* cdent nods20:42
cdentI'm pretty sure that the placement side of this fix is the easy part, yeah?20:42
jaypipesas much as it would please me to say "f it, just have the operators perform the slide puzzle" :)20:42
efriedcdent: The nova side is actually not bad.20:42
cdentI'll believe you when I see it, efried20:43
jaypipescdent: I don't think either side is all that complicated. just needs to be agreed upon which side is responsible for what.20:43
efriedjaypipes: Remember, if we want to buy time, we can hack the upgrade temporarily without changing the placement API at all ("locking" providers by setting reserved=total while we shuffle stuff around).20:43
efriedthen we can take our time figuring out the PERFECT form for this single-transaction migration.20:44
jaypipescdent: I personally think that placement should be responsible for all locking/transactional awareness and nova side should just be responsible for telling placement *either* what it wants the desired state to be *or* a list of instructions for placement to take in an atomic fashion.20:44
cdentI thinnk efried has just landed on the solution: custom http verb: PERFECT20:44
efried(Yeah, that's a lie, still have to have one leetle API change to allow us to "overallocate" when reserved==total)20:44
jaypipesheh20:45
efriedheh20:45
jaypipesefried: we won't be able to shuffle anything around while reserved=total...20:45
jaypipesefried: that just prevents scheduling, really.20:45
cdentjaypipes: I think we're in agreeement. My assertion is that the state awareness that nova is going to need to have to be able to express its needs to placement (whatever the format) is ... messy20:45
efriedjaypipes: Right, which is the only thing we actually need to prevent here.20:45
cdentbut then I tend to think stuff is messy a lot sooner than either of you two20:46
efriedcdent: Most of that messy awareness is already in update_from_provider_tree20:46
efriedcdent: with the exception of the allocations20:46
cdentbut yes: placement needs to be the authority on locking/transactions20:47
jaypipescdent: well, there's definitely gonna be mess... but the virt driver is really the only thing that knows how to say "this single compute node is now a parent and there are two children that represent these multiple NUMA nodes. put the allocations for instances X, Y, and Z on child A and put the allocations for instances Xa, Ya, and Za on child B"20:47
cdentsure, I'm not suggesting we can avoid the mess, simply that we should make sure we position our undergarments before we leap in20:48
cdentmanage expectations, etc20:48
jaypipesack20:49
efriedjaypipes, cdent: It's a good point: right now the virt driver, via update_provider_tree, is essentially providing us with the *full picture* (minus the allocations atm) so that's a mark in favor of the "full spec" version of the API.20:49
jaypipesefried: ack. again, I'm not opposed to the whole "tell me the desired state" thing. I just have some reservations about giving users a "super API" that may end up being overused.20:54
jaypipesefried: if you thought CERN having issues with our overly loquacious API calls for refreshing provider associations, having *any* caller make overuse of such a proposed "replace the world" API would be a similar performance issue..20:56
*** ttsiouts has quit IRC20:57
*** ttsiouts has joined #openstack-placement20:57
cdentjaypipes, efried: Isn't that just rope that the operators can choose to hang themselves with or not? Especially since the state gathering for huge operations will be itself painful, so people probably won't want to?20:57
jaypipescdent: not sure...20:58
efriedjaypipes: To be fair, refreshing provider associations was making many calls vs. one.  Not sure how a single "refresh" (à la https://review.openstack.org/#/c/521875/) would have affected their env...20:58
efriedcdent: I agree with that.  Though we're not talking about "operators" here so much as "API consumers" like potentially e.g. cyborg.20:59
jaypipesefried: a single "replace the world" operation would essentially block all activities (in the scheduler and elsewhere) for all providers in that provider tree for the duration of the operation.20:59
cdentthese are all system-admin tasks, though, yes?21:00
jaypipescdent: I'm thinking of Cinder and Cyborg as examples here.21:00
cdentit's not like an end user can bring down multiple nova-computes with a simple script posted josh21:00
cdentpresumably code review in cinder and cyborg would help avoid that?21:00
jaypipescdent: imagine if cinder, because it was easier, decided to do a "replace the world" API call every time it updated something for a shared volume storage provider...21:00
cdentwouldn't they learn quickly that was a bad idea?21:01
jaypipescdent: :) I have no idea.21:01
jaypipesin any case, I'm just logging concerns I have, nothing more.21:02
*** e0ne has quit IRC21:02
cdentpresumably the replace the world problems are present with the patch version too, assuming an adventurous client21:03
cdentand I think it is fair to assume that if we have any mode for replacing the world, people will explore ways to use it21:03
cdentand that's just how it goes?21:03
jaypipesperhaps21:04
*** tssurya has quit IRC21:10
*** tssurya has joined #openstack-placement21:11
efriedjaypipes: Okay, so as I put together the curated/distilled etherpad, are you okay if I use merge-patch (RFC 7396) as the PATCH proposal?21:17
jaypipesefried: as an alternative to RFC6902? or as a replacement (pun intended) for that?21:18
efriedreplacement.21:19
*** ttsiouts has quit IRC21:19
*** ttsiouts has joined #openstack-placement21:19
efriedjaypipes: Sayin, we're likely to argue pro or con PATCH on the merits of PATCH as opposed to on the exact syntax of the payload21:20
efriedthough maybe that's a wrong assumption.21:20
efriedjust trying to pre-cull as much as possible.21:20
jaypipesefried: sure, that's cool with me. maybe just leave a note about RFC6902 being an alternative format for PATCH.21:20
efriedroger that.21:20
jaypipescool, thx.21:20
jaypipesefried: personally, I'm looking forward to not seeing "old jaypipes" on this new etherpad.21:21
efriedheh.21:21
efriedjaypipes: You'll have to join as "puggsy_malone"21:22
jaypipesheh21:22
jaypipesmmm, Jules is making succotash for dinner. yum.21:22
efriedyou're not suffering, then, Yosemite Sam?21:24
efriedah, boo, that's Sylvester, not Sam.21:24
*** tssurya has quit IRC21:27
jaypipesefried: heh, no :)21:29
*** tssurya has joined #openstack-placement21:29
*** tssurya has quit IRC21:30
*** edmondsw has quit IRC21:35
openstackgerritLee Yarwood proposed openstack/nova stable/queens: Allow cinderv2 endpoints within the request context catalog  https://review.openstack.org/57221321:46
*** ttsiouts has quit IRC21:52
openstackgerritDavid Bingham proposed openstack/nova master: Adding apply_cells to nova-manage to enable automated cells_v2 configuration.  https://review.openstack.org/57221622:08
efriedjaypipes: Having written up the merge-patch version, it's so close to the removals-and-additions proposal that I'm just going to strike the latter.  Basically it would be the same proposal but with a different `VERB /endpoint`.22:11
efriedjaypipes: So I'm going to consolidate those with a note, if you're cool with that.22:11
efriedcdent: ^22:13
efriedjaypipes, cdent: https://etherpad.openstack.org/p/placement-making-the-(up)grade  <== wanna take a first pass before I send out a note?22:16
mriedemwho is going to be rodney dangerfield in this skit?22:18
mriedemoh wait, different 80s movie https://www.imdb.com/title/tt0087666/22:18
openstackgerritDavid Bingham proposed openstack/nova master: Adding apply_cells to nova-manage to enable automated cells_v2 configuration.  https://review.openstack.org/56898722:28
cdentefried: looking22:29
jaypipesefried: gimme a bit to digest, ok?22:29
efriedjaypipes: cdent: I'm adding preamble about the big picture.  Jump to "New Placement API Call"22:29
*** mriedem has quit IRC22:30
efriedjaypipes, cdent: Okay, I think I finished the preamble.22:42
efriedjaypipes, cdent: Have a note drafted announcing the etherpad and the hangout.  Let me know when I can punch the Send button.22:46
cdentefried: at the very end there is an unfinished sentence?22:48
efriedcdent: No, it was going to be a third proposal, but I realized it was going to be basically the same as the second.  I've deleted it.  Thanks for the catch.22:48
*** mriedem has joined #openstack-placement22:48
jaypipesefried: lgtm.22:48
efriedthx22:48
cdentthe "needs to suport" section is a good idea22:49
efriedcdent: What am I forgetting therein, that we already discussed?22:53
* cdent re-reads22:54
cdentefried: I can't think of anything else22:58
efriedjaypipes: cdent: Okay, thanks.  Emailing, then bailing out for the evening.  See y'all in the a.m.22:59
cdentthanks efried22:59
*** cdent_ has joined #openstack-placement23:03
*** cdent has quit IRC23:04
*** cdent_ is now known as cdent23:04
*** cdent_ has joined #openstack-placement23:24
*** cdent has quit IRC23:26
*** cdent_ is now known as cdent23:26
*** takashin has joined #openstack-placement23:34
*** mriedem has quit IRC23:48

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