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

٩(͡๏̮͡๏)۶ +1! On Wed, Dec 2, 2015 at 11:58 AM, Rob Cresswell (rcresswe) < rcres...@cisco.com> wrote: > 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

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

Definite +1 for me. I think they are great additions to the team! -Travis On 12/2/15, 11:57 AM, "David Lyle" wrote: >Let's try that again. > >I propose adding Richard Jones[1] to horizon-core. > >Over the last several cycles Richard has consistently been providing

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

Let's try that again. I propose adding Richard Jones[1] to horizon-core. Over the last several cycles Richard has consistently been providing great reviews, actively participating in the Horizon community, and making meaningful contributions around angularJS and overall project stability and

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

+1! On Wed, Dec 2, 2015 at 11:57 AM, Rob Cresswell (rcresswe) < rcres...@cisco.com> wrote: > 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

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

On 02/12/15 19:57, David Lyle wrote: > Let's try that again. > > I propose adding Richard Jones[1] to horizon-core. > Please respond with comments, +1s, or objections within one week. Yes, +1 from me. Matthias __ OpenStack

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

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 contributions particularly around testing and stability. Please respond with comments, +1s,

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] Proposal to add Richard Jones to horizon-core

Timur, I'm sure you can chime in even if your vote doesn't count [yet]! On Wed, Dec 2, 2015 at 12:11 PM, Tripp, Travis S wrote: > Definite +1 for me. I think they are great additions to the team! > > -Travis > > > > > > On 12/2/15, 11:57 AM, "David Lyle"

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

On 02/12/15 19: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 contributions particularly around testing and >

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

Thanks all. All comments so far are from neutron side. I would like to wait inputs from horizon side, especially David. Option (c) is what we do in neutron sub-projects under neutron stadium model and I agree it makes sense and sounds natural to neutron folks. My initial mail just did not cover

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

Another +1 from me From: David Lyle <dkly...@gmail.com> Sent: Thursday, 3 December 2015 5:57 AM To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [horizon] Proposal to add Richard Jones to horizon-core Let's try that again. I p

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

+1 thanks for all the hard work! And Timur will fix pagination too :) On Wed, Dec 2, 2015 at 7:52 PM, 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

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

On 12/02/2015 01:57 PM, David Lyle wrote: Let's try that again. I propose adding Richard Jones[1] to horizon-core. Over the last several cycles Richard has consistently been providing great reviews, actively participating in the Horizon community, and making meaningful contributions around

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

+1 thanks for all the hard work Richard! On Wed, Dec 2, 2015 at 7:56 PM, 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

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

+1, now we can see more merges in angular patches. On 12/03/2015 12:22 AM, 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

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

+1! On 3 December 2015 at 07:31, Matthias Runge wrote: > On 02/12/15 19: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

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

+1 from me From: David Lyle <dkly...@gmail.com> Sent: Thursday, 3 December 2015 5:52 AM To: OpenStack Development Mailing List Subject: [openstack-dev] [horizon] Proposal to add Timur Sufiev to horizon-core I propose adding Timur Sufiev[1] to h

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

On 11/29/2015 08:59 PM, Rob Cresswell (rcresswe) wrote: > https://blueprints.launchpad.net/horizon/+spec/drop-dj17 > > > This is where changes are currently being tracked. I don’t quite > understand why these would be back ported; they would break Liberty with > 1.7. Perhaps we can discuss on

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

https://blueprints.launchpad.net/horizon/+spec/drop-dj17 This is where changes are currently being tracked. I don’t quite understand why these would be back ported; they would break Liberty with 1.7. Perhaps we can discuss on IRC tomorrow? Rob On 27/11/2015 13:58, "Thomas Goirand"

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

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 release of Mitaka. Could you please make sure that all of these Django 1.9

[openstack-dev] [horizon] Supporting Django 1.9

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 have fixes for it ASAP. I already have bugs against some of the packages I maintain: https://bugs.debian.org/806365 https://bugs.debian.org/806362 Any help (patches sent upstream

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] Supporting Django 1.9

On 27/11/15 10: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 have fixes for it ASAP. I > already have bugs against some of the packages I maintain: I would expect upstream to go the same route

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

Sent from Nine<http://www.9folders.com/> From: Kyle Mestery <mest...@mestery.com> Sent: Nov 25, 2015 8:18 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects On Wed, Nov 2

[openstack-dev] [Horizon][Access and Security] ICMP type, ICMP code 'ValidationError' query

While inputing 'ICMP type' and 'ICMP code' at [1], validation is done which raises 'ValidationError', at [2] so if validation fails corresponding value is set to None. Then why is ValidationError raised again in [3]. Where is 'ValidationError' at [3] caught? [1]

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

I have some questions on option (c) and would like to make sure we are on the same page. Thanks, Cathy (c) neutron sub-project repo - [+] Each sub-project can develop a dashboard fast. - [-] It is doable, but the directory tree can be complicated. - [-] Lead to too many repos and the horizon

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

...@gmail.com] Sent: Tuesday, November 24, 2015 9:46 PM To: OpenStack Development Mailing List Subject: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects Hi, Neutron has now various subprojects and some of them would like to implement Horizon supports. Most of them

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

Rob Cresswell (rcresswe) wrote: > 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

[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][Neutron] dashboard repository for neutron subprojects

I like the idea of doing a Horizon plugin, similar to a devstack plugin... So choice (c) is my preference, given my current understanding. May be good to try it on one subproject and see how it works out. Would give a concrete example to discuss. Regards, Paul Michali (pc_m) On Wed, Nov 25,

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

<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [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

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

On Wed, Nov 25, 2015 at 1:06 AM, Armando M. wrote: > > > On 24 November 2015 at 21:46, Akihiro Motoki wrote: > >> Hi, >> >> Neutron has now various subprojects and some of them would like to >> implement Horizon supports. Most of them are additional

[openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

Hi, Neutron has now various subprojects and some of them would like to implement Horizon supports. Most of them are additional features. I would like to start the discussion where we should have horizon support. [Background] Horizon team introduced a plugin mechanism and we can add horizon

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

Hi Akihiro, Great initiative. On Wed, Nov 25, 2015 at 10:46 AM, Akihiro Motoki wrote: > Hi, > > Neutron has now various subprojects and some of them would like to > implement Horizon supports. Most of them are additional features. > I would like to start the discussion where

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

On 24 November 2015 at 21:46, Akihiro Motoki wrote: > Hi, > > Neutron has now various subprojects and some of them would like to > implement Horizon supports. Most of them are additional features. > I would like to start the discussion where we should have horizon support. > >

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

On Wed, Nov 25, 2015 at 12:06 PM, Armando M. wrote: > > > On 24 November 2015 at 21:46, Akihiro Motoki wrote: > >> Hi, >> >> Neutron has now various subprojects and some of them would like to >> implement Horizon supports. Most of them are additional

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

<openstack-dev@lists.openstack.org > <mailto:openstack-dev@lists.openstack.org>> > Date: Thursday, 19 November 2015 20:39 > To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org > <mailto:openstack-d

Re: [openstack-dev] [horizon][bug] Mitigation to BREACH vulnerability

On Fri, Nov 20, 2015 at 10:00:30PM +, BARTRA, RICK wrote: > Until django releases an official patch for the BREACH vulnerability, I think > we should take a look at django-debreach. The django-debreach package > provides some, possibly enough, protection against a BREACH attack. Its >

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

tack Development Mailing List (not for usage questions)" >> <openstack-dev@lists.openstack.org> >> Date: Thursday, 19 November 2015 20:39 >> To: "OpenStack Development Mailing List (not for usage questions)" < >> openstack-dev@lists.openstack.org> &

[openstack-dev] [horizon][bug] Mitigation to BREACH vulnerability

Until django releases an official patch for the BREACH vulnerability, I think we should take a look at django-debreach. The django-debreach package provides some, possibly enough, protection against a BREACH attack. Its integration to Horizon is clear by following the configuration found here:

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

o: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Date: Thursday, 19 November 2015 20:39 > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org>

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

Thanks Rob, next Tuesday is fine with me. -Zhenguo Sent from my iPhone > On Nov 19, 2015, at 19:19, Rob Cresswell (rcresswe) > wrote: > > 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

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

Let'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) wrote: > Hey folks, > > Our bug list is… rather large.

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

tack-dev@lists.openstack.org>> Date: Thursday, 19 November 2015 20:39 To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [Horizon] Bug day! Yeah! Let

[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] [Horizon] Bug day! Yeah!

On 19/11/15 12:19, Rob Cresswell (rcresswe) wrote: > 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:

[openstack-dev] [Horizon] Redundant checks in form values

In file [1] in `class AddRule` in method `_clean_rule_icmp` why checkups are performed on if `icmp_type` or `icmp_code` is `None` or in range of `-1 to 255`. What I mean here is that in `class AddRule` while values are being accepted from form data and being stored, validators do their job of

Re: [openstack-dev] [Horizon] Redundant checks in form values

In the current AddRule form, validate_port_range is used as a validator, so a value from 1 to 65535 is accepted. I think this is the reason that _clean_rule_icmp check the exact value range. You can improve it as you think. bug 1511748 is a regression of validate_port_range change in

Re: [openstack-dev] [Horizon] Redundant checks in form values

On Thu, Nov 19, 2015 at 3:10 AM, Akihiro Motoki wrote: > In the current AddRule form, validate_port_range is used as a validator, > so a value from 1 to 65535 is accepted. > I think this is the reason that _clean_rule_icmp check the exact value range. > You can improve it as

Re: [openstack-dev] [Horizon] Handling of 202 response code

Thanks Matthias for educating me. As there is no universal solution to this issue, I will check if launch instance page strategy will work out for this case. Regards, Saravanan KR On 11/04/2015 03:47 PM, Matthias Runge wrote: On 04/11/15 09:25, Saravanan KR wrote: There may be multiple

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

> it as a > >>>> "Work in progress", and make it clear in the commit message > that you > >>>> aren't planning further work on this, so the patch is available for > >>>> adoption. That way somebody else may be able to pick this up and &g

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

;>> way (I can't propose code written by somebody else) and I can't > > spend > > >>>> significant time on it right now. > > >>>> Would you or Anton be willing to propose whatever code and > > >>>> documentation &

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

atever code and > >>>> documentation > >>>> you have to Horizon? It doesn't have to be complete; it doesn't need > to > >>>> have grammar cleaned up or anything like that. You could mark it as a > >>>> "Work in progress", and make it

[openstack-dev] [horizon][infra] Horizon gate currently broken

Hello, it looks like Horizon gate jobs (esp. the npm-run-lint jobs) are currently timing out, and it looks like a networking issue. I opened https://bugs.launchpad.net/horizon/+bug/1514734 to track this. Matthias __

[openstack-dev] [Horizon] Handling of 202 response code

Hello, How are the HTTP status code 202 response (from nova) is handled in Horizon to know the asynchronous operation is completed? Background: I am working on Bug #1506429 [1] where invoking 'Detach Interface' initiates the detaching and refreshes the page. But the interface which is

Re: [openstack-dev] [Horizon] Handling of 202 response code

On 04/11/15 09:25, Saravanan KR wrote: > There may be multiple solutions: > 1) Waiting for the synchronous and then respond > 2) Do not trigger page refresh and respond with Operation in progress > 3) If there is a mechanism to know delete in progress, do not list the > interface > > To decide

[openstack-dev] [Horizon] Meetings Canceled for Nov 4

Due to recent summit and many folks being on vacation, both the Horizon and Horizon Drivers meeting are canceled for Nov 4. We will resume on November 11. David __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [Horizon] unit test improvements: work with DOM, not raw HTML strings?

+1 here. While the exact library choice may still be a topic for the discussion, unit tests clearly shouldn't hardcode html stings inside, it is too fragile. On Fri, 23 Oct 2015 at 02:00, Diana Whitten wrote: > Richard, > > I'm absolutely with you ... I've been bitten by

Re: [openstack-dev] [Horizon] unit test improvements: work with DOM, not raw HTML strings?

Richard, I'm absolutely with you ... I've been bitten by these very tests recently when changing a class in a simple template. If anyone wants to override these templates in the future, then they are forced to fight this 'expected_string' test as well. I think this is a good idea. - Diana On

[openstack-dev] Horizon social meetup in Tokyo

Hi Horizon team, Doug and I are planning a horizon social meetup in Tokyo. As you may know, it is planned on Monday Oct 26. 10/26 20:00 - Torikaku at Shinagawa Intercity (とりかく 品川インターシティ店) The location is:

[openstack-dev] [Horizon] Horizon social meetup in Tokyo

I resent my mail as I forgot to add [Horizon] tag. 2015-10-22 23:50 GMT+09:00 Akihiro Motoki : > Hi Horizon team, > > Doug and I are planning a horizon social meetup in Tokyo. > As you may know, it is planned on Monday Oct 26. > > 10/26 20:00 - > Torikaku at Shinagawa Intercity

[openstack-dev] [Horizon] Mitaka schedule and etherpads

The schedule for Horizon is published [1] and the initial etherpads are linked [2]. Happy typing. Looking forward to seeing everyone next week. David [1] http://mitakadesignsummit.sched.org/overview/type/horizon [2] https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads#Horizon

[openstack-dev] [horizon] - Overview page based in configurable widgets

Hello, I have a proposal in order to improve the Overview page in Horizon. The main idea is create a new Overview page based in configurable widgets. You can check it in https://blueprints.launchpad.net/horizon/+spec/overview-page-widget-based If any of you know other ideas like this, please

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

ic and you summarize your points >very nicely! > > I wish you¹d responded to this thread, though: >https://openstack.nimeyo.com/58582/openstack-dev-horizon-patterns-for-angu >lar-panels, because it is talking about the same problem. This is option >3 I mentioned there and I do think

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

Hi Doug! I think the is a great discussion topic and you summarize your points very nicely! I wish you’d responded to this thread, though: https://openstack.nimeyo.com/58582/openstack-dev-horizon-patterns-for-angular-panels, because it is talking about the same problem. This is option 3 I

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

I have two suggestions for handling both new panels and refactoring existing panels that I think could benefit us in the future: 1) When we are creating a panel that's a major refactor of an existing it should be a new separate panel, not a direct code replacement of the existing panel 2) New

[openstack-dev] [Horizon] Liberty RC2 available

Hello everyone, In order to include last-minute translations updates and fix a couple of issues, a new liberty release candidate was created for Horizon. RC2 tarballs are available at: https://launchpad.net/horizon/liberty/liberty-rc2 Unless new release-critical issues are found that warrant a

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

t <openstack-dev@lists.openstack.org>Cc:Subject: [openstack-dev] [horizon][keystone]Date: Tue, Oct 6, 2015 2:13 PM  Dear AllOne of my students, Anton Brida, has developed an Attribute Mapping GUIfor Horizon as part of his MSc project. Attribute mappings are anessential, though complex, part

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

al message - From: David Chadwick <d.w.chadw...@kent.ac.uk> To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org> Cc: Subject: [openstack-dev] [horizon][keystone] Date: Tue, Oct 6, 2015 2:13 PM Dear All One of my stud

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

could get credit for the work he has done. Doug Fish - Original message - From: David Chadwick <d.w.chadw...@kent.ac.uk> To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org> Cc: Subject: [openstack-dev] [horizon][keyston

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

ck <d.w.chadw...@kent.ac.uk> > To: OpenStack Development Mailing List > <openstack-dev@lists.openstack.org> > Cc: > Subject: [openstack-dev] [horizon][keystone] > Date: Tue, Oct 6, 2015 2:13 PM > > Dear All > > One of my students, Anto

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

ning further work on this, so the patch is available for >>> adoption. That way somebody else may be able to pick this up and work on >>> it in the future, but Anton could get credit for the work he has done. >>> >>> Doug Fish >>> >>>

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

ould mark it as a >>>> "Work in progress", and make it clear in the commit message that you >>>> aren't planning further work on this, so the patch is available for >>>> adoption. That way somebody else may be able to pick this up and >>>

[openstack-dev] [horizon][keystone]

Dear All One of my students, Anton Brida, has developed an Attribute Mapping GUI for Horizon as part of his MSc project. Attribute mappings are an essential, though complex, part of federated Keystone. Currently they can only be created as JSON objects in the config file. The Horizon code allows

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] Selenium is now green - please pay attention to it

Thanks for your work on this Richard! A good place to check this is during code reviews. If you see a patch causing these tests to fail, that's a good reason to -1! Sent from my iPhone > On Sep 30, 2015, at 10:45 PM, Richard Jones wrote: > > Hi folks, > > Selenium

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

On 2015-10-01 18:38:49 + (+), Rob Cresswell (rcresswe) wrote: > 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

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

Hi folks, Selenium tests "gate-horizon-selenium-headless" are now green in master again. Please pay attention if it goes red. I will probably notice, but if I don't, and you can't figure out what's going on, please feel free to get in touch with me (r1chardj0n3s on IRC in #openstack-horizon, or

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

eptember 2015 04:11 To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [Horizon] Horizon Productivity Suggestion I agree with Travis that 2-3 minutes is not en

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

uestions)" < > openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [Horizon] Horizon Productivity Suggestion > > I agree with Travis that 2-3 minutes is not enough, that may not be even > enough to talk about one bug. :) > > We could save some time if

[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] Horizon Productivity Suggestion

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 (rcresswe)" wrote: >Hi folks,

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

I agree with Travis that 2-3 minutes is not enough, that may not be even enough to talk about one bug. :) We could save some time if we have someone monitoring the bugs/feature and publish the high priority item into a report - something similar to what Keystone does [1]. Reviewers can look this

Re: [openstack-dev] [Horizon] [Cinder] [Keystone] Showing Cinder quotas for non-admin users in Horizon

If I understand correctly, the issue has been properly fixed with the Ivan's patch [1]. Thanks, Ivan! [1] https://review.openstack.org/#/c/225891/ On Wed, Sep 16, 2015 at 2:53 PM Ivan Kolodyazhny wrote: > Hi Timur, > > To get quotas we need to retrieve project information from

Re: [openstack-dev] [Horizon] [Cinder] [Keystone] Showing Cinder quotas for non-admin users in Horizon

Hi Timur, To get quotas we need to retrieve project information from the Keystone. Unfortunately, Keystone set "admin_required" rule by default [1] in their API. We can handle it and raise 403 if Keystone return this error only. [1]

[openstack-dev] [horizon] Mitaka Summit Topic Proposals

It's time to express your topic proposals for the Mitaka summit. In order to provide an accessible tool for all geographies, we'll be compiling session topics on an etherpad again for Mitaka. https://etherpad.openstack.org/p/horizon-mitaka-summit Please add your ideas there and follow the brief

[openstack-dev] [horizon] PTL Candidacy

I would like to announce my candidacy for Horizon PTL for Mitaka. I've been contributing to Horizon since the Grizzly cycle and I've had the honor of serving as PTL for the past four cycles. Over the past couple of releases, our main goal has been to position Horizon for the future while

[openstack-dev] [Horizon] [Cinder] [Keystone] Showing Cinder quotas for non-admin users in Horizon

Hi all! It seems that recent changes in Cinder policies [1] forbade non-admin users to see the disk quotas. Yet the volume creation is allowed for non-admins, which effectively means that from now on a volume creation in Horizon is free for non-admins (as soon as quotas:show rule is propagated

Re: [openstack-dev] [Horizon]Let's take care of our integration tests

Of course, your question confused me. As you switched to selenium tests. To run integration tests, ./run_tests.sh --integration which is also documented in ./run_tests.sh --help David On Fri, Sep 11, 2015 at 10:25 AM, David Lyle wrote: > Oops! > > ./run_tests.sh

Re: [openstack-dev] [Horizon]Let's take care of our integration tests

Is there any documentation to run the tests locally? Doing ./run_tests.sh --only-selenium skips a lot of tests. Is that the recommended way? -Rajat On Thu, Sep 10, 2015 at 3:54 PM, David Lyle wrote: > I completely agree about monitoring for integration test failures and >

Re: [openstack-dev] [Horizon]Let's take care of our integrationtests

t for usage questions)" <openstack-dev@lists.openstack.org>Cc:Subject: Re: [openstack-dev] [Horizon]Let's take care of our integration testsDate: Fri, Sep 11, 2015 11:39 AM  Of course, your question confused me. As you switched to selenium tests.To run integration tests,./run_tests.sh --in

Re: [openstack-dev] [Horizon]Let's take care of our integration tests

raj On Fri, Sep 11, 2015 at 10:11 AM, Rajat Vig wrote: > Is there any documentation to run the tests locally? > Doing ./run_tests.sh --only-selenium skips a lot of tests. Is that the > recommended way? > > -Rajat > > On Thu, Sep 10, 2015 at 3:54 PM, David Lyle

Re: [openstack-dev] [Horizon]Let's take care of our integration tests

Oops! ./run_tests.sh --only-selenium only skips the non-selenium tests. It works as intended. ./run_tests.sh --with-selenium will run all tests. Both of which are documented in the help of run_tests.sh David On Fri, Sep 11, 2015 at 10:23 AM, David Lyle wrote: > raj > > On

[openstack-dev] [horizon] Patterns for Angular Panels

"A pattern, apart from the term's use to mean Template is a discernible regularity in the world or in a manmade design. As such, the elements of a pattern repeat in a predictable manner." -https://en.wikipedia.org/wiki/Pattern Hello horizon-eers, We have made some progress towards angular

Re: [openstack-dev] [horizon] [keystone] [docs] Two kinds of 'region' entity: finding better names for them

elopment Mailing List \(not for usage questions\)" > > <openstack-dev@lists.openstack.org> > > Date: 07/09/2015 01:17 PM > > Subject: Re: [openstack-dev] [horizon] [keystone] [docs] Two kinds > > of 'region' entity: finding better names for them > > > > Had th

[openstack-dev] [Horizon]Let's take care of our integration tests

It looks like we've reached the point where our Horizon integration tests are functional again. Thanks for your work on this Timur! (Offer for beer/hug at the next summit still stands) I'd like to have these tests voting again ASAP, but I understand that might be a bit risky at this point. We

Re: [openstack-dev] [Horizon]Let's take care of our integration tests

I completely agree about monitoring for integration test failures and blocking until the failure is corrected. The hope is to make sure we've stabilized the integration testing framework a bit before reenabling to vote. Thanks Timur, I know this has been a considerable undertaking. David On

<    4   5   6   7   8   9   10   11   12   13   >