Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

Unfortunately none of this discussion solves the substantive issue which is that we cannot release an xstatic package without breaking the gate. We currently have one solution that's a close to viable as we've been able to get: move the version pinning for xstatic packages out of

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 13 March 2016 at 07:06, Matthias Runge wrote: > On 10/03/16 08:46, Richard Jones wrote: > > On 10 March 2016 at 18:23, Matthias Runge > > wrote: > > > > 4.alt.2: > > move to proper packages for static file management. I

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 03/17/2016 07:12 AM, Richard Jones wrote: > On 13 March 2016 at 07:11, Matthias Runge > wrote: > > On 10/03/16 11:48, Beth Elwell wrote: > > If we will anyway have potential breakage I don’t understand why the > > better solution here

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 14 March 2016 at 11:08, Thomas Goirand wrote: > > From a distribution package maintainer perspective, the most annoying > part is that there's no easy way to get the web app use the JS libs from > the OS, and there's no system wide registry of installed components. > There's

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 17/03/16 08:59, Thomas Goirand wrote: >> >> Horizon, for example, currently does *not* use the upper-constraints >> pinning in its test suite or installation, so we're vulnerable to, say, >> a python-*client release that's not compatible. I have a patch in the >> works to address this, but it

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

On 11 March 2016 at 04:37, Michael Krotscheck wrote: > On Wed, Mar 9, 2016 at 12:45 PM Tripp, Travis S > wrote: > >> The problem is that the warnings are so great that is really hard to read. >> > > If all the warnings were fixed - I know Matt

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 03/17/2016 07:23 AM, Richard Jones wrote: > There's a basic difference here though. Your traditional "installed > components" are pieces of software and data used *by programs on that > system.* > > The components we're talking about here are, as far as the system is > concerned, opaque data

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 13 March 2016 at 07:11, Matthias Runge wrote: > On 10/03/16 11:48, Beth Elwell wrote: > > If we will anyway have potential breakage I don’t understand why the > > better solution here would not be to just use the bower and npm tools > > which are standardised for JavaScript

Re: [openstack-dev] [horizon] PTL noncandidacy

ailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: 03/14/2016 07:04 PM Subject: Re: [openstack-dev] [horizon] PTL noncandidacy David, Thanks for your commitment and leadership, really appreciated all the help from you! On Tue, Mar 15,

[openstack-dev] [horizon] PTL candidacy

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

[openstack-dev] [horizon] remove 'external' option from router rules grid

Hi, I wanted to bring attention to the router rules grid on the horizon GUI. Currently, we have 'external' and 'any' as two different options on the router rules grid: github.com/openstack/horizon/blob/stable/liberty/openstack_dashboa

Re: [openstack-dev] [horizon] PTL noncandidacy

David, Thanks for your commitment and leadership, really appreciated all the help from you! On Tue, Mar 15, 2016 at 5:41 AM, Diana Whitten wrote: > David, > > I don't envy the person who has to fill these shoes. You've been amazing! > > - Diana > > On Mon, Mar 14,

Re: [openstack-dev] [horizon] PTL noncandidacy

David, I don't envy the person who has to fill these shoes. You've been amazing! - Diana On Mon, Mar 14, 2016 at 1:04 PM, Timur Sufiev wrote: > David, > > It's sad news for us, and a well-deserved vacation from bureaucratic > hassles for you! Will try hard to not break

Re: [openstack-dev] [horizon] PTL noncandidacy

David, It's sad news for us, and a well-deserved vacation from bureaucratic hassles for you! Will try hard to not break Horizon in your absence. On Mon, 14 Mar 2016 at 22:46, Doug Fish wrote: > David, congratulations on a job well done! > > Doug > > On Mar 14, 2016, at

Re: [openstack-dev] [horizon] PTL noncandidacy

David, congratulations on a job well done! Doug > On Mar 14, 2016, at 8:39 AM, Liz Blanchard wrote: > > > >> On Fri, Mar 11, 2016 at 12:19 PM, David Lyle wrote: >> After five cycles as PTL of Horizon, I've decided not to run for the >> Newton cycle. >

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

me, thanks for all the hard work Diana! >>>>> >>>>> >>>>> - Original message - >>>>> From: David Lyle <dkly...@gmail.com> >>>>> To: OpenStack Development Mailing List >>>>> <openstack-dev@lists.ope

Re: [openstack-dev] [horizon] PTL noncandidacy

On Fri, Mar 11, 2016 at 12:19 PM, David Lyle wrote: > After five cycles as PTL of Horizon, I've decided not to run for the > Newton cycle. > David, Thank you for everything you've done for Horizon, especially around helping push a focus on User Experience. Best, Liz > > I

Re: [openstack-dev] [horizon] PTL noncandidacy

On 11/03/16 18:19, David Lyle wrote: > After five cycles as PTL of Horizon, I've decided not to run for the > Newton cycle. Thank you David for all you have done for Horizon and the community around Horizon. It was (and is) still awesome to work with you. If you can, please stay and continue to

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 03/12/2016 09:11 PM, Matthias Runge wrote: > - how often have we been blocked by releases of software not managed by > OpenStack? Seriously, that happens quite a few times over a release > cycle, not to mention breakages by releases of our own tools turning out > to block one or the other

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 03/10/2016 12:14 PM, Richard Jones wrote: > On 10 March 2016 at 21:48, Beth Elwell > wrote: > >> On 10 Mar 2016, at 07:46, Richard Jones > > wrote: >> >> It has been

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 03/10/2016 11:48 AM, Beth Elwell wrote: > >> On 10 Mar 2016, at 07:46, Richard Jones > > wrote: >> >> >> It has been mentioned, xstatic packages can block the gate. We >> currently >> control xstatic package releases, thus

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 03/09/2016 04:53 PM, Monty Taylor wrote: > On 03/07/2016 10:52 PM, Richard Jones wrote: >> We've solved *most* of the issues around releasing new xstatic packages, >> documented here[1] (and related documentation). >> >> We have one final issue that's blocking us, which is that during the >>

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 03/08/2016 05:52 AM, Richard Jones wrote: > In the Python world, we code around this by making Horizon compatible > with both the X and X1 versions of xstatic-angular (if it was a Python > library). In Javascript land this is much more difficult - Javascript > libraries tend to break

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 10/03/16 11:48, Beth Elwell wrote: > > If we will anyway have potential breakage I don’t understand why the > better solution here would not be to just use the bower and npm tools > which are standardised for JavaScript and would move Horizon more > towards using widely recognised tooling

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 10/03/16 08:46, Richard Jones wrote: > On 10 March 2016 at 18:23, Matthias Runge > wrote: > > 4.alt.2: > move to proper packages for static file management. I mean, they need to > be built anyways. > > > Please define what you mean

Re: [openstack-dev] [horizon] PTL noncandidacy

On 03/11/2016 12:19 PM, David Lyle wrote: After five cycles as PTL of Horizon, I've decided not to run for the Newton cycle. I am exceptionally proud of the things we've accomplished over this time. I'm amazed by how much our project's community has grown and evolved. Looking at the community

Re: [openstack-dev] [horizon] PTL noncandidacy

Thanks for everything David. My involvement and engagement with the project would not be what it is without your leadership. I look forward to continuing to work with and learn from you! Richard On 12 March 2016 at 04:19, David Lyle wrote: > After five cycles as PTL of

Re: [openstack-dev] [horizon] PTL noncandidacy

David, Thank you so much for the patience and wisdom you’ve demonstrated over the years. I always appreciate sense of humor you bring to IRC. For the love of all that is OpenStack, please stay active on Horizon! -Travis On 3/11/16, 10:19 AM, "David Lyle" wrote: >After

Re: [openstack-dev] [horizon] PTL noncandidacy

message -From: Anita Kuno <ante...@anteaya.info>To: openstack-dev@lists.openstack.orgCc:Subject: Re: [openstack-dev] [horizon] PTL noncandidacyDate: Fri, Mar 11, 2016 1:18 PM  On 03/11/2016 12:19 PM, David Lyle wrote:> After five cycles as PTL of Horizon, I've decided not to run for th

Re: [openstack-dev] [horizon] PTL noncandidacy

On 03/11/2016 12:19 PM, David Lyle wrote: > After five cycles as PTL of Horizon, I've decided not to run for the > Newton cycle. > > I am exceptionally proud of the things we've accomplished over this > time. I'm amazed by how much our project's community has grown and > evolved. > > Looking at

Re: [openstack-dev] [horizon] PTL noncandidacy

Thanks for all the great work. Your leadership and commitment to horizon has been instrumental to the projects success. On Fri, Mar 11, 2016 at 9:19 AM, David Lyle wrote: > After five cycles as PTL of Horizon, I've decided not to run for the > Newton cycle. > > I am

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

om> wrote: >>>> >>>> Big +1 from me, thanks for all the hard work Diana! >>>> >>>> >>>> - Original message ----- >>>> From: David Lyle <dkly...@gmail.com> >>>> To: OpenStack Development Mailing List >>

[openstack-dev] [horizon] PTL noncandidacy

After five cycles as PTL of Horizon, I've decided not to run for the Newton cycle. I am exceptionally proud of the things we've accomplished over this time. I'm amazed by how much our project's community has grown and evolved. Looking at the community now, I believe we have a tremendous group of

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

t; From: David Lyle <dkly...@gmail.com> >>> To: OpenStack Development Mailing List < >>> openstack-dev@lists.openstack.org> >>> Cc: >>> Subject: [openstack-dev] [horizon] Proposal to add Diana Whitten to >>> horizon-core >>> Date: Tue, Mar 8,

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

: > >> Big +1 from me, thanks for all the hard work Diana! >> >> >> - Original message - >> From: David Lyle <dkly...@gmail.com> >> To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org >> > >> Cc: >> S

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

On Wed, Mar 9, 2016 at 4:15 PM Richard Jones wrote: > > We already have a "lintq" npm task that does this, which most of us use. > The problem is that we then ignore all the legitimate code linting warnings. > I think we both agree that some form of jsdoc linting is

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

On Wed, Mar 9, 2016 at 12:45 PM Tripp, Travis S wrote: > The problem is that the warnings are so great that is really hard to read. > If all the warnings were fixed - I know Matt Borland's working on that - would we be having this conversation? Michael

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 10 March 2016 at 21:48, Beth Elwell wrote: > > On 10 Mar 2016, at 07:46, Richard Jones wrote: > >> It has been mentioned, xstatic packages can block the gate. We currently >> control xstatic package releases, thus we can roll back, if something >>

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 03/10/2016 11:48 AM, Beth Elwell wrote: On 10 Mar 2016, at 07:46, Richard Jones > wrote: It has been mentioned, xstatic packages can block the gate. We currently control xstatic package releases, thus we can roll back, if

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

> On 10 Mar 2016, at 07:46, Richard Jones wrote: > > It has been mentioned, xstatic packages can block the gate. We currently > control xstatic package releases, thus we can roll back, if something > goes wrong. > > If we're pulling directly with npm/bower, someone

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 10 March 2016 at 18:23, Matthias Runge wrote: > > 4.alt.2: > move to proper packages for static file management. I mean, they need to > be built anyways. > Please define what you mean by "proper packages" here. I *think* you might mean system packages (aka Debian or Red

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 09/03/16 19:52, Michael Krotscheck wrote: > On Wed, Mar 9, 2016 at 7:58 AM Monty Taylor > wrote: > > > > SOLUTION 4: vendor the javascript > > > > Heh. > > Heh indeed. > > SOLUTION 4.alt: use npm/bower instead of

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

On 10 March 2016 at 06:49, Michael Krotscheck wrote: > I guess I don't see what problems is being solved by turning the rule off, > and I also don't see the harm in having more check. It does generate a lot > of warnings, but invoking `npm run lint -- --quiet` gets rid of

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

+2 for Diana :) - Original message - From: David Lyle <dkly...@gmail.com> To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org> Cc: Subject: [openstack-dev] [horizon] Proposal to add Diana Whitten to horizon-core Date: Tue, Mar 8, 2016 2:07 PM

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

> On 03/09/2016 04:43 PM, Serg Melikyan wrote: >>> >>> This is exactly my first thought. The plugins *must* depend on Horizon, >>> and they have to use the same versions of XStatic packages anyways, > > >> so why specify the dependencies twice? >> >> >> Plugins may require different xstatic

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

Hi Serg, There's a crucial difference: getting the solution to this wrong for Horizon will break the gate for all OpenStack projects. Updating an xstatic package that a plugin uses has no side-effect outside of the plugin. Richard On 10 March 2016 at 02:43, Serg Melikyan

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

>> Date: Wednesday, March 9, 2016 at 12:49 PM To: OpenStack List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [Horizon] Javascript linting and documentation +1 to what Rob said. I guess I don't see what problems is

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

+1 to what Rob said. I guess I don't see what problems is being solved by turning the rule off, and I also don't see the harm in having more check. It does generate a lot of warnings, but invoking `npm run lint -- --quiet` gets rid of those. Also, from my experience, sphinx-based doc builds are

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

ail.com> > To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org> > Cc: > Subject: [openstack-dev] [horizon] Proposal to add Diana Whitten to > horizon-core > Date: Tue, Mar 8, 2016 2:07 PM > > I propose adding Diana Whitten[1] to horizon-core. > > D

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

Big +1 from me, thanks for all the hard work Diana!   - Original message -From: David Lyle <dkly...@gmail.com>To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org>Cc:Subject: [openstack-dev] [horizon] Proposal to add Diana Whitten to horizon-coreDate: Tue,

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

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

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On Wed, Mar 9, 2016 at 7:58 AM Monty Taylor wrote: > > > SOLUTION 4: vendor the javascript > > > > Heh. > > Heh indeed. > > SOLUTION 4.alt: use npm/bower instead of xstatic to pull the javascript. > +1. Let's move the codebase forward, instead of continuing to build hacky

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 10 Mar 2016 2:58 AM, "Radomir Dopieralski" wrote: > > On 03/09/2016 04:43 PM, Serg Melikyan wrote: >>> >>> This is exactly my first thought. The plugins *must* depend on Horizon, >>> and they have to use the same versions of XStatic packages anyways, > > >> so why

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

I’m not a core but I wanted to add my complete agreement with making Diana a core in horizon. She has done some incredible work in horizon through her work on the code, reviews and also community attitude and assistance getting people (myself included) familiar with horizon. Beth > On 8 Mar

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

k.org<mailto:openstack-dev@lists.openstack.org>>> Date: Tuesday, March 8, 2016 at 3:48 PM To: OpenStack List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org><mailto:openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>&g

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

: OpenStack List <openstack-dev@lists.openstack.org> openstack-dev@lists.openstack.org>> >> Date: Tuesday, March 8, 2016 at 3:48 PM >> To: OpenStack List <openstack-dev@lists.openstack.org> openstack-dev@lists.openstack.org>> >> Subject: Re: [openstack-dev] [horizon]

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 03/09/2016 04:43 PM, Serg Melikyan wrote: This is exactly my first thought. The plugins *must* depend on Horizon, and they have to use the same versions of XStatic packages anyways, >> so why specify the dependencies twice? Plugins may require different xstatic library, which is not even

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 03/07/2016 10:52 PM, Richard Jones wrote: We've solved *most* of the issues around releasing new xstatic packages, documented here[1] (and related documentation). We have one final issue that's blocking us, which is that during the xstatic release there will be a point at which Horizon may

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

>This is exactly my first thought. The plugins *must* depend on Horizon, and >they have to use the same versions of XStatic packages anyways, so why specify >the dependencies twice? Plugins may require different xstatic library, which is not even used by Horizon. Issue raised by Richard exists

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 03/08/2016 11:43 PM, David Lyle wrote: I'm wondering if since horizon is really the only project consuming these xstatic libraries and none are likely to venture down this path of madness with us that it would be safe to manage the xstatic requirements and upper-constraints locally.

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

Hey all, I started looking into fixing the wall of "npm run lint" warnings today and quickly noticed that about 85% of the "linting" warnings were about jsdoc. We have significant issues around jsdoc anyway and we're supposed to be using Sphinx anyway[1]. Some Horizon folks will know that I've

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 9 March 2016 at 14:23, Jeremy Stanley wrote: > On 2016-03-09 13:57:45 +1300 (+1300), Robert Collins wrote: >> On 9 March 2016 at 13:07, Jeremy Stanley wrote: >> > On 2016-03-08 17:25:41 +1100 (+1100), Richard Jones wrote: >> > [...] >> >> SOLUTION 6 -

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 2016-03-09 13:57:45 +1300 (+1300), Robert Collins wrote: > On 9 March 2016 at 13:07, Jeremy Stanley wrote: > > On 2016-03-08 17:25:41 +1100 (+1100), Richard Jones wrote: > > [...] > >> SOLUTION 6 - make zuul capable of performing atomic cross-repository > >> commits. > > > >

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 9 March 2016 at 13:07, Jeremy Stanley wrote: > On 2016-03-08 17:25:41 +1100 (+1100), Richard Jones wrote: > [...] >> SOLUTION 6 - make zuul capable of performing atomic cross-repository >> commits. > > This seems unlikely to happen, as it's very much counter to Zuul's >

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

But Jeremy: Atomic Zuul. How cool is that name. So I know I'm going to potentially get yelled at for voicing this, but what are the chances that app-catalog and Horizon are ever installed on the same system? That is, could it have its own xstatic constraints, with the promise that the two

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 2016-03-08 17:25:41 +1100 (+1100), Richard Jones wrote: [...] > SOLUTION 6 - make zuul capable of performing atomic cross-repository > commits. This seems unlikely to happen, as it's very much counter to Zuul's designed-in reliance on serializing changes to test before merging them. -- Jeremy

Re: [openstack-dev] [Horizon][app-catalog] How do we move forward with xstatic releases?

...@gmail.com] Sent: Tuesday, March 08, 2016 2:43 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases? On Mon, Mar 7, 2016 at 9:52 PM, Richard Jones <r1chardj0...@gmail.com<mailto:r1c

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

ilto:os.lch...@gmail.com>> > Reply-To: OpenStack List <openstack-dev@lists.openstack.org openstack-dev@lists.openstack.org>> > Date: Tuesday, March 8, 2016 at 3:48 PM > To: OpenStack List <openstack-dev@lists.openstack.org openstack-dev@lists.openstack.org>> >

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

: Tuesday, March 8, 2016 at 3:48 PM To: OpenStack List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [horizon] Proposal to add Diana Whitten to horizon-core big +1 from me. She made a lot of contribution in making theming be

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

big +1 from me. She made a lot of contribution in making theming better for horizon and also prevented potential issues through reviews. Thanks for all the hard work, Diana. -Lin On Tue, Mar 8, 2016 at 2:06 PM, David Lyle wrote: > I propose adding Diana Whitten[1] to

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On Mon, Mar 7, 2016 at 9:52 PM, Richard Jones wrote: > We've solved *most* of the issues around releasing new xstatic packages, > documented here[1] (and related documentation). > > We have one final issue that's blocking us, which is that during the > xstatic release

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

I propose adding Diana Whitten[1] to horizon-core. Diana is an active reviewer, contributor and community member. Over the past couple of releases, Diana has driven extensive changes around theme-ability in Horizon and drastically increased the standardization of our use of bootstrap. During this

[openstack-dev] [horizon] [searchlight] Horizon, Search, and Composability

Hello everybody, At the Horizon mid-cycle we had a lot of discussion on UI composability and searchability. Matt and Tyr provided a short presentation and demo at the mid-cycle. This morning I gave a more detailed presentation and demo via hangouts on air regarding Searchlight and Horizon. The

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

Two things I forgot to mention: Currently there is another break point in the diagram of releases when X1 is released. Currently Horizon does not use upper-constraints and thus will immediately pick up the new xstatic release file, potentially breaking things. This is easy to fix - I will be

[openstack-dev] [Horizon] How do we move forward with xstatic releases?

We've solved *most* of the issues around releasing new xstatic packages, documented here[1] (and related documentation). We have one final issue that's blocking us, which is that during the xstatic release there will be a point at which Horizon may be broken from an integrated point of view -

Re: [openstack-dev] [Horizon] Blueprints for Outreachy internship

Hi Richard, Thanks for you reply. I had a short conversation with Matthias and we decided to put the blueprint for context-sensitive help as an internship idea for now. Maybe I add another project to the list, then I can look

Re: [openstack-dev] [Horizon] Blueprints for Outreachy internship

Hi Sayali, Sorry I missed your original message, and thanks Matthias for responding. Indeed the new Swift UI is currently being merged. Some of those blueprints you list are things I'd like to see once the basic reimplementation is landed. Select-all is already in the new version though (though

Re: [openstack-dev] [Horizon] Blueprints for Outreachy internship

On 29/02/16 12:41, Sayali Lunkad wrote: > Hi Matthias, > > Thanks for the links to the blueprints. I in fact did checkout the list > of bps earlier but I found many of them have not been approved yet. I > can give you a list of bps I would like to mentor for, from which we > could perhaps select

Re: [openstack-dev] [Horizon] Blueprints for Outreachy internship

Hi Matthias, Thanks for the links to the blueprints. I in fact did checkout the list of bps earlier but I found many of them have not been approved yet. I can give you a list of bps I would like to mentor for, from which we could perhaps select one or two for the internship program depending on

Re: [openstack-dev] [Horizon] Blueprints for Outreachy internship

On 26/02/16 10:36, Sayali Lunkad wrote: > Hello, > > I am looking for some blueprints in horizon that can be set aside for > the Outreachy Internship > program. If anyone has any > blueprints in mind which are not needed anytime soon as well as not so >

[openstack-dev] [Horizon] Testing of angular promise based code paths

Hi all, I've just added a comment to a review and I think I'd like to ask for a broader discussion of whether I'm correct. The review is here: https://review.openstack.org/#/c/284857/2 It boils down to: when testing code that uses a promise, should we *use* a promise to have the follow-on

Re: [openstack-dev] [horizon][i18n] Any Horizon plugins ready for translation in Mitaka?

ng Chun Guo (Daisy) > > > Akihiro Motoki <amot...@gmail.com> wrote on 2016/02/26 01:00:15: > >> From: Akihiro Motoki <amot...@gmail.com> >> To: "OpenStack Development Mailing List (not for usage questions)" >> <openstack-dev@lists.openstack.org>

[openstack-dev] [Horizon] Blueprints for Outreachy internship

Hello, I am looking for some blueprints in horizon that can be set aside for the Outreachy Internship program. If anyone has any blueprints in mind which are not needed anytime soon as well as not so difficult to implement please let me know so we can

Re: [openstack-dev] [horizon][i18n] Any Horizon plugins ready for translation in Mitaka?

questions)" >> <openstack-dev@lists.openstack.org> >> Date: 2016/02/26 01:04 > > >> Subject: Re: [openstack-dev] [horizon][i18n] Any Horizon plugins >> ready for translation in Mitaka? >> >> 2016-02-25 19:47 GMT+09:00 Andreas Jaeger &l

Re: [openstack-dev] [horizon][i18n] Any Horizon plugins ready for translation in Mitaka?

<amot...@gmail.com> wrote on 2016/02/26 01:00:15: > From: Akihiro Motoki <amot...@gmail.com> > To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Date: 2016/02/26 01:04 > Subject: Re: [opensta

[openstack-dev] [Horizon][Searchlight] Plans for Horizon cross-region view

The last info I've found on the ML about a cross-region view in Horizon is [1], which mentions making asynchronous calls to the APIs. Has anyone done further work on such a view? If not, I think it would make sense to only show the view if Searchlight is enabled. One of the Searchlight use

Re: [openstack-dev] [horizon][i18n] Any Horizon plugins ready for translation in Mitaka?

Ying Chun Guo (Daisy) >> >> >> Akihiro Motoki <amot...@gmail.com> wrote on 2016/02/23 15:56:39: >> >>> From: Akihiro Motoki <amot...@gmail.com> >>> To: "OpenStack Development Mailing List (not for usage questions)" >>&

Re: [openstack-dev] [horizon][i18n] Any Horizon plugins ready for translation in Mitaka?

ment Mailing List (not for usage questions)" >> <openstack-dev@lists.openstack.org> >> Date: 2016/02/23 16:00 >> Subject: Re: [openstack-dev] [horizon][i18n] Any Horizon plugins >> ready for translation in Mitaka? >> >> Hi Daisy, >> >> AFA

Re: [openstack-dev] [horizon][i18n] Any Horizon plugins ready for translation in Mitaka?

:56:39: > From: Akihiro Motoki <amot...@gmail.com> > To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Date: 2016/02/23 16:00 > Subject: Re: [openstack-dev] [horizon][i18n] Any Horizon plugins > ready for

Re: [openstack-dev] [Horizon][Neutron][QoS]horizon angular network QoS panel

Hi Masco!, Thanks a lot for working on this, I’m not following the [Horizon] tag and I missed this. I’ve added the Neutron and QoS tags. I will give it a try as soon as I can. Keep up the good work!, Cheers, Miguel Ángel. > On 10 Feb 2016, at 13:04, masco

Re: [openstack-dev] [horizon][i18n] Any Horizon plugins ready for translation in Mitaka?

Hi Daisy, AFAIK the following horizon plugins are ready for translation. I tested and confirmed translations of these two work well with Japanese. A minor improvement on devstack or other stuff are in progress but it does not affect translation. * trove-dashboard * sahara-dashboard The

Re: [openstack-dev] [horizon][i18n] Any Horizon plugins ready for translation in Mitaka?

On 2016-02-23 07:52, Ying Chun Guo wrote: > Hi, > > Mitaka translation will be started from March 4 and ended in the week of > March 28. > I'd like to know which Horizon plugins[1] are ready for translation in > Mitaka release. > If there are, I'm happy to include them in the Mitaka translation

[openstack-dev] [horizon][i18n] Any Horizon plugins ready for translation in Mitaka?

Hi, Mitaka translation will be started from March 4 and ended in the week of March 28. I'd like to know which Horizon plugins[1] are ready for translation in Mitaka release. If there are, I'm happy to include them in the Mitaka translation plan. Thank you. Best regards Ying Chun Guo (Daisy)

Re: [openstack-dev] [horizon] [octavia] [heat] [docs] Meeting times and the -cp meeting room

On Mon, Feb 22, 2016 at 8:49 AM, Anne Gentle wrote: > Hi all, > > The docs team has been seeking a new meeting time for North America/Europe > for a couple of months now. With that search comes the search for a meeting > room. Here's what we know: > > We want Wed

[openstack-dev] [horizon] [octavia] [heat] [docs] Meeting times and the -cp meeting room

Hi all, The docs team has been seeking a new meeting time for North America/Europe for a couple of months now. With that search comes the search for a meeting room. Here's what we know: We want Wed 20:00. Heat, Horizon, and Octavia are currently in the three meeting rooms in the time slot we

Re: [openstack-dev] [Horizon][Trove][Sahara] Horizon-Trove/Sahara External Repository

Hi, > Horizon still have some things we need to tidy up on our end to make sure we > have full support for testing and localization for external plugins. I am pleased to announce that translations of trove-dashboard and sahara-dashboard now work for the master branch. We have the parity to

Re: [openstack-dev] [Horizon][Trove] Horizon-Trove External Repository

.     - Original message -From: Andreas Jaeger <a...@suse.com>To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org>Cc:Subject: Re: [openstack-dev] [Horizon][Trove] Horizon-Trove External RepositoryDate: Mon, Feb 15, 2016 2:44 A

Re: [openstack-dev] [Horizon] eslint without color?

On 2016-02-15 16:45:09 +1100 (+1100), Richard Jones wrote: > I'm just curious why our eslint configuration (in packages.json) > specifies --no-color. It's much harder to spot the errors without > color, and I always end up running it manually to get the color. > Also, karma output has color, so

Re: [openstack-dev] [Horizon][Trove] Horizon-Trove External Repository

On 2016-02-15 11:32, Omer (Nokia - IL) Etrog wrote: > Hi, > Is there proper documentation how to add localization for external plugins > that use AngularJS? http://docs.openstack.org/infra/manual/creators.html#enabling-translation-infrastructure Note that the translation team only translates

Re: [openstack-dev] [Horizon][Trove] Horizon-Trove External Repository

: [openstack-dev] [Horizon][Trove] Horizon-Trove External Repository Hello Trovers and Horizoneers,   The intention of this email is to get everyone on the same page so we are all aware of what is going on. As many of you are probably already aware, Horizon is moving toward the plugin model for all

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