#openstack-meeting-alt log

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