Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for core

+1 from me. Kenji is also very active in the plugin space.   - Original message -From: David Lyle To: "OpenStack Development Mailing List (not for usage questions)" Cc:Subject: Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for

Re: [openstack-dev] [Horizon] ui-cookiecutter

.openstack.org/wiki/Meetings/HorizonBest regards,Shu Muto> -----Original Message-> From: Thai Q Tran [mailto:tqt...@us.ibm.com]> Sent: Tuesday, November 15, 2016 4:30 AM> To: openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [Horizon] ui-cookiecutter>> Hi Shuu,&

Re: [openstack-dev] [Horizon] ui-cookiecutter

Hi Shuu,   Sorry for the delay again, I just got back from vacation. I think your cookiecutter will be useful in a number of ways.   1. We can use it to easily generate plugins for beginners 2. We can use it in Horizon's startdash command (have to look into this) for internal use   Ideally, the

Re: [openstack-dev] [horizon] [horizon-plugin]

Hi Jason,   You should have access to it already. Just import from horizon the code you need. What you're looking for resides in the (request.user) object. Here are some usage examples, https://github.com/openstack/horizon/blob/master/openstack_dashboard/templatetags/context_selection.py   -

Re: [openstack-dev] [Horizon] Angular action services and initScope

You all sort of touched on what I am about to reiterate:   1. The scope was intended to be used as a way to propagate events up and down the chain (from table controller to step controller) since there was no real way to share information between controllers (remember that a modal dialog launches

Re: [openstack-dev] [security] [horizon] Security implications of exposing a keystone token to a JS client

I am not sure if this is a valid concern. If I am using a CLI and someone gets access to my computer, they can do whatever they well please. If I am using Horizon and someone gets access, its going to be the same story, they can still do damage even without knowing the token (at least until the

[openstack-dev] [zaqar][zaqar-ui] Nomating Shu Muto for Zaqar-UI core

Hello all, I am pleased to nominate Shu Muto to the Zaqar-UI core team. Shu's reviews are extremely thorough and his work exemplary. His expertise in angularJS, translation, and project infrastructure proved to be invaluable. His support and reviews has helped the project progressed. Combine

[openstack-dev] [swift][keystone] Using JSON as future ACL format

Hello all, Hope everyone had a good weekend, and hope this email does not ruin your next. We had a small internal discussion at IBM and here are some of the findings that I will present to the wider community. 1. The ":" separator that swift currently uses is not entirely safe since LDAP can

Re: [openstack-dev] [horizon] [javascript] Async file uploads in anew JS-centric UI

Thanks for the great explanation Timur. I have bookmarked both and will look into it shortly. From: Timur Sufiev To: "OpenStack Development Mailing List (not for usage questions)" Date: 05/17/2016 10:38 AM Subject:

Re: [openstack-dev] [horizon] PTL noncandidacy

Thanks David for your commitment and leadership. I learned a lot from you and your perspective on things. Looking forward to learn more from you and to work along side you into the foreseeable future. You are sticking around right? I still have TONS of questions to ask, JK :P   - Original

Re: [openstack-dev] [horizon] Proposal to add Diana Whitten tohorizon-core

Big +1 from me, thanks for all the hard work Diana!   - Original message -From: David Lyle To: OpenStack Development Mailing List Cc:Subject: [openstack-dev] [horizon] Proposal to add Diana Whitten to horizon-coreDate: Tue, Mar 8, 2016

Re: [openstack-dev] [Horizon][Trove] Horizon-Trove External Repository

Great article Andreas!   For angular translation to work, you'll need to reference https://github.com/openstack/horizon/blob/master/horizon/utils/babel_extract_angular.py which the guide already covers.   To use it, see https://angular-gettext.rocketeer.be/dev-guide/annotate/ for examples.    

Re: [openstack-dev] [Horizon] Handling 401 in new REST API

I am assuming that you meant redirecting on the server side. We already have a similar one in place on the client side. https://github.com/openstack/horizon/blob/master/horizon/static/framework/framework.module.js#L65   Currently, you're not able to hit the REST layer directly anyway, You get a

Re: [openstack-dev] [horizon] Angular Views overriding

Hello,   When we designed the architecture for the angular work, we had extension in mind. We have pretty good support for extending a workflow (see links below). We have a bunch of patches that when put together will do what you want, but no guide on how to do it. The documentation in Horizon is

Re: [openstack-dev] [Horizon] Mid-cycle Sprint

FYI, Cindy and I will put in a request for travel approval. Also, I have spoken to Mariam and would be willing to mentor David.   - Original message -From: David Lyle To: OpenStack Development Mailing List Cc:Subject: [openstack-dev]

Re: [openstack-dev] [horizon] Proposal to add Richard Jones tohorizon-core

An equally BIG +1 from me! Thanks for all the reviews and patches from your minions Richard!   - Original message -From: David Lyle To: OpenStack Development Mailing List Cc:Subject: [openstack-dev] [horizon] Proposal to add Richard

Re: [openstack-dev] [horizon] Proposal to add Timur Sufiev tohorizon-core

BIG +1 for me. Thanks for all of the great work Timur!   - Original message -From: David Lyle To: OpenStack Development Mailing List Cc:Subject: [openstack-dev] [horizon] Proposal to add Timur Sufiev to horizon-coreDate: Wed, Dec 2,

[openstack-dev] [Horizon][Trove] Horizon-Trove External Repository

Hello Trovers and Horizoneers,   The intention of this email is to get everyone on the same page so we are all aware of what is going on. As many of you are probably already aware, Horizon is moving toward the plugin model for all of its dashboards (including existing dashboards). This release

Re: [openstack-dev] [Horizon] Update on Angular Identity work

data to figure out what duplicate code can be abstracted out based from those two implementation.-LinOn Thu, Aug 20, 2015 at 4:36 PM, Doug Fish the.doug.f...@gmail.commailto:the.doug.f...@gmail.com wrote:It appears to me that option 1 would be better prepared to be extensible ... That is if a plu

Re: [openstack-dev] [Horizon] Update on Angular Identity work

extensible ... That is if a plugin needed to add an action or a column, we could make that happen with pattern 1 (possibly after adding in a service) I'm not sure how plugins ever add these things with pattern 2.On Aug 20, 2015, at 1:41 PM, "Thai Q Tran" tqt...@us.ibm.com wrote:Hi Lin,Let me draw on some exam

Re: [openstack-dev] [Horizon] Update on Angular Identity work

used most of the time rather than the customization case which maybe harder to do. Which leads me to preferring option 2.Thanks,LinOn Wed, Aug 19, 2015 at 12:16 PM, Thai Q Tran tqt...@us.ibm.com wrote:Hi Lin,I agree with you and Eric that we have a lot of HTML fragments. Some of the

Re: [openstack-dev] [Horizon] Update on Angular Identity work

to reduce the duplicated code before moving forward to other panels?-Lin[1] https://github.com/openstack/horizon/tree/master/openstack_dashboard/dashboards/identity/static/dashboard/identity/users/tableOn Tue, Aug 18, 2015 at 11:49 AM, Thai Q Tran tqt...@us.ibm.com wrote:Hi everyone,Just wanted to keep e

Re: [openstack-dev] [Horizon] Update on Angular Identity work

Hi everyone,Just wanted to keep everyone up to date on the angular panels work. The goal was to set a pattern that others can follow, to that end, there were a few requirements:1. reusable and possibly pluggable2. easy to understand3. reduce code duplicationThese requirements don't always go

Re: [openstack-dev] [Keystone] [Horizon] Federated Login

text/html; charset=UTF-8: Unrecognized __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [Openstack][Horizon] Sharable Angular mock

Love the idea, great explanation! I see value in this going forward. Definitely interested. From: Chen, Shaoquan sean.ch...@hp.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: 07/19/2015 05:34 PM Subject:

Re: [openstack-dev] [horizon] Angular dependencies and the hz.dashboard namespace

Heres a summary of what we talked about:1.Need to retain the same file structure so that pluggins continue to work.Example:https://github.com/stackforge/monasca-ui/tree/master/monitoringBasically we have existing pluggins that use this file structure, we need to honor it.This is not directly

Re: [openstack-dev] [javascript] [horizon] [merlin] [refstack] Javascript Linting

I agree with Rob in terms of tooling and with Travis on rules.Any linting tool is fine with me as long as it does not break the rules we currently have set in Horizon. I believe the rules right now are general enough, so switching to eslint might not be an issue, but its something to look into.

Re: [openstack-dev] [horizon][i18n] Ordering of PO files

openstack-dev@lists.openstack.orgFrom: Andreas Jaeger a...@suse.comDate: 06/09/2015 12:03AMSubject: Re: [openstack-dev] [horizon][i18n] Ordering of PO filesOn 06/09/2015 01:28 AM, Thai Q Tran wrote: Hi folks, In the midst of shifting to angular, we are making use of babel for extracting messages.

[openstack-dev] [horizon][i18n] Ordering of PO files

Hi folks,In the midst of shifting to angular, we are making use of babel for extracting messages. This would then allow us to write a custom extractor for angular templates.Here's the patch that compare PO files:https://review.openstack.org/#/c/189502/It looks worse than reality, if you compare

Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team

I am interested but not sure how much time I have this release cycle. I can take on a more hands-off approach and help review to make sure that magnum-ui is align with future horizon directions.-"Steven Dake (stdake)" std...@cisco.com wrote: -To: "OpenStack Development Mailing List (not

[openstack-dev] [horizon] Prioritize tests over JSCS

Hi folks,I know a lot of people are tackling the JSCS stuff, and thats really great. But it would be extra nice to see JSCS stuff along with JP's guidelines in your patches. Furthermore, if the file you are working on doesn't have an accompanying spec file, please make sure that the tests for it

[openstack-dev] [horizon] Angular-Django i18n

Hi folks,Just drafted a blueprint on this topic so that we can all be on the same page. Its quite long, but hopefully you will take some time to read through it and provide some meaningful feedback. In the mean time, I will do some more investigation and keep you all posted. If you have questions

Re: [openstack-dev] [Horizon] dashboard-app split in horizon

Yes Rob, you are correct. ToastService was something Cindy wrote to replace horizon.alert (aka messages). We can't remove it because legacy still uses it.-"Rob Cresswell (rcresswe)" rcres...@cisco.com wrote: -To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [Horizon] dashboard-app split in horizon

Looks/sounds good, I started down this path a while ago and it never gained traction, so glad to see that it is finally moving along.-Richard Jones r1chardj0...@gmail.com wrote: -To: "OpenStack Development Mailing List (not for usage questions)" openstack-dev@lists.openstack.orgFrom:

Re: [openstack-dev] [Horizon] Core Reviewer Update

Welcome to the team Doug, Rob, and Travis!!!-David Lyle dkly...@gmail.com wrote: -To: OpenStack Development Mailing List openstack-dev@lists.openstack.orgFrom: David Lyle dkly...@gmail.comDate: 04/28/2015 04:00PMSubject: [openstack-dev] [Horizon] Core Reviewer UpdateI am pleased to

Re: [openstack-dev] [Horizon] Outreachy call for mentor

Hi Victoria, Count me in also. I'll go ahead and subscribe myself to the mailing list as well. From: Victoria Martínez de la Cruz victo...@vmartinezdelacruz.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date:

Re: [openstack-dev] [horizon][keystone]

uot;Default Protocol" or "Discovery Service".The proposed UI is rather embarrassing.AntonOn Thu, Feb 5, 2015 at 12:54 AM, Thai Q Tran tqt...@us.ibm.com wrote:Hi all,I have been helping with the websso effort and wanted to get some feedback.Basically, users are presented with a login

Re: [openstack-dev] [horizon][keystone]

their accounts via the dashboard. Hint: This is being done by automatic redirect to predefined Keystone endpoint once user hits our dashboard's URL). Marek On 05.02.2015 20:15, Thai Q Tran wrote: Hi Ioram, Thanks

Re: [openstack-dev] [horizon] JavaScript docs?

As we're moving toward Angular, might make sense for us to adopt ngdoc as well.-Matthew Farina m...@mattfarina.com wrote: -To: "OpenStack Development Mailing List (not for usage questions)" openstack-dev@lists.openstack.orgFrom: Matthew Farina m...@mattfarina.comDate: 02/04/2015

[openstack-dev] [horizon][keystone]

Hi all,I have been helping with the websso effort and wanted to get some feedback.Basically, users are presented with a login screen where they can select: credentials, default protocol, or discovery service.If user selects credentials, it works exactly the same way it works today.If user selects

Re: [openstack-dev] [horizon] function expressions vs function declarations in JavaScript

there any process?On Wed, Jan 14, 2015 at 1:15 PM, Thai Q Tran tqt...@us.ibm.com wrote:It was definitely an interesting the read, I never really noticed the subtle difference. Since then I have also read a few other thoughts on it.For me, function declarations can get convoluted very fast

Re: [openstack-dev] [horizon] function expressions vs function declarations in JavaScript

It was definitely an interesting the read, I never really noticed the subtle difference. Since then I have also read a few other thoughts on it.For me, function declarations can get convoluted very fast if not use correctly.Surely, you should never define functions inside of an if statement, and

Re: [openstack-dev] [horizon] REST and Django

In your previous example, you are posting to a certain URL (i.e./keystone/{ver:=x.0}/{method:=update}).client: POST /keystone/{ver:=x.0}/{method:=update} = middleware: just forward to clients[ver].getattr("method")(**kwargs) = keystone: updateCorrect me if I'm wrong, but it looks like you have a

Re: [openstack-dev] [Horizon] Moving _conf and _scripts to dashboard

at 1:22 PM, Thai Q Tran tqt...@us.ibm.com wrote:It would not create a circular dependency, dashboard would depend on horizon - not the latter.Scripts that are library specific will live in horizon while scripts that are panel specific will live in dashboard.Let me draw a more concrete example.

Re: [openstack-dev] [Horizon] Moving _conf and _scripts to dashboard

don't mind moving the code around to _scripts file, but simply dropping the _conf file is my concern since it might already be extended from. Perhaps document it first that it will be deprecated, and remove it on later release.On Fri, Dec 12, 2014 at 10:43 AM, Thai Q Tran tqt...@us.ibm.com wrote:As i

Re: [openstack-dev] [Horizon] Moving _conf and _scripts to dashboard

n Wed, Dec 10, 2014 at 7:20 PM, Thai Q Tran tqt...@us.ibm.com wrote:Sorry for duplicate mail, forgot the subject.-----Thai Q Tran/Silicon Valley/IBM wrote: -To: "OpenStack Development Mailing List \(not for usage questions\)" openstack-dev@lists.openstack.orgFrom: Thai Q Tran/Silicon V

Re: [openstack-dev] [horizon] REST and Django

in batches, will receive the response from the API backend, and will render the results. The whole processing logic will be held in the Frontend(JS), while the middleware will just act as proxy(un/packer). This way we will maintain just the logic in the frontend, and will not need to duplicate some l

[openstack-dev] Moving _conf and _scripts to dashboard

The way we are structuring our_javascript_stoday is complicated. All of our static _javascript_s reside in /horizon/static and are imported through _conf.html and _scripts.html. Notice that there are already some panel specific _javascript_s like: horizon.images.js, horizon.instances.js,

[openstack-dev] [Horizon] Moving _conf and _scripts to dashboard

Sorry for duplicate mail, forgot the subject.-Thai Q Tran/Silicon Valley/IBM wrote: -To: "OpenStack Development Mailing List \(not for usage questions\)" openstack-dev@lists.openstack.orgFrom: Thai Q Tran/Silicon Valley/IBMDate: 12/10/2014 03:37PMSubject: Moving _conf an

Re: [openstack-dev] [horizon] [ux] Changing how the modals are closed in Horizon

I like David's approach, but having two modals (one for the form, one for the confirmation) on top of each other is a bit weird and would require constant checks for input. We already have three ways to close the dialog today: via the cancel button, X button, and ESC key. It's more important to

Re: [openstack-dev] [horizon] REST and Django

To: Travis Tripp travis.tr...@hp.com, Thai Q Tran/Silicon Valley/IBM tqt...@us.ibm.com, David Lyle dkly...@gmail.com, Maxime Vidori maxime.vid...@enovance.com, Wroblewski, Szymon szymon.wroblew...@intel.com, Wood, Matthew David (HP Cloud - Horizon) matt.w...@hp.com, Chen, Shaoquan sean.ch