Overview

The Context System (sometimes referred to as "context") is used by the platform to inject details into instances. It uses live attached disks to define networking interfaces and add SSH keys.

Future releases will include additional features.

Live-Update Support

The following table lists the live-attach and live-detach support for instances on the platform. Instances without support will still accept manual configuration after changing networking or disks from the web panel or API.

Instance	Disks	Networks	SSH Keys
CentOS 6.6	Yes	Yes	Yes
Citrix NetScaler	Yes	No(1)	No(1)
Debian 7.0 Wheezy	Yes	Yes	Yes
Debian 8.0 Jessie	Yes	Yes	Yes
FreeBSD 10.1-RELEASE	Yes	Yes	Yes
Ubuntu 14.04 Trusty LTS	Yes	Yes	Yes
VyOS 1.1 Helium	Yes	No(1)	No(1)
Windows Server 2008 R2	Yes	Yes	No(2)
Windows Server 2008 R2	Yes	Yes	No(2)

Specialized templates such as NetScaler and VyOS require manual configuration. Refer to the Routing chapter for information.
Windows Server templates use the Remote Desktop Protocol (RDP) by default, which require a new user password to be set upon creation. As this happens at the application layer, OrionVM engineers are not made privy to these credentials.

Upgrades

Linux and FreeBSD instances are pre-installed with a Context System repository, and are distributed through the context-system package.

Upon updating the system package manager, upgrades to the context. On Ubuntu and Debian:

apt-get update
apt-get upgrade context-system

On CentOS:

yum upgrade context-system

And on FreeBSD:

pkg update
pkg upgrade context-system

Disabling

The Context System can be disabled for circumstances where it is not required, or where it may overwrite local settings.

To disable the Context System for a target VM, you can use the OrionVM Developer API:

Log into the Organisation containing the VM to change.
In the top-right corner of the screen, select the Organisation name. This will open a drop-down menu. Choose Organisation Settings
From the sidebar under Integrations, select Access Tokens.
Click Create a token. Make a note of the token it generates, as it cannot be shown again.

You will also need the UUID of the target VM. To find this:

Log into the Organisation containing the VM to change. Click Instances from the sidebar.
Type Alt/option + Shift + i to bring up the IDs.
Copy the ID for the target VM.

With an API token and the target VM ID, you can now disable the Context System. In your console, enter the following commands:

$ OAUTH_TOKEN="<ACCESS TOKEN>"

$ curl -X POST \
    <PORTAL URL>/api/v1/instances/<VM ID>/context \
    -H "Authorization: Bearer $OAUTH_TOKEN" \
    -H "Content-Type: application/json" \
    -d '{
        "CONTEXT": "false",
    }'