19:02:54 #startmeeting Poppy Weekly Meeting 19:02:55 Meeting started Thu Aug 21 19:02:54 2014 UTC and is due to finish in 60 minutes. The chair is amitgandhinz. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:02:56 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:02:58 The meeting name has been set to 'poppy_weekly_meeting' 19:03:06 let’s continue on sahara channel 19:03:25 amitgandhinz: sorry 19:03:29 #topic roll call 19:03:37 who is here for Poppy? 19:03:39 o/ 19:03:39 * megan_w_ is here 19:03:45 \o/ 19:04:06 Here! 19:04:50 anyone from fastly or maxcdn? 19:05:00 or akamia? 19:05:25 looks like we might have a short meeting 19:05:34 potentially 19:06:02 #topic Review action items 19:06:11 #link: http://eavesdrop.openstack.org/meetings/poppy_weekly_meeting/2014/poppy_weekly_meeting.2014-08-14-19.00.html 19:06:31 catherine_r: update from you on this 19:06:37 (1) 19:07:14 I've reviewed some of doc via gerritt review for the issue mentioned in last week's meeting. 19:07:22 #link: https://review.openstack.org/#/c/113944/ 19:07:43 But I haven't finished that or moved to wiki review. Will work to get more done before next meeting. 19:07:57 i think good progress is being made on this. I still need to get the last set of comments handled 19:08:09 lets aim to get these docs merged before the next meeting 19:08:16 ok 19:08:39 #agreed: catherine_r and amitgandhinz will work to get the docs merged by next meeting: #link https://review.openstack.org/#/c/113944/ 19:08:57 ok, item 2 - amitgandhinz to move meetings higher up on the page 19:09:12 #link: https://wiki.openstack.org/wiki/Poppy 19:09:13 done 19:09:21 bam 19:09:41 (3) amitgandhinz to look into CDNManager in MaxCDN 19:09:50 this is not done. i will carry this over 19:10:06 #action: amitgandhinz to investigate MaxCDN CDN Manager API for master/sub accounts 19:10:19 (4) is the same as (3) =P 19:10:41 ok moving on .... 19:10:57 #topic Updates on Blueprints and Bugs 19:11:19 i started added the blueprints to launchpad: 19:11:24 #link: https://blueprints.launchpad.net/poppy 19:11:27 yay 19:11:46 can we get permissions to assign bluetprints and update them? 19:11:55 when creating a branch, be sure to name it bp/ 19:12:06 obulpathi: you cant do that right now? 19:12:09 hmmm..... 19:12:12 yep 19:12:22 I am naming my branches that way 19:12:36 #action: amitgandhinz to investigate permissions so that others in the team can manage bleuprints 19:12:40 but when I tried to assign a blueprint to myself .. I could not 19:12:53 ok i will investigate what needs to be done there 19:12:57 thanks for the heads up 19:12:59 thanks :) 19:13:40 we should try to keep the bp up to date with the correct status 19:14:13 do we want to spend time now updating it or do that offline? 19:14:41 let's do it now 19:14:46 that way we can get a feel for where we're at 19:14:50 ok 19:14:57 (unless anyone objects) 19:15:03 i think we have time today 19:15:08 agreed 19:15:15 agreed 19:15:25 #link: https://blueprints.launchpad.net/poppy 19:15:36 #link: https://blueprints.launchpad.net/poppy/+spec/add-docstrings 19:15:44 ametts: can i assign this to you? 19:15:54 since you showed eagerness on this previously =P 19:16:00 Sure 19:16:29 haha 19:17:12 https://blueprints.launchpad.net/poppy/+spec/cloudfront-driver 19:17:32 do you want to continue to drive this one obulpathi? 19:17:38 yep 19:17:42 please assign to me 19:17:45 or should we leave it open so others can also experience CF 19:17:58 I am open to both options 19:18:13 im inclined to leave it open for knowledge sharing 19:18:29 this one also has a dependency tree associated to it 19:18:54 #link: https://blueprints.launchpad.net/poppy/+spec/create-service 19:18:58 update service and multiple origins issues are open 19:19:00 no one has starting working on this yet right? 19:19:23 no from me 19:19:43 obulpathi: create bugs for those 19:19:57 I mean to say I have not working on these 19:20:14 but those are known issues, so lets create a bug to track it 19:20:18 sure 19:20:28 I will take that 19:20:30 https://bugs.launchpad.net/poppy 19:20:49 #link: https://blueprints.launchpad.net/poppy/+spec/docs-getting-started 19:20:57 this is in progress/review 19:21:06 my name goes on it 19:22:01 fastly and maxcdn driver stories are in the same boat as CF, so lets leave it open 19:22:27 for documentation, can you add my name for getting started with Poppy on Linux/Ubuntu/Fedora? 19:22:36 amitgandhinz: ^ 19:22:55 sure, can you create another bp for that 19:23:01 ok 19:23:52 ok flavors: flavors is making good progress, currently writing the tests for it 19:23:58 https://blueprints.launchpad.net/poppy/+spec/flavors 19:24:01 #link: https://blueprints.launchpad.net/poppy/+spec/flavors 19:24:32 there is a version submitted without the tests that could do with some review love (before the tests land) 19:24:54 #link: https://review.openstack.org/#/c/115130/ 19:25:19 #link: https://blueprints.launchpad.net/poppy/+spec/health 19:25:27 this is obulpathi's right? 19:25:33 yes, its is 19:25:46 state? 19:25:49 ping is done, waiting for approval 19:26:02 i'll put good progress 19:26:04 health is partially done, waiting for ping to get through 19:26:10 cool 19:26:16 did you address the comments for ping? 19:26:27 yes, addresses them and resubmitted the patch 19:26:35 #link: https://review.openstack.org/#/c/115408/ 19:26:36 s/addresses/addressed/ 19:26:40 ok lets get this reviewed 19:27:15 ok, i dont believe any of the other bp's are being worked on 19:27:27 tonytan4ever: you will need to create a bp for the model stuff you are working on 19:27:35 OK 19:27:42 CQL tests 19:27:52 I started looking into 19:27:57 can we add it to bps? 19:28:03 yes we should 19:28:14 did you look into the pysandra stuff i posted yesterday 19:28:30 yes. looking into pysandra and fakecassandra 19:28:42 no .. not yesterdays stuff 19:28:53 I only looking into jira cards details so far 19:28:53 #info: pysandra unit testing: http://javasplitter.blogspot.com/2013/01/embedded-cassandra-with-python-and-java.html 19:29:27 im not sure the viability of it if it helps but may be useful for our tests 19:29:47 ok, thanks 19:29:47 ok anything else regarding blueprints? 19:30:19 ... 19:30:21 ... 19:30:22 ... 19:30:26 ok moving on 19:30:39 #topic Permissions to assign and update blueprints 19:30:40 While we're waiting for Obu's response, there's the blue print I am working on: https://blueprints.launchpad.net/poppy/+spec/poppy-models 19:30:46 thats easy ;-) 19:31:00 #action: amitgandhinz to investigate permissions for blueprints 19:31:07 ok anything else on this topic? 19:31:38 i'll take that silence as a no 19:31:56 I am good wit it. 19:31:59 #topic Community Involvement 19:32:14 ok so we need to start ramping up the diversity of the team 19:32:36 agreed 19:32:41 +1 19:32:45 first thing i need to do is email the openstack-dev ML with announcing Poppy again 19:33:07 we did an initial round during the Atlanta Summit, but didnt get much feedback 19:33:20 i can help make sure our message is clear on that email 19:33:31 i think we can do better communicating the value of the project 19:33:34 amitgandhinz: Make sure you include links to wiki, github, et.al. so folks can see the progress that's been made. 19:33:36 now that we have a team, and valuable partners, we can go back to the community showing whats been happening 19:33:52 agreed. 19:33:53 also 19:34:02 we might garner more interest when they see akamai, fastly, maxcdn are all on board with the project 19:34:23 when it comes to provider involvement, i am wondering how we can get them involved more 19:34:45 what do we want from providers? they'll build their plugins when its time...but they cant really do that until we have the api 19:34:53 yeh 19:35:04 Why can't providers help build the API? 19:35:11 one we have the api and a few plugins, then other providers will prob get more interested 19:35:11 so if we're recruiting them, should we be saying, "come give us your input on what a standard api should look like?" 19:35:20 providers can if they want to 19:35:37 yeh 19:35:41 i thought last week's discussion about account structure was useful 19:35:46 definitely 19:35:59 maybe we can promote our agenda better??? 19:36:12 right now the api is very much driven by this team, but i would like to see providers inflluence the design also 19:36:18 for example, if they knew we wanted to talk about ssl certs today, would they have come? 19:36:19 +1 19:36:25 potentially 19:36:41 yeah me too. we just need to make it attractive to them 19:36:50 so lets try finalizing the agenda earlier in the week and then megan_w_ can work her magi 19:36:54 magic 19:36:58 i don't have any magi 19:37:02 only magic 19:37:15 amitgandhinz: seems like a good plan 19:37:24 and let's try to have a meaty topic everytime 19:37:30 even if its just design 19:37:40 #agreed: amitgandhinz to finalize agenda by Tuesday PM 19:38:07 #agreed: megan_w_ to communicate with providers before weekly meeting 19:38:13 bam 19:38:33 along with providers, if we can bring more poppy deployers (like Rackspace) that will add weight to to Poppy 19:38:38 then we can focus on more operators, which will really get providers interested 19:38:38 #agreed: amitgandhinz and megan_w_ to come up with Grade A meat in the agenda 19:38:49 obulpathi: great minds :) 19:39:02 I am planning to reach out to HP 19:39:03 copying ideas :D 19:39:13 they currently work with akamai, i believe 19:39:15 what happened with edgecast? 19:39:27 we just havent kicked off with them yet 19:39:33 their head guy was out for a week 19:39:36 oh ok 19:39:43 we were going to reconvene once he's bakc 19:39:49 cool 19:40:05 obulpathi: when was the next local openstack meetup 19:40:15 it would be good to get on their schedule to talk about Poppy 19:40:22 today 19:40:25 haha 19:40:27 ok next month then 19:40:31 yes 19:40:38 good idea 19:40:50 do you want to take charge on that since youre familiar with it? 19:41:08 sure 19:41:10 #action: obulpathi to get on the local atlanta Openstack Meetup schedule for poppy 19:41:36 dhellmann^ 19:41:57 You want me to schedule a meeting for Poppy? And you wil ldo the presentaiton? 19:42:07 presentation 19:42:11 ok i think thats a good step one for community building, and lets see what we can do next 19:42:22 obulpathi: we both can do the presentation =) 19:42:30 all of us can get on stage =P 19:42:40 amitgandhinz: Yes, I can switch slides :) 19:42:45 It's only a bar. There is no stage. :) 19:43:01 well, not sure if we want to do coyote ugly style presentations 19:43:06 that might get awkward 19:43:08 ewwww 19:43:08 lol 19:43:12 ok, let's move on 19:43:15 lol 19:43:16 ametts: Yes,I am in touch with dhellman. late response 19:43:35 ok moving on... 19:43:43 #topic SSL cert provisioning 19:44:01 is there much to discuss here, or should we defer to next time when the providers are present? 19:44:28 in related news, CloudFront released some SSL enhancements yesterday 19:44:28 yeah 19:44:40 we definitely need them to have an intelligent disucssion about it 19:44:46 them= providers 19:44:56 amitgandhinz: oh nice 19:45:01 #link: http://www.zdnet.com/aws-bolsters-cloudfront-security-7000032847/ 19:45:20 I think we can do some prep talk, about what we know about the providers. 19:45:48 tonytan4ever: take it away 19:45:57 megan_w_: you are out the next two meetings 19:45:59 #link: from aws website: https://aws.amazon.com/blogs/aws/cloudfront-ssl-ciphers-session-ocsp-pfs/ 19:46:03 yes i am 19:46:09 you want to be here for those discussions with the providers? 19:46:29 perhaps. we'll talk agenda offline 19:46:33 ok 19:46:37 And who will be live-blogging the wedding to #openstack-poppy? 19:46:39 ok 19:46:48 moving on... 19:46:54 #topic Open Discussion 19:47:17 ametts: we run a cdn service, megan_w_ will be live streaming =P 19:47:25 Ah. Of course. :) 19:47:35 you know it 19:47:57 ametts: any idea when we'll know about our talk proposal? 19:47:57 ok any open discussion items from anyone? 19:47:58 Megan will be our first customer? 19:48:35 i'd like to plan to demo poppy in paris 19:48:41 voting has already closed 19:48:42 megan_w_: No idea. I've been watching openstack-dev for clues, but I haven' t seen any. Should be soon. 19:48:56 if we dont get a session accepted, will we still ahve design sessions? 19:49:02 megan_w_: annegentle said maybe tomorrow... 19:49:07 oh cool 19:49:09 thanks catherine_r 19:49:12 one thing I forgot: AWS does not have an official python client 19:49:17 yuck 19:49:18 They'll have to be rogue/informal design sessions. 19:49:21 we should add it to bp or bugs 19:49:24 ok 19:49:28 Only incubated products get scheduled ones. 19:49:34 that's what i was wondering 19:49:36 good to know 19:49:44 They didn't even do Unconferences in the Atlanta summit. 19:50:00 ok, we'll plan our summit presence once we hear about the session, i guess 19:50:08 sounds like that decision is close enough to wait 19:50:43 yeh, else we just stand outside the eiffel tower holding poppy banners 19:50:49 maybe a field trip to normandy ;-) 19:50:58 ha 19:50:59 I was going to suggest that we distribute poppy flowers, but that might get us in trouble with customs. 19:51:07 giverny! 19:51:15 flowers :-) 19:51:30 lol, i was wondering what that was 19:51:41 ok, that's it for me. do we want to tlak about the aws python thing? 19:51:53 http://sharonsantoni.com/2013/06/the-poppy-fields-of-normandy.html 19:52:05 megan_w: sure 19:52:20 the thing is aws does not have a official python bindings for their API 19:52:36 amitgandhinz: Ah... good link. 19:52:40 obulpathi: can we just fork boto and apply our requirements to it? 19:52:44 on thei home page: https://aws.amazon.com/blogs/aws/cloudfront-ssl-ciphers-session-ocsp-pfs/ 19:52:54 and then submit back upstream? 19:53:03 amitgandhinz: yes 19:53:14 thats the plan for now 19:53:22 Wait. 19:53:30 just want to share it here 19:53:42 If you do that in Python, what will you be calling behind the scenes? 19:53:53 do what in python? 19:53:57 AWS API 19:54:08 REST API using "XML" 19:54:22 oic. I get it now. 19:54:41 boto already is a python client, its just out of date 19:54:49 and the patches are slow to apply 19:55:14 so if we fork boto, get the CloudFront pieces to where we need it to be and run with that until they merge it back upstream 19:55:24 Yeah, I was just temporarily confused about how we'd use boto if it didn't know anything about CloudFront. 19:55:48 no, it has CF support, just not things like multiple origins etc which the API supports 19:56:03 yes, only some pieces are missing 19:56:12 Ah. Ok. 19:56:21 #agreed: obulpathi will fork boto and apply necessary enhancements and submit upstream 19:56:29 got it 19:56:42 ok any other discussion items? 19:56:46 we have 4 minutes 19:56:55 not from me 19:57:05 Anyone know a 4-minute song we could sing? 19:57:12 "shake it off" 19:57:20 - taylor swift 19:57:28 yeah, i gotta go 19:57:30 idk if its 4 min tho lol 19:57:59 "papi" by J-Lo 19:58:13 ok i think we done here 19:58:17 * ametts thinks amitgandhinz has terrible taste in music 19:58:32 geez, no country, no hip hop 19:58:38 later gators 19:58:41 #endmeeting