Context: for SolusVM we only require setup of a single Lobster plan. Then we use customdisk, customcpu, etc. to configure the plan so that it matches the one in the Lobster database.
For OpenVZ, the vserver-create returns an invalid custom burst memory error if we set custommemory. Currently we are using a work-around where we change the memory after provisioning instead of initially. We should improve on this if possible.
Context: for SolusVM we only require setup of a single Lobster plan. Then we use customdisk, customcpu, etc. to configure the plan so that it matches the one in the Lobster database.
For OpenVZ, the vserver-create returns an invalid custom burst memory error if we set custommemory. Currently we are using a work-around where we change the memory after provisioning instead of initially. We should improve on this if possible.