14:03:20 #startmeeting publiccloud_wg 14:03:21 Meeting started Wed Jan 18 14:03:20 2017 UTC and is due to finish in 60 minutes. The chair is mattjarvis. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:03:22 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:03:25 The meeting name has been set to 'publiccloud_wg' 14:03:38 so I have to apologise, I have not had a chance to create an agenda for todays meeting 14:04:01 so it's a bit free form 14:04:27 :) 14:04:29 also, it looks like for the next few weeks I'm going to be very busy, so it would be great if one of the new co-chairs could run this meeting for the next couple of times ? 14:04:39 on the subject of apologies, i've not yet completed my action from the last meeting to update the wiki and write up definition / constituency 14:04:46 No problem! 14:04:49 I have a new job, and it's taking up slightly more of my time than I thought it would :) 14:05:19 no problem 14:05:27 we could rotate 14:05:28 i'll get a draft sorted over the weekend, it's been a hectic couple of weeks since the new year 14:05:41 I can take lead next meeting if that is ok 14:06:01 thank you tobberydberg 14:06:12 so I have just created a brief agenda on the etherpad 14:06:14 thx tobberydberg 14:06:26 could everyone add their names to the attendee list pls 14:06:27 Np 14:06:46 Someone remind me of the Etherpad URL please :-) 14:06:56 https://etherpad.openstack.org/p/publiccloud-wg 14:07:01 ta mattjarvis 14:07:12 no problemo seanhandley 14:07:49 Is this meeting every two weeks? 14:08:00 it is at the minute 14:08:16 ok, I'll adjust my calendar 14:08:19 #topic review last meeting action items 14:08:38 for some reason I couldn't find the meeting logs on eavesdrop 14:08:48 but I think we had two actions IIRC 14:08:52 http://eavesdrop.openstack.org/meetings/public_cloud_wg/2017/public_cloud_wg.2017-01-04-14.03.log.html 14:09:03 aha 14:09:15 that link doesn't work from the eavesdrop meeting definition though 14:09:23 I think maybe I did startmeeting wrong 14:09:41 its defined in eavesdrop as publiccloud_wg 14:10:15 so first action was on me, to close the Doodle poll and announce the results 14:10:22 which hopefully everyone saw 14:10:31 Yes 14:10:41 given the number of votes, both tobberydberg_ and zhipengh are now co-chairs for this group 14:10:53 welcome ! 14:11:00 and thank you for volunteering 14:11:05 Thank you 😊 14:11:10 thx matt :) 14:11:29 second action was on yankcrime - to create a consituency/definitions section on the wiki based on the content in the etherpad 14:11:36 so that one can roll over 14:11:43 #action yank crime to create a consituency/definitions section on the wiki based on the content in the etherpad 14:11:46 ta 14:12:15 final action was on zhipengh to distill Purpose sections down into a section on the wiki 14:12:43 I think I move part of that to the wiki 14:18:36 Only 5 people today? 14:21:11 sorry guys, had to deal with a phone call 14:21:53 tobberydberg_: 6 :) 14:22:15 Hehe....good 😊 14:23:32 #topic Discuss goals 14:23:41 so we started this discussion last time 14:23:50 and had some suggestions on the ether pad already 14:24:32 the first one was to generate some case studies which could be put into a white paper 14:24:52 shall we discuss that a bit further ? 14:25:26 ideally I think we would come to an agreement of what the goals of this team are between now and the Boston summit 14:25:45 should we first draft a skeleton for the white paper, and then people could fill in the blank 14:26:15 zhipengh, are you thinking a set of questions which we use for all the case studies ? 14:27:43 yes we could have a set of questions for the case studies section, and I was thinking of a skeleton for the white paper as a whole, for example we might have Overview, Case Study, Findings 14:28:12 and we could have more specific layouts for each section 14:28:31 I think we could target Boston for a read out or something like that 14:28:34 for the whitepaper 14:31:10 Sounds good regading white papers i think 14:31:34 So we get the same format of them all 14:33:04 I guess we could come to an agreement of the goals until Boston 14:33:50 btw should we have short meetings at PTG ? 14:34:31 so would someone be willing to take an action to come up with a template for discussion ? 14:34:52 I could come up with a template 14:34:58 do we have a repo ? 14:35:08 #action zhipengh to come up with a template for case studies 14:37:56 so it sounds like we are agreeing that a set of case studies would be one of our milestones ? 14:38:07 how many cloud providers are represented in this group today ? 14:38:21 Not what I know of...regarding repo 14:38:22 i.e. how many case studies would be have if each brought one ? 14:38:36 we do not have a repo at the minute 14:39:04 i think 2 -3 case studies should be enough 14:39:20 DataCentred's happy to put forward a case study 14:39:25 if we have more than that then we crunch them into 2 or 3 categories ? 14:39:28 I'm representing one 14:39:41 ok 14:39:41 Huawei also will provide one :) 14:39:50 so we have at least 3 14:39:59 sounds good 14:40:01 I can come up with one without peoplems 14:40:04 phew job half done :P 14:40:17 Hehe 14:40:29 so do we think that is enough to aim for before Boston ? 14:40:46 we also had a suggestion to produce a document showing the common problem spaces for public cloud operators 14:40:55 ie. what's missing upstream 14:41:08 that could be part of the white paper 14:41:17 I've got plenty of thoughts there 14:41:25 there was some interesting discussion on the ops list re people's ideal features for Pike 14:41:39 and many of the things I could think of from a public cloud context were in there 14:41:58 I have some thoughts as well 😊 14:41:59 i.e. everything we probably all implemented in our own management systems outside of OpenStack 14:42:14 so why don't we also take an action to collate those things 14:42:20 just as a list for now 14:42:38 +1 14:42:43 Agree 14:42:49 tobberydberg_, would you take this action ie. to collate from the rest of the group ? 14:43:01 I know seanhandley also has a lot to add there 14:43:07 Absolutly! 14:43:29 #action tobberydberg_ collate list of problem areas of functionality from the group 14:44:16 seanhandley, tobberydberg_ - have a look at the thread entitled What would you like in Pike? on openstack-operators 14:44:28 there are also a bunch of stuff in there I know we implemented at DataCentred 14:44:30 I just call seanhandley and I'm all set 😉 14:45:05 ok, so shall we vote that those two areas are what we will focus on until Boston ? 14:45:05 Yups, Will do that! 14:45:17 Sure 14:45:26 tobberydberg_: Sounds good 14:45:41 Seems well achievable in the time frame 14:45:49 #startvote agree milestones for Boston - produce 3 case studies of public cloud usage, identify common missing features for public cloud ? Yes, No 14:45:50 Begin voting on: agree milestones for Boston - produce 3 case studies of public cloud usage, identify common missing features for public cloud ? Valid vote options are Yes, No. 14:45:51 Vote using '#vote OPTION'. Only your last vote counts. 14:45:56 #vote Yes 14:46:02 #vote Yes 14:46:10 #vote yes 14:46:19 #vote Yes 14:46:43 any more votes ? 14:46:56 #endvote 14:46:57 Voted on "agree milestones for Boston - produce 3 case studies of public cloud usage, identify common missing features for public cloud ?" Results are 14:46:58 Yes (4): tobberydberg_, zhipengh, mattjarvis, seanhandley 14:47:11 I will take an action to update the wiki 14:47:21 #action mattjarvis to update wiki with agreed milestones for Boston 14:47:27 Good! Thanks! 14:47:46 I think we are all set then ! 14:48:04 I am going to have to drop off this meeting a little early as I have another call 14:48:12 is there anything else anyone wants to bring up at this stage ? 14:48:32 PTG meetngs ? 14:48:57 i might missed the response on that question... 14:49:21 zhipengh, I can't add anything to that, as not attending PTG 14:49:35 okey :) 14:49:37 anyone else have thoughts on that ? 14:49:42 no problem,just checking 14:50:12 :) 14:50:22 Good stuff 14:50:33 great, then I will close the meeting 14:50:40 Catch up in 2 weeks 14:50:42 #endmeeting