Monday, 2015-05-04

*** alex_xu has joined #openstack-api01:15
*** salv-orl_ has joined #openstack-api06:58
*** e0ne has joined #openstack-api09:04
*** e0ne has quit IRC09:10
*** salv-orlando has joined #openstack-api09:13
*** salv-orl_ has quit IRC09:13
*** salv-orlando has quit IRC09:43
*** salv-orl_ has joined #openstack-api09:46
*** salv-orlando has joined #openstack-api09:50
*** salv-orl_ has quit IRC09:53
*** salv-orl_ has joined #openstack-api10:31
*** e0ne has joined #openstack-api10:31
*** salv-orlando has quit IRC10:34
*** salv-orl_ has quit IRC10:46
*** salv-orlando has joined #openstack-api10:47
*** salv-orlando has quit IRC11:23
*** ryansb has joined #openstack-api11:47
*** salv-orlando has joined #openstack-api12:24
*** subscope has joined #openstack-api12:35
*** salv-orlando has quit IRC12:37
*** _elmiko is now known as elmiko13:07
*** elmiko has joined #openstack-api13:08
*** e0ne has quit IRC14:14
*** sigmavirus24_awa is now known as sigmavirus2414:14
*** salv-orlando has joined #openstack-api14:16
*** fzdarsky has joined #openstack-api14:22
*** salv-orlando has quit IRC14:32
*** etoews has quit IRC15:19
*** e0ne has joined #openstack-api15:28
*** salv-orlando has joined #openstack-api15:41
*** sigmavirus24 is now known as Apsu_15:53
*** Apsu_ is now known as sigmavirus2415:53
*** salv-orlando has quit IRC16:12
*** fzdarsky has quit IRC16:19
*** fzdarsky has joined #openstack-api16:22
*** salv-orlando has joined #openstack-api17:30
*** salv-orlando has quit IRC17:39
*** subscope_ has joined #openstack-api18:49
*** salv-orlando has joined #openstack-api19:22
*** e0ne has quit IRC19:26
*** e0ne has joined #openstack-api19:30
*** salv-orlando has quit IRC19:33
*** e0ne has quit IRC19:35
*** e0ne has joined #openstack-api19:37
*** e0ne has quit IRC19:39
*** e0ne has joined #openstack-api19:39
*** e0ne has quit IRC19:41
*** e0ne has joined #openstack-api19:42
*** e0ne has quit IRC19:42
*** e0ne has joined #openstack-api19:43
*** e0ne has quit IRC19:43
*** e0ne has joined #openstack-api19:45
*** e0ne has quit IRC19:45
*** e0ne has joined #openstack-api19:57
*** subscope_ has quit IRC20:08
*** sigmavirus24 has quit IRC20:23
*** sigmavirus24 has joined #openstack-api20:24
*** e0ne has quit IRC20:26
*** e0ne has joined #openstack-api20:30
*** sigmavirus24 has quit IRC20:34
*** sigmavirus24 has joined #openstack-api20:38
*** joesavak has joined #openstack-api20:43
*** e0ne has quit IRC20:45
*** etoews has joined #openstack-api20:47
*** salv-orlando has joined #openstack-api20:55
*** woodster_ has joined #openstack-api21:11
woodster_Hello folks, I was wondering if guidance on POST vs PUT requests for canonical OpenStack APIs is in the works, per this section?: https://github.com/openstack/api-wg/blob/4319ae3459f1dd79f5fc212c8a8dc38ec4fcd4f1/guidelines/http.rst#http-methods21:15
ryansbwoodster_: well, it's a TODO, but I don't think anybody's put a spec up yet21:23
woodster_ryansb: thanks. Yeah we were having a discussion about POST vs PUT on barbican earlier and someone suggested asking the api-wg channel about it.21:24
woodster_ryansb: I was going to look at what other projects were doing in this regard.21:25
ryansbah, well the general guideline (from the RFCs) is to use POST for creates only21:25
ryansband puts for updates21:25
woodster_ryansb: that's been my understanding as well, but someone mentioned that Keystone updates user info via a POST per this example: http://docs.openstack.org/developer/keystone/api_curl_examples.html#post-v3-users-user-id-password21:29
elmikoimo, woodster_ you had it correct to being with ;)21:32
elmiko*begin21:32
woodster_elmiko: yeah, I was hoping so, but I'm not 100% I'm sure 100% of the time!21:34
elmikohehe, yea. always good to check around =)21:34
woodster_would it be good to bring this up as an agenda item for the next wg meeting time permitting?21:36
elmikoyea, definitely21:39
elmikonext meeting is this thursday at noon eastern time21:39
woodster_sounds good! Thanks21:40
elmikowoodster_: if you don't make it, i'll try to remember to bring it up21:40
woodster_elmiko: that sounds good.21:40
ryansbwoodster_: also, you can add "APIImpact" in the commit message for specs and reviews21:51
elmikooh yea, good point ryansb21:51
woodster_ryansb: I was thinking such tags were more for a filter target rather than triggering interested parties to review things...is that not the case though?21:52
*** fzdarsky has quit IRC21:53
elmikowoodster_: in past meetings we have used the APIImpact flag to help direct traffic towards reviews. sometimes we discuss them in the meeting, other times we have just looked at the list to call attention to certain reviews.21:58
elmikoit kinda depends on how busy the agenda is, and what topics folks would like to discuss21:58
ryansbwell we use filters to find them, of course22:01
ryansbbut I have a query for APIImpact in my gerrit dash, and I try to review new ones in a timely fashion22:02
elmikothat's pretty good, i don't even seem to have time left for *Impact reviews =(22:04
elmiko*ever22:04
ryansbelmiko: I admit to stretching the definition of "timely" a tad22:06
elmikohehe ;)22:06
elmikoryansb: have you met much resistance when making comments about APIImpact?22:07
ryansbno, folks are pretty receptive22:07
elmikothat's cool22:07
*** elmiko is now known as _elmiko22:28
woodster__elmiko: ryansb that's good to know actually, thanks22:31
*** joesavak has quit IRC22:36

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