*** pballand has joined #openstack-api | 00:14 | |
*** pballand has quit IRC | 00:34 | |
*** Apoorva has quit IRC | 03:12 | |
*** pballand has joined #openstack-api | 04:02 | |
*** pballand has quit IRC | 04:17 | |
*** woodster_ has quit IRC | 05:21 | |
*** salv-orlando has joined #openstack-api | 05:54 | |
*** salv-orlando has quit IRC | 05:56 | |
*** salv-orlando has joined #openstack-api | 05:58 | |
*** etoews has quit IRC | 06:53 | |
*** lucasagomes has joined #openstack-api | 07:32 | |
*** salv-orl_ has joined #openstack-api | 07:37 | |
*** salv-orlando has quit IRC | 07:40 | |
*** fzdarsky has joined #openstack-api | 07:47 | |
*** salv-orl_ has quit IRC | 07:58 | |
*** salv-orlando has joined #openstack-api | 08:00 | |
*** alex_klimov has joined #openstack-api | 08:25 | |
*** e0ne has joined #openstack-api | 08:32 | |
*** e0ne is now known as e0ne_ | 08:38 | |
*** e0ne_ has quit IRC | 08:44 | |
*** e0ne has joined #openstack-api | 08:48 | |
*** cdent has joined #openstack-api | 08:58 | |
*** e0ne is now known as e0ne_ | 09:06 | |
*** e0ne_ has quit IRC | 09:11 | |
*** e0ne has joined #openstack-api | 09:15 | |
*** e0ne is now known as e0ne_ | 10:10 | |
*** e0ne_ has quit IRC | 10:20 | |
*** salv-orlando has quit IRC | 10:29 | |
*** e0ne has joined #openstack-api | 11:09 | |
*** salv-orlando has joined #openstack-api | 11:30 | |
*** salv-orlando has quit IRC | 11:36 | |
*** e0ne is now known as e0ne_ | 11:36 | |
*** lucasagomes is now known as lucas-hungry | 11:42 | |
*** e0ne_ has quit IRC | 11:46 | |
*** salv-orlando has joined #openstack-api | 11:54 | |
*** woodster_ has joined #openstack-api | 12:25 | |
*** agentle has joined #openstack-api | 12:26 | |
*** agentle has quit IRC | 12:35 | |
*** agentle has joined #openstack-api | 12:36 | |
*** e0ne has joined #openstack-api | 12:37 | |
*** lucas-hungry is now known as lucasagomes | 12:43 | |
*** salv-orlando has quit IRC | 12:52 | |
*** openstack has quit IRC | 13:17 | |
*** openstack has joined #openstack-api | 13:18 | |
*** salv-orlando has joined #openstack-api | 13:52 | |
*** agentle has joined #openstack-api | 13:53 | |
*** salv-orlando has quit IRC | 13:57 | |
*** cdent has quit IRC | 13:58 | |
*** cdent has joined #openstack-api | 13:58 | |
*** agentle has quit IRC | 14:01 | |
*** sigmavirus24_awa is now known as sigmavirus24 | 14:07 | |
*** e0ne is now known as e0ne_ | 14:44 | |
*** agentle has joined #openstack-api | 14:47 | |
*** e0ne_ is now known as e0ne | 14:49 | |
*** agentle has quit IRC | 15:00 | |
*** fzdarsky has quit IRC | 15:02 | |
*** Apoorva has joined #openstack-api | 15:23 | |
*** jxstanford has joined #openstack-api | 15:24 | |
*** etoews has joined #openstack-api | 15:26 | |
*** agentle has joined #openstack-api | 15:31 | |
*** pballand has joined #openstack-api | 15:32 | |
*** pballand has quit IRC | 15:43 | |
*** e0ne is now known as e0ne_ | 15:46 | |
*** e0ne_ is now known as e0ne | 15:47 | |
agentle | Anyone have a minute to explain the relationship between ISO 8601 and RFC 822 or 2822? | 15:48 |
---|---|---|
*** cdent has quit IRC | 15:49 | |
*** cdent has joined #openstack-api | 15:49 | |
elmiko | agentle: sorry, i'm not familiar enough with those docs :/ | 15:50 |
agentle | elmiko: s'ok, I'm learning some things by googling :) Seems like our API docs should always say ISO 8601 | 15:51 |
elmiko | agentle: ah, interesting | 15:51 |
agentle | elmiko: 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-api | 15:52 | |
elmiko | agentle: i take it the ISO doc is authoratative over the RFCs? | 15:52 |
elmiko | isn't that always the way ;) | 15:52 |
agentle | elmiko: I think so, RFC is Request for Comments, but this particular one is from 1982 or so :) | 15:53 |
elmiko | oh wow... so yea | 15:53 |
agentle | I just didn't know the exact relationship between RFC and ISO | 15:53 |
agentle | other than ISO is a "standard" | 15:53 |
agentle | and RFC is a draft doc? | 15:53 |
agentle | prior to the standard? | 15:53 |
elmiko | yea, i'm not sure about the relationship in general. but based on the names, i would think rfc comes before iso standard. | 15:54 |
agentle | Looking at https://en.wikipedia.org/wiki/ISO_8601 it seems like an RFC is a "profile?" | 15:54 |
cdent | agentle: are you talking about the way in which rfc 822 has "something" to say about timestamps, but 8601 is the official word? | 15:55 |
elmiko | huh | 15:55 |
agentle | cdent: pretty much. | 15:55 |
cdent | the general rule is that ISO wins over RFC, but often there is no ISO (for example for HTTP) | 15:56 |
agentle | cdent: 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 |
agentle | cdent: none for HTTP!!? | 15:56 |
agentle | yowch! | 15:56 |
cdent | HTTP is "standardized" by RFC | 15:56 |
cdent | which is, generally speaking, the norm for standards | 15:57 |
cdent | only rather special things (like time) get ISO, or things that are especially important for business interaction (also like time) | 15:57 |
cdent | HTTP is still in the land of outlaws, where the RFCs roam | 15:57 |
agentle | ha ha ha cdent that's a perfect explanation | 15:57 |
elmiko | lol | 15:57 |
cdent | which is not so much "yowch!" as "dat's cool man" | 15:57 |
elmiko | yarr mateys, i be draftin' an rfc! | 15:58 |
cdent | It all makes such a lot of sense, doesn't it? | 15:58 |
cdent | If 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 anymore | 15:58 |
elmiko | lol | 15:58 |
cdent | The 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 of | 15:59 |
cdent | Some-Header: some value | 15:59 |
*** pballand has quit IRC | 16:01 | |
cdent | since 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-api | 16:04 | |
elmiko | cdent: nice engineering history lesson =) | 16:05 |
cdent | I HOPE IT'S RIGHT | 16:06 |
cdent | ;) | 16:06 |
elmiko | lol | 16:06 |
elmiko | ME TOO! | 16:06 |
*** alex_klimov has quit IRC | 16:08 | |
*** agentle has quit IRC | 16:15 | |
*** salv-orlando has joined #openstack-api | 16:23 | |
*** e0ne has quit IRC | 16:29 | |
*** lucasagomes is now known as lucas-dinner | 16:29 | |
etoews | elmiko: i added the current crop of frozen guidelines to the agenda of the cross-project meeting https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda | 16:34 |
etoews | i'll be around for the meeting but i put both of our irc nicks in there for a bit of redundancy | 16:34 |
elmiko | etoews: ack, i'll try to make more of those meetings just in case ;) | 16:34 |
etoews | sure. but i think ping us if necessary is okay too. | 16:35 |
etoews | i'm interested in the Return request-id to caller topic so i'll be listening in mostly for that. | 16:35 |
elmiko | ok, cool | 16:36 |
*** cdent has left #openstack-api | 16:57 | |
*** dontalton has joined #openstack-api | 17:01 | |
*** jxstanford has quit IRC | 17:41 | |
*** e0ne has joined #openstack-api | 18:08 | |
*** e0ne is now known as e0ne_ | 18:27 | |
*** e0ne_ has quit IRC | 18:32 | |
*** jxstanford has joined #openstack-api | 18:39 | |
*** e0ne has joined #openstack-api | 18:41 | |
*** jxstanford has quit IRC | 19:11 | |
*** openstackgerrit has quit IRC | 19:21 | |
*** openstackgerrit has joined #openstack-api | 19:22 | |
*** fifieldt_ has joined #openstack-api | 19:30 | |
*** fifieldt has quit IRC | 19:34 | |
*** fzdarsky has joined #openstack-api | 19:50 | |
*** annegentle has joined #openstack-api | 20:04 | |
*** e0ne is now known as e0ne_ | 20:05 | |
*** e0ne_ is now known as e0ne | 20:05 | |
*** annegentle has quit IRC | 20:18 | |
*** annegentle has joined #openstack-api | 20:18 | |
*** fzdarsky has quit IRC | 20:26 | |
*** dontalton has quit IRC | 20:32 | |
*** dontalton has joined #openstack-api | 20:33 | |
*** annegentle has quit IRC | 21:03 | |
*** russellb has joined #openstack-api | 21:05 | |
*** alex_klimov has joined #openstack-api | 21:07 | |
*** annegentle has joined #openstack-api | 21:16 | |
*** e0ne is now known as e0ne_ | 21:28 | |
*** e0ne_ has quit IRC | 21:29 | |
*** annegentle has quit IRC | 21:34 | |
*** annegentle has joined #openstack-api | 21:34 | |
*** e0ne has joined #openstack-api | 21:34 | |
*** e0ne is now known as e0ne_ | 21:42 | |
*** e0ne_ is now known as e0ne | 21:45 | |
*** e0ne has quit IRC | 21:55 | |
elmiko | etoews: so, what was with the request-id discussion? | 22:01 |
etoews | do you mean the beating tpatil took? | 22:03 |
etoews | elmiko ^ | 22:03 |
elmiko | i just meant more in general | 22:04 |
elmiko | i 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 |
etoews | in this case, not just error conditions | 22:05 |
etoews | a lot of services return a "request id" to the caller in a header | 22:05 |
elmiko | ah, ok | 22:05 |
etoews | that request id can be used in all kinds of ways but ya, mostly when there's an error condition. | 22:06 |
elmiko | sounds 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-api | 22:09 | |
etoews | these request ids aren't codes (although that's in the works too) | 22:11 |
etoews | you can just think of these as a uuid for request/response you get from a cloud | 22:11 |
etoews | it's baffling to me that there's so much resistance to this | 22:12 |
elmiko | ok, so a little lower volume than an id for each rest transaction? | 22:13 |
*** annegentle has quit IRC | 22:13 | |
elmiko | yea, certainly seems useful | 22:13 |
stevelle | the problem really is a difference in how folks are thinking about it | 22:15 |
elmiko | how so? | 22:16 |
stevelle | Is 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 |
stevelle | how much does it need to be broken down seems to be a source of differing opinions | 22:19 |
elmiko | that makes sense | 22:19 |
*** dontalton2 has joined #openstack-api | 22:20 | |
stevelle | I suspect there is more service/project sovereignty issues going on as well | 22:20 |
stevelle | that isn't clear for me still | 22:21 |
elmiko | interesting | 22:21 |
elmiko | oh well, i'm off for awhile. take care all! | 22:21 |
*** annegent_ has quit IRC | 22:22 | |
*** annegentle has joined #openstack-api | 22:22 | |
*** sigmavirus24 is now known as sigmavirus24_awa | 22:26 | |
*** alex_klimov has quit IRC | 22:28 | |
*** pballand has quit IRC | 22:28 | |
*** pballand has joined #openstack-api | 22:31 | |
*** annegentle has quit IRC | 23:03 | |
*** annegentle has joined #openstack-api | 23:05 | |
*** annegentle has quit IRC | 23:10 | |
*** pballand has quit IRC | 23:12 | |
*** dontalton2 has quit IRC | 23:16 | |
*** dontalton has quit IRC | 23:16 | |
*** lucas-dinner has quit IRC | 23:17 | |
*** pballand has joined #openstack-api | 23:32 | |
*** pballand has quit IRC | 23:34 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!