14:03:47 #startmeeting Public Cloud WG 14:03:48 Meeting started Wed Jan 4 14:03:47 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:49 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:03:51 The meeting name has been set to 'public_cloud_wg' 14:04:09 firstly could everyone add their names to the ether pad attendees https://etherpad.openstack.org/p/publiccloud-wg 14:05:33 hello 14:05:35 still quite a few down on the first meeting - hope others will join later 14:05:38 hi zhipengh 14:05:50 happy new year :) 14:06:01 same to you :) 14:06:37 o/ 14:06:44 hello nick 14:06:55 * yankcrime really should put this in his diary 14:07:00 #topic Time length for chair voting 14:07:34 just a quick note, it's the participants section at the top of the ether pad, some folks are using the one from the last meeting 14:07:43 so, on to voting for chairs 14:08:04 the Doodle poll has now been open for 15 days 14:08:22 and we have 21 participants 14:08:46 are we happy to close the poll now, or does anyone want to run longer ? 14:09:44 any thoughts either way ? 14:10:01 Fine to close for me 14:10:13 i think we could close the polls now or by the end of this week 14:10:22 ok, let's put it to a vote then ( if I can remember the IRC fu ) 14:10:23 i think we could close the polls now or by the end of this week 14:10:55 Have you got a link for that poll, didn’t see it on the etherpad 14:11:11 can flick through the mailing list 14:11:13 http://doodle.com/poll/s63r5s4ghyucmnqu 14:11:15 i reckon a couple of weeks would usually have been sufficient, but given it's been holiday season leaving it to run until the end of the week seems reasonable to me 14:11:32 http://beta.doodle.com/poll/s63r5s4ghyucmnqu#table 14:11:39 thanks 14:11:41 yankcrime, that seems reasonable 14:12:02 so lets vote for the end of the week 14:12:02 agree yankcrime 14:12:13 #vote 14:12:43 #startvote close the chair poll on Friday 4th Jan ? Yes, No 14:12:44 Begin voting on: close the chair poll on Friday 4th Jan ? Valid vote options are Yes, No. 14:12:45 Vote using '#vote OPTION'. Only your last vote counts. 14:12:50 #vote Yes 14:13:10 #vote yes 14:13:14 #vote Yes 14:13:19 #vote yes 14:13:39 ...even though Friday is the 6th ;-) 14:13:58 sorry my bad :( 14:14:12 correction for the logs - Friday is the 6th Jan 14:14:16 #vote yes 14:14:17 Hehe, np 14:14:29 we don't need a recount :P 14:14:33 #endvote 14:14:34 Voted on "close the chair poll on Friday 4th Jan ?" Results are 14:14:36 Yes (5): zhipengh, yankcrime, mattjarvis, seanhandley, tobberydberg 14:14:49 ok, carried :) 14:14:57 I will close on Friday 14:15:22 #topic Work output to create definitions and consituency on wiki page 14:15:38 it would be good to get this put to bed now, we have some content added to the etherpad 14:17:28 is everyone happy with the definitions section ? ( under Who is our Constituency ) 14:17:59 and I think we all agreed that we wouldn't necessarily be bound by the Marketplace 14:18:50 one issue with not having the MP as part of the definition is that we now include operators who don't have the Powered by OpenStack certification 14:18:56 i like the NIST definition tbh 14:19:01 +1 14:19:33 not sure i agree with the 'full api access' statement though 14:19:42 I agree that we should not be bound with MP 14:19:56 yankcrime, can you explain a bit more ? 14:20:00 could be public operators that can't provide 'full api access' for one reason or another, but those reasons could be of wider value 14:20:31 full api access meaning full OpenStack API access ? 14:21:30 full api might not be the right phrase, publicly accessible api is what is meant? 14:21:42 I think the intention of that statement was about OpenStack API's as opposed to proprietary wrappers 14:21:56 in which case you'd be excluding rackspace surely 14:21:57 serverascode, yes I think so 14:22:01 some of the apis will not be publicly accessable in nature (for public clouds) 14:22:02 serverascode: that'd be ok 14:22:22 Public accessible native OpenStack APIs 14:22:48 tobberydberg, +1 14:23:00 would you mind updating the ether pad with that suggestion ? 14:23:01 +1 14:23:06 Sure! 14:23:10 Happy wih the definition, aggree with YC. 14:23:18 just don't restrict it to only native APIs 14:23:24 i think "publicly accessible apis" is sufficient 14:24:36 ok, I think there is enough there to create a definition and constituency section on the wiki 14:24:50 would anyone like to take an action to take that and create something on our wiki page ? 14:25:06 https://wiki.openstack.org/wiki/PublicCloudWorkingGroup 14:25:36 lol, ok I will take that as an action 14:25:37 i'm happy to write something up 14:25:41 sold 14:25:43 lol 14:26:08 #action yank crime to create a consituency/definitions section on the wiki based on the content in the etherpad 14:26:35 we need to agree the content in the etherpad, right ? 14:27:09 sorry, yes let's make sure we are in agreement on that 14:27:23 we are just talking about the Who is our Consituency section 14:28:13 #startvote are we happy with the content in the constituency section being used to seed the wiki ? Yes, No 14:28:15 Begin voting on: are we happy with the content in the constituency section being used to seed the wiki ? Valid vote options are Yes, No. 14:28:16 Vote using '#vote OPTION'. Only your last vote counts. 14:28:21 #vote yes 14:28:26 #vote Yes 14:28:52 #vote Yes 14:29:01 #vote yes 14:29:01 #vote yes 14:29:10 #vote Yes 14:29:19 #vote yes 14:29:35 any more ? 14:29:48 #endvote 14:29:49 Voted on "are we happy with the content in the constituency section being used to seed the wiki ?" Results are 14:29:50 Yes (6): rmart04, yankcrime, mattjarvis, tobberydberg, zhipengh, serverascode 14:30:03 #vote yes 14:30:11 #topic Discuss purpose and goals 14:30:19 Damn. Need to be quicker on the draw. 14:30:32 sorry :( 14:30:35 resounding yes anyway :) 14:30:53 my bad - I'll be quicker 14:31:08 so I think we have a pretty good definition of purpose in the section titled "Splitted concept of representation" 14:31:21 which Mariano from Enter provided I think 14:31:59 and there is also some concepts under " Purpose of the publiccloud-wg" at the bottom 14:32:23 could I ask that we all review both of those sections, add any new thoughts, and then we'll vote on adding that to the wiki also ? 14:32:52 Agree that "Splitted concept of representation" looks good! 14:32:54 I'll give everyone a couple of minutes to look at those sections 14:33:14 I think they probably need merging together and a bit of editing, but I agree 14:34:03 true that 14:34:51 lgtm 14:36:24 ok, so lets vote on moving that section forward 14:36:45 #startvote are we happy with the content we currently have to describe the purpose of the WG ? Yes, No 14:36:46 Begin voting on: are we happy with the content we currently have to describe the purpose of the WG ? Valid vote options are Yes, No. 14:36:47 Vote using '#vote OPTION'. Only your last vote counts. 14:36:50 #vote Yes 14:36:53 #yes 14:36:57 #vote yes 14:37:02 #vote yes 14:37:08 #vote yes 14:37:22 #vote Yes 14:37:39 #vote yes 14:38:18 any more ? 14:38:34 #endvote 14:38:35 Voted on "are we happy with the content we currently have to describe the purpose of the WG ?" Results are 14:38:36 Yes (6): seanhandley, yankcrime, mattjarvis, tobberydberg, zhipengh, serverascode 14:38:56 would anyone else like to take an action to distill those sections down into a Purpose section on the wiki ? 14:39:06 I am happy to do so 14:39:15 I could help 14:39:31 please feel free zhipengh 14:39:51 how about you take a first pass, and we can collaborate if needed afterwards ? 14:40:07 no problem 14:40:09 #action zhipengh to distill Purpose sections down into a section on the wiki 14:40:15 tx :) 14:40:38 so the last thing I wanted us to talk about today was about goals 14:41:03 there are obviously the overarching things which we have outlined under purpose 14:41:41 but taking input from others, the most successful working groups have set themselves achievable sets of goals within the release cycle timeframe 14:42:12 here is what David Flanders sent to me this week regarding this : 14:42:16 �First task is really to get two dedicated co-chairs who are going to be committed to bringing the group together via the regular drum-beat of IRC meetings. Second is having a good scoping document 9slides) to announce at the forum(summit) along with 1-3 small activities. That is about as much as you can hope for, a good start with some clear trajectories." 14:42:47 this sounds like a reasonable set of milestones to work towards initially 14:43:10 agree 14:43:22 agree 14:43:22 we obviously have the first underway, the second is tied up with some of the work we've just done on creating wiki content and defining things 14:44:22 does anyone have any further thoughts on the third ? 14:44:59 it's worth reading the "Things which public cloud have achieved this year" section on the etherpad 14:45:13 which does focus a lot on the app dev stuff, but still valid points 14:45:56 personally I'd be looking for SMART goals 14:46:04 and fairly small scope for the first iteration 14:47:33 one thing that did seem achievable and fairly self contained was to produce some case studies 14:47:41 which could then become part of a larger white paper 14:48:22 how should we categorize the cases ? 14:49:16 I was thinking that if we could provide 3-4 case studies for large customers who use public cloud openstack and why they use it - along with any challenges that customer creates for the provider ? 14:49:27 I can definitely think of 2 customers from DataCentred who would be interesting 14:50:03 I could have some from OTC customers I think 14:50:10 if the selection could be cross-industry that would also be interesting I think 14:50:44 so customers from different sectors 14:51:28 we should also decide on a template for the case study document 14:51:42 Like your suggestion Matt 14:51:46 what sections we should include in it for example 14:52:24 zhipengh, I agree 14:52:35 could you add that to the ether pad so we capture it 14:52:49 deffo agree with case studies that speak to openstack's strengths for public cloud in general 14:53:00 coming back to Flanders suggestions - I think what we are talking about here is what he has under section e. 14:53:33 I think we could also contribute to section d. - update, testing and screencasts of how various cloud app interfaces work atop openstack 14:53:52 and to section c. 14:54:04 participation at the summit OpenStack Academy* acting as mentors during the 'Training Games' and self-paced 'Cloud App Labs' lounge 14:55:27 Yes, participating and the OpenStack Academy with resources to execute sessions, labs or hackatons? 14:55:59 tobberydberg, yes exactly 14:56:06 Yes, participating and provide the OpenStack Academy with resources to execute sessions, labs or hackatons? 14:56:16 ...some lost words... 14:56:36 and also that would play into doing some work on section d. so that we ensure things actually work reliably across clouds 14:57:16 so we are coming up to the hour now 14:57:24 does anyone have any final thoughts for this weeks meeting ? 14:58:13 I suggest we add the case study discussion to the agenda for next meeting, as it seems we are all fairly in agreement 14:58:37 yeah, agreed 14:58:39 sounds good mattjarvis 14:58:55 agree 14:58:58 agree 14:59:04 thank you all for your input - I think we've made progress this meeting. By next time we should have some additional wiki content and some other chairs ! 14:59:14 thanks mattjarvis 14:59:20 #endmeeting