[openstack-dev] [horizon] 800 UTC Meeting Cancelled on 15/06

Hi all, I'm away next week so won't be able to run the 800 UTC meeting. The 2000 UTC meeting will be chaired by David Lyle. Rob __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [horizon] 1200 UTC meeting changed to 800 UTC

Hi all, The 1200 UTC meeting time has been changed to 800 UTC. You can find the ICS files for the team meetings and drivers meetings in the links below. http://eavesdrop.openstack.org/#Horizon_Team_Meeting http://eavesdrop.openstack.org/#Horizon_Drivers_Meeting Rob

[openstack-dev] [Horizon] Horizon Drivers meeting

Hi folks, With master now open for Newton development, I'm going to reopen the Horizon Drivers meeting. See https://wiki.openstack.org/wiki/Meetings/HorizonDrivers I intend to run the meeting both weeks for now (previously we had only held it every other week). The next meeting will be at

[openstack-dev] [Horizon] Bug day

Bug day returns! Everyone welcome! We've had some success but still a long way to go. The next bug day will be on the 5th of April. The focus of the bug days is to triage our existing bugs, not to fix specific bugs or find new ones (for now). In the future, as the list progresses to an

Re: [openstack-dev] [horizon][all] How to properly depend on Horizon

When you refer to publishing horizon on PyPI, did you mean the entire service (horizon + openstack_dashboard), or just the horizon package? My advice would be to add the horizon tarball to requirements.txt rather than test-requirements, and just use stable-* tarball when creating stable plugin

[openstack-dev] [horizon] Summit next week - Meetings cancelled

Hi all, Due to the summit next week, both of the usual Wednesday meetings are cancelled. Rob __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [horizon] Horizon Midcycle

Hi all, Horizon midcycle will be at Cisco HQ, Building 15 in San Jose, July 12th - 14th. Registration and topics etherpad: https://wiki.openstack.org/wiki/Sprints/HorizonNewtonSprint Rob __ OpenStack Development Mailing

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

could've discussed earlier, or during the summit for example. Rob On 1 May 2016 11:26 p.m., "Amrith Kumar" <amr...@tesora.com<mailto:amr...@tesora.com>> wrote: From: Rob Cresswell (rcresswe) [mailto:rcres...@cisco.com<mailto:rcres...@cisco.com>] Sent: Fr

[openstack-dev] [horizon] Midcycle Dates Poll

Hi all, Quick poll to get a preferred date for the Newton midcycle: http://doodle.com/poll/xvchsbbs4qz9tzr7 If you'd like a reference point, the release schedule is here: http://releases.openstack.org/newton/schedule.html. Planning should be finalised within the next week, so please respond

Re: [openstack-dev] [horizon] Plugin stability, failing tests etc.

The aim wasn't to be focused on what's easiest for Horizon at all; it was a suggestion to let plugins keep moving during brief periods of instability when people make mistakes. We're aware of the plugins need for stability and correct deprecation, but we won't catch everything. That said,

[openstack-dev] [horizon] Midcycle Summary

Hi everyone, We had the Horizon mid cycle meetup last week, and I wanted to highlight some of the discussion and decisions made. Agenda: https://etherpad.openstack.org/p/horizon-newton-midcycle Notes: https://etherpad.openstack.org/p/horizon-newton-midcycle-notes - Deprecation of table inline

[openstack-dev] [horizon] [horizon-plugin] Xstatic Angular 1.4.x release

Hi all, There is a patch up to release xstatic-angular 1.4.10.1 here: https://review.openstack.org/#/c/348254 From our testing, the upgrade required only a single patch to Horizon, found here: https://review.openstack.org/#/c/309004 The migration guide can be found here:

Re: [openstack-dev] [horizon] Midcycle Summary

mru...@redhat.com<mailto:mru...@redhat.com>> wrote: On 21/07/16 19:40, Rob Cresswell wrote: > Hi everyone, > > We had the Horizon mid cycle meetup last week, and I wanted to highlight > some of the discussion and decisions made. > > Agenda: https://etherpad.openstack.org/p/h

[openstack-dev] [horizon] Angular panel enable/disable not overridable in local_settings

Hi all, So we seem to be adopting a pattern of using UPDATE_HORIZON_CONFIG in the enabled files to add a legacy/angular toggle to the settings. I don't like this, because in settings.py the enabled files are processed *after* local_settings.py imports, meaning the angular panel will always be

Re: [openstack-dev] [horizon] Angular panel enable/disable not overridable in local_settings

) Rob On 2 August 2016 at 23:39, Richard Jones <r1chardj0...@gmail.com<mailto:r1chardj0...@gmail.com>> wrote: On 3 August 2016 at 00:32, Rob Cresswell <robert.cressw...@outlook.com<mailto:robert.cressw...@outlook.com>> wrote: Hi all, So we seem to be ado

[openstack-dev] [horizon] [horizon-plugin] AngularJS 1.5.8

Hi all, Angular 1.5.8 is now updated in its XStatic repo: https://github.com/openstack/xstatic-angular I've done some manual testing of the angular content and found no issues so far. I'll be checking that the JS tests and integration tests pass too; if they do, would it be desirable to

Re: [openstack-dev] [Horizon] On testing...

Another option is to just run separate test jobs. Like Django tests in one runner, and angular in another. As different panels are deprecated and removed, and we alter the scope of the tests, two jobs might act as a good stopgap. Rob On 21 July 2016 at 01:58, Richard Jones

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

Maybe I'm missing the point, but the schema stuff just defines a model and passes it to the schema directive via ctrl; doesn't that remove any issues with workflows? ui-bootstraps modal and modalinstance already provides a way to pass that data back to the initial location (table etc) again

Re: [openstack-dev] [horizon] Plugin stability, failing tests etc.

, angular work etc.) Rob On 20 July 2016 at 13:38, Hayes, Graham <graham.ha...@hpe.com<mailto:graham.ha...@hpe.com>> wrote: On 20/07/2016 10:16, Rob Cresswell wrote: > Hey all, > > So we've had a few issues with plugin stability recently, and its > apparent that many

[openstack-dev] [horizon] Plugin stability, failing tests etc.

Hey all, So we've had a few issues with plugin stability recently, and its apparent that many plugins are building off Horizon master as a dependency. I would really advise against this. A more manageable development process may be to: - Base stable plugins against a stable release of Horizon

Re: [openstack-dev] [horizon] Plugin stability, failing tests etc.

iscuss at the summit and judge demand, because most discussions thus far have concluded that its a lower priority issue than others. Rob On 20 July 2016 at 17:36, Hayes, Graham <graham.ha...@hpe.com<mailto:graham.ha...@hpe.com>> wrote: On 20/07/2016 15:13, Rob Cresswell wrote: &g

Re: [openstack-dev] [OPENSTACK] [HORIZON] Changing theme

Which version of Horizon are you running? Those look like Liberty settings to me, so wanted to check. Rob On 18 July 2016 at 07:49, ansh.ansh20...@gmail.com > wrote: Hi, I am unable to change the theme

[openstack-dev] [horizon] Next weeks meeting cancelled (2016-07-13)

Next weeks meeting is cancelled due to the midcycle. Meetings will resume as normal on the 20th of July. Rob __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [horizon] Keep / Remove 800 UTC Meeting time

There doesn't seem to have been any responses here, so I've gone ahead and proposed a patch to alter the meeting times: https://review.openstack.org/#/c/338130/ Rob On 30 June 2016 at 09:29, Rob Cresswell <robert.cressw...@outlook.com<mailto:robert.cressw...@outlook.com>> wrote:

[openstack-dev] [horizon] The bug list - how to use it, and how to triage

Hello! I just wanted to talk through Horizons bug list ( https://bugs.launchpad.net/horizon/ ), and how to use it to find issues you can help solve or review, as well as how to help triage bugs if you have time to help out. Using the bug list: - The "Tags" section on the right hand side is

[openstack-dev] [horizon] Keep / Remove 800 UTC Meeting time

Hi everyone, I've mentioned in the past few meetings that attendance for the 800 UTC meeting time has been dwindling. As it stands, there are really only 3 regular attendees (myself included). I think we should consider scrapping it, and just use the 2000 UTC slot each week as a combined

Re: [openstack-dev] [Heat][Horizon] Any guidelines for naming heat resource type names?

This sounds like a bug on the Horizon side. There is/was a patch regarding a similar issue with LBaaS v2 resources too. It's likely just an incorrect assumption in the logic processing these names. Rob On 16 Aug 2016 11:03 p.m., "Zane Bitter" >

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

re team, bug tracker, and release management. That will be a huge overhead to adding support for new neutron features. On Feb 6, 2017 03:36, "Rob Cresswell (rcresswe)" <rcres...@cisco.com<mailto:rcres...@cisco.com>> wrote: Core Neutron features should be within Horizon, with ext

Re: [openstack-dev] [Horizon] [Performance] Gathering quota usage data in Horizon

There's quite a lot to this. So, first off, quotas in horizon are not in great shape, and it should be one of our priorities next cycle to improve on this. As you've pointed out, it seems any check on quotas right now runs multiple serial API calls for everything that has quotas; I haven't

[openstack-dev] [horizon] PTL Candidacy for Pike

Hi everyone, I’m announcing my candidacy for PTL of Horizon for the Pike release cycle. Over the next 6 months I’d like to: - Narrow the blueprint/feature scope to ensure we focus on high priority areas, like non-performant panels or buggy user experiences. In previous cycles, our attitude

Re: [openstack-dev] [horizon] FFE Request

n 26, 2017 at 9:01 AM, Adrian Turjak <adri...@catalyst.net.nz<mailto:adri...@catalyst.net.nz>> wrote: +1 We very much need this as the performance of that panel is awful. This solves that problem while being a fairly minor code change which also provides much better UX. On 26/

[openstack-dev] [horizon] FFE Request

o/ I'd like to request an FFE on https://blueprints.launchpad.net/horizon/+spec/reorganise-access-and-security. This blueprint splits up the access and security tabs into 4 distinct panels. The first two patches are https://review.openstack.org/#/c/408247 and

[openstack-dev] [horizon] PTG Cross Project Sessions

Hi everyone, A reminder to those at the PTG about a couple of cross project sessions. - Wednesday, 2:30 - 3:30, Horizon / Keystone in Savannah 3 - Thursday 3:00 - 4:00, Horizon / I18n in Savannah 3 These are also listed in our PTG etherpad: https://etherpad.openstack.org/p/horizon-ptg-pike

[openstack-dev] [horizon] No meetings this week

Hi everyone, There will be no meetings this week due to the PTG (https://www.openstack.org/ptg/) Rob __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [horizon] [keystone] Cross-Project Meeting

Hey everyone, Quick reminder about the Keystone-Horizon meeting at 2000 UTC (about 1h45 from this email being sent). You can see the details and add it to your calendar via http://eavesdrop.openstack.org/#Keystone/Horizon_Collaboration_Meeting I'd like to keep up these meetings for the

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

Just a thought: With the way we currently do microversions, wouldnt this request 2.40 for every request ? There's a pretty good chance that would break things. Rob On 20 January 2017 at 00:02, Richard Jones > wrote: FFE granted for the

[openstack-dev] [horizon] Single core review for patch approval

Hey everyone, Horizon is moving to requiring only a single core review for code approval. Note that cores are not obliged to approve on a single +2; if a core would like a second opinion for patches that are complex or high risk, that is also fine. We still require at least one of the core

Re: [openstack-dev] [horizon] PTG Summary

will be reviewed and what will be ignored. Rob On 28 February 2017 at 04:33, Richard Jones <r1chardj0...@gmail.com<mailto:r1chardj0...@gmail.com>> wrote: On 28 February 2017 at 02:28, Rob Cresswell <robert.cressw...@outlook.com<mailto:robert.cressw...@outlook.com>> wrote:

[openstack-dev] [horizon] PTG Summary

Hi everyone! Quick summary of the PTG for those who missed it. Here's the etherpad, with notes inline: https://etherpad.openstack.org/p/horizon-ptg-pike We spent the first morning discussing plugins, with several plugin devs dropping in to discuss their issues. Several issues were mentioned

[openstack-dev] [horizon] Summit planning etherpad

Hi all, Etherpad for planning summit sessions: https://etherpad.openstack.org/p/horizon-ocata-summit Please note the sessions have been requested, not scheduled, so the actual number we get may not be the same. Rob __

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

Rob On 9 September 2016 at 12:49, Thierry Carrez <thie...@openstack.org<mailto:thie...@openstack.org>> wrote: Rob Cresswell wrote: > I've been toying with send this email for a while, but here goes: this > all feels like overcomplication and changing of a system that doesn't >

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

I've been toying with send this email for a while, but here goes: this all feels like overcomplication and changing of a system that doesn't really need to change. I've read the pros and cons, and I still can't really see a convincing reason not to move the PTL election to just-before-PTG, so

Re: [openstack-dev] [horizon] Integration Tests Status

Integration tests are now non-voting, so feel free to recheck failing builds. Rob On 28 September 2016 at 14:23, Rob Cresswell <robert.cressw...@outlook.com<mailto:robert.cressw...@outlook.com>> wrote: Hi all, So the integration tests have started failing all over the place

Re: [openstack-dev] [horizon] Browser Support

As you've noticed, this doc isn't updated currently. The current browsers supported are listed here: http://docs.openstack.org/developer/horizon/faq.html (Stable Firefox and Chrome, and IE 11+) Rob On 20 September 2016 at 08:23, Shinobu Kinjo >

Re: [openstack-dev] [horizon] Browser Support

. It is not a good situation that we have two contents. 2016-09-20 17:01 GMT+09:00 Rob Cresswell <robert.cressw...@outlook.com<mailto:robert.cressw...@outlook.com>>: > As you've noticed, this doc isn't updated currently. The current browsers > supported are listed here: > http

[openstack-dev] [horizon] Integration Tests Status

Hi all, So the integration tests have started failing all over the place again. Given the number of failures over the past few weeks I've put up a patch to make them non-voting [1]. Please stop rechecking patches until this merges. Reviewers, please be sure to check the test logs when they

Re: [openstack-dev] [horizon] USE_SSL

Was that ever in local_settings? I couldnt find any mention of it. The Django docs are probably your best bet for information: https://docs.djangoproject.com/en/1.10/topics/security/#ssl-https Rob On 9 November 2016 at 13:23, Luke Hinds > wrote: Hi,

Re: [openstack-dev] [horizon]New feature: enable/disable port security

Thanks for the patch! For something of this size, a wishlist bug is usually adequate, perhaps with an API reference to help us review faster :) Rob On 19 October 2016 at 12:19, Gyorgy Szombathelyi > wrote: Hi!

Re: [openstack-dev] [keystone][horizon] keystone/horizon integration session in barcelona

This sounds great! Thanks for organising, Steve. Rob On 11 October 2016 at 22:32, Richard Jones > wrote: Thanks, Steve, this will be a valuable session! On 12 October 2016 at 08:14, Steve Martinelli

[openstack-dev] [horizon] Summit Hangout Group

Just in case anyone missed this, we have a Google hangouts group for catching up at the summit, reminding each other of useful sessions, impromptu tequila, etc. If you'd like an invite, fire over an email address to me or Richard and we'll add you to the group. Rob

Re: [openstack-dev] [magnum-ui][horizon] use json-schema-form on workflow

From a quick scan, it looks like you're using it several times in the same workflow? Why not just use the existing tabs type and create a single form? Have a look at https://review.openstack.org/#/c/348969/for reference. Rob On 25 Nov 2016 08:28, "Shuu Mutou"

[openstack-dev] [horizon] Please avoid blueprint overload

Hey all, So this was discussed at the summit, but its still being done; we keep hugely overloading blueprint scope. There are dozens of patches assigned to a vague "identity tables" blueprint, which was already marked Obsolete. Several of these were just small unrelated features that are

Re: [openstack-dev] [horizon][nova][tc] nova-network deprecation in horizon

Frankly, it sounds like we can pretty comfortably drop support for nova-net in Pike. I'm fine with that, from a Horizon point of view. Rob On 28 March 2017 at 21:06, Matt Riedemann > wrote: On 3/28/2017 9:04 AM, Akihiro Motoki wrote: > Hi, > > I

[openstack-dev] [horizon] No meeting on 2017-03-22 (next week)

Hey everyone, I'm away for a week, so there'll be no Horizon meeting on the 22nd. Rob __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

[openstack-dev] [keystone] [horizon] Keystone-Horizon meeting on 2017-03-23 cancelled

Hey everyone, I'm away next week, so the Keystone-Horizon meeting on the 23rd is cancelled Rob __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [horizon] [horizon-plugin] Django Updates - Raising upper constraint to 1.9.13

Hi everyone, It's update time and we need to start raising the upper bounds on Django in global-requirements. We're currently capped at <1.9, which will shortly be raised to <1.10. This will raise the upper-constraint to 1.9.13. See https://review.openstack.org/#/c/453482/ Following a couple

[openstack-dev] [horizon] Pike-1 Tagged

Hey everyone, So we've just tagged our first milestone for Pike. I've checked launchpad and bumped anything unfinished to pike-2. You can see our progress for pike-1 at https://launchpad.net/horizon/+milestone/pike-1 5 blueprints implemented and 73 bugs closed, as well as many minor bugs that

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

It's been a week since the original email; I think we should scale back to a monthly sync up. No preference on which week of the month it falls in. Thanks! Rob On 13 April 2017 at 22:03, Lance Bragstad > wrote: Happy Thursday folks, Rob and I

[openstack-dev] [keystone] [horizon] Keystone - Horizon Cross Project Meeting

Hey folks, Just a reminder about the Keystone-Horizon meeting. It's Thursday, 2000 UTC (about 11 hours, 20 mins from sending this email) in #openstack-meeting-cp Discussion points, calendar links, current progress can be found at https://etherpad.openstack.org/p/keystone-horizon Rob

[openstack-dev] [horizon] Weekly meeting

Hey everyone, Reminder that the weekly IRC meeting is 2000 UTC on Wednesday in #openstack-meeting-3. Anyone is welcome to add to the agenda at https://wiki.openstack.org/wiki/Meetings/Horizon Previous logs, ICS files, and other info can be found at

[openstack-dev] [horizon] Weekly wrap-up

Hey folks, Great work since the PTG. In Pike so far we've already closed over 30 bugs (28 tracked, with a few minor untracked fixes) and backported several fixes to our stable releases, which we'll tag this week. Several blueprints are well on the way too, but really need reviews. Please check

Re: [openstack-dev] [horizon] Single core review for patch approval

there needs to be accountability re not always going for the single +2 when the patch is of that sort of size and you need a second opinion? Beth > On 28 Feb 2017, at 10:09, Rob Cresswell > <robert.cressw...@outlook.com<mailto:robert.cressw...@outlook.com>> wrote: > >

[openstack-dev] [horizon] [keystone] No Keystone-Horizon cross project meeting today

Hey everyone, Sorry for the late notice, but there will be no Horizon-Keystone cross project meeting this week, as we've little to discuss with the PTG so recent. The meeting will resume as normal next week. For those interested in joining, see

[openstack-dev] [horizon] Horizon Weekly IRC Meeting

Hey everyone, Reminder that the weekly IRC meeting is 2000 UTC on Wednesday (about 10.5 hours from sending this email) in #openstack-meeting-3. Anyone is welcome to add to the agenda at https://wiki.openstack.org/wiki/Meetings/Horizon Previous logs, ICS files, and other info can be found at

[openstack-dev] [horizon] Pike-3, Feature Freeze, and next steps

Hey everyone, We tagged Horizons Pike-3 milestone about 12 hours, so I wanted to quickly run through the next steps for the release. At this point, we are in "Feature Freeze" and also "Soft String Freeze". - Feature Freeze - No new features (blueprints or wishlist bugs) can be merged without

[openstack-dev] [horizon] [i18n] Horizon RC1 tagged

Hi everyone, We've now tagged Horizon's first Release Candidate for Pike (12.0.0). Please test it out, and get back to us ASAP with any critical bugs. This also means we've now created a stable/pike branch and master is open for features again; however, the immediate focus for the next few

[openstack-dev] [horizon] [keystone] [requirements] [rpm-packaging] [deb-packaging] Merging Django OpenStack Auth with Horizon

Apologies in advance for so many tags, hoping this is seen by the appropriate people. I've put up a patch to merge Django OpenStack Auth (DOA) into the Horizon tree: https://review.openstack.org/#/c/482561/ There is a blueprint to track any further changes / issues here:

[openstack-dev] [horizon] Bug reports and backporting

Hey everyone! Over the past few months there's been an increase in the number of patches without bug reports, and a decrease in the number of backports. I wanted to take a moment to explain why bug reports are useful, not just bureaucracy, and how they link to backports. Bug reports help in a

Re: [openstack-dev] [horizon] [horizon-plugin] [requirements] Moving to Django 1.11

, Rob Cresswell <robert.cressw...@outlook.com<mailto:robert.cressw...@outlook.com>> wrote: Hi everyone, Django 1.11 support has landed for Django OpenStack Auth [1], which was released shortly after [2]. Horizon's Django 1.11 support is just merging [3], at which point we will rais

[openstack-dev] [horizon] [horizon-plugin] [requirements] Moving to Django 1.11

Hi everyone, Django 1.11 support has landed for Django OpenStack Auth [1], which was released shortly after [2]. Horizon's Django 1.11 support is just merging [3], at which point we will raise the global requirement [4] and make the Horizon / DOA tests voting [5]. At that point, we should be

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

Hi everyone, I've put up a patch to global-requirements to raise the Django cap to "<1.11", with the upper-constraint at "1.10.7" (https://review.openstack.org/#/c/480215). Depending on the remaining time, I'd quite like to move us to "1.11.x" before Requirements Freeze, which will fall

[openstack-dev] [horizon] Progress on feedback from Boston Forum

Hi everyone, I've updated the etherpad tracking progress against feedback provided in the Boston Forum. There is a link to the original feedback etherpad inside: https://etherpad.openstack.org/p/horizon-pike-feedback-progress I wanted to highlight this as most of the feedback has now been

[openstack-dev] [horizon] OpenStack Summit meetups

Hello! A couple of notices about summit meetups for Horizon folk: - I've reserved about 2 hours on the Monday in Hynes, MR 108 from 2:00 -> 4:20. This may change if demand for the rooms is high, so keep an eye on https://ethercalc.openstack.org/Boston_Forum_Hacking_Rooms. I'll send a reminder

Re: [openstack-dev] [horizon]when I access my website, there is '500 internal server error'

It looks to me like you're updating dependencies past those that are supported in Ocata. When installing / upgrading packages, you should make sure they are bound by upper-constraints in the global requirements repo. Does horizon work from your AIO *before* you modified it? Rob On 8 Aug 2017

[openstack-dev] [horizon] Next 2 weekly meetings cancelled

Hi everyone! The next two weekly IRC meetings (3rd May, 10th May) are cancelled. I'm away this week and next week is the summit. Meetings will resume on the 17th! For those going to the summit, please read http://lists.openstack.org/pipermail/openstack-dev/2017-April/115982.html for meetup

Re: [openstack-dev] [horizon] Blueprint process question

There isn't a specific time for blueprint review at the moment. It's usually whenever I get time, or someone asks via email or IRC. During the weekly meetings we always have time for open discussion of bugs/blueprints/patches etc. Rob On 18 May 2017 at 16:31, Waines, Greg

[openstack-dev] [horizon] PTG Announcements

Hey everyone, I've made a Google Hangouts group for us to catch up at the PTG. Please ping me on IRC (robcresswell) or email me if you'd like the link to join. It would be great to meet you all in real life :) Also there will be no IRC meeting next week (13th of September) and I expect IRC to

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,

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] [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

[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

[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

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

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:

[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] 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

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] 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

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:

[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] 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] 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

[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

[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

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

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

  1   2   >