Re: VRs swapping with 256 MB RAM

[Rohit Yadav]

Hi Rene,


I've come across issues where vmware side would provision less than 256MB RAM 
to the guest OS while vCenter would still claim to have reserved/allocated 
256MB RAM. I've seen this happen few cases, which is why for 4.11+ VRs on 
vmware the guest os type selected is 'other linux 64'. Reference:


https://github.com/apache/cloudstack/blob/master/engine/schema/src/main/resources/META-INF/db/schema-41000to41100.sql#L448


Can you share what RAM allocation you see from vCenter side and inside of the 
VR by sharing the 'free -m' output from the VR?


While one can always increase the cpu/memory limits for default system 
offerings, the default of 256MB RAM should ideally work (at least works on kvm, 
xenserver). If we can conclude this behaviour, we can consider increasing the 
default VR RAM by 64 or 128MB, i.e. to 320 or 384 MB by default.


- Rohit






From: Rene Moser 
Sent: Tuesday, September 18, 2018 9:26:05 PM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: VRs swapping with 256 MB RAM

Hi

While running test for a 4.11.1 (VMware) upgrade in our lab, we run into
low memory / swapping of VRs having 256 MB RAM. After 2-3 days it became
critical because the management server connections to VRs took very
long, minutes, this resulted in many more problems all over.

Make sure your VRs have enough RAM.

Regards
René

rohit.ya...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

Network "restart required - yes"

[Andrija Panic]

Hi all,

does anyone know it means when on the Network tab (this is VPC network) it
says "Restart Required - yes" ?
 (the VR is using latest, up-to-date template just FYI).

Thanks,

-- 

Andrija Panić

Apache CloudStack Generic Key-Value and Communication Plug-in

[Ivan Kudryavtsev]

Hello, community.

We glad to announce a new Open Source plug-in for Apache CloudStack which
helps to maintain generic key-value storages. There are three types are
supported right now:

- temporary KV with TTL (many per account);
- persistent KV bound to VM (one per VM);
- persistent KV bound to account (many per account).

KV storages support a commit-log based approach where old values are not
erased with new ones and it provides the access to the last key/values and
to the history which helps to maintain things like quorums and other
operations which require serialized access.

The plugin uses Elasticsearch. I

If you are interested to know more, contact our website for the full
announcement and download details:
https://bitworks.software/en/2018-09-19-acs-vm-kv-storage-plugin.html

All questions, improvements and considerations are welcome!

-- 
With best regards, Ivan Kudryavtsev
Bitworks LLC
Cell: +7-923-414-1515
WWW: http://bitworks.software/