Hi,
I'm with Systems Design & Engineering group and I'm working on the Data Hub in CentOS CI OpenShift.
Major part of Data Hub infrastructure is Elasticsearch 5. Elasticsearch 5 is not officially supported in OpenShift 3.5 deployed in CentOS CI, we're working on getting proper Elasticsearch 5 support into OpenShift 3.7 and most likely we'll need at least OpenShift 3.6 features to properly support Elasticsearch 5. The reason for the requirement of OpenShift 3.6 is because we're moving to the new oauth-proxy to secure the routes for Kibana/Cerebro web ui, which requires OpenShift 3.6.
It would be great to have CentOS CI OpenShift environment upgraded to 3.6 soon after 3.6 is out.
Thanks, Anton.
Welcome to the CentOS CI team Anton, happy to have you onboard.
w.r.t 3.6 - there are some test builds already in place, I am CC'ing in troy who has details. Are we looking at plugging into the build, test infra there ?
Ari should have more info around this as well.
On 12/07/17 16:20, Anton Sherkhonov wrote:
Hi,
I'm with Systems Design & Engineering group and I'm working on the Data Hub in CentOS CI OpenShift.
Major part of Data Hub infrastructure is Elasticsearch 5. Elasticsearch 5 is not officially supported in OpenShift 3.5 deployed in CentOS CI, we're working on getting proper Elasticsearch 5 support into OpenShift 3.7 and most likely we'll need at least OpenShift 3.6 features to properly support Elasticsearch 5. The reason for the requirement of OpenShift 3.6 is because we're moving to the new oauth-proxy to secure the routes for Kibana/Cerebro web ui, which requires OpenShift 3.6.
It would be great to have CentOS CI OpenShift environment upgraded to 3.6 soon after 3.6 is out.
Thanks, Anton.
On Thu, Jul 13, 2017 at 6:23 AM, Karanbir Singh kbsingh@centos.org wrote:
Welcome to the CentOS CI team Anton, happy to have you onboard.
w.r.t 3.6 - there are some test builds already in place, I am CC'ing in troy who has details. Are we looking at plugging into the build, test infra there ?
I'm working off of alpha 2 of openshift 3.6 which is already available. I'm fine with developing locally, it's just that the deployment will require 3.6 features.
Ari should have more info around this as well.
On 12/07/17 16:20, Anton Sherkhonov wrote:
Hi,
I'm with Systems Design & Engineering group and I'm working on the Data Hub in CentOS CI OpenShift.
Major part of Data Hub infrastructure is Elasticsearch 5. Elasticsearch 5 is not officially supported in OpenShift 3.5 deployed in CentOS CI, we're working on getting proper Elasticsearch 5 support into OpenShift 3.7 and most likely we'll need at least OpenShift 3.6 features to properly support Elasticsearch 5. The reason for the requirement of OpenShift 3.6 is because we're moving to the new oauth-proxy to secure the routes for Kibana/Cerebro web ui, which requires OpenShift 3.6.
It would be great to have CentOS CI OpenShift environment upgraded to 3.6 soon after 3.6 is out.
Thanks, Anton.
-- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc
Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
On Jul 13 13:55, Anton Sherkhonov wrote:
On Thu, Jul 13, 2017 at 6:23 AM, Karanbir Singh kbsingh@centos.org wrote:
Welcome to the CentOS CI team Anton, happy to have you onboard.
w.r.t 3.6 - there are some test builds already in place, I am CC'ing in troy who has details. Are we looking at plugging into the build, test infra there ?
I'm working off of alpha 2 of openshift 3.6 which is already available. I'm fine with developing locally, it's just that the deployment will require 3.6 features.
I think we can plan on refreshing to 3.6 soon after release. Are your hostmounted ES roles applicable to 3.6 right now, or is that going to take a bit of work?
One thing that would be good to do is work with the CentOS Container Pipeline folks to get your containers built through that process. https://github.com/centos/container-index
Ari should have more info around this as well.
On 12/07/17 16:20, Anton Sherkhonov wrote:
Hi,
I'm with Systems Design & Engineering group and I'm working on the Data Hub in CentOS CI OpenShift.
Major part of Data Hub infrastructure is Elasticsearch 5. Elasticsearch 5 is not officially supported in OpenShift 3.5 deployed in CentOS CI, we're working on getting proper Elasticsearch 5 support into OpenShift 3.7 and most likely we'll need at least OpenShift 3.6 features to properly support Elasticsearch 5. The reason for the requirement of OpenShift 3.6 is because we're moving to the new oauth-proxy to secure the routes for Kibana/Cerebro web ui, which requires OpenShift 3.6.
It would be great to have CentOS CI OpenShift environment upgraded to 3.6 soon after 3.6 is out.
Thanks, Anton.
-- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc
Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
On Thu, Jul 13, 2017 at 2:01 PM, Brian Stinson brian@bstinson.com wrote:
On Jul 13 13:55, Anton Sherkhonov wrote:
On Thu, Jul 13, 2017 at 6:23 AM, Karanbir Singh kbsingh@centos.org
wrote:
Welcome to the CentOS CI team Anton, happy to have you onboard.
w.r.t 3.6 - there are some test builds already in place, I am CC'ing in troy who has details. Are we looking at plugging into the build, test infra there ?
I'm working off of alpha 2 of openshift 3.6 which is already available.
I'm
fine with developing locally, it's just that the deployment will require 3.6 features.
I think we can plan on refreshing to 3.6 soon after release. Are your hostmounted ES roles applicable to 3.6 right now, or is that going to take a bit of work?
They are applicable, but w/o oauth-proxy - i.e. insecure.
One thing that would be good to do is work with the CentOS Container Pipeline folks to get your containers built through that process. https://github.com/centos/container-index
ok. I'll check that.
Ari should have more info around this as well.
On 12/07/17 16:20, Anton Sherkhonov wrote:
Hi,
I'm with Systems Design & Engineering group and I'm working on the
Data
Hub in CentOS CI OpenShift.
Major part of Data Hub infrastructure is Elasticsearch 5. Elasticsearch 5 is not officially supported in OpenShift 3.5
deployed in
CentOS CI, we're working on getting proper Elasticsearch 5 support
into
OpenShift 3.7 and most likely we'll need at least OpenShift 3.6
features
to properly support Elasticsearch 5. The reason for the requirement of OpenShift 3.6 is because we're
moving
to the new oauth-proxy to secure the routes for Kibana/Cerebro web
ui,
which requires OpenShift 3.6.
It would be great to have CentOS CI OpenShift environment upgraded to 3.6 soon after 3.6 is out.
Thanks, Anton.
-- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc
Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-
Anton Sherkhonov -
Brian Stinson -
Karanbir Singh