14:01:09 #startmeeting publiccloud-wg 14:01:09 Meeting started Wed Jul 5 14:01:09 2017 UTC and is due to finish in 60 minutes. The chair is seanhandley. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:12 The meeting name has been set to 'publiccloud_wg' 14:01:23 Anyone else here for the public cloud WG meeting? 14:01:31 #link https://etherpad.openstack.org/p/publiccloud-wg 14:01:37 Please add your name to the etherpad :) 14:01:42 o/ 14:01:47 hi Labedz o/ 14:01:54 hi 14:02:38 We'll wait a couple more minutes for latecomers then get started 14:02:53 o/ 14:03:00 hi zhipeng :) 14:03:14 Hi Sean 14:05:22 Ok let's get started 14:05:35 First item, last weeks's APs 14:05:43 #topic Last meeting's action points 14:06:18 So it was assigned to me to discuss the idea of the OpenStack Public Cloud Passport with Flanders from the OpenStack Foundation 14:06:54 Basically, he wants this working group to take ownership of the design for how such a scheme would work technically 14:07:18 so it's up to us how it should work 14:07:31 if we need infrastructure to support it then the Foundation will provide it 14:07:41 what is it? 14:08:21 The Public Cloud Passport will be a scheme where users are effectively given some free credit that is valid on all participating OpenStack public clouds 14:08:52 i think the foundation mkt team could help design the form of the passport 14:09:05 there'll be some Foundation-specific branding and likely some centralised token validation authority that each cloud dials into when a user supplies their unique code 14:09:23 basically it's down to us to figure out a working technical solution 14:09:38 and they'll help us build/maintain it 14:10:18 i think promo schemes should left the public cloud providers 14:10:27 should avoid a grand centralised design 14:10:38 that will cost much more time 14:10:50 o/ 14:10:56 hey tobberydberg 14:10:59 Taking passive role today.... 14:11:10 i would assume that the foundation's reach is > any individual public cloud providers, at least the ones interested in participating 14:11:17 Will read up later =) 14:11:26 zhipeng: There'll have to be some single source of truth for valid tokens though 14:11:45 and it makes sense for it to belong to the Foundation because they'll be the ones handing out the Passports 14:11:56 do you consider any 'implementation' meeting about passport? 14:12:14 Yes, I think it's worth considered discussion around a whiteboard Labedz 14:12:15 like how to take care about legal stuff? 14:12:26 k 14:12:35 the passport is a mkt campaign that will help promote the notion of OpenStack public cloud 14:13:01 We're planning to run a couple of Public Cloud Working Group meetups before the Sydney Summit 14:13:09 One in London at OpenStack Days London in September 14:13:18 and another in Copenhagen for OpenStack Days Nordic in October 14:13:32 Labedz: Can you make it to either of those? 14:14:04 hard to say now :} 14:14:04 seanhandley shall we start meetup groups for that ? 14:14:15 for sure will try 14:14:21 (I know Howard, myself, Nick and Tobias will be there) 14:14:29 Would be great to have OVH at the table Labedz :) 14:14:40 zhipeng: That's a great idea 14:14:41 we will be for sure in FR ;) 14:14:43 we also need to write some material for the meetup series, so that Sydney Summit the foundation keynote could help promote 14:14:59 #action Howard to create Meetup groups for the Public Cloud WG Meetups at OpenStack Days UK and Nordic 14:15:15 Labedz: is this something you think OVH would participate in? 14:15:30 yankcrime: I think so 14:15:35 cool :) 14:15:56 zhipeng: Do you want to take on the task of writing that material? 14:16:17 seanhandley I don't think I could handle that only by myself :P 14:16:33 but we could do it around two weeks before Sydney 14:16:42 to summarize the meetups so far 14:16:46 Ok - would you write down some rough thoughts you have about it in a google doc and I'll collaborate with you on it? 14:16:53 sure 14:17:33 #action Howard and Sean to begin writing up some public cloud WG material ahead of the Sydney Summit 14:18:07 Cool. Any more thoughts before we move onto our next topic? 14:18:52 Ok! Onto the goals for the Sydney Summit 14:19:01 #topic Decide on goals for the Sydney Summit 14:19:12 #link https://etherpad.openstack.org/p/SYDNEY_GOALS_publiccloud-wg 14:19:23 See the Etherpad above for what we came up with previously 14:19:48 Flanders' advice is that we pick a single achievable goal and give it the majority of our focus 14:20:27 The EU meetups are piggybacking off existing conferences so they're effectively organised already 14:20:39 yep :) 14:21:26 Rather than do a vote, I want each of us to say which item in that goals list should be focussed on 14:21:40 (because I'm too lazy to curate them all into voting form) 14:22:29 anyone want to start? 14:22:33 i think the feature list and eu meetup series 14:22:35 or should I pick on someone :P 14:22:41 are two goals that we could achieve 14:23:03 passport is a little bit depending on each company 14:23:11 collaborating on missing features is a no-brainer 14:23:48 thoughts tobberydberg Labedz ? 14:26:09 Ok, none :D 14:26:15 Agree, but think that we should have passport as a goal as well 14:26:28 I agree tobberydberg 14:26:31 if fail, we have a head start for next summit 14:26:39 "Work on missing features" is vague 14:26:54 and it takes a cycle or two to get work into an OpenStack project 14:27:10 I'd hope we keep working on the missing features as a background task 14:27:17 and I'd like to see them drawn up as specs 14:27:30 but it's unlikely we can deliver any changes before the Sydney summit 14:27:44 yes, but at the mean time, the missing feature itself should be a work product 14:27:59 taht our working group could share with the community each cycle 14:28:04 that~~ 14:28:30 i think it needs a step back from that, it needs a process agreeing that participating public cloud operators can discuss and vote for missing features, and then volunteer to write blueprints and fund development 14:28:39 so the focus should be getting that process agreed and formalised 14:28:55 then it becomes a background task 14:29:11 afaik there's nothing analogous within the openstack community to that already 14:29:15 i could be wrong though 14:29:19 That's sort of already happening Nick: https://docs.google.com/spreadsheets/d/1Mf8OAyTzZxCKzYHMgBl-QK_2-XSycSkOjqCyMTIedkA/edit#gid=0 14:29:30 that's just a spreadsheet seanhandley 14:29:30 the list should be reviewed each cycle 14:29:58 agree with yankcrime that we need a process to consensus on the missing features 14:29:59 Yes, but people are referencing specs from it, marking their interest, and stating if it's currently being worked on 14:30:11 what's the process for adding stuff to it? do i just edit it? when does it get reviewed? 14:30:22 Do we know if any of us (from this WG) are working on any specific subject from our feature list by himself? 14:30:28 but i think it is doable for us to deliver the first version of the feature document before Sydney 14:30:41 I agree it's not ideal and it needs moving into the correct parts of the OpenStack process 14:31:13 yankcrime anyone should be able to add it, but we do need a process to pick the important features 14:31:20 that most of us agreed upon 14:31:21 it at least needs a wiki page linking off the public cloud wg calling attention to it 14:31:43 wiki page sounds like a great idea :) 14:31:45 How do other WGs accomplish their tasks? 14:32:00 they find volunteers mostly 14:32:08 Yes but how in terms of backlog management 14:32:20 their ideas have to exist somewhere 14:32:28 specs/blueprints? wikis? 14:32:46 and I agree a spreadsheet isn't great long term 14:32:51 it lacks visibility for one 14:33:20 wiki would be a good choice 14:33:43 the scientific wg have 'activity areas' 14:33:49 "Every OpenStack development cycle, four activity areas are selected to focus on, and working group members gather data on problems and solutions in areas that affect them." 14:33:58 there's wiki pages off the scientific wg for each of those 14:34:03 ok 14:34:08 so wiki is the answer then :) 14:34:35 So is it a reasonable summit goal to have moved our features list onto the wiki and have it prioritised somehow? 14:35:22 i think so 14:35:45 Ok 14:35:50 Perhaps a poll needs sending out 14:36:01 We list all the features and have public cloud reps number them in order 14:36:07 1 being highest priority etc 14:36:09 yup, and also wrapped up in a bit of documentation somewhere that says stuff like here's where you can suggest new ideas and vote for existing ones, here's when you can discuss them, here's what happens when there's sufficent votes, and options for collaboration 14:36:32 Sounds good yankcrime 14:36:39 sounds very good :) 14:36:44 Any volunteers to make a start on that process? 14:37:38 tumbleweed.gif 14:37:40 ;) 14:37:50 i'll do it 14:37:57 nice one Nick 14:38:35 #action Nick to update our wg wiki with information about how to get involved, and also moving features onto the wiki for better community visibility 14:39:15 So that's achievable by the Sydney Summit in November 14:39:31 I also think the Public Cloud Passport stuff is achievable by the Summit 14:39:41 and I think it's worth pouring some time and effort in 14:39:57 once there's a framework for it, public clouds can integrate against it at their leisure 14:40:03 and ultimately it's a very simple service 14:40:19 the authority creates unique tokens and then they're given to users 14:40:36 do we have a blueprint already? 14:40:44 when a user supplies that token to a public cloud they check it against the OpenStack authority and it gets validated 14:40:54 and then it gets marked as "used" 14:41:06 and they honour the commitment to the amount of credit associated 14:41:09 no Labedz 14:41:31 But I'm sure I could build a POC fairly quickly and then write it up as a blueprint 14:41:36 seanhandley sso like ? 14:41:38 great 14:41:42 yeah zhipeng 14:42:05 I'll discuss it with Flanders more before the next meeting and come up with a rough working model to share with the group 14:42:17 plz also cc me and tobias 14:42:31 #action Sean to discuss Public Cloud Passport with Flanders more before the next meeting and come up with a rough working model to share with the group 14:42:35 Will do zhipeng 14:42:53 I think it'd be neat to have this done by Sydney - would make for a great point in the keynotes 14:43:17 yes it would be a plus for us :) 14:43:42 Cool. I'll update the etherpad 14:44:08 so does it mean we could officially propose our wg to the UC ? 14:44:20 to have us formally recognized ? 14:44:32 with our goals pretty much agreed today 14:44:56 I'm not sure zhipeng 14:45:06 Hopefully - who do we talk to? 14:45:46 tobberydberg: Maybe that's a good AP for you this next two weeks? 14:46:18 Guess he's busy. He won't mind :D 14:46:40 #action Tobias to get the wg officially proposed to the UC using the goals we've agreed for the Sydney Summit 14:46:58 Ok, next topic... 14:47:32 #topic Submit OpenStack Summit Forum session(s) before July 14th 14:47:54 Does anyone have any thoughts on Forum Sessions we should be running in Sydney? 14:48:24 I guess this is tricky because it needs us to have conference attendance confirmed... 14:48:46 yes ... 14:49:05 missing feature discussion will continue to be a hit I guess :) 14:49:13 Definitely zhipeng 14:49:15 not sure about more possible session topics 14:49:27 that's good enough at this stage tbh 14:49:43 Are you definitely attending? 14:50:11 i'm not sure as well ... 14:50:40 I know Tobias hasn't had his attendance confirmed yet - and nobody from DataCentred either 14:50:42 Labedz ? 14:50:53 probably somebody from OVH will be ther 14:50:55 *there 14:51:11 Right 14:51:16 In that case 14:51:32 zhipeng: Would you submit a proposal via https://www.openstack.org/summit/sydney-2017/call-for-presentations/ ? 14:51:43 and if necessary we'll change who's chairing it 14:52:14 Or I can do it also 14:52:36 you mean Forum Session for Public Cloud WG? 14:52:37 The main thing is to be on the timetable - chairing the fishbowl shouldn't be too demanding 14:52:41 Yeah Labedz 14:52:43 ok 14:52:48 we did a couple at the Boston Summit 14:53:15 seanhandley is there a limit on Forum topic as well ? 14:53:26 I'm not actually sure... 14:53:28 there is a three topic per person limitation on the general session 14:53:37 But the deadline will have elapsed before our next WG meeting 14:53:54 ahh have you already got proposals submitted? 14:54:56 no, not yet 14:55:16 Thing is, I know for certain I'm not going to be there 14:55:36 I'm happy to submit the proposal but it won't be me chairing it 14:55:54 We're almost out of time 14:55:58 seanhandley I think that could be managed 14:56:45 I tell you what zhipeng - let's figure it out after this meeting over in the #openstack-publiccloud channel? 14:56:57 the main thing is someone makes sure a proposal is put forward 14:56:58 cool 14:57:03 yes 14:57:03 so I'll make sure that happens, somehow 14:57:21 #action Sean to make sure we get a Forum session proposal in for a missing features fishbowl at Sydney 14:57:41 and we're done with 3 minutes to spare :D 14:57:48 #topic Any other business? 14:58:50 Labedz: I see you added "Do we have track of current OpenStack infras issues in-house 'work in progress' ?" to the Etherpad 14:59:06 yeap - as far as I see we are talking about missing features 14:59:19 but for sure any of us are working on something daily 14:59:35 maybe we are fixing the same issues :) 14:59:43 Yes - that's true 14:59:51 Is it good idea to have some kind of track of that? 14:59:58 Definitely. 15:00:09 zhipeng: Does the spreadsheet have a column for that? 15:00:22 (and when it gets put on the wiki we'll have some info about it) 15:00:53 i think so 15:01:02 Is it the "Status" column? 15:01:19 yes 15:01:27 Perhaps a "Who's working on this?" column too - not a perfect solution, but it'd help 15:01:39 hi 15:01:58 seanhandley: good begining, we could improve later if needed 15:02:05 ok :) 15:02:26 Time to finish up then guys - thanks for coming - lots of stuff to talk about next time! 15:02:30 #endmeeting