Re: RFC: OKD4 Roadmap Draft

2019-08-19 Thread Clayton Coleman
> On Aug 16, 2019, at 10:25 PM, Michael McCune wrote: > >> On Fri, Aug 16, 2019 at 2:36 PM Kevin Lapagna <4...@gmx.ch> wrote: >> >>> On Fri, Aug 16, 2019 at 4:50 PM Clayton Coleman wrote: >>> >>> Single master / single node configurati

Re: [4.x] POC on OpenStack without admin rights.

2019-08-17 Thread Clayton Coleman
User provisioned infra? You can host the ignition file on any HTTP server the machines can reach at boot. On Aug 17, 2019, at 11:45 AM, Gilles Le Bris wrote: I have already installed OpenShift 4.x on KVM. Now, I would like to install it for a POC on OpenStack (Rocky). But, I haven't got any

Re: [3.x]: openshift router and its own metrics

2019-08-16 Thread Clayton Coleman
On Aug 16, 2019, at 4:55 AM, Daniel Comnea wrote: On Thu, Aug 15, 2019 at 7:46 PM Clayton Coleman wrote: > > > On Aug 15, 2019, at 12:25 PM, Daniel Comnea wrote: > > Hi Clayton, > > Certainly some of the metrics should be preserved across reloads

Re: RFC: OKD4 Roadmap Draft

2019-08-16 Thread Clayton Coleman
On Fri, Aug 16, 2019 at 10:49 AM Clayton Coleman wrote: > > > On Aug 16, 2019, at 10:39 AM, Michael McCune wrote: > > > > On Wed, Aug 14, 2019 at 12:27 PM Christian Glombek > wrote: > >> The OKD4 roadmap is currently being drafted here: >> >

Re: RFC: OKD4 Roadmap Draft

2019-08-16 Thread Clayton Coleman
On Aug 16, 2019, at 10:39 AM, Michael McCune wrote: On Wed, Aug 14, 2019 at 12:27 PM Christian Glombek wrote: > The OKD4 roadmap is currently being drafted here: > > https://hackmd.io/Py3RcpuyQE2psYEIBQIzfw > > There was an initial discussion on it in yesterday's WG meeting, with some >

Re: [3.x]: openshift router and its own metrics

2019-08-15 Thread Clayton Coleman
with more details, can’t say off the top of my head Thoughts? Cheers, Dani On Thu, Aug 15, 2019 at 3:59 PM Clayton Coleman wrote: > Metrics memory use in the router should be proportional to number of > services, endpoints, and routes. I doubt it's leaking there and if it were

Re: [3.x]: openshift router and its own metrics

2019-08-15 Thread Clayton Coleman
Metrics memory use in the router should be proportional to number of services, endpoints, and routes. I doubt it's leaking there and if it were it'd be really slow since we don't restart the router monitor process ever. Stats should definitely be preserved across reloads, but will not be

Re: Follow up on OKD 4

2019-07-25 Thread Clayton Coleman
[jber...@redhat.com] > Sent: Thursday, July 25, 2019 11:23 AM > To: Clayton Coleman; Aleksandar Lazic > Cc: users; dev > Subject: Re: Follow up on OKD 4 > >> On 7/25/19 6:51 AM, Clayton Coleman wrote: >> 1. Openshift 4 isn’t flexible in the ways people want (Ie you want to &

Re: Follow up on OKD 4

2019-07-25 Thread Clayton Coleman
ro do people want". If there's a group who want to get more involved in the "build a distro" part of tools that exist, that definitely seems like a different use case. > > The redhat container catalog is a good start too, but we need to be > thinking all the way up to the k8s le

Re: Follow up on OKD 4

2019-07-25 Thread Clayton Coleman
y, I'm just throwing some ideas out there, I wouldn't consider my >> statements as advocating strongly in any direction. Surely FCoS is >> the natural fit, but I think considering other distros merits >> discussion. > > +1 > > Regards > Aleks > > >>>

Re: Follow up on OKD 4

2019-07-24 Thread Clayton Coleman
previous suggestion (the auto updating kube distro) has the concrete goal of “don’t worry about security / updates / nodes and still be able to run containers”, and fcos is a detail, even if it’s an important one. How would you pitch the alternative? > >> On Wed, Jul 24, 2019 a

Re: Follow up on OKD 4

2019-07-24 Thread Clayton Coleman
On Wed, Jul 24, 2019 at 12:45 PM Fox, Kevin M wrote: > Ah, this raises an interesting discussion I've been wanting to have for a > while. > > There are potentially lots of things you could call a distro. > > Most linux distro's are made up of several layers: > 1. boot loader - components to get

Re: Follow up on OKD 4

2019-07-24 Thread Clayton Coleman
> From: dev-boun...@lists.openshift.redhat.com [ > dev-boun...@lists.openshift.redhat.com] on behalf of Michael Gugino [ > mgug...@redhat.com] > Sent: Wednesday, July 24, 2019 7:40 AM > To: Clayton Coleman > Cc: users; dev > Subject: Re: Follow up o

Re: Follow up on OKD 4

2019-07-24 Thread Clayton Coleman
On Wed, Jul 24, 2019 at 10:40 AM Michael Gugino wrote: > I tried FCoS prior to the release by using the assembler on github. > Too much secret sauce in how to actually construct an image. I > thought atomic was much more polished, not really sure what the > value-add of ignition is in this

Re: Follow up on OKD 4

2019-07-21 Thread Clayton Coleman
On Sat, Jul 20, 2019 at 12:40 PM Justin Cook wrote: > Once upon a time Freenode #openshift-dev was vibrant with loads of > activity and publicly available logs. I jumped in asked questions and Red > Hatters came from the woodwork and some amazing work was done. > > Perfect. > > Slack not so

Re: Follow up on OKD 4

2019-07-19 Thread Clayton Coleman
> via email :) > > I'll send out more info here ASAP. Stay tuned! > > With kind regards > > CHRISTIAN GLOMBEK > Associate Software Engineer > > Red Hat GmbH, registred seat: Grassbrunn > Commercial register: Amtsgericht Muenchen, HRB 153243 > Managing directors: Charl

Re: [v4]: v4.1.4 is using internal registry, is this a bug?

2019-07-18 Thread Clayton Coleman
On Jul 18, 2019, at 6:24 PM, Daniel Comnea wrote: On Thu, Jul 18, 2019 at 10:08 PM Clayton Coleman wrote: > We generally bump "latest" symlink once it's in the stable channel, which > 4.1.6 is not in. 4.1.6 is still considered pre-release. > [DC]: i looked [1] and so

Re: [v4]: v4.1.4 is using internal registry, is this a bug?

2019-07-18 Thread Clayton Coleman
We generally bump "latest" symlink once it's in the stable channel, which 4.1.6 is not in. 4.1.6 is still considered pre-release. For your first error message, which installer binary were you using? Can you link to it directly? On Thu, Jul 18, 2019 at 3:55 PM Daniel Comnea wrote: > Hi, > >

Follow up on OKD 4

2019-07-17 Thread Clayton Coleman
Thanks for everyone who provided feedback over the last few weeks. There's been a lot of good feedback, including some things I'll try to capture here: * More structured working groups would be good * Better public roadmap * Concrete schedule for OKD 4 * Concrete proposal for OKD 4 I've heard

Re: Proposal: Deploy and switch to Discourse

2019-07-16 Thread Clayton Coleman
:It would probably be good to solicit feedback via a survey - gather suggestions, assess how many people prefer the existing communication mechanisms we have, etc. On Tue, Jul 16, 2019 at 12:31 PM Jason Brooks wrote: > On Fri, Jul 12, 2019 at 7:20 AM Neal Gompa wrote: > > > > On Fri, Jul 12,

Re: Proposal: Deploy and switch to Discourse

2019-07-12 Thread Clayton Coleman
Another note - we reuse the Kubernetes slack channel, and we would have no plans to remove that channel because we get a lot of joint overlap with kube development. Adding more channels to discuss means people just have to log into more places. > On Jul 12, 2019, at 11:48 AM, Colin Walters

Re: Proposal: Deploy and switch to Discourse

2019-07-12 Thread Clayton Coleman
We’ve historically used StackOverflow for threaded human questions / response problems. Discourse feels like it would overlap a lot with that, especially since SO is still usually better for search engines > On Jul 12, 2019, at 10:18 AM, Neal Gompa wrote: > >> On Fri, Jul 12, 2019 at 10:11 AM

Re: OKD 4 - A Modest Proposal

2019-06-28 Thread Clayton Coleman
On Jun 28, 2019, at 3:38 AM, Daniel Comnea wrote: On Fri, Jun 28, 2019 at 4:58 AM Clayton Coleman wrote: > > On Jun 26, 2019, at 1:08 PM, Colin Walters wrote: > > > > > > > > On Thu, Jun 20, 2019, at 5:20 PM, Clayton Coleman wrote: > > > > > >

Re: OKD 4 - A Modest Proposal

2019-06-27 Thread Clayton Coleman
> On Jun 26, 2019, at 1:08 PM, Colin Walters wrote: > > > > On Thu, Jun 20, 2019, at 5:20 PM, Clayton Coleman wrote: > > >> Because the operating system integration is so critical, we need to >> make sure that the major components (ostree, ignition, and

OKD 4 - A Modest Proposal

2019-06-20 Thread Clayton Coleman
tps://commons.openshift.org/events.html#event%7Cokd4-road-map-release-update-with-clayton-coleman-red-hat%7C960> to further explore these topics with the wider community. I hope you’ll join the conversation and look forward to hearing from the others across the community. Meeting details here

Re: [4.x]: thoughts on how folks should triage and open issues on the right repos?

2019-06-17 Thread Clayton Coleman
Historically we also had a bugzilla Origin component that we used. One challenge with GitHub issues is that they lack some of the tools that bugzilla has for triage and management, and so they always ended up being somewhat neglected (despite the best efforts of many people). I definitely agree

Re: [4.x]: any future plans for proxy-mode: ipvs ?

2019-06-11 Thread Clayton Coleman
Clayton, Dan, thanks for taking the time to respond, much appreciated. On Mon, Jun 10, 2019 at 5:46 PM Dan Williams wrote: > On Sat, 2019-06-08 at 14:52 -0700, Clayton Coleman wrote: > > OVN implements kube services on nodes without kube-proxy - is there a > > specific feature g

Re: OKD 4.x

2019-06-06 Thread Clayton Coleman
v-boun...@lists.openshift.redhat.com < dev-boun...@lists.openshift.redhat.com> *On Behalf Of *Clayton Coleman *Sent:* jeudi, 6 juin 2019 12:15 *To:* Alix ander *Cc:* OpenShift Users List ; dev@lists.openshift.redhat.com *Subject:* Re: OKD 4.x We’re currently working on how Fedora CoreOS wi

Re: OKD 4.x

2019-06-06 Thread Clayton Coleman
We’re currently working on how Fedora CoreOS will integrate into OKD. There’s a fair chunk of work that needs to be done and FCoS has a broader mission than RHCoS does, so its a bit further behind (since OpenShift 4 / OKD 4 require an OS with ignition and ostree). Stay tuned, I was going to write

Re: Openshift Origin Haproxy metrics exporter source

2019-02-08 Thread Clayton Coleman
https://github.com/openshift/router/blob/master/pkg/router/metrics/haproxy/haproxy.go Is what converts haproxy stats from the stats socket to prometheus metrics On Feb 8, 2019, at 8:48 AM, Gowtham Sundara < gowtham.sund...@rapyuta-robotics.com> wrote: Hello, May I know where the source code for

FYI: As of 4.0, all OKD images are being pushed to quay

2019-01-22 Thread Clayton Coleman
As we've grown ever more images for 4.0 we are now publishing images exclusively to quay for OKD builds. A subset is still being mirrored to docker but the 4.0 versions will be discontinued over time, so please don't rely on them. All images published by CI for 4.0 onward are at:

Re: origin-console

2018-12-18 Thread Clayton Coleman
https://github.com/openshift/console On Dec 18, 2018, at 3:54 PM, Neale Ferguson wrote: >From what sources are the origin-console:v3.11.0 image built? Neale ___ dev mailing list dev@lists.openshift.redhat.com

Re: Openshift Origin builds for CVE-2018-1002105

2018-12-06 Thread Clayton Coleman
for < 3.10 (not on OKD i suspect) > Thanks > > On Thu, Dec 6, 2018 at 8:50 PM Daniel Comnea > wrote: > >> Cheers for chime in Clayton. >> >> In this case you fancy cutting new minor release for 3.10/ 3.11 and then >> i'll take it over? >>

Re: Openshift Origin builds for CVE-2018-1002105

2018-12-06 Thread Clayton Coleman
This are the correct PRa On Dec 6, 2018, at 10:14 AM, Daniel Comnea wrote: I'll chime in to get some clarity The CentOS rpms are built by the PaaS SIG and is based on the Origin tag release. As such in order to have new origin rpms built/ pushed into CentOS repos we will need: - the

Re: Openshift Origin builds for CVE-2018-1002105

2018-12-06 Thread Clayton Coleman
Rpms from CI are here https://artifacts-openshift-release-3-11.svc.ci.openshift.org/repo/ I forgot srpms aren’t created via this process, there’s not an easy way to add them due to the size increase. The centos paas sig was also creating them (and they have srpms) and would be where I would

Re: Dropping oadm binary entirely

2018-11-09 Thread Clayton Coleman
4.0 and newer. On Fri, Nov 9, 2018 at 12:07 PM Daniel Comnea wrote: > Okay thanks for the information. > > So which version will be if is not 4.0 ? i guess is going to be 4.x+ ? > > On Fri, Nov 9, 2018 at 1:08 PM Maciej Szulik wrote: > >> 4.0 and newer. 3.11 is not affected by this change. >>

Re: tags v3.10 or v3.11?

2018-10-12 Thread Clayton Coleman
That image is not updated after 3.10. It was removed in favor of new images that split its responsibilities. On Fri, Oct 12, 2018 at 3:45 PM Omer Faruk SEN wrote: > Hello , > > I have just checked https://hub.docker.com/r/openshift/origin/tags/ and > it says tag v3.10 was just released 2 hours

OKD v3.11.0 has been tagged and pushed to GitHub

2018-10-11 Thread Clayton Coleman
https://github.com/openshift/origin/releases/tag/v3.11.0 contains the release notes and latest binaries. The v3.11.0 tag on docker.io is up to date and will be a rolling tag (new fixes will be delivered there). Thanks to everyone on their hard work!

Re: Plans on cutting Origin 3.11 / 4.0 ?

2018-10-10 Thread Clayton Coleman
I was waiting for some last minute settling of the branch, and I will cut an rc On Wed, Oct 10, 2018 at 10:49 AM Daniel Comnea wrote: > Hi, > > What are the plans on cutting a new Origin release ? I see on > _release-3.11_ branch on Origin as well as openshift-ansible git repos > however i

Re: CI automation location for RPMs is moving

2018-10-09 Thread Clayton Coleman
What website? Just use a slash at the end - all the CI jobs look like their working > On Oct 9, 2018, at 10:10 PM, Rich Megginson wrote: > > Was this ever fixed? Is this the cause of the website being currently > unresponsive? > > >> On 9/10/18 2:33 PM, Clayton Colem

Re: Future Installer - Ansible vs Terraform

2018-09-18 Thread Clayton Coleman
> On Sep 18, 2018, at 8:06 AM, Tobias Brunner wrote: > > Hi, > > It seems like the future OpenShift installer > (https://github.com/openshift/installer) will be based on the Tectonic > installer which uses Terraform in it's heart. What does this mean for > the Ansible based installer

Re: CI automation location for RPMs is moving

2018-09-10 Thread Clayton Coleman
to > http://rpms.svc.ci.openshift.org:8080/openshift-origin-v3.11/ (drops > https and adds port number). > > On Sat, Sep 8, 2018 at 9:27 PM Clayton Coleman > wrote: > >> Previously, all RPMs used by PR and the test automation or Origin were >> located in GCS. Starting

Re: CI automation location for RPMs is moving

2018-09-10 Thread Clayton Coleman
://rpms.svc.ci.openshift.org meant to be public available or is only available internally for your own deployments ? In addition, is the plan that everyone deploying OCP/ OKD on RHEL/ CentOS to use the above common repo (assuming is going to be public accessible ) ? Dani On Sun, Sep 9, 2018 at 3:26 AM Clayton

CI automation location for RPMs is moving

2018-09-08 Thread Clayton Coleman
Previously, all RPMs used by PR and the test automation or Origin were located in GCS. Starting with 3.11 and continuing forward, RPMs will be served from the api.ci cluster at: https://rpms.svc.ci.openshift.org You can get an rpm repo file for a release by clicking on one of the links on

PSA for openshift users - dockerhub will be down for scheduled outage on August 25th

2018-08-16 Thread Clayton Coleman
Please see https://status.docker.com/ for times. Remember, if you have autoscaling nodes that need to pull new apps, or have pods that run with PullAlways, or push builds to the docker hub, while the hub is down those operations will fail. Mitigations could include: 1. Disable autoscaling for

Re: Removed "openshift start node" from origin master

2018-08-14 Thread Clayton Coleman
at we have today? On Tue, Aug 14, 2018 at 6:17 PM, Clayton Coleman wrote: > As part of the continuation of splitting OpenShift up to make it be able > to run on top of kubernetes, we just merged https://github.com/ > openshift/origin/pull/20344 which removes "openshift start no

Removed "openshift start node" from origin master

2018-08-14 Thread Clayton Coleman
As part of the continuation of splitting OpenShift up to make it be able to run on top of kubernetes, we just merged https://github.com/openshift/origin/pull/20344 which removes "openshift start node" and the "openshift start" commands. This means that the openshift binary will no longer include

Re: Kubelet/node nice level

2018-07-01 Thread Clayton Coleman
That’s the one the installer lays down. Ansible has never used the one in the RPMs (and the one in the RPMs is being removed in 3.10 to prevent confusion). On Jul 1, 2018, at 10:03 AM, Mateus Caruccio wrote: Yep, I copy/paste from an old buffer. It's /bin/nice already. Same results. Anyway, I

Re: Kubelet/node nice level

2018-06-30 Thread Clayton Coleman
/ Master of Puppets GetupCloud.com We make the infrastructure invisible Gartner Cool Vendor 2017 2018-06-30 15:03 GMT-03:00 Clayton Coleman : > Which version of openshift and what are your node start settings? > > On Jun 29, 2018, at 11:10 PM, Mateus Caruccio com> wrote: > > H

OpenShift v3.10.0-rc.0 has been published

2018-06-20 Thread Clayton Coleman
Clients and binaries have been pushed to GitHub https://github.com/openshift/origin/releases/tag/v3.10.0-rc.0 and images are available on the DockerHub. ___ dev mailing list dev@lists.openshift.redhat.com

Re: Openshift and Power loss

2018-06-20 Thread Clayton Coleman
On Jun 20, 2018, at 7:32 AM, Hetz Ben Hamo wrote: With all redundant hardware these days, with UPS - power loss can happen. I just got a power loss and upon powering on those machines, most of the services weren't working. Checking the pods shows almost all of them in error state. I deleted the

Re: Origin 3.10 release

2018-06-12 Thread Clayton Coleman
You should be using the current rolling tag. We're not yet ready to cut an rc candidate. Please see my previous email to the list about accessing the latest RPMs or zips for the project. On Tue, Jun 12, 2018 at 8:10 AM, Lalatendu Mohanty wrote: > Hi, > > We are working on code changes

Re: OpenShift Web Console - 3.9 - Pod / CrashLoopBackOff

2018-05-17 Thread Clayton Coleman
anyuid is less restrictive than restricted, unless you customized restricted. Did youvustomize restricted? On May 17, 2018, at 8:56 AM, Charles Moulliard wrote: Hi, If we scale down/up the Replication Set of the OpenShift Web Console, then the new pod created will crash

Re: OpenShift Origin incorporating CoreOS technologies ?

2018-05-16 Thread Clayton Coleman
Many if not most of the features will be in Origin. Probably the one exception is over the air cluster updates - the pieces of that will be open, but the mechanism for Origin updates may be more similar to the existing setup today than to what tectonic has. We’re still sorting out how that will

Re: How to build RPMs

2018-05-04 Thread Clayton Coleman
It looks like it is trying to push tags, maybe that is failing. You may need to add -x to hack/build-rpms.sh On May 4, 2018, at 10:30 AM, Mateus Caruccio wrote: Hi there. I'm having a hard time trying to build RPMs for 3.7.x What am I missing here? Thanks.

Changes to origin and OCP images in 3.10

2018-05-02 Thread Clayton Coleman
https://github.com/openshift/origin/pull/19509 has been merged and does two things: First, and most important, it puts our images and binaries on a diet: 1. oc is now 110M instead of 220M 2. most origin images were 1.26GB uncompressed (300 or so on the wire) are now half that size (150 on the

Images renamed in origin

2018-04-18 Thread Clayton Coleman
The following images are being renamed in 3.10: openshift/origin -> openshift/origin-control-plane openshift/node -> openshift/origin-node The following images are being removed: openshift/openvswitch: the RPMs and content here is now part of openshift/origin-node The following images won't be

Re: Annotation NodeSelector is missing

2018-04-12 Thread Clayton Coleman
And note that we don’t automatically set that label on single node installs because we are moving to more of an AMI / autoscaing model in the future, where we may configure a control plane by nodes dynamically join as they boot. Setting a compute label via inventory will be required for this

Re: Install OpenShift Origin 3.9 failed on single node

2018-04-10 Thread Clayton Coleman
You can try rerunning the install with -vv to get additional debug information. What OS and version on Ansible are you using? On Apr 10, 2018, at 3:24 AM, Yu Wei wrote: Hi, I tried to install openshift origin 3.9 on a single machine and encountered problems as below,

Re: OpenShift Origin v3.9.0 is now available

2018-04-01 Thread Clayton Coleman
|cut -d= -f2) > > encoding='UTF-8'?>NoSuchKeyThe specified > key does not exist.No such object: > origin-ci-test/logs/test_branch_origin_extended_conformance_gce_39/23/ > artifacts/rpms > ``` > > Regards > Aleks > Am 31.03.2018 um 01:33 schrieb Clayton Coleman: > &

OpenShift Origin v3.9.0 is now available

2018-03-30 Thread Clayton Coleman
The v3.9.0 OpenShift release has been tagged https://github.com/openshift/origin/releases/tag/v3.9.0 and images have been pushed to the Docker Hub. RPMs are available at: https://storage.googleapis.com/origin-ci-test/releases/openshift/origin/v3.9.0/origin.repo Starting in v3.9.0, the Origin

Re: [CentOS-devel] CentOS PaaS SIG meeting (2018-03-21)

2018-03-27 Thread Clayton Coleman
sers-boun...@lists.openshift.redhat.com>] *On Behalf Of *Clayton Coleman *Sent:* Tuesday, March 27, 2018 3:44 PM *To:* Troy Dawson <tdaw...@redhat.com> *Cc:* users <us...@redhat.com>; The CentOS developers mailing list. < centos-de...@centos.org>; dev <dev@lists.openshift.redhat.

Re: [CentOS-devel] CentOS PaaS SIG meeting (2018-03-21)

2018-03-27 Thread Clayton Coleman
Still waiting for a last couple of regressions to be fixed. Sorry everyone, I know you're excited about this. On Tue, Mar 27, 2018 at 6:04 PM, Troy Dawson wrote: > I didn't see anything saying that 3.9 was released yet. Last I heard > they were working on some regressions.

Re: Stop docker processes created by "oc cluster up"

2018-03-26 Thread Clayton Coleman
oc cluster down? On Mon, Mar 26, 2018 at 12:58 PM, Charles Moulliard wrote: > Hi, > > When we use "oc cluster up" command, then openshift is started as docker > containers (origin, router, registry + console) that we could stop/start > using command "docker stop|start

Re: Configuring Private DNS Zones and Upstream Nameservers in Openshift

2018-02-22 Thread Clayton Coleman
Probably have to wait until 3.9. We also want to move to coredns, but that could take longer. On Feb 15, 2018, at 6:26 PM, Srinivas Naga Kotaru (skotaru) < skot...@cisco.com> wrote: Is it possible like described in kubernetes?

Re: Leader election in Kubernetes control plane

2018-02-20 Thread Clayton Coleman
u (skotaru)" <skot...@cisco.com> wrote: >> >> It has just client-ca-file. We have 3 masters in each cluster. not sure how >> to identify which control manager is active? I usually find which oneʼs is >> writing logs by using journalctl >> atomic-openshift-m

Re: Leader election in Kubernetes control plane

2018-02-20 Thread Clayton Coleman
We use config maps - check in kube-system for that. On Feb 15, 2018, at 2:48 PM, Srinivas Naga Kotaru (skotaru) < skot...@cisco.com> wrote: while I was reading below article, I tried to do the same to find out which one is active control plane in Openshift. I could see zero end points in

New rolling pre-release tags for Origin v3.9

2018-02-01 Thread Clayton Coleman
Due to much popular demand and a desire to use this for rolling updates of cluster components, we have started publishing vX.Y and vX.Y.Z tags for origin, the registry, and logging and metrics. So by end of day tomorrow you should see v3.9 and v3.9.0 tags for all OpenShift components. These tags

Development nightly / PR artifacts

2018-01-29 Thread Clayton Coleman
We recently updated the tracking artifacts for releases - for any tag, branch, or PR that is built you can get at the RPMs For branches and tags, this URL gives you the link to the latest RPMs (the content of this file is a URL you can use in an RPM repo) curl -q "

Re: cbs-paas7-openshift-multiarch-el7-build

2018-01-23 Thread Clayton Coleman
Jason is probably the best contact for this On Mon, Jan 22, 2018 at 11:17 AM, Neale Ferguson wrote: > Hi, > I have been building CE for the s390x platform and notice in the recent > release there is a new repo used in the source image. At the moment most of > the packages

Re: service discovery if node service down

2018-01-18 Thread Clayton Coleman
It could be configured that way. You should be able to statically test that with the on disk config for dnsmasq to see if it works as expected (you'll want the node ip first) On Thu, Jan 18, 2018 at 11:55 AM, Srinivas Naga Kotaru (skotaru) < skot...@cisco.com> wrote: > Will service discovery

Re: Problem with tito when building RPMs

2018-01-18 Thread Clayton Coleman
Have you pulled tags into you git repo? On Jan 18, 2018, at 5:44 PM, Neale Ferguson wrote: I saw a similar problem reported in October last year but there was no report of a resolution. I have done a build since then and it worked but today when I went to build 3.7.1 I got

OpenShift v3.7.1 released

2018-01-16 Thread Clayton Coleman
This is patch release containing some high severity issues v3.7.1 Images have been pushed to the docker hub. RPMs will likely trail by a few days. ___ dev mailing list

Re: origin v3.7.0 images at docker.io

2017-12-19 Thread Clayton Coleman
ucture invisible Gartner Cool Vendor 2017 2017-11-21 16:54 GMT-02:00 Clayton Coleman <ccole...@redhat.com>: > We haven't cut 3.7.0 yet in origin. Still waiting for final soak > determination - there are a few outstanding issues being chased. I'd urge > everyone who wants 3.7.0 to verify

Re: Several questions about authorization

2017-12-18 Thread Clayton Coleman
On Mon, Dec 18, 2017 at 5:17 AM, Yu Wei wrote: > Hi, > > I have several questions about user and authorization management. > > 1, How could I remove user from project? > > > > > > > > > > > > > > > *[root@host-10-1-236-92 gpu-test]# oc login -u test1 -p test1 Login >

Re: [aos-devel] optimizing go guru

2017-12-05 Thread Clayton Coleman
Openshift and Kubernetes are massive go projects - over 3 million lines of code (last I checked). Initial compile can take a few minutes for these tools. Things to check: 1. Go 1.9 uses less memory when compiling 2. Be sure you are reusing your go compiled artifacts dir between multiple tools

Re: Webhook token auth

2017-12-01 Thread Clayton Coleman
At the current time authenticator web hooks aren't supported (3.6). It's being discussed for 3.9, but more realistically 3.10. This is for IAM integration with AWS? On Fri, Dec 1, 2017 at 3:48 PM, Mateus Caruccio < mateus.caruc...@getupcloud.com> wrote: > Hi. > Is it possible to use external

release-3.8 branch created, v3.8.0-alpha.1 and v3.9.0-alpha.0 tags created

2017-12-01 Thread Clayton Coleman
We've branched master for release-3.8 and created a v3.9.0-alpha.0 tag. This is because 3.8 is a "skip" release where we'll only do an internal data upgrade and then go from 3.7 to 3.9 directly. Expect the next Kubernetes rebase for 1.9 to begin soon. Commits to master are still allowed.

Re: Unpredictable oc binary path for Origin version v3.7.0

2017-11-30 Thread Clayton Coleman
Binaries are published. On Nov 30, 2017, at 10:11 AM, Clayton Coleman <ccole...@redhat.com> wrote: I can publish them to github for 3.7. We’re looking to reduce the amount of effort required to publish binaries so we can do it more often. Expect binaries to be published to GCS in the

Re: Unpredictable oc binary path for Origin version v3.7.0

2017-11-30 Thread Clayton Coleman
track tagged releases. It would be pretty convenient for scripting. not to have to employ logic to figure out latest build ids or release hashes. -- MAREK JELEN DEVELOPER ADVOCATE, OPENSHIFT https://www.redhat.com/ mje...@redhat.comM: +420724255807 On 30 November 2017 at 16:13:08, C

Re: Unpredictable oc binary path for Origin version v3.7.0

2017-11-30 Thread Clayton Coleman
I can publish them to github for 3.7. We’re looking to reduce the amount of effort required to publish binaries so we can do it more often. Expect binaries to be published to GCS in the future. On Nov 30, 2017, at 2:05 AM, Lalatendu Mohanty wrote: Hi, Till v3.7.0-rc.0

Re: registry deletion

2017-11-28 Thread Clayton Coleman
Note that any command that can generate objects can be an input to delete: oadm registry -o json | oc delete -f - It won’t delete objects you personally created, but is a good way to rewind. On Nov 28, 2017, at 6:13 PM, Ben Parees wrote: On Tue, Nov 28, 2017 at 6:06 PM,

Re: origin v3.7.0 images at docker.io

2017-11-21 Thread Clayton Coleman
We haven't cut 3.7.0 yet in origin. Still waiting for final soak determination - there are a few outstanding issues being chased. I'd urge everyone who wants 3.7.0 to verify that 3.7.0.rc0 works for them. On Tue, Nov 21, 2017 at 1:40 PM, Jason Brooks wrote: > Can we get

Re: question about openshift origin deployer

2017-11-19 Thread Clayton Coleman
The deploy command is a sub command in the openshift binary (openshift infra deploy —help) and makes api calls back to openshift to launch the pod. The deployment service account is used by the pod and is granted the permission to launch hook pods and also to scale the replica set for each

Re: v3.6.1 and v3.7.0-rc.0 released

2017-10-27 Thread Clayton Coleman
v3.6.0 images were carried forward, :latest was used for v3.7.0-rc.0 On Fri, Oct 27, 2017 at 7:15 PM, Rich Megginson <rmegg...@redhat.com> wrote: > What about logging and metrics? > > On 10/27/2017 11:09 AM, Clayton Coleman wrote: > >> v3.6.1 and v3.7.0-rc.0 have

v3.6.1 and v3.7.0-rc.0 released

2017-10-27 Thread Clayton Coleman
v3.6.1 and v3.7.0-rc.0 have been released on GitHub and the Docker Hub: https://github.com/openshift/origin/releases/tag/v3.7.0-rc.0 https://github.com/openshift/origin/releases/tag/v3.6.1 Thanks to everyone for their hard work so far! ___ dev mailing

Re: PTR record for POD

2017-10-05 Thread Clayton Coleman
No, we only report pod IPs via PTR records if they are part of a stateful set and you have set the serviceName field on the set. On Thu, Oct 5, 2017 at 6:35 PM, Srinivas Naga Kotaru (skotaru) < skot...@cisco.com> wrote: > HI > > > > Is it possible to get POD name given POD IP address by querying

Re: Scale up / down based on user traffic

2017-09-13 Thread Clayton Coleman
Custom metrics autoscaling is coming soon. It will be based on prometheus metrics exposed by your app. On Sep 13, 2017, at 7:33 AM, Josef Karasek wrote: At Promcon [0] I talked with a guy who exposes some metrics (https connections, sql queries) in the prometheus format

Re: Pods Not Terminating

2017-09-05 Thread Clayton Coleman
still stuck. > > > On Sep 5, 2017, at 2:13 PM, Clayton Coleman <ccole...@redhat.com> wrote: > > So the errors recur continuously for a given pod once they start happening? > > On Tue, Sep 5, 2017 at 5:07 PM, Patrick Tescher <patr...@outtherelabs.com> > wrote: >

Re: Pods Not Terminating

2017-09-05 Thread Clayton Coleman
fferent pods in different namespaces. > The only thing we did today was launch a stateful set in a new namespace. > Those pods were not the ones throwing this error. > > > On Sep 5, 2017, at 1:19 PM, Clayton Coleman <ccole...@redhat.com> wrote: > > Were any patches applied t

Re: Pods Not Terminating

2017-09-05 Thread Clayton Coleman
Were any patches applied to the system? Some of these are normal if they happen for a brief period of time. Are you seeing these errors continuously for the same pod over and over? On Tue, Sep 5, 2017 at 3:23 PM, Patrick Tescher wrote: > This morning our cluster

OpenShift Origin v3.7.0-alpha.1 released

2017-08-30 Thread Clayton Coleman
Release notes are up on GitHub v3.7.0-alpha.1 and the new images have been pushed. Of major note - in 3.7 OpenShift RBAC will shift to being a layer on top of Kubernetes RBAC (preserving your existing roles). Existing APIs will

Re: Is that possible to deploy openshift on existing k8s cluster?

2017-08-22 Thread Clayton Coleman
g that may be possible in the future) so that future versions of OpenShift may run directly on top of a Kube version. Today I would say it's probably very difficult and not recommended without a lot of expertise in both the OpenShift and Kube codebases. > > > > > Rgds, > Sanjeev >

Re: Is that possible to deploy openshift on existing k8s cluster?

2017-08-22 Thread Clayton Coleman
Not today. We hope to do so at some point in the future, but today openshift requires additional compiled in control points that only work when installing origin directly from the binaries we build. On Aug 22, 2017, at 6:36 AM, Yu Wei wrote: Hi, Now we have existing k8s

Re: [API Model] Query for DeploymentConfigStatus property in the DeploymentConfigs model

2017-08-22 Thread Clayton Coleman
It's not, we just need to mark it optional. Like other Kubernetes status fields, it is always ignored during POST and PUT, and only editable via the /status subresource as an admin. On Aug 22, 2017, at 8:46 AM, Hrishikesh Shinde wrote: Hello, As per specification[1]

Re: Changes in imagestream does not trigger build

2017-08-10 Thread Clayton Coleman
Is this an upgrade of a cluster, or a brand new cluster? If it's an upgrade, did you run cluster role reconcile after updating your cluster? On Thu, Aug 10, 2017 at 12:48 PM, Bamacharan Kundu wrote: > Hi, > I am having one build chain with openshift/origin:v3.6.0. where >

Re: Seeking Advice On Exporting Image Streams

2017-08-09 Thread Clayton Coleman
lly implementing image references, but the idea is to allow parameterizing other things such as environment variables, names, etc. This is orthogonal to transforming the resources for export which ‘GET’ with the export parameter needs to handle. On Aug 9, 2017, at 1:20 PM, Clayton Coleman <ccole..

Re: Seeking Advice On Exporting Image Streams

2017-08-09 Thread Clayton Coleman
Why do we need parameters? Which parameters are we adding? On Aug 9, 2017, at 12:21 PM, Cesar Wong wrote: Hi Devan, You can see my branch here: https://github.com/csrwng/origin/tree/parameterize_template (last 5 commits) Hopefully should be a PR soon. The REST endpoint

Re: OpenShift Origin v3.6.0 is released

2017-07-31 Thread Clayton Coleman
Yes, that'll probably have to be a point change. On Mon, Jul 31, 2017 at 11:02 PM, Andrew Lau <and...@andrewklau.com> wrote: > I think the node images are still missing the sdn-ovs package. > > On Tue, 1 Aug 2017 at 07:45 Clayton Coleman <ccole...@redhat.com> wrote: >

Re: OpenShift Origin v3.6.0 is released

2017-07-31 Thread Clayton Coleman
This has been fixed and images were repushed. On Mon, Jul 31, 2017 at 12:13 PM, Clayton Coleman <ccole...@redhat.com> wrote: > Hrm, so they do. Looking. > > On Mon, Jul 31, 2017 at 11:57 AM, Andrew Lau <and...@andrewklau.com> > wrote: > >> The images st

  1   2   3   >