
Remote Desktop Provisioning
The remote desktop is a regular RockyLinux instance equipped with X2Go. It enables you to access a graphical desktop computer running in your remote instance of choice, over a low bandwidth (or high bandwidth) connection. This means that you can connect to it via the X2Go client to enjoy a regular desktop user experience.
This is a configuration template (i.e. an Ansible Playbook) to customize your environment in the European Weather Cloud (EWC).
The template is designed to:
-
Provision an instance via Terraform, with your specified Linux distribution and desired flavor (a.k.a VM plan):
- If a
terraform.tfstate
state file is not found under the user-defined directory, attempts to create the instance from scratch
OR
- if
terraform.tfstate
file is found, leverages Terraform's out-of-the-box
functionality to update the instance referenced on it
- If a
-
Configure the existing or newly provisioned instance such that it:
- Enables users to operate the remote hosts through a graphical desktop (i.e. a MATE desktop environment), over a low or high bandwidth connection.
After successful provisioning, you can take advantage of Terraform built-in
functionality to safely modify or delete the instance. You'll find the definition of your
instance in main.tf
, and its current state in terraform.tfstate
, under the user-defined
tf_project_path
directory.
To learn the basics about managing infrastructure with Terraform, checkout the official documentation examples.
Prerequisites
💡 Versions listed correspond to minimal prerequisites.
To successfully run this playbook, the following packages should be available in your work environment:
Name | Version | License | Home URL |
---|---|---|---|
git | 2.0 | GPLv2 | https://git-scm.com/downloads |
python | 3.9 | PSF | https://www.python.org/downloads |
ansible | 2.15 | GPLv3+ | https://pypi.org/project/ansible |
terraform | 0.14 | BSL | https://developer.hashicorp.com/terraform/install |
Usage
1. Download Ansible dependencies
💡 By default, Ansible Roles are installed under the
~/.ansible/roles
directory within your working environment.
Download the correct version of the Ansible dependencies, if you haven't done so already:
ansible-galaxy role install -r requirements.yml
2. Configure and apply the template
2.1. Interactive Mode
By running the following command, you can trigger an interactive session that prompts you for the necessary user inputs, and then applies changes to your target EWC environment:
ansible-playbook remote-desktop-provisioning.yml
2.2. Non-Interactive Mode
💡 To learn more about defining variables at runtime, checkout the official Ansible documentation.
You can also run in non-interactive mode by passing the
--extra-vars
or -e
flag, followed by a map of key-value pairs; one for
each and every available input (see inputs section below). For example:
ansible-playbook \
-e '{
"ewc_provider": "eumetsat",
"tf_project_path":"~/iac/x2go-server-1",
"app_name":"x2go",
"instance_name":"server",
"instance_index": 1,
"flavor_name":"eo2.medium",
"image_name":"Rocky-9.5-20250604142417",
"public_keypair_name":"john-claudy-publickey",
"private_keypair_path":"~/.ssh/id_rsa",
"private_network_name": "private",
"security_group_name": "ssh",
"whitelisted_ip_ranges": ""
}' \
remote-desktop-provisioning.yml
3. Install the local client and connect to your remote desktop
⚠️ When configuring a connection, be sure to select "MATE" (instead of "KDE" or any other options) in the
Session Type
drop-down list, towards the bottom of theSession
tab. This is required for the local client to correctly communicate with your remote desktop.
Install the remote desktop client on Microsoft Window, Mac OS or Linux by following the links on the official X2Go installation page. Then follow the official X2Go client usage page if you do not know how to configure a new session.
For a session creation example, representative of a typical EWC environment, checkout the Remote Desktop section of this official EWC documentation page.
Inputs
Name | Description | Type | Default | Required |
---|---|---|---|---|
ewc_provider | your target EWC provider. Must match that the provider of your OpenStack application credentials. Valid input values are ecmwf or eumetsat . |
string |
n/a | yes |
tf_project_path | path to terraform working directory. Example: ~/iac/x2go-server-1 |
string |
n/a | yes |
app_name | application name, used as prefix in the full instance name. Example: x2go |
string |
n/a | yes |
instance_name | name of the instance, used in the full instance name. Example: server |
string |
n/a | yes |
instance_index | index or identifier for the instance, used as suffix in the full instance name. Example: 1 |
number |
n/a | yes |
flavor_name | name the flavor to use for the instance. To learn about available options, checkout the official EWC VM plans documentation. 💡 A VM plan with at least 4GB of RAM is recommended for successful setup and stable operation. | string |
n/a | yes |
image_name | name of the image to use for the instance. For complete information on available options, see the official EWC Images documentation. ⚠️ Only RockyLinux 8.10 and 9.5 instances are currently supported due to constrains imposed by the required ewc-ansible-role-remote-desktop Ansible Role. Example: Rocky-8.10-20250204105303 |
string |
n/a | yes |
public_keypair_name | name of public keypair (stored in OpenStack) to be copied into the instance for remote SSH access | string |
n/a | yes |
private_keypair_path | path to the local private keypair to use for SSH access to the instance. Example: ~/.ssh/id_rsa |
string |
n/a | yes |
private_networks_name | private network name to attach the instance to. Example: private |
string |
n/a | yes |
security_group_name | security group name to apply to the instance. Example: ipa |
string |
n/a | yes |
whitelisted_ip_ranges | IPv4 ranges (in CIDR format) to be whitelisted in Fail2ban configuration. When in doubt, do not set. Example: ['10.0.0.0/24','192.168.1.0/24'] |
list(string) |
n/a | no |
Dependencies
⚠️ Only RockyLinux 8.10 and 9.5 instances are currently supported due to constrains imposed by the required ewc-ansible-role-remote-desktop Ansible Role.
💡 A VM plan with at least 4GB of RAM is recommended for successful setup and stable operation.
Name | Version | License | Home URL |
---|---|---|---|
ewc-tf-module-openstack-compute | 1.4 | MIT | https://github.com/ewcloud/ewc-tf-module-openstack-compute |
ewc-ansible-role-remote-desktop | 1.1 | MIT | https://github.com/ewcloud/ewc-ansible-role-remote-desktop |