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

Just caught up with Kevin on IRC. If this is inside the Neutron tree, then support should live in the Horizon repo; similar to routers, floating ips etc. My initial, incorrect understanding was that it was more akin to lbaas or vpnaas. Rob On 6 February 2017 at 10:50, Kevin Benton

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

Well the UIs for the extensions inside the main Neutron repo are in the main horizon repo so far (e.g. routers, floating IPs, security groups, etc). LBaaS is a separate repo with separate devs so it makes sense to me that it would have its own UI repo. Trunks would be the the first extension that

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] [neutron] Horizon support for Neutron Trunks - PTL approval needed

That idea has merit, though I don't know what the scope for such a 'neutron-ui' might be. I'm definitely supportive of the Neutron Trunks UI efforts, but it'd be good to get an answer on this scope question before rolling along and creating the project. Richard On 6 February 2017 at 12:14,

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

If the horizon team would like neutron features to live outside, I wonder if it would make more sense to create a new 'neutron-ui' repo instead of it being trunk specific. That way we don't have to come up with a new repo for every new feature that needs a horizon UI. On Feb 3, 2017 09:26, "Bence

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

Hi All, I'd like to add support for Neutron Trunks [1][2] into Horizon together with a few colleagues in the Pike cycle. We thought of writing a new Horizon plugin [3] for that purpose. That way I hope to keep it optional for deployment and minimize the maintenance cost for the Horizon core team.

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

Hi folks, The mad rush to RC1 concluded this week with RC1 now tagged and the stable/ocata branch created. We've got a couple of bugfixes that should have made the RC1 release but just missed out so we're going to try to get those in for RC2; otherwise RC1 is a good release, we can all be happy

[openstack-dev] [horizon] horizon 11.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for horizon for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/horizon/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

[openstack-dev] [Horizon] Meeting at 20:00 UTC this Wednesday, 1st February

Hi folks, The Horizon team will be having our next meeting at 20:00 UTC this Wednesday, 1st February in #openstack-meeting-3 Meeting agenda is here: https://wiki.openstack.org/wiki/Meetings/Horizon Anyone is welcome to to add agenda items and everyone interested in Horizon is encouraged to

[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

On Thu, Jan 26, 2017 at 9:37 PM, Rob Cresswell wrote: > I'll put up Security Groups and Floating IPs once they start moving > (maintaining huge patch chains is a waste of time) ​Huge +1!​ Cheers, Lingxian Kong (Larry)

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

On Fri, Jan 27, 2017 at 12:28 AM, Rob Cresswell < robert.cressw...@outlook.com> wrote: > 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

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 non-candidacy

Hi folks, I won't be standing for PTL for the Pike release. Ocata has been quite the ride, and I will continue to be a contributor to Horizon after this release. Thanks for giving me a go in the big seat, and I look forward to supporting whoever steps up as PTL for Pike! Richard

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

his is great. :) Kevin From: Lingxian Kong [anlin.k...@gmail.com] Sent: Wednesday, January 25, 2017 2:23 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [horizon] FFE Request Hi, Rob, First, thanks for your work! What's your plan for the ot

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

his is great. :) Kevin From: Lingxian Kong [anlin.k...@gmail.com<mailto:anlin.k...@gmail.com>] Sent: Wednesday, January 25, 2017 2:23 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [horizon] FFE Request Hi, R

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

Hi, guys, Sorry for recalling this thread after 1 year, but we are currently suffering from the poor performance issue for our public cloud. As usage of our customers keeps growing, we are at a stage that should seriously pay more attention to horizon performance problem, so Google took me to

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

Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [horizon] FFE Request > > Hi, Rob, > > First, thanks for your work! > > What's your plan for the other two tabs (security group, floatingip)? > I could see the split is very helpful no matter from pe

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

(not for usage questions) Subject: Re: [openstack-dev] [horizon] FFE Request Hi, Rob, First, thanks for your work! What's your plan for the other two tabs (security group, floatingip)? I could see the split is very helpful no matter from performance perspective and both useful from end user's

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

Hi Rob, FFE granted for those two in-flight patches. On 26 January 2017 at 09:23, Lingxian Kong wrote: > Hi, Rob, > > First, thanks for your work! > > What's your plan for the other two tabs (security group, floatingip)? I > could see the split is very helpful no matter

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

Hi, Rob, First, thanks for your work! What's your plan for the other two tabs (security group, floatingip)? I could see the split is very helpful no matter from performance perspective and both useful from end user's perspective. BTW, a huge +1 for this FFE! Cheers, Lingxian Kong (Larry)

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

+1We 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/01/2017 8:07 AM, Rob Cresswell wrote: o/  I'd like to request an FFE on 

[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

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

I prepared a patch that forces the use of 2.40 api version if it's available for that particular endpoint. Instead of waiting for the microversion patch, I simply copied the needed fragments from it -- we can fix that later once we have proper microversion support implemented.

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

It was done like that to circumvent the existing possibility DoS-like usage requests when there are thousands of instances. Some of the history behind that decision can be found in the spec discussions [1]. And an easier to read spec can be found here [2]. [1]

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

No, for some reason Nova will now always limit the number of entries it sends in a single response, no matter what microversion you use. If you use microversion of at least 2.40, it will let you request more responses, to get all the entries. I don't know why they did it like that. On Tue, Jan

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] feature freeze exception request -- nova simple tenant usages api pagination

[I'm on vacation, so can't look into this too deeply, sorry] I'm not sure I follow Rob's point here. Does the patch https://review.openstack.org/#/c/410337 just check the version to see if it's >= 2.40 and take action appropriately? I don't see how it changes anything to force requesting 2.40

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

Yes, to do it differently we need to add the microversion support patch that you are working on, and make use of it, or write a patch that has equivalent functionality. On Fri, Jan 20, 2017 at 6:57 PM, Rob Cresswell wrote: > Just a thought: With the way we

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] Weekly wrap-up

Hi folks, We had a relatively brief Horizon meeting this week[1] in which I announced the (planned) Feature Freeze that took place this week. This means that all blueprint-related patches are now put on hold until after the Ocata release of Horizon is done. In the mean time, only bug patches and

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

FFE granted for the three patches. We need to support that nova API change. On 20 January 2017 at 01:28, Radomir Dopieralski wrote: > I would like to request a feature freeze exception for the following patch: > > https://review.openstack.org/#/c/410337 > > This patch

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

I would like to request a feature freeze exception for the following patch: https://review.openstack.org/#/c/410337 This patch adds support for retrieving the simple tenant usages from Nova in chunks, and it is necessary for correct data given that related patches have been already merged in

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

Hi folks, Welcome back from the break - I hope you had a good one! We kicked off 2017 with our first weekly meeting[1] that covered a few areas, notably the impending Ocata feature freeze next week. We also talked a little about the Pike PTG which is just over a month away, and I've started a

[openstack-dev] [horizon] Timeout issue

Hi, Maybe someone can help or give me some pointers. On horizon I am trying to attach a network interface to a router. When I do this I get the following error on horizon: “Danger: There was an error submitting the form. Please try again.” When I refresh the page I see that the operation has

[openstack-dev] [Horizon] No meeting this week, and most likely none next week

Hi folks, I'll be around but since most everyone else won't be, let's skip the meeting this week. I won't be around next week, so I won't be able to run the meeting then ether. Richard __ OpenStack Development Mailing

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

Yep, Rob's correct, that's the intent. There's also plenty of non-WIP high priority patches in the starred list :-) On 16 December 2016 at 23:31, Rob Cresswell (rcresswe) wrote: > I think the intent is to get eyes on those patches, to prevent a 1000 line > rewrite only for a

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] Weekly wrap-up

I wonder if it really makes sense to put WIP patches on the priority list. I think it's a bit counter-productive, considering that the prioritizing of patches was supposed to make them merge faster -- but we don't want to merge WIP patches, do we? On Fri, Dec 16, 2016 at 5:31 AM, Richard Jones

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

Hi folks, No Horizon meeting next week! I'll be around the week after (28th December) so if anyone else is around we can totally have a meeting then. Things that have happened this week, including in the team meeting[1] Ocata-2 was tagged! xstatic-angular-bootstrap 2.2.0.0 was released, which

[openstack-dev] [Horizon] Meeting at 20:00UTC this Wednesday, 14th December

Hi folks, The Horizon team will be having our next meeting at 20:00 UTC this Wednesday, 14th December in #openstack-meeting-3 Meeting agenda is here: https://wiki.openstack.org/wiki/Meetings/Horizon If we have spare time this meeting I think we should look into getting some patches reviewed

[openstack-dev] [Horizon] End of week wrap-up

Hi folks, Ocata-2 will be released next week and we've had little success getting the priority patches reviewed, unfortunately. We have had some wins though, getting the upper-constraints stability patches into stable Mitaka, which means we can be more confident releasing the angular-bootstrap

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

I also like Radomir’s version. From: "Ramirez, Eddie" <eddie.rami...@intel.com> Reply-To: OpenStack List <openstack-dev@lists.openstack.org> Date: Wednesday, December 7, 2016 at 11:28 AM To: OpenStack List <openstack-dev@lists.openstack.org> Subject: Re: [opensta

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

Very fixed, much color, so right. Wow. +1 Radomir’s From: Rob Cresswell (rcresswe) [mailto:rcres...@cisco.com] Sent: Wednesday, December 7, 2016 4:50 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [H

[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] Draft team mascot

Radomir’s version has my vote. On 7 Dec 2016, at 10:11, Radomir Dopieralski > wrote: Here, fixed. On Wed, Dec 7, 2016 at 10:54 AM, Radomir Dopieralski >wrote: That looks kinda like a

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

Here, fixed. On Wed, Dec 7, 2016 at 10:54 AM, Radomir Dopieralski wrote: > That looks kinda like a white baboon. It definitely doesn't look like Doge > -- wrong color, wrong head. I think the legs are too long too. > > On Wed, Dec 7, 2016 at 10:31 AM, Timur Sufiev

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

That looks kinda like a white baboon. It definitely doesn't look like Doge -- wrong color, wrong head. I think the legs are too long too. On Wed, Dec 7, 2016 at 10:31 AM, Timur Sufiev wrote: > I still think this one https://wtf.jpg.wtf/0c/10/1479414543- >

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

I still think this one https://wtf.jpg.wtf/0c/10/1479414543-0c1052f7c2f9990b6b0c472076594cb1.jpeg is the best :). On Wed, Dec 7, 2016 at 1:07 AM Jason Rist wrote: > On 12/06/2016 01:48 PM, Richard Jones wrote: > > >> On 6 Dec 2016, at 20:19, Richard Jones

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

On 12/06/2016 01:48 PM, Richard Jones wrote: > >> On 6 Dec 2016, at 20:19, Richard Jones 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) >

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

>> On 6 Dec 2016, at 20:19, Richard Jones 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) wrote: > Are we missing an attachment / link ?

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

[openstack-dev] [Horizon] Draft team mascot

Hi folks, Please let me know what you think (by December 12) of this draft for our Horizon team mascot. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [Horizon] Meeting at 20:00 UTC this Wednesday, 7th December

Hi folks, The Horizon team will be having our next meeting at 20:00 UTC this Wednesday, 7th December in #openstack-meeting-3 Meeting agenda is here: https://wiki.openstack.org/wiki/Meetings/Horizon If we have spare time this meeting I think we should look into getting some patches reviewed

[openstack-dev] [Horizon] End of week wrap-up

Hi folks, A bit delayed because of a bonkers conference this weekend, but here's what went on last week in Horizon land. During the team meeting[1] I reiterated that there's a priority list of patches for review that has still been needing attention[2], and that we'd start looking at pulling

[openstack-dev] [Horizon][Keystone] Weekly meeting log (2016/12/1)

Hi folks, The meeting bot disappeared during the meeting so the record is incomplete. The last 20 minutes are still in the channel log here: http://eavesdrop.openstack.org/irclogs/%23openstack-meeting-cp/%23openstack-meeting-cp.2016-12-01.log.html#t2016-12-01T20:42:08 Richard

[openstack-dev] [Horizon] [Keystone] cross-project meeting Thursday 1st December 2000UTC

Hi folks, The next Keystone/Horizon cross-project meeting is this Thursday, 1st December at 2000UTC in #openstack-meeting-cp The agenda is https://etherpad.openstack.org/p/ocata-keystone-horizon Please update that document if you're working on one of the items. Richard

[openstack-dev] [Horizon] Meeting at 20:00 UTC this Wednesday, 30th November

Hi folks, The Horizon team will be having our next meeting at 20:00 UTC this Wednesday, 30th November in #openstack-meeting-3 Meeting agenda is here: https://wiki.openstack.org/wiki/Meetings/Horizon Anyone is welcome to to add agenda items and everyone interested in Horizon is encouraged to

[openstack-dev] [Horizon] End of week wrap-up

Hi folks, This was a bit of a slow-ish week given the number of folks away for Thanksgiving. We had low-turnout Horizon meeting and cancelled the Horizon/Keystone cross-project meeting. In the team meeting[1] we covered: - The patch priority review list, which looks a lot like last week :-( - We

[openstack-dev] [Horizon][Keystone] No Horizon/Keystone cross-project meeting this week

Hi folks, Since so many key people are away on vacation, we'll skip this week's meeting (November 24th). Richard __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [Horizon] Meeting at 20:00 UTC this Wednesday, 23rd November

Hi folks, The Horizon team will be having our next meeting at 20:00 UTC this Wednesday, 23rd November in #openstack-meeting-3 Meeting agenda is here: https://wiki.openstack.org/wiki/Meetings/Horizon Anyone is welcome to to add agenda items and everyone interested in Horizon is encouraged to

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

Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for core > > As a result of the unanimous vote here, I welcome Kenji to the Horizon > Core Team! > > > Richar

[openstack-dev] [Horizon] Zhenguo Niu retiring from Horizon Core Team

Hi folks, Zhenguo Niu has been a core for many cycles, for which I thank him. His focus and time has shifted away from UI though, so he's asked to be removed from the core team. Thanks again, Zhenguo! Richard __

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

k-dev@lists.openstack.org> > Date: Friday, November 18, 2016 at 1:34 AM > To: OpenStack List <openstack-dev@lists.openstack.org> > > > Subject: Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for core > > > > +1 > > > > On Fri, Nov 18, 2016 at 1

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

+1 From: Timur Sufiev <tsuf...@mirantis.com> Reply-To: OpenStack List <openstack-dev@lists.openstack.org> Date: Friday, November 18, 2016 at 1:34 AM To: OpenStack List <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for core

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

usage questions)" < > openstack-dev@lists.openstack.org> > Cc: > Subject: Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for core > Date: Thu, Nov 17, 2016 11:51 AM > > +1 > > On Tue, Nov 15, 2016 at 5:02 AM, Akira Yoshiyama > <akirayoshiy...@gmail.com

[openstack-dev] [Horizon] End of week wrap-up

Hi folks, This week's Horizon goings-on saw several of the priority patches[1] for O-1 land, though more won't make it into that release. O-1 will be tagged in a few hours, once we sort out some issues with the npm test suite introduced with a recent patch. The team meeting this week[2] was a

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 <dkly...@gmail.com>To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org>Cc:Subject: Re: [openstack-dev] [Horizon]

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

+1 On Tue, Nov 15, 2016 at 5:02 AM, Akira Yoshiyama wrote: > +1 > > 2016年11月15日(火) 20:47 Rob Cresswell (rcresswe) : >> >> Big +1 from me >> >> > On 14 Nov 2016, at 00:24, Richard Jones wrote: >> > >> > Hi Horizon core team,

[openstack-dev] [Horizon] Meeting at 20:00 UTC this Wednesday, 16th November

Hi folks, The Horizon team will be having our next meeting at 20:00 UTC this Wednesday, 16th November in #openstack-meeting-3 Meeting agenda is here: https://wiki.openstack.org/wiki/Meetings/Horizon Anyone is welcome to to add agenda items and everyone interested in Horizon is encouraged to

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] Proposing Kenji Ishii for core

+1 2016年11月15日(火) 20:47 Rob Cresswell (rcresswe) : > 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

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] Proposing Kenji Ishii for core

+1 2016-11-14 9:24 GMT+09:00 Richard Jones : > 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 and good knowledge of

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

nal 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, > > Sorry for the delay again, I just got back

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

enstack.org" <openstack-dev@lists.openstack.org>Cc: Haruhiko Katou <har-ka...@ts.jp.nec.com>Subject: [openstack-dev] [Horizon] ui-cookiecutterDate: Tue, Nov 8, 2016 1:24 AM  Hi Horizoners,Thanks for picking up ui-cookiecutter[1] and setting Ocata-2 milestone at summit[2].Thai or Cindy? T

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

+1 On Mon, Nov 14, 2016 at 1:24 AM, 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 and good

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

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 and good knowledge of Horizion and related systems. Please respond with your votes by Friday. Thanks,

[openstack-dev] [Horizon] End of week wrap-up

Hi folks, We had our kickoff Keystone/Horizon cross-project meeting[1] which was super productive, and we've settled on Thursday 2000UTC as the meeting time going forward. We'll meet in #openstack-meeting-cp - details here[2]. The range of topics was broad, both on the Horizon and Keystone side.

Re: [openstack-dev] [horizon] USE_SSL

On Wed, Nov 9, 2016 at 1:56 PM, Rob Cresswell wrote: > Was that ever in local_settings? I couldnt find any mention of it. > Yes, seems to have stopped being used around Kilo: http://docs.openstack.org/kilo/config-reference/content/configure-dashboard.html > The

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,

[openstack-dev] [horizon] USE_SSL

Hi, I have noted that USE_SSL is no longer in local_settings.py I have not had any luck in having google find the background of why this was removed for first django (if it has?) and horizon. >From what I can see, it seems related to django views. Does anyone understand the context of this

[openstack-dev] [Horizon] Meeting at 20:00 UTC this Wednesday, 9nd November

Hi folks, The Horizon team will be having our next meeting at 20:00 UTC this Wednesday, 9nd November in #openstack-meeting-3 Meeting agenda is here: https://wiki.openstack.org/wiki/Meetings/Horizon Anyone is welcome to to add agenda items and everyone interested in Horizon is encouraged to

[openstack-dev] [Horizon] [Keystone] Inaugural weekly cross-project meeting summary

Hi folks, Today we had the first of what will be a regular cross-project meeting series for Horizon and Keystone developers[1]. It was a very productive meeting, and we resolved to continue to keep our ongoing notes and status summaries in the etherpad[2] while still ensuring that BPs or bugs

[openstack-dev] [Horizon] ui-cookiecutter

Hi Horizoners, Thanks for picking up ui-cookiecutter[1] and setting Ocata-2 milestone at summit[2]. Thai or Cindy? Thank you!! I'm maintaining ui-cookiecutter, but I'm ready for transferring it as Horizon subproject. Can I start to create subproject for ui-cookiecutter? Or please let me know

Re: [openstack-dev] [Horizon][DataTables] how to generate a confirmation dialog

Thanks Timur! That's exactly what I needed! On Mon, Nov 7, 2016 at 2:50 AM, Timur Sufiev wrote: > Hi, John, > > the code you're looking for is located here: > https://github.com/openstack/horizon/blob/master/horizon/static/horizon/js/horizon.tables.js#L227-L312 > This is

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][DataTables] how to generate a confirmation dialog

Hi, John, the code you're looking for is located here: https://github.com/openstack/horizon/blob/master/horizon/static/horizon/js/horizon.tables.js#L227-L312 This is bound at https://github.com/openstack/horizon/blob/master/horizon/static/horizon/js/horizon.forms.js#L368-L373 On Sun, Nov 6, 2016

Re: [openstack-dev] [Horizon][DataTables] how to generate a confirmation dialog

Ping. No thoughts on this from anyone? On Nov 4, 2016 9:26 PM, "John Calcote" wrote: > Hi all - > > I don't see a better forum anywhere for this post - please correct me > if I'm wrong. > > I have a django/horizon application. On one page users may delete > objects. I'd

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

Hi all, I've installed Openstack Prod env with Fuel and I would like to customize the dashboard by using my own logo.png and logo-splash.png. I've changed all logo and logo-splash in these folders and restarted services apache2 and memcached :

[openstack-dev] [Horizon][DataTables] how to generate a confirmation dialog

Hi all - I don't see a better forum anywhere for this post - please correct me if I'm wrong. I have a django/horizon application. On one page users may delete objects. I'd like to display a modal dialog confirming the delete before submit. Can anyone tell me if there's a way to tie a

[openstack-dev] [Horizon] End of week (almost) wrap-up

Hi folks, I'm going to be taking a long weekend, so the end of week wrap-up is early by a day :-) Last week was the summit, and I've written up a summary of Horizon-related design summit goings-on[1]. In our meeting this week[2] we covered a few topics, notably: - the removal of the Selenium

[openstack-dev] [Horizon] Meeting at 20:00 UTC this Wednesday, 2nd November

Hi folks, The Horizon team will be having our next meeting at 20:00 UTC this Wednesday, 2nd November in #openstack-meeting-3 Meeting agenda is here: https://wiki.openstack.org/wiki/Meetings/Horizon Anyone is welcome to to add agenda items and everyone interested in Horizon is encouraged to

[openstack-dev] [Horizon] Summit recap

Hi folks, We had several very productive Horizon sessions at the summit last week. Thanks to everyone who was able to contribute, especially the folks from the Keystone project for the combined session. A summary of the discussions and outcomes: == Project Organisation == We will be

Re: [openstack-dev] [Horizon] Rework Access & Security panel

On 27/10/2016 04:15, Adrian Turjak wrote: > Hello OpenstackDevs, > > In our deployment we keep running into a problem where customers forget > about the existence of floating ips once disassociated from an instance, > and when they then need to release them they often can't find where > because

Re: [openstack-dev] [Horizon] Rework Access & Security panel

On 27/10/16 15:11, Adrian Turjak wrote: > seems usual and rather confusing UX. s/usual/unusual/ __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [Horizon] Rework Access & Security panel

Hello OpenstackDevs, In our deployment we keep running into a problem where customers forget about the existence of floating ips once disassociated from an instance, and when they then need to release them they often can't find where because expecting them to be in 'Access & Security' is odd.

[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

[openstack-dev] [Horizon] Summit preparation

Hi folks, Summit's around the corner! Even if you aren't going to be at the summit, we'd appreciate if you could go over the etherpads we're going to be using, to add your valuable input. They're all linked from https://etherpad.openstack.org/p/horizon-ocata-summit and in particular if you have

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

Hi Rob, > -Original Message- > From: Rob Cresswell [mailto:robert.cressw...@outlook.com] > Sent: 2016 október 19, szerda 13:49 > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-d

<    1   2   3   4   5   6   7   8   9   10   >