On Wed, Aug 10, 2016 at 2:41 PM, Srinivas Naga Kotaru (skotaru) < skot...@cisco.com> wrote:
> > > > -- > *Srinivas Kotaru* > > From: "ccole...@redhat.com" <ccole...@redhat.com> > Date: Wednesday, August 10, 2016 at 11:33 AM > To: skotaru <skot...@cisco.com> > Cc: dev <dev@lists.openshift.redhat.com> > Subject: Re: few questions on quotas and limits > > > > On Wed, Aug 10, 2016 at 2:26 PM, Srinivas Naga Kotaru (skotaru) < > skot...@cisco.com> wrote: > >> Need some clarity on quotas and limits >> >> As a platform team, we want control quotas on cpu and memory and put >> upper bounds and same time provide more flexibility to app team to control >> or decide what is limits for their apps. >> >> Our clients come to our own UI and ask for project. They don’t’ have >> right to create projects. We disabled it. Our robot account will create >> project, setup initial project admin, and appropriate roles ( edit, view, >> admins etc) >> >> One activity we want to control from UI is set quotas and put limits. >> Robot account will be used to create quota and limit range on every >> project. These numbers different project to project depending on client >> type or apps types. We want to optimize better density + best QOS so both >> infra and apps will be happier in terms of better utilization of resources. >> >> Documentation is good but not answering real time scenarios or examples >> unless you understood big picture. >> >> Questions: >> >> >> 1. What if we just define per project quota but don’t create limitrange? >> Can client control request and limits by himself at pod level subject to >> with in the upper controls of cpu/memory? >> > > Yes. > > >> Thx for clarification > > >> >> 2. What if if we create both quota and limit range with defaults values >> for better density ( scheduler to place pods with decent default request) >> but later client to control both request and limits subject to quota >> limitations. Can they able to do or limitrange defaults always take >> precedence? >> >> default: >> cpu: “500m" >> memory: “1Gi" >> defaultRequest: >> cpu: “300m" >> memory: “512Mi” >> > > If you specify your own default, it overrides. > > >> can you bit elaborate it? Above example is from limitrange not pod > definition. Can client override limitrange defaults set by initial project > creation and set his own? Subject to accumulated usage with in quota > cpu/memory limits? > limit range defaults are always "only if the user doesn't set it". So clients override it by setting the limit and request fields on the containers. > >> 3. Any decent documentation which explain real use cases rather high >> level which is available from project docs. ( I think it is cut and paste >> from official Kubernetes docs) >> > > > There is Dan's latest blog but may not be quite at your use case level: > Managing > Compute Resources with OpenShift/Kubernetes > <https://blog.openshift.com/managing-compute-resources-openshiftkubernetes/> > > >>I read his blog but not as elaborative as am looking but it is excellent > story, keep writing > Derek, are you aware of anything along these lines? > > > >> >> >> -- >> *Srinivas Kotaru* >> >> _______________________________________________ >> dev mailing list >> dev@lists.openshift.redhat.com >> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >> >> >
_______________________________________________ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
