Re: [openstack-dev] [searchlight] Matt Borland Searchlight UI Core Nomination

2016-09-19 Thread Aulino, Rick
+1 for Matt being a core. Great job Matt!

+1 for creating a new searchlight-ui core team that is more than the union of 
the Searchlight/Horizon core teams.

--
Rick Aulino

-Original Message-
From: Tripp, Travis S 
Sent: Monday, September 19, 2016 10:13 AM
To: OpenStack List 
Subject: [openstack-dev] [searchlight] Matt Borland Searchlight UI Core 
Nomination

Hello!
 
I am nominating Matt Borland for Searchlight UI core. Matt has been working on 
searchlight UI since we started it and he is the primary author of the angular 
registration framework in Horizon which Searchlight depends upon. Matt has the 
second most searchlight UI commits in Newton [0], but more impressively, Matt 
has more commits on Horizon than ANY other person in Newton [1]. In addition, 
Matt is a top 5 reviewer on Searchlight UI [2] and a 12 reviewer on horizon [3] 
He has provided thoughtful feedback and valuable insights throughout his time 
on Searchlight.

Searchlight UI core team is currently the combination of Searchlight cores and 
Horizon Cores.  With this change we would make a searchlight UI core group that 
can has core privileges in addition to those two groups.
 
[0] http://stackalytics.com/?metric=commits&module=searchlight-ui
[1] http://stackalytics.com/?module=horizon&metric=commits
[2] http://stackalytics.com/report/contribution/horizon/180
[3] http://stackalytics.com/report/contribution/searchlight-ui/180

Thanks,
Travis


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


Re: [openstack-dev] [searchlight] [ceilometer] [fuel] [freezer] [monasca] Elasticsearch 2.x gate support

2016-07-06 Thread Aulino, Rick
Folks,

A follow-up to Steve's earlier email.

Elasticsearch recommends that the version's major numbers match between 
Elasticsearch and the Elasticsearch python client [1]. To accomodate this, we 
have submitted a requirement patch to update the Elasticsearch client to 2.3.X.

If this is a concern, please comment on the patch:

https://review.openstack.org/#/c/338425

[1] https://elasticsearch-py.readthedocs.io/en/master

> I'm looking into supporting and testing Elasticsearch 2.x in Searchlight's 
> test jobs. Currently I don't know of any other projects that run tests 
> against Elasticsearch in the gate (since we had to add it to Jenkins [1]). 
> Several projects install the python elasticsearch client in requirements.txt, 
> and it is currently capped to <2.0 in global-requirements [2], and others 
> consume it directly through HTTP requests. Searchlight needs to move to 
> support Elasticsearch 2.x in Newton but we are aware that doing so will 
> affect other projects.
>
> Elasticsearch 2.x is backwards incompatible [3] with 1.x in some ways. The 
> python client library is similarly backwards-incompatible; it is strongly 
> recommended the client major version matches the server major version. In 
> testing Searchlight we found only a couple of fairly minor changes were 
> needed (and the 1.x client library seems to continue to work against a 2.x 
> server) , but YMMV. Devstack's default ES version is 1.4.2 [4] (which should 
> be changed to 1.7 in any case) and we obviously cannot change that until all 
> projects support 2.x.
>
> A wholesale change to move to Elasticsearch 2.x would require changing 
> global-requirements, but this may obviously break projects not ready for the 
> change. My questions for the projects affected are:
>
> * Have you tested with ES 2.x at all?
> * Do you have plans to move to ES 2.x?
>
> Our likely fallback is testing with the 1.x client until we can move devstack 
> and global-requirements to 2.x; if we discover issues in the meantime we will 
> include a deployer note that the python library needs to be updated if 
> Elasticsearch 2.x is in use.
>
> Thanks,
>
> Steve

--
Rick Aulino

HPCS R&D  
rick.aul...@hpe.com
Hewlett Packard Enterprise 970-898-0575

__
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