Hey David, Yeah I agree. I responded to Rob with the same thinking.
I don’t mind taking a first pass at the Horizon blueprint / work to provide an extensible space in the page header for plugins to post content. And I will then move the content of this blueprint, as you suggest, to the Vitrage-Dashboard repo ... which will leverage the above new Horizon Page Header Plugin blueprint. Greg. From: David Lyle <dkly...@gmail.com> Reply-To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org> Date: Thursday, June 1, 2017 at 12:50 PM To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [horizon] Blueprint process question There have been a couple of projects that would like some space in the page header. I think the work in Horizon is to provide an extensible space in the page header for plugins to post content. The UI plugin for Vitrage, in this case, would then be responsible for populating that content if desired. This specific blueprint should really be targeted at the Vitrage UI plugin and a separate blueprint should be added to Horizon to create the extension point in the page header. David On Wed, May 31, 2017 at 11:06 AM, Waines, Greg <greg.wai...@windriver.com<mailto:greg.wai...@windriver.com>> wrote: Hey Rob, Just thought I’d check in on whether Horizon team has had a chance to review the following blueprint: https://blueprints.launchpad.net/horizon/+spec/vitrage-alarm-counts-in-topnavbar The blueprint in Vitrage which the above Horizon blueprint depends on has been approved by Vitrage team. i.e. https://blueprints.launchpad.net/vitrage/+spec/alarm-counts-api let me know if you’d like to setup a meeting to discuss, Greg. From: Rob Cresswell <robert.cressw...@outlook.com<mailto:robert.cressw...@outlook.com>> Reply-To: "openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: Thursday, May 18, 2017 at 11:40 AM To: "openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [horizon] Blueprint process question There isn't a specific time for blueprint review at the moment. It's usually whenever I get time, or someone asks via email or IRC. During the weekly meetings we always have time for open discussion of bugs/blueprints/patches etc. Rob On 18 May 2017 at 16:31, Waines, Greg <greg.wai...@windriver.com<mailto:greg.wai...@windriver.com>> wrote: A blueprint question for horizon team. I registered a new blueprint the other day. https://blueprints.launchpad.net/horizon/+spec/vitrage-alarm-counts-in-topnavbar Do I need to do anything else to get this reviewed? I don’t think so, but wanted to double check. How frequently do horizon blueprints get reviewed? once a week? Greg. p.s. ... the above blueprint does depend on a Vitrage blueprint which I do have in review. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org<mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org<mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
