Management Console

From PrgmrWiki
Revision as of 21:20, 2 September 2016 by Will (talk | contribs)

When you sign up, you give us an OpenSSH format public key. This key gives you access to simple text-based menu that lets you turn your domain on, off, and allows you to connect to the serial console. If you need help on how to make a key, please refer to Making an ssh key.


New Console (<user>@console-customer1.prgmr.com)

Legacy Console (<user>@<user>.console.xen.prgmr.com)

Logging in from an OpenSSH Client (Linux, Windows Cygwin) or Terminal (OS X)

To login to the new console (if your instance was created after August 21, 2016), use the command

ssh -i <path to secret key> <user>@console-customer1.prgmr.com

To login to the legacy console, use the command
<pre>
ssh -i <path to secret key> <user>@<user>.console.xen.prgmr.com

If this is your first time logging in, use the server public key list to verify the server fingerprint based on IP address.

Logging in via PuTTY Client (Windows only)

If you are unable to connect, please verify your version of PuTTY is up to date (0.64 or newer). You want to be using 0.64 or newer anyway since private keys were not completely wiped from memory before 0.64.

Starting from initial defaults the PuTTY Configuration settings are as follows:

  • For instances created before August 21, 2016, "Session:Host Name" needs to be <vpsname>.console.xen.prgmr.com, example "icecream.console.xen.prgmr.com" for a VPS named "icecream"
  • For instances created after August 21, 2016, "Session: Host Name" needs to be console-customer1.prgmr.com
  • "Session:Connection type" needs to be SSH
  • "Connection/Data: Auto-login username" needs to be <vpsname>, example "icecream" for a VPS named "icecream"
  • "Connection/SSH/Auth:Private key file for authentication" needs to point to the .ppk file associated with the public key used

Under "Session:Saved Sessions", name this session "Management for <vpsname>.xen.prgmr.com" and save. Click open to connect to the management console.
You may use this registry file as a starting point, however PLEASE open it with a text editor and review it before importing. Use at your own risk.

If this is your first time logging in, use the server public key list to verify the server fingerprint based on IP address.

Using

Once you log in, you see this menu (here, the domain is called cnryfield:)

Name                                        ID   Mem VCPUs	State	Time(s)
cnryfield                                  218  1024     1     r-----    1898.8

    Wiki at http://wiki.prgmr.com
    Please contact support@prgmr.com with any issues accessing your machine.

    Options for "cnryfield"
    1. out of band console (press ctrl-] to escape, not resizeable)
    2. create/start, opens OOB console (try this if the machine is not running)
    3. shutdown (requests operating system to shut down)
    4. force power off (destroy/hard shutdown)
    5. reboot (requests operating system to reboot)
    6. swap i386/amd64 bootloaders currently "i386"
    7. view/add/remove ssh authorized_keys
    8. set reverse dns
    9. swap pvgrub/grub2 bootloaders currently "pv-grub"

    0. exit


The out of band console can be used to access the serial console when the domain is running. Like other serial consoles, often you see nothing until you use ctrl-c or hit return, at which point you should see the normal login prompt

CentOS release 5.2 (Final)
Kernel 2.6.18-53.1.14.el5xen on an i686

cnryfield login: 

To exit the console once at the login screen shown above in most terminals, the escape sequence is ctrl+].

Create/start should be used when the domain is not running. Before printing the menu the script runs the xen command showing the status of the domain. Example output from when the domain is not running:

Domain cnryfield is not running.

Shutdown is used to nicely shut down the domain, like hitting the power button of a physical machine briefly.

Force poweroff is used to force the domain to shut down, like holding down the power button of a physical machine for several seconds.

Reboot requests the domain to reboot. Note that if your IPs have changed since the last time you started the machine, you will need to do a shutdown (3) or destroy (4) instead of just a reboot.

Swap i386/amd64 bootloaders should be used if you are reinstalling your OS with a different architecture; almost all operating systems come in 32 bit (i386) and 64 bit (amd64) flavors.

View/add/remove ssh authorized_keys should be used if you wish to add or remove ssh keys authorized to access this menu. It will not change the keys on your domain as we have a policy of not modifying user disk images.

Set reverse dns allows you to modify reverse DNS, IE the dns name that comes back when you type 'host <myip>' .

Swap pvgrub/grub2 bootloaders allows switching between legacy grub (pv-grub) and grub2.

Exit will end the ssh session.


The new console has two additional options:

Install new OS image which offers a menu that looks like this:

Installation will reset your system to boot from disk.

Options:
1. Ubuntu Trusty 14.04 - 64 bit
2. Ubuntu Trusty 14.04 Docker - 64 bit
3. Ubuntu Xenial 16.04 - 64 bit
4. Ubuntu Xenial 16.04 Docker - 64 bit
5. Debian Wheezy - 64 bit
6. Debian Jessie - 64 bit
7. Centos 6 - 64 bit
8. Centos 7 - 64 bit
9. Centos 7 Docker - 64 bit
a. Fedora 23 - 64 bit
b. Fedora 24 - 64 bit

System details, whose output looks something like

Command result: 
        Virtualization mode: HVM
        Memory: 640 MiB
        VCPUs: 1
        Total disk: 15 GiB
        IPs: 71.19.146.8 2605:2700:0:3:a800:ff:fe24:a3a0
        Last installed OS: Centos 7 - 64 bit
        Boot option: Disk