Victor, See inline Brent -----Original Message----- From: Victor Rodriguez [mailto:vm.rod25@gmail.com] Sent: Monday, April 29, 2019 9:43 AM To: Miller, Frank <Frank.Miller@windriver.com> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Agenda: Weekly Containerization Meeting Monday April 29 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. [BR] Enabling SWAP in general is not an option for performance reasons. On top of that it will not work with k8s. Regards Victor R On Mon, Apr 29, 2019 at 8:34 AM Miller, Frank <Frank.Miller@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@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss