Re: Is there a way to specify a node selector to limit nodes evaluated by the cluster capacity analysis tool?

2017-12-13 Thread Avesh Agarwal
Specify node selector for your worker nodes in the input pod spec. On Thu, Dec 7, 2017 at 2:41 PM, Cottrell, Ken wrote: > We are testing origin 3.6 cluster capacity analysis tool, currently > running in a pod as a cronjob. We have 3 worker nodes and 3 infra nodes in >

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

2017-08-12 Thread Avesh Agarwal
On Sat, Aug 12, 2017 at 11:59 AM, Avesh Agarwal <avaga...@redhat.com> wrote: > > > On Fri, Aug 11, 2017 at 2:28 AM, Per Carlson <pe...@hemmop.com> wrote: > >> Hi. >> >> We are in the process of rebuilding a cluster with a new topology, and >>

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

2017-08-12 Thread Avesh Agarwal
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 node labels to a scheduler policy, and would like to base > the policy on the default one. > > I've searched both the

Re: Method to move a single or multiple pods to a different node?

2017-07-08 Thread Avesh Agarwal
On Sat, Jul 8, 2017 at 3:45 PM, G. Jones wrote: > I’ve got an Origin 1.5 environment where, during an outage with my nodes, > pods got relocated to my masters fairly randomly. I need to clean it up and > get the pods back where I want them but have not yet found a way

Re: users Digest, Vol 58, Issue 5 -

2017-05-04 Thread Avesh Agarwal
On Thu, May 4, 2017 at 10:50 AM, Walters, Todd <todd_walt...@unigroup.com> wrote: > > >2. Pod Deployment with Memory Request and Limits (Bar?? Ayd?n?z) >3. Re: Pod Deployment with Memory Request and Lim

Re: Pod Deployment with Memory Request and Limits

2017-05-04 Thread Avesh Agarwal
On Thu, May 4, 2017 at 3:55 AM, Barış Aydınöz wrote: > Hi, > > Suppose we have 100 GB available on a node [only node that is scheduled] > > And we want to assure deployment of *at most 10 Pods* all of them java > applications and we limit max heap size as *2 GB*, with below

Re: Error: valueFrom fieldRef resource => ...env[5].valueFrom.fieldRef.fieldPath: Required value

2016-11-08 Thread Avesh Agarwal
nshift or origin version you are using? Thanks Avesh > > 2016-11-08 16:14 GMT+01:00 Stéphane Klein <cont...@stephane-klein.info>: > >> https://gist.github.com/harobed/fc24a7766dbcf2d9e61f42dd8a968a6c >> >> 2016-11-08 16:03 GMT+01:00 Avesh Agarwal <avaga...@redhat

Re: Error: valueFrom fieldRef resource => ...env[5].valueFrom.fieldRef.fieldPath: Required value

2016-11-08 Thread Avesh Agarwal
On Tue, Nov 8, 2016 at 8:50 AM, Stéphane Klein <cont...@stephane-klein.info> wrote: > > > 2016-11-08 13:43 GMT+01:00 Avesh Agarwal <avaga...@redhat.com>: > >> >> >> On Tue, Nov 8, 2016 at 5:44 AM, Stéphane Klein < >> cont...@

Re: Error: valueFrom fieldRef resource => ...env[5].valueFrom.fieldRef.fieldPath: Required value

2016-11-08 Thread Avesh Agarwal
On Tue, Nov 8, 2016 at 5:44 AM, Stéphane Klein wrote: > Hi, > > I've this ReplicationController: > > apiVersion: v1 > kind: List > metadata: {} > items: > - apiVersion: v1 > kind: ReplicationController > metadata: > labels: > metrics-infra:

Fwd: default node selectors

2016-11-07 Thread Avesh Agarwal
Forwarding as just subscribed to this list: -- Forwarded message -- From: Avesh Agarwal <avaga...@redhat.com> Date: Mon, Nov 7, 2016 at 12:29 PM Subject: Re: default node selectors To: Clayton Coleman <ccole...@redhat.com> Cc: Andrew Lau <and...@andrewkl