Tuesday, 2015-06-23

*** pballand has joined #openstack-api00:14
*** pballand has quit IRC00:34
*** Apoorva has quit IRC03:12
*** pballand has joined #openstack-api04:02
*** pballand has quit IRC04:17
*** woodster_ has quit IRC05:21
*** salv-orlando has joined #openstack-api05:54
*** salv-orlando has quit IRC05:56
*** salv-orlando has joined #openstack-api05:58
*** etoews has quit IRC06:53
*** lucasagomes has joined #openstack-api07:32
*** salv-orl_ has joined #openstack-api07:37
*** salv-orlando has quit IRC07:40
*** fzdarsky has joined #openstack-api07:47
*** salv-orl_ has quit IRC07:58
*** salv-orlando has joined #openstack-api08:00
*** alex_klimov has joined #openstack-api08:25
*** e0ne has joined #openstack-api08:32
*** e0ne is now known as e0ne_08:38
*** e0ne_ has quit IRC08:44
*** e0ne has joined #openstack-api08:48
*** cdent has joined #openstack-api08:58
*** e0ne is now known as e0ne_09:06
*** e0ne_ has quit IRC09:11
*** e0ne has joined #openstack-api09:15
*** e0ne is now known as e0ne_10:10
*** e0ne_ has quit IRC10:20
*** salv-orlando has quit IRC10:29
*** e0ne has joined #openstack-api11:09
*** salv-orlando has joined #openstack-api11:30
*** salv-orlando has quit IRC11:36
*** e0ne is now known as e0ne_11:36
*** lucasagomes is now known as lucas-hungry11:42
*** e0ne_ has quit IRC11:46
*** salv-orlando has joined #openstack-api11:54
*** woodster_ has joined #openstack-api12:25
*** agentle has joined #openstack-api12:26
*** agentle has quit IRC12:35
*** agentle has joined #openstack-api12:36
*** e0ne has joined #openstack-api12:37
*** lucas-hungry is now known as lucasagomes12:43
*** salv-orlando has quit IRC12:52
*** openstack has quit IRC13:17
*** openstack has joined #openstack-api13:18
*** salv-orlando has joined #openstack-api13:52
*** agentle has joined #openstack-api13:53
*** salv-orlando has quit IRC13:57
*** cdent has quit IRC13:58
*** cdent has joined #openstack-api13:58
*** agentle has quit IRC14:01
*** sigmavirus24_awa is now known as sigmavirus2414:07
*** e0ne is now known as e0ne_14:44
*** agentle has joined #openstack-api14:47
*** e0ne_ is now known as e0ne14:49
*** agentle has quit IRC15:00
*** fzdarsky has quit IRC15:02
*** Apoorva has joined #openstack-api15:23
*** jxstanford has joined #openstack-api15:24
*** etoews has joined #openstack-api15:26
*** agentle has joined #openstack-api15:31
*** pballand has joined #openstack-api15:32
*** pballand has quit IRC15:43
*** e0ne is now known as e0ne_15:46
*** e0ne_ is now known as e0ne15:47
agentleAnyone have a minute to explain the relationship between ISO 8601 and RFC 822 or 2822?15:48
*** cdent has quit IRC15:49
*** cdent has joined #openstack-api15:49
elmikoagentle: sorry, i'm not familiar enough with those docs :/15:50
agentleelmiko: s'ok, I'm learning some things by googling :) Seems like our API docs should always say ISO 860115:51
elmikoagentle: ah, interesting15:51
agentleelmiko: unfortunately, I found some Rackspace docs that have RFC 822. Which is nearly identical. Hence, confusion!15:52
agentle:)15:52
*** pballand has joined #openstack-api15:52
elmikoagentle: i take it the ISO doc is authoratative over the RFCs?15:52
elmikoisn't that always the way ;)15:52
agentleelmiko: I think so, RFC is Request for Comments, but this particular one is from 1982 or so :)15:53
elmikooh wow... so yea15:53
agentleI just didn't know the exact relationship between RFC and ISO15:53
agentleother than ISO is a "standard"15:53
agentleand RFC is a draft doc?15:53
agentleprior to the standard?15:53
elmikoyea, i'm not sure about the relationship in general. but based on the names, i would think rfc comes before iso standard.15:54
agentleLooking at https://en.wikipedia.org/wiki/ISO_8601 it seems like an RFC is a "profile?"15:54
cdentagentle: are you talking about the way in which rfc 822 has "something" to say about timestamps, but 8601 is the official word?15:55
elmikohuh15:55
agentlecdent: pretty much.15:55
cdentthe general rule is that ISO wins over RFC, but often there is no ISO (for example for HTTP)15:56
agentlecdent: so in the API reference documents, for example, always refer to ISO 8601 I think. But I've now found documents that refer to RFC 822. Which seems to be an Email format.15:56
agentlecdent: none for HTTP!!?15:56
agentleyowch!15:56
cdentHTTP is "standardized" by RFC15:56
cdentwhich is, generally speaking, the norm for standards15:57
cdentonly rather special things (like time) get ISO, or things that are especially important for business interaction (also like time)15:57
cdentHTTP is still in the land of outlaws, where the RFCs roam15:57
agentleha ha ha cdent that's a perfect explanation15:57
elmikolol15:57
cdentwhich is not so much "yowch!" as "dat's cool man"15:57
elmikoyarr mateys, i be draftin' an rfc!15:58
cdentIt all makes such a lot of sense, doesn't it?15:58
cdentIf you're one of the cool kids as soon as something goes off to be ISO standardized then it is pretty much not worth paying attention to anymore15:58
elmikolol15:58
cdentThe reason RFC 822 keeps coming up all over the place is because it formalized a format for handling email and set the standard for headers being separated from body by two blank lines, and for header information to take the form of15:59
cdentSome-Header: some value15:59
*** pballand has quit IRC16:01
cdentsince then loads of other RFCs (including early HTTP RFCs) followed the precedents set in 822 (including on topics like time)16:01
*** pballand has joined #openstack-api16:04
elmikocdent: nice engineering history lesson =)16:05
cdentI HOPE IT'S RIGHT16:06
cdent;)16:06
elmikolol16:06
elmikoME TOO!16:06
*** alex_klimov has quit IRC16:08
*** agentle has quit IRC16:15
*** salv-orlando has joined #openstack-api16:23
*** e0ne has quit IRC16:29
*** lucasagomes is now known as lucas-dinner16:29
etoewselmiko: i added the current crop of frozen guidelines to the agenda of the cross-project meeting https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda16:34
etoewsi'll be around for the meeting but i put both of our irc nicks in there for a bit of redundancy16:34
elmikoetoews: ack, i'll try to make more of those meetings just in case ;)16:34
etoewssure. but i think ping us if necessary is okay too.16:35
etoewsi'm interested in the Return request-id to caller topic so i'll be listening in mostly for that.16:35
elmikook, cool16:36
*** cdent has left #openstack-api16:57
*** dontalton has joined #openstack-api17:01
*** jxstanford has quit IRC17:41
*** e0ne has joined #openstack-api18:08
*** e0ne is now known as e0ne_18:27
*** e0ne_ has quit IRC18:32
*** jxstanford has joined #openstack-api18:39
*** e0ne has joined #openstack-api18:41
*** jxstanford has quit IRC19:11
*** openstackgerrit has quit IRC19:21
*** openstackgerrit has joined #openstack-api19:22
*** fifieldt_ has joined #openstack-api19:30
*** fifieldt has quit IRC19:34
*** fzdarsky has joined #openstack-api19:50
*** annegentle has joined #openstack-api20:04
*** e0ne is now known as e0ne_20:05
*** e0ne_ is now known as e0ne20:05
*** annegentle has quit IRC20:18
*** annegentle has joined #openstack-api20:18
*** fzdarsky has quit IRC20:26
*** dontalton has quit IRC20:32
*** dontalton has joined #openstack-api20:33
*** annegentle has quit IRC21:03
*** russellb has joined #openstack-api21:05
*** alex_klimov has joined #openstack-api21:07
*** annegentle has joined #openstack-api21:16
*** e0ne is now known as e0ne_21:28
*** e0ne_ has quit IRC21:29
*** annegentle has quit IRC21:34
*** annegentle has joined #openstack-api21:34
*** e0ne has joined #openstack-api21:34
*** e0ne is now known as e0ne_21:42
*** e0ne_ is now known as e0ne21:45
*** e0ne has quit IRC21:55
elmikoetoews: so, what was with the request-id discussion?22:01
etoewsdo you mean the beating tpatil took?22:03
etoewselmiko ^22:03
elmikoi just meant more in general22:04
elmikoi need to read the spec, but i wasn't quite following the gist. seemed like codes to help line up with error conditions experienced by end users?22:05
etoewsin this case, not just error conditions22:05
etoewsa lot of services return a "request id" to the caller in a header22:05
elmikoah, ok22:05
etoewsthat request id can be used in all kinds of ways but ya, mostly when there's an error condition.22:06
elmikosounds almost nightmarish to try and link those codes with specific actions, wouldn't there be a *ton* of them? (as evidenced by the boris mq question)22:08
*** annegent_ has joined #openstack-api22:09
etoewsthese request ids aren't codes (although that's in the works too)22:11
etoewsyou can just think of these as a uuid for request/response you get from a cloud22:11
etoewsit's baffling to me that there's so much resistance to this22:12
elmikook, so a little lower volume than an id for each rest transaction?22:13
*** annegentle has quit IRC22:13
elmikoyea, certainly seems useful22:13
stevellethe problem really is a difference in how folks are thinking about it22:15
elmikohow so?22:16
stevelleIs a request-id for a rest call for one service or all the rest calls performed across all services to perform an action?22:18
stevellehow much does it need to be broken down seems to be a source of differing opinions22:19
elmikothat makes sense22:19
*** dontalton2 has joined #openstack-api22:20
stevelleI suspect there is more service/project sovereignty issues going on as well22:20
stevellethat isn't clear for me still22:21
elmikointeresting22:21
elmikooh well, i'm off for awhile. take care all!22:21
*** annegent_ has quit IRC22:22
*** annegentle has joined #openstack-api22:22
*** sigmavirus24 is now known as sigmavirus24_awa22:26
*** alex_klimov has quit IRC22:28
*** pballand has quit IRC22:28
*** pballand has joined #openstack-api22:31
*** annegentle has quit IRC23:03
*** annegentle has joined #openstack-api23:05
*** annegentle has quit IRC23:10
*** pballand has quit IRC23:12
*** dontalton2 has quit IRC23:16
*** dontalton has quit IRC23:16
*** lucas-dinner has quit IRC23:17
*** pballand has joined #openstack-api23:32
*** pballand has quit IRC23:34

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