16:00:50 <david-lyle> #startmeeting Horizon
16:00:50 <openstack> Meeting started Tue Sep 30 16:00:50 2014 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:51 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:53 <openstack> The meeting name has been set to 'horizon'
16:01:03 <david-lyle> Hello everyone
16:01:04 <gary-smith> hi
16:01:05 <rdopieralski> hi
16:01:09 <doug-fish> hello!
16:01:11 <hurgleburgler> hi
16:01:12 <jacalcat> Hi
16:01:15 <jgravel> hello
16:01:22 <amotoki> hi
16:01:26 <jomara> ahoy
16:01:30 <rbertram> hi
16:01:32 <TravT> o/
16:01:36 <bpokorny> Hi
16:01:43 <clu_> hello!
16:01:47 <Daisy> hi
16:01:58 <rhagarty_> hello
16:02:02 <pawelss> Hi
16:02:16 <david-lyle> We're in the final push for RC-1
16:02:31 <lcheng> hello
16:02:32 <woodm1979> HI!  (sorry late)
16:02:42 <EmilyW> howdy
16:02:51 <david-lyle> https://launchpad.net/horizon/+milestone/juno-rc1
16:02:53 <bradjones> hi
16:02:56 <david-lyle> 3 bugs left
16:03:01 <akrivoka> hello !
16:03:10 <david-lyle> once those are in, we'll cut RC1
16:03:23 <david-lyle> then master will open to Kilo development
16:03:58 <david-lyle> any other issues not tracked to RC1 that anyone feels should block release?
16:04:45 <david-lyle> I also owe some release notes, that I hope to be able to work on in the next day or two
16:05:07 <gary-smith> Possibly https://bugs.launchpad.net/horizon/+bug/1374931
16:05:26 <gary-smith> Launching instances from volume snapshots is broken
16:05:40 <rdopieralski> for some reason https://review.openstack.org/#/c/116583/ is not listed there :/
16:07:21 <david-lyle> gary-smith, why is the volume size 0?
16:07:39 <gary-smith> The field is hidden on the form
16:08:07 <david-lyle> gary-smith, if I read the bug right, it seems that's data coming from Cinder
16:08:22 <david-lyle> or are we setting it to 0 on creation?
16:08:34 <david-lyle> I'm confused
16:09:08 <gary-smith> Sorry, didn't identify whether cinder caused it or in the UI.
16:09:11 <amotoki> rdopieralski: I hope you file a bug so that we can track it.
16:09:31 <rdopieralski> amotoki: right! on it
16:09:58 <david-lyle> rdopieralski, I'm not sure I'm excited about a ~10K code rip on the day before release
16:10:21 <david-lyle> understanding that it's effectively just a move
16:10:55 <david-lyle> I suppose that's what we make RC2s to fix
16:12:16 <david-lyle> gary-smith, if it's a cinder issue, not much we can do about it at this point
16:12:33 <gary-smith> agreed. Let me drill down, and I'll update with findings
16:12:51 <david-lyle> if you confirm it's horizon, mark it as RC1
16:12:56 <gary-smith> will do
16:13:01 <david-lyle> gary-smith, thanks!
16:13:33 <david-lyle> any other bugs that need to be fixed in RC1?
16:14:17 <david-lyle> ping me if something comes up
16:14:46 <amotoki> I think core team should avoid +A before RC1 is cut.
16:15:17 <david-lyle> amotoki, regarding ?
16:15:35 <amotoki> david-lyle: ah... except RC1 targeted bugs.
16:15:52 <david-lyle> ok, yes. Good reminder
16:16:36 <david-lyle> Short agenda today
16:16:38 <david-lyle> https://wiki.openstack.org/wiki/Meetings/Horizon
16:16:56 <david-lyle> #topic Juno translations import ( Daisy )
16:17:04 <Daisy> Hi, I'm here
16:17:20 <Daisy> Shall I start?
16:17:27 <woodm1979> So, the first item is that jpich needs to apologize for being gone!  :-)
16:17:30 <david-lyle> Daisy, the floor's yours
16:17:38 <Daisy> I'm from translation team. Tranlation team started the horizon translation since F release. In every dev cycle, after string freeze, the translators will work on translation till the final openstack release. amotoki and jpich usually work together with us.
16:18:01 <Daisy> There are scripts to automatically syncronize between code repsoitory to translation tools. before RC1, the importing could be done automatically. After RC1, the master code will be openned for kilo and juno code will be switched to /juno branch. The automatica importing will be broken. We need manually syncronization after RC1. So after RC1 before RC2 is cut, we need a manually translation...
16:18:03 <Daisy> ...import, that will be the deadline for our transaltions work.
16:18:37 <Daisy> I'd like to understand when the final translation import will be, and who will help to take care of translation after RC1 is cut.
16:19:11 <david-lyle> Daisy, we hope to cut RC1 in the next couple of days
16:19:23 <david-lyle> then we'll open RC2 primarily for translations
16:19:38 <Daisy> That's great, david-lyle
16:19:44 <david-lyle> as soon as the translations are ready, we'll merge them
16:19:56 <Daisy> How many days do you think translators will have after RC1 is cut ?
16:20:07 * david-lyle checking on over release schedule
16:21:06 <david-lyle> Daisy looks like Juno release is targeted for the week of Oct 16
16:21:25 <david-lyle> certainly don't want to push to the last day if possible
16:21:35 <Daisy> sure, understandable.
16:22:12 <david-lyle> after more looking, looks like the 16th is the intended release data
16:22:14 <david-lyle> *dte
16:22:17 <amotoki> how about one week after RC1? possibly Oct 8 or 9. one week including the weekend is good enough to me.
16:22:31 <david-lyle> That works for me
16:22:32 <amotoki> *for translators.
16:22:43 <Daisy> I agreee 1 week is good.
16:22:57 <david-lyle> Let
16:23:00 <david-lyle> argh
16:23:05 <david-lyle> typing is hard
16:23:09 <david-lyle> let
16:23:20 <david-lyle> let's target the 9th then
16:23:49 <Daisy> ok. Then I will let our translators know. 9th will be their deadline to finish translations.
16:24:09 <david-lyle> Thank you Daisy
16:24:20 <Daisy> One more question, who will take care of translation synchronization after RC1 is cut ?
16:24:32 <Daisy> amotoki: will you take care of it ?
16:24:41 <amotoki> I can
16:24:50 <Daisy> Thank you, amotoki !
16:24:55 <david-lyle> Thanks amotoki
16:25:11 <amotoki> if i am not available, i will reach Daisy or jpich.
16:25:28 <Daisy> Sure, amotoki. I will be there if you are not available.
16:26:18 <david-lyle> #topic Open Discussion
16:26:53 <bpokorny> I've got a question about Tempest tests for Horizon
16:27:28 <bpokorny> It looks to me like there's only 1 tempest test for Horizon, which is a scenario test.
16:27:29 <david-lyle> bpokorny, ok
16:27:37 <david-lyle> yes
16:27:49 <david-lyle> that is all for right now
16:28:11 <bpokorny> ok.  And I've seen some posts on the mailing list indicating scenario tests will be deprecated
16:28:22 <bpokorny> In favor of the tempest client.
16:28:45 <david-lyle> bpokorny, do you have a link?
16:29:49 <bpokorny> david-lyle: I'll have to dig it up again..  I'll look for it and ping you later on, if that's ok.
16:30:02 <david-lyle> bpokorny, sure
16:30:13 <TravT> david-lyle: did you put out a new template for how we should structure new blueprints?
16:30:45 <david-lyle> I'm not sure what the tempest client involves but I'm concerned it wouldn't support Horizon very well
16:30:51 <david-lyle> will need to look into more
16:31:14 <bpokorny> david-lyle:  Yeah, I don't understand it well at this point either.
16:31:20 <david-lyle> TravT, yes, let me find the link again
16:31:34 <bpokorny> So I was surprised to see that info on the mailing list.
16:31:48 <david-lyle> https://blueprints.launchpad.net/horizon/+spec/template
16:31:54 <TravT> thanks!
16:32:12 <david-lyle> TravT, I still owe an example
16:32:34 <david-lyle> re: client side data loading/filtering/pagination/etc
16:32:50 <clu_> :) :)
16:32:56 <david-lyle> still trying to get to that this week
16:33:38 <david-lyle> but I believe all feedback on the template has been rolled in
16:34:03 <david-lyle> provide any additional feedback in the whiteboard section
16:34:25 <clu_> cool, we have an someone who has some good ideas we can share toward that bp :)
16:34:33 <TravT> for already existing blueprints, do they need to be rewritten in that format?
16:35:17 <TravT> certainly not a problem... just want to meet expectations!
16:35:19 <david-lyle> TravT, yes, to move forward in Kilo, I'd like to have them in the new format
16:35:46 <david-lyle> again, for certain areas N/A are acceptable where appropriate
16:35:58 <david-lyle> s/are/is/
16:36:32 <TravT> ok. sounds good.
16:37:30 <david-lyle> also a reminder for the summit
16:37:32 <david-lyle> https://etherpad.openstack.org/p/horizon-kilo-summit
16:37:52 <david-lyle> is the etherpad for session ideas and unscheduled session ideas
16:38:18 <david-lyle> we'll have 6 sheduled sessions and a half-day of unscheduled sessions
16:39:37 <TravT> we used etherpad for the glance mini summit.
16:39:53 <TravT> one of the suggestions coming out of it was to add the person who originally added the topic
16:40:13 <david-lyle> TravT good suggestion
16:40:15 <TravT> and another suggestion was to add a line to each one for people to add their name to it if they are interested in the session
16:40:38 <david-lyle> TravT, we'll get to the voting part once we're closer
16:40:47 <TravT> ok
16:40:48 <david-lyle> although I suppose we're getting closer
16:40:51 <david-lyle> :d
16:41:02 <david-lyle> this keyboard is killing me
16:41:39 <david-lyle> probably vote in a couple of weeks
16:42:26 <david-lyle> As in the past, I would expect the person proposing the session to lead the discussion, or if there are other volunteers, that's acceptable as well
16:46:47 <david-lyle> While everyone's typing away in the etherpad...  Any other topics for today?
16:48:24 <david-lyle> going twice
16:48:31 <doug-fish> while Daisy and amotoki are here... I've been thinking about this patch:  https://bugs.launchpad.net/horizon/+bug/1333927
16:48:48 <amotoki> doug-fish: here
16:48:58 <doug-fish> I'm not sure how much value it brings for i18n, but having the tz translated might be nice
16:49:04 <doug-fish> there are 4 new segments
16:49:22 <doug-fish> thoughts?
16:50:13 <amotoki> I have no strong opinion on this because I never have changed a timezone..
16:50:43 <Daisy> Having it would be nice, just in order to make the UI consistent.
16:51:02 <Daisy> I don't have strong opinions to have it in this release.
16:51:09 <amotoki> four strings are not a matter. I think it is up to UX topic.
16:51:10 <david-lyle> coming from a large installation, changing timezone just seems really odd to me in general
16:51:42 <david-lyle> but I digress
16:51:52 <doug-fish> I'm not hearing a strong demand for it from i18n
16:52:05 <doug-fish> and I'm really not a big fan of last minute changes (surprisingly enough!)
16:52:17 <doug-fish> so I think it can wait
16:52:36 <amotoki> what is affected?  usage in the project/admin overview page and ceilometer stats?
16:53:14 <david-lyle> doug-fish, if we provide the option, it should be localized, but I think this can go in Kilo
16:53:14 <doug-fish> amotoki:  the patch changes the user settings list of timezones to be shown in a localized manner
16:53:30 <doug-fish> the option is already there
16:53:35 <david-lyle> doug-fish, I know
16:53:40 <Daisy> doug-fish: amotoki and I just talked about the "sell puppies" and "sold puppies" you introduced. The developers notes are not shown in the translation tools properly.
16:53:44 <amotoki> my question is what feature uses timezone information. if only a few features use it, there is no need to chnage timezone now.
16:54:01 <doug-fish> :-)  there will be no deleting of puppies in my code.
16:54:08 <doug-fish> I hope that didn't cause too much confusion
16:54:38 <amotoki> doug-fish: "translators note" are not extracted to PO files as expected.
16:55:07 <amotoki> doug-fish: it is Daisy and i discussed. I have a fix, but it is not urgent I think.
16:55:10 <doug-fish> amotoki:  I assumed (maybe incorrectly) that every date and time shown in the UI was localized via the user setting
16:55:37 <david-lyle> doug-fish, I don't believe that is the case
16:55:40 <doug-fish> but I don't know the answer for sure
16:55:42 <david-lyle> and that would be horrible
16:55:46 <doug-fish> well that's disappointing
16:55:48 <doug-fish> really?
16:55:55 <david-lyle> and I would advocate removing it
16:56:11 <doug-fish> so on the overview page for example?
16:56:21 <doug-fish> I'd expect the dates to be localized to my timezone
16:56:26 <doug-fish> are you saying you wouldn't?
16:56:31 <amotoki> doug-fish: uptime information is localized already.
16:58:39 <david-lyle> let
16:58:52 <david-lyle> I give up on typing
16:58:56 <doug-fish> lol
16:59:16 <david-lyle> let's finish this discussion in launchpad or the review
16:59:27 <doug-fish> agreed
17:00:00 <sarob> Morning
17:00:02 <david-lyle> Thanks everyone for all the great work on RC1. Almost done. Review the remaining issues and we'll cut RC1 in the next day or two.
17:00:09 <david-lyle> Have a great week.
17:00:12 <david-lyle> #endmeeting