Instances
In this article:
Instances#
K2 Cloud provides computing resources as instances. The Instances subsection is used to create virtual machines, change their parameters and advance settings, and display a list and details of all instances created under the project and VPC.
Each instance has several parameters:
ID — the unique instance identifier in K2 Cloud.
Status — the current status of the instance. An instance can have the following statuses:
Pending
Running
Stopped
Booting
Suspending
Suspended
Snapshot
Name tag is a tag with the Name key and a value set by a user. To learn more about tags, please see Tags section.
Type – the instance type.
Availability zone — the information on the data center in which physical hardware is located.
Subnet — the subnet in which the instance is located.
Created — the instance creation date.
SSH-key — the specific SSH-key assigned to an instance.
Elastic IP — the external IP address of the primary network interface of an instance.
Private IP — the private IP address of the primary network interface of an instance.
Placement group — the placement group that the instance belongs to.
Click the icon on the right to search bar to go to instance parameter display settings.
Instance types#
K2 Cloud offers users a wide variety of instance types with different combinations of computing resources and memory sizes.
Все типы экземпляров сгруппированы и упорядочены по семействам. Вы можете выбирать типы из семейств общего назначения (General Purpose), оптимизированных для памяти (Memory Optimized), вычислений (Compute Optimized), запуска ресурсоёмких приложений (HPC Optimized) и с гарантированной доступностью vCPU менее 100% (Shared Core).
Для всех экземпляров, кроме семейства Shared Core, гарантируется 100 % доступность ресурсов. Несколько экземпляров семейства Shared Core совместно используют одно физическое ядро, при этом каждому гарантируется определённый процент процессорного времени — не ниже 50 % или 20 % в зависимости от типа экземпляра. Это позволяет сократить расходы для сервисов и задач, где не нужна постоянная полная загрузка процессоров. Если ресурсы свободны, конкретному экземпляру может предоставляться до 100 % процессорного времени.
The table provides recommendations on instance types for various tasks.
Семейство |
Description |
Применение |
|---|---|---|
General Purpose |
These instances are suitable for wide range of tasks. They offer a balance of computing power and memory size. |
|
Compute Optimized |
These instances are optimized for compute-intensive workloads. They are optimal for tasks that require many computing cores, but do not require a large amount of memory. |
|
Memory Optimized |
These instances are optimal for memory-intensive workloads. They offer more memory per core than instances of other types. |
|
HPC Optimized |
These instances deliver ultra-high performance for compute-intensive workloads. These instances are based on 2nd Generation Intel® Xeon® Scalable Processors. |
|
Shared Core |
Экземпляр с гарантированной доступностью процессорного времени 50 % и 20 %. Для сервисов и задач, где не нужна постоянная полная загрузка процессоров. |
|
K2 Cloud instances are powered by Intel® CPUs. Hardware characteristics for each generation are shown in the table.
Important
In the ru-spb region, only instances powered by gen5 CPUs are available.
Generation 1 |
CPU |
Architecture |
Characteristics |
|---|---|---|---|
gen5 |
Intel® Xeon® Gold 6254 |
Cascade Lake |
Max Turbo Frequency 4.00 GHz |
gen5p |
Intel® Xeon® Gold 6244 |
Cascade Lake |
Max Turbo Frequency 4.40 GHz |
gen6 2 |
Intel® Xeon® Gold 6348 |
Ice Lake |
Max Turbo Frequency 3.50 GHz |
gen7 |
Intel® Xeon® Gold 6548y+ |
Emerald Rapids |
Max Turbo Frequency 4.10 GHz |
- 1
Gen3 (Intel® Xeon® Gold 6140) and gen4 (Intel® Xeon® Platinum 8168) processors are gradually being phased out.
- 2
The gen6 CPUs are installed only on dedicated hosts.
All our servers have the Power Boost option enabled. This allows instances to get the most out of the CPU and run at the maximum CPU frequency. Hypervisor does not allow passing this information to an instance. Therefore, if you try to check CPU frequency using OS tools from within the instance, you will see the base CPU frequency.
Creating an instance#
You can launch an instance using one of the following methods:
Create an instance using the wizard#
To launch the instance wizard, go to the section Virtual machines Compute Instance and click Create.
Step 1. Select an image#
When starting an instance, you need to select a pre-created image with the OS you want to use, for example, Windows, Debian, Ubuntu, etc.
In a drop-down list of the creation wizard, the following pre-created images are available for selection:
All images — all available images;
K2 Cloud images – images that K2 Cloud offers;
Own images – images created by a user in the Images subsection;
Shared images — user project images to which access is granted.
Note
To display backup-related images, enable Show recovery points.
To quickly find an image, you can use the image filter and/or search by ID or description. Select a pre-built image and click Select.
Note
If the desired image is not among the available images, click Create new image. You will be automatically switched to Images subsection. Create here the desired image according to the instruction. You will have to start the instance creation procedure all over again, so it is better to create the image in advance.
Note
If the image contains a backup copy of the instance, we recommend creating the instance directly from the backup. In this case, you will not need to redefine the instance parameters.
Step 2. Select an instance placement#
At this step, you need to select where in the cloud the instance will be placed.
Placement group — When you select a placement group, its member instances will be launched on different computing nodes. This helps minimize the number of failed instances if one of the physical nodes fails. To use the placement group, create it first. For more information, see the documentation on placement groups.
Important
Для экземпляров из семейства Shared Core группы размещения не поддерживаются.
Placement type — If the default value (
Shared server) is selected, instances will be started on a shared computing node where instances of other users can be deployed. To launch an instance on a dedicated host, order it first. More information about starting an instance on a dedicated host can be read in the respective section of the documentation.
Step 3. Select an instance type#
To quickly find the required instance type, you can search by instance type or apply filters by family, CPU generation, vCPU count, and RAM size. Select a predefined instance type from the list according to your needs and click Select.
Note
Если вы не уверены, какой тип ВМ лучше всего подходит для вашей рабочей нагрузки, лучше начать с использования экземпляров General Purpose. В K2 Cloud вы можете изменить тип экземпляра при необходимости. Для оптимальной производительности рекомендуем использовать типы экземпляров текущих поколений gen5.
Note
For Windows, we recommend choosing instance types with at least 4,096 MB RAM.
Step 4. Select instance parameters#
In this step, set the parameters required to create an instance.
Parameter |
Description |
|---|---|
Name tag |
A tag with the Name key and a value set by a user. |
Number of instances |
Number of instances of this type to create (1 by default). |
Virtualization type |
|
SSH-key |
If public SSH keys are added to the project, you can select one of them. |
VPC |
VPC where the instance will run. To create the instance in a new VPC, click Create a new VPC and subnet and set the required VPC and subnet parameters. |
Subnet |
Subnet where the instance will run. To create the instance in a new subnet, click Create a new subnet and set the required parameters. |
User data |
User data describes operations that are automatically executed when the instance is created. |
Delete on instance shutdown |
Specifies whether the instance should automatically be terminated after the shutdown. |
RAM monitoring 3 |
Selecting this option enables RAM monitoring. |
- 3
RAM monitoring is only available for Linux instances. In addition to enabling monitoring, CloudWatch agent must be installed on them (for details, see).
Then, you can directly proceed to view the selected instance configuration. To do this, click Overview and launch. Attachable devices, such as network interface and volumes, will use default parameters. To specify other parameters, add more devices, or set tags, click Next to go to the desired step.
Step 5. Select network devices#
In this step, set the parameters of the network interfaces that will be attached to the instance.
A network interface allows you to connect an instance to a subnet or switch. By default, a new instance will have a network interface with 0 index. This primary network interface cannot be detached from the instance.
Optionally, you can specify the following parameters:
Parameter |
Description |
|---|---|
Device index |
The primary network interface index of an instance ( |
Network interface |
You can select an existing interface or keep the field intact. A new interface will be created then. |
Network |
The field displays the subnet or switch selected in the previous step. |
Description |
Interface description provided by a user. |
Private IP |
The internal address of the primary interface at which the instance will be accessible. If a Private IP is not specified, it will be assigned automatically. |
Security groups |
Security groups to be assigned to the interface (up to 5 groups). If no security group is specified, a default group from the selected VPC will be assigned to the instance. |
Delete with instance |
This option specifies whether to delete the network interface along with the instance (enabled by default). |
Associate with existing Elastic IP 4 |
Associates an available public IP address to access the instance from the Internet after the instance launch. This can be done only if the network interface was created in a subnet and if the VPC has an attached internet gateway. The default value of the option (enabled or disabled) depends on the selected network interface. 5 |
- 4
If there is only one available Elastic IP, the Associate Elastic IP checkbox is displayed together with the address ID and the address itself. If there are no available addresses, the Allocate Elastic IP checkbox is displayed. When selecting it, specify the address pool (default one or user one) from which the Elastic IP will be allocated, and (optional) set the Name tag for the address. The address will be allocated automatically when proceeding to another step.
- 5
If the primary network interface is created in the subnet with enabled automatic Elastic IP association, then the Associate with existing Elastic IP option is also enabled by default. To disable this option, clear its check box. If the primary network interface is created in the subnet with disabled automatic Elastic IP association, then the Associate with existing Elastic IP option is also disabled by default. To enable it, select its check box.
In this step, you can create and attach additional network interfaces to the instance. To create a new interface or select an existing available network interface, click Add device.
You can create or select max. 15 network interfaces in this step. For more information on network interfaces, see Network Interfaces.
Once you have set interface parameters, you can proceed to review the configuration for quick instance creation or follow the other wizard steps. In the former case, click Review and launch; in the latter, click Next.
Step 6. Select volumes#
In this step, set parameters of the volumes that will be created with the instance.
A set of parameters in a dialog helps choose volume configuration:
Parameter |
Description |
|---|---|
Snapshot |
A snapshot from which you are going to create an instance (by default, snapshots that belong to the selected images are shown). |
Size |
Volume size in gibibytes (1 gibibyte = 1,024 mebibytes). |
Volume type |
Sets the desired volume type. For more information on volume features and parameters see page Volumes. |
IOPS |
The maximum total number of I/O operations per second. For volumes types gp2, st2 and st3 the number of IOPS is calculated automatically, for the volume type io2 you can specify the required number of IOPS. |
Throughput |
The maximum total rate, in MiB/s, at which data can be read from or written to a volume. It is calculated automatically. Calculated automatically. |
Delete with instance |
Specifies whether the volume must be automatically deleted after the instance is deleted. |
To add more volumes, click Add volume and specify the required parameters. You can attach up to 16 volumes to instances with the hvm virtualization type, and up to 4 volumes to instances with the hvm-legacy virtualization type.
For instance, the volume marked with the icon will be bootable, while the rest will be additional volumes. Unlike additional volumes, a bootable volume cannot be detached from an instance.
Once you have set the volume parameters, you can skip the next step (tag setting) and proceed directly to reviewing the instance configuration and creating the instance. To do this, click Review and launch. To set tags, click Next.
Step 7. Add tags#
At this step, you can assign custom tags to the instance and volumes that will be created with this instance. Specify key-value combinations, select Assign to volumes checkbox if necessary, and click Review and launch.
Step 8. Review parameters#
In the Review step, check your instance parameters and click Launch.
Instance start takes some time. Upon completion of the instance launch process, its status will change from Pending to Running. Each created instance is assigned a unique ID in the i-xxxxxx format.
Some instance parameters can be changed anytime. Click a link with unique ID to make changes, attach or detach additional volumes, reboot or shut down an instance, change public address, etc.
Create an instance from a launch template#
If you need to launch instances with the same parameters from time to time, use launch template to quickly launch an instance from a saved configuration. You can also create instances with differing parameters, using template versions.
Go to the Virtual machines section Compute Instances.
Справа от кнопки Создать в выпадающем меню выберите Создать экземпляр из шаблона запуска.
In the dialog window, select a launch template and its version.
If the option Security groups was selected when creating the launch template, then you should specify the subnet to which the primary network interface will be attached. If the Advanced network configuration option was selected when creating the launch template, you do not need specify the subnet. You will also see in the dialog window the ID and name of the VPC where the corresponding network resources are located.
Specify the number of instances to be launched.
If necessary, change the instance type and the Name tag, as well as the resources which the Name tag is assigned to.
To enable RAM monitoring, select RAM Monitoring checkbox.
Note
RAM monitoring is only available for Linux instances with CloudWatch agent installed (for details, see).
Once the parameters are set, click Overview and Launch and check the instance configuration.
To create an instance, click Launch.
You can also create an instance from a template in the Launch Templates section.
Create an instance from another instance#
You can create a required number of instances with the same parameters as an existing instance has.
Go to the Virtual machines section Compute Instances.
В таблице ресурсов выберите экземпляр с необходимыми параметрами, который будет использоваться в качестве эталонного.
To the right of the Create button, select Create an additional instance in the drop-down menu.
In the dialog window, specify the number of instances to be created.
To enable RAM monitoring, select RAM Monitoring checkbox.
Note
RAM monitoring is only available for Linux instances with CloudWatch agent installed (for details, see).
You can also change the Name tag, enable the Terminate on instance shutdown option to delete the instance after it is stopped, and add user data.
Once the parameters are set, click Overview and Launch and check the instance configuration.
Click Launch.
Deleting an instance#
Attention
Before deleting an instance, make sure you do not lose any important data. If you need to save a volume copy for future use in K2 Cloud, you can create a snapshot of a volume. If you need a volume or instance copy to boot from and run in your local infrastructure, use the export function.
Go to the Virtual machines section Compute Instances.
Выберите экземпляр в таблице ресурсов и нажмите Удалить.
In the dialog window, confirm the action.
Note
Вместе с экземпляром будут удалены диски и сетевые интерфейсы, для которых задан флаг Удалить с экземпляром, а также все его теги.
Connecting to an instance#
Getting the console output#
Чтобы получить информацию об актуальном состоянии процесса запуска экземпляра или получить пароль:
Go to the Virtual machines section Compute Instances.
Найдите экземпляр в таблице ресурсов и нажмите на его идентификатор для перехода на страницу экземпляра.
На вкладке Информация нажмите Получить вывод.
Accessing the remote console#
В K2 Cloud вы можете подключиться к экземпляру с помощью удалённой консоли вне зависимости от состояния сети и наличия внешнего IP-адреса. Чтобы открыть консоль для удалённого управления экземпляром:
Go to the Virtual machines section Compute Instances.
Найдите экземпляр в таблице ресурсов и нажмите на его идентификатор для перехода на страницу экземпляра.
In the Information tab, click Open console.
В правом верхнем углу консоли управления для удобства работы пользователя расположены дополнительные кнопки:
— click this button to open virtual keyboard.
— clicking this button has the same effect as pressing Ctrl + Alt + Delete on a keyboard.
Enabling access to the remote console#
You can grant any K2 Cloud user with a remote access to the instance.
Go to the Virtual machines section Compute Instances.
Найдите экземпляр в таблице ресурсов и нажмите на его идентификатор для перехода на страницу экземпляра.
На вкладке Информация нажмите Предоставить доступ.
In the dialog window, set the following parameters:
email — адрес электронной почты пользователя;
длительность — срок, на который предоставляется доступ.
После задания всех необходимых параметров нажмите Предоставить доступ.
На указанный адрес электронной почты будет отправлена ссылка с доступом к удалённой консоли.
Important
Access to the remote console can only be granted to the users that have user account in cloud.
Other methods#
You can read about other ways to connect to an instance in Instructions section of documentation.
Actions on instances#
Rebooting an instance#
Перезагрузка экземпляра равнозначна перезагрузке операционной системы. В большинстве случаев перезагрузка экземпляра занимает всего несколько минут. Чтобы перезагрузить экземпляр с корректной остановкой всех сервисов:
Go to the Virtual machines section Compute Instances.
Выберите экземпляр в таблице ресурсов.
Нажмите Перезагрузить.
Подтвердите перезагрузку экземпляра.
Activating hibernation#
Important
We do not guarantee that an instance without a proper preconfiguration will enter the hibernation mode after clicking the Hibernate button.
Hibernation is a state in which the memory content of an instance, applications, and processes is saved to the local volume of the instance before it enters the stopped state. It differs from stopping an instance as follows:
To hibernate an instance, its operating system must be correctly configured;
In the hibernation mode, instances save memory and application states that they had when hibernation was initiated;
Hibernation can be used for instance pre-warming if the instance or application takes a long time to boot.
When you hibernate a correctly configured instance, K2 Cloud signals the OS to perform hibernation. To start hibernation, the guest OS uses an installed QEMU Guest Agent. The cloud communicates with the agent and sends it the appropriate command, where thereafter QEMU Guest Agent prompts the OS to enter the hibernation mode. In this mode, the OS saves the memory content of the instance to a volume.
Important
Please note that the volume size must be larger than the RAM size of the instance.
Attention
We do not recommend resizing the volume or changing the type of hibernated instance. Otherwise, the OS will boot normally, and the saved VM memory state will be ignored.
When you start this instance again, it will enter the Pending state, the memory content will be downloaded from the volume, and the states of processes and applications will be restored.
How fast an instant enters/exits the hibernation mode depends on the volume performance. To accelerate the process, you can use higher-performance volume types, such as gp2: Universal (SSD) and io2: Maximum (SSD).
Using hibernation mode reduces your cloud cost during instance suspension periods since the payment is only charged for storing its volumes and Elastic IP.
Чтобы перевести экземпляр в режим гибернации:
Go to the Virtual machines section Compute Instances.
Выберите экземпляр в таблице ресурсов.
Нажмите Гибернация.
Подтвердите перевод экземпляра в режим гибернации.
Stopping an instance#
Go to the Virtual machines section Compute Instances.
Выберите экземпляр в таблице ресурсов.
Нажмите Выключить.
Подтвердите выключение экземпляра.
Important
Если ОС экземпляра не завершает работу в течение нескольких минут, выполните принудительное завершение работы, аналогичное отключению источника питания сервера, нажмите Выключить (принудительно).
Some instance parameters can only be changed when it is stopped.
Creating an image#
Образ можно создавать как из выключенного, так и из работающего экземпляра. Чтобы создать образ экземпляра, из которого в дальнейшем можно будет создавать новые экземпляры с данными параметрами:
Go to the Virtual machines section Compute Instances.
Выберите экземпляр в таблице ресурсов и нажмите Создать образ.
В открывшемся окне укажите имя и описание образа.
Если необходимо назначить дополнительные теги, перейдите на следующий шаг, нажав Добавить теги. Укажите ключ тега и его значение.
After setting all the required parameters, click Create.
An Image is created in two steps. First, snapshots of all attached volumes are taken simultaneously. This takes a fraction of a second and does not block the running instance.
In the second step, snapshots are written in parallel to object storage. The duration of this stage depends on the maximum amount of data on the volumes and may take a long time. All this time, the image will be in the pending status.
The instance can be restarted, stopped or even deleted without waiting for the second image creation stage to complete. But you can create another image from the instance only after the image creation process is complete and the image status changes to Available. The current image status can, for example, be viewed on its page.
You can find the image you have made Virtual machines Storage Images.
Exporting an instance#
Important
This action is available only for an instance in the Stopped status.
Important
You need to create a bucket in the Object storage section before exporting an instance.
Чтобы экспортировать экземпляр в бакет:
Go to the Virtual machines section Compute Instances.
Выберите экземпляр в таблице ресурсов и нажмите Экспортировать.
In the dialog window, set the following parameters:
prefix;
формат для экспорта;
description;
бакет, в который будет экспортирован экземпляр.
Если вы хотите получить оповещение о завершении процесса экспорта, выберите соответствующую опцию и укажите адрес электронной почты.
После задания всех необходимых параметров нажмите Экспортировать.
Экспорт экземпляра займёт некоторое время, после этого образ экземпляра будет доступен в Объектном хранилище. Подробнее ознакомиться с данной функциональностью можно на странице документации Импорт/Экспорт.
Attach an instance to the Auto Scaling group#
You can attach one or more instances to an existing Auto Scaling group.
Changing instance parameters#
After the instance starts successfully, you can make changes to it. Below are some parameters you can change to suit your needs.
Note
Right-clicking on the selected instance in the table opens the context menu for instance management.
Changing the instance type#
Important
This action is available only for an instance in the Stopped status.
You can change the instance type if it does not suite your workload, it. To do this, go to the instance page, navigate to the Information tab, and edit the Instance type field.
All instance types are grouped and ordered by family. You can choose the desired combination of computing power and memory size and optimize your instance for specific tasks or business needs.
Associate/disassociate an Elastic IP address with/from an instance#
Important
An Elastic IP can be associated with the instance only if the primary interface was created in a subnet and if the VPC has an attached internet gateway.
Чтобы назначить экземпляру публичный адрес из списка выделенных IP-адресов:
Go to the Virtual machines section Compute Instances.
Выберите экземпляр в таблице ресурсов.
Нажмите Назначить Elastic IP.
Вы также можете назначить Elastic IP на странице экземпляра. Адрес будет назначен основному (primary) интерфейсу экземпляра.
Note
Once the Elastic IP is associated, the network interface becomes available at the specified address within a minute.
Чтобы отсоединить назначенный публичный IP-адрес от основного интерфейса экземпляра и сделать адрес доступным для использования:
Go to the Virtual machines section Compute Instances.
Выберите экземпляр в таблице ресурсов.
Нажмите Освободить Elastic IP.
Подтвердите отсоединение Elastic IP от сетевого интерфейса.
Вы также можете отсоединить назначенный Elastic IP от основного интерфейса экземпляра на странице экземпляра.
To assign a different Elastic IP to an instance, first release the assigned IP address from the primary interface.
How to associate/disassociate an Elastic IP with/from an arbitrary instance interface, is described below.
Changing the SSH key#
Important
This operation adds a new key each time a key is changed but old key is not removed. Reboot an instance for changes to take effect.
Чтобы назначить экземпляру новый SSH-ключ:
Go to the Virtual machines section Compute Instances.
Найдите экземпляр в таблице ресурсов и нажмите на его идентификатор для перехода на страницу экземпляра.
На вкладке Информация отредактируйте поле SSH-ключ.
Changing user data#
Чтобы изменить пользовательские данные экземпляра после его создания:
Go to the Virtual machines section Compute Instances.
Найдите экземпляр в таблице ресурсов и нажмите на его идентификатор для перехода на страницу экземпляра.
На вкладке Информация отредактируйте поле Пользовательские данные.
Подробная информация приведена в разделе документации Instance Metadata API.
Attaching/detaching network interfaces#
Instances connect to subnets/switches via network interfaces. You can manage interfaces in the subsection Network Interfaces or via API.
Чтобы присоединить сетевой интерфейс к экземпляру:
Go to the Virtual machines section Compute Instances.
Выберите экземпляр в таблице ресурсов.
Нажмите Присоединить сетевой интерфейс.
Либо перейдите на страницу экземпляра, откройте вкладку Информация или Сеть и безопасность и нажмите Присоединить сетевой интерфейс. Интерфейс может быть присоединён только к одному экземпляру в один момент времени.
The following restrictions apply to attaching network interfaces:
multiple interfaces may not be attached to the same instance if they belong to the same subnet or switch;
if the primary network interface of an instance is a virtual switch network interface, then a subnet interface may not be attached to the instance;
up to 16 network interfaces (including a primary interface) may be attached to an instance;
attached interfaces should be in the same availability zone and belong to the same VPC as the instance itself.
To ensure proper operation of the attached interfaces, we recommend performing a minimum configuration of the interfaces or using K2 Cloud images. In these images interfaces are configured automatically. Please see Configure the attached interfaces.
Чтобы отсоединить сетевой интерфейс от экземпляра:
Go to the Virtual machines section Compute Instances.
Выберите экземпляр в таблице ресурсов.
Нажмите Отсоединить сетевой интерфейс.
Configure hot attachment/detachment of network interfaces#
Interfaces can be attached to/detached from both stopped and running instances. All official K2 Cloud images support hot attachment/detachment of interfaces.
The list of Linux distributions that we have tested to support “hot” attachment/detachment of network interfaces:
CentOS/RHEL/OEL 6/7
Ubuntu ≥ 12.04
Debian ≥ 7
Fedora ≥ 19
If you use CentOS/RHEL/OEL 5.x or Ubuntu 10.x, please download the acpiphp kernel module and add it to the autoload.
This functionality is not guaranteed for instances launched from other images.
If you use other Linux distributions, then make sure the kernel is compiled with HOTPLUG_PCI_ACPI support:
[root@host ~]# grep 'CONFIG_HOTPLUG_PCI_ACPI=' /boot/config-`uname -r`
CONFIG_HOTPLUG_PCI_ACPI=y
If the command output is CONFIG_HOTPLUG_PCI_ACPI=y, it means that “hot” attachment/detachment of network interfaces are supported by this operating system “out of box”.
If the result of the command CONFIG_HOTPLUG_PCI_ACPI = m, then hot attach/detach of network interfaces requires downloading acpiphp or pci_hotplug module, depending on OS.
If the command output is a blank line, then the kernel does not support “hot” attachment/detachment of network interfaces.
Attention
If you detach a network interface from an instance and the instance does not support “hot” attachment/detachment of PCI devices at the OS level, the interface will remain in the Detaching internal state until the instance is stopped.
The cloud will return an error to subsequent attempts of hot attachment/detachment of this network interface.
Change the primary network interface#
Important
Сменить основной сетевой интерфейс можно, только когда экземпляр выключен.
If you need to move an instance to another subnet or VPC, or from non-VPC to VPC, change the primary network interface of the instance. To do this, you need to have an unattached network interface in the target subnet or VPC. If there is no such interface, create it first. If necessary, assign the new interface an internal IP address of your choice from the target network.
The network interface to be used instead of the primary one should be:
in the same availability zone as the source one;
created in a subnet;
not attached to any instance.
Note
If you are going to move an instance to another VPC, it should not have any other interfaces in the subnet other than the primary one.
To change a primary network interface:
Go to the Virtual machines section Compute Instances.
Выберите экземпляр в таблице и нажмите Изменить основной сетевой интерфейс. Если эта кнопка не отображается, то откройте меню дополнительных действий (Eщё). Либо вы можете перейти на страницу экземпляра и открыть вкладку Информация или Сеть и безопасность.
In the dialog window, select the required interface from the list.
Click Change to confirm the change of the primary interface.
Note
Primary interface replacement does not include the transfer of its assigned Elastic IP. If you want the instance to inherit the old Elastic IP, then first disassociate it from the old primary interface and then manually assign it to the new one.
Associate/disassociate an Elastic IP address to/from the network interface#
Important
An Elastic IP can be associated only if the network interface was created in a subnet and if the VPC has an attached internet gateway.
Чтобы назначить публичный IP-адрес произвольному интерфейсу экземпляра:
Go to the Virtual machines section Compute Instances.
Найдите экземпляр в таблице ресурсов и нажмите на его идентификатор для перехода на страницу экземпляра.
На вкладке Сеть и безопасность выберите нужный интерфейс из списка и нажмите Назначить Elastic IP.
В открывшемся окне выберите нужный IP-адрес из списка и нажмите Назначить.
Note
Once the Elastic IP is associated, the network interface becomes available at the specified address within a minute.
Чтобы отсоединить назначенный публичный IP-адрес от произвольного интерфейса экземпляра:
Go to the Virtual machines section Compute Instances.
Найдите экземпляр в таблице ресурсов и нажмите на его идентификатор для перехода на страницу экземпляра.
На вкладке Сеть и безопасность выберите нужный интерфейс из списка и нажмите Освободить Elastic IP.
Подтвердите отсоединение Elastic IP от интерфейса.
To assign a different Elastic IP to a network interface, first release the associated IP address from the interface.
Enable/disable RAM monitoring#
RAM monitoring is only available for Linux instances with CloudWatch agent installed (for details, see).
To enable/disable RAM monitoring:
Go to the Virtual machines section Compute Instances.
Найдите экземпляр в таблице ресурсов и нажмите на его идентификатор для перехода на страницу экземпляра.
Move the RAM monitoring switch to the desired position in the Information tab.
Changing security groups#
Important
This action is allowed only for the network interface created in a subnet.
Чтобы изменить список групп безопасности, назначенных на сетевой интерфейс:
Go to the Virtual machines section Compute Instances.
Найдите экземпляр в таблице ресурсов и нажмите на его идентификатор для перехода на страницу экземпляра.
На вкладке Сеть и безопасность выберите нужный интерфейс из списка и нажмите Изменить группы безопасности.
В открывшемся окне удалите ненужные группы безопасности, выберите необходимые группы из списка и нажмите Изменить.
Note
If source/destination check (source-dest-check) is disabled on the selected interface and at least one of the added security groups is a source in the inbound rules of this or any other group, then you cannot associate such security groups with the network interface.
Change placement group#
Important
This action is available only for an instance in the Stopped status.
Чтобы перевести экземпляр в другую группу размещения:
Go to the Virtual machines section Compute Instances.
Выберите экземпляр в таблице ресурсов и нажмите Изменить размещение.
В открывшемся окне выберите группу размещения и нажмите Изменить.
Либо вы можете перейти на страницу экземпляра и на вкладке Информация отредактировать поле Группа размещения.
Operations with volumes#
The Volumes tab contains a list of all volumes attached to the instance. Each volume has a set of parameters:
ID — the unique volume ID.
State — the information on the volume status.
Volumes – the sequential number of the volume in this instance.
Size — the maximum amount of data that a volume can hold.
Name tag — a tag with the Name key and a value set by the user.
Volume type.
IOPS — the volume performance (IOPS).
To view volume details in the Volumes subsection, go to the instance page and click the link with its unique ID in the Volumes tab.
Attaching/detaching a volume#
Attach a volume#
Important
A volume can be attached to an instance if they are in the same availability zone.
Only volumes with Available status (which aren’t attached to any instance) can be attached to an instance.
Attention
Up to 16 volumes can be attached to an instance. However, you can attach maximum four volumes to instances of the hvm-legacy virtualization type.
To attach one more volume to an instance:
Go to the Virtual machines section Instances.
In the resource table, find the instance to which you need to attach a volume and click the instance ID to go to its page.
Open the Volumes tab and click Attach.
In the window that opens, select the desired volume from the list.
If there are no available volumes or their characteristics do not match your needs, you can create a volume with the required parameters right in the volume attachment dialog box.
Click Create volume.
Enter Name tag (optional).
Select the volume size.
Select the volume type.
Set IOPS (only for io2 volumes).
Confirm the action by clicking Attach (for the existing volume) or Create and attach (for the newly created volume).
Detach a volume#
Important
You can detach only non-boot volumes from the instance.
To detach a volume from an instance:
Go to the Virtual machines section Instances.
Найдите в таблице ресурсов экземпляр, от которого необходимо отсоединить диск, и нажмите на его идентификатор для перехода на страницу экземпляра.
Open the Volumes tab, select the volume to be detached and click Detach.
Подтвердите отсоединение диска от экземпляра.
Changing the boot device#
Important
You can only change the boot device when the instance is in the Stopped status.
Чтобы изменить загрузочное устройство:
Go to the Virtual machines section Compute Instances.
Найдите экземпляр в таблице ресурсов и нажмите на его идентификатор для перехода на страницу экземпляра.
На вкладке Информация отредактируйте поле Загрузочное устройство.
В качестве загрузочного устройства вы можете выбрать загрузочный диск (disk1) или загрузочное меню (menu).
Если образ, из которого был создан экземпляр, поддерживает CD-ROM, то в этом случае возможен также выбор CD-ROM (cd-rom).
Changing the boot volume#
Before changing the boot volume, you should first attach the volume you want to use as a boot one.
Important
You can only change the boot volume when the instance is in the Stopped status.
Go to the Virtual machines section Compute Instances.
Найдите экземпляр в таблице ресурсов и нажмите на его идентификатор для перехода на страницу экземпляра.
На вкладке Диски выберите диск, который вы хотите сделать загрузочным.
Click Set as boot device.
Confirm the action.
Creating a snapshot#
В любой момент вы можете создать моментальный снимок диска, присоединённого к экземпляру. Чтобы получить снимок диска и в дальнейшем использовать его в качестве образа для новых дисков или резервного копирования данных:
Note
Для регулярного резервного копирования данных рекомендуем использовать сервис Резервное копирование.
Go to the Virtual machines section Compute Instances.
Найдите экземпляр в таблице ресурсов и нажмите на его идентификатор для перехода на страницу экземпляра.
На вкладке Диски выберите диск, снимок которого хотите создать.
Click Create snapshot.
В открывшемся окне вы можете задать тег Name и описание снимка диска.
Если необходимо назначить дополнительные теги, перейдите на следующий шаг, нажав Добавить теги. Укажите ключ тега и его значение.
After setting all the required parameters, click Create.
Snapshot is created in two steps. At the first step, a snapshot of the volume state is created. This is a sub-second operation, which does not block volume reads/writes.
At the second step, the snapshot content is transferred to object storage. It can take a long time depending on the amount of data; meanwhile, the volume snapshot will be in the Creating state. The volume can be attached, detached, or deleted without waiting for this step to complete. You can only create another snapshot of the same volume after the snapshot has been fully transferred to the object storage and the snapshot state has changed to Completed. You can monitor the progress on the volume snapshot page.
Important
For all company projects and users, you can simultaneously create a maximum of 16 volume snapshots.
Important
To ensure volume snapshot consistency of a volume attached to a running instance, stop the instance or flush the cache and suspend writing to the volume.
Create a volume version#
To save the volume content at a certain point in time and then quickly restore it, you can create a volume version, which creates a volume snapshot. However, the snapshot content is not sent to another storage, so the version is created in a fraction of a second.
Чтобы создать версию диска:
Go to the Virtual machines section Compute Instances.
Найдите экземпляр в таблице ресурсов и нажмите на его идентификатор для перехода на страницу экземпляра.
На вкладке Диски выберите диск, версию которого хотите создать.
Нажмите Создать версию.
В открывшемся окне вы можете задать тег Name.
Если необходимо назначить дополнительные теги, перейдите на следующий шаг, нажав Добавить теги. Укажите ключ тега и его значение.
After setting all the required parameters, click Create.
Вы можете также создать версию диска в подразделе Диски или на странице диска. Об использовании версий дисков, в частности, как восстановить диск из имеющейся версии, читайте в документации на версии дисков.
Important
As with volume snapshots, to ensure version consistency of a volume attached to a running instance, stop the instance or flush the cache and suspend writing to the volume.
Instance information#
Общую информацию об экземплярах можно посмотреть таблице ресурсов в разделе Виртуальные машины Вычислительные ресурсы Экземпляры. Для просмотра сводной таблицы всех экземпляров в проекте выберите Все VPC в фильтре VPC. Для отображения экземпляров из конкретного VPC выберите нужное VPC в фильтре.
To go to the page of a particular instance, click its ID in the resource table in the Instances subsection. To facilitate the instance search, select its relevant VPC in the VPC filter or use the table search.
The Information tab provides the detailed information about the instance:
state;
instance name (Name tag);
instance image;
instance type;
SSH-key;
DNS name;
availability zone;
placement group;
placement type;
dedicated host (only for instances running on dedicated hosts);
affinity with the host (only for instances running on dedicated hosts);
virtualization type;
VPC;
network interfaces;
security groups;
network the primary network interface is attached to;
Elastic IP;
Private IP;
boot device;
boot menu status;
user data.
Here you can:
change the instance name (Name tag);
The Volumes tab displays a table with information about volumes attached to the instance:
volume ID;
volume name;
state;
size;
volume type;
volume IOPS performance;
Delete with instance option value;
device type: boot or additional volume.
The sequence and scope of the displayed data may vary depending on the table settings.
Here, you can perform all basic operations and actions with volumes.
The Network and security tab contains a table with details of the network interfaces attached to the instance and security groups assigned to the network interfaces of the instance:
network interface ID;
network interface description;
subnet ID;
Elastic IP;
Private IP;
assigned security group IDs.
Here you can:
Metrics tab shows charts with instance metrics:
CPU utilization;
Network activity;
volumes utilization.
You can select the displayed statistics and set the period of time for which it is displayed. To automatically update the graph, enable Auto-refresh; to update it manually, click Refresh.
The Alarms tab contains a table with information about alarms configured for this instance:
state;
alarm name;
alarm trigger condition.
Here you can:
delete existing alarms with Delete button.
The Tags tab displays all tags assigned to the intance. You can add new, modify existing, and delete no-longer-needed tags.