[Starlingx-discuss] Limit memory usage on Virtual Environment

[Curtis]

On Wed, May 8, 2019 at 11:33 AM Lemus Contreras, Cristopher J <
cristopher.j.lemus.contreras at intel.com> wrote:

> Hello,
>
>
>
> During today’s Community meeting, memory usage on virtual environments was
> discussed. In summary, the memory requirements for each VM has increased
> significantly (see bug: https://bugs.launchpad.net/bugs/1826445 ).
>
>
>

I think it's important that we as a project try to keep memory resources as
low as reasonably possible. I've seen this happen in other OpenStack
projects where they find that their memory usage is increasing and they go
and look and find some low hanging fruit where they can reduce
requirements. I think we definitely need to take a look and see where we
can reduce some memory usage.

IHMO, we also need need to make sure it's possible to do a PoC with low
requirements. I find that during workshops etc that memory requirements are
quite high. We need to document a virtual PoC All-in-one which is quite a
bit smaller than prod environments. The place for this to happen may be
starlingx-in-a-box but I haven't been able to look at that code yet.

Finally, I would expect to find people wanting to use stx in small ucpe
style systems where memory could be hardware with less than 16gb. Certainly
we could decide not to support that, but we shouldn't be surprised to see
some people suggest that use case. :)

Thanks,
Curtis




> An alternative was mentioned, during the deployment it’s possible to limit
> the amount of memory that starlingx is going to use. Does somebody has the
> instructions to implement such limits? It’ll help us a lot to continue
> working with Virtual Environments.
>
>
>
> Thanks in advance.
>
>
>
> Cristopher Lemus
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
>


-- 
Blog: serverascode.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190508/ab25ee24/attachment-0001.html>