[Starlingx-discuss] Agenda: Weekly Containerization Meeting Monday April 29

Victor Rodriguez vm.rod25 at gmail.com
Tue Apr 30 19:42:15 UTC 2019


Thanks, Bin


On Mon, Apr 29, 2019 at 8:33 PM Yang, Bin <bin.yang at intel.com> wrote:
>
> Hi Victor,
>
>         K8s always not works with "swap enabled". Refer to: https://github.com/ku
> bernetes/kubernetes/issues/53533
>
This is a clear answer to my question with a good thread where I got good points

>         As "Angus Lees" mentioned, "Applications should configure limits.memory
> with the max ram they ever want to use, and requests.memory with their intended
> working set (including kernel buffers, etc)"
>
Agree ,

Doing a search with Cristopher we found that 2GB might be a good limit

>         I think it needs to assign enough memory for STX critical containers to
> keep system being stable. Please correct me if wrong.

My question, as not expert in docker, is if the option

docker run -m, --memory bytes                   Memory limit

could be a good solution to limit the memory bound

Regards

>
> thanks,
> Bin
>
>
> On Mon, 2019-04-29 at 08:42 -0500, Victor Rodriguez wrote:
> > Hi Frank
> >
> > I am in charge of the track of performance and footprint of the STX systems
> >
> > Due to the fact that this bug was a footprint issue I was wondering if
> > should discuss on the meeting on what stages and part of the STX do
> > you want me to track the memory footprint
> >
> > Also, I have a question regarding the chance to set up -m to each
> > docker image so we can limit the amount of memory of each one. One of
> > the experiments we did las Friday debugging the issue was that if we
> > set -m and the system has SWAP it will take memory from there and keep
> > running since we in STX do not have swap the containers fails from
> > starvation.
> >
> > Regards
> >
> > Victor R
> >
> > On Mon, Apr 29, 2019 at 8:34 AM Miller, Frank
> > <Frank.Miller at windriver.com> wrote:
> > >
> > >
> > > We will be holding a meeting today.  Planned agenda is below – please add to
> > > the etherpad agenda if you have any additional topics to discuss:
> > >
> > >
> > >
> > > Etherpad: https://etherpad.openstack.org/p/stx-containerization
> > >
> > >
> > >
> > > Agenda:
> > >
> > > 1. Sanity status/issue discussion:
> > >
> > >     - All in one systems, bare metal
> > >
> > >     - Multi node systems
> > >
> > >     - Virtual systems
> > >
> > >
> > >
> > > 2. Test team status & top issues
> > >
> > >
> > >
> > > 3. Feature Topics:
> > >
> > >     - Overall status
> > >
> > >     - Technical discussion on any outstanding features
> > >
> > >
> > >
> > > 4. Open topics
> > >
> > >     - no meeting Monday May 6th
> > >
> > >     - other items?
> > >
> > >
> > >
> > >
> > >
> > > ------
> > >
> > > Frank
> > >
> > >
> > >
> > > _______________________________________________
> > > Starlingx-discuss mailing list
> > > Starlingx-discuss at lists.starlingx.io
> > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
> > _______________________________________________
> > Starlingx-discuss mailing list
> > Starlingx-discuss at lists.starlingx.io
> > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss



More information about the Starlingx-discuss mailing list