16:00:16 #startmeeting api wg 16:00:17 Meeting started Thu Jan 14 16:00:16 2016 UTC and is due to finish in 60 minutes. The chair is etoews. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:21 The meeting name has been set to 'api_wg' 16:00:28 heyo/ 16:00:54 hiya 16:01:04 o/ 16:02:14 slow day... 16:02:18 smallish crowd today 16:02:30 #topic agenda 16:02:37 #link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda 16:02:47 #topic previous meeting action items 16:02:56 #link http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-12-17-16.00.html 16:03:38 I did mine 16:03:44 \o/ 16:03:54 huzzah! 16:03:56 https://wiki.openstack.org/wiki/API_Working_Group/Current_Design/Version_Responses#Telemetry 16:04:23 I know, right? I'm pretty impressed too. 16:04:23 that page has filled out nicely 16:04:31 hehe 16:04:44 looks like a pretty good cross section of projects to me 16:04:50 yea 16:05:15 This big "GET / requires auth, which is probably a bug. " is being fixed in at least gnocchi 16:05:19 s/big/bit/ 16:05:40 i noticed sahara does that too, should these calls be unauth'd? 16:06:29 I tend to think: why should they be authed? 16:06:33 or is that a decision we leave up to the projects? 16:06:41 yea, i agree. just didn't know the full history 16:06:49 me neither 16:07:17 ok, maybe i'll push on sahara then. thanks 16:07:42 It turns out that the fix in gnocchi is more complex than I would have predicted, because of keystone middleware 16:07:50 doh! 16:07:59 https://review.openstack.org/#/c/266301/ 16:09:51 okay to move on? 16:10:06 good here 16:10:12 #topic openstack summit in austin 16:10:34 #link https://www.openstack.org/summit/austin-2016/ 16:11:02 i actually live in the austin area so this will be nice :) 16:11:17 so, you'll be showing us the hot night spots ;) 16:11:29 :P 16:12:05 i know a few places to get a good beer 16:12:22 \o/ 16:12:29 * cdent needs a bit of mexican food 16:12:32 they better be serving breakfast tacos every morning or it will be an outrage 16:12:39 ooh, yea, i heard rumors of breakfast tacos 16:12:46 must try 16:12:48 \o/ 16:13:03 as for the actual summit itself, i'm totally up for doing another "state of the wg" type session 16:13:12 cool. 16:13:14 it was small in tokyo, but we had a really nice discussion 16:13:25 the new track rules are interesting but kinda make sense 16:13:26 oh mean, I forgot Austin would have great texmex 16:13:38 we have to submit it formally as a presentation this year. 16:13:39 best summit ever 16:13:44 and i would really like to talk more about the mission of the wg, and if it's appropriate to work on code projects under the guise of the wg 16:14:02 didn't we already okay that? 16:14:13 ryansb: it's gonna be a good one ;) 16:14:15 ah, did we? if so, maybe i misse dit 16:14:20 there was a bit of pushback from somewher, but I can't remember where/when 16:14:29 things went funky one xmas rolled around 16:14:29 yea, that's what i thought too 16:14:32 everything is a haze now 16:14:44 +1 16:14:52 we discussed in an api wg meeting sometime last year 16:15:03 yea, when the fairy-slipper stuff came up 16:15:20 and actually, i think i owe the ML a message about project ideas 16:15:31 i'm basically a +0 on it 16:15:40 ok, noted 16:15:49 no strong opinion but i'm certainly not against it. 16:15:52 we had some good excitement for an "example project" at the summit 16:16:04 and i have zero time to put towards something like that 16:16:09 fair 16:16:26 but if you can build some momentum for the api wg with it. more power to you. 16:16:27 i'm up for taking the reigns on this one, if we get some good traction 16:16:40 yea, i'm trying to build up a good piece of code to show off 16:16:42 * cdent gives elmiko some leather 16:16:44 cool. just go for it. no need for more discussion. 16:16:48 you can probably pick up some boots in austin 16:16:51 great, thanks! 16:17:11 you can definitely pick up boots in austin. they come with a free 10 gallon hat. 16:17:20 ooh, nice =) 16:17:31 for an extra buck, you can upgrade to a 15 gallon hat 16:17:33 big hat, no cattle 16:18:01 cdent: elmiko: how do you want to get the prez proposal written up? etherpad like last cycle? 16:18:11 sounds good 16:18:13 etoews: yea, i think that work 16:18:15 s 16:18:23 do you have a link handy to the last one? 16:18:40 * cdent looks at elmiko 16:19:06 * etoews looks at elmiko 16:19:10 #link https://etherpad.openstack.org/p/mitaka-api-wg-session-plans 16:19:12 this one? 16:20:07 i don't even know what the n release is going to be called :| 16:20:29 legal is still chewing, aren't they? 16:20:50 ¯\_(ツ)_/¯ 16:20:56 cdent: yeah, haven't seen anything other than the poll 16:21:03 so someone is chewing 16:21:28 far too much time/effort/money is spent on that naming nonsense IMO 16:21:43 anyway, don't want to go off on that tangent 16:22:49 #link https://etherpad.openstack.org/p/austin-api-wg-session-plans 16:23:30 i'll drop some stuff on that tomorrow after sleeping on it 16:23:48 (that's my new strategy for everything: tomorrow after I sleep on it) 16:24:01 nice 16:25:13 cdent: your taking advantage of your diffuse mode thinking 16:25:19 s/your/you're/ 16:25:25 i do that often too 16:25:47 I guess someone decided the proposal process was too chaotic. Lots more rules and forms and guidelines and what not this time around. I guess that's to dissuade the dilletantes 16:26:02 diffuse mode is where the cool stuff is 16:26:15 i copied the CFP sections into the etherpad. i think most of those section can be pretty "thin" for a WG prez proposal. 16:26:22 agreed 16:27:17 okay. we just need to get it finished by feb. 1. lots of time. 16:27:30 let's move on 16:27:37 cool 16:27:40 #topic magnum api refresh 16:27:50 #link https://etherpad.openstack.org/p/magnum-unified-container-actions 16:28:19 the magnum team seems to be considering a big api refresh. maybe a v2? 16:28:32 interesting 16:28:40 i highlight this because this is an area i'm becoming much more involved in 16:29:12 nice, looks like a cool project 16:29:14 the new carina (containers as a service) product at rackspace will be built on magum 16:29:21 #link https://getcarina.com/ 16:29:38 oh yea, i remember looking at that after the keynotes. looks very cool! 16:29:46 so we want to make sure they have a first rate api 16:30:27 another person on my team is taking the lead on proposing changes and i'm helping guide from an api wg perspective 16:30:29 do they just want more eyes on the proposal? 16:30:42 i expect so 16:30:45 k 16:31:07 some parts of that api make heavy use of actions. 16:31:15 ah, interesting 16:31:27 so i pointed them at #link https://review.openstack.org/234994 16:31:30 that old canard 16:31:32 cool 16:31:32 ;) 16:31:44 i like that spec, but it seemed to run aground slightly 16:31:53 sort of my fault 16:32:10 hopefully some of the work in magnum can feedback into that guideline 16:32:14 also, i think we probably need to carry the baton from miguelgrinberg as i think he is working on other things now 16:32:26 cdent: anything you can do to move it forward? 16:32:27 That's a shame 16:32:57 I can re-evalulate my position and add a dash of pragmatism and it will probably be all fine. 16:33:00 i can take over and attempt to address the issue in the guideline if folks want? 16:33:08 sgtm 16:33:20 I was originally trying to push for some measure of aspiration 16:33:21 as long as that's cool with miguelgrinberg 16:33:33 i *think* so, but i'll ping him 16:33:41 etoews: he emailed the heat team to that effect 16:33:42 #action elmiko to ping miguelgrinberg about taking over https://review.openstack.org/#/c/234994/ 16:33:48 ++ 16:33:57 (as in, go ahead and take over my WIP, my focus is changing a bit) 16:34:05 #action cdent to re-review https://review.openstack.org/#/c/234994/ with an eye to reaching consensus 16:34:06 fwiw 16:34:15 ryansb: ah, which one was yours? 16:34:34 no, I mean miguel said that 16:35:13 oh, great. thanks 16:36:07 #topic guidelines to propose for freeze 16:36:15 #link https://review.openstack.org/#/c/190743 16:36:46 yes 16:37:04 i added this, seemed like it was ready again 16:37:38 elmiko: go ahead and freeze it 16:37:48 k, i'll make the preparations ;) 16:37:57 #action elmiko to freeze https://review.openstack.org/#/c/190743 16:38:22 prepare it for freezing in carbonite 16:38:35 * elmiko calls ahead to Lando 16:38:57 best leave him in there, things get dangerous after he's let out 16:39:15 lol 16:39:22 :) 16:39:55 this needs more eyeballs https://review.openstack.org/#/c/243041/ 16:40:21 yes, +1 16:40:23 #action etoews to add more eyeballs to https://review.openstack.org/#/c/243041/ 16:40:38 we also merged two very old guidelines =) 16:40:48 that reminds me: I think we probably need to send a reminder to the mailing list about the group's existence, because of the usual post xmas amnesia 16:41:00 ooh, good idea 16:41:07 "happy new year from the api-wg" ? 16:41:09 ;) 16:41:20 so that people who would normally be here remember to come and to review (before freeze time) 16:42:04 cdent: care to send that reminder? 16:42:21 Sure, can do 16:43:09 #action cdent send an api-wg exists reminder email 16:43:14 ++ 16:43:22 #action etoews to add more eyeballs to https://review.openstack.org/#/c/254895/ 16:43:51 +1 * 2 ;) 16:44:23 i'll hold off on https://review.openstack.org/#/c/234994/ until it gets at least one more patch set (likely from elmiko) 16:44:44 cool, i'll get that in before the next meeting 16:46:04 https://review.openstack.org/#/c/187896/ and https://review.openstack.org/#/c/243414/ and https://review.openstack.org/#/c/243429/ are in need of some love 16:46:25 alex_xu: do you have sometime to review/update those guidelines? ^ 16:48:10 this seems like a reasonable thing to do but i'm not really familiar with it https://review.openstack.org/#/c/267329/ 16:48:45 yes, it's fine. that's one of the recent "let's fix something in all the repo mass bug fixes" 16:49:06 I think someone must have run some kind of audit against the code 16:49:17 _all_ the code 16:49:53 yea, this change has been making the rounds 16:50:12 yeah, it's handy that it's an autopatch though 16:50:33 just so deprecated junk isn't kicking around forever 16:50:42 yup 16:50:47 this one actually works. there have been some others that are wrong. 16:50:49 can someone more familiar with the change go ahead and merge it? 16:51:04 sure 16:51:07 i just bumped https://review.openstack.org/#/c/161946/ 16:51:15 * cdent can only +1 16:51:27 k, i'll +A 16:52:11 sigmavirus24 is at the ossp midcycle currently, but maybe he will take a look later 16:52:21 durwasa:What's up? 16:52:23 sigmavirus24: your thoughts, https://review.openstack.org/#/c/161946/ 16:52:30 bumped https://review.openstack.org/#/c/183599/ 16:52:38 Oh I can probably rebase that 16:52:53 cdent: you can only +1? wha??? 16:52:54 sigmavirus24: sweet =) 16:53:08 weird... 16:53:10 it's just you and elmiko and jaypipes at this point I think? 16:53:22 you were supposed to be added too 16:53:26 yeah... 16:53:30 hawt 16:53:32 ;) 16:53:45 in fact, I believe it's best to remove me and replace with cdent. 16:53:53 * elmiko gasps 16:53:55 ;) 16:54:06 does this mean I need to shave my head? 16:54:11 haha 16:54:12 elmiko: it's already tough to find time to perform my Nova duties :( 16:54:20 cdent: yes 16:54:20 cdent: yes, of course it does. 16:54:29 jaypipes: i hear ya, and no worries on this end =) 16:54:34 jaypipes: thank you for service good sir. 16:54:38 /o\ 16:54:38 +1 16:54:54 etoews: cheers 16:55:25 i'll go ahead and make those changes right now if there are no objections. 16:55:36 Thanks, I'll try not to break everything. 16:56:09 etoews: none here 16:56:18 * elmiko watches cdent closely... 16:56:32 * cdent starts shaving 16:56:37 lol 16:56:46 well played sir /me tips fedora 16:57:27 anything else in the last few min? 16:57:37 nothing from me 16:57:49 nor me 16:58:06 nope 16:58:17 alright then. let's end it a little early. thanks all! 16:58:24 #endmeeting