Thursday, 2018-06-21

*** germs has quit IRC04:07
*** aprice has quit IRC06:45
*** aprice has joined #openstack-publiccloud06:48
*** aprice has quit IRC06:54
*** aprice has joined #openstack-publiccloud06:58
*** peereb has joined #openstack-publiccloud07:15
*** zhipeng has joined #openstack-publiccloud13:58
tobberydbergo/14:00
apriceo/14:01
tobberydberg#startmeeting publiccloud_wg14:01
openstackMeeting started Thu Jun 21 14:01:28 2018 UTC and is due to finish in 60 minutes.  The chair is tobberydberg. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: publiccloud_wg)"14:01
openstackThe meeting name has been set to 'publiccloud_wg'14:01
tobberydbergNice to see you here aprice14:01
aprice:)14:01
tobberydbergSome more here for todays meeting?14:02
apricedanny and chris from the foundation are also planning to join so we can talk more about the powered program like we discussed from the previous meeting14:02
tobberydbergcool :)14:03
tobberydbergKets wait a couple of minutes then =)14:03
hogepodgehi14:06
tobberydbergwelcome hogepodge14:07
*** Danny_ has joined #openstack-publiccloud14:08
apricewith hogepodge and Danny_ here, one of the things I wanted to make sure we covered today was the powered program feedback that was raised in the last meeting14:10
apricewhen we were discussing using that as a requirement for passport14:10
tobberydbergYes, absolutely14:11
hogepodgeIt's my understanding that there were concerns about the program, and the ability of clouds to meet the defined standard?14:11
tobberydbergLets kick off the meeting here and see who is joining14:12
tobberydberghttps://etherpad.openstack.org/p/publiccloud-wg14:12
tobberydbergPlease add your name there14:12
mnaseri am here14:12
tobberydbergNice to see you here mnaser14:13
mnaser:)14:13
Danny_hello everyone!14:13
tobberydbergThe plan for today - get some feedback of the "initial draft spec" of the PP v214:13
tobberydbergThat includes your topic aprice, Danny_ and hogepodge14:14
tobberydberg#link spec draft: https://etherpad.openstack.org/p/PCWG-pp-spec-draft14:14
tobberydbergJust to give you all a little overview of the thinking around this14:15
tobberydbergWould like to summarize the PP in a spec - will become to big probably, so will use this as parent and refer to more detailed specs as for example the technical solution for the coupon codes system etc14:16
mnaserme likes #3 in selection criteria.  #2 i feel like is too specific.. some vendors depending on their pricing model, $100 might mean nothing vs others14:16
tobberydbergSo, open for any feedback to the format, way of thinking, content etc etc14:16
mnaseri *think* if we scope it out to be similar to aws free tier which is like "ability to at least run <x> type of vm or equivilant" or something like that.14:17
tobberydbergGood, I like all feedback - need to get the discussions going to come to some conclusion14:17
mnaserand my other last comment is selection criteria for the *password applicants* .. is that up to the provider to decide14:18
tobberydbergso, add +1's and -1's to what ever is in the spec14:18
mnaserogood idea14:18
tobberydberglike that idea o the "free tier" thinking as well14:18
mnaseryah i put up my feedback14:19
mnaserbut i think it's important for us to know that who gets to hand out those unique coupons14:19
tobberydbergagree14:20
tobberydbergPlease all, put your name in the top if possible in this etherpad as well ... easier to reach out and get clarification of feedback if necessary14:21
mnaseri wanted to throw out an idea here before writing it out14:22
mnaserhow do we feel about handing the foundation a whole bunch of credentials that are tied into billing accounts ready with certain funding14:23
mnaserand then the 'sign up' / 'get started' process is instead point and click directly from the openstack website14:23
mnaserand you get handed over credentials right away and it gets marked as 'used'14:23
tobberydbergby credentials you mean the "coupon codes" ?14:24
mnaserno, like actual pre-provisioned accounts14:24
tobberydbergaha14:25
mnaserlike you just get keystone credentials and we get an email from openstack saying "this tenant, this is the user info"14:25
tobberydbergI guess that depends on the usage of them14:25
mnaseri mean that's the big question mark ere14:25
mnaserhere**14:25
mnaserwho hands them out and where.. that's my concern14:25
mnaserespecially that with coupons, there is no 'prescreening' so to tspeak14:25
tobberydbergHaven't thought of it like that earlier14:26
mnaserthere was some talks about using them as 'motivation' to make people come to meet ups.14:26
mnasereverytime you come, you get a coupon14:26
tobberydbergwith the codes, you can still have your screening14:26
mnaseri'm personally not comfortable with that sort of thing14:26
tobberydbergwith pre-created accounts, you can't14:26
mnaseri thought the whole idea behind coupons is instant setup14:26
tobberydbergno, that isn't at all how I've seen it14:27
mnasermaybe an imagined workflow should be put up in that case14:28
mnaser;)14:28
tobberydbergI've seen it as the codes we (citycloud) and OVH has ... like a X digit unique code, that gives you like a $xxx rebate/free usage ... but you still need to pass each members screening process14:28
apriceMaybe this could be how we pull in the user groups?14:29
tobberydbergYes, agree with you when it comes to the "imagined workflow" ... like the PP use cases Flanders came up with for the PP release14:29
mnaserthat's reasonable.  so how is that different than filling out a form14:29
mnaserthat goes to a human which processes it14:30
mnaseraprice: not sure what you mean by pulling in user groups14:31
apriceAs far as people to try the coupon method14:31
tobberydbergBigger marketing value to be able to hand out "$100 worth of OpenStack", then sending people to o.o/passport and then signup for a trial, gives more flexibility when it comes to values etc etc14:32
mnaseraprice: oh yes14:33
mnasertobberydberg: sure, sounds good to me14:34
mnaserso here is a technical concern :)14:35
tobberydbergIt's ok to not like that approach as well =)14:35
mnaserif you get a code, you use it at some_cloud, it gets marked as as used.  some_cloud decides they don't want to give you the credit for $reasons14:35
mnasernow you are stuck with an unusable code14:35
tobberydbergYes, "Passport coupon codes" section in spec is supposed to gather the use case/scenarios, tech requirements for that .... Then we choose technical implementation14:36
mnasernoooow the other way around is: you get the code and some_cloud does not mark it as used until they activate it, well you can do rounds on all providers, hehe :)14:36
mnaseranyways, might be getting ahead of ourselves14:36
mnaserit seems to be okay with me at this state14:36
tobberydberggood point ... but, we still need to trust the members of the program that they behave well14:37
zhipengmnaser that is actually why we had this blockchain experiment :)14:37
zhipengto tackle exactly the issue you just mentioned14:37
mnasertobberydberg: that's a given.14:37
mnaserzhipeng: i am *all* for that, if you find someone to implement it :)14:37
zhipengyep :)14:38
zhipengback to tobias :)14:39
tobberydbergGood feedback, a things that need to be tackled14:39
tobberydbergso ... powered/interop14:39
tobberydbergaprice ... did you have something specific there that you want to start with?14:40
hogepodgeWe were thinking that being a powered cloud should be a condition to participate in the powered program14:42
tobberydbergin the meantime I start by saying that I added "InterOp Powered Standards" as a filtering option for the PP homepage14:42
tobberydbergyou mean passport program hogepodge?14:42
apricePassport program14:43
hogepodgeThe aim of program is to guarantee interoperability and API conformance for end users.14:43
apriceYeah14:43
hogepodgeyes, passport14:43
tobberydbergyes, I agree and I like that thought for exactly that reason14:43
mnaseris it powered compute or powered platform we're talking about14:43
tobberydbergI would say compute14:43
hogepodgeCompute.14:43
tobberydberg++14:43
hogepodgeSwift isn't deployed widely enough to require it.14:44
mnaserthat seems reasonable enough14:44
tobberydbergso, only concern ... who is not today among the members?14:44
tobberydberg1,3 or more then 5?14:44
hogepodgeI don't have those numbers. I could work them up.14:45
tobberydbergThe mentioned concern have been the "Foundation sponsor" thing14:45
Danny_one of the concerns raised in Vancouver was to become "openstack powered" one had to become a corporate sponsor of the foundation14:45
Danny_yes14:45
Danny_which we're willing to discuss on a 1:1 basis14:45
tobberydbergif all of todays 10 clouds are, then is not an issue basically ... if not, can be hard for some smaller players?14:46
tobberydbergok14:46
mnaserso: if you're part (or willing to be part) of the passport program, you must be openstack compute powered, if you're not (then run it and become one), if you are not a corporate sponsor, talk to the foundation and they'll sort you out14:46
mnaserdoes that seem like a reasonable idea of what we're talking about?14:47
tobberydbergSounds just like that14:47
hogepodgeyes14:47
Danny_yes14:47
tobberydbergthe only thing to state in the reqs is that "if you are not willing to sponsor, call us and Danny will by you a dinner and then we are all good" ;-)14:48
tobberydberg*buy14:48
Danny_dinner AND drinks : )14:48
tobberydberghahaha14:48
tobberydbergbut I'm fine with that14:48
tobberydbergI guess that is more of a foundation issue telling some partners that today only are sponsors because of getting the powereed stamp why they should pay up14:49
tobberydbergI add that to the requirement section in the draft as well14:49
Danny_keep in mind that powered products (who are also foundation sponsors) are also listed in the public cloud marketplace14:50
Danny_https://www.openstack.org/marketplace/public-clouds/14:50
tobberydberg"6) They must be accepted for the OpenStack Powered Compute (or platform) - this to guarantee interoperability and API conformance for end users"14:51
*** peereb has quit IRC14:51
tobberydbergyes, I know =)14:52
tobberydbergJust a couple of minutes left ... what else?14:52
tobberydbergI will try to have a more "final draft" ready by the meeting in 2 weeks, might reach out to you before that to vet ideas14:54
apricetobberydberg: feel free to ping me and I can work with you on it14:54
tobberydbergAlso, will post to the mailing list when we have something more final14:54
tobberydbergawesome, thanks14:54
tobberydbergShould we reach out more "direct" to the current members when we have somehting more final?14:55
mnaseri think so14:56
mnaseror maybe say "we're discussing the final details in the next wg meeting"14:56
tobberydbergEven though they should know that these meetings and the mailinglist is the place to be to stay tunes and have a say in the discussions14:56
mnaser"You should be there" :-)14:56
tobberydbergexactly14:56
Danny_that's a good idea14:56
tobberydbergWhat gives the most, foundation reaching out and remember them of that?14:56
apriceyeah, we can reach out and cc you and zhipeng since you run the WG14:57
apricecan also remind them of the PTG - yall are planning to meet there right?14:57
tobberydbergSounds perfect14:57
tobberydbergyes14:57
tobberydbergAs it looks right now I have clearance to go there, so that is my plan14:58
apriceawesome!14:58
* mnaser has booked the day the PTG was announced14:58
mnaserlittle do you know travel is so cheap when you do it so far out14:58
tobberydberghahaha14:58
apricenice!14:58
apriceyou're an event planner's dream14:58
Danny_hahaha14:59
mnaser💅14:59
tobberydbergI have the ticket, but no flight and no hotel room14:59
mnaserexcept no cheap leftover hotel rooms for me14:59
mnaser:P14:59
tobberydbergare they all sold out?14:59
tobberydbergI mean at the official hotel14:59
apriceit is not14:59
mnaseri dont know but i menat like how usually at summits 2 weeks before15:00
tobberydbergphu15:00
mnaserthe foundation throws out those "We reserved too many rooms so grab em ultra cheap" :p15:00
apricekendall waters who runs ptg on our team says there are plenty of rooms right now15:00
tobberydberggreat! Will try to get that sorted next week15:00
apriceperfect!15:00
mnaserthanks everyone, off to to tc office hours :)15:01
tobberydbergSo, time is up for this week! Thanks a lot for your time today!15:01
Danny_👋15:01
tobberydbergTalk to you all in 2 weeks if not before that!15:01
apricethanks everyone!15:01
tobberydberg#endmeeting15:01
*** openstack changes topic to "New meeting time!! Thursday odd weeks at 1400 UTC in this channel!!"15:01
openstackMeeting ended Thu Jun 21 15:01:56 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/publiccloud_wg/2018/publiccloud_wg.2018-06-21-14.01.html15:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/publiccloud_wg/2018/publiccloud_wg.2018-06-21-14.01.txt15:02
openstackLog:            http://eavesdrop.openstack.org/meetings/publiccloud_wg/2018/publiccloud_wg.2018-06-21-14.01.log.html15:02
*** zhipeng has quit IRC15:07
*** blake has joined #openstack-publiccloud15:52
*** blake has quit IRC16:50
*** blake has joined #openstack-publiccloud16:50
*** blake has quit IRC16:55
*** blake has joined #openstack-publiccloud17:01
*** Danny_ has quit IRC17:20
*** blake has quit IRC17:55
*** blake has joined #openstack-publiccloud17:55
*** blake has quit IRC18:00
*** germs has joined #openstack-publiccloud18:05
*** germs has quit IRC18:05
*** germs has joined #openstack-publiccloud18:05
*** blake has joined #openstack-publiccloud18:07
*** germs has quit IRC18:10
*** blake has quit IRC20:17
*** blake has joined #openstack-publiccloud20:28
*** blake has quit IRC21:19
*** blake has joined #openstack-publiccloud21:20
*** blake has quit IRC21:24
*** blake has joined #openstack-publiccloud21:29
*** blake has quit IRC21:30
*** blake has joined #openstack-publiccloud21:32
*** blake has quit IRC21:33
*** blake has joined #openstack-publiccloud21:39
*** blake has quit IRC21:39
*** blake has joined #openstack-publiccloud21:49
*** blake has quit IRC21:49
*** blake has joined #openstack-publiccloud21:52
*** blake has quit IRC21:56
*** blake has joined #openstack-publiccloud22:15
*** germs has joined #openstack-publiccloud22:18
*** germs has quit IRC22:18
*** germs has joined #openstack-publiccloud22:18
*** blake has quit IRC22:19
*** blake has joined #openstack-publiccloud22:19
*** germs has quit IRC22:31
*** blake has quit IRC23:49
*** blake has joined #openstack-publiccloud23:49

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!