16:01:09 #startmeeting defcore 16:01:09 Meeting started Wed Dec 7 16:01:09 2016 UTC and is due to finish in 60 minutes. The chair is markvoelker. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:14 The meeting name has been set to 'defcore' 16:01:29 o/ 16:01:31 #chair eglute hogepodge 16:01:31 Current chairs: eglute hogepodge markvoelker 16:01:37 o/ 16:01:43 o/ 16:01:43 #link Today's agenda https://etherpad.openstack.org/p/DefCoreRoble.5 16:01:45 o/ 16:02:23 hi 16:02:50 hi folks. Let's jump right in... 16:02:57 #topic PTG 16:03:05 hogepodge: any updates on meeting space? 16:03:27 markvoelker: yes, catherineD through refstack has secured two days of meeting space for us 16:04:02 excellent, thanks catherineD 16:04:15 #info meeting at PTG is on 16:04:19 It is officially ok for us to use that space along with the refstack project 16:04:43 do we know which days? 16:05:24 I think the first two days, but catherineD can confirm. 16:05:31 yes, i see it on the website 16:05:34 https://www.openstack.org/ptg/ 16:05:59 We're even on the schedule. :-D 16:06:05 Monday and Tuesday 16:06:21 thank you catherineD! 16:06:22 do we know how the space will work? 16:06:27 #info PTG Monday and Tuesday February 20-21 16:06:34 are we going to have one room for us and refstack, or? 16:06:35 #link https://www.openstack.org/ptg/ 16:06:46 The first two days are focused on cross project needs 16:06:52 yes one room for both days 16:07:11 thanks catherineD 16:07:38 catherineD: ok, so sounds like we'll need to work out some kind of agenda so we're not stepping all over each other. =) 16:08:19 Is there a tentative schedule for refstack yet? 16:08:58 yea, but mostly willl be Interop WG meeting just like the meet term we had before 16:10:02 ok, so I guess eglute and you and I should circle up and hash out a tentative agenda then. Shall we start an etherpad for topics? 16:10:16 yes, lets do that 16:10:35 * shamail cant't make it since kids are off that week 16:10:38 Ok, eglute would you mind setting one up and sending it to the ML's 16:10:45 shamail: bummer =/ 16:10:53 I know :( 16:11:02 #action eglute start etherpad with agenda for PTG and send it out to ML 16:11:07 because most of the cores from the RefStack team won't be at PTG 16:11:53 #action eglute to start PTG agenda etherpad and post to ML 16:12:03 Anythign else on PTG before we move on? 16:12:29 hearing none.... 16:12:36 #topic 2017.01 16:12:46 First up: cinder 16:13:26 I looked at the etherpad last night to start working on cinder but got a little stuck 16:13:57 I think we want to add all V3 as advisory but reference the V2 tests (which are the same ones referenced by the approved capabilities)? 16:14:03 shamail: ? 16:14:20 Is that correct? 16:14:43 The other dilemma is that cinder does have a list API versions call but there is no test for it 16:15:07 That sounds correct to me, since v3 is the equivalent of nova v2.1 in microversion intent 16:15:28 Shamail: Yeah, I think the general idea is to put v3 into advisory as long as the same tests work. 16:15:31 So we're okay with referencing the same ID idempotent ID? 16:15:41 yup 16:15:47 shamail: sounds like we should write a test for it in the next month. My suggestion is to add the capability section as a placeholder until the test is written 16:15:57 Okay, thanks. 16:16:15 For the version list thing: I've written a couple of those tests now, seems like something I can add to my plate. 16:16:25 Likely not in time for this round of scoring, but... 16:16:36 So my actions are create cinder V3 as advisory and add list apis as advisory but no test definition yet? 16:17:11 I'd go ahead and add version-list to the scoring sheet and note that no test currently exists for it. 16:17:22 V3 will also probably not pass scoring since most/all SDKs are still using V2 16:17:28 If me or someone else can create one in time we can consider adding it. 16:17:28 But I'll score it as well 16:17:43 Okay, sounds good 16:17:51 If not, it'll be a note in the scoring sheet for next time so we can re-eval then 16:18:09 I'll knock that one out tonight 16:18:45 Ok, on to Swift then? Anything else on cinder? 16:18:55 That's all for cinder until next week 16:19:21 Thanks for reviewing Swift Mark! I will update it today 16:19:22 Ok, eglute? Swift updates? 16:19:33 Sure. Sorry that took so long. 16:19:51 thank you for reviewing! 16:20:12 i think i need to do another PR for just updated tests 16:20:21 but i wonder if that is better for the next cycle 16:20:34 since that would be a lot of tests to review 16:21:49 ok. I'll just note that we're running really low on time since January is right aroudn the corner, so the sooner the better (esp. for stuff that may take a while). 16:22:38 anything else on swift? 16:23:02 not at the moment 16:23:26 On the time note, for scheduling 16:23:28 #info Next is Board meeting January 28, 12:00pm-2:00pm Pacific Conference Call 16:23:33 ok, moving on to Nova. Shamail has a patch up for this 16:23:44 Ack, wrong date, that's last year 16:23:46 ignore that 16:23:48 #link Nova patch https://review.openstack.org/#/c/385781/6 16:23:50 Yes, I moved the new capabilities to advisory. 16:24:54 Cool, thanks. There was something with the suspend/resume tests I wanted to check into, but I think this getting close 16:25:26 Okay, please let me know if I need to follow-up on anything. 16:25:34 January Board meeting will most likely be on January 31st. 16:25:40 I also rebased the changer 16:25:46 This could use some more eyeballs from other folks, so please take a look 16:26:00 link? 16:26:21 eglute: yes, late january is the proposed date 16:26:26 Rockyg: see above. =) 16:26:28 #info Jan 31, 1 -3pm pacific 16:26:40 https://review.openstack.org/#/c/385781/6 16:26:47 oh. oops. Thanks. 16:27:02 Ok, anything further on nova? 16:27:38 Keystone and Glance patches are landed, so we're good there. 16:28:09 While we're discussing reviews, I'll just note that there are a couple of patches out for aliasing and flagging existing stuff 16:28:25 eglute: I think you Workflow+1'd one of them but it hasn't merged yet? 16:28:36 hm, let me see 16:28:40 eglute: https://review.openstack.org/#/c/405048/ 16:29:10 may need a recheck (and a +2 from you while you're at it =) 16:29:34 The other one is: 16:29:40 #link Alias patch https://review.openstack.org/#/c/405039/ 16:29:57 Which LGTM but needs another review or two 16:30:25 looks good to me, I can move it later after others have a chance to look 16:30:37 Will review today 16:30:58 thanks luzC and shamail! 16:31:00 It's a pretty simple change so should be quick. 16:31:06 Ok, monving on to the name change 16:31:25 Shamail: I see you got the wiki moved over 16:31:30 Yes sir 16:31:55 I think it's time to pull the trigger on deleting the old #openstack-defcore channel. What do folks think? We've been warning about it for weeks... 16:32:01 All the links I checked worked, but if we notice any issues please let me know 16:32:01 (months?) 16:32:02 ++ good job! 16:32:23 i think closing the other channel is fine! 16:32:37 any idea how much traffic it's getting? 16:32:44 We also need to send out official announcement telling people to move 16:32:49 Now that we have the wiki moved, is it okay if we change the eavesdrop listing? 16:32:59 IRC channel? about zero traffic 16:33:03 shamail yes please 16:33:29 We can stay with the same meeting ID for now to keep the same logs or change it to 'interop' and add a pointer to the old DefCore logs in the wiki. Thoughts? 16:34:04 Yeah. just checked the channel. Mostly the veterans who are just there in case 16:34:05 Shamail: I'd be inclined to go ahead and make the change. 16:34:21 (and add pointer in wiki) 16:34:22 Agree. 16:34:29 I'm waiting on infra to approve the new mailing list. I pinged them on it this morning. 16:34:32 markvoelker: +1, we'll have to do it sooner orblater 16:35:06 Can you please assign the action to update eavesdrop so I remember? 16:35:18 #link New Mailing List review https://review.openstack.org/#/c/404921/ 16:35:29 shamail: oh, actually I thnk I wrote the eavesdrop change before remembering you had that AI. =) 16:35:42 I'll go ahead and push it this afternoon if that makes life easier on you. =) 16:35:49 Perfect 16:36:00 #action markvoelker push eavesdrop patch to update meeting name 16:36:01 hogepodge once the mailing list is created, we can send out official announcment 16:36:02 Make sure you update the wiki location in eavesdrop 16:36:12 shamail: yeah, the openstack bot it out of there 16:36:25 shamail: will do 16:36:35 #action markvoelker update meeting info in wiki once patch lands 16:36:38 lets not shut down current ML until official announcement goes out 16:37:18 once the new ML is up I'll send the announcement alerting people to move over, then shut down the list so no new messages can reach it. 16:37:24 just waiting on infra now 16:37:29 sounds like a plan. 16:37:51 The other action related to this on my plate is updting https://review.openstack.org/#/c/327086/ which I'm about 50% done with. 16:37:54 Awesome 16:39:26 We also wanted to get repo names updates, but I sorta felt like it would be best to land that patch first 16:40:05 ++ 16:40:25 agree 16:40:34 ok, anything else we need to talk about on this topic today? 16:41:11 Ok, moving on 16:41:24 #topic documenting how projects can become part of Guidelines 16:41:44 eglute: I just realized I had an AI to send you some notes I'd started drafting on that, which I totally forgot to do 16:41:51 I'll get those over to you after linch 16:41:54 *lunch 16:42:01 markvoelker it is ok! i was swamped last week 16:42:14 thank you markvoelker ! 16:42:26 And with that we're at open discussion... 16:42:29 #topic open floor 16:42:40 I created etherpad for PTG: https://etherpad.openstack.org/p/InteropWGAtlantaPTG 16:42:47 eglute: thanks 16:42:54 please let us know if you are planning to attend 16:43:02 and propose topics for PTG. 16:43:14 Do we see DefCore playing a role in the strategic OpenStack futures discussion? 16:43:17 we will plan our agenda around it 16:43:32 shamail good question 16:43:45 Do things like scenario tests, discoverability, etc. need to be noted in that convo 16:43:59 i think so 16:44:00 shamail: not sure if everyone is even quite aware of that discussion at the past couple of Board meetings...if not, a good primer: https://etherpad.openstack.org/p/ocata-strategic-review-board 16:45:01 Discoverability should be there and strategically we should ask better collaboration on interoperability in general to achieve a "one global Cloud" feel as described in "one platform" 16:45:07 also blog post by Mark McLoughlin: https://crustyblaa.com/december-6-openstack-foundation-board-meeting.html 16:45:35 shamail good points 16:46:28 shamail: I think some of those things will be reflected in some of the responses to the "12 questions" exercise too. 16:46:40 Or at least I know they will for at least one response. =p 16:46:50 I defer to y'all to determine the right time since the conversation is still high-level for now... we would just want to raise interoperability as a concern before it becomes too low-level based on next steps 16:47:00 LOL, make that TWO responses :) 16:47:11 shamail i agree 16:47:34 Note also that DefCore was called out specifically in the etherpad there a couple of times, so folks are thinking about how we fit into that picture 16:47:34 the full discussion on this will be during the next in person board meeting 16:47:49 markvoelker: +1 16:47:51 eglute: remind me, did they decide to try to do that in person at the PTG with the TC? 16:47:55 tentatively, it is scheduled for February 24th in Atlanta 16:47:57 Or was that still just a proposal? 16:47:59 ok 16:48:05 They will be following up to see if it works for them/when 16:48:10 Ah nice 16:48:20 That was fast 16:49:18 The tc just let everyone know the board might wwant to meet with them at PYG 16:50:03 The response was "not during the normal days of ptg 16:50:35 well, normal ptg is monday-thursday i think 16:50:41 and the board meeting on Friday 16:50:41 Though maybe part of Friday. 16:50:55 Rockyg where are you seeing this? 16:51:09 the TC meeting yesterday. 16:51:14 Rockyg thanks! 16:51:25 check the meeting logs. very near the end. 16:51:32 Rockyg will do! 16:52:00 Yeah. We need to tag team here to cover all angles ;-) 16:52:24 :) 16:53:12 ok, anything else today folks? 16:53:55 we can finish early! 16:53:55 hearing nothing, I think we can close up for the day 16:53:57 :D 16:54:01 thank you markvoelker! 16:54:02 Thanks everyone! 16:54:06 #endmeeting