Quick start

In this section we examine several aspects that will assist you in adapting to the SIM-Cloud service interface and with the most important factor: getting started quickly with running your infrastructure in our cloud.

The following fundamental points for fast deployment are covered:
  • Overview of project resources after activation.
  • Quick deployment of an instance, plus the settings for remote access to it.
  • Creating a disk and launching the instance under the MS Windows 2016 Standard operating system.
  • Assigning a floating IP address for the instance and basic settings for remote access by RDP.
  1. Accessing the SIM-Cloud dashboard
1.1 Open the web browser, with JavaScript and cookies enabled.


We recommend that you use the latest version of either Google Chrome or Mozilla Firefox.

MS Edge may cause errors to occur, although most functions work normally.
IE 11 may cause errors to occur, although most functions work normally.
IE 10 and below are not supported.
1.2. In the address line of the browser, enter the URL:  https://cloud.sim-cloud.net/.
1.3. On the login page that appears, enter your username and password, then press ‘Connect’.
Once authorisation is completed a new window opens, in the top of which your username is displayed.
You can also open the ‘Settings’ tab (‘OpenStack Dashboard‘ - ‘Settings’) or exit the dashboard.
  1. Project resources overview

Every SIM-Cloud project is created with a defined set of computational resources. The quota for all computational resources is assigned at the point of activation. The available free resources of the project allow you to create infrastructure objects such as instances, disks, routers, networks, subnetworks, backup copies, VPN services and so on. Before deploying your infrastructure you should check your quota of available resources.

Before deploying your infrastructure you should check your quota of available resources.

  • Computational resources (vCPU, RAM, storage)
  • Network resources (routers, subnetworks, floating IPs)
_images/4.png _images/5.png _images/6.png

By default, SIM-Cloud projects are activated using already created network objects:

  • One router (with the name vpc-router-project id);
  • One network (with the name vpc-network- project id and one subnetwork, with DHCP service;
  • One IPv4 floating IP address.

Network elements that have been created in advance enable the required infrastructure to be deployed quickly and access provided to the publicly accessible network.

  1. Creating the disk

The first requirement for launching an instance is to create a disk.

3.1. In the Project tab, open the Disks tab and select the Disks category.
3.2. Click ‘Create disk’.

In the dialog that opens, enter or choose the following values:

- Disk name: specify a name for the disk.
- Description: provide a brief description for the disk (this entry is optional).
- Disk source: Select the item ‘Image’. Find out more about the whole selection of available images, plus more information on how to use them, in our thematic article OS Images.
If you choose this parameter to create a disk, a new field will appear allowing the use of the image as a source. Select the required image from the list shown. If you create a new system boot disk, you must select an image with the required operating system. If you select ‘No sources, blank disk’, the service will create a blank disk without either a file system or a partition table. You should choose this option only if it is necessary to create an additional disk that can be connected to the instance. In our case we select to create a disk with the image for MS Windows 2016 Standard [RU] Build 14393.
- Type: select a disk type from the list (cs1 or gs1).
- Size (GB): disk volume in gigabytes (GB). The minimum recommended size for an instance with a Windows OS is 32 GB and for Linux OS is 16 GB.
- Availability zone: select a default availability zone.


Note that the list of available images for disk creation includes images supported by the ‘cloud-init’ function and also with the included option ‘key-based authentication’. The use of such images will enable the deployment of instances to be accelerated thanks to advance configuration with the aid of the cloud-init scripts, and the use of authentication keys will improve the security of working with the instance. These images include the tags [cloud-init, OS] in their properties. When creating an instance on the basis of images of this type it is essential to specify a key pair for subsequent authentication; if a key is not specified, it will not be possible to complete authentication by password (in which case it will be necessary to recreate the disk using a standard image or assigning a key during a repeated creation; there also remains the alternative option of resetting the passworde using standard Linux OS methods).

3.3. Click create disc.
3.4. Disc creation can be seen in the toolbar, in the discs tab.
     It may take about 10 minutes for the disc to be created.
  1. Launching the instance
4.1. In the "Project" tab, open the "Computing Resources" tab and click on the "Disks" category.
4.2. The toolbar displays disks with their own attributes: "Name", "Description", "Size", "Status", "Type", "Connected to",
     Availability Zone, Bootable, Encrypted, Action.
     In the "Actions" column, select the drop-down list for your disk and click "Run as Instance".
4.3. In the Launch Instance dialog box, specify the following required values.


- Instance name. Provide an initial hostname for the instance.


The name you assign here becomes the initial hostname of the server. If the name is longer than 63 characters, the service will automatically truncate it to ensure that dnsmasq works correctly. If, after building the server, you change the server name in the API, or change the hostname directly, the names will not be updated in the control panel. Server names are not guaranteed to be unique when created, so you may have two instances with the same hostname.

In instance naming, it is unacceptable to use Cyrillic and Umlaut (Ää, Öö and Üü), the use of these symbols will lead to an instance creation error.

- Availability zone. Selecting the default availability zone.
- Number. To run multiple instances, enter a value greater than 1. The default is 1.

A source:

- Disk. If you chose to launch an instance using a disk, the Disk field will be displayed.
Select the drive name from the list that appears.
If you want to delete the disk when deleting an instance, select the Yes checkbox next to the Delete disk when deleting an instance option.
We recommend that you select “No”, this will ensure that when you delete the instance, your boot disk will not be deleted.

Instance type:

- Instance types:. Specify the size of the instance to run.
Instance types are responsible for the amount of memory and processing power allocated to the instances that are created.
Please note that the type of instance is selected depending on the image selected to launch the instance.


- Select the created private subnet of the “vpc-network-project id” type.
To add a network to an instance, click + in the Available field.

Security groups

Select the security groups that you want to assign to the instance.

Security groups - it’s kind of
cloud firewall that determines which network outbound and inbound traffic is redirected to the port of the instance.

If you have not created any security groups, you can only assign the default security group to the instance.

4.4. Click Launch Instance.
     The instance runs on a compute node in the cloud.
4.5. Completion of the OS installation process.
Access to the instance via the console:
- In the Projects tab, open the Instances tab.
- In the action column, select the drop-down list for your Instance and click “Console”, which will open a new window.
In a new window, you will have access to the instance console, where you can complete the OS installation.
  • Please note that only Windows instances require additional configuration after installation, Linux instances
    do not need additional actions and are immediately ready to work.
_images/20.png _images/21.png
  • When creating a disk that is larger than the minimum required volume, you must complete the procedure for expanding the disk using OS tools.
4.6. Checking network settings.
Each instance has a private fixed IP address, and can also have a public or floating IP address.
Private IP addresses are used for inter-instance communication, and public addresses are used for communication with networks outside the Cloud, including the Internet.
When launching an instance, it is automatically assigned a private IP address, which remains unchanged as long as
until you explicitly delete the instance or disconnect the network interface. Rebooting the instance does not affect the private IP address.
All instances receive network settings via DHCP. Using a connection to a private internal subnet from the range, the instances have access to the public network - the Internet.
The private subnet uses a NAT mechanism to the outside public network. In this case, the instances only have access to the public network, but you do not have access from
public network to instances. This type of access allows you to download updates for the OS, software, or set up a VPN tunnel between the office and the cloud infrastructure.
_images/24.png _images/25.png _images/26.png
If you need public network access to your instance, you need to use a floating IP address.
We will describe this issue in the next step.
  1. Assigning a floating IP
Besides a fixed IP address Floating IP an instance can be assigned a floating IP.
Unlike fixed IPs, floating IPs can change their associations at any time, regardless of the state of the instances involved.
This procedure describes how to reserve a floating IP address from an existing pool of addresses and associate that address with a specific instance.

In the Projects tab, select the Networking tab.

5.1. Go to the Floating IPs tab, which displays the floating
     Instance-dedicated IP addresses.
5.2. Click to "Allocate ip to project" button
5.3. Select the pool from which to select an IP address.
5.4. Click "Allocate IP".
5.5. In the Floating IPs list, click Assign.
5.6. In the Manage Floating IP Assignment dialog box, select the following options:

The IP address field is filled in automatically, but you can add a new IP address by clicking the "+" button.
In the Destination Port field, select a port from the list.
The list displays all instances with fixed IP addresses that can be assigned a floating IP.

5.7. Click Assign.

_images/30.png _images/31.png

To unbind the IP address from the instance, click the Unassign button.

When a floating IP is assigned to an instance, you need to change group policies.

This step will allow you to finally open remote access to the instance from required IP addresses or subnets.

  1. Changing security groups

    All outbound traffic is allowed on instance ports, and inbound traffic is blocked by the default security group.

This procedure includes access to the instance via RDP and ICMP (ping). The rules apply to all instances within a given project and must be installed for each project unless there is a reason to deny RDP or ICMP access for instances.

Adding a rule to the default security group:

6.1. На вкладке «Проект» откройте вкладку «Сеть».
On the Project tab, open the Networking tab.
6.2. Select a default security group and click Manage Rules.
6.3. To allow RDP access, click Add Rule.
 6.4. In the Add Rule dialog box, enter the following values:

  Rule: RDP
  Remote Address: CIDR

To accept requests from a specific range of IP addresses, enter a block of IP addresses in the CIDR field.
6.5. Click Add.
6.6. Now port 3389 RDP will be open on the port of the instance, for requests from any IP addresses.
6.7. To add an ICMP rule, click "Add Rule".
6.8. In the Add Rule dialog box, enter the following values:
Rule: All ICMP
Direction: Incoming traffic
Remote address: CIDR
_images/35.png _images/36.png
6.9. Click Add.

Instances will now accept all incoming ICMP packets. Additionally, for Windows instances, you must enable ICMP permissive rules.

_images/37.png _images/38.png _images/39.png

After you assign an IP address and configure the security group rules for the instance, it will become publicly available on the floating IP address from the public network.

  1. Exiting the SIM-Cloud dashboard

At the top of the window where your username is displayed, you must select the drop-down list and click “Logout”, after which you will be redirected to the login page.


Let’s summarize.

After studying this article, we can quickly create instances and configure access to them using security groups and floating IP.