15:00:20 #startmeeting FEMDC 15:00:21 Meeting started Wed Sep 27 15:00:20 2017 UTC and is due to finish in 60 minutes. The chair is parus. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:22 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:25 The meeting name has been set to 'femdc' 15:00:46 Good morning/Afternoon to all! 15:01:00 o/ 15:01:10 o/ 15:01:14 Hi 15:01:20 hi 15:01:54 Good morning 15:01:57 I tried to send the link to the etherpad through mailing list but I think it bounced. 15:02:05 so here is the link 15:02:09 #link https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 15:02:52 it seems we may a have quorum. So lets' get started. 15:03:34 Ad_rien_ excused himself for today. So I will try to chair. Please be patient with me. 15:03:54 thank you 15:04:20 First topic: 15:04:28 #topic Announcements 15:05:22 about Sydney: our timeslot for the f2f is fixed. you will find the link in the etherpad. 15:05:39 Are any additional people confirmed to attend. 15:05:55 I know that dpertin and myself are. 15:06:21 glad to share the session with you parus 15:06:24 I can't make Sydney 15:06:26 :( 15:06:34 I don't think I will be going, some outside chance I'd send myself but my organization will not 15:07:45 so it will be a smaller meeting I guess, if there are any topics that you feel should be discussed, please let us know. 15:08:14 next topic is cross wg chair. 15:08:35 #topic CrossWGChairSessions 15:09:10 This topic was added by ad_rien_. I am affraid I do not now much about it. Anyone can comment? 15:09:52 I missed the announcement and the actual attempted session for Cross WG chairs which was Sept 14 15:10:27 ok 15:10:32 I think ad_rien was the only one to join at least at the start 15:10:48 Then we will have him report on the next meeting. 15:11:11 I see he has put some links to an event announcement that is happening today. 15:11:15 In this last Monday UC meeting tHere was an agreement made by User Committee and a few others including me to try again 15:11:41 I'll include the relevant links and next proposed date in Etherpad as I find them 15:11:55 Thank you jamemcc_ 15:12:16 Next 15:12:23 #topic SIG 15:13:09 following the change of status between team and workgroup. 15:13:32 I understand that a new change is being discussed that might give us more flebility and autonomy. 15:14:03 The concept of a Special Interest Group is being discussed and this team's name has been mentionned as a candidate. 15:14:48 More on this will follow as it unfolds. There was some exchange in the last couple of weeks, and it seems there may be only benefits to the change. 15:15:08 I agree that we shoudl volunteer and take the minor actions required to be listed as a SIG, it should help us to be a larger group and attract engineers 15:15:51 I think we/you are already a good model for how one would operate 15:16:35 Any other opinions? 15:17:55 Let's wait for the larger group to be here before we make a decision. Maybe we can have that as a topic for next meeting. 15:19:10 ok 15:20:35 thanks for adding the link to the follow-up on Etherpad... Definitely, if we make the change there will be opportunities to better define what we do. 15:20:45 next topic 15:20:56 The forum in sydney. 15:21:27 We have an opportunity to propose topics to be discussed at the forum in sydney. 15:21:37 These will be cross workgroup discussion. 15:22:12 We would have to put forward those proposals in the next day or so. 15:22:19 See Link on etherpad. 15:22:49 Any one has suggestions? 15:23:20 #link https://wiki.openstack.org/wiki/Forum/Sydney2017 15:25:26 Thanks jamemcc_ 15:25:45 Not sure if anyone else (I know I'm not) is very versed on the next steps from the Open-Dev 15:26:01 That is a good point! 15:26:06 But seems to me some of that should become Forum topics 15:26:45 I may be guilty there. One thing that came out of opendev was the need for a follow-up session on edge. 15:27:08 but I have not seen any announcement on that. Beth was certainly one of the leads. 15:27:22 I will take an action to reach out to her. 15:27:47 #action parus to reach out to Beth/Kandan about follow-ups from opendev. 15:27:48 thanks 15:28:33 my recollection is that we were suppose to have separate sessions to prepare for Sydney. 15:29:17 One more announcement. 15:29:55 in the margins of opendev we had meetings with openedge 15:30:32 One key member of that group is Sathia from CMU. 15:30:58 He is organizing a meeting to give us more details about their extension openstack. 15:31:11 this is a project called openstack++ 15:31:29 Meeting is scheduled for october 3rd. 15:31:58 If anyone has an interest, I do not think there would be a problem adding a few more people to the invite. 15:32:28 any comment? 15:33:03 Let's move on. 15:33:08 #topic ONAP 15:33:26 ad_rien_ added this topic to the agenda. 15:33:51 this was a major outcome from opendev from my perspective. 15:34:27 The question is about what functionality falls under openstack 15:34:44 vs what functionality is left to a layer above. 15:34:59 The layer above can be the application itself .... or it could be ONAP. 15:35:34 Did anyone have a different perspective on what the topic is? 15:36:45 From my quick read of the OpenDev Key findings. I agree 15:36:55 Thanks! 15:37:40 Anything we can do to dig further? 15:38:15 FYI - those are #url https://etherpad.openstack.org/p/OpenDevTakeaways 15:38:26 jamecc_ : do you have any insight on what ONAP is doing for Edge? 15:39:07 just level setting - for the Telco and NFV use case - ONAP is the Design and Orchestrate and Manage oversight layer 15:39:54 But I think it being Junior in that task had not exactly agreed to take on the Fog Edge for all applciations/use cases 15:40:13 So it may be further out in their roadmap? 15:40:50 I think to some extent - that purpose of the OpenDev from ONAP perspetive would be to see if there are other Open ways to handle 15:41:27 ANd if not to try to gather the interested resources to put more work into ONAP 15:41:55 I suspect this means for us that we should keep monitoring. 15:42:05 Just trying to add tot he conversation - I dont' have any more detailed knowledge of strategy from the ONAP effort 15:42:18 thanks. Let's move on. 15:43:05 #topic AMQP 15:43:13 Hi 15:43:33 Matthieu has done excellent work on the testplan - see epad for link (linke 1284) 15:44:10 Admittedly I've been the slow horse in that effort, but I think the tests and metrics are fairly complete 15:44:37 Next is to update the test tool (ombt2) to capture the defined metrics - I hope to have that done by end of week 15:45:16 great! 15:45:25 And the kolla/ansilbe patch still hasn't landed, but the reviews have given us some feedback since last meeting 15:45:39 and that's about it from AMQP land 15:45:48 questions? 15:45:51 Thanks for the good work! 15:46:04 our pleasure! 15:46:28 What is the next step on Kolla? 15:46:59 To get the patch fixed up and landed. 15:47:08 ansmith: how is the feedback so far? 15:47:22 feedback very strong, just need a few +2's 15:47:37 will keep engaging the kolla team 15:48:03 Thank you guys. Let's move . 15:48:06 ansmith: would it help if others in femdc added to the comments (like +1's)? 15:48:11 ;0 15:48:35 it nevers hurts, Matthieu has done so 15:48:48 Send us the link and I can certainly take an action on my side. 15:49:19 it is in etherpad as well => https://review.openstack.org/#/c/468966/ 15:49:20 patch 468966 - kolla-ansible - Add support for hybrid messaging backends 15:49:52 #action parus to review kolla patch and support. 15:50:10 #topic CockroadDB 15:50:36 sorry for the typo 15:50:51 #topic CockroachDB 15:51:14 anyone can comment on updates? 15:51:45 if not let's move on. 15:52:20 FBK excused themselves today, so we can defer the discussion on use cases to next time. 15:52:41 Let's open up for discussions. 15:52:48 #topic open discussion 15:53:21 ad_rien was suggesting a follow-up meeting at the end of this week. 15:53:24 Any takers? 15:53:58 Yes - I'm glad to attend 15:54:18 Please add your name to the etherpad 15:55:17 any other comments? 15:55:48 Am I the only one who took some actions? 15:56:41 #action kgiusti to release update to ombt21 15:56:47 Sorry about that - thanks again for facilitating 15:56:52 s/ombt21/ombt2/g 15:57:20 thank you all for being so patient with me. 15:57:39 and we get to finish three minutes early :-) 15:57:39 parus: thanks for the good leadership! :) 15:57:49 #endmeeting