20:01:21 <nikhil_k> #startmeeting Glance
20:01:23 <openstack> Meeting started Thu Oct 16 20:01:21 2014 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:01:24 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
20:01:26 <openstack> The meeting name has been set to 'glance'
20:01:30 <ativelkov> o/
20:01:30 <kragniz> o/
20:01:34 <TravT> o/
20:01:39 <jokke_> o/
20:01:56 <TravT> \o
20:02:03 <nikhil_k> Brian may be missing today's meeting
20:02:11 <flwang> o/
20:02:13 <nikhil_k> let's give it another min
20:02:16 <zhiyan> o/
20:02:27 <nikhil_k> #link https://etherpad.openstack.org/p/glance-team-meeting-agenda
20:02:52 <esheffield> o/
20:03:01 <nikhil_k> okay!
20:03:16 <nikhil_k> #topic updates
20:03:32 <nikhil_k> #link  https://review.openstack.org/#/c/126974/
20:03:42 <nikhil_k> so, we got some feedback on that already I sup
20:04:01 <nikhil_k> however, let's keep in mind to add tests to tempest for all of our new additions
20:04:08 <nikhil_k> features, bugs .. stuff
20:04:23 <nikhil_k> we go RC3 for glance
20:04:32 <nikhil_k> for covering out last min bugs and such
20:04:46 <nikhil_k> a config issue conflicting with documentation was major reason for that
20:05:04 <nikhil_k> so, what we do not have in Juno is
20:05:07 <nikhil_k> #link https://bugs.launchpad.net/glance/+bugs?field.tag=juno-rc-potential
20:05:26 <nikhil_k> for varied reasons
20:05:37 <nikhil_k> next up!
20:05:43 <nikhil_k> Please please please vote!
20:05:50 <nikhil_k> for the TC elections going on
20:06:00 <nikhil_k> Believe the deadline is Friday
20:06:03 <flwang> I have voted :)
20:06:17 <nikhil_k> next is
20:06:28 <jokke_> yeah it's fri by 1300 utc
20:06:29 <nikhil_k> some feedback from the ptl sync meeting
20:06:41 <nikhil_k> agood news for all
20:06:54 <nikhil_k> we will have a *full* pypi mirrow on the gates
20:07:09 <jokke_> \\o \o/ o// o/7
20:07:11 <kragniz> wooo!
20:07:13 <nikhil_k> so,not only the req. but also the dep. will be mirrored
20:07:39 <flwang> awesome
20:07:41 <ativelkov> cool
20:07:48 <TravT> so, I hope this means faster tests and less random failures?
20:07:53 <nikhil_k> :)
20:07:56 <nikhil_k> hope so
20:08:05 <nikhil_k> there is no fixed date for the imlementation yet
20:08:06 <jokke_> TravT: if the mirror is stable ;)
20:08:24 <TravT> jokke_: sshhh.... it'll hear you.
20:08:24 <nikhil_k> I'll rush through here
20:08:38 <nikhil_k> tentative deadline for confirming summit topics is Oct 28th
20:08:55 <nikhil_k> however, for Glance we'd confortable doing it well before
20:09:01 <nikhil_k> is my understanding at this point
20:09:05 <nikhil_k> so the email out to ML
20:09:12 <nikhil_k> if anyone has a link to it :)
20:09:49 <nikhil_k> so, if you think your topic needs discussion or further discussion in the summit please do add
20:09:54 <nikhil_k> *however*
20:10:08 <nikhil_k> we've limited spots
20:10:14 <nikhil_k> so please do keep that in mind
20:10:35 <nikhil_k> again
20:10:37 <nikhil_k> #link https://etherpad.openstack.org/p/kilo-glance-summit-topics
20:10:47 <jokke_> we have one meeting before the deadline ... let's agree what we push through week now based on what is proposed on the etherpad?
20:10:49 <nikhil_k> we may be missing flavio here
20:11:31 <nikhil_k> jokke_: ohk yes, good point
20:11:49 <nikhil_k> let's discuss the finalizing of topics in just a bit
20:12:15 <nikhil_k> we prolly should have release of store and client before the summit
20:12:32 <nikhil_k> if someone is affected by that please let me know and I will try to do it sooner than later
20:12:42 <nikhil_k> else please expect delays as we fix stuff
20:13:01 <nikhil_k> #topic Virtual Mini Summit
20:13:09 <nikhil_k> #link https://etherpad.openstack.org/p/kilo-glance-virtual-mini-summit
20:13:16 <nikhil_k> #link http://doodle.com/e42y2xvrhycqbmu5
20:13:30 <nikhil_k> please try to go through the etherpad and do give me your feedback
20:13:48 <nikhil_k> if the dates do not work please let me know too
20:14:07 <nikhil_k> will give a min here to let everyone digest that link
20:14:12 <nikhil_k> and if there are questions
20:14:34 <flwang> nikhil_k: what's the time of the virtual summit?
20:14:40 <nikhil_k> TBD
20:14:49 <TravT> is vidyo, the new rackspace service you were mentioning?
20:14:52 <flwang> nikhil_k: ok
20:14:55 <nikhil_k> so, the in doodle I'd ask you to put your TZ  in
20:15:03 <flwang> got
20:15:03 <nikhil_k> however, the dates are relative to UTC
20:15:21 <jokke_> nikhil_k: the timeslots for those two days?
20:15:34 <nikhil_k> based on interest and availability
20:15:47 <nikhil_k> kind of a scheduling issue here hence, need feedback soon on that
20:16:15 <jokke_> ok, fair enough .. I'll put myself up there, but can't commit before I have the times
20:16:24 <nikhil_k> we'd prefer to keep things closer to business times in UTC
20:16:48 <nikhil_k> so, the possibility of the mini summit ranging over 2 days kind of seems more feasible
20:16:57 <nikhil_k> just to include everyone in the loop
20:17:15 <nikhil_k> 3-4 sessions per day
20:17:46 <nikhil_k> should we move on if there are no more questions?
20:18:14 <nikhil_k> #topic Introductions Part 2
20:18:19 <TravT> is vidyo better than google hangouts?
20:18:24 <nikhil_k> much
20:18:33 <ativelkov> hangouts has a limit for the number of attendees
20:18:55 <nikhil_k> vidyo here at the Rack can take upto 50 I guess
20:19:15 <jokke_> I think the standard hangout is only like 10 people
20:19:19 <nikhil_k> we'll have to give it a try :)
20:19:24 <jokke_> so that vidyo sounds good
20:19:39 <TravT> ok.
20:19:42 <jokke_> nikhil_k: did you check the recording possibility?
20:19:50 <nikhil_k> jokke_: not yet :)
20:20:03 <zhiyan> nikhil_k: what about i's quality for non-US user? like Asia pepople. any feedback for that?
20:20:28 <nikhil_k> zhiyan: good question, let's give it a dry run sometime soon before the event
20:20:46 <jokke_> nikhil_k, zhiyan can we have small 15min test run like tomorrow on that to check the region quality?
20:20:51 <zhiyan> nikhil_k: will be great. ping me when you have chance.
20:20:54 <zhiyan> nikhil_k: thanks
20:20:59 <nikhil_k> jokke_: zhiyan that sounds good
20:21:16 <jokke_> I'm in Europe so we have all majors covered
20:21:17 <nikhil_k> 14UTC ?
20:21:18 <nikhil_k> TravT: ?
20:21:22 <jokke_> sounds good to me
20:21:47 <nikhil_k> feel like we's span the globe as much as possible :)
20:21:54 <TravT> Yeah, i'm available.
20:22:03 <nikhil_k> awesome
20:22:19 <nikhil_k> intro volunteers please !
20:22:27 <nikhil_k> :)
20:22:33 <jokke_> kragniz: can you join from office to check that it works within HP firewall?
20:22:45 <ativelkov> Didn't we agree to update a wiki page with the team members info?
20:22:45 <kragniz> jokke_: yeah, no problem
20:23:04 <jokke_> ativelkov: I thought we did
20:23:20 <nikhil_k> ativelkov: that's a good idea, who has action item on that..?
20:23:41 <nikhil_k> we can do that later too
20:24:03 <nikhil_k> intros!
20:24:14 <kragniz> I did an introduction last week!
20:24:17 <nikhil_k> who's new?
20:24:26 <nikhil_k> nice. thanks kragniz
20:24:46 <nikhil_k> do I allocate slots for people? :)
20:25:14 <nikhil_k> aight, this seems to be failing bad
20:25:22 <kragniz> nikhil_k: I think you're going to have to, if you want people to give them!
20:25:30 <jokke_> I think we don't have other news than kragniz ;)
20:25:37 <nikhil_k> oldies then
20:25:40 <nikhil_k> how about you?
20:25:42 <TravT> we have some new people in Intel, but they can't usually make the meeting
20:25:45 <jokke_> he is the new new guy! ;)
20:26:00 <nikhil_k> ok TravT , can you please voluntter?
20:26:14 <TravT> ok.
20:26:18 <nikhil_k> give us some inspiration
20:26:28 <TravT> I'm Travis Tripp from HP.
20:26:39 <TravT> been working on cloud / openstack related projects for over 3 years
20:26:59 <TravT> somehow finally got to start working upstream starting this past February
20:27:02 <TravT> and I LOVE IT!
20:27:07 <nikhil_k> woot!
20:27:10 <kragniz> TravT: \o/
20:27:20 <zhiyan> Welcome TravT!
20:27:23 <ativelkov> that is inspiring indeed)
20:27:28 <nikhil_k> welcome :)
20:27:33 <nikhil_k> agree
20:27:43 <nikhil_k> ativelkov: next ?
20:27:50 <ativelkov> ok )
20:27:59 <ativelkov> I am Alexander Tivelkov from Mirantis
20:28:18 <ativelkov> HAve been with Openstack for about year and a half
20:28:36 <ativelkov> Core contributor and ex-PTL (if they have PTLs for non-incubated projects) for Murano
20:29:00 <ativelkov> Have been interested in Catalog-related stuff for openstack since february
20:29:15 <ativelkov> Currently primary working on Artifact initiative.
20:29:42 <ativelkov> Want to make Glance more and more important for all the projects across the eco-system, not only Nova
20:30:13 <ativelkov> That's it :)
20:30:15 <nikhil_k> awesome!
20:30:39 <TravT> +1 ativelkov
20:30:42 <nikhil_k> That was great!
20:30:45 <zhiyan> Welcome ativelkov! Let's make Artifact stuff get landing in K cycle.
20:30:52 <nikhil_k> welcome :)
20:31:03 <nikhil_k> or welcome again :)
20:31:07 <nikhil_k> for both
20:31:27 <nikhil_k> jokke_: please don't miss the next meeting ;)
20:31:42 <nikhil_k> #topic Planning, Priorotization, Focus, etc.
20:31:42 <jokke_> ;)
20:32:01 <nikhil_k> does anyone feel blocked by me?
20:32:12 <TravT> yeah, can you move to the left a litte?
20:32:18 <nikhil_k> lol
20:32:20 <nikhil_k> sure
20:32:23 <TravT> thanks
20:32:23 <nikhil_k> there ya go
20:32:36 <kragniz> lol
20:32:36 <jokke_> no no no, our left ;)
20:32:52 <nikhil_k> I did, well let me try the other side now
20:32:58 <hemanthm> you're blocking me now, to the right please
20:33:00 <TravT> no, now I can't see the TV
20:33:24 <nikhil_k> :)
20:33:47 <nikhil_k> anyways, that was just a question for following up on office hours
20:33:52 <nikhil_k> which may be answered
20:34:03 <nikhil_k> couple of months down the line too
20:34:04 <ativelkov> So, we have J officially released, should we start with merging what is tagged  juno-backport-potential?
20:34:16 <nikhil_k> just keep in mind before yelling at me, please please :)
20:34:32 <TravT> yeah, what is the meaning of RC3 if OpenStack was released today?
20:34:45 <jokke_> TravT: RC3 was out, what 2 days
20:34:54 <nikhil_k> RC3 is released, no?
20:34:59 <nikhil_k> yes
20:35:01 <jokke_> just a tarball to give out if something obvious blows up
20:35:06 <kragniz> rc3 is tagged
20:35:15 <TravT> ok... just saw that earlier in the meeting and was lost
20:35:15 <nikhil_k> so RC3 is just for fixing critical bugs
20:35:16 <ativelkov> Ah, I saw official J release notice in ML
20:35:28 <ativelkov> wasn't it final?
20:35:31 <jokke_> ativelkov: yeah that's today
20:35:33 <nikhil_k> yes, it is
20:35:45 <nikhil_k> 2014.2.final
20:35:58 <jokke_> so proposed/juno should be now stable/juno
20:36:00 <nikhil_k> or 2014.2.0 final
20:36:08 <nikhil_k> yeah
20:36:23 <nikhil_k> however, we may not be able to get all sorts of bugs in stable
20:36:34 <jokke_> and we shouldn't
20:36:37 <nikhil_k> there are restrictions for post-release bugs
20:37:12 <kragniz> nikhil_k: what are they, out of interest?
20:37:13 <zhiyan> cross fingers
20:37:21 <jokke_> should be really just security/stability?
20:37:25 <nikhil_k> kragniz: what do you mean?
20:37:29 <nikhil_k> jokke_: yes
20:37:36 <kragniz> jokke_: okay, that makes sense
20:37:52 <nikhil_k> no config changes and anything that breaks the api
20:37:57 <TravT> what is the criteria for backporting to stable?
20:37:57 <kragniz> cool
20:38:12 <jokke_> nor really "we didn't have time to implement this by release"
20:38:15 <nikhil_k> TravT: I think they are laid out in wiki somewhere
20:38:20 <nikhil_k> there are finer lines though
20:38:34 <nikhil_k> so, basically propose rationally and see if it works
20:38:47 <TravT> i probably have one to submit.
20:38:52 <nikhil_k> ok
20:38:59 <jokke_> and remember that it needs to be merged on master before it can land
20:39:08 <TravT> our good friends in Intel are doing further checks.
20:39:21 <nikhil_k> awesome
20:39:26 <nikhil_k> checking is gooooood
20:39:57 <nikhil_k> anyways, we'd a last minute run this release
20:40:08 <nikhil_k> we'd prolly try to avoid that next one
20:40:22 <nikhil_k> I heard in nova they have a informal freeze
20:40:27 <nikhil_k> from kilo-2
20:40:39 <jokke_> nikhil_k: but they are beast size wise as well
20:40:45 <jokke_> same as neutron
20:40:45 <nikhil_k> yeah
20:40:52 <nikhil_k> for glance we can do kilo2.5
20:40:56 <jokke_> they need that extra time to stabilize
20:41:02 <nikhil_k> or even 3
20:41:13 <nikhil_k> we'll know a couple months down the line
20:41:25 <nikhil_k> really we just need more stuff going through gate
20:41:27 <nikhil_k> faster
20:41:33 <jokke_> +1
20:41:36 <kragniz> nikhil_k: wasn't freeze at j3 planned for this release cycle?
20:41:41 <TravT> i think what we really missed was formally targetting bugs for a milestone.
20:41:45 <nikhil_k> and zhiyan should not be the one doing more than half of that
20:41:55 <kragniz> nikhil_k: I heard people talking about it, but it didn't seem to happen in glance
20:42:00 <nikhil_k> TravT: yes, that too
20:42:11 <nikhil_k> TravT: I'm a bit hesistent about the reviews as well
20:42:20 <nikhil_k> we'd a really linient review cycle for glance
20:42:46 <nikhil_k> usually a simplest of patch takes at least 2-3 PS before landing (with changes)
20:43:12 <zhiyan> nikhil_k: frankly, imo team need pay more efforts on review instead of just push code up
20:43:25 <nikhil_k> zhiyan: agree
20:43:30 <kragniz> zhiyan: +1
20:43:31 <zhiyan> nikhil_k: we have a lot of dead-end MPs there
20:43:38 <nikhil_k> yes
20:43:43 <jokke_> nikhil_k: also it seems that more simple the change is the more sloppy it also is regarding the styling etc.
20:43:56 <jokke_> zhiyan: +1
20:44:19 <nikhil_k> kragniz: about the freeze, yeah .. I'm not sure, there were last minute changes
20:44:25 <zhiyan> so probably I think in K, we can freeze feature MP pushup in K-2.5 (if have), and focus on review them more
20:44:53 <nikhil_k> zhiyan: absolutely
20:44:53 <ativelkov> As they say, 10 lines of code = 12 comments, 300 lines of code = +1, LGTM :)
20:45:11 <nikhil_k> ativelkov: right on!
20:45:12 <kragniz> is k2.5 a thing, or does that mean half way between k2 and k3?
20:45:25 <jokke_> ativelkov: and quite often for good reason ;)
20:45:32 <kragniz> ativelkov: heh
20:45:32 <nikhil_k> kragniz: ideally, we'd have specs approved by k2
20:45:33 <jokke_> ativelkov: not good trend 'though
20:45:45 <zhiyan> jokke_: for those tiny change, e.g. just one line, or doc update/sync, imho, we can just +2/A directly. and if have issue, we can push a revert commit soon later
20:45:48 <jokke_> nikhil_k: can we just do spec freeze at k2?
20:46:05 <nikhil_k> zhiyan: I'd not encourage to have just 1 +2
20:46:10 <nikhil_k> *NOT*
20:46:13 <nikhil_k> please
20:46:14 <kragniz> zhiyan: that has the risk of breaking the gate, right?
20:46:20 <nikhil_k> let's stick to 2 +2s before +A
20:46:22 <nikhil_k> unless
20:46:44 <jokke_> zhiyan: I'm not that worried about those ... I'm more worried about the ones where even the commiter has not reviewd the change one pushed through with simple shell script
20:46:55 <nikhil_k> *unless* we've certain conditions on the patch like a change needs to land before a certain date and no one is available for review
20:47:01 <kragniz> jokke_: I think I know who you're talking about ;)
20:47:21 <jokke_> kragniz: he's not the only one
20:47:23 <nikhil_k> jokke_: so, good point
20:47:29 <nikhil_k> we need priorities here
20:47:44 <zhiyan> sorry just break from net
20:48:03 <nikhil_k> we'd ideally have a list of bugs/reviews to be done on priority
20:48:11 <nikhil_k> like the tiny changes which jokke_ was talking about
20:48:12 <zhiyan> kragniz: i don't think so, due to breaking gate will block Jenkins merge it.
20:48:22 <nikhil_k> such things add more pressure on the gate too
20:48:28 <nikhil_k> if more PS are uploaded and such
20:48:56 <zhiyan> nikhil_k: 2 more +2s for normal case, of course, I just like to speed up those doc change, or global-req syncup, something like that.
20:49:15 <TravT> yes, but better to get the simple changes pushed through early rather than piling up at the end of cycle when the gate is really backed up
20:49:15 <nikhil_k> zhiyan: yeah, simple doc changes are really good
20:49:30 <jokke_> nikhil_k: personally I'd like to see the bigger taking priority ... that 10 line change is way easier to rebase than the big one that has been sitting in the Q for a month
20:49:44 <nikhil_k> however, we'd careful about a doc change which could break things
20:49:58 <nikhil_k> like docs becoming inconsistent
20:50:08 <nikhil_k> and we need to rush through on the very last day of cycle
20:50:20 <jokke_> nikhil_k: I think there is difference of doc change and spelling correction here
20:50:33 <nikhil_k> jokke_: yes, priorities in general
20:50:39 <nikhil_k> not only smaller ones
20:50:45 <nikhil_k> a theme based approach
20:50:57 <nikhil_k> where we focus on a particular BP/bug for reivew
20:50:58 <TravT> it was so incredibly frustrating to be at the end of the cycle having to babysit a doc change through the 2 - 4 day merge at gate.
20:51:02 <jokke_> nikhil_k: I think zhiyan is talkin of just direct approving the spelling corrections, translations etc. which I do +1
20:51:07 <nikhil_k> get it done, merge it or -2 it .. move one
20:51:09 <nikhil_k> on*
20:51:19 <nikhil_k> jokke_: sure
20:51:35 <nikhil_k> TravT: yeah, that's the biggest worry here
20:51:52 <nikhil_k> ok, just to point out we've 10 mins left
20:51:55 <TravT> that's why i'm not opposed to pushing simple changes early in the cycle.
20:52:01 <TravT> even if lower priority.
20:52:05 <nikhil_k> and we cruised into our painpoints discussion too
20:52:09 <TravT> otherwise they'll get carried for multiple releases
20:52:09 <jokke_> TravT: Thanks for taking the time and effort doing that. I was really happy to see that Doc part of the metadef!!
20:52:24 <nikhil_k> TravT: yeah, thanks thanks thanks!
20:52:28 <nikhil_k> really appreciate that
20:52:42 <TravT> no worries
20:52:51 <nikhil_k> and thanks to rosmaita as well who has taken care of such changes for us in the past quite often!
20:53:05 <TravT> lakshmiS also worked on docs
20:53:15 <TravT> so he deserves extra credit
20:53:23 <jokke_> nikhil_k: what you had next? I think you need to have that priority discussion with the cores.
20:53:43 <nikhil_k> woot to lakshmiS!
20:54:05 <nikhil_k> jokke_: yes, I will try to do that once I'm authorized to
20:54:15 <nikhil_k> am still a proxy for Mark
20:54:37 <nikhil_k> but for somethings, I'm taking an excuse :)
20:54:51 <nikhil_k> #topic Open Discussion
20:54:53 <jokke_> nikhil_k: when's the transition ... I thought it was per release and we're officially on kilo now ;)
20:55:14 <zhiyan> nikhil_k: i have one
20:55:18 <nikhil_k> jokke_: believe, it's during or after the summit .. not 100% on that though
20:55:18 <jokke_> Logging!
20:55:20 <zhiyan> #link http://lists.openstack.org/pipermail/openstack-dev/2014-October/048597.html
20:55:24 <nikhil_k> jokke_: could be now really
20:55:25 <hemanthm> I have one too
20:55:32 <nikhil_k> FCFS
20:55:34 <nikhil_k> zhiyan: go
20:55:52 <nikhil_k> aight, how can we help on that zhiyan ?
20:56:12 <zhiyan> so folks, when/if you ok, please help review those changes asap, Doug proposed a worth point for projects
20:56:43 <ativelkov> do you have the list of patches somewhere?
20:56:46 <jokke_> Spam Doug to give deprecation period as it is expected from every other project ;)
20:56:48 <zhiyan> especially on second #PS, it contains a change for 'upstream' policy.py
20:57:05 <ativelkov> ah, got it
20:57:32 <nikhil_k> yes, please do test the policy change?
20:57:34 <zhiyan> i just proposed that change hours ago, so before comments/update for oslo team, we need to make sure that is what we need
20:57:58 <zhiyan> https://review.openstack.org/#/c/128881/
20:58:09 <zhiyan> for the upstream policy.py change
20:58:10 <nikhil_k> #link https://review.openstack.org/#/c/128881/
20:58:21 <nikhil_k> cool
20:58:29 <zhiyan> thanks team
20:58:37 <zhiyan> i'm done. hemanthm
20:58:38 <nikhil_k> next?
20:58:45 <hemanthm> guess its jokke_
20:58:48 * kragniz has one, too
20:58:53 <nikhil_k> jokke_: go go go
20:59:13 <jokke_> Logging: two changed have been hanging on rebase loop now 3 months
20:59:28 <nikhil_k> does anyone have links?
20:59:29 <jokke_> including change to i18n which is one of those Dougs painpoints
20:59:44 <jokke_> Glance refactoring logging https://blueprints.launchpad.net/glance/+spec/refactoring-glance-logging
20:59:46 <nikhil_k> let's approve that soon
20:59:47 <jokke_> https://review.openstack.org/#/c/116626/ another rebase
20:59:49 <jokke_> https://review.openstack.org/#/c/117204/ likewise
21:00:02 <nikhil_k> #link https://blueprints.launchpad.net/glance/+spec/refactoring-glance-logging
21:00:08 <nikhil_k> cool
21:00:12 <nikhil_k> we'r out of time!
21:00:19 <nikhil_k> #endmeeting