19:00:20 #startmeeting Poppy Weekly Meeting 19:00:21 Meeting started Thu Nov 13 19:00:20 2014 UTC and is due to finish in 60 minutes. The chair is amitgandhinz. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:22 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:00:24 The meeting name has been set to 'poppy_weekly_meeting' 19:00:32 #topic RollCall 19:00:34 o/ 19:00:35 o/ 19:00:39 o/ 19:00:42 hey guys 19:00:48 \o/ 19:01:03 ugh ametts has two hands. he can do twice the work ;-) 19:01:10 \\o// 19:01:17 ummmm...... 19:01:20 (I'm limber) 19:02:07 #link https://wiki.openstack.org/wiki/Meetings/Poppy 19:02:19 #topic Review Last Week 19:02:30 #link http://eavesdrop.openstack.org/meetings/weekly_poppy_meeting/2014/weekly_poppy_meeting.2014-11-06-21.01.html 19:02:52 megan_w_: did you investigate SNI? 19:03:00 yes i did 19:03:06 care to share? 19:03:31 akamai says they aren't ready to heavily invest in SNI yet, since all broswers aren't compatible 19:03:50 i haven't heard back from Fastly, but i sent the email less than 5 mintues ago.. 19:03:57 lol 19:04:03 ok 19:04:07 sorry what is "SNI" ? 19:04:17 http://en.wikipedia.org/wiki/Server_Name_Indication 19:04:24 ..tahnks 19:04:43 basically, a way to serve over TLS without buying your own cert.. 19:04:44 and on this topic of SSL, I spoke with the Barbican team at the summit 19:05:03 we may utilize them to generate SSL certs and send to providers 19:05:05 o/ 19:05:12 o/ 19:05:31 amitgandhinz: do they have a timeline for their project? or is it working today? 19:05:49 they are "working" with dogtag today 19:05:55 ok 19:05:59 they are about to start with semantic i believe 19:06:10 to wrap this action item up....i will continue to look at SNI 19:06:15 but we are probably looking at a Q2 timeframe 19:06:28 #action megan_w_will continue to look at SNI 19:06:37 but i think we should follow our plan of not worrying about it until 2 providers support it 19:06:50 malini: take care of posting review guidelines 19:06:51 or whatever the "sanity check" number was for features 19:06:55 megan_w_: _1 19:06:56 +1 19:07:19 I created a wiki page with whatever I cud think of https://wiki.openstack.org/wiki/Poppy/Developer_-_Review_Guidelines 19:07:32 Will update this on an ongoing basis 19:07:38 oooh nice! 19:07:41 thanks 19:07:41 so should everybody else :) 19:08:00 yw :) 19:08:21 cool 19:08:24 bookmarking it :) 19:08:26 malini to update guidelines regarding running api tests 19:08:42 Good. I will keep track of it too. 19:08:49 did we have an action for the api tests? 19:08:55 I missed that :( 19:09:11 Can we carry it over? 19:09:12 has your name on it =P 19:09:13 ok 19:09:17 #action malini to update guidelines regarding running api tests 19:09:42 ok, and there are a bunch of unassigned items that appear to be a misuse of the action tag =P 19:09:52 so im going to skip over them 19:09:57 thats me :D 19:10:10 #action obulpathi to learn meetbot ;-) 19:10:19 anoted :) 19:10:30 #topic Blueprints 19:10:32 we will have a test next week obulpathi 19:10:37 #link https://blueprints.launchpad.net/poppy 19:10:46 ok so first thing to note on this 19:10:55 i spent some time with my project manager hat on 19:11:09 and i assigned blueprints to series and milestones. 19:11:14 yayy 19:11:16 so you will now see kilo on most of them 19:11:20 yay 19:11:30 and drilling into kilo you will see kilo-1, kilo-2, kilo-3 milestones 19:11:39 so that we can track the openstack release cycles 19:11:50 fyi kilo-1 is due on Dec 5 !!! 19:12:00 oh openstack has release cycles inside each release? 19:12:02 ok 19:12:03 no pressure :/ 19:12:13 but this will help us priortize and work on the most important deliverables 19:12:37 i also added a "future" series which consists of "ongoing" and "next" 19:12:47 they should be self explanatory what they mean 19:13:11 to see what is assigned to kilo -1 19:13:13 #link https://launchpad.net/poppy/+milestone/kilo-1 19:13:36 so we can track our discussion based on this list instead of the full list of bprints 19:13:44 any questions? 19:14:02 nope 19:14:03 s/dec 5/dec 4 ;-) 19:14:06 nop 19:14:11 Sounds good to me 19:14:33 okie doke 19:14:34 so, each release has three parts? 1, 2 and 3 each spanning 2 months? 19:14:52 openstack release i mean 19:15:02 obulpathi: pretty much 19:15:12 cool 19:15:13 there is r1, r2, r3, and then time for the final cut 19:15:21 oh ok 19:15:39 #link https://blueprints.launchpad.net/poppy/+spec/provider-url-in-conf 19:15:43 malini: ^ 19:15:54 It is in progress 19:15:58 i see a PR for that? 19:16:09 yeah..which is failing horribly 19:16:14 nice 19:16:20 I need to fix/add tests 19:16:20 ok marked as Good Progress 19:16:43 #link https://blueprints.launchpad.net/poppy/+spec/home-doc 19:16:46 miqui: ^ 19:17:18 hi... have not started... the bp of docstrings can be closed, but is pending the failed doc jobs.. 19:18:30 ok. will you be starting on the home-doc soon?" 19:18:34 yes 19:18:48 cool 19:19:09 tonytan4ever: akamai driver 19:19:10 amitgandhinz: will you log a bug for the failed eradthedocs build? 19:19:23 miqui: sure 19:19:52 I'd call it Good Progress, I am working with Akamai folks on finishing this. 19:20:19 Got one more purge api to go, but all other features are in good hands. 19:20:48 awesome! 19:20:48 tht is very humble tonytan4ever :D 19:20:57 +1 19:21:14 +1 19:21:23 humble is good. 19:21:25 obulpathi: https://blueprints.launchpad.net/poppy/+spec/cloud-dns-driver 19:21:34 fixed all the bugs 19:21:42 not adding the unit tests 19:21:50 not? 19:21:51 should be good to go by tomorrow 19:21:54 now 19:21:59 s/not/now/ 19:22:02 haha, malini was about to punch you haha 19:22:12 lucky for me 19:22:18 good for obulpathi I am WFH 19:22:21 awesome 19:22:21 she is not working from office today :D 19:22:45 obulpathi: that also takes care of the Default DNS driver? 19:22:56 default DNS driver is done 19:23:02 but I got it bundled with teh rackspace one 19:23:08 so both will roll out at same time 19:23:11 ok 19:23:22 ill keep it in progress until a patch is available to review 19:23:37 tonytan4ever: Purge? 19:23:48 That one is under review. 19:24:08 Addressed a few comments. 19:24:16 lets get some eyes on it 19:24:34 obulpathi: Patch? 19:24:55 the poppy-server hanging bug was forcing patch to sit in review 19:25:06 there is currently a merge conflict on it 19:25:06 https://review.openstack.org/#/c/128682/ 19:25:08 now the server hanging bug is addresed, 19:25:15 yes, will fix it 19:25:18 thanks :) 19:25:38 tonytan4ever: https://blueprints.launchpad.net/poppy/+spec/set-restrictions 19:25:52 That one is under review too. 19:26:06 could use more reviews, folks. 19:26:06 https://review.openstack.org/#/c/131252/ 19:26:19 yup lets get some eyes on this too 19:26:24 sure 19:27:04 ok so blueprints wise i think we are getting close 19:27:09 will do tonytan4ever 19:27:13 lets just get better about reviewing 19:27:23 somethings are sitting for a while 19:27:46 anything else on blueprints? 19:27:52 before we move on to bugs? 19:28:13 whena re we planning for the worker/queue mechanism? 19:28:31 after we get this stuff discussed above done =) 19:28:45 so its for kilo-2 .. ok cool 19:28:46 i have it slated for kilo 3 currently 19:28:50 oh ok 19:28:55 but i can move it up to kilo 2 if needed 19:29:13 if we do that all our patches will be much small and can improve our speed 19:29:21 agree 19:29:29 +1 19:29:58 caching rules is also one of the last major features for kilo1/2 that we need to expose 19:30:13 i have it down as kilo2 as i dont think we will get to that by dec 4 (or maybe we will =)) 19:30:39 ok 19:30:42 but we need to get through the other kilo1 in progress work first 19:30:48 then i will draw more bp in 19:30:55 cool .. got it 19:31:07 #topic bugs 19:31:34 full bug list #link: https://bugs.launchpad.net/poppy 19:31:54 i have targeted some of these to kilo1: https://launchpad.net/poppy/+milestone/kilo-1 19:32:29 #link: https://bugs.launchpad.net/bugs/1389790 19:32:31 Launchpad bug 1389790 in poppy "API tests failing for create service" [High,New] 19:32:40 who wants to take this one? 19:32:49 I am 19:32:50 That one can go to me 19:32:57 I am working on thsi one 19:32:58 sorry 19:33:00 ....and fight 19:33:02 OK 19:33:04 haha, it goes to obulpathi 19:33:06 he was first 19:33:14 aah…missed a good fight 19:33:16 I fix deadlock so I am not fighting. 19:33:23 :D 19:33:29 thanks Tony :) 19:33:40 #link https://bugs.launchpad.net/bugs/1389766 19:33:46 Launchpad bug 1389766 in poppy "API tests for flavors are failing" [High,Confirmed] 19:34:02 that sounds like the api test code is broken 19:34:13 obulpathi updated this, rt? 19:34:14 based on the "flavor_ref" rename 19:34:19 I think this is fixed? right? 19:34:26 yes. 19:34:27 yeah, I remember fixing it and 19:34:33 it is merged too 19:34:35 and it looks like merged too 19:34:37 yep 19:34:41 can i close it? 19:34:49 we might have a few open bugs, but not related to flavor_ref 19:34:53 ok 19:34:57 I'll create a new one if needed 19:34:58 I forgot to add that closes bug text in patch message 19:35:04 make sure we reference bugs in the commit messages so they are linked 19:35:08 sure 19:36:08 ok i slated the rest for kilo2 and onwards as they didnt feel critical enough for right now 19:36:16 any objections? 19:36:41 nope 19:36:45 nope 19:37:06 #topic New Items 19:37:13 no new items on the agenda 19:37:18 #topic Open Discussion 19:37:28 amitgandhinz: you can assign #1381091 to me... 19:37:33 any one want to discuss anything in particular? 19:37:48 i do 19:38:01 question: who does the zuul gates for poppy? 19:38:07 assigned 19:38:15 folks from openstack infra team? 19:38:17 that will be openstack-infra 19:38:27 anyone in particular? 19:38:41 there are yaml files that have it configured what to run at the gate 19:38:54 they all live in the openstack-infra repo 19:38:57 right... zuul config stuff sure.. 19:39:08 we dont have a dedicated person who manages itfor us (that i know of) 19:39:17 i did the initial set up 19:39:22 ok, 19:39:34 infra approves it? 19:39:38 yeh 19:39:41 k 19:39:58 basically you submit patches to the files and they approve it and merge it in 19:40:06 k 19:40:25 i wonder why docs gate did not work 19:40:37 i.e. test failed, but merged ocurred... 19:40:54 maybe they are not voting? 19:41:04 not sure. i wonder if its an issue with readthedocs specifically 19:41:10 good one. i will check the infra code 19:41:18 because the docs env on tox is working 19:41:26 you can try running doc8 also 19:41:28 exactly.. 19:41:38 is tht like pep8? 19:41:40 doing it now... 19:41:41 yeh 19:42:08 my guess is due to the obsure error in readthedocs that its not a syntactical issue, maybe something else 19:42:37 ok next item..... 19:42:45 amitgandhinz: did you already update abt the Paris summit? 19:42:57 can we all agree to get better with reviewing 19:43:05 i feel patches are sitting there forever 19:43:07 +1 19:43:12 yes :-$ 19:43:12 and we have a lot of -1's there too 19:43:21 yes 19:43:31 so we need to kill patches that arent going anywhere, or fix them, or mark them WIP 19:43:48 +1 19:43:55 the cassandra tests patch 19:43:58 is just sitting there 19:44:05 #agreed we will be better reviewers and nicer patchers 19:44:16 can we kill that one and 19:44:31 I will add it when we try it again? 19:44:33 yeh 19:44:42 https://review.openstack.org/#/c/122824/ 19:44:47 ok .. 19:44:56 and the queue-driver patches need to be merged together, and old ones abandoned 19:45:19 and also name the branch after the name of the bleuprint 19:45:53 ok 19:46:04 I think tonytan4ever merged it 19:46:06 https://review.openstack.org/#/c/132063/ this is the combined queue-driver set 19:46:08 so I will delete mine 19:46:09 patch 19:46:14 ok 19:46:42 malini: did the py34 opencafe patch get merged? 19:46:54 no..But I have it in my personal repo 19:47:03 ok, will wait on that then... 19:47:04 We can point to that one in tox.ini for now? 19:47:10 ok 19:47:25 alrighty 19:47:34 does anyone still need an update on the summit? 19:47:43 i think i updated some on the normal channel the other day 19:47:54 aah..ok..I thought miqui missed it 19:47:56 but i can go over it again if anyone wants it 19:48:05 i chatted with miqui on tues i think 19:48:10 cool 19:48:10 +1 19:48:18 ..yes thanks.. 19:48:51 ok any other topics? 19:49:34 not from me... 19:49:37 nop 19:49:39 me neither 19:49:42 you all get 11 minutes of your time back then =) 19:49:50 thanks all :) 19:49:52 thanks everyone 19:49:53 ..thanks 19:50:00 Thanks. 19:50:03 bye 19:50:06 is this going to change the time? 19:50:07 #endmeeting