Quick Start

The following guide will take you through the steps necessary to start your first virtual machine instance.

Prerequisites:

  • Up-to-date web browser
  • Active account in MetaCentrum Cloud
  • Basic knowledge of SSH (for remote connections)

Sign In

The dashboard is available at https://dashboard.cloud.muni.cz.

  1. Select EINFRA CESNET.

    Notice:
    Users of the Czech national e-infrastructure should always select EINFRA CESNET. International users may choose EGI Check-in or ELIXIR AAI, depending on their membership.
  2. Click on Sign In.

  3. Select your institution from the drop-down list.

    Notice:
    You can use the search box at the top as a filter.
  4. Provide your institution-specific sign-in credentials.

  5. Wait to be redirected back to our dashboard.

    Notice:
    If your attempts repeatedly result in an error message about projects, make sure you have an active MetaCentrum account and that you are selecting the correct institution when attempting to log in. If the problem persists, please, contact user support.

Create Key Pair

All virtual machine instances running in the cloud have to be accessed remotely. The most common way of accessing an instance remotely is SSH. Using SSH requires a pair of keys - a public key and a private key.

  1. In Project > Compute > Key Pairs, click the Create Key Pair button.

  2. Name your key. Avoid using special characters, if possible.

  3. You can see your newly created key pair and its fingerprint. We recommend you store the key in a safe location and back it up in case you accidentally delete it.

For details, refer to the official documentation.

Update Security Group

In MetaCentrum Cloud, all incoming traffic from external networks to virtual machine instances is blocked by default. You need to explicitly allow access to virtual machine instances and services via a security group.

You need to add two new rules to be able to connect to your new instance (or any instance using the given security group). This is similar to setting up firewall rules on your router or server. If set up correctly, you will be able to access your virtual machine via SSH from your local terminal.

  1. Go to Project > Network > Security Groups. Click on Manage Rules, for the default security group.

  2. Click on Add rule, choose SSH and leave the remaining fields unchanged. This will allow you to access your instance.

  3. Click on Add rule, choose ALL ICMP and leave the remaining fields unchanged. This will allow you to ping your instance.

For details, refer to the official documentation.

Create Virtual Machine Instance

  1. In Compute > Instances, click the Launch Instance button.

  2. Choose name, description, and the number of instances. If you are creating more instances, -%i will be automatically appended to the name of each instance.

  3. Choose an image from which to boot the instance. Image will be automatically copied to a persistent volume that will remain available even after the instance has been deleted.

  4. Choose the size of your instance by selecting a flavor. Additional volumes for data can be attached later on.

  5. (optional) On the Configuration tab, you can use user_data to customize your instance at boot. See cloud-init for details.

For details, refer to the official documentation.

Setup Router gateway (Required for Group projects)

Completing Create Virtual Machine Instance created instance connected to software defined network represented by auto-allocated private network, subnet and router. Router has by default gateway address from External Network public-muni-147-251-124, which is for non-production only and is released daily. For persistent gateway address follow these steps:

  1. In Network > Routers, click the Set Gateway button next to auto_allocated_router.

  2. From list of External Network choose public-cesnet-78-128-251 or private-muni-10-16-116

Router is setup with persistent gateway.

Associate Floating IP

To make an instance accessible from external networks (e.g., The Internet), a so-called Floating IP Address has to be associated with it.

  1. In Project > Network > Floating IPs, select Allocate IP to Project. Pick an IP pool from which to allocate the address. Click on Allocate IP.

    Notice:
    When picking an IP pool from which to allocate a floating IP address, please, keep in mind that you have to allocate an address in the pool connected to your virtual router. For automatically allocated routers, this means public-muni-147-251-124.
    Warning:
    Group projects can persistently allocate IPs only from public-cesnet-78-128-251 or private-muni-10-16-116 networks. IPs from public-muni-147-251-124 allocated to Group projects will be released daily.
    Notice:
    Please, keep an eye on the number of allocated IPs in Project > Network > Floating IPs. IPs remain allocated to you until you explicitly release them in this tab. Detaching an IP from an instance is not sufficient and the IP in question will remain allocated to you and consume your Floating IP quota.
  2. In Project > Compute > Instances, select Associate Floating IP from the Actions drop-down menu for the given instance.

  3. Select IP address and click on Associate.

Create Volume

When storing a large amount of data in a virtual machine instance, it is advisable to use a separate volume and not the root file system containing the operating system. It adds flexibility and often prevents data loss. Volumes can be attached and detached from instances at any time, their creation and deletion are managed separately from instances.

  1. In Project > Volumes > Volumes, select Create Volume.
  2. Provide name, description and size in GBs. If not instructed otherwise, leave all other fields unchanged.
  3. Click on Create Volume.
  4. (optional) In Project > Compute > Instances, select Attach Volume from the Actions drop-down menu for the given instance.
  5. (optional) Select Volume ID from the drop-down list and click Attach Volume.

For details, refer to the official documentation.

results matching ""

    No results matching ""