Thursday, 2018-06-07

*** blake has quit IRC01:56
*** germs has quit IRC03:37
*** germs has joined #openstack-publiccloud03:38
*** blake has joined #openstack-publiccloud03:57
*** blake has quit IRC04:02
*** blake has joined #openstack-publiccloud04:09
*** blake has quit IRC04:14
*** germs has quit IRC04:16
*** blake has joined #openstack-publiccloud04:45
*** blake has quit IRC04:50
*** mma has joined #openstack-publiccloud06:05
*** mma has quit IRC06:34
*** mma has joined #openstack-publiccloud06:37
*** mma has quit IRC06:38
*** mma has joined #openstack-publiccloud06:55
*** pilgrimstack has joined #openstack-publiccloud08:17
*** pilgrimstack has quit IRC08:23
*** pilgrimstack has joined #openstack-publiccloud08:24
*** mma has quit IRC10:58
tobberydbergReminder: Bi-weekly meeting here in the channel at 1400 UTC today10:58
tobberydbergAgenda at https://etherpad.openstack.org/p/publiccloud-wg10:58
tobberydbergFeel free to add topics!10:59
*** mma has joined #openstack-publiccloud11:21
*** VW has joined #openstack-publiccloud12:35
*** chris2000 has joined #openstack-publiccloud12:50
*** VW has quit IRC13:09
*** VW has joined #openstack-publiccloud13:10
*** VW has quit IRC13:15
*** chris2000 has quit IRC13:47
* mnaser really wanted to start attending but has a conflict at 10am from day 113:47
tobberydbergThe intention is half way there mnaser .... we hope to see you here next meeting then :-)14:00
tobberydbergo/14:00
apriceo/14:00
tobberydberg#startmeeting publiccloud_wg14:01
openstackMeeting started Thu Jun  7 14:01:53 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
tobberydbergHi aprice !14:02
apriceHello!14:02
tobberydbergSo, who's around?14:02
mnasero/14:03
mnaser(looks like my conflict is no longer one..)14:03
tobberydbergwhoop whoop =)14:03
tobberydberghttps://etherpad.openstack.org/p/publiccloud-wg14:04
tobberydbergagenda ^^^14:04
tobberydbergI hope that a few more pops in during the meeting here14:04
tobberydberg#topic 1. Recap Vancouver Summit14:05
*** openstack changes topic to "1. Recap Vancouver Summit (Meeting topic: publiccloud_wg)"14:05
tobberydbergWell .. all of you here were in Vancouver so probably pretty aware of what happened there ... but will mention a few things for the record14:06
tobberydbergI think that we had pretty good interest around all our Forum sessions in general14:07
tobberydbergA lot of PTLs and cores interesting in the "missing features list"14:07
tobberydbergGot some feedback how we can do that even better, which was good14:08
tobberydberg#link to that session: https://etherpad.openstack.org/p/YVR-forum-missing-features-pc14:08
mnaser++14:08
mnaserit was a great session14:08
tobberydbergGot some more comments to the items at launchpad as well14:08
tobberydbergYea, I was surprised14:09
pilgrimstackhi14:09
tobberydbergwelcome pilgrimstack14:09
pilgrimstackdouble meeting once again for me, I'm partially with you guys, sorry14:09
pilgrimstackhi tobberydberg14:09
tobberydbergAlso, a lot of interest around the passport, which is good and motivating to take the next step there14:09
tobberydbergForum session #link for that: https://etherpad.openstack.org/p/YVR-forum-passport-program14:10
tobberydbergOne thing that became pretty clear was that we need to come to a conclusion on our way forward, define the use case, then choose technique for how to solve the problem14:11
mnaserindeed14:12
mnaseri feel like we havent progressed much a little bit since then :(14:12
tobberydbergno, basically nothin14:13
tobberydbergthat leads me into the next topic ... if we don't have any questions14:14
mnaseri just hope that we can move with a potential target/solution14:15
tobberydbergthats the next topic - so good =)14:16
tobberydberg#topic 2. Passport program - way forward14:16
*** openstack changes topic to "2. Passport program - way forward (Meeting topic: publiccloud_wg)"14:16
tobberydbergSo, we have an "old" spec that was created after the OpeStack Days UK14:17
tobberydberg#link Passport program - way forward14:17
tobberydbergoops14:17
tobberydberg#link https://git.openstack.org/cgit/openstack/publiccloud-wg/tree/doc/source/passport_program.rst14:18
tobberydbergThis was written before the programs release and based on the discussions that took place there. My suggestion is that we rewrite this and propose the "new" definition (use case) for the Passport Program14:19
aprice+114:20
tobberydbergThen we can collect the feedback there, discussion the use case spec there so it feels more official14:20
apriceand I think that will transition nicely into revamping the website language per mnaser's feedback14:20
tobberydbergYes, absolutely. The wording feedback should be reflected in the definition in the spec as well14:21
apriceagreed14:21
tobberydbergI hope to be able to pull that off until next meeting in 2 weeks...might need help though, have pretty much on the agenda upcoming weeks14:22
apriceim happy to help with that14:22
tobberydbergAwesome, thanks!14:23
mnaserthank you aprice14:23
tobberydbergI setup an etherpad and post a draft there and then we (and everyone that wants to help put) can collaborate there14:23
tobberydberg#action tobberydberg to setup etherpad for passport spec draft and post draft in 2 weeks14:24
apricesounds good!14:24
tobberydbergWhat do we want in that spec? Do we want tech solution at all?14:25
*** jamesmcarthur has joined #openstack-publiccloud14:25
tobberydbergOr just the use case we are trying to solve?14:25
apriceI think that it should start with the use case and goal of the program14:25
tobberydberg+114:25
apriceand once we get folks to weigh in, we can dig into the technical specs14:26
tobberydbergsounds good14:26
tobberydbergI'll talk to Darcy and Howard as well so that they know what is going on here14:27
tobberydbergA lot of the good use of the PP is a little bit on hold on the coupon solution .... thinking about the meetup group handouts etc14:28
tobberydbergSo, would be really neat to have that in place to Berlin14:29
apriceyeah, the program came up again in the user community leadership forum session14:29
mnaseri think handouts are a bit hard14:30
mnaserbecause as a provider i don't know where they'll end up14:30
mnaserheck, they might end up on some online forum with someone signing up and using it to mine crypto :)14:30
mnaserso there's a it of a harder way of tracking things of whats going on14:30
tobberydbergsingle coupon codes14:30
tobberydbergnot worse than offer trial14:30
tobberydbergone code only valid once14:30
jamesmcarthurRight - I think the idea was a one time use.14:31
mnaseri guess it comes down to is it self-serve or is it vetted14:31
mnaserbecause a coupon feels to me like it would be self-serve making it harder to know about bad stuff(tm) only after the fact14:31
mnaseri14:31
mnaseri'd be okay with it as long as we have some sort of clear agreement with those who hand them out i guess14:31
tobberydbergAgreed14:32
tobberydbergShould make sense where to hand them out14:32
mnaser++14:32
tobberydbergLiked the feedback from the us meetup group14:33
tobberydbergthey put in a lot of work into that14:33
*** VW has joined #openstack-publiccloud14:34
jamesmcarthuryou could also capture user info and ask them to opt-in to communications so you could follow up after they use the coupon code14:34
mnaserjamesmcarthur: that is a good idea too14:34
tobberydbergI totally agree with them, at the high level, that you should get a good experience of using openstack no matter what member you pick14:34
tobberydberg++ jamesmcarthur14:35
tobberydbergbut, that's pretty hard ... but I believe that we should put together a list of requirements that you need to fulfil to be in the program14:36
tobberydbergKnow we had, but we haven't been good at following up o them14:36
tobberydbergFiltering on foundation homepage is one thing that can make the fit better, but the feeling of openstack is more than that14:38
tobberydbergWe talked about "Powered" requirement. Thoughts around that?14:38
* mnaser shrugs14:44
mnaseri don't recall this, i recall discussing the idea of the requirement of being a corporate member14:45
apricemnaser: i can clarify14:45
apriceto be considered a powered cloud, there are a set of requirements. To date, one of those has been to be a Foundation corporate member, but we have worked with providers who are unable to fulfill that requirement14:46
apriceso that's just one of the criteria in addition to testing that Chris Hoge from our team runs.14:46
mnaseroh i see14:46
apricesince we collect so much information on the Powered clouds for the public cloud marketplace, the idea was to encourage the Passport members to be Powered so that the criteria we collect (what version of OpenStack they're running among many) are options for filter on the passport page14:47
tobberydbergYups, we discussed this and the corporate member part is the part that doesn't make sense in this case14:47
mnaser++14:48
mnasermaybe as an intermediate14:48
tobberydbergthe rest would be perfect for PP members ... both when it comes to Chris tests and the information that is collected about the clouds14:48
mnasermaybe we can add something like14:48
mnaser"passport enabled" as a field for starters14:49
mnaserthat you can filter on14:49
apriceyeah, and I think that this goes back to the goal of the program which we need to figure out. because i think that once we agree on that direction, we will have a better sense of how we want to filter / represent participants14:51
tobberydbergin the markeplace you mean=14:51
mnaseryes tobberydberg14:51
tobberydbergDid you and danny get a task to look into this aprice?14:51
mnaserso looking through the marketplace, we can have users maybe filter based on those that are part of passport program14:51
apricetobberydberg: to look into which piece?14:52
tobberydbergthats a good idea to internally market at o.o the program as well14:52
pilgrimstackmy input about "Powered" or not: in the best situation, that would be great and assure the community that we offer an similar experience (at least on the APIs) to the use, the fact is we (OVH) were certified, and now we don't pass the current requirement14:53
tobberydberg"something" regarding the requirements etc fo be part of powered... Let me see if I have more notes around that14:53
tobberydbergMight be that I don't remember correct14:53
pilgrimstackso if the passport program requires a powered certification, we'll lose some public cloud actors14:53
apricetobberydberg: ah yes, he and I can look into that today.14:54
tobberydbergyep, now ... we do the same from time to time ... and all tests are not really applicable for a public cloud either - admin things and ceilometer stuff14:55
tobberydbergnot sure about how the latest tests and how those looks though14:55
tobberydbergthanks aprice14:56
apricei think that's a bigger convo and jamesmcarthur and I can talk to Chris about how that's planning to evolve.14:56
tobberydbergNeed to very soon run into a meeting here. If someone wan't to continue discuss this at some other time soon, let me know and we can schedule something14:57
tobberydbergawesome aprice14:57
apriceill see if Chris and Danny can join the next PCWG meeting so we can have a bigger discussion14:57
jamesmcarthurtobberydberg: can you send us the exact things you think are not appropriate for Public Cloud?14:58
tobberydberg++ aprice14:58
jamesmcarthurI'd like to make sure Chris and Danny are armed with that before the next meeting.14:58
tobberydbergI can look into that jamesmcarthur ... unfortunately I haven't been taking notes of it, but lets see what I can find14:59
tobberydbergThanks for today folks! Need to run here! Lets talk more soon!14:59
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  7 15:01:22 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-07-14.01.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/publiccloud_wg/2018/publiccloud_wg.2018-06-07-14.01.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/publiccloud_wg/2018/publiccloud_wg.2018-06-07-14.01.log.html15:01
apricethanks all!15:05
*** pilgrimstack has left #openstack-publiccloud15:21
*** pilgrimstack has joined #openstack-publiccloud15:22
*** pilgrimstack has quit IRC16:37
*** jamesmcarthur has quit IRC16:39
*** jamesmcarthur has joined #openstack-publiccloud16:40
*** jamesmcarthur has quit IRC16:44
*** jamesmcarthur has joined #openstack-publiccloud16:58
*** jamesmca_ has joined #openstack-publiccloud17:00
*** jamesmcarthur has quit IRC17:03
*** jamesmca_ has quit IRC17:17
*** zigo has joined #openstack-publiccloud20:34
*** VW_ has joined #openstack-publiccloud20:45
*** VW has quit IRC20:49
*** VW_ has quit IRC20:50
*** germs has joined #openstack-publiccloud20:59
*** germs has quit IRC21:01
*** germs has joined #openstack-publiccloud21:03
*** germs has quit IRC21:04

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