16:00:07 #startmeeting oslo 16:00:08 Meeting started Mon Jun 20 16:00:07 2016 UTC and is due to finish in 60 minutes. The chair is harlowja_at_home. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:12 The meeting name has been set to 'oslo' 16:00:12 hola 16:00:33 courtesy ping for amotoki, amrith, bknudson, bnemec, dansmith, dhellmann, dims 16:00:33 courtesy ping for dougwig, e0ne, flaper87, garyk, gcb, GheRivero, haypo 16:00:34 courtesy ping for ihrachyshka, jd__, jecarey, johnsom, jungleboyj, kgiusti, kragniz 16:00:34 courtesy ping for lifeless, lintan, lxsli, Nakato, ozamiatin, rbradfor, redrobot 16:00:34 courtesy ping for rpodolyaka, sergmelikyan, sileht, spamaps, sreshetnyak, sreshetnyak, stevemar 16:00:35 courtesy ping for therve, thinrichs, toabctl, viktors, zhiyan, zzzeek 16:00:36 hullo! 16:00:41 let's see anyone around today :-P 16:00:44 or is everyone on vacation, lol 16:01:02 o/ o/ 16:01:09 yo yo 16:01:12 o/ 16:01:41 harlowja_at_home, my IRC didn't alert me, seems and IRC disconnect has me on an alternative nic? 16:01:47 hmmmm 16:01:48 evil irc 16:02:02 i forgive u this time, lol 16:02:07 I'd say unreliable network but ... 16:02:14 :-P 16:02:17 #topic Red flags for/from liaisons 16:02:22 nothing from neutron side 16:02:27 o/ 16:02:29 #link http://status.openstack.org/openstack-health/#/?groupKey=build_name&resolutionKey=hour&searchProject=-with-oslo 16:02:35 Nothing from Cinder that I am aware of. 16:02:35 seems ok from that above link 16:02:57 cool 16:03:23 guess everyone else on vacation, lol 16:04:45 #topic Releases for newton 16:05:25 i'll get a release bundle out in a little bit/later today so feel free to yell at me if u want me to add/remove a release from that 16:06:32 #topic Architecture working group 16:06:47 since it did mention oslo, i'm just gonna mention it here as well :-P 16:06:53 #link http://lists.openstack.org/pipermail/openstack-dev/2016-June/097668.html 16:07:06 tbd what that will end up being, but thought folks here might be interested 16:07:24 aka the wishful thinking group 16:07:25 harlowja_at_home, I did read this email from Spamaps 16:07:31 jd__, lol 16:07:34 jd__, welcome, who are u 16:07:35 lol 16:08:18 rbradfor, ya, i'm not sure what it will be yet, but meh, can't hurt to see where it goes 16:08:34 harlowja_at_home, OpenStack lacks arctitecture direction, and Oslo should be a least aware of what is discussed. I for one will be following the group. 16:08:47 yup 16:09:21 #topic Time isoformat() 16:09:29 jd__, while i have u, amrith are u around ;) 16:09:32 yes 16:09:42 I am a very big around, my dr. tells me 16:09:51 amrith, where we at with that isotime adjustments 16:10:06 I've incorporated all of the comments I've got 16:10:09 #link https://review.openstack.org/#/c/329384/ 16:10:16 primarily from bknudson_ 16:10:18 jd__, i know u are gonna be like 'no way' 16:10:24 but wondering if we can compromise 16:10:52 I don't believe jd__ responded to my question 16:11:11 right 16:11:26 gonna see if we can get him while hes here ;) (not entrapment) 16:11:27 lol 16:12:16 so ... I'm waiting for confirmation from bknudson_ that this works for him 16:12:21 and would also like to close the loop with dims 16:12:24 amrith, kk 16:12:29 i'll fly to paris to find jd__ 16:12:30 the last time we were talking about this, dims was on the #tc meeting 16:12:30 lol 16:12:31 I gave my opinion, that's all :) 16:12:38 it's just _my_ opinion :) 16:12:49 noooooooo its _the_ opinion 16:12:53 if nobody shares it, do whatever you like, or follow me :) 16:12:58 harlowja_at_home: ah then it's not only me :-) 16:13:01 ha 16:14:23 so, where do we go from here? 16:14:49 amrith, i guess bknudson_ needs to double check it over 16:15:50 i'd like to be able to maybe send a ML email to the projects that have copied timeutils code, and if those folks will look over this code and say 'yes we'll use that' then I think that's a big 'ok from me, even if its not the ideal solution' path (life is compromises after all) 16:16:02 amrith, u did some research into who has copied that right 16:16:15 "Where do we go from here now that all of the children have grown up 16:16:15 And how do we spend our time knowin' nobody gives us a damn" - Alan Parsons Project (not part of the big tent) 16:16:25 lol 16:16:45 i don't ever wanna grow up 16:17:11 * kgiusti gave up on that long ago.... 16:17:23 ok, we'll wait for bknudson_ 16:17:33 k 16:17:40 are we there yet? 16:17:45 bknudson_, are we there yet? 16:18:04 i'll form a little email to the dev list, so that others that have copied this can look it over 16:18:13 (or copied the old version or whatever) 16:18:36 harlowja_at_home, my earlier email listed those projects 16:18:42 may save you the time having to go find them 16:18:44 kk, i'll find that email then :-P 16:19:30 http://openstack.markmail.org/thread/xosf5h7gvhqdwtz7 16:19:35 thx 16:19:40 amrith : harlowja_at_home : i have the same opinion as jd__ and am ok if everyone wants to get it in 16:20:43 dims, I know that was the case. But does the fact that several projects have just copied the code as it was mean that it makes sense for oslo to reconsider? 16:20:45 dims, yup, if there is enough agreement that projects copying it would move to it, then i'm gonna lean on the 'its ok, its not perfect, but if it helps have less variation in all the projects, then thats ok' 16:21:20 we can save up the 'major disagreement' stuff for bigger things IMHO :-P 16:21:33 ah, ok 16:21:35 like, the architecture working group, lol 16:22:07 yes, as one of my former managers said to me "take your little problems away and come back to me when they are big problems" 16:22:15 ya 16:22:18 amrith : my main thing here was folks are using it in API w/o realizing the problems. if we add it here, they will continue to do so and i did not want us to be part of that loop 16:22:35 dims, that's not the current proposal 16:22:44 the current proposal is NOT to undeprecate the old function 16:22:52 but to propose a new one that doens't have those problems 16:23:01 isotime will be deprecated 16:23:05 a new function is being added 16:23:12 that wraps isoformat() 16:23:28 and provides an iso compatible output that projects can use without changing their API's. 16:23:39 an idea, should we call this isoformat2 ? 16:23:48 it is called isoformat() 16:23:48 and leave the old one as is 16:23:53 timeutils.isoformat() 16:23:59 as opposed to datetime.datetime.isoformat() 16:24:56 ah, i see. dims commented on patch set 1. 16:24:59 this is now patch set 2 16:25:00 https://review.openstack.org/#/c/329384/2 16:25:47 the deprecated function was timeutils.isotime() 16:26:07 yes rbradfor 16:26:12 ah 16:26:13 kk 16:26:29 thx 16:27:25 ok, let's continue chugging away at that one, seems like a few tiny loose ends to close 16:27:43 #topic Stuck reviews and/or specs and/or code 16:27:59 any reviews people want to bring up (besides the isoformat one) 16:28:19 bring your reviews, 10 for 1$ 16:28:19 lol 16:28:33 who wants to be an AMQP 1.0 guru? 16:28:44 u? 16:28:45 16:28:45 lol 16:28:58 i'd like to learn more about it :) 16:29:05 but i'm not sure if that's guru-level 16:29:16 You can be like me and fake it! 16:29:16 mild-guru 16:29:19 lol 16:29:35 i'll take 1 mild-guru and a diet coke 16:29:42 sorry, I had to go schedule a root canal 16:29:49 which starts in 2m :) 16:29:52 :-/ 16:30:03 harlowja_at_home, I would vote for somebody that is a messaging guru giving some beginner tutorial (hangout) about how messaging works (i.e. the guts) and then how AMQP,0MQ and others impact that usage 16:30:13 ya me too 16:30:13 root canaling - is much more fun... 16:30:25 rbradfor, agreed 16:30:30 wonder if we can find such a person 16:30:41 amrith, just go tom hanks castaway that tooth. 16:30:41 I'm writing up a doc describing the amqp 1.0 driver design FWIT 16:30:45 just took a quick look at https://review.openstack.org/#/c/329384/3/oslo_utils/timeutils.py -- I like the changes since they're backwards compatible. 16:31:04 kgiusti, nice 16:31:11 thx bknudson_ 16:31:13 but I'm a non guru zmq-wise 16:31:24 1/4 guru? 16:31:25 lol 16:31:46 amrith : does not help with my issue. All REST API should be 'Z' prefixed and should only have UTC time 16:32:25 dims, why is that? 16:32:33 or should we take this up at a later meeting/offline 16:32:37 other then knowing messaging (and hence rabbitMQ) is critical for project communication it would be good for more Oslo people (well ok, just me then) to appreciate it's importance with intermediate skills? 16:32:49 offline ~ on another line 16:32:53 rbradfor, +1 16:33:18 amrith : http://markmail.org/message/elxv2l4xhrksvpse 16:33:21 maybe we can have a tiny session/hangout with sileht, the zeromq guy (i forget his name), and kgiusti 16:33:24 hey I can blabber on about amqp 1.0 for hours - if you're into root canals and such... 16:33:46 dims, yes, I've read that email but I'm not sure it is complete 16:33:49 longer discussion I guess 16:33:49 i'm all about the root canals 16:34:07 "don't stop now" -- little shop of horror ref 16:34:19 amrith: keystone will have to ensure that "at" parameters are tagged as UTC? (Not sure how to do that) 16:34:37 maybe they will be already somehow... I think they mostly come from a DB query. 16:34:55 we'll get the arch doc done and then if people are interested in a hangout let me know.... 16:35:09 (I've looked at the python docs and for some reason it's not obvious how to get a UTC timzone) 16:35:27 kgiusti, cool, i think rbradfor and i at least would be :) 16:35:30 we like root canals, lol 16:35:55 there will be laughing gas 16:35:55 harlowja_at_home: I'm only into the laughing gas, myself. 16:35:58 harlowja_at_home, hey, was there a poll for you to license "we", I don't 16:36:00 he he 16:36:09 rbradfor, ha 16:36:18 ya, that pool was earlier 16:36:20 *poll 16:36:28 poll of 1 16:36:45 dictators are not welcome here :) 16:36:54 :-P 16:36:58 rbradfor: not interested in wading thru https://review.openstack.org/#/c/320492/ 16:37:31 rbradfor: it will put hair on your chest - which is good because you'll pull out everything on your head... 16:37:53 lol 16:38:20 kgiusti, I don't need any accelerated hair loss ideas 16:38:48 rbradfor: I've got plenty extra if you need some... 16:38:55 amrith : scars from web services wars (R3217 - http://www.ws-i.org/profiles/basicsecurityprofile-1.0.html) 16:39:09 u guys are giving out chest hair? or hair loss ideas 16:39:12 idk anymore, lol 16:39:39 #topic Open discussion 16:39:49 harlowja_at_home: rbradfor: but seriously - I'd like to land these patches on the feature branch at least.... 16:40:07 kgiusti, agreed, i'm gonna try to get through some of them this week, i swear 16:40:19 Some folks from the massive distributed WG are interested in trying out the new routing feature. 16:40:24 https://review.openstack.org/#/q/status:open+project:openstack/oslo.messaging+branch:feature/amqp-dispatch-router right? 16:41:09 harlowja_at_home: ya - and I have one more (last hopefully) large patch to follow. 16:41:14 k 16:42:14 harlowja_at_home: thank you!!! 16:42:20 np :) 16:43:03 dims, ' Davanum Srinivas (Computer Associates)' nice nice, u in the appendix C 16:43:19 (of that web service thing) 16:43:24 deep scars :) 16:43:31 cleaned it up with soap i hope 16:43:32 lol 16:43:37 (the wound/scar) 16:43:43 :) 16:44:20 ok, anything else people want to bring up? 16:44:27 else, u all get a few minutes back! 16:44:28 lol 16:44:36 (and u can go read that nice SOAP document) 16:44:36 lol 16:44:40 distracted by DockerCon live sessions right now. 16:44:48 ah 16:44:53 * harlowja_at_home i should watch those to 16:45:44 Great slide a few mins ago. The best tools... 1. Get out of the way. 2. adapt to you. 3. make the powerful simple. I wonder if other projects should assess this. 16:46:09 that's the definition of openstack. 16:46:10 he he 16:46:58 4. be written in go, ha 16:47:17 alright, andddd with that, ---> #openstack-oslo i guess for further fun commentary 16:47:26 thanks for showing up folks :) 16:47:36 #endmeeting