[openstack-dev] [Horizon] Some thoughts about Horizon's test suite

I'm relatively new to Horizon, but I come with a bunch of experience with Python more generally. I've contributed a couple of small patches to Horizon in an effort to get more familiar with the codebase. Julie Pichon's blog post about testing in Horizon has been invaluable

Re: [openstack-dev] [Horizon] Some thoughts about Horizon's test suite

something I'd like to see done. But that's not really the point of this email, as you note :) On 29 August 2014 19:46, Radomir Dopieralski openst...@sheep.art.pl wrote: On 29/08/14 04:22, Richard Jones wrote: Very recently I attempted to fix a simple bug in which a Panel was being

[openstack-dev] Supporting Javascript clients calling OpenStack APIs

[This is Horizon-related but affects every service in OpenStack, hence no filter in the subject] I would like for OpenStack to support browser-based Javascript API clients. Currently this is not possible because of cross-origin resource blocking in Javascript clients - that is, given some

Re: [openstack-dev] Supporting Javascript clients calling OpenStack APIs

On 12 September 2014 07:50, Adam Young ayo...@redhat.com wrote: On 09/11/2014 03:15 AM, Richard Jones wrote: [This is Horizon-related but affects every service in OpenStack, hence no filter in the subject] I would like for OpenStack to support browser-based Javascript API clients

Re: [openstack-dev] Supporting Javascript clients calling OpenStack APIs

On 12 September 2014 09:24, Richard Jones r1chardj0...@gmail.com wrote: On 12 September 2014 07:50, Adam Young ayo...@redhat.com wrote: So, lets have these two approaches work in parallel. THe proxy will get things goint while we work out the CORS approach. I will look at submitting my

Re: [openstack-dev] [Horizon]Dev environment default login

I needs to point at a devstack or openstack installation for login to work. On 12 September 2014 15:50, Rajdeep Dua rajdeep@gmail.com wrote: Hi, I have setup a local dev environment with a custom dashboard using instructions below

Re: [openstack-dev] [all] OpenStack bootstrapping hour - Friday Sept 19th - 3pm EST

This is a great idea, thanks! On 16 September 2014 08:56, Sean Dague s...@dague.net wrote: A few of us have decided to pull together a regular (cadence to be determined) video series taking on deep dives inside of OpenStack, looking at code, explaining why things work that way, and fielding

Re: [openstack-dev] [Keystone][Horizon] CORS and Federation

PM, Richard Jones wrote: CORS for all of OpenStack is possible once the oslo middleware lands*, but as you note it's only one of many elements to be considered when exposing the APIs to browsers. There is no current support for CSRF protection in the OpenStack APIs, for example. I believe

Re: [openstack-dev] [TripleO] pypi-mirror is now unsupported - what do we do now?

On 10 July 2014 02:19, Ben Nemec openst...@nemebean.com wrote: On 07/08/2014 11:05 PM, Joe Gordon wrote: On Tue, Jul 8, 2014 at 8:54 PM, James Polley j...@jamezpolley.com wrote: It may not have been clear from the below email, but clarkb clarifies on

Re: [openstack-dev] [TripleO] pypi-mirror is now unsupported - what do we do now?

On 10 July 2014 23:27, Mulcahy, Stephen stephen.mulc...@hp.com wrote: When I last tested bandersnatch, it didn’t work well behind a proxy (in fact most of the existing pypi mirroring tools suffered from the same problem) – pypi-mirror has worked extremely well for mirroring a subset of pypi and

Re: [openstack-dev] [all] concrete proposal on changing the library testing model with devstack-gate

On 30 September 2014 08:14, Doug Hellmann d...@doughellmann.com wrote: On Sep 29, 2014, at 4:22 PM, Robert Collins robe...@robertcollins.net wrote: As far as pip goes, you may not know, but tox defaults to pip --pre, which means anyone using tox, like us all here, will be pulling the

[openstack-dev] [Horizon] the future of angularjs development in Horizon

Hi all, At the summit last week, we developed a plan for moving forward with modernising Horizon's UI using AngularJS. If you weren't at that meeting and are interested in helping out with this effort please let me know! The relevant etherpad from the meeting:

[openstack-dev] [Horizon] proposal: alternating weekly meeting time

Hi all, At the summit meetup last week I proposed that the Horizon weekly meeting time alternate between the current time and something more suitable for those of us closer to UTC+10. I'd like to get an indication of the interest in this, and I'll look into getting a second meeting time booked

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

to be a lot of enthusiasm for gulp. I will look at making a branch of angboard that uses gulp to get a good feeling for it (unless someone produces a PR that does it for me ;) Richard On Tue, Nov 11, 2014 at 11:02 AM, Richard Jones r1chardj0...@gmail.com wrote: Hi all, At the summit

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 11 November 2014 20:53, Jiri Tomasek jtoma...@redhat.com wrote: Hey, Thanks for writing this up! I am including some notes and questions inline... On 11/11/2014 08:02 AM, Richard Jones wrote: Hi all, At the summit last week, we developed a plan for moving forward with modernising

Re: [openstack-dev] URLs

On 12 November 2014 09:47, Ian Cordasco ian.corda...@rackspace.com wrote: On 11/11/14, 16:35, Adam Young ayo...@redhat.com wrote: Recent recurrence of the Why ios everything on its own port question triggered my desire to take this pattern and put it to rest. My suggestion, from a while

Re: [openstack-dev] [Horizon] proposal: alternating weekly meeting time [doodle poll created]

wrote: On 11/11/14 08:09, Richard Jones wrote: Hi all, At the summit meetup last week I proposed that the Horizon weekly meeting time alternate between the current time and something more suitable for those of us closer to UTC+10. I'd like to get an indication of the interest

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 12 November 2014 18:17, Matthias Runge mru...@redhat.com wrote: On 11/11/14 10:53, Jiri Tomasek wrote: Hey, Thanks for writing this up! The Storyboard project has successfully integrated these tools into the OpenStack CI environment. OpenStack CI and distributors are different,

Re: [openstack-dev] [Horizon] proposal: alternating weekly meeting time [doodle poll created]

:45, Richard Jones r1chardj0...@gmail.com wrote: I have set up a doodle poll to let folk enter their preferred times. It's in UTC/GMT (/London time, because doodle) so use something like http://everytimezone.com/ to figure that out :) https://doodle.com/47h3f35nad62ncnf Richard On 11

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 13 November 2014 09:35, Adam Young ayo...@redhat.com wrote: On 11/12/2014 03:03 AM, Matthias Runge wrote: On 12/11/14 08:40, Richard Jones wrote: I believe the nodeenv method of installing node solves this, as it's entirely local to the development environment. See below, this touches

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

Gabriel has responded saying very much what I would have said, so I won't repeat that. I would like to note though that bower and npm are two separate beasts entirely. The dependency trees in bower are very limited indeed (only two additional components are installed beyond the list below) which

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 14 November 2014 02:04, Thomas Goirand z...@debian.org wrote: On 11/13/2014 12:13 PM, Richard Jones wrote: the npm stuff is all tool chain; tools that I believe should be packaged as such by packagers. npm is already in Debian: https://packages.debian.org/sid/npm However, just like

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

I think that it boils down to whether it'is possible that distributions: 1. package the node-based tools (grunt, karma, protractor, ...) as installable programs, and 2. xstatic-package the bower-based packages that we use (probably a couple of dozen at least). We might even be able to get away

Re: [openstack-dev] [Horizon] proposal: alternating weekly meeting time [doodle poll created]

I did it that way so that the form wouldn't blow out completely, and I thought for our purposes of scheduling a 2 hour precision would be good enough. On 14 November 2014 22:32, Jaromir Coufal jcou...@redhat.com wrote: On 12/11/14 02:45, Richard Jones wrote: I have set up a doodle poll to let

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 15 November 2014 00:58, Radomir Dopieralski openst...@sheep.art.pl wrote: On 14/11/14 13:02, Richard Jones wrote: I think that it boils down to whether it'is possible that distributions: 1. package the node-based tools (grunt, karma, protractor, ...) as installable programs, and 2

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 17 November 2014 06:42, Thomas Goirand z...@debian.org wrote: On 11/15/2014 06:27 AM, Gabriel Hurley wrote: So, I propose that a group gets together and defines criteria: we need to accept that the Horizon team (and those knowledgeable about web-app development) know best what tools

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 17 November 2014 11:11, Thomas Goirand z...@debian.org wrote: On 11/15/2014 05:03 AM, Matthias Runge wrote: On 14/11/14 16:21, Adam Young wrote: Example: I don't need Grunt to run a web server. I need Apache for that. Grunt does not need to be in the distro, mod_wsgi does. I

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 17 November 2014 21:54, Radomir Dopieralski openst...@sheep.art.pl wrote: On 17/11/14 09:53, Martin Geisler wrote: [...] As Richard said, npm and bower are not competitors. You use npm to install bower, and you use bower to download Angular, jQuery, Bootstrap and other static files.

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 18 November 2014 10:59, Richard Jones r1chardj0...@gmail.com wrote: On 17 November 2014 21:54, Radomir Dopieralski openst...@sheep.art.pl wrote: - Bower in the development environment, - Bower configuration file in two copies, one for global-requirements, and one for the Horizon's

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 18 November 2014 19:22, Radomir Dopieralski openst...@sheep.art.pl wrote: On 18/11/14 00:59, Richard Jones wrote: On 17 November 2014 21:54, Radomir Dopieralski openst...@sheep.art.pl mailto:openst...@sheep.art.pl wrote: - Bower in the development environment, - Bower configuration

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 19 November 2014 03:14, Radomir Dopieralski openst...@sheep.art.pl wrote: On 18/11/14 12:54, Matthias Runge wrote: On Tue, Nov 18, 2014 at 09:36:00PM +1100, Richard Jones wrote: I guess I got the message that turning bower packages into system packages was something that the Linux

Re: [openstack-dev] [Horizon] proposal: alternating weekly meeting time [doodle poll created]

. Richard On 12 November 2014 12:45, Richard Jones r1chardj0...@gmail.com wrote: I have set up a doodle poll to let folk enter their preferred times. It's in UTC/GMT (/London time, because doodle) so use something like http://everytimezone.com/ to figure that out :) https://doodle.com

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

: - there are no other projects that use bower components, so we don't need to ensure cross-project compatibility - we can vet new versions of bower components as part of standard Horizon change review Richard On 19 November 2014 06:43, Richard Jones r1chardj0...@gmail.com wrote: On 19

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

. On 11/18/2014 07:59 AM, Richard Jones wrote: I was envisaging us creating a tool which generates xstatic packages from bower packages. I'm not the first to think along these lines http://lists.openstack.org/pipermail/openstack-dev/2014-March/031042.html I think that's a very good idea

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 21 November 2014 16:12, Thomas Goirand z...@debian.org wrote: On 11/21/2014 10:52 AM, Richard Jones wrote: On 11/18/2014 04:22 PM, Radomir Dopieralski wrote: If we use Bower, we don't need to use Xstatic. It would be pure overhead. Bower already takes care of tracking

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

All the bower components I've used have included full source alongside any minified versions. On Sat, 22 Nov 2014 07:40 Fox, Kevin M kevin@pnnl.gov wrote: Simply having a git repository does not imply that its source. In fact, if its considered compiled (minified), I'm thinking the debian

Re: [openstack-dev] [Horizon] proposal: alternating weekly meeting time [doodle poll created]

on the excel sheet and my code :) According to the meetings wiki page, we should be able to get an IRC room at any of the above times. Richard On Wed Nov 19 2014 at 9:15:40 AM Richard Jones r1chardj0...@gmail.com wrote: Thanks everyone who has responded. I'm going to leave the poll open

Re: [openstack-dev] [Horizon] proposal: alternating weekly meeting time [doodle poll created]

Thanks! On Tue Nov 25 2014 at 3:15:49 AM Yves-Gwenaël Bourhis yves-gwenael.bour...@cloudwatt.com wrote: Le 24/11/2014 04:20, Richard Jones a écrit : Thanks everyone, I've closed the poll. I'm sorry to say that there's no combination of two timeslots which allows everyone to attend

Re: [openstack-dev] [horizon] REST and Django

://blueprints.launchpad.net/horizon/+spec/launch-instance-redesign -Travis From: Richard Jones r1chardj0...@gmail.com Date: Wednesday, November 26, 2014 at 11:55 PM To: Travis Tripp travis.tr...@hp.com, Thai Q Tran/Silicon Valley/IBM tqt...@us.ibm.com, David Lyle dkly...@gmail.com, Maxime Vidori

Re: [openstack-dev] [horizon] REST and Django

for Richard Jones ---11/27/2014 05:38:53 PM---On Fri Nov 28 2014 at 5:58:00 AM Tripp, Travis S travis.tr]Richard Jones ---11/27/2014 05:38:53 PM---On Fri Nov 28 2014 at 5:58:00 AM Tripp, Travis S travis.tr...@hp.com wrote: From: Richard Jones r1chardj0...@gmail.com To: Tripp, Travis S travis.tr

[openstack-dev] [Horizon] REST API split and new requirements.txt

Hi all, just to let you know that on request from Thai I split the REST API change into two: https://review.openstack.org/#/c/136676 - original change which just has the base code https://review.openstack.org/#/c/139532 - keystone specifics The identity WIP should now base itself off the

Re: [openstack-dev] [horizon] REST and Django

to duplicate some logic in the middleware. On Tue, Dec 2, 2014 at 4:45 PM, Adam Young ayo...@redhat.com wrote: On 12/02/2014 12:39 AM, Richard Jones wrote: On Mon Dec 01 2014 at 4:18:42 PM Thai Q Tran tqt...@us.ibm.com wrote: I agree that keeping the API layer thin would be ideal. I should add

Re: [openstack-dev] Moving _conf and _scripts to dashboard

+1 to moving application configuration to the application, out of the library. Richard On Thu Dec 11 2014 at 10:38:20 AM Thai Q Tran tqt...@us.ibm.com wrote: The way we are structuring our javascripts today is complicated. All of our static javascripts reside in /horizon/static and are

Re: [openstack-dev] [horizon] REST and Django

On Fri Dec 12 2014 at 1:06:08 PM Tripp, Travis S travis.tr...@hp.com wrote: ​Do we really need the lines:​ project = api.keystone.tenant_get(request, id) kwargs = _tenant_kwargs_from_DATA(request.DATA, enabled=None) ​ I agree that if you already have all the data it is really bad to have

Re: [openstack-dev] [horizon] static files handling, bower/

This is a good proposal, though I'm unclear on how the static_settings.py file is populated by a developer (as opposed to a packager, which you described). Richard On Fri Dec 19 2014 at 12:59:37 AM Radomir Dopieralski openst...@sheep.art.pl wrote: Hello, revisiting the package

Re: [openstack-dev] [horizon] static files handling, bower/

On Wed Jan 21 2015 at 7:00:12 AM Matthew Farina m...@mattfarina.com wrote: Radomir, maybe you can help me better understand where this would go. I have a few questions. First, can you point me to a time when horizon used system packages successfully for JavaScript libraries? When I looked

Re: [openstack-dev] [horizon] static files handling, bower/

On Fri Jan 23 2015 at 4:28:59 AM Matthew Farina m...@mattfarina.com wrote: I would like to add one more nuance to this discussion that I don't remember seeing. JavaScript libraries run in web browser in their JavaScript engines (like v8) rather than on the server. A version of a JS library

Re: [openstack-dev] [horizon] static files handling, bower/

On Mon Jan 05 2015 at 7:59:14 PM Radomir Dopieralski openst...@sheep.art.pl wrote: On 05/01/15 00:35, Richard Jones wrote: On Mon Dec 22 2014 at 8:24:03 PM Radomir Dopieralski openst...@sheep.art.pl mailto:openst...@sheep.art.pl wrote: On 20/12/14 21:25, Richard Jones wrote

Re: [openstack-dev] [horizon] static files handling, bower/

that should only be used by Horizon. Is there some other reason that this should have to go through global requirements? Thanks, Travis From: Richard Jones r1chardj0...@gmail.commailto:r1chardj0...@gmail.com Reply-To: OpenStack List openstack-dev@lists.openstack.orgmailto: openstack-dev

Re: [openstack-dev] [horizon] static files handling, bower/

Thanks, Radomir. How much detail from this discussion should be captured in the blueprint? I'm afraid I'm more familiar with the Python PEP process. On Thu Jan 08 2015 at 11:38:57 PM Radomir Dopieralski openst...@sheep.art.pl wrote: On 06/01/15 01:53, Richard Jones wrote: I think the only

Re: [openstack-dev] [horizon] static files handling, bower/

easier for the re-packagers since they'll know which files they need to cater for in static_settings.py Richard On Mon Dec 22 2014 at 8:24:03 PM Radomir Dopieralski openst...@sheep.art.pl wrote: On 20/12/14 21:25, Richard Jones wrote: This is a good proposal, though I'm unclear on how

[openstack-dev] [Horizon] Rethinking the launch-instance wizard model

Hi folks, Currently the launch instance model file does all the fetching of various bits of data. Combined with all of the controllers also being loaded at wizard startup, this results in some very difficult synchronisation issues*. An issue I've run into is the initialisation of the controller

Re: [openstack-dev] [horizon] bower

On Sun, 8 Mar 2015 at 04:59 Michael Krotscheck krotsch...@gmail.com wrote: Anyone wanna hack on a bower mirror puppet module with me? BTW are you aware of this spec for bower/Horizon/infra? https://review.openstack.org/#/c/154297/ Richard

Re: [openstack-dev] [Horizon]Informal Pre-summit get together

I'm planning on wearing my openstack badge, to make things a little easier for those I don't spend all week on hangouts with ;) On Sun, 17 May 2015 at 16:33 Michael Krotscheck krotsch...@gmail.com wrote: Do you have any distinguishing features? Like an enormous openstack hat? On Sun, May 17,

[openstack-dev] [Horizon] high priority patches, please review

Hi Horizon devs, The following test patches are a high priority, blocking further new work in Liberty until they're landed. Please consider helping review them to get the landed ASAP: https://review.openstack.org/#/c/170554/ https://review.openstack.org/#/c/167738/

[openstack-dev] Angular dependencies and the hz.dashboard namespace

The Adding Angular Identity Dashboard[1] patch exposed an issue I saw previously that worried me[2]. I believe during recent Horizon work the concept of angular module namespaces and dependencies have been conflated. There's this idea that if you create a submodule inside a module namespace you

Re: [openstack-dev] [horizon] Angular dependencies and the hz.dashboard namespace

On 20 June 2015 at 09:11, Thai Q Tran tqt...@us.ibm.com wrote: -Richard Jones r1chardj0...@gmail.com wrote: - To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org From: Richard Jones r1chardj0...@gmail.com Date: 06/19/2015 03:49PM

Re: [openstack-dev] [javascript] [horizon] [merlin] [refstack] Javascript Linting

JSCS in Horizon has been extended with the John Papa style guidelines to enforce consistent angularjs code style*. It's no longer just a findbug tool. I don't have time to investigate - can ESLint perform the same role for Horizon? Current Horizon activity involves a whole lot of bringing code

Re: [openstack-dev] [javascript] [horizon] [merlin] [refstack] Javascript Linting

Sorry, wrong patch. That one added the style requirement to the project contribution guidelines. This is the one that added the .jscsrc config: https://review.openstack.org/#/c/185725/ On Tue, 16 Jun 2015 at 14:21 Richard Jones r1chardj0...@gmail.com wrote: JSCS in Horizon has been extended

Re: [openstack-dev] [horizon] Angular-Django i18n

Hi Thai, Thanks for writing that up! As I can tell the blueprint only has the whiteboard which is kinda yuck, so here's my comments: I'm already on the record for preferring markup approach 3 so we can avoid having to write our own implementation of a translation engine. I really, really don't

[openstack-dev] [Horizon] configuration of plugins in an angularjs world

Hi all, Just a new conundrum for you :) At the top level of our base.html dashboard app, we have some dependencies 'horizon.auth', 'horizon.framework' and 'hz.dashboard' (that name will change to 'horizon.dashboard', but that's for another day). I think we need to remove 'hz.dashboard' from that

Re: [openstack-dev] [Horizon] dashboard-app split in horizon

move forward, won’t that file just end up as a toast element and nothing more? Maybe I’m misinterpreting it, I’m not familiar with toastService. Rob From: Richard Jones r1chardj0...@gmail.com Reply-To: OpenStack Development Mailing List (not for usage questions) openstack-dev

Re: [openstack-dev] [Horizon] dashboard-app split in horizon

? Richard On Sat, 23 May 2015 at 11:46 Richard Jones r1chardj0...@gmail.com wrote: As part of the ongoing Horizon project code reorganisation, we today agreed to clean up the Horizon-the-Framework and OpenStack Dashboard separation issue by doing a couple of things: 1. nuke (the recently

[openstack-dev] [Horizon] dashboard-app split in horizon

As part of the ongoing Horizon project code reorganisation, we today agreed to clean up the Horizon-the-Framework and OpenStack Dashboard separation issue by doing a couple of things: 1. nuke (the recently-created) horizon dashboard-app by moving the angular app over to dashboard and the other

Re: [openstack-dev] [nova][api] Pagination in thre API

As a consumer of such APIs on the Horizon side, I'm all for consistency in pagination, and more of it, so yes please! On 5 November 2015 at 13:24, Tony Breeds wrote: > On Thu, Nov 05, 2015 at 01:09:36PM +1100, Tony Breeds wrote: > > Hi All, > > Around the middle of

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

+1 this would definitely be the best approach from Horizon's perspective since we can cache the capabilities per-flavour. Having to request capabilities per-instance would be an unreasonable burden on the poor users of Horizon. On 6 November 2015 at 23:09, Sean Dague wrote: > On

Re: [openstack-dev] [javascript] [qa] [eslint-config-openstack] Nominating Cindy Lu for eslint-config-openstack-core

+1 On 10 July 2015 at 05:53, David Lyle dkly...@gmail.com wrote: On Thu, Jul 9, 2015 at 1:33 PM, Michael Krotscheck krotsch...@gmail.com wrote: Hey everyone! We've been hard at work getting some solid, shared code style rules in place for our javascript code, and nobody's been more

Re: [openstack-dev] [horizon] URL Sanity

Interesting idea, and in general I'm for consistency. I can't speak directly to the network/port question, though it seems to me that if ports must be attached to networks then it makes sense for the URL to reflect that. On the other hand, some could argue that the django URL routing is ...

Re: [openstack-dev] [horizon] python-selenium landed in Debian main today (in Debian Experimental for the moment)

On 9 September 2015 at 05:35, Thomas Goirand wrote: > After the non-free files were removed from the package (after I asked > for it through the Debian bug https://bugs.debian.org/770232), Selenium > was uploaded and reached Debian Experimental in main today (ie: Selenium > is

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

The etherpad that we had running for the bulk of L was really handy; something like that would be great to keep using to let folks know what is in play. On 29 September 2015 at 19:32, Rob Cresswell (rcresswe) wrote: > I wasn’t really envisioning a big discussion on the bugs;

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

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

[openstack-dev] [all] Liberty release - what is the correct version - 2015.2.0, 8.0.0 or 12.0.0?

Hi all, Historically OpenStack releases are versioned .N as documented in the Release Naming wiki page[1]. The Liberty Release Schedule[2] has the version 2015.2.0. However, in Horizon land, I've been informed that OpenStack is moving to semver. I can't find any information about this move

[openstack-dev] [horizon][release][infra] New xstatic package release proposal

TL;DR: "Releasing xstatic packages" https://review.openstack.org/#/c/253296/ xstatic is an existing standard for packaging up static resources for web development (HTML, Javascript and CSS) as Python modules. Horizon makes use of two dozen xstatic packages. We need a

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

om me! Thanks for all the reviews and patches from > your > > minions Richard! > > > > > > - Original message - > > From: David Lyle <dkly...@gmail.com> > > To: OpenStack Development Mailing List < > openstack-dev@lists.openstack.org> >

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

+1! On 3 December 2015 at 07:31, Matthias Runge wrote: > On 02/12/15 19:52, David Lyle wrote: > > I propose adding Timur Sufiev[1] to horizon-core. > > > > Over the last several cycles Timur has consistently been providing > > great reviews, actively participating in the

Re: [openstack-dev] [Horizon] naming of Javascript bits

confusing to >> use it in other places. >> >> With regards to tying the folder path and the Service/Controller I'd >> mostly go with that as that encourages simpler rules on how to namespace. >> >> For the particular patch you mentioned, the namespaces had a bit of churn >&

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

Let's do it. I'd like to suggest we use an etherpad to keep track of what people have done. If it's not created when I start my day, I'll make one. Richard On 19 November 2015 at 22:19, Rob Cresswell (rcresswe) wrote: > Hey folks, > > Our bug list is… rather large.

Re: [openstack-dev] [Horizon] Updating XStatic packages

In terms of process, obviously updating the data in the xstatic is relatively easy (for most packages) but I wonder from a review standpoint what sort of process we should have here. To approve a merge of an xstatic package update, I feel like I should have, in order of preference: 1. a link to

Re: [openstack-dev] [Horizon] Routing in Horizon

The tag addition has had to be reverted as it broke other parts of the application (notably lazy loaded tabs like Instance Details), sadly. Regarding which router to use - I've used the built-in router in the past quite successfully. I think I'd want to see a solid reason for using a 3rd party

[openstack-dev] [Horizon] xstatic publishing update - broken xstatic-angular-bootstrap

Hi folks, I released a couple of broken xstatic-angular-bootstrap packages to pypi yesterday - 0.11.0.4 and 0.11.0.5. There was to be an automated release of 0.11.0.6 through openstack-release, but I've abandoned that as it contained the same breakage. I've performed an emergency direct upload of

[openstack-dev] [Horizon] New procedure for releasing xstatic packages

Hi folks, It's been a lng time coming, but we're almost there. I've put up a BP outlining the steps we need to get over the line and start releasing those looong awaited updates of our xstatic packages: https://blueprints.launchpad.net/horizon/+spec/xstatic-release-process I'll be

Re: [openstack-dev] [Horizon] Handling 401 in new REST API

To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Cc: > Subject: Re: [openstack-dev] [Horizon] Handling 401 in new REST API > Date: Thu, Jan 28, 2016 8:46 AM > > I think that's the sane thing to do. > >

[openstack-dev] [Horizon] Handling 401 in new REST API

Hi fellow angular/REST Horizon developers, I'd like to propose that we handle HTTP 401 responses at the core of the new angular code interfacing to our new REST API so that *any* 401 just does basically what the Django code used to: redirect to the login page with a "from". What do y'all think?

Re: [openstack-dev] [Horizon] Recent integration tests failures

Ugh, dependencies with breaking API changes in minor point releases :/ On 2 February 2016 at 04:53, Timur Sufiev wrote: > Maintainers of outside dependencies continue to break our stuff :(. New > issue is https://bugs.launchpad.net/horizon/+bug/1540495 patch is > currently

[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

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

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 why one and not the other? In short, would anyone object to turning

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 10 March 2016 at 21:48, Beth Elwell <e.r.elw...@gmail.com> wrote: > > On 10 Mar 2016, at 07:46, Richard Jones <r1chardj0...@gmail.com> wrote: > >> It has been mentioned, xstatic packages can block the gate. We currently >> control xstatic package releases, th

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

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] How do we move forward with xstatic releases?

constraints will never meet in a dark alley behind some VM somewhere? app-catalog isn't in the integrated tests, so it's never going to break the gate like Horizon will... On 9 March 2016 at 11:07, Jeremy Stanley <fu...@yuggoth.org> wrote: > On 2016-03-08 17:25:41 +1100 (+1100), Richard Jo

[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] Proposal to add Diana Whitten to horizon-core

+1 we need Diana's perspective, knowledge and enthusiasm On 9 March 2016 at 10:03, Tripp, Travis S wrote: > +1, no questions asked. It is rare to find somebody with the passion that > Diana has shown. > > From: Lin Hua Cheng

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] [all][infra] revert new gerrit

On 19 March 2016 at 02:35, Monty Taylor wrote: > On 03/18/2016 08:31 AM, Andrey Kurilin wrote: > >> Hi all! >> >> I want to start this thread because I'm tired. I spent a lot of time, >> but I can't review as easy as it was with old interface. New Gerrit is >> awful. Here

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

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?

Thanks, Christopher (and the app-catalog team). On 21 March 2016 at 08:35, Christopher Aedo <d...@aedo.net> wrote: > On Sun, Mar 20, 2016 at 1:26 PM, Richard Jones <r1chardj0...@gmail.com> > wrote: > > Unfortunately none of this discussion solves the substantive issu

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

t;z...@debian.org> wrote: > 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 w

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

On 13 March 2016 at 07:06, Matthias Runge <mru...@redhat.com> wrote: > On 10/03/16 08:46, Richard Jones wrote: > > On 10 March 2016 at 18:23, Matthias Runge <mru...@redhat.com > > <mailto:mru...@redhat.com>> wrote: > > > > 4.alt.2: > > mo

  1   2   >