Adding the Yandex Compute VM hostprovider
This topic shows how to add the Yandex Compute VM hostprovider, which allows to create multiple virtual machines in the Yandex.Cloud.
Before adding the Yandex Compute VM hostprovider, make sure that:
The Folder exists in the Yandex.Cloud.
The subnet is created in the Yandex.Cloud.
ADCM can establish the connection to the specified subnet in the Yandex.Cloud.
The user that creates the virtual machine has all necessary rights.
If automatic Red Hat registration is required for virtual machines using RHEL, you should have:
A subscription to Red Hat services and the corresponding organization ID.
A configured Red Hat activation key.
In comparison with the Yandex.Cloud console, the Yandex Compute VM hostprovider does not support the configuring of:
Static IP addresses.
Additional network adapters.
A typical installation sequence for the Yandex Compute VM hostprovider includes the following steps.
Hostprovider distributions for ADCM come in bundles. Regarding the Yandex Compute VM hostprovider, a bundle is a regular archive that includes a description and logic to interact with the Yandex.Cloud.
The steps for downloading a bundle are given below:
Go to the Arenadata Cluster Manager product website and click Download.Switching to the Arenadata Cluster Manager downloading page
Another way — go to the Arenadata App Store website and choose Arenadata Cluster Manager.Switching to the Arenadata Cluster Manager downloading page from App StoreSwitching to the Arenadata Cluster Manager downloading page from App Store
The opened page displays a brief description of the product, links to its distribution components, and information about the last release: release date, release type, minor version, and links to the Usage License and Release Notes. Choose the versions of ADCM and operation system in the corresponding fields and expand the Arenadata ADCM Infrastructure Bundles drop-down list. The bundle of the Yandex Compute VM hostprovider is called Yandex Compute VM Provider Bundle.Starting downloading processStarting downloading process
In the opened application form, fill in all mandatory fields. After the data being sent, a browser starts downloading the selected bundle.An application form for downloading the productAn application form for downloading the product
To upload a bundle to ADCM, follow these steps in the ADCM web interface:
Open the BUNDLES tab and click Upload bundle.
Select the downloaded bundle in the Open File Dialog.Switching to uploading a bundleSwitching to uploading a bundle
As a result of the performed actions, the uploaded bundle is displayed at the BUNDLES tab.The result of successful uploading a bundle
To add a new hostprovider to ADCM on the base of the uploaded bundle, follow these steps in the ADCM web interface:
Open the HOSTPROVIDERS tab and click Create provider.Creating a new hostprovider
In the opened window:
Filling in the new hostprovider parameters
Select the uploaded bundle in the Bundle field.
Select the desired version of the bundle in the Version field. Several versions become available in the case of different versions of the same bundle being uploaded. By default, the latest version is displayed.
Enter the hostprovider name in the Hostprovider name field.
Enter the hostprovider description in the Description field, if necessary.
As a result of the performed actions, the created hostprovider is displayed at the HOSTPROVIDERS tab.The result of successful adding a hostprovider
In order to configure the access to the cloud, perform the following actions:
Open the HOSTPROVIDERS tab, find the row with a desired hostprovider, and click the gear icon in the Config column.Switching to configuring the hostprovider
In the next window set the Advanced flag, fill in the necessary parameters, and click Save.Configuring the hostprovider
The assignment of parameters is listed below.
Configuration parameters UI pane Parameter Mandatory Description
Service account credentials
Static access keys, that can be obtained for the service account according to the Yandex.Cloud documentation. The
Service account credentialsfield is incompatible with
OAuth, you should use only one of these fields for authentication. Pay attention, that static keys should be transformed into the JSON format before being inserted into the field
A custom endpoint, that is used to connect to a private Yandex.Cloud installation
The root certificates, that are used to connect to a private Yandex.Cloud installation
An OAuth token, that can be obtained according to the Yandex.Cloud documentation. The
OAuthfield is incompatible with
Service account credentials, you should use only one of these fields for authentication
A target folder for new virtual machines, for example
b1gotqhf08176hh183dn. Can be copied from the Id column in the folders list of the Yandex.Cloud
A target subnet for new virtual machines, for example
b0cccgrn656k0nixi92a. To get the
Subnet IDvalue, open the Virtual Private Cloud service in the Yandex.Cloud console, click on the desired network in the Cloud networks section, and copy the value of the Id column from the row that contains the desired subnet in the list of subnets that opens
A target availability zone for new virtual machines, for example
ru-central1-c. Every zone corresponds to the specific data center . To get the
Zonevalue, open the Virtual Private Cloud service in the Yandex.Cloud console, click on the desired network in the Cloud networks section, and copy the value of the Zone column from the row that contains the desired subnet in the list of subnets that opens
A list of OpenSSH keys with the
user@hostnamedata in the end. When adding virtual machines, the users list is parsed from this field. Every user is created with the corresponding key
Active operations limit timeout
A timeout activated when the quota of simultaneously performed operations is exceeded (resulting in errors returned by the Yandex.Cloud gPRC). If empty, the timeout is not activated. If
0, the waiting time is unlimited. Any positive integer in the field equals the waiting time, during which the operation should move from the queue to the execution stage. Measured in seconds
The default labels that are used for all created VMs. Should be specified in the
key:valueformat. The labels, specified when adding VMs, have a higher priority compared to the labels, specified for the hostprovider
The organization ID that is provided at subscribing to Red Hat services. This ID is available in the Red Hat client portal. Should be filled in simultaneously with the
Activation keyfield, if automatic Red Hat registration is required for virtual machines using RHEL. The field is available in the 2.15 bundle version or later
An activation key that is configured in the Red Hat client portal. Should be filled in simultaneously with the
Organization IDfield, if automatic Red Hat registration is required for virtual machines using RHEL. The field is available in the 2.15 bundle version or later
Return to the HOSTPROVIDERS tab. As a result, the orange exclamation mark stops being displayed in the Actions column. The actions available for the configured hostprovider can be opened by clicking the icon in the Actions column.The result of successful hostprovider configuring