Re: Default cluster administrator user in a multi-node cluster

Thanks Aleks. Maybe this is obvious, but somehow I missed this detail. On Mon, Aug 14, 2017 at 3:28 PM, Aleksandar Lazic wrote: > Hi Isuru. > > when you on the master and root user you are by default system:admin, > afaik. > > You will need to add a user and give them the cluster-admin privilege

Re: Better understanding of limits and quotas

That might be the resources you set for the deployed application pod, but the _builder_ pod, the one with the "-build" suffix, is BestEffort. On Mon, Aug 14, 2017 at 10:39 AM, Thorvald Hallvardsson wrote: > Hi Derek, > > Thank you for your reply. > > But as I mentioned in my first post I requeste

Re: Better understanding of limits and quotas

Title: Re: Better understanding of limits and quotas Hi Thorvald. I found this blog very helpfully. https://blog.openshift.com/full-cluster-capacity-management-monitoring-openshift/ What's the output of oc describe oc get ev It's also one of the trickiest part of oc & kube for me. Regards

Re: Better understanding of limits and quotas

Hi Derek, Thank you for your reply. But as I mentioned in my first post I requested following: request.cpu: 1 limits.cpu: 2 request:mem: 256Mi limit.mem: 512Mi So it wasn't a pod without any resource request. There was an request but it just didn't work or I don't understand the entire concept.

Re: Better understanding of limits and quotas

If you create a pod with no resource requests, the pod has BestEffort QoS. This means it has no resource guarantees, and will get variable performance based on what else is happening on the machine running your pod. For your scenario, it appears you are trying to run builds as "BestEffort" workloa

Re: Scheduler policy in 3.6 (default and custom at install time)

On Mon, Aug 14, 2017 at 3:20 AM, Per Carlson wrote: > Hi. > > On 12 August 2017 at 18:39, Avesh Agarwal wrote: > >> >> >> On Sat, Aug 12, 2017 at 11:59 AM, Avesh Agarwal >> wrote: >> >>> >>> >>> On Fri, Aug 11, 2017 at 2:28 AM, Per Carlson wrote: >>> Hi. We are in the process of

Re: Docker Thin Pool Space

Thanks On Mon, Aug 14, 2017 at 2:20 PM, Aleksandar Lazic wrote: > Hi David. > > Yes. > > on Montag, 14. August 2017 at 15:05 was written: > > > Thanks Aleksandar, > > Do you just have that cron'd on each node? > > On Mon, Aug 14, 2017 at 1:24 PM, Aleksandar Lazic > wrote: > > Hi David. > > on M

Re: Docker Thin Pool Space

Title: Re: Docker Thin Pool Space Hi David. Yes. on Montag, 14. August 2017 at 15:05 was written: Thanks Aleksandar, Do you just have that cron'd on each node? On Mon, Aug 14, 2017 at 1:24 PM, Aleksandar Lazic wrote: Hi David. on Montag, 14. August 2017 at 13:4

Re: Docker Thin Pool Space

Thanks Aleksandar, Do you just have that cron'd on each node? On Mon, Aug 14, 2017 at 1:24 PM, Aleksandar Lazic wrote: > Hi David. > > on Montag, 14. August 2017 at 13:46 was written: > > > I keep getting the below error on my app nodes. Running Origin v1.4.1 > > on AWS installed using the refe

Re: Docker Thin Pool Space

Hi David. on Montag, 14. August 2017 at 13:46 was written: > I keep getting the below error on my app nodes. Running Origin v1.4.1 > on AWS installed using the reference architecture. Am I missing > something which should be cleaning up? You should cleanup the local docker storage on regular bas

Docker Thin Pool Space

I keep getting the below error on my app nodes. Running Origin v1.4.1 on AWS installed using the reference architecture. Am I missing something which should be cleaning up? Error syncing pod, skipping: failed to "StartContainer" for "jnlp" with ErrImagePull: "failed to register layer: devmapper: T

Re: Default cluster administrator user in a multi-node cluster

Title: Re: Default cluster administrator user in a multi-node cluster Hi Isuru. when you on the master and root user you are by default system:admin, afaik. You will need to add a user and give them the cluster-admin privileges to work from remote or as normal user. https://docs.openshift.org/

Better understanding of limits and quotas

Hi, I'm trying to play a bit with limits and quotas and generally I don't understand anything. I'm trying to build a test application and I get an error: Failed to create build pod: pods "wordpress-1-build" is forbidden: failed quota: compute-resources: must specify limits.cpu,limits.memory,reque

Default cluster administrator user in a multi-node cluster

Hi all, Followed [1] to create a multi node setup with a single master and three nodes using the ansible installer. After the all nodes started successfully, tried to use the CLI tool against the Openshift cluster, similar to how I used it in the local minishift environment, to login as the defaul

Re: Scheduler policy in 3.6 (default and custom at install time)

Hi. On 12 August 2017 at 18:39, Avesh Agarwal wrote: > > > On Sat, Aug 12, 2017 at 11:59 AM, Avesh Agarwal > wrote: > >> >> >> On Fri, Aug 11, 2017 at 2:28 AM, Per Carlson wrote: >> >>> Hi. >>> >>> We are in the process of rebuilding a cluster with a new topology, and >>> I'm trying to fit the