Re: [openstack-dev] [horizon][neutron] tools/tox_install changes - breakage with constraints

On Thu, 15 Mar 2018, Akihiro Motoki wrote: (1) it makes difficult to run tests in local environment We have only released version of neutron/horizon on PyPI. It means PyPI version (i.e. queens) is installed when we run tox in our local development. Most neutron stadium projects and horizon

Re: [openstack-dev] [horizon][neutron] tools/tox_install changes - breakage with constraints

The current version of proposed patches which drops tox_install.sh works in our CI. Even if we have neutron>=12.0.0 (queens) or horizon>=13.0.0 (queens), if we have "required-projects" in zuul v3 config, tox-sibling role ensures to install the latest master of neutron/horizon. It is okay in our

Re: [openstack-dev] [horizon][neutron] tools/tox_install changes - breakage with constraints

On 2018-03-14 20:46, Andreas Jaeger wrote: > On 2018-03-14 20:39, Andreas Jaeger wrote: >> We now have neutron and horizon in global-requirements and do not need >> to install them anymore with tools/tox_install.sh. >> >> This allows to simplify our jobs and testing. >> >> Unfortunately, the

Re: [openstack-dev] [horizon][neutron] tools/tox_install changes - breakage with constraints

On 2018-03-14 20:39, Andreas Jaeger wrote: > We now have neutron and horizon in global-requirements and do not need > to install them anymore with tools/tox_install.sh. > > This allows to simplify our jobs and testing. > > Unfortunately, the merging caused now the projects that install neutron >

[openstack-dev] [horizon][neutron] tools/tox_install changes - breakage with constraints

We now have neutron and horizon in global-requirements and do not need to install them anymore with tools/tox_install.sh. This allows to simplify our jobs and testing. Unfortunately, the merging caused now the projects that install neutron and horizon via tools/tox_install to break with

Re: [openstack-dev] [horizon] [heat-dashboard] Horizon plugin settings for new xstatic modules

Hi Horizon Team, I reported a bug about lack of ``ADD_XSTATIC_MODULES`` plugin option, and submitted a patch for it. Could you please help to review the patch. https://bugs.launchpad.net/horizon/+bug/1755339 https://review.openstack.org/#/c/552259/ Thank you very much. Best Regards, Xinni On

Re: [openstack-dev] [horizon] [heat-dashboard] Horizon plugin settings for new xstatic modules

Hi Kaz, Thanks for cleaning this up. I put +1 on both of these patches Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Tue, Mar 13, 2018 at 4:48 AM, Kaz Shinohara wrote: > Hi Ivan & Horizon folks, > > > Now we are submitting a couple of patches to have the new

Re: [openstack-dev] [horizon] [devstack] horizon 'network create' panel does not distinguished

Hello Jaewook and everyone, I tried to install upstream/master Horizon+Heat-dashboard, still could not see the error. Maybe a clean installation of devstack could fix the issue. If you want to enable heat-dashboard in current working environment, you can try to install it manually. I share my

Re: [openstack-dev] [horizon] [heat-dashboard] Horizon plugin settings for new xstatic modules

Hi Ivan & Horizon folks, Now we are submitting a couple of patches to have the new xstatic modules. Let me request you to have review the following patches. We need Horizon PTL's +1 to move these forward. project-config https://review.openstack.org/#/c/551978/ governance

Re: [openstack-dev] [horizon] [devstack] horizon 'network create' panel does not distinguished

Hello Jaewook, Very glad to know it. I will add comments to the bug report, and continue to find a better solution to prevent the issue from happening. Best Regards! Xinni On Tue, Mar 13, 2018 at 10:34 AM, Jaewook Oh wrote: > Hello, Xinni. > > I followed your description,

Re: [openstack-dev] [horizon] [devstack] horizon 'network create' panel does not distinguished

Hello, Xinni. I followed your description, and it worked properly :) Can you comment your description in the bug report? https://bugs.launchpad.net/bugs/1755140 It would be very helpful for me or somebody else who doesn't know how to restart the horizon independently! Best Regards, Jaewook.

Re: [openstack-dev] [horizon] [devstack] horizon 'network create' panel does not distinguished

Hello Xinni, Thanks for your kind help and information. I'll try what you said soon :) By the way, I reported this issue in the bug report, if anybody interested in it, please visit https://bugs.launchpad.net/bugs/1755140 Best Regards, Jaewook.

Re: [openstack-dev] [horizon] [devstack] horizon 'network create' panel does not distinguished

The detail of this issue is tracked in https://bugs.launchpad.net/bugs/1755140 and it turned out that it is caused by the older version of the enabled file of the template generator. I strongly recommend to cover this in the release notes. Akihiro 2018/03/13 午前9:45 "Xinni Ge"

Re: [openstack-dev] [horizon] [devstack] horizon 'network create' panel does not distinguished

Hello, Jaewook and everyone It looks like the error is caused by some angular module of heat-dashboard not being loaded correctly. I tried to reproduce it in my devstack by installing stable/queens Horiozn/Heat-dashboard, but couldn't see the same error. Maybe you want to try the following

Re: [openstack-dev] [horizon] [devstack] horizon 'network create' panel does not distinguished

Thanks for feedback! As you said, I got errors in the JavaScript console. Below is the error log : 3bf910c7ae4c.js:652 JQMIGRATE: Logging is active fddd6f634ef8.js:2299 Uncaught TypeError: Cannot read property 'layout' of undefined at Object.25../arrows (fddd6f634ef8.js:2299) at s

Re: [openstack-dev] [horizon] [heat-dashboard] Horizon plugin settings for new xstatic modules

Yes, please do that. We can then discuss in the review about technical details. On Mon, Mar 12, 2018 at 2:54 AM, Xinni Ge wrote: > Hi, Akihiro > > Thanks for the quick reply. > > I agree with your opinion that BASE_XSTATIC_MODULES should not be > modified. > It is much

Re: [openstack-dev] [horizon] [heat-dashboard] Horizon plugin settings for new xstatic modules

Hi, Akihiro Thanks for the quick reply. I agree with your opinion that BASE_XSTATIC_MODULES should not be modified. It is much better to enhance horizon plugin settings, and I think maybe there could be one option like ADD_XSTATIC_MODULES. This option adds the plugin's xstatic files in

Re: [openstack-dev] [horizon] [heat-dashboard] Horizon plugin settings for new xstatic modules

Hi Xinni, 2018-03-09 12:05 GMT+09:00 Xinni Ge : > Hello Horizon Team, > > I would like to hear about your opinions about how to add new xstatic > modules to horizon settings. > > As for Heat-dashboard project embedded 3rd-party files issue, thanks for > your advices in

[openstack-dev] [horizon] [heat-dashboard] Horizon plugin settings for new xstatic modules

Hello Horizon Team, I would like to hear about your opinions about how to add new xstatic modules to horizon settings. As for Heat-dashboard project embedded 3rd-party files issue, thanks for your advices in Dublin PTG, we are now removing them and referencing as new xstatic-* libs. So we

Re: [openstack-dev] [horizon][ptg] Horizon PTG Highlights

On 2018-03-07 00:08:39 +0200 (+0200), Ivan Kolodyazhny wrote: [...] > - we agreed to make go forward with Eventlet by default and make it >configurable to allow native Python threads which are used now >- let's ask the community about their experience with Eventlet >- Eventlet is not

Re: [openstack-dev] [horizon][ptg] Horizon PTG Highlights

On Tue, Mar 6, 2018 at 2:08 PM, Ivan Kolodyazhny wrote: > Horizon needs to fix integration tests > > Ironic UI team wants to have their integration tests based on Horizon tests Not exactly. There are multiple goals, with the central end goal of preventing breaking changes in

Re: [openstack-dev] [horizon][ptg] Horizon PTG Highlights

On 03/06/2018 11:08 PM, Ivan Kolodyazhny wrote: > * Angular and XStatic packages versions > o testing and updating were done mostly manually by Radomir and Rob > o we agreed to update XStatic packages in Rocky if they have > suitable for Horizon versions and we've got

[openstack-dev] [horizon][ptg] Horizon PTG Highlights

Hi team, First of all, I would like to say a thank you to all who was able to attend PTG this time. We'd got very productive discussions with a great team. Below is my short summary related on the etherpad [1]: - Current blueprints and features proposals: - we agreed to allow new

[openstack-dev] [horizon] horizon 13.0.0.0rc2 (queens)

Hello everyone, A new release candidate for horizon for the end of the Queens 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][plugins] Supported Django versions for Horizon in Rocky

Hi team, As was discussed at the weekly meeting on December, 20th, Horizon team is going to bump minimum Django version to the next LTS release which is 1.11. Django 1.8 will be supported at least until April 2018 [2]. In Rocky release, we agreed to support Django 1.11 and Django 2.x as

Re: [openstack-dev] [horizon] collectstatic with custom theme is broken at least since Ocata

Hello Mateusz, thanks for your input. I just want to confirm that a patch was merged in master and backported all the way back to Ocata to fix the bug. details here: https://bugs.launchpad.net/horizon/+bug/1744239 thank you Saverio On 05.02.18 14:54, Mateusz Kowalski wrote: > Hi, > > We

[openstack-dev] [horizon] horizon 13.0.0.0rc1 (queens)

Hello everyone, A new release candidate for horizon for the end of the Queens 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] PTG Planning Etherpad

Hi team, In case if you missed it, it's a friendly reminder that we've got etherpad [1] with Rocky PTG topics proposals. If you're going to attend it or want to get some topic discussed, please add your name and topic to the list [1]. Hope to see you all in Dublin. [1]

[openstack-dev] [horizon][ptl] Rocky PTL Candidacy

Hello Team, I would like to announce my candidacy for PTL of Horizon for Rocky release. I use Horizon since I begin to work with OpenStack in Diablo timeframe. I wasn't active contributor before Pike release, nevertheless, I can see how both Horizon project and community changed over the times.

Re: [openstack-dev] [horizon] collectstatic with custom theme is broken at least since Ocata

Hi, We are running Horizon in Pike and cannot confirm having the same problem as you describe. We are using a custom theme however the folder structure is a bit different than the one you presented in the bug report. In our case we have -

[openstack-dev] [horizon] collectstatic with custom theme is broken at least since Ocata

Hello, I have tried to find a fix to this: https://ask.openstack.org/en/question/107544/ocata-theme-customization-with-templates/ https://bugs.launchpad.net/horizon/+bug/1744239 https://review.openstack.org/#/c/536039/ I am upgrading from Newton to Pike. Here the real question is: how is it

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

Thanks Akihiro I will bring it up on today's meeting. Regards Lajos On 2018-01-31 10:39, Akihiro Motoki wrote: +1 for FFE. I can support it. We need a final ack from our PTL. Akihiro 2018-01-30 5:13 GMT+09:00 Lajos Katona : Hi, I would like to ask for FFE on the

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

+1 for FFE. I can support it. We need a final ack from our PTL. Akihiro 2018-01-30 5:13 GMT+09:00 Lajos Katona : > Hi, > > I would like to ask for FFE on the neutron-trunk-ui blueprint to let the > admin panel for trunks be accepted for Queens. > > Based on discussion

[openstack-dev] [horizon] FFE Request for Queens

Hi, I would like to ask for FFE on the neutron-trunk-ui blueprint to let the admin panel for trunks be accepted for Queens. Based on discussion on IRC (http://eavesdrop.openstack.org/irclogs/%23openstack-horizon/%23openstack-horizon.2018-01-29.log.html#t2018-01-29T14:36:58 ) the remaining

Re: [openstack-dev] [horizon][packaging] django-openstack-auth retirement

2018-01-27 2:45 GMT+09:00 Jeremy Stanley : > On 2018-01-24 08:47:30 -0600 (-0600), Monty Taylor wrote: > [...] >> Horizon and neutron were updated to start publishing to PyPI >> already. >> >> https://review.openstack.org/#/c/531822/ >> >> This is so that we can start working on

Re: [openstack-dev] [horizon][packaging] django-openstack-auth retirement

On 2018-01-24 08:47:30 -0600 (-0600), Monty Taylor wrote: [...] > Horizon and neutron were updated to start publishing to PyPI > already. > > https://review.openstack.org/#/c/531822/ > > This is so that we can start working on unwinding the neutron and > horizon specific versions of jobs for

Re: [openstack-dev] [horizon][packaging] django-openstack-auth retirement

On 01/24/2018 08:25 AM, Jeremy Stanley wrote: On 2018-01-23 23:19:59 +0900 (+0900), Akihiro Motoki wrote: [...] Horizon usually does not publish its releases to PyPI, so I think what we can do is to document it. P.S. The only exceptions on PyPI horizon are 12.0.2 and 2012.2 releases. 12.0.2

Re: [openstack-dev] [horizon][packaging] django-openstack-auth retirement

On 2018-01-23 23:19:59 +0900 (+0900), Akihiro Motoki wrote: [...] > Horizon usually does not publish its releases to PyPI, so I think what > we can do is to document it. > > P.S. > The only exceptions on PyPI horizon are 12.0.2 and 2012.2 releases. > 12.0.2 was released last week but I don't know

Re: [openstack-dev] [horizon][packaging] django-openstack-auth retirement

2018-01-22 20:30 GMT+09:00 Jeremy Stanley : > On 2018-01-22 14:40:49 +0900 (+0900), Akihiro Motoki wrote: > [...] >> If you install horizon and django-openstack-auth by using pip (instead >> of distribution packages), please uninstall django-openstack-auth >> python package

Re: [openstack-dev] [horizon][packaging] django-openstack-auth retirement

On 2018-01-22 14:40:49 +0900 (+0900), Akihiro Motoki wrote: [...] > If you install horizon and django-openstack-auth by using pip (instead > of distribution packages), please uninstall django-openstack-auth > python package before upgrading horizon. > Otherwise, "openstack_auth" module is

[openstack-dev] [horizon][packaging] django-openstack-auth retirement

Hi, packaging teams and operators This mail is the announcement of retirement of django-openstack-auth python package in the Queens release. Horizon team merged the code of django-openstack-auth into the horizon repo mainly from the maintenance reason. For more detail, see the blueprint

[openstack-dev] [horizon][trunk][ngdetails] Trunk admin panel and changes related to ngdetails patches

Hi Horizon Team I read the meeting log (http://eavesdrop.openstack.org/meetings/horizon/2018/horizon.2018-01-10-20.00.log.html) and if I understand well the proposal is to merge part of the ngdetails patches (https://review.openstack.org/#/q/topic:bug/1681627+(status:open) ) in Queens, and

Re: [openstack-dev] [horizon] Adding Ivan Kolodyazhny to the Horizon Core team

Thanks Ying and the team! I'm happy to be a part of our Horizon Core Reviewers team. I have a bit more opportunity to make Horizon better now. Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Mon, Dec 18, 2017 at 2:39 PM, Chenjun Shen wrote: > Congratulations to

Re: [openstack-dev] [horizon] Adding Ivan Kolodyazhny to the Horizon Core team

Congratulations to Ivan! On Sun, Dec 17, 2017 at 1:39 PM, Akihiro Motoki wrote: > Welcome Ivan to the team! > > Akihiro > > 2017-12-16 1:52 GMT+09:00 Ying Zuo (yinzuo) : > > Hi everyone, > > > > > > > > After some discussion with the Horizon Core team, I am

Re: [openstack-dev] [horizon] Adding Ivan Kolodyazhny to the Horizon Core team

Welcome Ivan to the team! Akihiro 2017-12-16 1:52 GMT+09:00 Ying Zuo (yinzuo) : > Hi everyone, > > > > After some discussion with the Horizon Core team, I am pleased to announce > that we are adding Ivan Kolodyazhny to the team. Ivan has been actively > contributing to Horizon

Re: [openstack-dev] [horizon] Adding Ivan Kolodyazhny to the Horizon Core team

Ivan, Congratulations! Jay On 12/15/2017 10:52 AM, Ying Zuo (yinzuo) wrote: Hi everyone, After some discussion with the Horizon Core team, I am pleased to announce that we are adding Ivan Kolodyazhny to the team. Ivan has been actively contributing to Horizon since the beginning of the

[openstack-dev] [horizon] Adding Ivan Kolodyazhny to the Horizon Core team

Hi everyone, After some discussion with the Horizon Core team, I am pleased to announce that we are adding Ivan Kolodyazhny to the team. Ivan has been actively contributing to Horizon since the beginning of the Pike release. He has worked on many bug fixes, blueprints, and performed thorough

Re: [openstack-dev] [horizon] Fetch resources in parallel

Hi Team, It's me again and I've got some new tests results [3]. I'd got the following test environment: - 3 controllers - 2 computes - 1 node with horizon - 60 items per page - 60 instances launched with only 3 different images. As always, any feedback is welcome [3]

Re: [openstack-dev] [horizon][heat] heat-dashboard is ready for Horizon team's review

Hi all, I've confirmed a couple of things below. - heat-dashboard is released in queens-2 Thx! Rico :) you can see the release tag 1.0.0 in http://git.openstack.org/cgit/openstack/heat-dashboard/ - Dropped heat related code from horizon repo. Thx! Akihiro :)

Re: [openstack-dev] [horizon][heat] heat-dashboard is ready for Horizon team's review

Hi Akihiro, Horizon team, Thanks a lot for your help as always:) >> Thanks for updating the horizon patch. Is it ready to merge from the >> perspective of heat dashboard team? Yes, we think it's ready to be merged. >> Perhaps the system panel needs to be pluggable. >> As of now, it sounds no

Re: [openstack-dev] [horizon] Fetch resources in parallel

Hi Team, Last week we had a hot discussion about this topic at the meeting [6]. We still don't have an agreement how to go forward with it. As was requested, I did some perf testing with a current approach [3]. TBH, these tests results don't show real data but look realistic. I used the same VM

Re: [openstack-dev] [horizon][heat] heat-dashboard is ready for Horizon team's review

I have another announcement on heat-dashboard split out. I moved the horizon bugs related to heat to heat-dashboard launchpad project last week. IIRC about 25 bugs were forwarded. I hope heat-dashboard team can investigate them. Akihiro 2017-12-06 15:46 GMT+09:00 Akihiro Motoki

Re: [openstack-dev] [horizon][heat] heat-dashboard is ready for Horizon team's review

Hi Kaz, 2017-12-05 18:45 GMT+09:00 Kaz Shinohara : > Hi Akihiro, Horizon & Heat team, > > > We've slightly updated your change for the split out, please check > https://review.openstack.org/#/c/523402/ Thanks for updating the horizon patch. Is it ready to merge from the

Re: [openstack-dev] [horizon][heat] heat-dashboard is ready for Horizon team's review

Hi Akihiro, Horizon & Heat team, We've slightly updated your change for the split out, please check https://review.openstack.org/#/c/523402/ One non-voting job failed but hopefully not related to this change. In parallel, we could confirm that heat-dashboard works without any issue along with

Re: [openstack-dev] [horizon][heat] heat-dashboard is ready for Horizon team's review

Hi Akihiro, Thanks for your quick response! As you requested, we will check & update your patch to slit out heat support from Horizon repo. https://review.openstack.org/#/c/523402/ Also replied for your comment in our etherpad, please kindly check.

Re: [openstack-dev] [horizon][heat] heat-dashboard is ready for Horizon team's review

Hi Kaz, Good hear the good progress of heat-dashboard. Thanks. I created a blueprint in horizon to track the effort (mainly in horizon side) and assign it to you: https://blueprints.launchpad.net/horizon/+spec/heat-dashboard-split-out I also left comments in your etherpad. I think it is time to

[openstack-dev] [horizon][heat] heat-dashboard is ready for Horizon team's review

Hi Horizon team, As I talked with Rob & Ying in Sydney, now heat-dashboard repo is ready, please kindly review it. http://git.openstack.org/cgit/openstack/heat-dashboard Also we described points to be clarified in this review, if you find anything to be noted/fixed, please feel free to put

[openstack-dev] [horizon] Pagination issues and resource deletion

Hi team, Pagination issues are a hot topic for Horizon. We had a good discussion at PTG [1] for it. Also, I would like to say thanks to Ferenc for working on it [2]. As a long-term solution, we decided to implement 'Show more' button and improve filtering at PTG [1]. This will help us to fix

Re: [openstack-dev] [horizon] Fetch resources in parallel

Just forgot to mention one other option: we can use celery [6] too but I didn't do any performance testing with it. This solution will be more complex. [6] http://www.celeryproject.org/ Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Tue, Oct 31, 2017 at 7:15 PM, Ivan Kolodyazhny

[openstack-dev] [horizon] Fetch resources in parallel

Hi team, We all know that unfortunately Horizon's performance not good enough in some cases. That's why we try to fix it on both sides: client-side and server-side. I would like to talk mostly about server-side now. On some views, we use 'futurist' library [1] to fetch resources from API's in

Re: [openstack-dev] [horizon] bp/neutron-trunk-ui

Sorry for the double post, I forgot the subject. On Thu, Oct 12, 2017 at 2:29 PM, Bence Romsics wrote: > Hi Horizon Folks, > > After the PTG I'm back from vacation and I'd like to ask for reviews > for bp/neutron-trunk-ui: > >

[openstack-dev] [horizon]

Hi Horizon Folks, After the PTG I'm back from vacation and I'd like to ask for reviews for bp/neutron-trunk-ui: https://review.openstack.org/#/q/status:open+topic:bp/neutron-trunk-ui When you'll hit that link you'll see a Jenkins-1 on some of the patches, but please don't be put off by that. We

Re: [openstack-dev] [horizon] [ceilometer] A Monitoring panel plugin for Horizon

Hi Julien, - 15 Eyl 2017 tarihinde, 15:20 saatinde, julien şunları yazdı: > I guess if you found everything you wanted in the Gnocchi API that's > awesome. If there are feature you think you miss, please let us know! I think Gnocchi API is very handy, the resource,

Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon

On Fri, Sep 15 2017, Esra Celik wrote: Hi Esra, > We published a new release of our Monitor Panel which uses Gnocchi api as the > backend [1]. > As Gokhan said, our cloud platform is still on Mitaka so we tested this new > release on Devstack, That sounds cool. > It seems quite faster than

[openstack-dev] [horizon] A Monitoring panel plugin for Horizon

Hi Julien, On Tue, Aug 11 2017, Julien Danjou wrote: >> We are happy to share with you that we developed an AngularJS based usage >> >> monitoring panel for Horizon. >> The panel visualizes the collected >> utilization data by Ceilometer. >> >> Source code is now available on github >> [1].

[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

[openstack-dev] [horizon] PTG meetup

Hi all, Just wondering who is going to the PTG from the horizon team and whether we want to organise a google hangout group and/or plans for a happy hour or evening for the team to get to know each other better maybe? Looking forward to seeing you there, Beth Elwell (betherly)

[openstack-dev] [horizon] horizon 12.0.0.0rc3 (pike)

Hello everyone, A new release candidate for horizon for the end of the Pike 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] horizon 12.0.0.0rc2 (pike)

Hello everyone, A new release candidate for horizon for the end of the Pike 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

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

> This may be a bug; I recall it was patched recently and perhaps the same logic > needs to be applied to the Admin view. It sounds like an oversight. Thanks, Rob. I filed 1711486. What you mentioned is probably df194c8b. It added code in Admin dashboard instance index view class to retrieve

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

Thanks, Rob, blueprint is proposed here: https://blueprints.launchpad.net/horizon/+spec/horizon-multi-region-support Cheers, Lingxian Kong (Larry) On Thu, Aug 17, 2017 at 11:05 PM, Rob Cresswell (rcresswe) < rcres...@cisco.com> wrote: > As I mentioned the last time you asked :), we use

Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon

Pazartesi 2017 9:34:51 Konu: Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon Hi Julien, We developed the monitor dashboard to use it on our private cloud in the first place. We have Mitaka release and we use MongoDB with Ceilometer. But you are right, we can update the

Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon

tos Cuma 2017 15:29:17 Konu: Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon On Tue, Aug 01 2017, Gökhan IŞIK (BİLGEM BTE) wrote: Hi, > We are happy to share with you that we developed an AngularJS based usage > monitoring panel for Horizon. > The panel visualizes the

Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon

Pazartesi 2017 9:34:51 Konu: Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon Hi Julien, We developed the monitor dashboard to use it on our private cloud in the first place. We have Mitaka release and we use MongoDB with Ceilometer. But you are right, we can update the

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

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

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

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

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

Hi, Horizon developers, In our OpenStack based public cloud(Catalyst Cloud), Keystone is a shared identity service across 3 regions, our customers have been asking for the feature that they could select their preferred region when they log in Horizon, rather than switching region each time after

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

Hi, I observed accessing Admin dashboard's instance index page generated lots of duplicate requests to Glance for converting instance image id to name, but accessing Project dashboard's instance index page didn't (my system runs Newton, but from what I can tell, Ocata and Pike code seem to

Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon

On Tue, Aug 01 2017, Gökhan IŞIK (BİLGEM BTE) wrote: Hi, > We are happy to share with you that we developed an AngularJS based usage > monitoring panel for Horizon. > The panel visualizes the collected utilization data by Ceilometer. > > Source code is now available on github [1]. > > The

[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] horizon 12.0.0.0rc1 (pike)

Hello everyone, A new release candidate for horizon for the end of the Pike 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

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]when I access my website, there is '500 internal server error'

Hi: the log is here: http://paste.openstack.org/show/617722/ . I install Ocata in centos by all in one,then I copy Ironic-UI plugin to ‘enable’,I update some lib which is Ironic-UI based on,when I restart the httpd server, the error coming. how can I fix it except reinstall the env?

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

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

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

On 08/03/2017 04:21 AM, Sean Dague wrote: On 08/03/2017 06:13 AM, Zhenyu Zheng wrote: I was thinking, the current "edit" in Horizon is delete-and-create, and it is there maybe just because flavor has many fields, user may want to have a new flavor but just modify one of the old flavor, so they

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

On 08/03/2017 06:13 AM, Zhenyu Zheng wrote: > I was thinking, the current "edit" in Horizon is delete-and-create, and > it is there maybe just because > flavor has many fields, user may want to have a new flavor but just > modify one of the old flavor, so > they don't want to manually copy all

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

I was thinking, the current "edit" in Horizon is delete-and-create, and it is there maybe just because flavor has many fields, user may want to have a new flavor but just modify one of the old flavor, so they don't want to manually copy all other fields. And it is the automatic delete action that

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

On 08/02/2017 10:12 PM, Zhenyu Zheng wrote: > Hi All, > > Horizon provided the feature to allow user edit existing flavors, no > matter it is currently used by any instances or not. While Nova doesn't > provide this kind of ability, Horizon achieved this by deleting the old > flavor first and

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

On Thu, Aug 3, 2017 at 11:12 AM, Zhenyu Zheng wrote: > Hi All, > > Horizon provided the feature to allow user edit existing flavors, no > matter it is currently used by any instances or not. While Nova doesn't > provide this kind of ability, Horizon achieved this by

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

Hi All, Horizon provided the feature to allow user edit existing flavors, no matter it is currently used by any instances or not. While Nova doesn't provide this kind of ability, Horizon achieved this by deleting the old flavor first and create a new flavor with the requested properties. And the

[openstack-dev] [horizon] A Monitoring panel plugin for Horizon

Hi all, We are happy to share with you that we developed an AngularJS based usage monitoring panel for Horizon. The panel visualizes the collected utilization data by Ceilometer. Source code is now available on github [1]. The plugin consists of 3 panels; a monitoring panel for users, a

[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

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

django_openstack_auth and django-babel have been released, and now the generated upper-constraints patch containing Django 1.11.x is here: https://review.openstack.org/#/c/486093 If something suddenly starts misbehaving in Horizon or a plugin, there's a good chance it's stemmed from this

[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

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

Awesome, I appreciate the work here. I spoke with a couple Django folk on IRC and they didn’t have any other solution than “vendor the code”, so I think your approach is probably the most reasonable. I’m fairly annoyed that they dropped an interface like that, but oh well. I’ll take a look at

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

Was hoping to play with this much sooner, but here is a quick hack for horizon working with django 1.11 https://review.openstack.org/#/c/484277/ The main issues are with widgets from Django which are no longer there, and all I've done is move them to our repo from django 1.10's code. This is

[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] Raising Django version cap

> -Original Message- > From: Rob Cresswell (rcresswe) [mailto:rcres...@cisco.com] > Sent: Wednesday, July 05, 2017 7:24 PM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [horizon]

[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

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