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