Skip to content

PersonalSetup

Jump to bottom
uakfdotb edited this page Jan 8, 2016 · 1 revision

Although Lobster is designed as an hourly billing panel, it can also be used to control your own virtual machines on disparate platforms from one panel.

Installation and Configuration

First, follow the instructions in the Getting Started guide to install and configure Lobster. You'll want to add a VMI to lobster.cfg.json for each platform that you want to manage in your panel instance.

Create Administrator Account

Run Lobster, navigate to localhost:8080 in your web browser, and create an account.

Then, give your new account administrator access with a MySQL query:

UPDATE users SET admin = 1;

Now, if you login, you can access the administration section in the panel by clicking the dropdown menu in the top right, and selecting "Admin".

From the administration section, select Users, select your account, and then give yourself a large amount of credit.

Associate Plans and Images

Lobster assumes administrators will manually add plans and images. For personal use, we don't want to go through that process. Instead, we'll use the autopopulate functionality to automatically associate any plans and images supported by the platforms.

Select Plans from the administration section. For each region that you have configured, select the region under Autopopulate, and press the autopopulate button.

Then, do the same for Images.

Now, if you go back to the panel (select icon in top right, click Panel) and try to provision a VM, you should see plans and images already available.

Associating Existing VMs

You might also want to associate VMs that you have previously provisioned on the platforms with Lobster. Currently, this cannot be done from the panel. Instead, perform a MySQL query like this:

INSERT INTO vms (user_id, region, plan_id, name, identification) VALUES (1, 'REGION', PLAN_ID, 'NAME', 'IDENTIFICATION');

You'll need to replace some fields:

  • REGION: this is the region name used in lobster.cfg.json
  • PLAN_ID: ID of the plan in the database; go to Admin -> Plans to find the ID, or use the ID of an arbitrary plan if you don't care about the VM specifications showing up correctly in the panel
  • NAME: label for the VM in the panel, e.g. the VM hostname
  • IDENTIFICATION: ID of the VM in the backend; for example, on Luna Node, this would be the integer ID that you see in the URL when selecting your VM from the Luna Node Dynamic panel.

Clone this wiki locally