Monday, 2015-06-08

openstackgerritAlex Xu proposed openstack/api-wg: Add guideline for microverion bumping  https://review.openstack.org/18789602:57
openstackgerritAlex Xu proposed openstack/api-wg: Add guideline for microversion specification  https://review.openstack.org/18711202:57
*** stevelle has quit IRC03:27
*** stevelle has joined #openstack-api03:28
*** fzdarsky has joined #openstack-api07:19
*** lucasagomes has joined #openstack-api08:05
*** e0ne has joined #openstack-api08:56
*** e0ne is now known as e0ne_09:10
*** cdent has joined #openstack-api09:20
*** e0ne_ has quit IRC09:20
*** e0ne has joined #openstack-api09:29
*** cdent has quit IRC09:41
*** cdent has joined #openstack-api09:41
*** openstackgerrit has quit IRC10:09
*** openstackgerrit has joined #openstack-api10:09
*** e0ne is now known as e0ne_10:56
*** e0ne_ is now known as e0ne10:57
*** fesp has joined #openstack-api11:20
*** e0ne is now known as e0ne_11:38
*** e0ne_ is now known as e0ne11:39
*** lucasagomes is now known as lucas-hungry11:44
*** alex_klimov has joined #openstack-api11:46
*** annegentle has joined #openstack-api12:09
*** fesp is now known as flaper8712:25
*** flaper87 has quit IRC12:25
*** flaper87 has joined #openstack-api12:25
*** woodster_ has quit IRC12:32
*** lucas-hungry is now known as lucasagomes12:38
alex_xuhi guys, Could this patch https://review.openstack.org/181784 enter freeze period?13:00
elmikoalex_xu: is there going to be another patchset, or is final for now?13:08
alex_xuelmiko: it only need some update for commit message. But the reviewer didn't -1 for it. I'm afraid all the +1 and +2 will be clean. Then waiting for more time13:10
alex_xuelmiko: but if we think it's worth to fix, I'm happy with another patchset13:10
elmikoalex_xu: no, that's fine. i just didn't understand the last message.13:10
alex_xuelmiko: sorry for my poor english :(13:11
elmikoalex_xu: i'll make a post about it later today13:11
alex_xuelmiko: thanks a lot :)13:11
elmikoalex_xu: no worries, it's early in the morning for me ;)13:11
alex_xuelmiko: hah, have a good day :)13:12
elmikothanks, you too!13:12
*** krotscheck has joined #openstack-api13:34
*** woodster_ has joined #openstack-api13:35
*** krotscheck has quit IRC13:38
*** krotscheck has joined #openstack-api13:39
*** krotscheck has quit IRC13:40
*** krotscheck has joined #openstack-api13:41
*** e0ne is now known as e0ne_13:56
cdent501 the debate that will not die13:57
ryansbthe bikeshed must be tie-dyed13:58
elmikolol14:02
elmikofunny, i was just responding to the 5xx guidance one14:02
*** notmars has joined #openstack-api14:02
*** blmartin has joined #openstack-api14:03
sdaguenext up is my rebase of all those patches14:04
sdaguecdent: is there a new bit on it?14:04
sdaguehonestly, I was so heads down getting the nova api long form article out, I didn't circle back to it on friday14:04
*** notmars_ has joined #openstack-api14:06
*** notmars has quit IRC14:07
*** notmars_ is now known as notmars14:07
*** e0ne_ has quit IRC14:07
*** e0ne has joined #openstack-api14:08
*** sigmavirus24_awa is now known as sigmavirus2414:11
cdentsdague: nothing new, just continued feedback from people who want to use 501 for "functionality not available in this instance of this api"14:14
cdentelmiko: it was your latest response to someone that set me looking and then posting that little quip14:15
elmikocdent: i kinda figured it was something along those lines ;)14:16
sdagueis stanek in here?14:16
elmikolooks like not14:16
cdentbrb14:16
sdaguebecause I continue to not understand how one can reconcile "501 means POST isn't supported by this server on any resource" with "it could mean something narrower"14:21
*** notmars has quit IRC14:22
cdentoh dear. I just failed to boil water when making coffee. I might need to take an extended break to locate my brain.14:26
elmikoouch...14:27
*** annegentle has quit IRC14:29
cdentI ground the coffee, wet the little aeropress filter thing, assembled the pieces, set it up on my cup, poured in the coffee, poured in the water14:29
cdentoops14:29
elmikocold water?14:29
cdentyeah14:30
elmikobummer =(14:30
cdentI hear cold brew is pretty good, but I didn't have time for that.14:30
elmikolol14:30
openstackgerritSean Dague proposed openstack/api-wg: http guideline expansion: background  https://review.openstack.org/18193114:33
openstackgerritSean Dague proposed openstack/api-wg: add subsection around caching behavior and http  https://review.openstack.org/18352314:33
openstackgerritSean Dague proposed openstack/api-wg: add section describing 501 common mistake  https://review.openstack.org/18345614:33
sdagueok, rebased14:33
sdaguewith more language in there to hopefully get ahead of the debate.14:33
sdagueI also restacked so the 501 is on top14:33
sdaguethe other two I think were pretty agreed on14:34
sdaguesomeone with +2 on the repo able to hit the rebase button for - https://review.openstack.org/#/c/185288/ ?14:34
elmikoi'll give it a whirl14:35
openstackgerritMichael McCune proposed openstack/api-wg: Added note about caching of responses when using https  https://review.openstack.org/18528814:35
elmikomiguelgrinberg: fyi, rebased https://review.openstack.org/#/c/185288/14:36
sdaguelooks like it was detected as trivial rebase, so all votes were kept14:36
cdentsdague++14:37
elmikothankfully =)14:37
*** annegentle has joined #openstack-api14:52
openstackgerritSean Dague proposed openstack/api-wg: add section describing 501 common mistake  https://review.openstack.org/18345614:54
sdagueI just realized I forgot to finish my last paragraph14:54
*** terrylhowe has joined #openstack-api15:18
*** pballand has joined #openstack-api15:22
*** terrylhowe has quit IRC15:24
sdagueok, I also just linked the o'reilly book explanation of 501, which maybe further clarifies15:57
sdaguehttps://books.google.com/books?id=XUaErakHsoAC&lpg=PA387&ots=5kejGntNtw&dq=restful%20web%20services%20501&pg=PA387#v=onepage&q=restful%20web%20services%20501&f=false15:57
elmikonice that they have that book up for free now15:59
cdentThat should help15:59
elmikolet's hope so15:59
cdentI reckon the mindset thing is pretty important for the future though, or we'll just keep having the same detail oriented discussion for each guideline15:59
cdentrather than being having the experience or information to just "get it"16:00
elmikoagreed16:01
cdentsigh, cedric's response to me16:01
sdagueelmiko: well, it's not exactly up for free, but google book search is "fair use"16:01
sdagueso good enough to footnote16:01
elmikoah, ok. thanks for the clarification16:01
* cdent is not sure where to go now16:01
elmikocdent: yea, i'm not understanding why this is such a sticky point16:02
cdentIf I were the me from about 10 years ago things would not be fun from here on out, but I'm not that guy anymore, so ....16:04
* cdent shrugs16:04
elmikolol!16:04
cdentin this particular instance there is confusion over to what an "api contract" applies16:05
cdentbut I'm not sure I can be assed to fight about it16:05
*** annegentle has quit IRC16:06
elmikoyea, i mean, i think i get what cedric is trying to say but i still agree with sdague's assessment. not sure where that leaves me, aside from +1 on the review16:06
cdenthmm.16:07
cdentcedric is wrong16:07
cdentBut you know, it's the 21st century and declaring someone is wrong just isn't allowed :)16:08
elmikoha!16:08
elmikoi'm just acknowledging my lack of depth on this particular point. from my reading, his position still doesn't make sense with regards to the evidence.16:09
cdentI do, however, love the name Cedric16:09
cdentIt is one of several nicknames that got used on me in a chris-rich-environment16:10
sdagueyeh, it's one of the problems of mapping a new use of http onto it post-hoc, hence why I proposed the new http overview introduction to make it clear that it's not going to be an exact mapping, and we need to best effort fit based on being least wrong16:10
elmikosdague: fwiw, it makes sense to me16:11
sdagueactually, the whole status code section at the back of the o'reilly book is pretty useful, I hadn't picked it up in a while.16:12
elmikoi've been using it my go-to reference16:12
sdaguealso, as a pretty interesting data point, the recommended fall back error in rails in it's rest framework is 400, not 500. That's in a "I give up and don't know what to do" case16:13
elmikointeresting16:14
*** fzdarsky has quit IRC16:14
cdentusings rails as a guideline for _anything_ is dangerous territory :)16:14
elmikoyea, was gonna say it might not go over well lol16:14
elmikobut interesting none-the-less16:14
cdentyes16:14
sdaguecdent: well, they did get a bunch of this out there before other folks. first to implement wins some times. :)16:15
cdentbollocks16:15
cdent(to the before other folks)16:15
cdentbut then I guess I tend to define "out there" on a different scale16:16
sdagueyeh, well it was pretty wide spread. And like you said, a lot of this is not just what's on paper by the norms by the implementations that actually exist16:24
elmikosdague: no content arguments from me, but i did find a few grammar nits16:26
sdagueelmiko: ok, cool, there is enough new text in there I assumed there would be some of those16:27
miguelgrinbergelmiko: thx for the rebase16:31
elmikomiguelgrinberg: np, it was sdague's idea. i just wanted to make sure you knew =)16:32
*** Apoorva has joined #openstack-api16:35
*** Apoorva has quit IRC16:37
*** pballand has quit IRC16:39
*** pballand has joined #openstack-api16:47
*** Apoorva has joined #openstack-api16:48
*** alex_klimov has quit IRC16:55
cdentsigmavirus24: thanks for responding to cedric, I was out of juice16:59
sigmavirus24cdent: I'm always up for a good slap fight when referencing RFC sections17:00
cdentha! :)17:00
elmikolol17:00
sigmavirus24I hate that people keep referencing 2616 too17:00
sigmavirus24So that adds fuel17:00
sigmavirus242616 is dead17:00
sigmavirus24Long live the 6 new RFCs17:00
sigmavirus24+ the one for 30817:00
sigmavirus24whatever that one is17:00
*** lucasagomes is now known as lucas-dinner17:01
*** e0ne has quit IRC17:06
*** annegentle has joined #openstack-api17:06
*** annegentle has quit IRC17:12
*** annegentle has joined #openstack-api17:20
*** cdent has quit IRC17:42
*** annegentle has quit IRC17:55
*** annegentle has joined #openstack-api17:56
*** e0ne has joined #openstack-api18:08
*** openstackgerrit has quit IRC18:09
*** openstackgerrit has joined #openstack-api18:09
*** krotscheck is now known as krotscheck_confe18:21
*** krotscheck_confe is now known as krotsch_at_con18:21
*** e0ne is now known as e0ne_18:25
*** e0ne_ has quit IRC18:30
*** e0ne has joined #openstack-api18:46
*** krotsch_at_con is now known as krotsck_at_con18:46
*** annegentle has quit IRC19:06
*** annegentle has joined #openstack-api19:06
*** alex_klimov has joined #openstack-api19:56
*** annegentle has quit IRC20:44
*** annegentle has joined #openstack-api21:11
*** blmartin has quit IRC21:18
HenryGCan someone from the API WG take a look at the API proposed here:  https://review.openstack.org/18080321:37
*** lucas-dinner has quit IRC21:37
elmikoHenryG: ack, i'll take a look21:41
HenryGthanks elmiko21:43
*** lucas-dinner has joined #openstack-api21:50
*** lucas-dinner has quit IRC21:50
elmikoHenryG: i thought neutron was going to be using microversions? (or is that still under debate)21:53
*** Apoorva has quit IRC21:54
*** Apoorva has joined #openstack-api21:55
*** krotsck_at_con is now known as krotscheck22:08
*** annegentle has quit IRC22:10
*** annegentle has joined #openstack-api22:15
*** pballand has quit IRC22:52
*** annegentle has quit IRC23:02
*** markdstafford has joined #openstack-api23:03
*** e0ne has quit IRC23:05
*** annegentle has joined #openstack-api23:22
*** alex_klimov has quit IRC23:29
*** annegentle has quit IRC23:37
*** markdstafford has quit IRC23:50
*** annegentle has joined #openstack-api23:51
*** annegentle has quit IRC23:54

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