Re: Containerized OCP requires atomic-openshift?

The set_version_rpm task in the openshift_version role has the check for the atomic-openshift package. This is fine and is being skipped in my containerised installation. But the same check was added to the main task of the role as part of the 3.6 release (it's not there in the 1.5 branch). Looks

Re: Containerized OCP requires atomic-openshift?

Hi Lionel, I think that package is still used as a comparison in containerized deployments, so if the channel subscriptions aren't sufficient on the systems you're deploying to, it won't be able to get the information back about it. -Chris On 21 October 2017 at 11:59, Lionel Orellana

Re: Containerized OCP requires atomic-openshift?

Thanks Chris. I have those 3 properties (although it looks like deployment_type is now openshift_deployment_type? either way it's not working). Fair enough if it wants to install the excluders but why the atomic-openshift package? On 21 October 2017 at 21:48, Chris Ganderton

Re: Containerized OCP requires atomic-openshift?

> > From: users-boun...@lists.openshift.redhat.com > on behalf of Lionel Orellana > > Sent: Saturday, October 21, 2017 11:14 AM > To: users > Subject: Containerized OCP requires atomic-openshift? > > Hi, > > I'm trying to install

Containerized OCP requires atomic-openshift?

Hi, I'm trying to install OCP 3.6. I've done a few installations of Origin before but it's my first OCP. I'm installing on RHEL and have set containerized=true in the inventory. The byo playbook for some reason insists on requiring atomic-openshift to be installed. Failure summary: 1.

Re: Q: Refer to runtime properties from within "templates"?

Object Definition Files, I can live with that one :) And I agree it's very useful to be able to put the whole "Application Lifecycle Landscape", as you call it, inside one of them. But... the issue we're encountering is with the "full parameterization" part. It's okay if every single property

Re: OpenShift master keeps consuming lots and memory and swapping

No one with 2 nodes and 11 namespaces needs 20GB. Up to a few hundred pods and ten nodes the openshift processes themselves shouldn't be using more than a few hundred megs. If you plan on growing or haven't upgraded to etcd3 you obviously want to leave some wiggle room, but even very large