18:00:02 <cp16net> #startmeeting trove
18:00:03 <openstack> Meeting started Wed Oct 14 18:00:02 2015 UTC and is due to finish in 60 minutes.  The chair is cp16net. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:05 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:00:07 <openstack> The meeting name has been set to 'trove'
18:00:18 <cp16net> #link https://wiki.openstack.org/wiki/Meetings/TroveMeeting
18:00:36 <amrith> .
18:00:37 <cp16net> #topic roll call
18:00:39 <amrith> ./
18:00:45 <cp16net> howdy yall
18:00:51 <amrith> howdy cp16net
18:00:52 <dougshelley66> o/
18:00:54 <peterstac> o?
18:01:13 <vkmc> o/
18:01:24 <SlickNik> hey there trove folks!
18:02:24 <cp16net> #topic Trove pulse update
18:02:32 <cp16net> #link https://etherpad.openstack.org/p/trove-pulse-update
18:02:43 <schang> o/
18:02:50 <edmondk> o/
18:03:06 <cp16net> so i expanded what peterstac did last time
18:03:17 <cp16net> #link http://bit.ly/1VQyg00
18:03:23 <danritchie> o/
18:03:34 <cp16net> let me know if you cant see the graphs
18:03:47 <amrith> looks good, am able to see them.
18:04:40 <cp16net> cool
18:04:50 <SlickNik> Can see them here too — nice work!
18:04:51 <mvandijk> ./
18:05:36 <cp16net> we are trending up on the reviews in the last couple weeks
18:05:51 <atomic77> o/
18:06:12 <cp16net> i think it looks pretty cool
18:06:34 <vgnbkr> o/
18:06:38 <cp16net> if ther are suggestions for other stats let me know
18:07:12 <peterstac> cp16net, I just noticed that the timeline on the Total Reviews graph seems to be backwards
18:07:42 <cp16net> hmm yeah i didnt realize that
18:07:48 <cp16net> i'll see if i can fix that
18:07:54 <peterstac> All the others seem fine
18:07:57 <cp16net> probably just a setting of the graph
18:08:04 <peterstac> ok, no biggie, looks great!
18:08:09 <cp16net> ok so then i take back my statement of trendingup
18:08:11 <cp16net> :-P
18:08:26 <amrith> I thought I was missing something so didn't want to say anything ;)
18:08:27 <cp16net> pretty flat line since the milestone
18:08:49 <cp16net> #action cp16net fix the timeline on total reviews graph
18:08:51 <amrith> open reviews however is trending up ...
18:09:00 <cp16net> yep
18:09:34 <cp16net> ok anything else there?
18:10:22 <cp16net> #topic action items from last week
18:11:17 <cp16net> i still ask about remote participation at the summit
18:11:43 <cp16net> #action cp16net check on remote participation at summit
18:11:53 <cp16net> i'll make sure i have that this week
18:12:13 <cp16net> amrith: double checked your tickets :-P
18:12:21 <edmondk> I also still would like to have some type of audio/video meeting like we talked about in sunnyvale
18:12:33 <edmondk> Would be helpful for some of the larger int tests review etc
18:12:41 <edmondk> and some of the blueprints
18:12:46 <amrith> cp16net, my tickets are good.
18:13:52 <cp16net> edmondk: we talked about replacing this meeting with a google chat or soemthing similar
18:14:18 <cp16net> edmondk: but i think even using something like that for focusing on reviewing large features would be great
18:14:30 <amrith> clarification please ... this meeting as in the trove weekly meeting?
18:14:53 <cp16net> amrith: yes thats what i thought we were talking about at the midcycle
18:15:06 <amrith> I believe that it was somethng else
18:15:12 <amrith> if I recall correctly it was for summit
18:15:27 <amrith> and as far as a openstack project is concerned, you have to use IRC, I think ....
18:15:33 <amrith> isn't that part of the "openstack way".
18:16:02 <edmondk> we can continue to use IRC, but at times I would like do what we did at mid cycle and go through reviews from the person who commited
18:16:03 <cp16net> i saw a cinder meeting that took place on google hangouts that was recorded
18:16:21 <edmondk> For example: peter going through this https://review.openstack.org/#/c/234461/ for everyone would be a good example
18:16:29 <cp16net> i personally like the weekly meetings on irc
18:16:43 <edmondk> we would still have these this is something extra
18:16:50 <amrith> I like extras
18:16:54 <edmondk> lol
18:16:58 <cp16net> but setting up another meeting to go over reviews would be good
18:17:08 <cp16net> especially big reviews
18:17:12 <amrith> dougshelley66 loves meetings
18:17:30 <edmondk> it doesn't have to be a normal cadence for reviews that are large and have been idle would be good to set aside some time and meet in google hangouts
18:17:42 <edmondk> and discuss through it
18:17:44 <cp16net> i agree edmondk
18:17:50 <edmondk> if anything it forces us to look at the review at that time
18:17:53 <edmondk> without distraction
18:18:33 <cp16net> edmondk: want to put together a meeting to look at that review?
18:18:51 <edmondk> sure
18:19:10 <cp16net> that would be great
18:19:20 <amrith> sounds great
18:19:24 <amrith> let's dry run it ...
18:19:27 <cp16net> #action edmondk setup hangout meeting or something to look over https://review.openstack.org/#/c/234461/
18:19:31 <cp16net> yeah
18:19:38 <peterstac> edmondk, well, we should probably do the spec first :)
18:19:45 <peterstac> (or at the same time)
18:19:45 <edmondk> yeah
18:19:54 <cp16net> same time would be good as a refresher
18:20:04 <peterstac> yep, I'm good with that
18:20:12 <edmondk> since you have both it would be good to talk through it
18:20:27 <cp16net> ok so i've started looking over the blueprints we have and still need to get through them
18:20:50 <cp16net> i'll continue on this today
18:21:00 <cp16net> #action cp16net priotitize blueprints for mitaka
18:21:21 <cp16net> vkmc create an etherpad with the concerns raised with the tenant isolation solution for the trove deployment concern
18:21:40 <cp16net> vkmc: any headway on this?
18:21:59 <vkmc> cp16net, not really
18:22:03 <cp16net> i dont recall seeing a link
18:22:03 <vkmc> sorry about that
18:22:10 <cp16net> ok no worries
18:22:16 <vkmc> I got some useful information from amrith and dougshelley66 on that regard
18:22:35 <amrith> vkmc, maybe I can submit the stuff to the etherpad ;)
18:22:36 <vkmc> so putting that information instead of concerns only would be probably better :)
18:22:59 <vkmc> let's do that now
18:23:22 <vkmc> #link https://etherpad.openstack.org/p/trove-guestagent-security
18:23:31 <cp16net> excellent
18:23:43 <amrith> sounds good, I have stuff to put in it ;)
18:24:23 <cp16net> ok the last action item i see is adding item we would like from oslo.messaging and/or oslo.*
18:24:39 <amrith> yes
18:24:45 <amrith> I have two things for that
18:24:49 <amrith> and I've submitted them
18:24:59 <amrith> also, there was an oslo survey that went out today
18:25:05 <amrith> people should consider filling that
18:25:15 <amrith> if you don't have a link, check your openstack-dev mailing list ;)
18:25:33 <amrith> #link https://www.surveymonkey.com/r/QKMVDG6
18:25:49 <cp16net> great
18:26:03 <amrith> In parallel, I've made some requests of oslo
18:26:12 * amrith scampers to find links
18:26:21 <pmackinn> scampers?
18:26:39 <amrith> https://bugs.launchpad.net/oslo.messaging/+bug/1504525
18:26:39 <openstack> Launchpad bug 1504525 in oslo.messaging "oslo messaging should provide a mechansim to generate a completely encrypted channel" [Undecided,New] - Assigned to Amrith (amrith)
18:26:56 <amrith> http://www.merriam-webster.com/dictionary/scampers
18:27:23 <amrith> also a couple of conversations about oslo.messaging exposing a user and ACL API
18:28:12 <cp16net> cool that could be helpful for the security issues that were brought up
18:28:45 <amrith> cp16net, I had made a presentation which would address this "security concern"
18:28:54 <amrith> I'm going to share that as a blogpost or something
18:29:03 <amrith> I'll share a link on mailing list as well
18:29:13 <cp16net> nice yeah that would be a great idea
18:29:27 <cp16net> ok then i think that wrapps up the actions
18:29:45 <cp16net> #topic Mitaka Summit Sessions
18:29:57 <cp16net> #link https://etherpad.openstack.org/p/mitaka-trove-summit
18:30:14 <cp16net> we've had alot of great ideas here
18:31:35 <cp16net> just a reminder to add topics that we should think about for the summit
18:32:11 <cp16net> i added a few other things to be bottom in Other Topics
18:33:32 <cp16net> #topic Mitaka Mid-Cycle
18:34:18 <cp16net> we've been talking about having the next midcycle in raleigh NC
18:34:25 <pmackinn> http://bit.ly/1LMvFcE
18:34:36 <cp16net> lol
18:34:41 <pmackinn> you're all welcome...except for amrith
18:34:52 <dougshelley66> but we need his credit card
18:34:59 <pmackinn> ah good point
18:35:13 <cp16net> pmackinn: has held the dates of Feb 9-11 2016
18:35:13 <amrith> pmackinn, I promise to bring your glasses
18:35:27 <pmackinn> amrith, come on down!
18:35:28 <amrith> or maybe SlickNik has them, not sure.
18:36:06 <cp16net> this should be far enough ahead and the dates are tues-thurs
18:36:24 <vkmc> when mid-cycle should happen?
18:36:47 <SlickNik> I'm good with Feb 9-11 — I'm not sure I have pmackinn's glasses though :)
18:37:15 <amrith> pmackinn, I'm good with 2/9-2/11 and SlickNik may not have your glasses ;)
18:37:27 <cp16net> vkmc: are you asking if this is a reasonable date to hold a midcycle?
18:37:37 <amrith> maybe cp16net, edmondk or shayneburgess. not sure who I gave them to.
18:37:37 <pmackinn> there are two hotels adjacent: full Marriott or full Sheraton. preference?
18:38:40 <vkmc> cp16net, nope, just asking when is generally midcycle happens :)
18:38:49 <amrith> No intercontinental, ritz, four seasons or  waldorf astoria class hotel ;)
18:39:11 <amrith> vkmc, usually we've been holding them between summits
18:39:21 <amrith> we've also been trying to give people a lot of notice
18:39:26 <amrith> so they can plan around these dates.
18:39:26 <cp16net> vkmc: generally its been about a month or 2 before the final release cut
18:39:38 <vkmc> well, looking at the roadmap, it should happen between M-2 and M-3
18:39:58 <amrith> as we found in the last situation, having it sooner is better.
18:40:01 <cp16net> i think this last one was too close to the final release which had us rushing patches
18:40:14 <amrith> having it between m2 and m3 would have us in more of a rush than we did this time around
18:40:18 <cp16net> #link https://wiki.openstack.org/wiki/Mitaka_Release_Schedule
18:40:38 <cp16net> yeah i think this is a good time to have it
18:40:47 <vkmc> https://wiki.openstack.org/wiki/Mitaka_Release_Schedule
18:40:49 <vkmc> oh there
18:40:49 <vkmc> hehe
18:40:53 <cp16net> :-P{
18:40:55 <amrith> and, fyi, 2/9 to 2/11 is between m2 and m3
18:41:02 <vkmc> so February, cool
18:41:13 <dougshelley66> exactly
18:41:15 <cp16net> yea
18:41:33 <dougshelley66> hopefully Ralleigh won't be so cool
18:41:38 <dougshelley66> in February
18:41:55 <cp16net> alright so it doesnt sound liek there are any issues with the dates
18:42:20 <cp16net> lets move forward with them then
18:42:22 <amrith> thanks for setting this up pmackinn and thx to RedHat (one word) for sponsoring
18:42:32 <pmackinn> Red Hat, dammit
18:42:33 <cp16net> btw thanks pmackinn and redhat for hosting :)
18:42:38 <pmackinn> Red Hat, dammit
18:42:57 <dougshelley66> RedHat, RedHat, RedHat
18:42:59 <cp16net> :)
18:43:04 <pmackinn> aaarrrrgggh
18:43:09 <amrith> Ubuntu is one word.
18:43:34 <cp16net> alright moving on
18:43:49 <cp16net> #topic gate issues with tox tests
18:43:53 <amrith> #link https://tctechcrunch2011.files.wordpress.com/2014/04/redhat_hat.jpg
18:43:59 <amrith> yes, I'm looking into tox issues
18:44:10 <amrith> at least, one that I noticed starting yesterday afternoon
18:44:12 <cp16net> so it looks like we have an issue with the fake tests starting
18:44:15 <amrith> for those who don't know about it yet
18:44:22 <amrith> if you run tox -e py27 ... it hangs
18:44:35 <amrith> the issue is that there is something in the event_simulator that is getting hosed
18:45:07 <amrith> see https://gist.github.com/amrith/6d06f9530e49dedee6cd
18:45:16 <cp16net> i'm wondering if there was a libarry that was updated that is casuing the issue
18:45:19 <cp16net> not sure atm
18:45:23 <amrith> ditto
18:45:32 <amrith> I'm concerned by the error jsut before this hang which reads
18:45:33 <amrith> self.dispatcher)
18:45:42 <amrith> self.dispatcher)
18:45:43 <peterstac> do we still need to run the fake tests?
18:45:48 <cp16net> because there was no changes to the tests that should ahve caused this that i'm aware of
18:45:53 <peterstac> would it make sense just to diable them?
18:46:02 <peterstac> s/diable/disable/
18:46:19 <amrith> error: /opt/stack/trove/.tox/py27/local/lib/python2.7/site-packages/oslo_messaging/server.py:141: RuntimeWarning: It is highly recommended that when eventlet is used that the ['thread'] modules are monkey patched when using the 'oslo.messaging eventlet executor' (to avoid spurious or unexpected lock-ups and/or hangs)
18:46:24 <cp16net> peterstac: we could but there is a benifit to running them
18:46:26 <amrith> I was chasing this down
18:46:36 <amrith> if someone has a venv where this problem doesn't occur
18:46:39 <amrith> please preserve it
18:46:46 <amrith> I accidentally blew mine away
18:47:05 <cp16net> and they also are part of validating the request/repsonse examples
18:47:05 <amrith> peterstac, I believe you have one of these
18:47:20 <peterstac> cp16net, please enlighten ;)  (I always ignore the fake output ...)
18:48:07 <cp16net> it can be usful to test the api before running the 20 min long test
18:48:11 <peterstac> amrith, I do have an env where py27 works, but it's my dev one - don't want to muck with it much
18:48:31 <amrith> please save it
18:48:49 <peterstac> cp16net, maybe it should be a separate test then (not run with the unittests)
18:49:35 <cp16net> so in short this looks like its affect the gate so we need to resolve this issue
18:49:38 <peterstac> amrith, will do
18:50:00 <cp16net> thanks for looking into this
18:50:11 <amrith> cp16net, peterstac does anyone really understand event_simulator.py?
18:50:29 <cp16net> i have a little understanding of it
18:50:37 <peterstac> amrith, not me
18:50:40 <amrith> ok, maybe we can chat offline
18:50:44 <cp16net> we can chat about what is does
18:51:05 <cp16net> we can chat about it in the chan after
18:51:18 <cp16net> #topic open discussion
18:51:26 <cp16net> anyone have anything for this?
18:52:15 <imandhan> So does that error mean that we can't test till it's fixed? I had been getting the error but couldn't figure out why exactly and what I messed up.
18:52:47 <amrith> heads up guys, abramley just pointed me to https://review.openstack.org/#/c/233854
18:52:53 <cp16net> means that the tox tests dont pass in the gate because this fails and we can merge anything now
18:52:56 <peterstac> imandhan, well, running 'tox -epy27' will appear to hang (while it writes tons into the log file)
18:53:14 <amrith> and for trove https://review.openstack.org/#/c/231242
18:53:17 <amrith> thanks abramley
18:53:23 <imandhan> yup peterstac that's what was happening
18:53:48 <amrith> so we should be able to test this by not using oslo.messaging 2.6.0
18:53:49 <cp16net> awesome
18:53:56 <amrith> peterstac, is that a difference between your two venvs?
18:54:37 <cp16net> ok so one other thing i had was to update the cross project liasons
18:54:44 <peterstac> amrith, the latest bot skips that version https://review.openstack.org/#/c/231242/6/requirements.txt,cm
18:54:51 <peterstac> but the test still fails
18:54:59 <cp16net> #link https://wiki.openstack.org/wiki/CrossProjectLiaisons
18:55:16 <dims> amrith: you may be hitting the same one that ceilometer hit - https://bugs.launchpad.net/oslo.messaging/+bug/1505730
18:55:16 <openstack> Launchpad bug 1505730 in Ceilometer "oslo.messaging 2.6.1 breaks ceilometer unit tests" [Undecided,New]
18:55:17 <amrith> cp16net, please sign me up as oslo liaison
18:55:28 <cp16net> amrith: you are already there :) thanks
18:55:36 <amrith> dims ... looks similar
18:55:42 <amrith> my broken venv has 2.6.1
18:55:49 <amrith> and dougshelley66's good environment has 2.5.0
18:55:54 <dims> amrith: downgrade to 2.5.0 and it would work
18:55:56 <amrith> updating my requirements.txt file and will test
18:56:02 <dims> amrith: y, patch in progress
18:57:10 <cp16net> thanks dims for the info
18:57:46 <cp16net> last thing i'd like to ask everyone is if everyone will be available next week for the meeting?
18:57:56 <amrith> ./
18:57:59 <vkmc> o/
18:58:24 <pmackinn> o/
18:58:32 <cp16net> its the week before the summit so we can bring up last minute things before meeting up there
18:58:39 <peterstac> o/
18:58:49 <SlickNik> o/
18:58:50 <atomic77> o/
18:58:58 <amrith> that's right, cp16net is going to tokyo a week ahead ;)
18:59:11 <cp16net> heh i wish
18:59:20 <cp16net> alright time it about up
18:59:30 <vgnbkr> o/
18:59:31 <cp16net> thanks everyone!
18:59:39 <cp16net> #endmeeting