ustcweizhou opened a new issue #3455: Configurable disk size of systemvm
URL: https://github.com/apache/cloudstack/issues/3455
 
 
   Currently we have systemvm template which has very small disk size.
   Because of this, it is difficult to install new packages or upgrade existing 
packages.
   Another issue is, if disk is full, virtual routers will not work because 
cloudstack will write some files to local disk when new configurations are 
applied to virtual routers.
   
   Here is the partitions of a virtual router
   ```
   root@r-220-VM:~# df -h
   Filesystem      Size  Used Avail Use% Mounted on
   udev            110M     0  110M   0% /dev
   tmpfs            49M   25M   24M  52% /run
   /dev/sda5       1.1G  714M  342M  68% /
   tmpfs           121M     0  121M   0% /dev/shm
   tmpfs           5.0M     0  5.0M   0% /run/lock
   tmpfs           121M     0  121M   0% /sys/fs/cgroup
   /dev/sda1        92M   35M   57M  39% /boot
   /dev/sda6       435M   31M  400M   8% /var
   /dev/sda7        75M  1.6M   72M   3% /tmp
   tmpfs           121M   20K  121M   1% /ramdisk
   tmpfs            25M     0   25M   0% /run/user/0
   ```
   
   
   ##### ISSUE TYPE
   Improvement Request
   
   
   ##### COMPONENT NAME
   SystemVM Template
   
   ##### CLOUDSTACK VERSION
   4.14 (?)
   
   
   ##### SUMMARY
   
   It would be nice to make disk size of systemvm configurable.
   To archive it, we need to 
   (1) add global setting to indicate the disk size of systemvms and virtual 
routers
   (2) allocate disk with new size when provision the systemvm and virtual 
routers
   (3) install some packages/scripts in sysemvm template, so systemvm/vr can be 
auto-resized when systemvm/vr start.
   some documents in openstack: 
https://docs.openstack.org/image-guide/openstack-images.html#disk-partitions-and-resize-root-partition-on-boot-cloud-init
   
   We might need to change scripts to build the systemvm template (to have only 
one partition in systemvm ?)
   
   this is related to #3426  @rhtyd 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to