Re: [openstack-dev] [Horizon][searchlight] Sharing resource type implementations

I've completed this work. The two patches to migrate the code over and one additional bug fix are: Horizon: Copy os-nova-servers from searchlight ui https://review.openstack.org/#/c/444095/ Searchlight UI: Remove os-nova-servers resource type https://review.openstack.org/#/c/450067/

Re: [openstack-dev] [Horizon][searchlight] Sharing resource type implementations

at the moment (I think because of bug https://bugs.launchpad.net/searchlight/+bug/1648255). Richard On 14 March 2017 at 09:43, Richard Jones <r1chardj0...@gmail.com> wrote: > I'll definitely be looking at getting a searchlight-ui patch up for > the mirror side of my Horizon patch

Re: [openstack-dev] [Horizon][searchlight] Sharing resource type implementations

/tree/master/devstack > > Thanks, > Travis > > On 3/9/17, 10:58 PM, "Richard Jones" <r1chardj0...@gmail.com> wrote: > > Thanks, Steve! > > I've put together an initial patch > https://review.openstack.org/#/c/444095/ which pulls in the >

Re: [openstack-dev] [Horizon][searchlight] Sharing resource type implementations

nova-servers) > to the modules we'll be OK. If you or Rob put a patch up against horizon I > (or a willing victim/volunteer) can test a searchlight-ui patch against it. > > > Original message ---- > From: Richard Jones <r1chardj0...@gmail.com> > Date: 3/9/17 21:13 (

Re: [openstack-dev] [Horizon][searchlight] Sharing resource type implementations

existing usage in searchlight ui. We could bikeshed this for ages, so if I could just get Rob and Steve to wrestle over it or something, that'd be good. Rob's pretty scrappy. Richard On 10 March 2017 at 09:56, Richard Jones <r1chardj0...@gmail.com> wrote: > OK, I will work

Re: [openstack-dev] [Horizon][searchlight] Sharing resource type implementations

ht-ui doesn’t have to carry some >> horrible workarounds and can just remove the code from their repo. >> >>Basically; start putting the code in the Horizon repo, and when its done, >> Searchlight-UI can remove it from their repo. >> >>Rob >>

[openstack-dev] [Horizon][stable][requirements] Modifying global-requirements to cap xstatic package versions

Hi folks, We've run into some issues with various folks installing Horizon and its dependencies using just requirements.txt which doesn't limit the versions of xstatic packages beyond some minimum version. This is a particular problem for releases prior to Ocata since those are not compatible

Re: [openstack-dev] [horizon] PTG Summary

On 28 February 2017 at 20:42, Rob Cresswell wrote: >> - Use [horizon-plugin] mailer tag to keep people up to date > > So the idea here is to send an email for changes that are likely to affect > plugins; new libs for example, or changes to core components, with the >

Re: [openstack-dev] [horizon] PTG Summary

On 28 February 2017 at 02:28, Rob Cresswell wrote: > Quick summary of the PTG for those who missed it. Here's the etherpad, with > notes inline: https://etherpad.openstack.org/p/horizon-ptg-pike Was there much discussion around project health, and the lack of core

Re: [openstack-dev] [horizon] PTG Summary

On 28 February 2017 at 02:28, Rob Cresswell wrote: > Quick summary of the PTG for those who missed it. Here's the etherpad, with > notes inline: https://etherpad.openstack.org/p/horizon-ptg-pike Thanks, Rob! > - Use [horizon-plugin] mailer tag to keep people up to

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

Hi folks, A quiet week this week as folks gear up for Pike and the PTG next week. We did get Ocata RC2 out the door this week with those final few bug fixes and the wonderful translations from the i18n team! Thanks to everyone who helped make Ocata Horizon happen :-) If you're going to the PTG,

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

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

[openstack-dev] [Horizon] Final project mascot

Hi folks, Here's the final mascot/logo from the Foundation. Richard -- Forwarded message -- From: Heidi Joy Tretheway <heidi...@openstack.org> Date: 14 February 2017 at 08:49 Subject: Horizon project mascot To: Rob Cresswell <robert.cressw...@outlook.com>, R

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

Hi folks, We're well on our way to RC2, which will probably be tagged early next week unless someone objects.We've got the requirements.txt updates for the xstatic packages in but just need those last couple of domain context related patches to get in (poke, poke...) Use domain_context not

Re: [openstack-dev] [requirements] [Horizon][Karbor][Magnum] Requesting FFE for xstatic packages

com> wrote: > On Tue, Feb 07, 2017 at 10:39:41AM +1100, Richard Jones wrote: >> Hi requirements team, >> >> We've had a downstream packager come to us with issues packaging the >> Horizon RC as described in this bug report: >> >> https://bugs.launchpad.ne

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

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

[openstack-dev] [requirements] [Horizon] Requesting FFE for xstatic packages

Hi requirements team, We've had a downstream packager come to us with issues packaging the Horizon RC as described in this bug report: https://bugs.launchpad.net/horizon/+bug/1662180 The issues stems from the requirements file having several xstatic package minimum versions specified that are

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

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

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

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

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

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

[openstack-dev] [Horizon] PTL non-candidacy

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

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

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

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

t 6:57 PM, Rob Cresswell > <robert.cressw...@outlook.com> wrote: >> >> Just a thought: With the way we currently do microversions, wouldnt this >> request 2.40 for every request ? There's a pretty good chance that would >> break things. >> >> Rob >> &

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

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

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

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

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

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

[openstack-dev] Meeting at 20:00UTC this Wednesday, 11th January

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

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

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

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

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

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

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

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

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

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

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

[openstack-dev] [Requirements] [Horizon] upper-constraints shenanigans and development milestones

Hi folks, We in Horizon land are looking to update to a new version of one of our dependencies, Angular Bootstrap version 2.2.0. We do this through xstatic packaging, so the release we'll be making is actually xstatic-angular-bootstrap 2.2.0.0 This release is backward incompatible and breaks

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

>> On 6 Dec 2016, at 20:19, Richard Jones <r1chardj0...@gmail.com> wrote: >> Please let me know what you think (by December 12) of this draft for >> our Horizon team mascot. > On 7 December 2016 at 07:38, Rob Cresswell (rcresswe) <rcres...@cisco.com> wrote: >

[openstack-dev] [Horizon] Draft team mascot

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Hi Horizon core team, I propose Kenji Ishii as a new Horizon core reviewer. Kenji has been a solid Horizon contributor for some time, with thoughtful and helpful reviews showing good judgment and good knowledge of Horizion and related systems. Please respond with your votes by Friday. Thanks,

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

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

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

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

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

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

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

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

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

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

[openstack-dev] [Horizon] Summit recap

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

Re: [openstack-dev] Resigning from horizon core

Thank-you for everything, Matthias! I'll see you around OpenStack land :-) Richard Sent from my portable device, please excuse the brevity. On 26 Oct. 2016 17:30, "Matthias Runge" wrote: > Hello, > > this has been long due (and thank you Richard for reminding me), > my job

[openstack-dev] [Horizon] Summit preparation

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

Re: [openstack-dev] [Horizon] Meeting this week cancelled

Oh, and the meeting next week (26th) will also not happen due to the summit. Richard On 19 October 2016 at 14:22, Richard Jones <r1chardj0...@gmail.com> wrote: > Hi folks, > > With the summit almost upon us, and no agenda items or significant > notices, I'm cancellin

[openstack-dev] [Horizon] Meeting this week cancelled

Hi folks, With the summit almost upon us, and no agenda items or significant notices, I'm cancelling this week's team meeting (was scheduled for 2016/10/19 20:00UTC). Cheers, Richard __ OpenStack Development Mailing

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

Hi folks, The kind folks from Keystone have organised to have a shared session at the summit, thanks to Steve Martinelli for offering. In our meeting this week[1] we covered a few topics, notably: - the per-session etherpads for the summit are up now, linked from the main summit etherpad[2] -

Re: [openstack-dev] [keystone][horizon] keystone/horizon integration session in barcelona

Thanks, Steve, this will be a valuable session! On 12 October 2016 at 08:14, Steve Martinelli wrote: > The keystone team had a spare fishbowl session, and we decided to use it > to collaborate with the horizon team on a few long standing issues we've > had between the

Re: [openstack-dev] [all][stable] Moving stable/mitaka to Phase-II and liberty to Phase-III

On 11 October 2016 at 08:34, Tony Breeds wrote: > On Mon, Oct 10, 2016 at 08:42:48AM +0200, Ihar Hrachyshka wrote: > > I think it would also make sense to *release* on the boundary of the > switch; > > so that it’s clear which phase a release followed. > > I agree, I

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

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

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

Hi folks, Congratulations to all contributors to the Newton release - a release we can all be proud of: http://docs.openstack.org/releasenotes/horizon/newton.html Thanks to Rob Cresswell for his leadership through the Newton release. I'm looking forward to seeing what we can achieve in Ocata.

Re: [openstack-dev] [horizon] gate failures (fragile integrated tests)

This seems to also be a connection issue to Firefox, but just in a different place: http://logs.openstack.org/69/375669/1/check/gate-horizon-dsvm-integration-deprecated-ubuntu-xenial/468d333/console.html#_2016-09-23_19_38_05_221999 Richard On 23 September 2016 at 22:18, Akihiro Motoki

[openstack-dev] [Horizon] Ocata design summit

Hi folks, Not long to go before the Ocata summit. We'll devote next week's team meeting[1] to discussing the design sessions. If you haven't done so already, please add your thoughts to the planning etherpad[2]. Thanks, Richard [1] https://wiki.openstack.org/wiki/Meetings/Horizon [2]

[openstack-dev] [Release] [FFE] two xstatic packages to be bumped in upper-constraints, please

Hi folks, We have two patches to upper-constraints up that we'd like to see merged for Newton. The package updates in question only changed meta-data, but they did so in a way that fixes issues for downstream, and it makes sense to keep upper-constraints in line with what they'll be packaging.

[openstack-dev] [Horizon] PTL candidacy

or keep up to date with what’s happening in Horizon. Thank you, Richard Jones __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [horizon] [horizon-plugin] AngularJS 1.5.8

Let's do it, yep. On 3 August 2016 at 20:19, Rob Cresswell wrote: > Hi all, > > Angular 1.5.8 is now updated in its XStatic repo: > https://github.com/openstack/xstatic-angular > > I've done some manual testing of the angular content and found no issues > so far.

Re: [openstack-dev] [horizon] Angular panel enable/disable not overridable in local_settings

On 3 August 2016 at 00:32, Rob Cresswell wrote: > Hi all, > > So we seem to be adopting a pattern of using UPDATE_HORIZON_CONFIG in the > enabled files to add a legacy/angular toggle to the settings. I don't like > this, because in settings.py the enabled files are

[openstack-dev] [Horizon] ResourceType'ing the Swift UI and a bit of a speed bump

Hi folks, I've just pushed up an initial patch which implements *some* of the Swift UI functionality using the ResourceType framework: https://review.openstack.org/347114 I say *some* because there's an issue in the current code which will require some refactoring to make it work in a

Re: [openstack-dev] [Horizon] Angular action services and initScope

Thanks for the response, Thai! Before I get into addressing your specifics below, I've put up a proof of concept patch that modifies images create-volume to remove the need for scope: https://review.openstack.org/#/c/345145 On 21 July 2016 at 08:23, Thai Q Tran wrote: >

Re: [openstack-dev] [Horizon] On testing...

e tests to tempest will make it more difficult to run them locally. > Also there is > > 5. Parallelize integration tests. > Ah, yep, good catch. I'm not sure whether this will negatively impact our stability on some of the test nodes though :/ Richard > On Wed, Jul 20, 2016 at

[openstack-dev] [Horizon] On testing...

Hi folks, Sorry I didn't make the meeting this morning :-( We touched on testing at the mid-cycle and again it came up in the meeting this morning. We identified two issues: 1. Our integration test suite cannot grow to too many more tests because they take too long to run (and get auto-killed).

Re: [openstack-dev] [Horizon] Angular action services and initScope

On 18 July 2016 at 11:49, Rob Cresswell wrote: > Maybe I'm missing the point, but the schema stuff just defines a model and > passes it to the schema directive via ctrl; doesn't that remove any issues > with workflows? ui-bootstraps modal and modalinstance already

Re: [openstack-dev] [Horizon] Angular action services and initScope

On 18 July 2016 at 11:34, Tripp, Travis S <travis.tr...@hpe.com> wrote: > TL;DR, I’ll be quite happy to get rid of the need for initScope and like > exploring a common way to share model other than events. > > |From: Richard Jones <r1chardj0...@gmail.com> > | Date: Su

Re: [openstack-dev] [Horizon] Angular action services and initScope

ts own named model to store the data captured by the step - and as a side effect it can poke at (and watch) the data captured by other steps, which is often useful. Workflow $modal resolution supplies the workflow model for the consumer of the workflow to then to something with all that data.

Re: [openstack-dev] [horizon] Logo

+2 very appropriate On 17 July 2016 at 11:01, Diana Whitten wrote: > Dunno if there have been any suggestions, but I'd like to suggest a Shiba > Inu for the Horizon logo mascot. > > If you unfamiliar with a Shiba Inu, take a look here: >

[openstack-dev] [Horizon] Angular action services and initScope

Hi folks, Something that's been bothering me for a while is that the action services break the encapsulation model of Angular Services - that they are singletons, and consumable by multiple simultaneous consumers without those consumers affecting each other through their use of the Service. At

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

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

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

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

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

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?

will be proposing a patch soon. SOLUTION 6 - make zuul capable of performing atomic cross-repository commits. Richard Sent from my portable device, please excuse the brevity. On 8 Mar 2016 15:52, "Richard Jones" <r1chardj0...@gmail.com> wrote: > We've solved *most* of the issues a

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

[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

  1   2   >