19:00:44 #startmeeting Poppy Weekly Meeting 19:00:45 Meeting started Thu Feb 5 19:00:44 2015 UTC and is due to finish in 60 minutes. The chair is amitgandhinz. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:46 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:00:49 The meeting name has been set to 'poppy_weekly_meeting' 19:00:53 #topic RollCall 19:00:56 o/ 19:01:03 o/ 19:01:12 #link https://wiki.openstack.org/wiki/Meetings/Poppy 19:01:57 o/ 19:02:07 hi all o/ 19:02:09 _/\_ 19:02:13 o/ 19:02:31 o/ 19:02:51 /\o/\ 19:04:01 #topic last Week Review 19:04:06 #link http://eavesdrop.openstack.org/meetings/poppy_weekly_meeting/2015/poppy_weekly_meeting.2015-01-29-18.59.html 19:04:27 ok only one action item from last week - and that was to review teh provider getting started guide 19:04:31 anyone do that? 19:04:59 #link https://wiki.openstack.org/wiki/Poppy/Provider_-_Getting_Started#Building_a_Provider_Driver 19:05:10 I saw parts of it, need to go through them in detail. 19:05:21 cool 19:05:43 i havent received any feedback, so please send it my way (or make the modifications if needed) 19:06:09 ok nothing else from last week 19:06:26 #topic Updates on K3 19:06:30 #link https://launchpad.net/poppy/+milestone/kilo-3 19:07:43 ok, only looks like one bug is assigned to miqui 19:08:04 miqui has a meeting conflict so isnt here today 19:08:20 anybody else working on any bugs currently? 19:08:46 ok, moving on to Blueprints 19:09:05 tonytan4ever: Message Queue Driver (should rename this to Taskflow Driver) 19:09:28 TaskFlow driver itself is done, so it's under review. 19:10:07 Now I am trying to work on breaking functions into TF tasks to apply retry/revert features to them. 19:10:14 There's also a dependent patch on it, which breaks up the tasks into simpler units. 19:10:24 tonytan4ever beat me to it. :P 19:10:52 ok cool 19:10:56 See:   https://review.openstack.org/#/c/151004/ and https://review.openstack.org/#/c/152987/ 19:11:33 ok will review it soon 19:12:43 malini: https://blueprints.launchpad.net/poppy/+spec/conformance-tests 19:12:47 any progress on this? 19:12:50 and welcome back =) 19:12:51 havent started on tht yet :/ 19:13:29 do you think you will be able to soon? we need this to enable providers to build their own drivers 19:13:46 else i can remove your name from it 19:14:04 can you remove my name for now? I will grab it later if I can 19:14:33 ok 19:14:59 amitgandhinz: https://blueprints.launchpad.net/poppy/+spec/cookie-rules 19:15:08 ok i havent done anything around this either 19:15:12 im going to remove my name from it for now 19:15:34 miqui: https://blueprints.launchpad.net/poppy/+spec/home-doc 19:15:59 miqui sent an update on the normal channel 19:16:10 he is working on this and will have a first pass to review shortly 19:16:24 obulpathi: https://blueprints.launchpad.net/poppy/+spec/mimic-racksapce-dns 19:16:41 I did not make any progress on thsi 19:16:52 but, I would like to keep my name 19:16:55 ok 19:17:03 i'll keep it as is 19:17:07 thanks :) 19:17:14 any other stories above being worked on? 19:18:12 I'm just working on familiarity with the project, and taskflow stuff with tonytan4ever. 19:18:27 & fixing all our READMEs :) 19:18:37 pretty soon, can actually start getting some work done ;) 19:18:45 malini: lol 19:18:49 haha, awesome sriram 19:18:53 welcome to Poppy sriram :) 19:19:12 :) 19:19:13 #topic New Items 19:19:21 ok i just added a new item to discuss 19:19:26 Openstack Vancouver! 19:19:41 https://www.openstack.org/summit/vancouver-2015/call-for-speakers/ 19:19:59 so a submission has to be made by Feb 9 19:20:06 which is Monday!!!! 19:20:07 eeek 19:20:18 whoa, thats really close. 19:20:21 eeek indeed! 19:20:39 do you want to talk about options now? 19:21:15 I created this etherpad - https://etherpad.openstack.org/p/Poppy_Vancouver 19:21:57 yeh we should talk about what we want to talk about 19:22:14 i need to submit this by Monday, so nows probably a good chance to talk about it 19:22:44 i think it should be something that would interest people who weren't necessarily CDN people 19:22:55 is there something different or interesting about the way we're doing poppy? 19:23:04 not really 19:23:15 (i'm proposing this as an additonal topic, not to replace the one you've suggested) 19:23:19 its a driver model (which is fairly common across openstack) 19:23:20 you just crushed our ego amitgandhinz! 19:23:32 heh 19:23:33 except we integrate with partner api's 19:23:48 others integrate with hardware api's (or vitual software api's) 19:23:57 we are similar to designate in that regard 19:24:13 we also need to focus on getting more providers to support and build drivers? 19:24:17 might be cool to talk about working with providers (who are competitors ) on a common framework 19:24:23 megan_w_: +1 19:24:29 +1 19:24:30 +1 19:24:31 +1 19:24:34 i think the goal of the talk should be on exposing Poppy 19:24:39 the partnerships 19:24:59 do we want to talk about the deployment of Poppy on Rackspace? 19:25:00 maybe a panel of us, come of our vendors, and perhaps the desegnate guys 19:25:21 amitgandhinz: i worry it might come off too marketing-ish 19:25:32 megan_w_: you make a lot of sense 19:25:40 it would be more compelling to the poppy story if we were using multiple providers 19:25:42 the whole intent of Openstack is vendor neutral cloud, rt? 19:25:47 ya 19:26:27 that means we need more providers, to be viewed as vendor neutral. 19:26:33 idk just thinking out loud. 19:26:39 the session i'm proposing wouldn't be technical, perhaps more conversational 19:26:40 poppy has drivers for fastly, akamai, maxcdn 19:26:49 drivers, but not participants :) 19:26:52 ya 19:26:58 that should be a :( 19:27:17 and we dont have that to a level we can talk about yet 19:27:33 but we have 5 months to work on it! 19:27:35 can we add a little bit on how we do anync stuff? 19:27:44 taskflow? 19:27:51 btw .. this will be completely technical right? 19:27:55 tht is an openstack thing -rt. 19:28:02 so nothing new there :( 19:28:13 it can be technical details, or it can be marketing-ish 19:28:23 ok 19:28:28 one part of the audience is design summit attendees (tech stackers) 19:28:36 the other half is sales, operators, etc 19:28:39 ok 19:28:56 let me write up the "multiple vendors on a common platform" proposal. we'll see if it looks good enough to submit 19:29:01 so may be an evolution of how we went from long latencies to async API 19:29:12 lets figure out what the aim of our talk is 19:29:23 backend as cassandra with no downtime and schema updates 19:29:29 ok 19:29:38 amitgandhinz: my biggest goal would be to get another operator using poppy 19:29:42 i feel talking about cassandra is opening up a hornets nest lol 19:29:48 hahha 19:29:51 not every operator is willing to deploy cassandra 19:30:02 Really? 19:30:07 its more over head 19:30:15 they already manage a mysql cluster 19:30:23 why deploy mongo or cassandra 19:30:24 Ah 19:30:27 requires expertise 19:30:33 amitgandhinz: you saw my goal. what's your goal for the talks? 19:30:45 I think thats where the sqlalchemy blueprint comes in. 19:30:55 my goal is to bring awareness to Poppy and increase community participation 19:30:56 sriram: ya 19:31:22 so i think megan_w_ our goals are aligned 19:31:26 the awarness piece can come from anything then...technical or non technical 19:31:43 i think operators need to know poppy exists and what it can do for them 19:31:51 but that turns into marketing speak 19:31:53 just people knowing what we're doing creates awareness. the participation part is different 19:32:02 but there is place for it in the conference 19:32:17 by the way, might be interesting to talk about logging/reporting in openstack 19:32:28 getting services "billing ready" 19:32:32 big data / sahara 19:32:58 that opens another can of worms around ceilometer when discussing reporting for billing 19:33:24 is there anything we can talk abt without opening a can of worms :/ 19:33:45 so ideas so far are ... 19:33:52 1. marketing speech on poppy 19:34:00 2. architecture of poppy and challenges faced 19:34:16 3. supporting multiple vendor api's on a common platform 19:34:28 lets write the ideas to the etherpad 19:34:37 bam :) 19:34:39 you beat me :( 19:34:45 =P 19:36:17 is HP or any other provider deploying or planning to deploy Poppy? 19:37:41 obulpathi: not that we know of 19:38:05 megan_w_: oh ok 19:42:59 Did everyone just drop off the face of the earth? 19:43:15 We are all here: https://etherpad.openstack.org/p/Poppy_Vancouver 19:43:36 #link https://etherpad.openstack.org/p/Poppy_Vancouver 19:46:06 sriram: The colors in 4 make it look like you are talking to yourself (and you are in the user list twice heh) 19:46:19 oh, really. 19:46:22 didnt realise it. 19:46:34 must have joined it twice :P 19:46:44 sriram: Or someone stole your name :P 19:46:55 heh 19:47:35 amitgandhinz: time warning, 13 minutes left in meeting 19:47:52 there is no other agenda items 19:47:55 ah, ok 19:47:55 mpanetta: that should be fixed now, cant change the other name. :/ 19:47:58 so lets do this for the remainder of time 19:48:09 ok 19:48:13 sriram: haha now you are real :P 19:48:33 how do i differentiate between TheSriram and "the real sriram" 19:48:37 as there can only be one 19:48:52 amitgandhinz: not another sriram… nooooooo 19:48:56 amitgandhinz: You don't you just need to cut one of their heads off 19:49:10 * sriram ducks his head and runs away 19:49:16 which one? 19:49:20 ahahhaa 19:49:21 mpanetta needs to watch ramayan 19:49:28 :D 19:49:29 that is the question. 19:49:32 ramramyaan 19:49:35 Ooo what's that? 19:49:37 two rams :P 19:49:52 https://yogyom.files.wordpress.com/2014/09/ravan.jpg 19:50:01 this meeting is gone downhill 19:50:09 haha 19:50:13 amitgandhinz: u hurt my religous feelings 19:50:17 is he using stevedore? 19:50:21 he got so many heads? 19:50:53 back to Vancouver 19:51:03 yes please 19:51:51 so my thoughts are around (1) which covers topics suggested ine 2 and 3 19:52:02 keeps it a bit high level 19:52:04 talks about poppy 19:52:08 talks about architecture 19:52:11 talks about challenges 19:52:18 and talks about partners 19:54:15 ok 6 min left 19:54:18 lets wrap it up 19:54:29 i worry something too generic won't attract people 19:55:02 if we do "using docker and mimic with Poppy CDN" 19:55:14 and then talk about poppy, arch, and partners 19:55:27 and then cover where docker helps in local deployment and testing 19:55:33 love it 19:55:34 and mimic helps with provider conformance 19:55:36 now we're talking 19:55:43 and docker and mimic are buzzwords to get ppl in 19:55:48 we really need to talk abt partners to explain why mimic fits in 19:55:52 ya 19:55:52 i was just going to say buzz works 19:57:10 ok, i'll tidy things up, and get feedback before i submit it on monday 19:57:20 #topic Open Discussion 19:57:29 3 min to talk about anything else (important) 19:57:32 we can add our ideas to the etherpad in the next couple of days, rt? 19:57:35 ya 19:57:56 cool, lets keep this in the back of our heads, and keep adding things that come to mind. 19:58:13 sounds good 19:58:56 ok anythign else to discuss? 19:59:00 1 min left 19:59:02 nothing from me 19:59:02 nows your chance 19:59:04 going once 19:59:06 im good. 19:59:07 nothing from me 19:59:15 thanks everyone 19:59:21 #endmeeting