Monday, 2015-07-20

*** annegent_ has joined #openstack-api00:07
*** annegentle_ has quit IRC00:08
*** annegent_ has quit IRC00:23
*** Apoorva has quit IRC00:35
*** Apoorva has joined #openstack-api01:35
*** Apoorva has quit IRC01:40
*** annegentle_ has joined #openstack-api01:43
*** jxstanford has quit IRC02:01
*** annegentle_ has quit IRC02:09
*** jxstanford has joined #openstack-api02:51
*** Apoorva has joined #openstack-api02:53
*** annegentle_ has joined #openstack-api03:30
*** jxstanford has quit IRC03:49
*** annegentle_ has quit IRC03:57
*** jxstanford has joined #openstack-api04:07
*** jxstanford has quit IRC04:25
*** Apoorva has quit IRC04:51
*** briancurtin has quit IRC04:58
*** ameade has quit IRC04:59
*** briancurtin has joined #openstack-api04:59
*** ameade has joined #openstack-api05:01
*** ameade has quit IRC05:36
*** briancurtin has quit IRC05:36
*** ameade has joined #openstack-api05:40
*** briancurtin has joined #openstack-api05:44
*** e0ne has joined #openstack-api06:13
*** alexus is now known as alex_xu06:14
*** e0ne has quit IRC06:17
*** e0ne has joined #openstack-api06:21
*** e0ne has quit IRC06:29
*** e0ne has joined #openstack-api06:33
*** e0ne has quit IRC06:56
*** e0ne has joined #openstack-api07:00
*** e0ne has quit IRC07:22
*** e0ne has joined #openstack-api07:26
*** e0ne has quit IRC07:29
*** e0ne has joined #openstack-api07:29
*** e0ne has quit IRC07:30
*** ameade has quit IRC07:31
*** ameade has joined #openstack-api07:48
*** lucasagomes has joined #openstack-api08:03
*** fzdarsky has joined #openstack-api08:28
*** fzdarsky_ has joined #openstack-api08:46
*** fzdarsky has quit IRC08:49
*** e0ne has joined #openstack-api08:55
*** alex_klimov has joined #openstack-api09:53
*** alex_klimov has quit IRC10:32
*** alex_klimov has joined #openstack-api10:32
*** cdent has joined #openstack-api11:02
*** ig0r_ has joined #openstack-api11:08
*** lucasagomes is now known as lucas-hungry11:17
*** woodster_ has joined #openstack-api12:01
*** ig0r_ has quit IRC12:05
*** lucas-hungry is now known as lucasagomes12:11
*** annegentle_ has joined #openstack-api13:08
*** jxstanford has joined #openstack-api13:14
*** jxstanford has quit IRC13:16
*** annegentle_ has quit IRC13:16
*** annegentle_ has joined #openstack-api13:17
*** terrylhowe has joined #openstack-api13:17
*** annegentle_ has quit IRC13:30
*** annegentl_ has joined #openstack-api13:30
*** alex_klimov has quit IRC13:32
*** annegentl_ has quit IRC13:48
*** annegentl_ has joined #openstack-api14:11
*** alex_klimov has joined #openstack-api14:15
*** sigmavirus24_awa is now known as sigmavirus2414:16
*** sc68cal_ has joined #openstack-api14:36
*** sc68cal has quit IRC14:37
*** sc68cal_ is now known as sc68cal14:37
*** kfox1111_ has joined #openstack-api14:39
*** sdague_ has joined #openstack-api14:40
*** krotscheck_ has joined #openstack-api14:41
*** krotscheck has quit IRC14:42
*** sdague has quit IRC14:42
*** kfox1111 has quit IRC14:42
*** sdague_ is now known as sdague14:42
*** krotscheck_ is now known as krotscheck14:42
*** terrylhowe has left #openstack-api14:56
*** jxstanford has joined #openstack-api16:08
*** vishwanathj has joined #openstack-api16:12
*** alex_klimov has quit IRC16:15
*** notmars has joined #openstack-api16:17
*** e0ne has quit IRC16:18
*** Apoorva has joined #openstack-api16:23
*** salv-orlando has joined #openstack-api16:26
*** annegentl_ has quit IRC16:40
*** notmars has quit IRC16:48
*** e0ne has joined #openstack-api17:15
*** openstackgerrit has quit IRC17:16
*** openstackgerrit has joined #openstack-api17:17
*** lucasagomes is now known as lucas-dinner17:21
*** annegentl_ has joined #openstack-api17:44
*** annegentl_ has quit IRC17:56
*** annegentl_ has joined #openstack-api17:56
*** lucas-dinner has quit IRC18:52
*** lucas-dinner has joined #openstack-api19:04
*** jxstanford has quit IRC19:06
*** salv-orlando has quit IRC19:38
*** jxstanford has joined #openstack-api19:56
*** salv-orlando has joined #openstack-api20:06
elmikohey all, i'm reviewing a spec in sahara and we are talking about using PUT for an update. i gathered from previous conversations that doing a PUT with a partial resource can be controversial, but in cases where most of the fields are read-only it could be acceptable. is this accurate?20:15
cdentelmiko: generally speaking, yeah, PUT is supposed to be a representation of the full resource20:17
cdentbut it sounds like you have a sort of asymmetric representation20:17
cdentwhere what you GET is much different from what it makes sense to PUT20:17
elmikoyea totally20:18
cdentI think it has become fairly common to PUT the entre collection of writable stuff20:18
elmikoour GET is crazy, filled with info that the user won't be able to change20:18
elmikoand we are now opening up the possibility to update 1 field20:18
cdentthat would seem weird20:18
cdent(to me)20:18
cdentwhy not do a PATCH?20:18
ryansbpatch++20:19
elmikothat might make sense20:23
elmikohmm20:24
elmikoi didn't want to descend down the PATCH rabbit hole20:24
cdentelmiko: you don't have to use a PATCH language to patch, it's okay to send a partial representation and just be done with it20:25
elmikointeresting, this seems like a philosophical point though, no?20:26
sigmavirus24elmiko: how do you mean?20:27
elmikonot trying to be pedantic, i just read a blog post admonishing people for using patch like that20:27
elmikoisn't patch literally supposed to be like a diff-ish patch that you send20:27
cdentelmiko: reference?20:27
elmikoinstructing the server how to change the resource, but not the actual updated resource20:27
cdent_some_ people think that but I think that's crazy20:27
cdentincredibly limiting20:27
elmikoright, that's why i said philosophical point ;)20:27
cdentit will just make people use PUT incorrectly20:28
cdentI guess it depends a lot on representations20:28
sigmavirus24== cdent20:28
cdentsigmavirus24: ?20:29
sigmavirus24I've seen patches where you send {"field_to_update": "updated_value"}20:29
sigmavirus24that seems very limiting and will push people to use PUT incorrectly20:29
ryansbsigmavirus24: yeah, the only time that falls flat is list/set ops20:29
sigmavirus24ryansb: sure20:29
sigmavirus24I'm saying, in some cases, it works. And from the bits I've seen elmiko talk about, it sounds like it'll work in this case20:30
ryansbanyways, I'd rather you do the diff-style PATCH than do partial PUTs20:30
elmikointeresting20:30
ryansbthat is, of course, just my opinion20:30
elmikoyea, i don't have a strong opinion on this, just trying to collate a bunch of other folks thoughts20:31
elmikoi mean, PATCH with partial resource seems ok to me. but this post i read went on about how that "bad wrong(TM)"20:31
elmikowell, i shouldn't have quoted20:31
sigmavirus24elmiko: link?20:32
* cdent releases a new gabbi20:32
sigmavirus24no don't do that20:32
sigmavirus24=P20:32
elmikohttp://williamdurand.fr/2014/02/14/please-do-not-patch-like-an-idiot/20:33
sigmavirus24Link alone is enough for me to want to disregard this20:33
sigmavirus24=P20:33
elmikohaha, i knew you would love it!20:33
ryansblol20:33
elmikosigmavirus24: given your penchant for RFCs i thought you would love the verbal pedantry20:34
sigmavirus24So20:34
ryansbcdent: got release notes for that?20:34
sigmavirus24The other core dev on requests just authored a draft20:34
sigmavirus24And I feel obligated to read it20:34
sigmavirus24(Using HTTP/2 for p2p)20:35
cdentryansb: release notes on gabbi? nothing more than the changelog in the pypi package. something more formal is probably a good idea now that it is >1.020:36
ryansbcdent: no worries, I just https://github.com/cdent/gabbi/compare/1.1.1...1.1.2 instead20:36
* cdent totally forgot he'd been tagging the repo20:37
ryansbyou sorta have to if you use pbr20:37
cdentI'm not sure of the terminology, but I guess I "pre-version" which is the way to make sure that pbr doesn't behave in that utterly insane way that it does20:38
ryansbOh, that works too20:38
elmikoryansb: so, given your update to the put guidelines, i'm guessing you are cool with allowing partial resource updates through PATCH?20:39
cdentI do the tagging via makefile targets which drive the release process20:39
cdentI wanted pbr for the easy handing of stuff in setup.cfg but not for the release automation20:39
cdentryansb: are you using gabbi, or just tracking it for fun and profit?20:40
ryansbYes, I'm totally cool with partial PATCH20:43
ryansbas long as you don't need set/list operations20:44
elmikohmm20:44
ryansbcdent: tracking & playing with for personal projects20:44
ryansbI have a couple pyramid apps that I've done the basic gabbi-hello-world type tests on20:44
ryansbhoping to cover them all the way, when I have time.20:45
elmikoi'm just trying to figure out the best way to advise on this review. i mean we have an obscenely long record with mostly read-only attributes and we want to update 1 thing.20:45
elmikothink i'll mention both styles20:45
ryansbfor that case, patch is (imo) totally the way to go. How you implement patch is up for other debate20:46
sigmavirus24== ryansb20:46
*** salv-orlando has quit IRC20:47
elmikoyea, gonna note that in my comments20:48
*** fzdarsky_ has quit IRC20:55
elmikoryansb: so, on a PATCH to a resource that may involve an async action, we send back a 202, but what body with that?21:01
elmikomaybe send back the resource in its current state, assuming no errors?21:02
elmikoryansb, cdent, if you guys have time i would definitely appreciate your thoughts on https://review.openstack.org/#/c/19826421:07
cdentI've marked it to look at it tomorrow morning, I'm sort of out of brain now21:08
*** fzdarsky has joined #openstack-api21:08
*** salv-orlando has joined #openstack-api21:09
elmikocdent: totally understandable, and thanks =)21:11
elmikoit's like what, 10pm there?21:11
* cdent nods21:15
elmikodefinitely time for a pint ;)21:19
elmikoway past actually21:19
*** fzdarsky_ has joined #openstack-api21:21
ryansbelmiko: also marked for tomorrow, gotta head out21:22
elmikoryansb: thanks!21:22
cdentelmiko: instead of a pint I got some cake21:25
cdentand with my cake I'm going to retire to reading vague drivel on the interwebs21:26
cdentg'night21:26
*** cdent has quit IRC21:26
*** lucas-dinner has quit IRC21:34
*** e0ne has quit IRC21:48
*** e0ne has joined #openstack-api21:48
*** fzdarsky has quit IRC21:53
*** fzdarsky_ has quit IRC21:53
*** sigmavirus24 is now known as sigmavirus24_awa21:58
*** e0ne has quit IRC22:25
*** sigmavirus24_awa is now known as sigmavirus2423:12
*** bitblt has joined #openstack-api23:20
*** jxstanford has quit IRC23:37
*** gmann_ has quit IRC23:43
*** gmann has joined #openstack-api23:50
*** sigmavirus24 is now known as sigmavirus24_awa23:58

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