12:01:29 <mrunge> #startmeeting Horizon
12:01:30 <openstack> Meeting started Wed Jan 21 12:01:29 2015 UTC and is due to finish in 60 minutes.  The chair is mrunge. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:01:31 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:01:33 <openstack> The meeting name has been set to 'horizon'
12:01:44 <mrunge> good morning everyone
12:01:57 <tsufiev> hello
12:01:57 <akrivoka> hiya \o
12:01:57 <pkarikh> Hello!
12:02:00 <rdopiera> hi
12:02:31 <tmazur> hello o/
12:03:11 <mrunge> I don't have anything special for this meeting
12:03:18 <mrunge> and it looks like, nobody else had
12:03:34 <mrunge> #link https://wiki.openstack.org/wiki/Meetings/Horizon
12:03:54 <nikunj2512> mrunge: if i may?
12:04:04 <mrunge> go ahead
12:04:46 <nikunj2512> i want to talk to our i18n
12:05:05 <nikunj2512> framework and how we currently translate one language to another
12:05:30 <nikunj2512> as horizon is using angularjs why don't we use angularjs to translate?
12:06:01 <mrunge> ... as opposed to?
12:06:23 <nikunj2512> i came across this good angularjs plugin for translation -> http://angular-translate.github.io/ and i think it will to implement this rather to have static translations
12:06:28 <mrunge> nikunj2512, do you have a proposal, how to translate current strings?
12:07:01 <nikunj2512> i am still in process of putting togeather a proprosal
12:07:40 <nikunj2512> currently i was playing with the above mentioned library to see if it can be useful to horizon
12:07:51 <jpich> The mailing list might be more appropriate for this conversation, so people have time to familiarise themselves with the background when the proposal is ready
12:08:05 <nikunj2512> jpich: Ok
12:08:08 <mrunge> nikunj2512, once you're done, submit a blueprint
12:08:30 <jpich> The current angular patches may also have something already in place to allow translations
12:08:35 <jpich> Thanks
12:08:49 <nikunj2512> mrunge: Ok but if i may ask this -> will changing the method on how we translate the strings will be a good idea or not?
12:09:17 <nikunj2512> jpich: ok.. if possible can you point me to those patches?
12:09:33 <mrunge> nikunj2512, we're changing horizon from django based to be angular based, because we can
12:09:41 <mrunge> why shouldn't we do that?
12:10:00 <nikunj2512> yes... We should do it
12:10:01 <jpich> nikunj2512: I don't have them at hand, sorry - once you post on the list I'm sure the authors will be happy to share what i18n processes they were looking into
12:10:16 <nikunj2512> jpich: Ok
12:10:24 <nikunj2512> also i want to talk about the feature of "message of the day"?
12:10:36 <nikunj2512> what community thinks about this feature?
12:10:55 <mrunge> nikunj2512, do you have a blueprint?
12:11:01 <nikunj2512> someone has already filed a bug for this
12:11:02 <nikunj2512> no
12:11:20 <nikunj2512> but we have some technical issues with this
12:11:26 <mrunge> nikunj2512, my 2ct?
12:11:45 <nikunj2512> mrunge: ??
12:11:57 <mrunge> you'd need a database to provide a current "message of the day". Horizon doesn't require a database
12:12:00 <nikunj2512> but we have some technical issues with this like where we will store the sting for the message?
12:12:04 <nikunj2512> yes
12:12:14 <mrunge> see?
12:12:22 <nikunj2512> excatly that is the same thing i was wondering
12:12:24 <nikunj2512> yes
12:12:29 <rdopiera> in settings :P
12:12:39 <mrunge> oh yes, awesome
12:12:47 <wchrisj> lol
12:12:49 <nikunj2512> yes
12:13:16 <nikunj2512> but don't then admin have to edit the settings file everytime he/she has to change the message?
12:13:22 <nikunj2512> will it be good approach?
12:13:35 <mrunge> nikunj2512, not to mention: what admin?
12:14:01 <mrunge> nikunj2512, an admin in horizon is not necessarly in the position to change that file
12:14:01 <nikunj2512> The administator which has access to the cloud
12:14:16 <nikunj2512> Ok.. Then this creates one more issue
12:14:25 <mrunge> sure
12:14:30 <nikunj2512> Ok.. admin is the one who have access to the code
12:14:57 <mrunge> nikunj2512, depending on your POV
12:15:12 <nikunj2512> because admins might want to tell something to other users but if they don't have access to code, they can't change the message
12:16:04 <mrunge> nikunj2512, and what about showing different messages to different people?
12:16:14 <nikunj2512> mrunge: yes but for this functionality to work seamless they should be able to change the message from the horizon itself
12:16:29 <nikunj2512> mrunge: good suggestion
12:17:15 <mrunge> nikunj2512, about translations, https://github.com/openstack/horizon/commit/272314fdee8622a51c201eb4041d6ca278ffd7a2 was merged recently
12:17:23 <nikunj2512> mrunge: but on what bases will you show the different message to different people?
12:17:45 <mrunge> nikunj2512, I could imagine, that's totally dependent on the installation
12:17:49 <nikunj2512> mrunge: great.. thanks
12:18:05 <mrunge> nikunj2512, show message to everyone using more than 5 machines
12:18:08 <nikunj2512> mrunge: what is dependent on installation>
12:18:18 <mrunge> show to group xy
12:18:21 <nikunj2512> mrunge: Ok
12:18:28 <mrunge> show to folks located in huston
12:18:41 <mrunge> show to users of image foo
12:18:42 <nikunj2512> but for that you have to define certain caterias
12:18:58 <mrunge> nikunj2512, that is completely free
12:19:10 <nikunj2512> and it might be long list and will that much be required
12:19:16 <nikunj2512> Ok
12:19:19 <mrunge> and probably has the same bandwidth as billing
12:19:52 <nikunj2512> Ok.. like this we can have many more use-cases
12:20:05 <mrunge> and until we have a data store, it's quite useless to speak about that
12:20:11 <nikunj2512> yes
12:20:18 <mrunge> anything else?
12:20:20 <tsufiev> nikunj2512, I've seen a word 'messaging' at https://wiki.openstack.org/wiki/Zaqar Is it totally stupid to use it for MOTD?
12:21:04 <mrunge> is zaquar intended to be used for openstack internal projects?
12:21:12 <mrunge> or is that oslo.messaging?
12:21:38 <flaper87> mrunge: depends on what you need
12:21:41 <mrunge> tsufiev, but coupling to a message service is something we really want
12:21:50 <tsufiev> mrunge, frankly speaking, I do not know whether Zaqar is level-higher than oslo.messaging
12:21:54 <flaper87> oslo.messaging -> message broker communications / high loads / whatever
12:22:04 <flaper87> zaqar -> messaging API (higher level API but still messaging)
12:22:19 <flaper87> tsufiev: it's at a higher level
12:22:35 <nikunj2512> flaper87: ok.. Will zaqar will give us what we want here?
12:22:51 <flaper87> nikunj2512: no idea what you want, sorry. I should read the backlog.
12:22:56 * flaper87 has a highlight on Zaqar
12:22:57 <flaper87> :)
12:23:03 <mrunge> :D
12:23:04 <nikunj2512> flaper87: :)
12:23:16 <nikunj2512> but it is not a default openstack service.. correct?
12:23:17 <mrunge> nikunj2512, no. in your case: no.
12:23:30 <flaper87> nikunj2512: there won't be such a thing soon :)
12:23:33 <nikunj2512> mrunge: ok.
12:23:39 <nikunj2512> :)
12:23:42 <flaper87> it's not part of what's considered a cloud-core product
12:23:47 <flaper87> not sure how the TC calls it
12:23:52 <nikunj2512> ohh
12:24:10 <flaper87> but such distinction between integrated/non-integrated is going away
12:24:11 <tsufiev> nikunj2512, I believe that messaging service could be used not only for the MOTD, but also, for real-time broadcasting, e.g. message to all users that the could will be shut-down for 10 mins for maintenance
12:24:14 <mrunge> flaper87, and if we, as horizon, would make zaqar a dependency?
12:24:26 <flaper87> mrunge: that would be.... amazing :)
12:24:29 <tsufiev> s/could/cloud/
12:24:41 <flaper87> mrunge: I believe it would become an important piece
12:24:43 <flaper87> yes
12:24:49 <flaper87> (at least required)
12:24:56 <nikunj2512> tsufiev: yes.. that will be great
12:25:03 <mrunge> flaper87, yes, I think so.
12:25:42 <mrunge> we have a huge stack of operations running asynchronously
12:25:50 <nikunj2512> but it will be a great addition for but purpose?? if we can't use zaqar for message broadcasting?
12:25:51 <mrunge> and we don't see the results
12:28:27 <nikunj2512> mrunge: can we move to next item?
12:28:37 <mrunge> nikunj2512, of course
12:28:44 <mrunge> I don't have anything :D
12:28:57 <nikunj2512> i have one more thing
12:28:58 <nikunj2512> https://blueprints.launchpad.net/horizon/+spec/detecting-browser
12:29:25 <nikunj2512> The discussion on this blueprint is going on and on and last year also we discussed
12:29:46 <nikunj2512> what others think about this feature?
12:30:20 <mrunge> nikunj2512, are you trying to get this into kilo?
12:30:31 <tsufiev> nikunj2512, I hope that the browsers that don't support modern standards will eventually go away, given enough time :)
12:30:43 <nikunj2512> Yes.. i hope so.. with the community blessing :)
12:30:48 <mrunge> tsufiev, +1
12:31:04 <mrunge> nikunj2512, and others https://wiki.openstack.org/wiki/Kilo_Release_Schedule
12:31:11 <nikunj2512> yes but there are many people who still use windows XP and have old browsers
12:31:19 <mrunge> March 19th is kilo-3 deadline
12:31:30 <mrunge> nikunj2512, we agreed, not to support them
12:31:49 <nikunj2512> mrunge: i think we have enough time to implement and push this feature by then
12:32:20 <mrunge> nikunj2512, you'll need to have it reviewed as well
12:32:52 <mrunge> nikunj2512, and March19th is also string freeze
12:33:02 <mrunge> feature freeze is 2 weeks earlier
12:33:12 <nikunj2512> mrunge: yes but when a user uses horizon on legacy browsers and when they don't see any kind of message says we don't support your browser, they think code is broken
12:33:26 <nikunj2512> mrunge: ohhh... my bad
12:34:10 <nikunj2512> mrunge: it is not a big feature implementation wise but will greatly increase the horizon experience for users
12:34:19 <mrunge> nikunj2512, when someone agreed to move to angular, we dropped older browser support
12:34:53 <jpich> I think this has been discussed a lot already... some approaches are acceptable, and others aren't. You won't get 100% consensus/agreement from everyone. At this point it's probably best to get working on a patch
12:35:10 <nikunj2512> jpich: Ok...
12:35:25 <nikunj2512> jpich: i have something already in works and i will upload it
12:36:00 <mrunge> ok thank you
12:36:05 <mrunge> anything else?
12:36:14 <nikunj2512> Sorry one more -> https://blueprints.launchpad.net/horizon/+spec/set-default-params-for-launch
12:36:41 <nikunj2512> same old question will it be good feature to have it?
12:37:47 <mrunge> nikunj2512, it's my impression, it's superseeded by the launch-instance-workflow rework
12:38:03 <mrunge> which is currently blocking a few fixes
12:38:33 <nikunj2512> ok... which means to wait until that goes in?
12:38:53 <mrunge> as it doesn't make sense to work on a bug fix, when the whole code is being thrown away
12:39:05 <nikunj2512> correct
12:39:13 <nikunj2512> So, i will wait :")
12:40:28 <mrunge> waiting for a few mins for others to join the conversation here
12:41:04 <pkarikh> just fyi we have some problems with pypi package of django_openstack_auth. 1.1.8 hasn't been pushed into pypi.
12:41:35 <pkarikh> I've talked with infra-team on the last week, they are working on it
12:41:44 <mrunge> pkarikh, thanks
12:41:50 <pkarikh> But there ws no feedback for a long time.
12:42:08 <jpich> Yep, might be good to ask where it's at. Thanks pkarikh!
12:42:22 <pkarikh> they said that there is some bug and it is not trivial, or something like this.
12:42:39 <mrunge> pkarikh, I'd vote to release 1.1.9
12:42:48 <mrunge> to include e.g. https://github.com/openstack/django_openstack_auth/commit/336d7a531d8fb422e3b86a46b865339b3a321902
12:42:56 <mrunge> which fixes a regression
12:43:32 <mrunge> or this revoke token thing should be also included
12:43:38 <tsufiev> mrunge, +1, this regression was noticed quite fast :)
12:43:52 <jpich> mrunge: It's the entire "uploading django_openstack_auth to pypi" system which is broken, so we can tag that too, but that won't help for now
12:43:54 <mrunge> tsufiev, sure
12:44:17 <mrunge> jpich, thanks for sharing
12:44:22 <pkarikh> jpich mrunge no problem. :)
12:44:46 <mrunge> folks, is there something else?
12:45:01 <mrunge> I'd need to run out more sooner than later
12:46:31 <mrunge> thanks for joining us, and sorry for this quite confused meeting. I simply didn't knew until 12 UTC, that there is no leader.
12:46:35 <mrunge> #endmeeting