VMIConfig: SolusVM

The Lobster SolusVM interface requires a single client to be created with username set to "lobster". All services will be provisioned on this SolusVM client. An administrative API ID is also needed. The following keys are checked:

• name: a label for the region
• type: set to "solusvm"
• virt_type: a SolusVM virtualization type (e.g. "kvm", "openvz")
• node_group: the target node group ID, expressed as string (e.g. "1")
• url: API access URL ("https://example.com:5656/api/admin/command.php")
• api_id: API ID
• api_key: API key
• insecure: optional; either true or false (without quotation marks since it is JSON bool), with false being default. If true, then HTTPS certificate at API URL won't be validated.

Images

To register an image, use the image filename without extension. It should be the same as other software that uses API.

Plans

A dummy plan with name set to "Lobster virttype" (e.g. "Lobster openvz" or "Lobster kvm") must be created; all virtual machines will use this dummy plan. Lobster will assign customdiskspace/custommemory/customcpu so that the plan matches the one specified in Lobster. Note that the plan will have a large bandwidth allocation; this is because Lobster bills for bandwidth overages, so the backend shouldn't be handling it.

VNC

For virtualization types that support VNC, Lobster will provide a noVNC client that will connect from the Lobster server to the host node. This means you can lockdown the host node VNC access if desired, so that only connections made via Lobster are permitted; this is of course not necessary.