Re: [openstack-dev] [horizon] Multi-region support in shared Keystone service deployment

As I mentioned the last time you asked :), we use blueprints, and the template is here: https://blueprints.launchpad.net/horizon/+spec/template Please register a blueprint for discussion / tracking. The change looks sensible, although I’d prefer we use a setting name like

Re: [openstack-dev] [horizon] Admin dashboard instances index page generated duplicate Glance requests

This may be a bug; I recall it was patched recently and perhaps the same logic needs to be applied to the Admin view. It sounds like an oversight. Rob > On 14 Aug 2017, at 03:46, Xiong, Huan wrote: > > Hi, > > I observed accessing Admin dashboard's instance index

Re: [openstack-dev] [Openstack][horizon][ceilometer][gnocchi]Viewing gnocchi statistics on Dashboard

We removed the old Ceilometer content in Horizon a while ago; since then, nobody has worked on a new plugin to my knowledge. Rob > On 8 Aug 2017, at 15:15, gordon chung wrote: > > > > On 08/08/17 02:17 AM, pearl.dsil...@wipro.com wrote: >> I would like to know if there exists

Re: [openstack-dev] [Horizon][Nova] Editing flavor causing instance flavor display error

I’m planning on putting up a patch for this today. My proposal is to add a setting that disables it by default, then add a big warning side on the setting documentation and release notes. Anyone who then explicitly enables it will see the warning. Beyond that, we can deprecate it this cycle,

Re: [openstack-dev] [horizon] [horizon-plugin] Raising Django version cap

managed some projects and users. There is tons to actually test, but mostly it just seems to work. On 05/07/17 22:24, Rob Cresswell (rcresswe) wrote: If you want to install Django 1.11 and test it, that would be very helpful, even if its just to open bugs. I’m in the process of adding a non-voting j

Re: [openstack-dev] [horizon] [horizon-plugin] Raising Django version cap

If you want to install Django 1.11 and test it, that would be very helpful, even if its just to open bugs. I’m in the process of adding a non-voting job for 1.11 right now, so we should be able to move quickly. Rob On 5 Jul 2017, at 01:36, Adrian Turjak

[openstack-dev] [horizon] Next weekly IRC meeting cancelled

Hey everyone, The next weekly IRC meeting (2017-06-21) is cancelled, as I’m away for a week. Rob __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [horizon] seeing another users panel in Mitaka ?

This isn’t ringing any bells. Do you have any logs you could share? Rob On 7 Jun 2017, at 12:15, Waines, Greg > wrote: Has anyone seen the following behavior / issue ? I am using Mitaka. Sometimes ... with many users using the

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

[horizon] django-openstack-auth - blocking django - intermediary https://review.openstack.org/#/c/469420 is up to release django_openstack_auth. Sorry for the delays. Rob __ OpenStack Development Mailing List (not for

[openstack-dev] [horizon] Adding Ying Zuo to core team

Hey everyone, I’m adding Ying Zuo to the Horizon Core team. She’s been contributing many great patches to the code base driven by operator experience, as well as providing solid reviews. Welcome to the team! Rob __

Re: [openstack-dev] [ptls] Project On-Boarding Rooms

Hi, Could we take Horizon off the list? That’ll free up some time for other projects too. Rob On 28 Mar 2017, at 22:59, Kendall Nelson > wrote: Done! Zaqar is on the list - Kendall On Tue, Mar 28, 2017 at 4:17 PM Fei Long Wang

Re: [openstack-dev] [ptls] Project On-Boarding Rooms

Horizon would love the opportunity to baffle newcomers. This could also be useful for the many plugins that are managed by their respective service teams. Rob On 15 Mar 2017, at 18:20, Kendall Nelson > wrote: Hello All! As you may have seen

Re: [openstack-dev]  [Horizon] Empty metadata value support

You’d be better off checking each API or tagging Glance in this, since I think they originally wrote the metadata stuff. Horizon shouldn’t require anything the APIs don’t, but I’d imagine it was there for a reason, at least initially. Rob > On 14 Mar 2017, at 13:06, Mateusz Kowalski

Re: [openstack-dev] [Horizon][searchlight] Sharing resource type implementations

I tried searching the meeting logs but couldn’t find where we discussed this in the Searchlight meeting. The conclusion at the time was option 4 IIRC. The main thing is to make sure we get it done within one cycle, even if it isn’t default. this means searchlight-ui doesn’t have to carry some

Re: [openstack-dev] [horizon] [neutron] Horizon support for Neutron Trunks - PTL approval needed

Core Neutron features should be within Horizon, with extensions outside. This is a little hazy since even the default behaviour in Neutron is still a plugin, but thats the general idea. There are already some features outside, like the lbaas dashboard. Personally, I’d keep them in their own

Re: [openstack-dev] [horizon] feature freeze exception request -- nova simple tenant usages api pagination

As I understand it, if someone configures Nova to use 2.40 via settings, then it will use 2.40 for every request. This could likely break Horizon in weird ways, which makes it seem risky to try and support it. What I don’t really understand about this FFE, is why we need to modify the

Re: [openstack-dev] [Horizon] Weekly wrap-up

I think the intent is to get eyes on those patches, to prevent a 1000 line rewrite only for a core to say “I think this is a bad idea”. So for important patches, its probably good to get earlier feedback. Rob On 16 Dec 2016, at 08:13, Radomir Dopieralski

Re: [openstack-dev] [Horizon] Draft team mascot

ardj0...@gmail.com<mailto:r1chardj0...@gmail.com>> wrote: > >> Please let me know what you think (by December 12) of this draft for > >> our Horizon team mascot. > > > On 7 December 2016 at 07:38, Rob Cresswell (rcresswe) > <rcres...

Re: [openstack-dev] [Horizon] Draft team mascot

Are we missing an attachment / link ? :) > On 6 Dec 2016, at 20:19, Richard Jones wrote: > > Hi folks, > > Please let me know what you think (by December 12) of this draft for > our Horizon team mascot. > >

Re: [openstack-dev] [ptl][release] ocata release management communication

It looks like your email was already replied to: http://lists.openstack.org/pipermail/openstack-dev/2016-November/108141.html On 30 Nov 2016, at 18:38, Rob C > wrote: [Resending without the PTLs in CC because it got my mail stuck in the spam

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

Big +1 from me > On 14 Nov 2016, at 00:24, Richard Jones wrote: > > Hi Horizon core team, > > I propose Kenji Ishii as a new Horizon core reviewer. Kenji has been a > solid Horizon contributor for some time, with thoughtful and helpful > reviews showing good judgment

Re: [openstack-dev] [Horizon] Can not connect to Openstack Dashboard

Hi! It sounds like there’s nothing wrong with your customisations at all; you’ve followed the standard workflow there. I think the final line of the error log is key here: "RuntimeError: Unable to create a new session key. It is likely that the cache is unavailable.” Sounds to me something

Re: [openstack-dev] [Horizon][FFE]Support a param to specify subnet or fixed IP when creating port

I’m happy to allow this personally, but wanted to get others input and give people the chance to object. My reasoning for allowing this: - It’s high level, doesn’t affect any base horizon lib features. - It is mature code, has multiple patch sets and a +2 I’ll give it a few days to allow others

[openstack-dev] [horizon] Feature Freeze one week earlier in Newton.

Hi all, As requested we’ll be moving our feature freeze in Newton to R-6 (http://releases.openstack.org/newton/schedule.html). This is one week earlier than in previous cycles, to give plugins a chance to finalise their own features for Newton without risk of breaking changes. The FFE process

Re: [openstack-dev] [horizon][release] freeze timelines for horizon in newton

This has been discussed (just now) in the release management plan (https://etherpad.openstack.org/p/newton-relmgt-plan) See point 8 under Communication/Governance Changes. From an immediate standpoint, the RC phase of this cycle will be much stricter to prevent late breakages. Going forward,

Re: [openstack-dev] [horizon] - oAuth tab proposal

Could you put up a blueprint for discussion? We have a weekly meeting to review blueprints: https://wiki.openstack.org/wiki/Meetings/HorizonDrivers The blueprint template is here: https://blueprints.launchpad.net/horizon/+spec/template Thanks! Rob On 31 Mar 2016, at 10:57, Marcos Fermin Lobo

Re: [openstack-dev] [Horizon] How to add plugins from outside horizon tree

http://docs.openstack.org/developer/horizon/tutorials/plugin.html This should answer most questions about setting up and installing a plugin. Hope it helps! Rob On 28 Mar 2016, at 18:33, Mohan Kumar > wrote: Hi Team , Could you

[openstack-dev] [horizon] PTL candidacy

Hi folks, I'm announcing my candidacy for PTL for Horizon for the Newton release cycle. My main goals for the cycle are: - Remove roadblocks from AngularJS development so that the code can mature. This means optimistically approving patches in the experimental disabled panels, so that it

Re: [openstack-dev] [Horizon] Javascript linting and documentation

If possible, I’d really prefer we left linting work to Newton. It’ll be good to get it to a more usable state again, but we ought to be focusing on thoroughly checking the new Launch Instance for bugs and edge usage cases, as well as the outstanding bugs and blueprints targeted at RC1

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

+1 from me. Diana’s almost single handedly fixed our Bootstrap usage and gives lots of great reviews all across Horizon too. The boost to branding, theming and potential for accessibility, as well as huge reduction in CSS/HTML maintenance overhead, has been brilliant. Rob On 9 Mar 2016, at

Re: [openstack-dev] [Horizon] Bug Day 2

Reminder about bug day! Just starting if you’re over in Australia ;) Rob On 4 Jan 2016, at 10:54, Rob Cresswell (rcresswe) <rcres...@cisco.com<mailto:rcres...@cisco.com>> wrote: Hi folks, I think we should have another bug day to continue the good work started last time. I’d sug

[openstack-dev] [Horizon] Bug Day 2

Hi folks, I think we should have another bug day to continue the good work started last time. I’d suggest Tuesday the 12th of January, as most people should be back at work by then. We can use the same etherpad too: https://etherpad.openstack.org/p/horizon-bug-day For those not around for the

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

An equally big +1! On 02/12/2015 18:56, "David Lyle" wrote: >I propose adding Richard Jones[1] to horizon-core. > >Over the last several cycles Timur has consistently been providing >great reviews, actively participating in the Horizon community, and >making meaningful

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

A big +1 for me! On 02/12/2015 18:52, "David Lyle" wrote: >I propose adding Timur Sufiev[1] to horizon-core. > >Over the last several cycles Timur has consistently been providing >great reviews, actively participating in the Horizon community, and >making meaningful

Re: [openstack-dev] [horizon] Supporting Django 1.9

d" <z...@debian.org> wrote: >On 11/27/2015 11:18 AM, Rob Cresswell (rcresswe) wrote: >> Mitaka will support 1.9. I’m already working on it :) >> Liberty is >= 1.7 and < 1.9, so shouldn’t matter. >> >> Rob > >It does mater for me, at least until the final

Re: [openstack-dev] [horizon] Supporting Django 1.9

Mitaka will support 1.9. I’m already working on it :) Liberty is >= 1.7 and < 1.9, so shouldn’t matter. Rob On 27/11/2015 09:23, "Thomas Goirand" wrote: >Hi, > >Django 1.9 is due to be released in early December, and will reach >Debian Sid soon after that. It'd be nice to

[openstack-dev] [Horizon] Bug Day: The Aftermath

Hi all, Bug day was great! We categorised around 140 bugs, reducing the Undecided count to 466 from ~600, and also removed around 50 bugs that were no longer valid. This is a step in the right direction, and I think it would be worth organising more bug days in the cycle, spread out so as not

[openstack-dev] [Horizon] Bug day! Yeah!

Reminder about bug day! Hop on IRC (#openstack-horizon) and help out :) https://etherpad.openstack.org/p/horizon-bug-day Rob __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Horizon] Bug day! Yeah!

's do it. I'd like to suggest we use an etherpad to keep track of what people have done. If it's not created when I start my day, I'll make one. Richard On 19 November 2015 at 22:19, Rob Cresswell (rcresswe) <rcres...@cisco.com<mailto:rcres...@cisco.com>> wrote: Hey folks, Ou

[openstack-dev] [Horizon] Bug day! Yeah!

Hey folks, Our bug list is… rather large. We’ve discussed having a bug day, where as a community we all dedicate some time to triaging bugs and discussing in the IRC channel as we go. First off, see the docs about bug triage: https://wiki.openstack.org/wiki/BugTriage Secondly, lets pick a

Re: [openstack-dev] [ceilometer][vitrage][horizon] ceilometer alarms screen in horizon

This blueprint is being revived by a new assignee I believe: https://blueprints.launchpad.net/horizon/+spec/ceilometer-alarm-management-page Rob From: "ITZIKOWITZ, Noy (Noy)" > Reply-To:

Re: [openstack-dev] [Horizon] Suggestions for handling new panels and refactors in the future

Personally, I¹d still vote for feature branching: I¹d really love to see an Angular Panels feature branch worked on separately and then merged back in; effectively, Travis¹ 2nd option. Pick 3(?) panels, like Users, Images, and the System Information one I¹ve seen around, iterate quickly, merge in

[openstack-dev] [horizon] Weekly Bug Report

Morning Horizoneers, https://wiki.openstack.org/wiki/Horizon/WeeklyBugReport Weekly bug report has been updated! Most of the bugs were solved (woohoo!), or are stuck at discussion point and have been removed until better solutions are found. I¹ve added new priority bugs, and there are still

Re: [openstack-dev] [Horizon] Selenium is now green - please pay attention to it

Also, please rebase patches to make sure they are passing selenium and integration, even if they have been previously verified. Yes, it¹s a little frustrating, but selenium is still non-voting so it will not block merges. Rob On 01/10/2015 19:34, "Doug Fish" wrote:

Re: [openstack-dev] [Horizon] Horizon Productivity Suggestion

t;mailto:travis.tr...@hpe.com>> wrote: Things always move more quickly at the end of a cycle because people feel release pressure, but I do think this is a good idea. 2 - 3 minutes isn’t very realistic. It would need to be planned for longer. On 9/28/15, 3:57 AM, "Rob Cresswell (rcre

[openstack-dev] [Horizon] Horizon Productivity Suggestion

Hi folks, I¹m wondering if we could try marking out a small 2-3 minute slot at the start of each weekly meeting to highlight Critical/ High bugs that have code up for review, as well as important blueprints that have code up for review. These would be blueprints for features that were identified

Re: [openstack-dev] [horizon] URL Sanity

seems to me that if ports must be attached to networks then it makes sense for the URL to reflect that. On the other hand, some could argue that the django URL routing is ... legacy ... and shouldn't me messed with :) On the gripping hand, thinking about this could inform future angular routing planning..

[openstack-dev] [horizon] URL Sanity

Hi all, I recently started looking into properly implementing breadcrumbs to make navigation clearer, especially around nested resources (Subnets Detail page, for example). The idea is to use the request.path to form a logical breadcrumb that isn’t dependent on browser history (

Re: [openstack-dev] [horizon] Minimum Unit Test Coverage

at 6:33 AM, Rob Cresswell (rcresswe) rcres...@cisco.commailto:rcres...@cisco.com wrote: Hi all, As far as I’m aware, we don’t currently enforce any minimum unit test coverage, despite Karma generating reports. I think as part of the review guidelines, it would be useful to set a minimum. Since

[openstack-dev] [horizon] Minimum Unit Test Coverage

Hi all, As far as I’m aware, we don’t currently enforce any minimum unit test coverage, despite Karma generating reports. I think as part of the review guidelines, it would be useful to set a minimum. Since Karma’s detection is fairly relaxed, I’d put it at 100% on the automated reports. I

[openstack-dev] [horizon] [docs] AngularJS in Horizon Docs

Hi all, Had another pass of the AngularJS documentation: https://review.openstack.org/#/c/182243/ My hope here is to merge soon, noting those sections that may change, and update as they do change. This may potentially mean short periods of inaccuracy between the docs and reality, but

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

So my view here is that I don’t particularly mind which plugin/ set of plugins Horizon uses, but the biggest deterrent is the workload. We’re already cleaning everything up quite productively, so I’m reluctant to swap. That said, the cleanup from JSCS/ JSHint should be largely relevant to

Re: [openstack-dev] [Horizon][sahara]

This was a known bug with the modals, which was fixed yesterday. Update horizon master, and you’re good to go :) Bug: https://bugs.launchpad.net/horizon/+bug/1459115 Patch: https://review.openstack.org/#/c/185927/ Rob From: lu jander juvenboy1...@gmail.commailto:juvenboy1...@gmail.com

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

Went through the files myself and I concur. Most of these files define pieces specific to our implementation of the dashboard, so should be moved. I’m not entirely sure on where _messages should sit. As we move forward, won’t that file just end up as a toast element and nothing more? Maybe I’m

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

...@linux.vnet.ibm.com wrote: I would be happy with either the two proposed solutions (both improvements over the what we have now). Any thoughts on combining them? Only close if esc or 'x' is clicked, but also warn them if data was entered. On 12/3/2014 7:21 AM, Rob Cresswell (rcresswe) wrote: +1 to changing

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

+1 to changing the behaviour to ‘static'. Modal inside a modal is potentially slightly more useful, but looks messy and inconsistent, which I think outweighs the functionality. Rob On 2 Dec 2014, at 12:21, Timur Sufiev tsuf...@mirantis.commailto:tsuf...@mirantis.com wrote: Hello,