New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Resizing a server
For the providers here, how do you handle resizes / upgrades / downgrades?
- Are they all automated
- Do you allow resizes to custom formats to should they upgrade all to a bigger plan
- Do you allow downsizes (of disk?)
- How do you do the billing (and what if there are multiple resizes)
- Do resizes affect the hypervisor node a vps is placed on? Do you resize-by-migrate?
SolusVM seems to lack a client side option to resize a plan... Openstack however has it. Any others? Custom panels maybe?
Comments
Seems like it's possible to upgrade within SolusVM, GreenValueHost gave me 8TB of ram for free
OpenStack resize is annoying, you can't just add another virtual core without having to also resize the entire disk AFAIK (or bypassing OpenStack / editing SQL, which is often going to break things).
OpenVZ supports online resizes - both up and down of RAM, HDD space and CPU power. The VPS doesn't even have to be rebooted.
We allow resizing during upgrades.
Are they all automated?
No, disk resizes done manually
Do you allow resizes to custom formats to should they upgrade all to a bigger plan
Only for ext4
Do you allow downsizes (of disk?)
No
How do you do the billing (and what if there are multiple resizes)
Pro-rated. Again, manual calculation for the current month. Regular new price applies from next month
Do resizes affect the hypervisor node a vps is placed on? Do you resize-by-migrate?
We allocate disk space completely (and not sparse file).
I believe this can be done through solusvm, the billing would be whmcs and and it can do the automation
Just a matter of which flavours you have defined. If your define a new flavour limited to one tenant and give that the better specs it works just fine.
We allocate disk space completely (and not sparse file).
Assuming you use local storage, if the disk becomes to big for the host node, do you migrate?
Yes, of course
That is just a display bug, you can't hit more than the RAM they assigned you.
CloudStack can resize data disks. This is limited to specific hypervisors like KVM. Root disks can be resized by KVM. OpenStack do resize over cloud-init (phyton scrip for cloud instance provisioning) which can resize instances included partitioning and filesystem updates.
Upgrades should be unproblematic, but shrinks can lead data loss. Customer must shrink there partitions and filesystems correctly. So resize on LVM/file based images can produce some problems. Mostly it is easier to drop the instance or data disk and create a bigger one.
Systems like openvz or docker do not have this problem. Disk limits are built in software and can resized easily.
free -h gives me 8TB total
Try to allocate more than the RAM you have assigned initially, and you'll see