Skip to content

Commit

Permalink
Merge branch 'yandex-cloud:master' into master
Browse files Browse the repository at this point in the history
maqmm authored Oct 31, 2024

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
2 parents af8a7d4 + 0a24737 commit 57998b5
Showing 1,876 changed files with 110,494 additions and 31,431 deletions.
94 changes: 94 additions & 0 deletions en/_assets/billing/billing-cycle-business-credit.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed en/_assets/compute/connect-sa.png
Binary file not shown.
3 changes: 3 additions & 0 deletions en/_assets/console-icons/chevrons-expand-up-right.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 3 additions & 0 deletions en/_assets/console-icons/circle-plus-fill.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 3 additions & 0 deletions en/_assets/console-icons/cubes-3.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
1 change: 1 addition & 0 deletions en/_assets/console-icons/handset-arrow-in.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 3 additions & 0 deletions en/_assets/console-icons/stop.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 3 additions & 0 deletions en/_assets/console-icons/triangle-right.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified en/_assets/datalens/concepts/widget.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified en/_assets/datalens/solution-03/01-metrica-list.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified en/_assets/datalens/solution-03/10-delete-charts1.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified en/_assets/datalens/solution-03/11-replace-charts.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified en/_assets/datalens/solution-03/12-delete-charts2.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified en/_assets/datalens/solution-03/14-edit-chart.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified en/_assets/datalens/solution-03/15-choose-pie.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified en/_assets/datalens/solution-03/16-save-chart.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified en/_assets/datalens/solution-03/17-refresh-dashboard.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
86 changes: 86 additions & 0 deletions en/_assets/overview/legal-entity-trial-period.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
1 change: 1 addition & 0 deletions en/_assets/storage/bucket.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
1 change: 1 addition & 0 deletions en/_assets/storage/link.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
1 change: 1 addition & 0 deletions en/_assets/storage/upload.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
@@ -20,7 +20,7 @@ Syntax:
|`--name`|<b>`string`</b><br/>Secret name.|
|`--async`|Display information about the operation in progress, without waiting for the operation to complete.|
|`--description`|<b>`string`</b><br/>Version description.|
|`--payload`|<b>`string`</b><br/>YAML or JSON array defining how to change payload from the base version.<br/>Each item of the array must match the format: https://yandex.cloud/ru/docs/lockbox/api-ref/grpc/secret_service#PayloadEntryChange<br/>For instance, to modify the value of "password" entry from the base version payload:<br/>[{"key": "username", "text_value": "alice"}, {"key": "password", "text_value": "p@$$w0rd"}]<br/>the following JSON can be passed:<br/>[{"key": "password", "text_value": "another-p@$$w0rd"}]<br/>so the resulting payload of the newly added version will be:<br/>[{"key": "username", "text_value": "alice"}, {"key": "password", "text_value": "another-p@$$w0rd"}]<br/>To remove the entry pass an item containing only the "key" field, e.g.:<br/>[..., {"key": "the-key-of-the-entry-to-remove"}, ...]<br/>Use - value to pass payload string via stdin.|
|`--payload`|<b>`string`</b><br/>YAML or JSON array defining how to change payload from the base version.<br/>Each item of the array must match the format: https://yandex.cloud/ru/docs/lockbox/api-ref/grpc/Secret/create#yandex.cloud.lockbox.v1.PayloadEntryChange<br/>For instance, to modify the value of "password" entry from the base version payload:<br/>[{"key": "username", "text_value": "alice"}, {"key": "password", "text_value": "p@$$w0rd"}]<br/>the following JSON can be passed:<br/>[{"key": "password", "text_value": "another-p@$$w0rd"}]<br/>so the resulting payload of the newly added version will be:<br/>[{"key": "username", "text_value": "alice"}, {"key": "password", "text_value": "another-p@$$w0rd"}]<br/>To remove the entry pass an item containing only the "key" field, e.g.:<br/>[..., {"key": "the-key-of-the-entry-to-remove"}, ...]<br/>Use - value to pass payload string via stdin.|
|`--base-version-id`|<b>`string`</b><br/>Base version id. By default, the current one is used.|

#### Global Flags
Original file line number Diff line number Diff line change
@@ -21,7 +21,7 @@ Syntax:
|`--labels`|<b>`key=value[,key=value...]`</b><br/>A list of label KEY=VALUE pairs to add. For example, to add two labels named 'foo' and 'bar', both with the value 'baz', use '--labels foo=baz,bar=baz'.|
|`--kms-key-id`|<b>`string`</b><br/>KMS key ID will be used to encrypt the secret payload.|
|`--version-description`|<b>`string`</b><br/>Description of the first version.|
|`--payload`|<b>`string`</b><br/>YAML or JSON array defining the entries of the secret payload.<br/>Each item of the array must match the format: https://yandex.cloud/ru/docs/lockbox/api-ref/grpc/secret_service#PayloadEntryChange<br/>For instance, the following payload JSON defines a payload containing two text value entries:<br/>[{"key": "username", "text_value": "alice"}, {"key": "password", "text_value": "p@$$w0rd"}]<br/>Use - value to pass payload string via stdin.|
|`--payload`|<b>`string`</b><br/>YAML or JSON array defining the entries of the secret payload.<br/>Each item of the array must match the format: https://yandex.cloud/ru/docs/lockbox/api-ref/grpc/Secret/create#yandex.cloud.lockbox.v1.PayloadEntryChange<br/>For instance, the following payload JSON defines a payload containing two text value entries:<br/>[{"key": "username", "text_value": "alice"}, {"key": "password", "text_value": "p@$$w0rd"}]<br/>Use - value to pass payload string via stdin.|
|`--deletion-protection`|Enable deletion protection for the secret.|
|`--async`|Display information about the operation in progress, without waiting for the operation to complete.|

Original file line number Diff line number Diff line change
@@ -18,5 +18,5 @@
1. Make sure the web server returns a list of folders in the `test-server` folder. Open the terminal on your computer and run this command:

```bash
curl -v <VM_public_IP_address>:8080
curl --verbose <VM_public_IP_address>:8080
```
7 changes: 7 additions & 0 deletions en/_includes/backup/baremetal-note.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
{% note info %}

{{ backup-name }} also supports [{{ baremetal-full-name }} server](../../baremetal/concepts/servers.md) backups. For details, see [Connecting a {{ baremetal-name }} server to {{ backup-name }}](../../backup/tutorials/backup-baremetal.md).

_{{ baremetal-name }} will be released at the [Preview stage](../../overview/concepts/launch-stages.md) in Q4 2024._

{% endnote %}
4 changes: 2 additions & 2 deletions en/_includes/backup/operations/full-config.md
Original file line number Diff line number Diff line change
@@ -191,10 +191,10 @@ Attribute sections with multiple nested values.
| `scheduling.backupSets.sinceLastExecTime.delay.type` | Units of time used to set the interval between backups. | <ul><li>`TYPE_UNSPECIFIED`: Not set.</li><li>`SECONDS`: Seconds.</li><li>`MINUTES`: Minutes.</li><li>`HOURS`: Hours.</li><li>`DAYS`: Days.</li><li>`WEEKS`: Weeks.</li><li>`MONTHS`: Months.</li></ul> |
| `scheduling.backupSets.sinceLastExecTime.delay.count` | Duration of the interval between backups in time units set by the `delay.type` attribute. | Integer |
| `scheduling.enabled` | Making scheduled backups. | <ul><li>`true`: Enabled.</li><li>`false`: Disabled.</li></ul> |
| `scheduling.maxParallelBackups` | Maximum number of parallel backups allowed. Unlimited if no value is specified. | Integer |
| `scheduling.maxParallelBackups` | Maximum permissible number of parallel backups. Unlimited if no value is specified. | Integer |
| `scheduling.randMaxDelay.type` | Units of time used to set the maximum delay before running parallel jobs. | <ul><li>`TYPE_UNSPECIFIED`: Not set.</li><li>`SECONDS`: Seconds.</li><li>`MINUTES`: Minutes.</li><li>`HOURS`: Hours.</li><li>`DAYS`: Days.</li><li>`WEEKS`: Weeks.</li><li>`MONTHS`: Months.</li></ul> |
| `scheduling.randMaxDelay.count` | Maximum delay before running parallel jobs in time units set by the `randMaxDelay.type` attribute. The delay is determined randomly but it may not exceed the value set here. | Integer |
| `scheduling.scheme` | Backup schedule scheme. | <ul><li>`SCHEME_UNSPECIFIED`: Not set.</li><li>`SIMPLE`: Simple.</li><li>`ALWAYS_FULL`: Always full.</li><li>`ALWAYS_INCREMENTAL`: Always incremental.</li><li>`WEEKLY_INCREMENTAL`: Weekly: incremental.</li><li>`WEEKLY_FULL_DAILY_INCREMENTAL`: Weekly: full; daily: incremental.</li><li>`CUSTOM`: User-defined.</li><li>`CDP`: Continuous data protection.</li></ul> |
| `scheduling.weeklyBackupDay` | Day of the week to make weekly backups on. | Integer from 1 to 7 |
| `scheduling.weeklyBackupDay` | Day of the week for the weekly backup. | Integer from 1 to 7 |

{% endlist %}
2 changes: 1 addition & 1 deletion en/_includes/billing/billing-account-create-individual.md
Original file line number Diff line number Diff line change
@@ -14,7 +14,7 @@ To create a billing account:

1. If you see a list of available payers in the **{{ ui-key.yacloud_billing_account.create-account-wizard.field_person-id }}** section, you can select one of them or add a new one. To add a payer:

* Select the **{{ ui-key.startrek.ui_components_page-admin_BillingAccountInfo.person-type-invididual }}** payer type and click **{{ ui-key.yacloud_billing_account.cloud-billing-account.label_wizard-next }}**.
* Select the **Individual** payer type and click **{{ ui-key.yacloud_billing_account.cloud-billing-account.label_wizard-next }}**.
* Enter your first and last name.
* (Optional) Enter your middle name and mailing address.
* Click **{{ ui-key.yacloud_billing_account.cloud-billing-account.label_wizard-next }}**.
38 changes: 30 additions & 8 deletions en/_includes/billing/billing-account-create-legal-entities.md
Original file line number Diff line number Diff line change
@@ -2,35 +2,57 @@ To create a billing account:

1. {% include [move-to-billing-step](../../billing/_includes/move-to-billing-step.md) %}

1. Log in to your Yandex ID or Yandex 360 account. If you do not have an account yet, [sign up](https://yandex.ru/support/id/authorization/registration.html) and create an [organization](../../organization/quickstart.md) to work in [{{org-full-name}}]({{link-org-main}}). If you use a social network profile to log in to Yandex, [create a username and password](https://passport.yandex.com/passport?mode=postregistration&create_login=1).
1. Log in to your Yandex ID or Yandex 360 account. If you do not have an account yet, [sign up](https://yandex.ru/support/id/authorization/registration.html) and create an [organization](../../organization/quickstart.md) in [{{ org-full-name }}]({{ link-org-main }}) for you to work in. If using your social network profile to log in to Yandex, [create a username and password](https://passport.yandex.com/passport?mode=postregistration&create_login=1).

1. On the **{{ ui-key.yacloud_billing.billing.title_accounts }}** page, click **Create billing account**. Fill in your information:

* {% include [choose-name-step](../../billing/_includes/choose-name-step.md) %}
* {% include [choose-org-step](../../billing/_includes/choose-org-step.md) %}
* {% include [choose-country-step](../../billing/_includes/choose-country-step.md) %}

{% include [billing-account-payers](../../billing/_includes/billing-account-payers.md) %}
{% include [billing-account-payers](../../billing/_includes/billing-account-payers.md) %}

1. If you see a list of available payers in the **{{ ui-key.yacloud_billing_account.create-account-wizard.field_person-id }}** section, you can select one of them or add a new one.

1. Select the **{{ ui-key.startrek.ui_components_page-admin_BillingAccountInfo.person-type-company }}** payer type.
1. Select the **Legal entity or individual entrepreneur** payer type.

1. Select the **{{ ui-key.yacloud_billing.billing.account.create-new.payment-type_label_invoice }}** payment method.
1. Select the **{{ ui-key.yacloud_billing.billing.account.create-new.payment-type_label_card }}** or **{{ ui-key.yacloud_billing.billing.account.create-new.payment-type_label_invoice }}** payment method. You can [change the payment method](../../billing/operations/change-payment-method.md) any time after creating a billing account.

1. Click **{{ ui-key.yacloud_billing_account.cloud-billing-account.label_wizard-next }}**.

1. If you selected **{{ ui-key.yacloud_billing.billing.account.create-new.payment-type_label_card }}** as a payment method:

1. Enter the legal information of your organization and your contact details.
1. Enter the legal information of your organization and your contact details.

1. Enter your current email address and phone number. Contact details are required not only to reach you, but also to issue payment invoices and send financial documents. If you have already signed up for {{ yandex-cloud }}, check that your contact details are correct.
{% include [contacts-note](contacts-note.md) %}

1. Link your corporate bank card:

{% include [pin-card-data](pin-card-data.md) %}

* Confirm that the card is a corporate one and you are authorized to use it.

* Click **{{ ui-key.yacloud_billing_account.cloud-billing-account.label_wizard-next }}**.

{% include [payment-card-types](payment-card-types-business.md) %}

{% include [yandex-account](payment-card-validation.md) %}

1. Enter your current email address and phone number. Contact details are required not only to reach you, but also to issue payment invoices and send financial documents. If you have already signed up for {{ yandex-cloud }}, check that your contact details are correct.

1. If you selected **{{ ui-key.yacloud_billing.billing.account.create-new.payment-type_label_invoice }}** as a payment method:

1. Enter the legal information of your organization and your contact details.

1. Enter your current email address and phone number. Contact details are required not only to reach you, but also to issue payment invoices and send financial documents. If you have already signed up for {{ yandex-cloud }}, check that your contact details are correct.

1. If this is your first {{ yandex-cloud }} billing account, you are eligible for a [trial period](../../billing/concepts/trial-period.md). After it expires, the access to your resources will be suspended. To resume operation, you will need to switch to the [paid version](../../billing/operations/activate-commercial.md).

1. Click **{{ ui-key.yacloud.common.create }}**.

If you select the **{{ ui-key.yacloud_billing.billing.account.create-new.payment-type_label_invoice }}** payment method or if the payer is a non-resident of Russia and Kazakhstan, further instructions will be emailed to you at the address specified in your Yandex or Yandex 360 account. It may take up to three business days to activate your billing account.

Further instructions will be emailed to you at the address specified in your Yandex or Yandex 360 account. It may take up to three business days to activate your billing account.

Email the following documents to [{{ billing-docs-email }}](mailto:{{ billing-docs-email }}):
* Copy of the minutes or resolution on the appointment of the general director
* [Billing account](../../billing/concepts/billing-account.md#billing-account-id) ID

5 changes: 0 additions & 5 deletions en/_includes/billing/card-business-nonresidents.md

This file was deleted.

2 changes: 1 addition & 1 deletion en/_includes/billing/contract.md
Original file line number Diff line number Diff line change
@@ -1 +1 @@
In {{ yandex-cloud }}, all services are provided under an agreement you enter into by accepting an [offer]({{ billing-oferta-url }}?lang=en) when creating your [billing account](../../billing/concepts/billing-account.md). The agreement does not need to be signed by both parties.
In {{ yandex-cloud }}, all services are provided under an agreement you enter into by accepting an offer when creating your [billing account](../../billing/concepts/billing-account.md). The agreement does not need to be signed by both parties.
5 changes: 5 additions & 0 deletions en/_includes/billing/legal-entity-nonresidents.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{% note info %}

If you are a non-resident of Russia or Kazakhstan, specify the bank details of the legal entity you signed the [agreement](../../billing/concepts/contract.md) with when [creating your billing account](../../billing/operations/create-new-account.md).

{% endnote %}
5 changes: 5 additions & 0 deletions en/_includes/billing/non-residents-functional-access.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{% note info %}

This feature is not available for non-residents of Russia and Kazakhstan.

{% endnote %}
5 changes: 5 additions & 0 deletions en/_includes/billing/payment-card-types-business.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
We accept Mir, Visa, and MasterCard.

* Residents of Russia make payments in RUB and can only use bank cards issued by Russian banks. Customers with tax residency in the Republic of Belarus pay for {{ yandex-cloud }} services in RUB with their Belcard cards issued in the Republic of Belarus or Mir cards issued in the Russian Federation.
* Residents of Kazakhstan make payments in KZT and can only use bank cards issued by non-Russian banks.
* Non-residents of Russia and Kazakhstan make payments in USD and can only use credit or debit cards issued by non-Russian banks.
3 changes: 2 additions & 1 deletion en/_includes/billing/payment-card-types.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,5 @@
We accept Mir, Visa, and MasterCard.

* Residents of Russia make payments in RUB and can only use bank cards issued by Russian banks.
* Residents of Kazakhstan make payments in KZT and can only use bank cards issued by non-Russian banks.
* Residents of Kazakhstan make payments in KZT and can only use bank cards issued by non-Russian banks.
* Non-residents of Russia and Kazakhstan make payments in USD and can only use credit or debit cards issued by non-Russian banks.
1 change: 1 addition & 0 deletions en/_includes/cloud-desktop/access-options.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{{ cloud-desktop-name }} leverages [{{ iam-full-name }} roles](../../cloud-desktop/security/index.md) and [access control lists (ACL)](../../cloud-desktop/concepts/acl.md) to manage access. [This example](../../cloud-desktop/concepts/acl.md#example) shows how access control works in {{ cloud-desktop-name }}.
12 changes: 6 additions & 6 deletions en/_includes/cloud-desktop/limits.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
#### Quotas {#quotas}

| Type of limit | Value |
Type of limit | Value
----- | -----
| Maximum number of desktops per cloud | 5 |
| Maximum total number of vCPUs per cloud | 10 |
| Maximum total amount of RAM per cloud | 20 GB |
| Maximum total HDD storage capacity per cloud | 500 GB |
| Maximum total SSD storage capacity per cloud | 500 GB |
Maximum number of desktops per cloud | 5
Maximum total number of vCPUs per cloud | 10
Maximum total amount of RAM per cloud | 20 GB
Maximum total HDD space per cloud | 500 GB
Maximum total SSD space per cloud | 500 GB
27 changes: 27 additions & 0 deletions en/_includes/cns-limits.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
#### Quotas {#quotas}

**Type of limit** | **Value**
----- | -----
Maximum message size per [push notification](../notifications/concepts/push.md) | 4 KB

#### Limits {#limits}

**Type of limit** | **Value**
----- | -----
Maximum number of [push notification channels](../notifications/concepts/push.md#mobile-channel) per cloud | 20
Maximum number of [SMS notification](../notifications/concepts/sms.md) channels per cloud | 10
Maximum number of SMS notification channels with a [shared sender ](../notifications/concepts/sms.md) per cloud | 1
Maximum number of SMS notification channels with an [individual sender](../notifications/concepts/sms.md#individual-sender) per cloud | 10
Maximum number of [test phone numbers](../notifications/concepts/sms.md#sandbox) per SMS notification channel | 10
Maximum number of SMS messages per cloud^1^ | 100 per month
Maximum message size per push notification | 200 KB
Maximum SMS message length | 1,600 characters (10 segments)
Maximum name length for a push notification channel | 40 characters
Maximum length for user data (`CustomUserData`) per mobile endpoint | 256 characters
Maximum length for a device ID per mobile endpoint | 256 characters
Maximum rate of requests to create or update notification channel attributes per cloud | 30 requests per second
Maximum rate of requests to send an SMS message per cloud | 20 requests per second
Maximum number of SMS messages to verify one test number | 5 per day for one number
Maximum number of SMS messages to verify test numbers per cloud | 20 per day

^1^ Moving forward, the limit on the maximum number of SMS messages per cloud will become a [quota](#quotas). You will be able to increase it by contacting support.
2 changes: 1 addition & 1 deletion en/_includes/code-assistant/auto-manual-modes.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
{{ ca-name }} analyzes your code context and provides the following types of suggestions:
* Automatic.
* Upon user request (use **Ctrl** + **Space** or **Ctrl** + **Enter**).
* User-triggered (**Ctrl** + **Space**). In Visual Studio Code, you can also use **Ctrl** + **Enter**.
1 change: 1 addition & 0 deletions en/_includes/code-assistant/unable-to-download.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
If you cannot download it for any reason, contact your system administrator so that they open network access to {{ yandex-cloud }} resources.
3 changes: 0 additions & 3 deletions en/_includes/compute/backup-info.md

This file was deleted.

126 changes: 43 additions & 83 deletions en/_includes/compute/create-from-snapshot.md
Original file line number Diff line number Diff line change
@@ -3,109 +3,69 @@
- Management console {#console}


1. In the [management console]({{ link-console-main }}), select the folder to create the virtual machine in.
1. In the list of services, select **{{ ui-key.yacloud.iam.folder.dashboard.label_compute }}**.
1. At the top right, click **{{ ui-key.yacloud.compute.instances.button_create }}**.
1. Under **{{ ui-key.yacloud.compute.instances.create.section_base }}**:

* Enter a name and description for the VM. The naming requirements are as follows:

{% include [name-format](../name-format.md) %}

{% include [name-fqdn](../compute/name-fqdn.md) %}

* Select an [availability zone](../../overview/concepts/geo-scope.md) to put your virtual machine in.

1. Under **{{ ui-key.yacloud.compute.instances.create.section_image }}**, choose a snapshot:

* Go to the **{{ ui-key.yacloud.compute.instances.create.image_value_custom_new }}** tab and click **{{ ui-key.yacloud.common.select }}**.
* In the window that opens, go to the **{{ ui-key.yacloud.compute.instances.create-disk.value_source-snapshot }}** tab.
* Select a disk snapshot from the list and click **{{ ui-key.yacloud.common.apply }}**.


1. {% include [encryption-section-boot](encryption-section-boot.md) %}


1. Under **{{ ui-key.yacloud.compute.instances.create.section_storages_ru }}**, [add a disk](../../compute/operations/vm-create/create-from-disks.md):

* Click **{{ ui-key.yacloud.compute.component.instance-storage-dialog.button_add-disk }}**.
* Enter the disk name.
1. In the [management console]({{ link-console-main }}), select the [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) to create your VM in.
1. In the list of services, select **{{ ui-key.yacloud.iam.folder.dashboard.label_compute }}**.
1. In the left-hand panel, select ![image](../../_assets/console-icons/server.svg) **{{ ui-key.yacloud.compute.switch_instances }}**.
1. Click **{{ ui-key.yacloud.compute.instances.button_create }}**.
1. Under **{{ ui-key.yacloud.compute.instances.create.section_image }}**:

* Go to the **{{ ui-key.yacloud.compute.instances.create.image_value_custom_new }}** tab.
* Click ![image](../../_assets/console-icons/pencil.svg), and, in the window that opens, select **{{ ui-key.yacloud.common.create-new }}**.
* In the **{{ ui-key.yacloud.compute.instances.create-disk.field_source }}** field, select `{{ ui-key.yacloud.compute.instances.create-disk.value_source-snapshot }}` and then select the disk snapshot you need from the list below. Use filters if you need to.
* Enter a name for the new boot disk.
* Select the [disk type](../../compute/concepts/disk.md#disks_types).
* Specify the required block size.
* Specify the required disk size.


* {% include [encryption-section-secondary](encryption-section-secondary.md) %}


* (Optional) Enable the **{{ ui-key.yacloud.compute.field_disk-autodelete }}** option if you need to automatically delete the disk when deleting the VM it will be attached to.
* Select `{{ ui-key.yacloud.compute.instances.create-disk.value_source-snapshot }}` as content.
* Click **{{ ui-key.yacloud.compute.instances.create-disk.button_create }}**.


1. (Optional) Under **{{ ui-key.yacloud.compute.instances.create.section_storages_ru }}**, select the **{{ ui-key.yacloud.compute.nfs.label_filesystems }}** tab and attach the [file storage](../../compute/concepts/filesystem.md):

* Click **{{ ui-key.yacloud.compute.nfs.button_attach-filesystem-to-the-instance }}**.
* In the window that opens, select the file storage.
* Enter the device name.
* Click **{{ ui-key.yacloud.compute.nfs.button_attach-filesystem-to-the-instance }}**.


1. Under **{{ ui-key.yacloud.compute.instances.create.section_platform }}**:

* Choose a [platform](../../compute/concepts/vm-platforms.md).
* Specify the [guaranteed share](../../compute/concepts/performance-levels.md) and the required number of vCPUs, as well as the amount of RAM.
* If required, make your VM [preemptible](../../compute/concepts/preemptible-vm.md).
* (Optional) Enable a [software-accelerated network](../../compute/concepts/software-accelerated-network.md).

1. Under **{{ ui-key.yacloud.compute.instances.create.section_network }}**:

{% include [network-settings](network-settings.md) %}


1. {% include [backup-info](backup-info.md) %}


1. Under **{{ ui-key.yacloud.compute.instances.create.section_access }}**, specify the information required to access the instance:
* Specify the required disk and block size.
* (Optional) Enable the **{{ ui-key.yacloud.compute.field_disk-autodelete }}** option in the **{{ ui-key.yacloud.compute.field_additional }}** field if you need to automatically delete this disk when deleting the VM.
* Click **{{ ui-key.yacloud.compute.component.instance-storage-dialog.button_add-disk }}**.

* (Optional) Select or create a [service account](../../iam/concepts/users/service-accounts.md). With a service account, you can flexibly configure access rights for your resources.
* Enter the username in the **{{ ui-key.yacloud.compute.instances.create.field_user }}** field.
1. Under **{{ ui-key.yacloud.k8s.node-groups.create.section_allocation-policy }}**, select an [availability zone](../../overview/concepts/geo-scope.md) to place your VM in.
1. Add a secondary [disk](../../compute/concepts/disk.md):

{% note alert %}
* Under **{{ ui-key.yacloud.compute.instances.create.section_storages_ru }}**, click **{{ ui-key.yacloud.compute.instances.create-disk.button_create }}**
* In the window that opens, select **{{ ui-key.yacloud.compute.instances.create-disk.value_source-disk }}**`Create new`.
* In the **{{ ui-key.yacloud.compute.instances.create-disk.field_source }}** field, select `{{ ui-key.yacloud.compute.instances.create-disk.value_source-snapshot }}`.
* Enter a name for the new disk.
* Select the [disk type](../../compute/concepts/disk.md#disks_types).
* Specify the required disk and block size.
* (Optional) Enable the **{{ ui-key.yacloud.compute.field_disk-autodelete }}** option in the **{{ ui-key.yacloud.compute.field_additional }}** field if you need to automatically delete this disk when deleting the VM.
* Click **{{ ui-key.yacloud.compute.component.instance-storage-dialog.button_add-disk }}**.

Do not use the `root` username or other names reserved by the operating system. To perform operations that require superuser permissions, use the `sudo` command.
1. {% include [encryption-section-secondary](encryption-section-secondary.md) %}
1. {% include [section-storages-filesystem](create/section-storages-filesystem.md) %}
1. {% include [section-platform](create/section-platform.md) %}
1. {% include [network-settings](create/section-network.md) %}
1. {% include [section-access](create/section-access.md) %}

{% endnote %}
1. Under **{{ ui-key.yacloud.compute.instances.create.section_base }}**, specify the VM name:

* In the **{{ ui-key.yacloud.compute.instances.create.field_key }}** field, paste the contents of the [public key](../../compute/operations/vm-connect/ssh.md#creating-ssh-keys) file.
* If required, grant access to the [serial console](../../compute/operations/serial-console/index.md).
{% include [name-format](../name-format.md) %}

{% include [vm-connect-linux](../vm-connect-linux.md) %}
{% include [name-fqdn](../compute/name-fqdn.md) %}

1. (Optional) Under **{{ ui-key.yacloud.compute.instances.create.section_placement }}**, select a VM [placement group](../../compute/concepts/placement-groups.md).
1. Click **{{ ui-key.yacloud.compute.instances.create.button_create }}**.
1. {% include [section-additional](../../_includes/compute/create/section-additional.md) %}
1. Click **{{ ui-key.yacloud.compute.instances.create.button_create }}**.

The virtual machine will appear in the list. When a VM is created, it is assigned an [IP address](../../vpc/concepts/address.md) and [host name](../../vpc/concepts/address.md#fqdn) (FQDN).
You will see the new VM in the list. Every new VM gets an [IP address](../../vpc/concepts/address.md) and [host name](../../vpc/concepts/address.md#fqdn) (FQDN).

- CLI {#cli}

{% include [cli-install](../cli-install.md) %}
{% include [cli-install](../cli-install.md) %}

{% include [default-catalogue](../default-catalogue.md) %}
{% include [default-catalogue](../default-catalogue.md) %}

1. View the description of the CLI command for creating a VM:
1. View the description of the CLI command for creating a VM:

```
yc compute instance create --help
```
1. Prepare snapshots of the required disks, see [{#T}](../../compute/operations/disk-control/create-snapshot.md).
1. Get a list of snapshots in the default folder:
1. Prepare the snapshots of the disks, see [{#T}](../../compute/operations/disk-control/create-snapshot.md).
1. Get a list of snapshots in the default folder:
{% include [compute-snapshot-list](../../compute/_includes_service/compute-snapshot-list.md) %}
1. Select the `ID`s or `NAME`s of the snapshots you need.
1. Create a VM in the default folder:
1. Select the IDs (`ID`) or names (`NAME`) of the snapshots you need.
1. Create a VM in the default folder:
```
yc compute instance create \
@@ -117,7 +77,7 @@
--ssh-key ~/.ssh/id_ed25519.pub
```
This command creates a VM named `first-instance` in the `{{ region-id }}-a` availability zone, with a public IP and the disks from the snapshots.
This command creates a VM named `first-instance` in the `{{ region-id }}-a` availability zone, with a public IP and disks from the snapshots.
{% include [name-fqdn](name-fqdn.md) %}
@@ -128,6 +88,6 @@
- API {#api}
Use the [create](../../compute/api-ref/Instance/create.md) REST API method for the [Instance](../../compute/api-ref/Instance/) resource or the [InstanceService/Create](../../compute/api-ref/grpc/Instance/create.md) gRPC API call.
Use the [create](../../compute/api-ref/Instance/create.md) REST API method for the [Instance](../../compute/api-ref/Instance/) resource or the [InstanceService/Create](../../compute/api-ref/grpc/Instance/create.md) gRPC API call.
{% endlist %}
4 changes: 4 additions & 0 deletions en/_includes/compute/create/access-ssh-key.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
In the **{{ ui-key.yacloud.compute.instances.create.field_key }}** field, paste the contents of the [public key](../../../compute/operations/vm-connect/ssh.md#creating-ssh-keys) file.

You need to create a key pair for the SSH connection yourself. To learn how, see [Connecting to a VM via SSH](../../../compute/operations/vm-connect/ssh.md).

Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
To create a VM instance from an existing boot disk, go to the **{{ ui-key.yacloud.compute.instances.create.image_value_custom_new }}** tab and select the boot disk you need. To update its settings, click ![image](../../../_assets/console-icons/pencil.svg) next to the disk name.
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
If you are creating a VM instance from an existing boot disk, update the settings of that disk in the **{{ ui-key.yacloud.compute.instances.create.image_value_custom_new }}** tab under **{{ ui-key.yacloud.compute.instances.create.section_image }}** at the top of the form.
87 changes: 26 additions & 61 deletions en/_includes/compute/create/create-vm-with-gpu-console.md
Original file line number Diff line number Diff line change
@@ -1,79 +1,44 @@
1. In the [management console]({{ link-console-main }}), select the folder to create the virtual machine in.
1. In the [management console]({{ link-console-main }}), select the folder to create your VM in.
1. In the list of services, select **{{ ui-key.yacloud.iam.folder.dashboard.label_compute }}**.
1. At the top right, click **{{ ui-key.yacloud.compute.instances.button_create }}**.
1. Under **{{ ui-key.yacloud.compute.instances.create.section_base }}**:
* Enter a name and description for the VM. The naming requirements are as follows:

{% include [name-format](../../name-format.md) %}

{% include [name-fqdn](../name-fqdn.md) %}

* Select an [availability zone](../../../overview/concepts/geo-scope.md) to place your virtual machine in.


{% include [gpu-zones](../gpu-zones.md) %}



1. In the left-hand panel, select ![image](../../../_assets/console-icons/server.svg) **{{ ui-key.yacloud.compute.switch_instances }}**.
1. Click **{{ ui-key.yacloud.compute.instances.button_create }}**.
1. Select one of the [GPU-oriented images](/marketplace?search=gpu) and OS version under **{{ ui-key.yacloud.compute.instances.create.section_image }}** in the **{{ ui-key.yacloud.compute.instances.create.image_value_marketplace }}** tab.

{% include [gpu-os](../gpu-os.md) %}

1. (Optional) Configure the boot disk under **{{ ui-key.yacloud.compute.instances.create.section_storages_ru }}**:
* Select the [disk type](../../../compute/concepts/disk.md#disks_types).
* Specify the required disk size.

{% include [gpu-os](../gpu-os.md) %}

* {% include [encryption-section-boot](../../../_includes/compute/encryption-section-boot.md) %}
1. Under **{{ ui-key.yacloud.k8s.node-groups.create.section_allocation-policy }}**, select an [availability zone](../../../overview/concepts/geo-scope.md) to place your VM in.
1. (Optional) Configure the boot [disk](../../../compute/concepts/disk.md) under **{{ ui-key.yacloud.compute.instances.create.section_storages_ru }}**:

* Select the [disk type](../../../compute/concepts/disk.md#disks_types).
* Specify the required disk size.
* {% include [encryption-section-secondary](../encryption-section-secondary.md) %}

If you are creating a VM from an existing boot disk, update the settings of that disk in the **{{ ui-key.yacloud.compute.instances.create.image_value_custom_new }}** tab under **{{ ui-key.yacloud.compute.instances.create.section_image }}** at the top of the form.

1. (Optional) Under **{{ ui-key.yacloud.compute.instances.create.section_storages_ru }}**, select the **{{ ui-key.yacloud.compute.nfs.label_filesystems }}** tab and attach the [file storage](../../../compute/concepts/filesystem.md):

* Click **{{ ui-key.yacloud.compute.nfs.button_attach-filesystem-to-the-instance }}**.
* In the window that opens, select the file storage.
* Enter the device name.
* Click **{{ ui-key.yacloud.compute.nfs.button_attach-filesystem-to-the-instance }}**.


1. {% include [section-storages-secondary-disk](section-storages-secondary-disk.md) %}
1. {% include [section-storages-filesystem](section-storages-filesystem.md) %}
1. Under **{{ ui-key.yacloud.compute.instances.create.section_platform }}**:
* Choose a [platform](../../../compute/concepts/vm-platforms.md#gpu-platforms):


* {{ v100-broadwell }}
* {{ v100-cascade-lake }}
* {{ a100-epyc }}
* {{ t4-ice-lake }}



* Select a VM [configuration](../../../compute/concepts/gpus.md#config) specifying the required number of GPUs.
* Make your VM [preemptible](../../../compute/concepts/preemptible-vm.md), if required.


1. Under **{{ ui-key.yacloud.compute.instances.create.section_network }}**:

{% include [network-settings](../../../_includes/compute/network-settings.md) %}

1. Under **{{ ui-key.yacloud.compute.instances.create.section_access }}**, specify the data required to access the VM:
* (Optional) Select or create a [service account](../../../iam/concepts/index.md#sa). With a service account, you can flexibly configure access rights for your resources.

For VMs with a Linux-based operating system:
* Enter the username in the **{{ ui-key.yacloud.compute.instances.create.field_user }}** field.
* Go to the **{{ ui-key.yacloud.component.compute.resources.label_tab-gpu }}** tab.
* Choose a [platform](../../../compute/concepts/vm-platforms.md#gpu-platforms):

{% note alert %}
* {{ v100-broadwell }}
* {{ v100-cascade-lake }}
* {{ a100-epyc }}
* {{ t4-ice-lake }}

Do not use the `root` username or other names reserved by the operating system. To perform operations that require superuser permissions, use the `sudo` command.
* Select one of the available configurations with the required GPUs, vCPUs, and amount of RAM.

{% endnote %}
1. {% include [network-settings](section-network.md) %}
1. {% include [section-access](section-access.md) %}

* In the **{{ ui-key.yacloud.compute.instances.create.field_key }}** field, paste the contents of the [public key](../../../compute/operations/vm-connect/ssh.md#creating-ssh-keys) file.
1. Under **{{ ui-key.yacloud.compute.instances.create.section_base }}**, specify the VM name:

* (Optional) Enable access to the [serial console](../../../compute/operations/index.md#serial-console), if required.
{% include [name-format](../../name-format.md) %}

{% include [vm-connect-linux](../../../_includes/vm-connect-linux.md) %}
{% include [name-fqdn](../../compute/name-fqdn.md) %}

1. (Optional) Under **{{ ui-key.yacloud.compute.instances.create.section_placement }}**, select a VM [placement group](../../../compute/concepts/placement-groups.md).
1. {% include [section-additional](section-additional.md) %}
1. Click **{{ ui-key.yacloud.compute.instances.create.button_create }}**.

The virtual machine will appear in the list.
The virtual machine will appear in the list.
17 changes: 17 additions & 0 deletions en/_includes/compute/create/section-access.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
Under **{{ ui-key.yacloud.compute.instances.create.section_access }}**, specify the data for access to the VM:

* (Optional) [Enable VM access via OS Login](../../../compute/operations/vm-connect/os-login.md). The option is available for Linux images from [{{ marketplace-name }}](/marketplace) with `OS Login` in their names.
* Enter the username into the **{{ ui-key.yacloud.compute.instances.create.field_user }}** field.

{% note alert %}

Do not use `root` or other usernames reserved by the OS. To perform operations requiring superuser permissions, use the `sudo` command.

{% endnote %}

* In the **{{ ui-key.yacloud.compute.instances.create.field_key }}** field, paste the contents of the [public key](../../../compute/operations/vm-connect/ssh.md#creating-ssh-keys) file. You need to create a key pair for the SSH connection yourself. To learn how, see [Connecting to a VM via SSH](../../../compute/operations/vm-connect/ssh.md).

If you want to add several users with SSH keys to the VM at the same time, [specify](../../../compute/concepts/vm-metadata.md#how-to-send-metadata) these users' data under **{{ ui-key.yacloud.common.metadata }}**. You can also use metadata to [install additional software](../../../compute/operations/vm-create/create-with-cloud-init-scripts.md) on a VM when creating it.

{% include [vm-connect-linux](../../vm-connect-linux.md) %}

9 changes: 9 additions & 0 deletions en/_includes/compute/create/section-additional.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
Under **{{ ui-key.yacloud.compute.instances.create.section_additional }}**:

* (Optional) Select or create a [service account](../../../iam/concepts/users/service-accounts.md). With a service account, you can flexibly configure access rights for your resources.
* (Optional) Grant access to the [serial console](../../../compute/operations/serial-console/index.md).
* (Optional) Under **Backup**, enable **{{ ui-key.yacloud.compute.instances.create.action_activate-backup }}** and select or create a [backup policy](../../../backup/concepts/policy.md) to back up your VMs automatically using [{{ backup-name }}](../../../backup/index.yaml).

For more information, see [{#T}](../../../backup/concepts/vm-connection.md).
* (Optional) Under **{{ ui-key.yacloud.compute.instances.create.section_monitoring }}**, enable the **{{ ui-key.yacloud.compute.instances.create.unified-agent }}** option to configuire delivery of [metrics](../../../compute/metrics.md) to [{{ monitoring-full-name }}](../../../compute/monitoring/).
* (Optional) Under **{{ ui-key.yacloud.compute.instances.create.section_placement }}**, select a VM [placement group](../../../compute/concepts/placement-groups.md).
33 changes: 33 additions & 0 deletions en/_includes/compute/create/section-network.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
Under **{{ ui-key.yacloud.compute.instances.create.section_network }}**:

* In the **{{ ui-key.yacloud.component.compute.network-select.field_subnetwork }}** field, enter the ID of a subnet in the new VM’s availability zone. Alternatively, you can select a [cloud network](../../../vpc/concepts/network.md#network) from the list.

* Each network must have at least one [subnet](../../../vpc/concepts/network.md#subnet). If there is no subnet, create one by selecting **{{ ui-key.yacloud.component.vpc.network-select.button_create-subnetwork }}**.
* If you do not have a network, click **{{ ui-key.yacloud.component.vpc.network-select.button_create-network }}** to create one:

* In the window that opens, enter the network name and select the folder to host the network.
* (Optional) Select the **{{ ui-key.yacloud.vpc.networks.create.field_is-default }}** option to automatically create subnets in all availability zones.
* Click **{{ ui-key.yacloud.vpc.networks.create.button_create }}**.

* In the **{{ ui-key.yacloud.component.compute.network-select.field_external }}** field, choose a method for assigning an IP address:

* `{{ ui-key.yacloud.component.compute.network-select.switch_auto }}`: Assign a random IP address from the {{ yandex-cloud }} IP address pool. In this case, you can enable [DDoS protection](../../../vpc/ddos-protection/index.md) using the option below.
* `{{ ui-key.yacloud.component.compute.network-select.switch_list }}`: Select a public IP address from the list of previously reserved static addresses. For more information, see [{#T}](../../../vpc/operations/set-static-ip.md).
* `{{ ui-key.yacloud.component.compute.network-select.switch_none }}`: Do not assign a public IP address.

* Select the [appropriate security groups](../../../vpc/concepts/security-groups.md). If you leave this field empty, the default security group will be assigned to the VM.

* Expand the **{{ ui-key.yacloud.component.compute.network-select.section_additional }}** section and select a method for internal IP address assignment in the **{{ ui-key.yacloud.component.internal-v4-address-field.field_internal-ipv4-address }}** field:

* `{{ ui-key.yacloud.common.label_auto }}`: Assign a random IP address from the pool of IP addresses available in the selected subnet.
* `{{ ui-key.yacloud.common.label_list }}`: Select a private IP address from the list of previously reserved IP addresses. Click **{{ ui-key.yacloud.component.internal-v4-address-field.button_internal-address-reserve }}** to reserve a private IP address in the selected subnet if needed.
* Enable the **{{ ui-key.yacloud.common.field_ddos-protection-provider }}** option, if needed. The option is available if you previously selected the automatic IP assignment method in the public address settings.

* (Optional) Create records for the VM in the [DNS zone](../../../dns/concepts/dns-zone.md):

* Expand the **{{ ui-key.yacloud.dns.label_dns-internal-settings }}** section and click **{{ ui-key.yacloud.dns.button_add-record }}**.
* Specify the zone, FQDN, and TTL for the record. When setting the FQDN, you can select `{{ ui-key.yacloud.dns.label_auto-select-zone }}` for the zone.
You can add multiple records to [internal DNS zones](../../../dns/concepts/dns-zone.md). For more information, see [Cloud DNS integration with Compute Cloud](../../../dns/concepts/compute-integration.md).
* To create another record, click **{{ ui-key.yacloud.dns.button_add-record }}**.

If you want to attach an additional [network interface](../../../compute/concepts/network.md) to your VM, click **{{ ui-key.yacloud.compute.instances.create.label_add-network-interface }}** and repeat the settings from this step for the new interface. You can add up to eight network interfaces to a single VM.
7 changes: 7 additions & 0 deletions en/_includes/compute/create/section-platform.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
Under **{{ ui-key.yacloud.compute.instances.create.section_platform }}**, select a preset configuration or create a new one. To create a configuration:

* Go to the **{{ ui-key.yacloud.component.compute.resources.label_tab-custom }}** tab.
* Choose a [platform](../../../compute/concepts/vm-platforms.md).
* Specify the [guaranteed share](../../../compute/concepts/performance-levels.md) and required number of vCPUs, as well as RAM size.
* Enable a [software-accelerated network](../../../compute/concepts/software-accelerated-network.md) if needed.
* If required, make your VM [preemptible](../../../compute/concepts/preemptible-vm.md).
9 changes: 9 additions & 0 deletions en/_includes/compute/create/section-storages-filesystem.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
(Optional) Connect a [file storage](../../../compute/concepts/filesystem.md):

* Under **{{ ui-key.yacloud.compute.instances.create.section_storages_ru }}**, click **{{ ui-key.yacloud.compute.instances.create-disk.button_create }}**.

* In the window that opens, select **File storage** and select the storage you want to connect from the list.

If you do not have any file storages, click **{{ ui-key.yacloud.compute.nfs.button_create-filesystem }}** to create a new one.

* Click **Add file storage**.
14 changes: 14 additions & 0 deletions en/_includes/compute/create/section-storages-secondary-disk.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
(Optional) Add a secondary [disk](../../../compute/concepts/disk.md):

* Under **{{ ui-key.yacloud.compute.instances.create.section_storages_ru }}**, click **{{ ui-key.yacloud.compute.instances.create-disk.button_create }}**
* In the window that opens, select **{{ ui-key.yacloud.compute.instances.create-disk.value_source-disk }}**. You can select an existing disk or create a new one, either empty or from a snapshot / image.

For example, to create a new empty disk:

* Select `Create new`.
* In the **{{ ui-key.yacloud.compute.instances.create-disk.field_source }}** field, select `{{ ui-key.yacloud.compute.instances.create-disk.value_source-none }}`.
* Specify the disk name.
* Select the [disk type](../../../compute/concepts/disk.md#disks_types).
* Specify the required disk size and block size.
* (Optional) Enable the **{{ ui-key.yacloud.compute.field_additional }}** option in the **{{ ui-key.yacloud.compute.field_disk-autodelete }}** field if you need to automatically delete this disk when deleting the VM.
* Click **{{ ui-key.yacloud.compute.component.instance-storage-dialog.button_add-disk }}**.
9 changes: 0 additions & 9 deletions en/_includes/compute/encryption-section-boot.md

This file was deleted.

10 changes: 9 additions & 1 deletion en/_includes/compute/encryption-section-secondary.md
Original file line number Diff line number Diff line change
@@ -1 +1,9 @@
(Optional) To encrypt a disk, configure encryption parameters.
(Optional) To [encrypt](../../compute/concepts/encryption.md) a boot disk or a secondary disk, under **{{ ui-key.yacloud.compute.instances.create.section_storages_ru }}**, click ![image](../../_assets/console-icons/pencil.svg) to the right of the disk name and set encryption parameters for the disk:

* Select **{{ ui-key.yacloud.compute.disk-form.label_disk-encryption }}**.
* In the **{{ ui-key.yacloud.compute.disk-form.label_disk-kms-key }}** field, select the [key](../../kms/concepts/key.md) to encrypt the disk with. To [create](../../kms/operations/key.md#create) a new key, click **{{ ui-key.yacloud.component.symmetric-key-select.button_create-key-new }}**.
* In the **{{ ui-key.yacloud.compute.disk-form.label_service-account }}** field, select a [service account](../../iam/concepts/users/service-accounts.md) with the `kms.keys.encrypterDecrypter` [role](../../kms/security/index.md#kms-keys-encrypterDecrypter) for the specified key. To [create](../../iam/operations/sa/create.md) a service account, click **{{ ui-key.yacloud.component.service-account-select.button_create-account-new }}**.

{% include [encryption-preview-note](encryption-preview-note.md) %}

{% include [encryption-keys-note](encryption-keys-note.md) %}
4 changes: 1 addition & 3 deletions en/_includes/compute/gpu-os.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,3 @@

For VMs with GPUs, you can use the following special images of operating systems with NVIDIA drivers:

{{ v100-broadwell }} and {{ v100-cascade-lake }}
@@ -15,5 +14,4 @@ For VMs with GPUs, you can use the following special images of operating systems
: * [Ubuntu 20.04 LTS GPU A100](/marketplace/products/yc/ubuntu-20-04-lts-gpu-a100) (`ubuntu-2004-lts-a100`)
* [Ubuntu 18.04 LTS GPU A100](/marketplace/products/yc/ubuntu-18-04-lts-gpu-a100) (`ubuntu-1804-lts-a100`)

We recommend using a standard image from {{ yandex-cloud }}. You can also [install the drivers](../../compute/operations/vm-operate/install-nvidia-drivers.md) on another standard image yourself or [create a custom image](../../compute/operations/image-create/custom-image.md) with pre-installed drivers.

We recommend using a standard image from {{ yandex-cloud }}. You can also [install the drivers](../../compute/operations/vm-operate/install-nvidia-drivers.md) on another standard image yourself or [create a custom image](../../compute/operations/image-create/custom-image.md) with pre-installed drivers.
29 changes: 0 additions & 29 deletions en/_includes/compute/network-settings.md

This file was deleted.

5 changes: 5 additions & 0 deletions en/_includes/compute/os-login-certificate-short-lived.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{% note info %}

The certificate is valid for one hour. After this time has elapsed, you will need to [export](../../compute/operations/vm-connect/os-login-export-certificate.md) a new certificate to connect to the VM.

{% endnote %}
3 changes: 3 additions & 0 deletions en/_includes/compute/oslogin-connect-cert-enable-in-org.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
[Enable](../../organization/operations/os-login-access.md) access via OS Login at the organization level.

To connect to a VM via OS Login using an SSH certificate, enable **{{ ui-key.yacloud_org.form.oslogin-settings.title_ssh-certificate-settings }}**.
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
[Create](../../compute/operations/vm-connect/ssh.md#creating-ssh-keys) an SSH key pair and [add](../../organization/operations/add-ssh.md) the public key to the OS Login profile of a user or [service account](../../iam/concepts/users/service-accounts.md). Remember where your private key is stored, as you will need it to connect to a VM.
16 changes: 16 additions & 0 deletions en/_includes/compute/oslogin-connect-instr-list-vms.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
Get a list of all VMs in the default folder:

```bash
yc compute instance list
```

Result:

```text
+----------------------+-----------------+---------------+---------+---------------+--------------+
| ID | NAME | ZONE ID | STATUS | EXTERNAL IP | INTERNAL IP |
+----------------------+-----------------+---------------+---------+---------------+--------------+
| fhm0b28lgf********** | first-instance | {{ region-id }}-a | RUNNING | 158.160.**.** | 192.168.0.8 |
| fhm9gk85nj********** | second-instance | {{ region-id }}-a | RUNNING | 51.250.**.*** | 192.168.0.12 |
+----------------------+-----------------+---------------+---------+---------------+--------------+
```
5 changes: 5 additions & 0 deletions en/_includes/compute/oslogin-connect-key-enable-in-org.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
[Enable](../../organization/operations/os-login-access.md) access via OS Login at the organization level.

To connect to a VM via OS Login using an SSH certificate, enable **{{ ui-key.yacloud_org.form.oslogin-settings.title_user-ssh-key-settings }}**.

To add an SSH key to an organization user profile, enable **{{ ui-key.yacloud_org.form.oslogin-settings.title_allow-edit-own-keys }}**.
54 changes: 14 additions & 40 deletions en/_includes/compute/oslogin-connect-with-cli.md
Original file line number Diff line number Diff line change
@@ -1,52 +1,26 @@
To connect to a VM via OS Login with an SSH certificate using the YC CLI:

1. [Enable](../../organization/operations/os-login-access.md) access via OS Login at the organization level.

To connect to a VM via OS Login with an SSH certificate using the YC CLI, enable **{{ ui-key.yacloud_org.form.oslogin-settings.title_ssh-certificate-settings }}**.

1. {% include [oslogin-connect-cert-enable-in-org](../../_includes/compute/oslogin-connect-cert-enable-in-org.md) %}
1. View the description of the CLI command to connect to a VM:

```bash
yc compute ssh --help
```

1. Get a list of all VMs in the default folder:
1. {% include [os-login-cli-organization-list](../../_includes/organization/os-login-cli-organization-list.md) %}
1. {% include [os-login-cli-profile-list](../../_includes/organization/os-login-cli-profile-list.md) %}
1. {% include [oslogin-connect-instr-list-vms](../../_includes/compute/oslogin-connect-instr-list-vms.md) %}
1. Connect to the VM:

```bash
yc compute instance list
```

Result:

```text
+----------------------+-----------------+---------------+---------+----------------------+
| ID | NAME | ZONE ID | STATUS | DESCRIPTION |
+----------------------+-----------------+---------------+---------+----------------------+
| fhm0b28lgf********** | first-instance | {{ region-id }}-a | RUNNING | my first vm via CLI |
| fhm9gk85nj********** | second-instance | {{ region-id }}-a | RUNNING | my second vm via CLI |
+----------------------+-----------------+---------------+---------+----------------------+
yc compute ssh \
--name <VM_name>
--login <user_or_service_account_login>
--internal-address
```

1. Connect to the VM:

To connect via OS login, use the VM name:

```bash
yc compute ssh \
--name <VM_name>
```

When connecting via OS Login, you can specify the VM ID instead of its name:

```bash
yc compute ssh \
--id <VM_ID>
```
Where:
* `--name`: Previously obtained VM name. You can specify the VM ID instead of its name by using the `--id` parameter.
* `--login`: Previously obtained user or service account login, as set in the OS Login profile. This is an optional parameter. If this parameter is not specified, the connection will use the SSH certificate of the user or service account currently authorized in the YC CLI profile.
* (Optional) `--internal-address`: To connect using an internal IP address.

To connect via OS login by an internal IP address, use the `--internal-address` parameter:

```bash
yc compute ssh \
--name <VM_name> \
--internal-address
```
You can also see the command for VM connection in the [management console]({{ link-console-main }}). On the **{{ ui-key.yacloud.compute.instance.overview.label_title }}** page of the VM you need, under **Connect to VM**, expand the **Connect via the {{ yandex-cloud }} CLI interface** section and select the **Certificate** tab.
93 changes: 14 additions & 79 deletions en/_includes/compute/oslogin-connect-with-exported-cert.md
Original file line number Diff line number Diff line change
@@ -1,91 +1,26 @@
You can use a standard SSH client or exported OS Login certificate to connect to a VM with OS Login access enabled. To do this, [assign](../../iam/operations/roles/grant.md) the `compute.osLogin` or `compute.osAdminLogin` role to the user or service account holding the certificate.
To connect to a VM via OS Login with an SSH certificate using a standard SSH client:

To connect to a VM via OS Login using a standard SSH client, [export](../../compute/operations/vm-connect/os-login-export-certificate.md) the OS Login certificate to your local computer and specify this certificate when connecting to a VM:

1. [Enable](../../organization/operations/os-login-access.md) access via OS Login at the organization level.

To connect to a VM via OS Login using an SSH certificate over a standard SSH client, enable **{{ ui-key.yacloud_org.form.oslogin-settings.title_ssh-certificate-settings }}**.

1. Get a list of all VMs in the default folder:

```bash
yc compute instance list
```

Result:

```text
+----------------------+-----------------+---------------+---------+---------------+--------------+
| ID | NAME | ZONE ID | STATUS | EXTERNAL IP | INTERNAL IP |
+----------------------+-----------------+---------------+---------+---------------+--------------+
| fhm0b28lgf********** | first-instance | {{ region-id }}-a | RUNNING | 158.160.**.** | 192.168.0.8 |
| fhm9gk85nj********** | second-instance | {{ region-id }}-a | RUNNING | 51.250.**.*** | 192.168.0.12 |
+----------------------+-----------------+---------------+---------+---------------+--------------+
```

1. Get a [public address](../../vpc/concepts/address.md#public-addresses) of the VM by specifying its ID:

```bash
yc compute instance get \
--id <VM_ID>
```

{% cut "Result:" %}

```yaml
id: fhm0b28lgf**********
folder_id: b1gt6g8ht345********
created_at: "2023-12-09T06:23:04Z"
name: first-instance
zone_id: {{ region-id }}-a
platform_id: standard-v3
resources:
memory: "2147483648"
cores: "2"
core_fraction: "100"
status: RUNNING
metadata_options:
gce_http_endpoint: ENABLED
aws_v1_http_endpoint: ENABLED
gce_http_token: ENABLED
aws_v1_http_token: DISABLED
boot_disk:
mode: READ_WRITE
device_name: epd9m2csd95p********
auto_delete: true
disk_id: epd9m2csd95p********
network_interfaces:
- index: "0"
mac_address: d0:0d:87:75:**:**
subnet_id: e2li9tcgi7ii********
primary_v4_address:
address: 192.168.0.8
one_to_one_nat:
address: 158.160.**.**
ip_version: IPV4
gpu_settings: {}
fqdn: first-instance.{{ region-id }}.internal
scheduling_policy: {}
network_settings:
type: STANDARD
placement_policy: {}
```

You can find the VM public address in the `network_interfaces.primary_v4_address.one_to_one_nat.address` field.

{% endcut %}
1. {% include [oslogin-connect-cert-enable-in-org](../../_includes/compute/oslogin-connect-cert-enable-in-org.md) %}
1. [Export](../../compute/operations/vm-connect/os-login-export-certificate.md) the SSH certificate to your local computer.
1. {% include [os-login-cli-organization-list](../../_includes/organization/os-login-cli-organization-list.md) %}
1. {% include [os-login-cli-profile-list](../../_includes/organization/os-login-cli-profile-list.md) %}
1. {% include [oslogin-connect-instr-list-vms](../../_includes/compute/oslogin-connect-instr-list-vms.md) %}

Save the public IP address (the `EXTERNAL IP` value) of the VM you want to connect to.
1. Connect to the VM:

```bash
ssh -i <certificate_file_path> <username>@<VM_public_IP_address>
ssh -i <certificate_file_path> \
-l <user_or_service_account_login> <VM_public_IP_address>
```

Where:

* `<certificate_file_path>`: Path to the previously saved `Identity` file of the certificate. e.g., `/home/user1/.ssh/yc-cloud-id-b1gia87mbaom********-orgusername`.
* `<username>`: Organization user's name. You can see the username at the end of the exported OS Login certificate. In the example above, it is `orgusername`.
* `<VM_public_IP_address>`: VM public IP address obtained earlier.
* `<certificate_file_path>`: Path to the certificate’s `Identity` file you exported previously, e.g., `/home/user1/.ssh/yc-cloud-id-b1gia87mbaom********-orgusername`.
* `<user_or_service_account_login>`: Previously obtained user or [service account](../../iam/concepts/users/service-accounts.md) login, as set in the OS Login profile.
* `<VM_public_IP_address>`: VM public IP address you saved earlier.

You can also see the command for VM connection in the [management console]({{ link-console-main }}). On the **{{ ui-key.yacloud.compute.instance.overview.label_title }}** page of the VM you need, under **Connect to VM**, expand the **Connect via SSH client** section and select the **Certificate** tab.

If this is your first time connecting to the VM, you will see an unknown host warning:

36 changes: 12 additions & 24 deletions en/_includes/compute/oslogin-connect-with-key.md
Original file line number Diff line number Diff line change
@@ -1,41 +1,29 @@
You can use a custom SSH key to connect to VMs with OS Login access enabled. To do this, [create](../../compute/operations/vm-connect/ssh.md#creating-ssh-keys) an SSH key, [add](../../organization/operations/add-ssh.md) it to the organization user or service account profile in {{ org-full-name }}, and specify the following when connecting:
To connect to a VM instance via OS Login with an SSH key using the YC CLI:

1. [Enable](../../organization/operations/os-login-access.md) access via OS Login at the organization level.

To connect to a VM via OS Login using an SSH key over the YC CLI, enable **{{ ui-key.yacloud_org.form.oslogin-settings.title_user-ssh-key-settings }}**.

1. Get a list of all VMs in the default folder:
1. {% include [oslogin-connect-key-enable-in-org](../../_includes/compute/oslogin-connect-key-enable-in-org.md) %}
1. {% include [oslogin-connect-instr-create-ssh-key](../../_includes/compute/oslogin-connect-instr-create-ssh-key.md) %}
1. View the description of the CLI command to connect to a VM:

```bash
yc compute instance list
yc compute ssh --help
```

Result:

```text
+----------------------+-----------------+---------------+---------+---------------+--------------+
| ID | NAME | ZONE ID | STATUS | EXTERNAL IP | INTERNAL IP |
+----------------------+-----------------+---------------+---------+---------------+--------------+
| fhm0b28lgf********** | first-instance | {{ region-id }}-a | RUNNING | 158.160.**.** | 192.168.0.8 |
| fhm9gk85nj********** | second-instance | {{ region-id }}-a | RUNNING | 51.250.**.*** | 192.168.0.12 |
+----------------------+-----------------+---------------+---------+---------------+--------------+
```

1. {% include [os-login-cli-organization-list](../../_includes/organization/os-login-cli-organization-list.md) %}
1. {% include [os-login-cli-profile-list](../../_includes/organization/os-login-cli-profile-list.md) %}
1. {% include [oslogin-connect-instr-list-vms](../../_includes/compute/oslogin-connect-instr-list-vms.md) %}
1. Connect to the VM:

```bash
yc compute ssh \
--name <VM_name> \
--identity-file <path_to_private_SSH_key_file> \
--login <username> \
--login <user_or_service_account_login> \
--internal-address
```

Where:

* `--name`: Previously obtained VM name. You can specify the VM ID instead of its name by using the `--id` parameter.
* `--identity-file`: Path to the previously saved private SSH key file, e.g., `/home/user1/.ssh/id_ed25519`.
* `--login`: OS Login username.
* `--identity-file`: Path to a private SSH key file, e.g., `/home/user1/.ssh/id_ed25519`.
* `--login`: Previously obtained user or service account login, as set in the OS Login profile. This is an optional parameter. If this parameter is not specified, the connection will use the SSH certificate of the user or service account currently authorized in the YC CLI profile.
* (Optional) `--internal-address`: To connect using an internal IP address.

You will connect to the specified virtual machine using your SSH key. If this is your first time connecting to this VM, a new user profile will be created in the VM's operating system.
You can also see the command for VM connection in the [management console]({{ link-console-main }}). On the **{{ ui-key.yacloud.compute.instance.overview.label_title }}** page of the VM you need, under **Connect to VM**, expand the **Connect via the {{ yandex-cloud }} CLI interface** section and select the **SSH key** tab.
32 changes: 9 additions & 23 deletions en/_includes/compute/oslogin-export-certificate.md
Original file line number Diff line number Diff line change
@@ -1,48 +1,34 @@
To export an OS Login user certificate from an organization to your local computer:
To export the SSH certificate of a {{ org-name }} organization user or [service account](../../iam/concepts/users/service-accounts.md) to a local computer:

{% list tabs group=instructions %}


- CLI {#cli}

{% include [cli-install](../cli-install.md) %}

{% include [default-catalogue](../default-catalogue.md) %}

1. See the description of the CLI command for exporting an OS Login certificate to a local directory:
1. See the description of the CLI command for exporting an SSH certificate to a local directory:

```bash
yc compute ssh certificate export --help
```

1. If you have multiple organizations, get the ID of the organization you want to export the certificate from. If you have a single organization, skip this step.

```bash
yc organization-manager organization list
```

Result:

```text
+----------------------+-------------------------+-------------------------+
| ID | NAME | TITLE |
+----------------------+-------------------------+-------------------------+
| bpf1smsil5q0******** | sample-organization1 | Organization 1 |
| bpf2c65rqcl8******** | sample-organization2 | Organization 2 |
| bpf6dne49ue8******** | sample-organization3 | Organization 3 |
+----------------------+-------------------------+-------------------------+
```

1. {% include [os-login-cli-organization-list](../../_includes/organization/os-login-cli-organization-list.md) %}
1. {% include [os-login-cli-profile-list](../../_includes/organization/os-login-cli-profile-list.md) %}
1. Export the certificate:

```bash
yc compute ssh certificate export \
--login <user_or_service_account_login>
--organization-id <organization_ID> \
--directory <path_to_directory>
```

Where:
* `--organization-id`: Previously obtained ID of the organization to export the OS Login certificate from. This is an optional parameter. If omitted, the certificate will be exported from the organization the default folder belongs to.
* `--directory`: Path to the local directory to save the exported OS Login certificate to. This is an optional parameter. If not specified, the certificate will be saved by default to the `.ssh` home directory of the current PC user (`~/.ssh/`).
* `--login`: Previously obtained user or service account login, as set in the OS Login profile. This is an optional parameter. If you do not set this parameter, you will export the SSH certificate of the user or service account currently authorized in the YC CLI profile.
* `--organization-id`: Previously obtained ID of the organization to export the SSH certificate from. This is an optional parameter. If omitted, the certificate will be exported from the organization the default folder belongs to.
* `--directory`: Path to the local directory to save the exported SSH certificate to. This is an optional parameter. If not specified, the certificate will be saved by default to the `.ssh` home directory of the current PC user (`~/.ssh/`).

Result:

33 changes: 33 additions & 0 deletions en/_includes/compute/oslogin-ssh-connect-with-ssh-key.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
To connect to a VM instance via OS Login with an SSH key using a standard SSH client:

1. {% include [oslogin-connect-key-enable-in-org](../../_includes/compute/oslogin-connect-key-enable-in-org.md) %}
1. {% include [oslogin-connect-instr-create-ssh-key](../../_includes/compute/oslogin-connect-instr-create-ssh-key.md) %}
1. {% include [os-login-cli-organization-list](../../_includes/organization/os-login-cli-organization-list.md) %}
1. {% include [os-login-cli-profile-list](../../_includes/organization/os-login-cli-profile-list.md) %}
1. {% include [oslogin-connect-instr-list-vms](../../_includes/compute/oslogin-connect-instr-list-vms.md) %}

Save the public IP address (the `EXTERNAL IP` value) of the VM you want to connect to.
1. Connect to the VM:

```bash
ssh -i <path_to_private_SSH_key_file> \
-l <user_or_service_account_login> <VM_public_IP_address>
```

Where:

* `<path_to_private_SSH_key_file>`: Path to the file containing the private SSH key, e.g., `/home/user1/.ssh/id_ed25519`.
* `<user_or_service_account_login>`: Previously obtained user or service account login, as set in the OS Login profile.
* `<VM_public_IP_address>`: VM public IP address you saved earlier.

You can also see the command for VM connection in the [management console]({{ link-console-main }}). On the **{{ ui-key.yacloud.compute.instance.overview.label_title }}** page of the VM you need, under **Connect to VM**, expand the **Connect via SSH client** section and select the **SSH key** tab.

If this is your first time connecting to the VM, you will see an unknown host warning:

```text
The authenticity of host '158.160.**.** (158.160.**.**)' can't be established.
ECDSA key fingerprint is SHA256:PoaSwqxRc8g6iOXtiH7ayGHpSN0MXwUfWHk********.
Are you sure you want to continue connecting (yes/no)?
```
Type `yes` in the terminal and press **Enter**.
5 changes: 3 additions & 2 deletions en/_includes/compute/software-accelerated-network.md
Original file line number Diff line number Diff line change
@@ -3,6 +3,7 @@
In the {{ yandex-cloud }} infrastructure, all VMs run in the [QEMU-KVM](https://en.wikipedia.org/wiki/QEMU) virtualization environment. A *hypervisor* proportionally distributes the computing load across all processor cores allocated to a VM.

The computing load can be logically divided into three parts:

* User load: OS processes and user processes run in the OS of a user VM.
* Processes maintaining the operation of [network disks](../../compute/concepts/disk.md).
* Processes for handling the VM's network traffic.
@@ -44,9 +45,9 @@ The [cost](../../compute/pricing.md#software-accelerated-network) of additional

To enable a software-accelerated network:

* Select the **{{ ui-key.yacloud.component.compute.resources.label_sw-accelerated-net }}** option when [creating a new VM](../../compute/operations/vm-create/create-linux-vm.md) or [reconfigure](../../compute/operations/vm-control/vm-update-resources.md#enable-software-accelerated-network) an existing VM.
* Select the **{{ ui-key.yacloud.component.compute.resources.field_sw-accelerated-net }}** option when [creating a new VM](../../compute/operations/vm-create/create-linux-vm.md) or [reconfigure](../../compute/operations/vm-control/vm-update-resources.md#enable-software-accelerated-network) an existing VM.

* Enable the **{{ ui-key.yacloud.component.compute.resources.label_sw-accelerated-net }}** option in the basic VM configuration when [creating an instance group](../../compute/operations/instance-groups/create-fixed-group.md) or set the `network_settings.type` key to `SOFTWARE_ACCELERATED` in the [YAML specification](../../compute/concepts/instance-groups/specification.md).
* Enable the **{{ ui-key.yacloud.component.compute.resources.field_sw-accelerated-net }}** option in the basic VM configuration when [creating an instance group](../../compute/operations/instance-groups/create-fixed-group.md) or set the `network_settings.type` key to `SOFTWARE_ACCELERATED` in the [YAML specification](../../compute/concepts/instance-groups/specification.md).

## Recommendations for using a software-accelerated network {#use-cases}

Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
**{{ ui-key.yc-data-transfer.data-transfer.console.form.common.console.form.common.Connection.authorization_connman.title }}**: Enables using a database conection via [{{ connection-manager-full-name }}](../../../../../metadata-hub/quickstart/connection-manager.md):

* **{{ ui-key.yc-data-transfer.data-transfer.console.form.postgres.console.form.postgres.ConnmanConnection.connection_id.title }}**: Specify a connection ID from {{ connection-manager-name }}.
* **{{ ui-key.yc-data-transfer.data-transfer.console.form.common.console.form.common.ConnmanConnection.connection_id.title }}**: Specify a connection ID from {{ connection-manager-name }}.

* {% include [database](../../../fields/postgresql/ui/database.md) %}

29 changes: 29 additions & 0 deletions en/_includes/datasphere/dag-load-job-results.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
You can use a DAG operator to load the output file of one job (`result.txt`) and provide it as an input file (`INPUT_DATA`) for another:

{% list tabs group=programming_language %}

- Python {#bash}

```python
from typing import Dict

from airflow.decorators import dag, task
import pendulum

from datasphere import SDK

now = pendulum.now()

@dag(dag_id='output_files_for_other_job', start_date=now, schedule="@daily", catchup=False)
def run():
@task(task_id='fork_job')
def fork_job(files_job_id: str, fork_source_job_id: str):
sdk = SDK()
sdk.download_job_files(files_job_id)
job = sdk.fork_job(fork_source_job_id, vars={'INPUT_DATA': 'result.txt'})
job.wait()

fork_job('<ID_of_job_to_download>', '<ID_of_job_to_run>')
```

{% endlist %}
56 changes: 29 additions & 27 deletions en/_includes/instance-groups/create-autoscaled-group-via-concole.md
Original file line number Diff line number Diff line change
@@ -5,13 +5,13 @@
1. Under **{{ ui-key.yacloud.compute.groups.create.section_base }}**:
* Enter a name and description of the instance group. The naming requirements are as follows:

{% include [name-format](../name-format.md) %}
{% include [name-format](../name-format.md) %}

{% include [name-fqdn](../compute/name-fqdn.md) %}
{% include [name-fqdn](../compute/name-fqdn.md) %}

* Select a [service account](../../iam/concepts/users/service-accounts.md) from the list or create a new one. To be able to create, update, and delete instances in the instance group, assign the `editor` role to the service account. By default, all operations in {{ ig-name }} are performed on behalf of a service account.
* Select a [service account](../../iam/concepts/users/service-accounts.md) from the list or create a new one. To be able to create, update, and delete VM instances in the instance group, assign the `editor` role to the service account. By default, all operations in {{ ig-name }} are performed on behalf of a service account.

{% include [sa-dependence-brief](../../_includes/instance-groups/sa-dependence-brief.md) %}
{% include [sa-dependence-brief](../../_includes/instance-groups/sa-dependence-brief.md) %}

* Enable **{{ ui-key.yacloud.compute.groups.create.field_deletion-protection }}** if needed. You cannot delete a group with this option enabled.
1. Under **{{ ui-key.yacloud.compute.groups.create.section_allocation }}**, select the required ones in the **{{ ui-key.yacloud.compute.groups.create.field_zone }}** field. Instances of a group may reside in [different availability zones](../../overview/concepts/geo-scope.md).
@@ -20,48 +20,50 @@
* Under **{{ ui-key.yacloud.compute.instances.create.section_image }}**, select a system to be deployed on the VM instance's boot [disk](../../compute/concepts/disk.md).

* Under **{{ ui-key.yacloud.compute.instances.create.section_disk }}**:
* Select the [disk type](../../compute/concepts/disk.md#disks_types).
* Specify the disk size.
* To add more disks, click **{{ ui-key.yacloud.compute.component.instance-storage-dialog.button_add-disk }}**.
* Select the [disk type](../../compute/concepts/disk.md#disks_types).
* Specify the disk size.
* To add more disks, click **{{ ui-key.yacloud.compute.component.instance-storage-dialog.button_add-disk }}**.
* Under **{{ ui-key.yacloud.compute.instances.create.section_platform }}**:
* Choose a [platform](../../compute/concepts/vm-platforms.md).
* Enter the required number of vCPUs, [guaranteed vCPU performance](../../compute/concepts/performance-levels.md), and the amount of RAM.
* Choose a [platform](../../compute/concepts/vm-platforms.md).
* Enter the required number of vCPUs, [guaranteed vCPU performance](../../compute/concepts/performance-levels.md), and the amount of RAM.

* {% include [include](specify-preemptible-vm.md) %}
* {% include [include](specify-preemptible-vm.md) %}

* (Optional) Enable a [software-accelerated network](../../compute/concepts/software-accelerated-network.md).
* (Optional) Enable a [software-accelerated network](../../compute/concepts/software-accelerated-network.md).
* Under **{{ ui-key.yacloud.compute.instances.create.section_network }}**:

{% include [network-settings-group](../../_includes/compute/network-settings-group.md) %}
{% include [network-settings-group](../../_includes/compute/network-settings-group.md) %}

* Under **{{ ui-key.yacloud.compute.instances.create.section_access }}**, specify the information required to access the instance:
* Select a service account to link to the instance.
* If you selected a Linux [image](../../compute/concepts/image.md), fill out the fields **{{ ui-key.yacloud.compute.instances.create.field_user }}** and **{{ ui-key.yacloud.compute.instances.create.field_key }}**. For a key, use the contents of the [public key](../../compute/operations/vm-connect/ssh.md#creating-ssh-keys) file.
* Select `{{ ui-key.yacloud.compute.instances.create.field_serial-port-enable }}`, if needed.
* Under **{{ ui-key.yacloud.compute.instances.create.section_access }}**, specify the data for access to the VM:
* Select a service account to link to the instance.
* If you selected a Linux [image](../../compute/concepts/image.md), fill out the fields **{{ ui-key.yacloud.compute.instances.create.field_user }}** and **{{ ui-key.yacloud.compute.instances.create.field_key }}**. For a key, use the contents of the [public key](../../compute/operations/vm-connect/ssh.md#creating-ssh-keys) file.
* Select `{{ ui-key.yacloud.compute.instances.create.field_serial-port-enable }}`, if needed.
* Click **{{ ui-key.yacloud.compute.groups.create.button_edit }}**.
1. Under **{{ ui-key.yacloud.compute.groups.create.section_deploy }}**:
* In the **{{ ui-key.yacloud.compute.groups.create.field_deploy-max-expansion }}** field, specify the number of instances you can exceed the group size by.

{% include [max-expansion-notice](./max-expansion-notice.md) %}
* In the field **{{ ui-key.yacloud.compute.groups.create.field_deploy-max-unavailable }}**, specify the number of instances you can decrease the group size by.
* In the **{{ ui-key.yacloud.compute.groups.create.field_deploy-max-creating }}** field, specify how many instances can be created at the same time.
* In **{{ ui-key.yacloud.compute.groups.create.field_deploy-startup-duration }}**, specify the period after which the VM instance will start receiving the load.
* In the **{{ ui-key.yacloud.compute.groups.create.field_deploy-max-deleting }}** field, specify how many instances can be stopped at the same time.
* In the **{{ ui-key.yacloud.compute.groups.create.field_deploy-strategy }}** field, specify one of the [strategies](../../compute/concepts/instance-groups/policies/deploy-policy.md#strategy):
* `{{ ui-key.yacloud.compute.groups.create.value_strategy-proactive }}`: {{ ig-name }} itself chooses which instances to stop when updating or scaling down the group.
* `{{ ui-key.yacloud.compute.groups.create.value_strategy-opportunistic }}`: {{ ig-name }} waits for the instances to stop on their own or be stopped by the user.
* `{{ ui-key.yacloud.compute.groups.create.value_strategy-proactive }}`: {{ ig-name }} itself chooses which instances to stop when updating or scaling down the group.
* `{{ ui-key.yacloud.compute.groups.create.value_strategy-opportunistic }}`: {{ ig-name }} waits for the instances to stop on their own or be stopped by the user.
1. Under **{{ ui-key.yacloud.compute.groups.create.section_scale }}**:
* Select the `{{ ui-key.yacloud.compute.groups.create.value_scale-auto }}` [scaling type](../../compute/concepts/instance-groups/scale.md).
* Specify the following:
* **{{ ui-key.yacloud.compute.groups.create.field_auto-scale-type }}**: `{{ ui-key.yacloud.compute.groups.create.value_scale-zonal }}` autoscaling adjusts the number of VM instances separately for each availability zone specified in the group settings. `{{ ui-key.yacloud.compute.groups.create.value_scale-regional }}` is applied to the entire instance group.
* **{{ ui-key.yacloud.compute.groups.create.field_min-zone-size }}**.
* **{{ ui-key.yacloud.compute.groups.create.field_max-size }}**.
* **{{ ui-key.yacloud.compute.groups.create.field_measurement-duration }}** to average the utilization measurements for each instance in the group.
* **{{ ui-key.yacloud.compute.groups.create.field_warmup-duration }}**: Startup duration of an instance in the group.
* **{{ ui-key.yacloud.compute.groups.create.field_cooldown-duration }}**: Interval during which the required number of instances in the group cannot be reduced.
* **{{ ui-key.yacloud.compute.groups.create.field_initial-size }}**.
* **{{ ui-key.yacloud.compute.groups.create.field_auto-scale-type }}**: `{{ ui-key.yacloud.compute.groups.create.value_scale-zonal }}` autoscaling adjusts the number of VM instances separately for each availability zone specified in the group settings. `{{ ui-key.yacloud.compute.groups.create.value_scale-regional }}` does the same for the entire instance group.
* **{{ ui-key.yacloud.compute.groups.create.field_min-zone-size }}**.
* **{{ ui-key.yacloud.compute.groups.create.field_max-size }}**.
* **{{ ui-key.yacloud.compute.groups.create.field_measurement-duration }}** to average the utilization measurements for each instance in the group.
* **{{ ui-key.yacloud.compute.groups.create.field_warmup-duration }}**: Startup duration of an instance in the group.
* **{{ ui-key.yacloud.compute.groups.create.field_cooldown-duration }}**: Interval during which the required number of instances in the group cannot be reduced.
* **{{ ui-key.yacloud.compute.groups.create.field_initial-size }}**.
1. Under **{{ ui-key.yacloud.compute.groups.create.label_custom-metrics }}**, specify:
* In the **{{ ui-key.yacloud.compute.groups.create.field_metric }}** field:
* [{{ ui-key.yacloud.compute.groups.create.metric-type-cpu }}](../../compute/concepts/instance-groups/scale.md#cpu-utilization): Specify the average CPU utilization level that {{ ig-name }} must support.
* [{{ ui-key.yacloud.compute.groups.create.metric-type-custom }}](../../compute/concepts/instance-groups/scale.md#custom-metrics): Specify the name of the custom metric and target value that {{ ig-name }} must support.
* [{{ ui-key.yacloud.compute.groups.create.metric-type-cpu }}](../../compute/concepts/instance-groups/scale.md#cpu-utilization): Specify the average CPU utilization level that {{ ig-name }} must support.
* [{{ ui-key.yacloud.compute.groups.create.metric-type-custom }}](../../compute/concepts/instance-groups/scale.md#custom-metrics): Specify the name of the custom metric and target value that {{ ig-name }} must support.
1. If needed, enable the **{{ ui-key.yacloud.compute.groups.create.section_health-check }}** to get information about the state of instances and their automatic recovery on failure.
* In the **{{ ui-key.yacloud.load-balancer.network-load-balancer.label_health-check-protocol }}** field, select the protocol for the health checks: `{{ ui-key.yacloud.common.label_http }}` or `{{ ui-key.yacloud.common.label_tcp }}`.
* In the **{{ ui-key.yacloud.load-balancer.network-load-balancer.label_health-check-path }}** field (for the HTTP type), specify the URL path for the HTTP check requests sent from {{ ig-name }}.
42 changes: 22 additions & 20 deletions en/_includes/instance-groups/create-fixed-group-via-concole.md
Original file line number Diff line number Diff line change
@@ -1,53 +1,55 @@
1. In the [management console]({{ link-console-main }}), select a folder to create your instance group in.
1. In the [management console]({{ link-console-main }}), select a folder to create your VM group in.
1. In the list of services, select **{{ ui-key.yacloud.iam.folder.dashboard.label_compute }}**.
1. In the left-hand panel, select ![image](../../_assets/console-icons/layers-3-diagonal.svg) **{{ ui-key.yacloud.compute.switch_groups }}**.
1. Click **{{ ui-key.yacloud.compute.groups.button_create }}**.
1. Under **{{ ui-key.yacloud.compute.groups.create.section_base }}**:
* Enter a name and description of the instance group. The naming requirements are as follows:

{% include [name-format](../name-format.md) %}
{% include [name-format](../name-format.md) %}

{% include [name-fqdn](../compute/name-fqdn.md) %}
{% include [name-fqdn](../compute/name-fqdn.md) %}

* Select a [service account](../../iam/concepts/users/service-accounts.md) from the list or create a new one. To be able to create, update, and delete instances in the instance group, assign the `editor` role to the service account. By default, all operations in {{ ig-name }} are performed on behalf of a service account.
* Select a [service account](../../iam/concepts/users/service-accounts.md) from the list or create a new one. To be able to create, update, and delete VM instances in the instance group, assign the `editor` role to the service account. By default, all operations in {{ ig-name }} are performed on behalf of a service account.

{% include [sa-dependence-brief](../../_includes/instance-groups/sa-dependence-brief.md) %}

* Enable the **{{ ui-key.yacloud.compute.groups.create.field_deletion-protection }}** option, if needed. You cannot delete a group with this option enabled.
1. Under **{{ ui-key.yacloud.compute.groups.create.section_allocation }}**, select the required ones in the **{{ ui-key.yacloud.compute.groups.create.field_zone }}** field. Instances of a group may reside in [different availability zones](../../overview/concepts/geo-scope.md).
1. Under **{{ ui-key.yacloud.compute.groups.create.section_allocation }}**, select the required ones in the **{{ ui-key.yacloud.compute.groups.create.field_zone }}** field. VM groups may reside in [different availability zones](../../overview/concepts/geo-scope.md).
1. Under **{{ ui-key.yacloud.compute.groups.create.section_instance }}**, click **{{ ui-key.yacloud.compute.groups.create.button_instance_empty-create }}** to configure a basic instance:
* Under **{{ ui-key.yacloud.compute.instances.create.section_base }}**, enter a description for the [template](../../compute/concepts/instance-groups/instance-template.md).
* Under **{{ ui-key.yacloud.compute.instances.create.section_image }}**, select a system to be deployed on the VM instance's boot [disk](../../compute/concepts/disk.md).

* Under **{{ ui-key.yacloud.compute.instances.create.section_disk }}**:
* Select the [disk type](../../compute/concepts/disk.md#disks_types).
* Specify the disk size.
* To add more disks, click **{{ ui-key.yacloud.compute.component.instance-storage-dialog.button_add-disk }}**.
* Select the [disk type](../../compute/concepts/disk.md#disks_types).
* Specify the disk size.
* To add more disks, click **{{ ui-key.yacloud.compute.component.instance-storage-dialog.button_add-disk }}**.
* Under **{{ ui-key.yacloud.compute.instances.create.section_platform }}**:
* Choose a [platform](../../compute/concepts/vm-platforms.md).
* Enter the required number of vCPUs, [guaranteed vCPU performance](../../compute/concepts/performance-levels.md), and the amount of RAM.
* Choose a [platform](../../compute/concepts/vm-platforms.md).
* Enter the required number of vCPUs, [guaranteed vCPU performance](../../compute/concepts/performance-levels.md), and the amount of RAM.

* {% include [include](specify-preemptible-vm.md) %}

* (Optional) Enable a [software-accelerated network](../../compute/concepts/software-accelerated-network.md).
* {% include [include](specify-preemptible-vm.md) %}
* (Optional) Enable a [software-accelerated network](../../compute/concepts/software-accelerated-network.md).
* Under **{{ ui-key.yacloud.compute.instances.create.section_network }}**:

{% include [network-settings-group](../../_includes/compute/network-settings-group.md) %}
{% include [network-settings-group](../../_includes/compute/network-settings-group.md) %}

* Under **{{ ui-key.yacloud.compute.instances.create.section_access }}**, specify the information required to access the instance:
* Select a service account to link to the instance.
* If you selected a Linux [image](../../compute/concepts/image.md), fill out the fields **{{ ui-key.yacloud.compute.instances.create.field_user }}** and **{{ ui-key.yacloud.compute.instances.create.field_key }}**. For a key, use the contents of the [public key](../../compute/operations/vm-connect/ssh.md#creating-ssh-keys) file.
* Select `{{ ui-key.yacloud.compute.instances.create.field_serial-port-enable }}`, if needed.
* Under **{{ ui-key.yacloud.compute.instances.create.section_access }}**, specify the data for access to the VM:
* Select a service account to link to the instance.
* If you selected a Linux [image](../../compute/concepts/image.md), fill out the fields **{{ ui-key.yacloud.compute.instances.create.field_user }}** and **{{ ui-key.yacloud.compute.instances.create.field_key }}**. For a key, use the contents of the [public key](../../compute/operations/vm-connect/ssh.md#creating-ssh-keys) file.
* Select `{{ ui-key.yacloud.compute.instances.create.field_serial-port-enable }}`, if needed.
* Click **{{ ui-key.yacloud.compute.groups.create.button_edit }}**.
1. Under **{{ ui-key.yacloud.compute.groups.create.section_deploy }}**:
* In the **{{ ui-key.yacloud.compute.groups.create.field_deploy-max-expansion }}** field, specify the number of instances you can exceed the group size by.

{% include [max-expansion-notice](./max-expansion-notice.md) %}
* In the field **{{ ui-key.yacloud.compute.groups.create.field_deploy-max-unavailable }}**, specify the number of instances you can decrease the group size by.
* In the **{{ ui-key.yacloud.compute.groups.create.field_deploy-max-creating }}** field, specify how many instances can be created at the same time.
* In **{{ ui-key.yacloud.compute.groups.create.field_deploy-startup-duration }}**, specify the period after which the VM instance will start receiving the load.
* In the **{{ ui-key.yacloud.compute.groups.create.field_deploy-max-deleting }}** field, specify how many instances can be stopped at the same time.
* In the **{{ ui-key.yacloud.compute.groups.create.field_deploy-strategy }}** field, specify one of the [strategies](../../compute/concepts/instance-groups/policies/deploy-policy.md#strategy):
* `{{ ui-key.yacloud.compute.groups.create.value_strategy-proactive }}`: {{ ig-name }} itself chooses which instances to stop when updating or scaling down the group.
* `{{ ui-key.yacloud.compute.groups.create.value_strategy-opportunistic }}`: {{ ig-name }} waits for the instances to stop on their own or be stopped by the user.
* `{{ ui-key.yacloud.compute.groups.create.value_strategy-proactive }}`: {{ ig-name }} itself chooses which instances to stop when updating or scaling down the group.
* `{{ ui-key.yacloud.compute.groups.create.value_strategy-opportunistic }}`: {{ ig-name }} waits for the instances to stop on their own or be stopped by the user.
1. Under **{{ ui-key.yacloud.compute.groups.create.section_scale }}**:
* Select the `{{ ui-key.yacloud.compute.groups.create.value_scale-fixed }}` [scaling type](../../compute/concepts/instance-groups/scale.md).
* Specify the instance group size.
1 change: 1 addition & 0 deletions en/_includes/instance-groups/max-expansion-notice.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
When bringing the number of VMs in the group to the target value, VMs created in excess of the target under the `max_expansion` quota can remain in the group, while those that existed in the group before may be deleted.
7 changes: 5 additions & 2 deletions en/_includes/managed-gitlab/instance-create-console.md
Original file line number Diff line number Diff line change
@@ -18,12 +18,12 @@ Once an instance is created, you cannot change its resource configuration, i.e.,
1. Under **{{ ui-key.yacloud.gitlab.label_configuration-section }}**:

1. Select the instance type.
1. Specify the [subnet](../../vpc/concepts/network.md#subnet) where the instance will be hosted. Currently, {{ yandex-cloud }} technical restrictions do not allow selecting a subnet with an address range of `192.168.0.0/24`.
1. Specify the [subnet](../../vpc/concepts/network.md#subnet) where the instance will be hosted. Currently, you cannot select a subnet with the `192.168.0.0/24` address range due to {{ yandex-cloud }} technical restrictions.

The [default security group](../../vpc/concepts/security-groups.md#default-security-group) for the selected [network](../../vpc/concepts/network.md#network) will be used for the instance. If you cannot open the {{ GL }} web interface after creating the instance, create a separate security group and [configure it](../../managed-gitlab/operations/configure-security-group.md) so that the rules allow incoming traffic from the required ports and IP addresses.

1. Select the [disk](../../compute/concepts/disk.md) size.
1. Specify the [instance domain name](../../compute/concepts/network.md#hostname): relevant DNS records will be created for it in the `.gitlab.yandexcloud.net` domain.
1. Specify the [instance domain name](../../compute/concepts/network.md#hostname): the required DNS records for this domain name will be automatically created in `.gitlab.yandexcloud.net`.

The domain name must be unique throughout {{ yandex-cloud }}.

@@ -32,6 +32,9 @@ Once an instance is created, you cannot change its resource configuration, i.e.,
* It must not start or end with a dash character.

1. Set up the retention period for automatic backups (in days).
1. (Optional) Enable [code approval rules](../../managed-gitlab/concepts/approval-rules.md). To do this, select the appropriate configuration for approval rules.

{% include [note-approval-rules-pricing](note-approval-rules-pricing.md) %}

1. Under **{{ ui-key.yacloud.gitlab.label_admin-section }}**, specify:
* **{{ ui-key.yacloud.gitlab.field_admin-email }}**: Email address of the {{ GL }} instance administrator. This mailbox will receive an email with a link for creating a password.
Original file line number Diff line number Diff line change
@@ -108,7 +108,7 @@ Where:

* `tls` (`BackendTLS`)

TLC connection settings for the load balancer nodes and backend endpoints.
TLS connection settings for the load balancer nodes and backend endpoints.

If the field is specified, the load balancer established TLS connections with the backend and compares the certificates received to the certificate specified in the `trustedCa` field. If the field is not specified, the load balancer will make unencrypted connections to the backend.

2 changes: 0 additions & 2 deletions en/_includes/mdb/list-operations-about.md

This file was deleted.

19 changes: 14 additions & 5 deletions en/_includes/mdb/mgp/cluster-sg-rules.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,18 @@


Set up the cluster security groups to allow any incoming and outgoing traffic over any protocol. To do this, [create rules](../../../vpc/operations/security-group-add-rule.md) for incoming and outgoing traffic:
1. For incoming traffic:

* **{{ ui-key.yacloud.vpc.network.security-groups.forms.field_sg-rule-port-range }}**: `{{ port-any }}`
* **{{ ui-key.yacloud.vpc.network.security-groups.forms.field_sg-rule-protocol }}**: `{{ ui-key.yacloud.vpc.network.security-groups.forms.value_any }}` (`Any`)
* **{{ ui-key.yacloud.vpc.network.security-groups.forms.field_sg-rule-source }}**: `{{ ui-key.yacloud.vpc.network.security-groups.forms.value_sg-rule-destination-cidr }}`
* **{{ ui-key.yacloud.vpc.network.security-groups.forms.field_sg-rule-cidr-blocks }}**: `0.0.0.0/0`
* **{{ ui-key.yacloud.vpc.network.security-groups.forms.field_sg-rule-port-range }}**: `{{ port-mgp }}`.
* **{{ ui-key.yacloud.vpc.network.security-groups.forms.field_sg-rule-protocol }}**: `{{ ui-key.yacloud.common.label_tcp }}`.
* **{{ ui-key.yacloud.vpc.network.security-groups.forms.field_sg-rule-source }}**: `{{ ui-key.yacloud.vpc.network.security-groups.forms.value_sg-rule-destination-cidr }}`.
* **{{ ui-key.yacloud.vpc.network.security-groups.forms.field_sg-rule-cidr-blocks }}**: Range of addresses to connect from.

1. For outgoing traffic:

* **{{ ui-key.yacloud.vpc.network.security-groups.forms.field_sg-rule-port-range }}**: `{{ port-any }}`.
* **{{ ui-key.yacloud.vpc.network.security-groups.forms.field_sg-rule-protocol }}**: `{{ ui-key.yacloud.vpc.network.security-groups.forms.value_any }}` (`Any`).
* **{{ ui-key.yacloud.vpc.network.security-groups.forms.field_sg-rule-source }}**: `{{ ui-key.yacloud.vpc.network.security-groups.forms.value_sg-rule-destination-cidr }}`.
* **{{ ui-key.yacloud.vpc.network.security-groups.forms.field_sg-rule-cidr-blocks }}**: `0.0.0.0/0`.

This rule enables {{ mgp-name }} to use external data sources, e.g., PXF or GPFDIST.

190 changes: 150 additions & 40 deletions en/_includes/mdb/mgp/dbms-settings.md
Original file line number Diff line number Diff line change
@@ -1,90 +1,200 @@
* **Gp add column inherits table setting** {{ tag-con }} {{ tag-api }} {#setting-gp-add-column-inherits-table-setting}

This setting controls whether to apply the data compression parameters (`compresstype`, `compresslevel`, and `blocksize`) specified for the [AOCO table](../../../managed-greenplum/concepts/tables.md) when adding a column.

By default, the setting is disabled, i.e., the table’s data compression parameters are ignored.

For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#gp_add_column_inherits_table_setting).

* **Gp workfile compression**{#setting-gp-workfile-compression} {{ tag-con }} {{ tag-api }}

This setting determines whether temporary files created on the disk during a hash connection or hash aggregation will be compressed.
This setting determines whether temporary files created on the disk during a hash connection or hash aggregation will be compressed.

By default, it is disabled, i.e., temporary files are not compressed.
By default, it is disabled, i.e., temporary files are not compressed.

For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#gp_workfile_compression).
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#gp_workfile_compression).

* **Gp workfile limits per query**{#setting-gp-workfile-limits} {{ tag-con }} {{ tag-api }}

The maximum amount of disk space (in bytes) the temporary files of an active query can occupy in every segment.
The maximum amount of disk space (in bytes) the temporary files of an active query can occupy in every segment.

The maximum value is `1099511627776` (1 TB), the minimum one is `0` (unlimited amount), and the default one is also `0`.
The maximum value is `1099511627776` (1 TB), the minimum value is `0` (unlimited amount), and the default value is `0`.

For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#gp_workfile_limit_per_query).
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#gp_workfile_limit_per_query).

* **Gp workfile limit files per query**{#setting-gp-workfile-limit-files} {{ tag-con }} {{ tag-api }}

The maximum number of temporary files the service creates in a segment to process a single query. If the limit is exceeded, the query will be canceled.
The maximum number of temporary files the service creates in a segment to process a single query. If the limit is exceeded, the query will be canceled.

The maximum value is `100000`, the minimum one is `0` (unlimited number of temporary files), and the default one is `10000`.
The maximum value is `100000`, the minimum value is `0` (unlimited number of temporary files), and the default value is `10000`.

For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#gp_workfile_limit_files_per_query).
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#gp_workfile_limit_files_per_query).

* **Gp workfile limit per segment**{#setting-gp-workfile-limit-per-segment} {{ tag-con }} {{ tag-api }}

The maximum amount of disk space (in bytes) the temporary files of all active queries can occupy in every segment.
The maximum amount of disk space (in bytes) the temporary files of all active queries can occupy in every segment.

The maximum value is `1099511627776` (1 TB), the minimum value is `0` (unlimited amount). The default value [depends on the segment host storage size](#settings-instance-dependent) and is calculated by the formula:

```text
0.1 × <segment_host_storage_size> / <number_of_segments_per_host>
```
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#gp_workfile_limit_per_segment).
* **Log connections** {{ tag-con }} {#setting-log-connections}
This setting controls whether to log a string detailing each successful connection to the {{ GP }} server.
The setting is disabled by default (no logging).
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#log_connections).
* **Log disconnections** {{ tag-con }} {#setting-log-disconnections}
This setting controls whether to log session completion. If the setting is enabled, after each completed client session, a string with the session duration is output to the log.
The setting is disabled by default (no logging).
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#log_disconnections).
* **Log error verbosity** {{ tag-con }} {#setting-log-error-verbosity}
This setting controls the amount of detail written to the {{ GP }} log for each message. Log detail levels in ascending order of verbosity:
* `terse`.
* `default` (default value).
* `verbose`.
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#log_error_verbosity).
* **Log hostname** {{ tag-con }} {#setting-log-hostname}
This setting controls whether to output the host name of the {{ GP }} database master server to the connection log. If the setting is enabled, the IP address and host name are logged. If the setting is disabled, only the IP address is logged.
This setting is disabled by default.
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#log_hostname).
* **Log min duration statement** {{ tag-con }} {#setting-log-min-duration-statement}
This setting specifies the minimum command duration required to log the command (in milliseconds).
If the value is `0`, the runtime of all commands is logged.
The maximum value is `1099511627776` (1 TB), the minimum one is `0` (unlimited amount). The default value [depends on the segment host storage size](#settings-instance-dependent) and is calculated by the formula:
The minimum value is `-1` (disables runtime logging), the maximum value is `2147483647`. The default value is `-1`.
```text
0.1 × <segment_host_storage_size> / <number_of_segments_per_host>
```
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#log_min_duration_statement).
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#gp_workfile_limit_per_segment).
* **Log min messages** {{ tag-con }} {#setting-log-min-messages}
This setting defines the logging level in {{ GP }}. All messages of the selected severity level (or higher) are logged. Possible values (in ascending order of severity): `DEBUG5`, `DEBUG4`, `DEBUG3`, `DEBUG2`, `DEBUG1`, `INFO`, `NOTICE`, `WARNING`, `ERROR`, `LOG`, `FATAL`, and `PANIC`.
The default value is `WARNING`. This means all the messages with the following severity levels will be logged: `WARNING`, `ERROR`, `LOG`, `FATAL`, and `PANIC`.
To disable logging of most messages, select `PANIC`.
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#log_min_messages).
* **Log statement**{#setting-log-statement} {{ tag-con }} {{ tag-api }}
Filter for SQL statements that will be written to the {{ GP }} log:
Filter for SQL commands that will be written to the {{ GP }} log:
* `NONE`: Filter is disabled, no SQL commands are logged.
* `DDL`: Logs SQL commands used to change data structure definitions (such as `CREATE`, `ALTER`, `DROP` etc.).
* `MOD`: Logs the `DDL` commands and commands allowing you to modify data (`INSERT`, `UPDATE`, `DELETE`, `TRUNCATE`, and `COPY FROM`).
* `ALL`: Logs all SQL commands.
The default value is `ALL`.
The `PREPARE` and `EXPLAIN ANALYZE` expressions are also logged if they contain the relevant types of commands.
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#log_statement).
* **Log statement stats** {{ tag-con }} {#setting-log-statement-stat}
This setting controls whether to log query statistics (parsing, scheduling, execution).
The setting is disabled by default (no logging).
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#log_statement_stats).
* **Master shared buffers** {{ tag-con }} {#setting-master-shared-buffers}
* `NONE`: The filter is disabled and SQL statements are not logged.
* `DDL`: SQL statements that change data definitions are logged (such as `CREATE`, `ALTER`, and `DROP`).
* `MOD`: SQL statements that fall under the `DDL` filter and statements that allow you to change data (`INSERT`, `UPDATE`, `DELETE`, `TRUNCATE`, and `COPY FROM`) are logged.
* `ALL`: All SQL statements are logged.
The amount of memory the {{ GP }} master host uses for shared memory buffers (in bytes).
The default value is `ALL`.
The minimum value is `1048576` (1 MB). The default value is `134217728` (128 MB).
The `PREPARE` and `EXPLAIN ANALYZE` expressions are also logged if they contain the relevant types of commands.
The maximum value is calculated using the following formula:
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#log_statement).
```text
min(<master_host_storage_size> / 4, 8 * <size_of_DB_data>)
```
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#shared_buffers).
{% note warning %}
Changing this setting will restart the cluster.
{% endnote %}
* **Max connections**{#setting-max-connections} {{ tag-con }} {{ tag-api }}
The maximum number of simultaneous connections to a master host.
The maximum number of concurrent connections to the master host.
The maximum value is `1000`, the minimum one is `250`, and the default one is `350`. For segment hosts, this value is automatically multiplied by five.
The maximum value is `1000`, the minimum value is `250`, and the default value is `350`. For segment hosts, this value is automatically multiplied by five.
If you increase this value, we recommend increasing [Max prepared transactions](#setting-max-prepared-transactions) as well.
If you increase this value, we recommend increasing [Max prepared transactions](#setting-max-prepared-transactions) as well.
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#max_connections).
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#max_connections).
* **Max prepared transactions**{#setting-max-prepared-transactions} {{ tag-con }} {{ tag-api }}
Maximum number of concurrent [prepared]({{ pg.docs.org }}/current/sql-prepare-transaction.html) transactions.
The maximum number of transactions that can be in the [prepared state]({{ pg.docs.org }}/current/sql-prepare-transaction.html) at the same time.
The maximum value is `10000`, the minimum one is `350`, and the default one is `350`. The values for master hosts and segment hosts are the same.
The maximum value is `10000`, the minimum value is `350`, and the default value is `350`. The values for master hosts and segment hosts are the same.
We recommend choosing a value higher than [Max connections](#setting-max-connections).
We recommend choosing a value higher than [Max connections](#setting-max-connections).
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#max_prepared_transactions).
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#max_prepared_transactions).
* **Max slot wal keep size**{#setting-max-slot-wal-keep-size} {{ tag-con }} {{ tag-api }}
The maximum [Write-Ahead Log (WAL)](https://www.postgresql.org/docs/current/wal-intro.html) file size in bytes allowed for replication.
The maximum [write-ahead log (WAL)](https://www.postgresql.org/docs/current/wal-intro.html) file size in bytes allowed for replication.
The minimum value is `0` (no logging), the maximum one is `214748364800` (200 GB). The default value [depends on the segment host storage size](#settings-instance-dependent) and is calculated by the formula:
The minimum value is `0` (no logging), and the maximum value is `214748364800` (200 GB). The default value [depends on the segment host storage size](#settings-instance-dependent) and is calculated by the formula:
```text
0.1 × <segment_host_storage_size> / <number_of_segments_per_host>
```
```text
0.1 × <segment_host_storage_size> / <number_of_segments_per_host>
```
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#max_slot_wal_keep_size).
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#max_slot_wal_keep_size).
* **Max statement mem**{#setting-max-statement-mem} {{ tag-con }} {{ tag-api }}
The maximum amount of memory (in bytes) allocated for query processing.
The maximum amount of memory (in bytes) allocated for query processing.
The minimum value is `134217728` (128 MB), the maximum value is `1099511627776` (1 TB), and the default value is `2097152000` (2,000 MB).
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#max_statement_mem).
* **Segment shared buffers** {{ tag-con }} {#setting-segment-shared-buffers}
The amount of memory the {{ GP }} segment hosts use for shared memory buffers (in bytes).
The minimum value is `1048576` (1 MB). The default value is `134217728` (128 MB).
The maximum value is calculated using the following formula:
```text
min(<segment_host_storage_size> / 4 / <number_of_segments_per_host>, 8 * <size_of_DB_data>)
```
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#shared_buffers).
{% note warning %}
The minimum value is `134217728` (128 MB), the maximum one is `1099511627776` (1 TB), and the default one is `2097152000` (2000 MB).
Changing this setting will restart the cluster.
For more information, see the [{{ GP }} documentation]({{ gp.docs.vmware }}/6/greenplum-database/ref_guide-config_params-guc-list.html#max_statement_mem).
{% endnote %}
30 changes: 15 additions & 15 deletions en/_includes/mdb/mgp/limits.md
Original file line number Diff line number Diff line change
@@ -1,23 +1,23 @@
#### Quotas {#quotas}

| Type of limit | Value |
| Type of limit | Value |
|--------------------------------------------------------------------------------|----------|
| Number of clusters per cloud | 16 |
| Total number of processor cores for all database hosts per cloud | 96 |
| Total virtual memory for all database hosts per cloud | 640 GB |
| Total storage capacity for all clusters per cloud | 4096 GB |
| Number of clusters per cloud | 16 |
| Total number of processor cores for all database hosts per cloud | 96 |
| Total virtual memory for all database hosts per cloud | 640 GB |
| Total storage capacity for all clusters per cloud | 4096 GB |


#### Limits {#limits}

| Type of limit | Minimum value | Maximum value |
| Type of limit | Minimum value | Maximum value |
|:--------------------------------------------------------------------------------------------------------------|:-------------------------------------------------|:-------------------------------------------------|
| Host class | s2.medium (8 vCPU Intel Cascade Lake, 32 GB RAM) | i3-c40-m320 (40 vCPU Intel Ice Lake, 320 GB RAM) |
| Number of master hosts in the cluster | 2 | 2 |
| Number of segment hosts in the cluster | 2 | 32 |
| Number of segments per host | 1 | 16 |
| Amount of data on the host when using HDD network storage | 10 GB | 2048 GB |
| Amount of data on the host when using network SSD storage | 10 GB | 8192 GB |
| Amount of host data when using non-replicated SSD storage (for segment hosts only) | 93 GB | 8184 GB |
| Amount of data on the host when using local SSD storage (for Intel Cascade Lake) | 100 GB | 1500 GB |
| Amount of data on the host when using local SSD storage (for Intel Ice Lake) | {{ local-ssd-v3-step }} | {{ local-ssd-v3-max }} |
| Host class | s2.medium (8 vCPU Intel Cascade Lake, 32 GB RAM) | i3-c40-m320 (40 vCPU Intel Ice Lake, 320 GB RAM) |
| Number of master hosts in the cluster | 2 | 2 |
| Number of segment hosts in the cluster | 2 | 32 |
| Number of segments per host | 1 | 16 |
| Amount of data on the host when using HDD network storage | 10 GB | 2048 GB |
| Amount of data per host when using network SSD storage | 10 GB | 8,192 GB |
| Amount of data per host when using non-replicated SSD storage | 93 GB | 8184 GB |
| Amount of data on the host when using local SSD storage (for Intel Cascade Lake) | 100 GB | 1500 GB |
| Amount of data per host when using local SSD storage (for Intel Ice Lake) | {{ local-ssd-v3-step }} | {{ local-ssd-v3-max }} |
2 changes: 0 additions & 2 deletions en/_includes/mdb/mkf-list-operations-about.md

This file was deleted.

4 changes: 2 additions & 2 deletions en/_includes/mdb/mmg-readonly-safeguard.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
If at least one host in a {{ mmg-name }} cluster runs out of allocated disk space, the {{ MG }} instance on this host will crash and the host will be disabled. If the host was a [`PRIMARY` replica](../../managed-mongodb/concepts/replication.md), this role will be assigned to one of the `SECONDARY` replicas. As a result of migrating the `PRIMARY` role from one host to another, you may run out of disk space on all hosts in the cluster, which will result in a complete cluster failure.
If at least one host in a {{ mmg-name }} cluster runs out of its allocated disk space, the {{ MG }} instance on this host will crash and the host will be disabled. If this host was a [`PRIMARY` replica](../../managed-mongodb/concepts/replication.md), this role will be assigned to one of the `SECONDARY` replicas. As a result of migrating the `PRIMARY` role from one host to another, you may run out of disk space on all hosts in the cluster, which will result in a complete cluster failure.

To avoid this, {{ mmg-name }} monitors disk space in use and automatically enables read-only mode (using the [`db.fsyncLock` method](https://docs.mongodb.com/manual/reference/method/db.fsyncLock/)) for those hosts in the cluster that have:
To avoid this, {{ mmg-name }} monitors disk space in use and automatically enables _read-only_ mode (using the [`db.fsyncLock` method](https://docs.mongodb.com/manual/reference/method/db.fsyncLock/)) for those hosts in the cluster that have:

* Less than 500 MB of free disk space left (if the host storage size is less than 600 GB).
* Less than 5 GB of free disk space left (if the host storage size is 600 GB or more).
2 changes: 1 addition & 1 deletion en/_includes/mdb/mmg/note-info-db-name-limits.md
Original file line number Diff line number Diff line change
@@ -1 +1 @@
A database name may contain Latin letters, numbers, underscores, and hyphens. The name may be up to 63 characters long. Such names as `config`, `local`, `admin`, and `mdb_internal` are reserved for {{ mmg-name }}. You cannot create DBs with these names.
A database name may contain Latin letters, numbers, underscores, and hyphens. The name may be up to 63 characters long. Such names as `config`, `local`, `admin`, and `mdb_internal` are reserved for {{ mmg-name }}. You cannot create DBs with these names.
6 changes: 3 additions & 3 deletions en/_includes/mdb/mmg/settings-host-class.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@

Under **{{ ui-key.yacloud.mdb.forms.section_resource }}**, select:

* One of the available [platforms](../../../compute/concepts/vm-platforms.md)
* Configuration type: **memory-optimized**, **standard**, or **burstable**.
* [Host class](../../../managed-mongodb/concepts/instance-types.md): Defines the technical specifications of the VMs where the DB hosts will be deployed. When you change the host class for the cluster, the characteristics of all existing hosts change, too.
* One of the available [platforms](../../../compute/concepts/vm-platforms.md).
* Configuration type: **memory-optimized**, **cpu-optimized**, **standard**, or **burstable**.
* [Host class](../../../managed-mongodb/concepts/instance-types.md): Defines the technical specifications of the VMs where the DB hosts will be deployed. When you change the host class for the cluster, the characteristics of all existing hosts change, too.

32 changes: 16 additions & 16 deletions en/_includes/mdb/mmy-limits.md
Original file line number Diff line number Diff line change
@@ -1,22 +1,22 @@
#### Quotas {#mmy-quotas}

| Type of limit | Value |
| Type of limit | Value |
|:-------------------------------------------------------------------------------|:---------|
| Number of clusters per cloud | 16 |
| Total number of processor cores for all database hosts per cloud | 96 |
| Total virtual memory for all database hosts per cloud | 640 GB |
| Total storage capacity for all clusters per cloud | 4096 GB |
| Number of clusters per cloud | 16 |
| Total number of processor cores for all database hosts per cloud | 96 |
| Total virtual memory for all database hosts per cloud | 640 GB |
| Total storage capacity for all clusters per cloud | 4,096 GB |

#### Limits {#mmy-limits}

| Type of limit | Minimum value | Maximum value |
|:------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------------------------------------|
| Host class | b1.medium (2 × [50%](../../compute/concepts/performance-levels.md) vCPU Intel Broadwell, 4 GB RAM) | m3-c80-m640 (80 vCPU Intel Cascade Lake, 640 GB RAM) |
| Number of hosts per cluster when using HDD or SSD network storage | 1 | 7 |
| Number of hosts per cluster when using non-replicated SSD or local SSD storage | 3 | 7 |
| Amount of data per host when using network SSD storage | 10 GB | 6144 GB |
| Amount of data per host when using network HDD storage | 10 GB | 2048 GB |
| Amount of data per host when using non-replicated SSD storage | 93 GB | 8184 GB |
| Amount of data per host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake) | 100 GB | 1500 GB |
| Amount of data per host when using local SSD storage (for Intel Ice Lake) | {{ local-ssd-v3-step }} | {{ local-ssd-v3-max }} |
| Number of databases per cluster | 1 | {{ all-mdb.max-databases }} |
| Type of limit | Minimum value | Maximum value |
|:------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------------------------------------------------------------------|:-----------------------------------------------------|
| Host class | b1.medium (2 × [50%](../../compute/concepts/performance-levels.md) vCPU Intel Broadwell, 4 GB RAM) | m3-c80-m640 (80 vCPU Intel Cascade Lake, 640 GB RAM) |
| Number of hosts per cluster when using HDD or SSD network storage | 1 | 7 |
| Number of hosts per cluster when using non-replicated SSD or local SSD storage | 3 | 7 |
| Amount of data per host when using network SSD storage | 10 GB | 6,144 GB |
| Amount of data per host when using network HDD storage | 10 GB | 2,048 GB |
| Amount of data per host when using non-replicated SSD storage | 93 GB | 8,184 GB |
| Amount of data per host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake) | 100 GB | 1,500 GB |
| Amount of data per host when using local SSD storage (for Intel Ice Lake) | {{ local-ssd-v3-step }} | {{ local-ssd-v3-max }} |
| Number of databases per cluster | 1 | {{ all-mdb.max-databases }} |
12 changes: 6 additions & 6 deletions en/_includes/mdb/monitoring-cluster-health.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
| State | Description | Suggested actions |
| :--- | :--- | :--- |
| **ALIVE** | Cluster is operating normally. | No action is required. |
| **DEGRADED** | Cluster is not running at its full capacity: the state of at least one of the hosts is other than `ALIVE`. | Run the diagnostics:<ul><li>Go to the **{{ ui-key.yacloud.mdb.cluster.hosts.label_title }}** tab and see which hosts are not alive.</li><li>Go to the **{{ ui-key.yacloud.common.operations-key-value }}** tab and make sure all of them are completed.</li><li>Check that the cluster is not under maintenance.</li></ul>If you cannot find the cause yourself, [contact support]({{ link-console-support }}). |
| **DEAD** | Cluster is out of order: all of its hosts are down. | [Prepare an application to support]({{ link-console-support }}) stating the following:<ul><li>Cluster ID.</li><li>IDs of the last operations performed on it.</li><li>Time the cluster entered the `DEAD` state according to the [availability charts](#monitoring-cluster).</li></ul> |
| **UNKNOWN** | Cluster state is unknown. | [Prepare an application to support]({{ link-console-support }}) stating the following:<ul><li>Cluster ID.</li><li>IDs of the last operations performed on it.</li><li>Time the cluster entered the `UNKNOWN` state according to the [availability charts](#monitoring-cluster).</li></ul> |
State | Description | Suggested actions
:--- | :--- | :---
**ALIVE** | Cluster is operating normally. | No action is required.
**DEGRADED** | Cluster is not running at its full capacity: the state of at least one of the hosts is other than `ALIVE`. | Run the diagnostics:<ul><li>Go to the **{{ ui-key.yacloud.mdb.cluster.hosts.label_title }}** tab and see which hosts are not working.</li><li>Go to the **{{ ui-key.yacloud.common.operations-key-value }}** tab and make sure all operations are completed.</li><li>Make sure the cluster is not under maintenance.</li></ul>If you cannot find the cause yourself, [contact support]({{ link-console-support }}).
**DEAD** | The cluster is down: none of its hosts are running. | [Make a support request]({{ link-console-support }}) stating the following:<ul><li>Cluster ID.</li><li>IDs of the last operations performed on it.</li><li>Time the cluster entered the `DEAD` state according to the [availability charts](#monitoring-cluster).</li></ul>
**UNKNOWN** | Cluster state is unknown. | [Make a support request]({{ link-console-support }}) stating the following:<ul><li>Cluster ID.</li><li>IDs of the last operations performed on it.</li><li>Time the cluster entered the `UNKNOWN` state according to the [availability charts](#monitoring-cluster).</li></ul>
18 changes: 9 additions & 9 deletions en/_includes/mdb/monitoring-cluster-status.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
| Status | Description | Suggested actions |
Status | Description | Suggested actions
:--- | :--- | :---
| **CREATING** | Preparing for the first launch | Wait a while and get started. The time it takes to create a cluster depends on the host class. |
| **RUNNING** | Cluster is operating normally | No action is required. |
| **STOPPING** | Stopping | After a while, the cluster's status will change to `STOPPED` and it will be disabled. No action is required. |
| **STOPPED** | Stopped | For instructions on how to restart it, see **Stopping and restarting a cluster**. |
| **STARTING** | Starting the cluster that was stopped earlier | After a while, the cluster's status will change to `RUNNING`. Wait a while and get started. |
| **UPDATING** | Updating the cluster status | After the update is completed, the cluster's status will change to `RUNNING`. Wait a while and get started. |
| **ERROR** | An error occurred that does not allow the cluster to continue working | Run the initial diagnostics:<ul><li>Analyze the cluster's [monitoring charts](#monitoring-cluster) and view operations that were performed in it.</li><li>Prepare a list of IDs of problem resources.</li></ul>If you cannot find the cause of the error yourself, [contact support]({{ link-console-support }}). |
| **STATUS_UNKNOWN** | Cluster is unable to determine its own status | Run the initial diagnostics:<ul><li>Analyze the cluster's [monitoring charts](#monitoring-cluster) and view operations that were performed in it.</li><li>Prepare a list of IDs of problem resources.</li></ul>If you cannot find the cause of the error yourself, [contact support]({{ link-console-support }}). |
**CREATING** | Preparing for the first launch | Wait a while and get started. The time it takes to create a cluster depends on the host class.
**RUNNING** | Cluster is operating normally | No action is required.
**STOPPING** | Stopping cluster | After a while, the cluster status will change to `STOPPED` and the cluster will be disabled. No action is required.
**STOPPED** | Cluster stopped | Start the cluster to get it running again.
**STARTING** | Starting the cluster that was stopped earlier | After a while, the cluster status will change to `RUNNING`. Wait a while and get started.
**UPDATING** | Updating the cluster status | After the update is completed, the cluster status will change to `RUNNING`. Wait a while and get started.
**ERROR** | An error occurred that does not allow the cluster to continue working | Run the initial diagnostics:<ul><li>Analyze the cluster [monitoring charts](#monitoring-cluster) and view the operations performed.</li><li>Prepare a list of IDs of problem resources.</li></ul>If you cannot find the cause of the error yourself, [contact support]({{ link-console-support }}).
**STATUS_UNKNOWN** | Cluster is unable to determine its own status | Run the initial diagnostics:<ul><li>Analyze the cluster [monitoring charts](#monitoring-cluster) and view the operations performed.</li><li>Prepare a list of IDs of problem resources.</li></ul>If you cannot find the cause of the error yourself, [contact support]({{ link-console-support }}).
8 changes: 0 additions & 8 deletions en/_includes/mdb/mpg/performance-diagnostics-api.md

This file was deleted.

34 changes: 17 additions & 17 deletions en/_includes/mdb/mrd-limits.md
Original file line number Diff line number Diff line change
@@ -1,28 +1,28 @@
#### Quotas {#mrd-quotas}

| Type of limit | Value |
| Type of limit | Value |
|:-------------------------------------------------------------------------------|:---------|
| Number of clusters per cloud | 16 |
| Total number of processor cores for all database hosts per cloud | 64 |
| Total virtual memory for all database hosts per cloud | 512 GB |
| Total storage capacity for all clusters per cloud | 4,096 GB |
| Number of clusters per cloud | 16 |
| Total number of processor cores for all database hosts per cloud | 64 |
| Total virtual memory for all database hosts per cloud | 512 GB |
| Total storage capacity for all clusters per cloud | 4,096 GB |

#### Limits {#mrd-limits}


| Type of limit | Minimum value | Maximum value |
| Type of limit | Minimum value | Maximum value |
|:----------------------------------------------------------------------------------------------------------|:--------------------------------------|:--------------------------------------------------|
| Host class | b2.medium (`burstable`, 4 GB RAM) | hm3-c32-m512 (32 vCPU Intel Ice Lake, 512 GB RAM) |
| Number of hosts in an unsharded cluster | 1 or 3 depending on the [disk type](../../managed-redis/concepts/storage.md#storage-type-selection) | 7 |
| Number of shards in a sharded cluster | 1 | 10 |
| Number of hosts per shard when using network SSD storage | 1 | 7 |
| Number of hosts per shard when using local SSD storage^*^ | 2 | 7 |
| Number of hosts per shard when using non-replicated SSD storage^*^ | 3 | 7 |
| Number of hosts in a sharded cluster | 1, 2, or 3 hosts depending on the [disk type](../../managed-redis/concepts/storage.md#storage-type-selection) | 70 (10 shards, 7 hosts) |
| Amount of data per host when using network SSD storage | Twice the amount of selected RAM | 4096 GB |
| Amount of data per host when using non-replicated SSD storage^*^ | Twice the amount of selected RAM, at least 93 GB | 8184 GB |
| Amount of data per host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake)^*^ | Twice the amount of selected RAM, at least 100 GB | 1500 GB |
| Amount of data per host when using local SSD storage (for Intel Ice Lake)^*^ | Twice the amount of selected RAM, at least {{ local-ssd-v3-step }} | {{ local-ssd-v3-max }} |
| Host class | b2.medium (`burstable`, 4 GB RAM) | hm3-c32-m512 (32 vCPU Intel Ice Lake, 512 GB RAM) |
| Number of hosts in an unsharded cluster | 1 or 3 depending on the [disk type](../../managed-redis/concepts/storage.md#storage-type-selection) | 7 |
| Number of shards in a sharded cluster | 1 | 10 |
| Number of hosts per shard when using network SSD storage | 1 | 7 |
| Number of hosts per shard when using local SSD storage^*^ | 2 | 7 |
| Number of hosts per shard when using non-replicated SSD storage^*^ | 3 | 7 |
| Number of hosts in a sharded cluster | 1, 2, or 3 hosts depending on the [disk type](../../managed-redis/concepts/storage.md#storage-type-selection) | 70 (10 shards, 7 hosts) |
| Amount of data per host when using network SSD storage | Twice the amount of selected RAM | 4,096 GB |
| Amount of data per host when using non-replicated SSD storage^*^ | Twice the amount of selected RAM, at least 93 GB | 8,184 GB |
| Amount of data per host when using local SSD storage (for Intel Broadwell and Intel Cascade Lake)^*^ | Twice the amount of selected RAM, at least 100 GB | 1,500 GB |
| Amount of data per host when using local SSD storage (for Intel Ice Lake)^*^ | Twice the amount of selected RAM, at least {{ local-ssd-v3-step }} | {{ local-ssd-v3-max }} |
| Number of cluster connections || 65,000 |

{% include [storage-limitations-mrd](./mrd/storage-limitations-note.md) %}
4 changes: 2 additions & 2 deletions en/_includes/mdb/mrd/conn-strings-non-sharded.md
Original file line number Diff line number Diff line change
@@ -166,7 +166,7 @@
Password: "<password>",
ReadOnly: false,
TLSConfig: &tls.Config{
RootCAs: rootCertPool,
RootCAs: rootCertPool,
},
},
)
@@ -284,7 +284,7 @@
String redisPass = "<cluster_password>";
System.setProperty("javax.net.ssl.trustStore", "/home/<home_directory>/.redis/YATrustStore");
System.setProperty("javax.net.ssl.trustStorePassword", "<password_to_secure_certificate_storage>");
System.setProperty("javax.net.ssl.trustStorePassword", "<secure_certificate_storage_password>");
SSLParameters sslParameters = new SSLParameters();
DefaultJedisClientConfig jedisClientConfig = DefaultJedisClientConfig.builder().
5 changes: 3 additions & 2 deletions en/_includes/mdb/sg-rules-limits.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
[Security groups](../../vpc/concepts/security-groups.md) follow the _All traffic that is not allowed is prohibited_ principle. To connect to a cluster, security groups must include rules allowing traffic from certain ports, IP addresses, or other security groups.
[Security groups](../../vpc/concepts/security-groups.md) follow the _All traffic that is not allowed is prohibited_ principle. To connect to a cluster, configure security group rules. These rules allow traffic from certain ports, IP addresses, or other security groups. For example, a VM will not be able to connect to a cluster in the following cases:

For example, let's assume a VM in {{ yandex-cloud }} is used to access the cluster. In this case, if only the 10.133.0.0/24 subnet is specified in the incoming traffic rules for the security group, while the VM is in the 10.128.0.0/16 subnet, the VM will not be able to connect to the cluster. A VM from the 10.133.0.0/24 subnet will not be able to connect either, in case it tries to access a port that is not specified in the security group rules.
* The VM is in subnet 10.128.0.0/16, whereas the incoming traffic rules only specify subnet 10.133.0.0/24.
* The VM is in subnet 10.133.0.0/24 but attempts to access a port not specified in the security group rules.
1 change: 1 addition & 0 deletions en/_includes/notifications/about-service.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{{ cns-name }} ({{ cns-short-name }}) is a service for multichannel notifications of users. The service's HTTP API is compatible with the [Amazon SNS API](https://docs.aws.amazon.com/sns/latest/api/welcome.html).
1 change: 1 addition & 0 deletions en/_includes/notifications/ask-for-turning-on.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
To enable {{ cns-name }}, request access to the service from your account manager or [technical support]({{ link-console-support }}).
13 changes: 13 additions & 0 deletions en/_includes/notifications/auth-apns.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
You can authenticate with APNs using either a _token_ or a _certificate_:
* To authenticate using a token, you will need the following data:
* **Token**: To get a token in `.p8` format, create an authentication key in your Apple developer account: **Certificates, Identifiers & Profiles****Keys**![image](../../_assets/console-icons/circle-plus-fill.svg). You can download the token file only once.
* **Token ID**: Get the ID in your Apple developer account: **Certificates, Identifiers & Profiles****Keys**. Make sure the ID matches the token you want to use. It must be 10 characters long.
* **Team ID**: You can find it in the top-right corner of your Apple developer account. It must be 10 characters long and contain only numbers and Latin letters.
* **Bundle ID**: Get the [bundle ID](https://developer.apple.com/documentation/appstoreconnectapi/list_bundle_ids) in your Apple developer account: **Certificates, Identifiers & Profiles****Identifiers** or in the Xcode app: **Target****General****Identity**. It may contain only numbers, Latin letters, hyphens, and periods.
* To authenticate using a certificate, you will need the following data:
* **Certificate**: SSL certificate file in `.p12` format.
* **Certificate private key**.

For more information about the certificate, see the [Apple documentation](https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/establishing_a_certificate-based_connection_to_apns#2947597).

Token-based authentication is preferred as it is more progressive.
11 changes: 11 additions & 0 deletions en/_includes/notifications/auth-fcm.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
You can authenticate with FCM using either the _HTTP v1 API_ or _Legacy API_:
* To authenticate using the HTTP v1 API, you will need a **Google Cloud service account key in JSON format**. The key is used to generate OAuth 2.0 temporary tokens for authenticating requests in the FCM HTTP v1 API. You can get it in the Google Cloud management console.
* To authenticate using the Legacy API, you will need an **API key** (server key). You can get it in the Firebase management console.

{% note info %}

The HTTP v1 API is preferred as [FCM will no longer support](https://firebase.google.com/docs/cloud-messaging/migrate-v1) the Legacy API starting from June 2024.

{% endnote %}

See more in the [Firebase documentation](https://firebase.google.com/docs/cloud-messaging/android/client).
5 changes: 5 additions & 0 deletions en/_includes/notifications/auth-hms.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
You can authenticate with HMS using the following parameters:
* **Key ID**
* **API key**

See more in the [HMS documentation](https://developer.huawei.com/consumer/en/doc/hmscore-common-Guides/get-started-hmscore-0000001212585589).
3 changes: 3 additions & 0 deletions en/_includes/notifications/channels-push-preview.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
At the preview stage, you can send personalized [push notifications](../../notifications/concepts/push.md) to iOS and Android devices as well as [text messages (SMS)](../../notifications/concepts/sms.md).

Moving forward, we will add notifications to messengers and browsers.
9 changes: 9 additions & 0 deletions en/_includes/notifications/common-sender-description.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
An SMS notification channel with a _shared sender_ is a good option for testing the service's features and has the following advantages:
* You do not have to register the sender's name with the telecom operator.
* No monthly subscription fee is charged.

There are restrictions in place for this type of sender:
* All SMS messages are signed with a shared service name.
* Promotional SMS messages are not allowed.
* A [cloud](../../resource-manager/concepts/resources-hierarchy.md#cloud) can contain only one SMS notification channel with a shared sender.
* A channel can only operate in a [sandbox](../../notifications/concepts/sms.md#sandbox) with a limited number of test phone numbers.
1 change: 1 addition & 0 deletions en/_includes/notifications/individual-in-sandbox.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
The SMS notification channel with an individual sender is originally created in the sandbox.
8 changes: 8 additions & 0 deletions en/_includes/notifications/individual-sender-description.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
An SMS notification channel with an _individual sender_ is suitable for the product environment and has the following advantages:
* All SMS messages are signed with the sender's unique text name.
* After leaving the [sandbox](#sandbox) you can send SMS to any Russian phone numbers in [E.164](https://en.wikipedia.org/wiki/E.164) format.

There are restrictions and rules in place for this type of sender:
* The sender's text name will be registered with the service provider.
* You will be charged a monthly subscription fee for using the sender's text name.
* In the [cloud](../../resource-manager/concepts/resources-hierarchy.md#cloud), one sender's text name can correspond to one SMS notification channel.
5 changes: 5 additions & 0 deletions en/_includes/notifications/limits-warning.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{% note info %}

The service is subject to limitations. For more information, see [{#T}](../../notifications/concepts/limits.md).

{% endnote %}
5 changes: 5 additions & 0 deletions en/_includes/notifications/preview-stage.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{% note info %}

The service is at the [preview stage](../../overview/concepts/launch-stages.md).

{% endnote %}
5 changes: 5 additions & 0 deletions en/_includes/notifications/registration-duration-warning.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{% note info %}

Registering a sender's text name may take from 2 to 4 weeks.

{% endnote %}
8 changes: 8 additions & 0 deletions en/_includes/notifications/sa-role-static-key.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
For authentication in {{ cns-name }}, use a [static access key](../../iam/concepts/authorization/access-key.md). The key is issued for the [service account](../../iam/concepts/users/service-accounts.md), and all actions are performed on behalf of that service account.

To get a static access key:
1. [Create](../../iam/operations/sa/create.md) a service account.
1. [Assign](../../iam/operations/sa/assign-role-for-sa.md) the service account the `editor` [role](../../iam/roles-reference.md#editor) for the folder.
1. [Create](../../iam/operations/sa/create-access-key.md) a static access key for the service account.

Save the ID and private key.
3 changes: 3 additions & 0 deletions en/_includes/notifications/sandbox-test-numbers.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
A _sandbox_ is a test environment, in which you can send SMS messages only to _test phone numbers_.

Each test phone number is registered in a channel using a confirmation code from an SMS. By adding a number, you agree to receive messages to it.
1 change: 1 addition & 0 deletions en/_includes/notifications/sms-quota-increase.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
You can also request an increase in the service quotas together with your request to exit the sandbox mode.
1 change: 1 addition & 0 deletions en/_includes/notifications/sms-short-description.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
With {{ cns-name }}, you can send [text messages (SMS)](https://en.wikipedia.org/wiki/SMS) using _SMS notification channels_. Russian phone numbers in [E.164](https://en.wikipedia.org/wiki/E.164) format are supported, e.g., `+79991112233`. SMS messages are signed with sender text names. The maximum length of one SMS is 160 Latin characters or 70 Cyrillic characters. Longer texts are sent using multiple SMS messages.
17 changes: 17 additions & 0 deletions en/_includes/organization/os-login-cli-organization-list.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
Get the ID of the organization which contains the required OS Login profile of a user or [service account](../../iam/concepts/users/service-accounts.md):

```bash
yc organization-manager organization list
```

Result:

```text
+----------------------+-------------------------+-------------------------+
| ID | NAME | TITLE |
+----------------------+-------------------------+-------------------------+
| bpf1smsil5q0******** | sample-organization1 | Organization 1 |
| bpf2c65rqcl8******** | sample-organization2 | Organization 2 |
| bpf6dne49ue8******** | sample-organization3 | Organization 3 |
+----------------------+-------------------------+-------------------------+
```
20 changes: 20 additions & 0 deletions en/_includes/organization/os-login-cli-profile-list.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
Get a list of logins in the OS Login profiles of an organization's users and service accounts by specifying its ID:

```bash
yc organization-manager os-login profile list \
--organization-id <organization_ID>
```

Result:

```text
+----------------------+----------------------+-----------+----------------------+----------------------+------------+
| ID | LOGIN | UID | ORGANIZATION ID | SUBJECT ID | IS DEFAULT |
+----------------------+----------------------+-----------+----------------------+----------------------+------------+
| aje1eb5qm7jb******** | yc-sa-my-service-acc | 487816044 | bpfaidqca8vd******** | ajevnu4u2q3m******** | true |
| ajegs81t2k9s******** | user1 | 760684761 | bpfaidqca8vd******** | aje7b4u65nb6******** | true |
| ajej57b2kf0t******** | user2 | 1011 | bpfaidqca8vd******** | ajei280a73vc******** | true |
+----------------------+----------------------+-----------+----------------------+----------------------+------------+
```

Save the `LOGIN` field value for the required user or service account: you will need it later.
11 changes: 11 additions & 0 deletions en/_includes/organization/os-login-roles-needed-for-vm-access.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
{% list tabs %}

- Connecting via the YC CLI

To connect to a virtual machine or {{ k8s }} node with OS Login access enabled via the [YC CLI](../../cli/quickstart.md), the user or [service account](../../iam/concepts/users/service-accounts.md) under which you will run the YC CLI command needs the `compute.osLogin` or `compute.osAdminLogin` role, as well as the `compute.operator` role.

- Connecting via a standard SSH client

To connect to a virtual machine or {{ k8s }} node with OS Login access enabled via a standard SSH client, the user or [service account](../../iam/concepts/users/service-accounts.md) used for connection needs the `compute.osLogin` or `compute.osAdminLogin` role.

{% endlist %}
1 change: 0 additions & 1 deletion en/_includes/organization/os-login-yc-cli-roles-needed.md

This file was deleted.

2 changes: 1 addition & 1 deletion en/_includes/pricing/currency-choice.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{% note info %}

Currency of Service rates (prices) depends on the company you made a contract with:
* Prices in US dollars are applicable to customers of Iron Hive doo Beograd (Serbia).
* Prices in US dollars are applicable to customers of Iron Hive doo Beograd (Serbia) or Direct Cursus Technology L.L.C. (Dubai).
* Prices in Russian roubles are applicable to customers of Yandex.Cloud LLC.

{% endnote %}
2 changes: 1 addition & 1 deletion en/_includes/pricing/use-calculator.md
Original file line number Diff line number Diff line change
@@ -1 +1 @@
To calculate the cost of using the service, use the [calculator]({{ link-cloud-calculator }}) on the {{ yandex-cloud }} website or see the prices in this section.
To calculate the cost of using the service, use the [calculator]({{ link-cloud-calculator }}) on the {{ yandex-cloud }} website or see the pricing in this section.
6 changes: 2 additions & 4 deletions en/_includes/quickstart-all-no-billing.md
Original file line number Diff line number Diff line change
@@ -30,10 +30,8 @@
* [Manage data streams in {{ yds-name }}](../data-streams/quickstart/index.md).
* [Use {{ iot-name }} as your framework for smart home development](../iot-core/quickstart.md).
* Databases and clusters:
* [{{ CH }}](../managed-clickhouse/quickstart.md).
* [{{ MG }}](../managed-mongodb/quickstart.md).
* [{{ MY }}](../managed-mysql/quickstart.md).
* [{{ RD }}](../managed-redis/quickstart.md).
* [{{ CH }}](../managed-clickhouse/quickstart.md).
* [{{ MY }}](../managed-mysql/quickstart.md).
* [{{ PG }}](../managed-postgresql/quickstart.md).

* [{{ OS }}](../managed-opensearch/quickstart.md).
4 changes: 2 additions & 2 deletions en/_includes/security-deck/sd-limits.md
Original file line number Diff line number Diff line change
@@ -4,7 +4,7 @@ Type of limit | Value
--- | ---
Number of scanning sessions per folder | 10,000
Number of data sources per folder | 1,000
Number of files per bucket to scan | 1,000
Number of files per bucket to scan | 500
Number of results per scanning session | 1,000
Number of results per file | 1,000
Number of results for a particular data type per file | 500
Number of results for a particular data type per file | 500
17 changes: 5 additions & 12 deletions en/_includes/smartcaptcha/captcha-validation.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
After validating a request, {{ captcha-name }} assigns it an ID: a one-time token. You can use the token to retrieve the result of a user request validation from the service. The token is valid for five minutes. After this time expires, it becomes invalid and the user has to go through the validation process again.

After validation, the token is loaded into the `<input type="hidden" name="smart-token" value="<token>" ...>` element on the user's page. For example:
After validation, the token is loaded into the `<input type="hidden" name="smart-token" value="<token>" ...>` element on the user page. Here is an example:

```HTML
<div id="captcha-container" class="smart-captcha" ...>
@@ -14,17 +14,10 @@ Where:
* `<div id="captcha-container" class="smart-captcha" ...>`: `div` element with a widget.
* `value`: Token value.

To find out the result of the validation, send a POST request to `https://smartcaptcha.yandexcloud.net/validate`:
To find out the result of the validation, send a POST request to `https://smartcaptcha.yandexcloud.net/validate` providing parameters in `x-www-form-urlencoded` format:

```HTML
response = requests.post(
"https://smartcaptcha.yandexcloud.net/validate",
{
"secret": SMARTCAPTCHA_SERVER_KEY,
"token": token,
"ip": "<user_IP_address>"
}
)
```
secret=<server_key>&token=<token>&ip=<user_IP_address>
```

Where:
@@ -85,7 +78,7 @@ In its response, the service will return a JSON object containing the `status` a

## Request errors {#errors}

If your request to `https://smartcaptcha.yandexcloud.net/validate` is incorrect, the service will return an error. For example:
If your request to `https://smartcaptcha.yandexcloud.net/validate` is incorrect, the service will return an error. Here is an example:

1. Request missing the server key:

2 changes: 1 addition & 1 deletion en/_includes/smartwebsecurity/sum-cloud-account.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
Billing is based on the number of requests across all [clouds](../../resource-manager/concepts/resources-hierarchy.md#cloud) linked to a single [billing account](../../billing/concepts/billing-account.md).

You pay for the actual number of legitimate requests. For each request you are charged for:
You pay for the actual number of legitimate requests. For each request, you are charged for:

* Processing with security profile rules, both [basic](../../smartwebsecurity/concepts/rules.md#base-rules) and [Smart Protection](../../smartwebsecurity/concepts/rules.md#smart-protection-rules) ones.

200 changes: 200 additions & 0 deletions en/_includes/speechkit/transcribe-result-example.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,200 @@
{% cut "Result example" %}

```bash
[session_uuid {
uuid: "df49eaa2-25a55218-ae967fa1-********"
user_request_id: "f8dkup42nmhk********"
}
audio_cursors {
received_data_ms: 6600
partial_time_ms: 6600
final_time_ms: 6600
}
response_wall_time_ms: 204
final {
alternatives {
words {
text: "I"
start_time_ms: 380
end_time_ms: 420
}
words {
"text": "Yandex"
start_time_ms: 539
end_time_ms: 919
}
words {
"text": "SpeechKit"
start_time_ms: 960
end_time_ms: 1719
}
words {
text: "I"
start_time_ms: 2159
end_time_ms: 2200
}
words {
"text": "can"
start_time_ms: 2260
end_time_ms: 2440
}
words {
text: "turn"
start_time_ms: 2520
end_time_ms: 3000
}
words {
"text": "any"
start_time_ms: 3060
end_time_ms: 3320
}
words {
"text": "text"
start_time_ms: 3419
end_time_ms: 3740
}
words {
"text": "into"
start_time_ms: 3780
end_time_ms: 3800
}
words {
"text": "speech"
start_time_ms: 3860
end_time_ms: 4279
}
words {
"text": "now"
start_time_ms: 4680
end_time_ms: 5240
}
words {
"text": "you"
start_time_ms: 5339
end_time_ms: 5380
}
words {
"text": "can"
start_time_ms: 5460
end_time_ms: 5766
}
words {
text: "too"
start_time_ms: 5920
end_time_ms: 6393
}
text: "I'm Yandex SpeechKit I can turn any text into speech now you can too"
end_time_ms: 6600
}
channel_tag: "0"
}
channel_tag: "0"
, session_uuid {
uuid: "df49eaa2-25a55218-ae967fa1-********"
user_request_id: "f8dkup42nmhk********"
}
audio_cursors {
received_data_ms: 6600
partial_time_ms: 6600
final_time_ms: 6600
}
response_wall_time_ms: 204
final_refinement {
normalized_text {
alternatives {
words {
text: "I"
start_time_ms: 380
end_time_ms: 420
}
words {
"text": "Yandex"
start_time_ms: 539
end_time_ms: 919
}
words {
"text": "SpeechKit"
start_time_ms: 960
end_time_ms: 1719
}
words {
text: "I"
start_time_ms: 2159
end_time_ms: 2200
}
words {
"text": "can"
start_time_ms: 2260
end_time_ms: 2440
}
words {
text: "turn"
start_time_ms: 2520
end_time_ms: 3000
}
words {
"text": "any"
start_time_ms: 3060
end_time_ms: 3320
}
words {
"text": "text"
start_time_ms: 3419
end_time_ms: 3740
}
words {
"text": "into"
start_time_ms: 3780
end_time_ms: 3800
}
words {
"text": "speech"
start_time_ms: 3860
end_time_ms: 4279
}
words {
"text": "now"
start_time_ms: 4680
end_time_ms: 5240
}
words {
"text": "you"
start_time_ms: 5339
end_time_ms: 5380
}
words {
"text": "can"
start_time_ms: 5460
end_time_ms: 5766
}
words {
text: "too"
start_time_ms: 5920
end_time_ms: 6393
}
text: "I'm Yandex SpeechKit I can turn any text into speech now you can too"
end_time_ms: 6600
}
channel_tag: "0"
}
}
channel_tag: "0"
, session_uuid {
uuid: "df49eaa2-25a55218-ae967fa1-********"
user_request_id: "f8dkup42nmhk********"
}
audio_cursors {
received_data_ms: 6600
partial_time_ms: 6600
final_time_ms: 6600
eou_time_ms: 6600
}
response_wall_time_ms: 204
eou_update {
time_ms: 6600
}
channel_tag: "0"
]
```

{% endcut %}
8 changes: 4 additions & 4 deletions en/_includes/speechsense/reports/filters.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
# Report filtering
# Filtering in the report

You can use filtering to select the dialogs to include in your report. To do this, use the following settings:

* Period: Period of time for which the report is generated.
* Filters: Use the same fields as for the parameters.
* Grouping: Choose how to group data in your report. You can only group by metadata fields, e.g.:
* **Period**: Time period of the report.
* **Filters**: Use the same fields as for the parameters. You can also use [neuroparameters](../../../speechsense/concepts/reports/neuro-parameters.md) in filters.
* **Grouping**: Choose how to group data in your report. You can only group by metadata fields, for example:

* By agent, to analyze the performance of each one.
* By product, to learn which products agents make fewer mistakes presenting in dialogs.
6 changes: 3 additions & 3 deletions en/_includes/speechsense/reports/parameters.md
Original file line number Diff line number Diff line change
@@ -3,8 +3,8 @@
* **Bot** (only for chats): Bot data.
* **Speech statistics** (only for audio): Agent and customer speech quality criteria, e.g., speech rate, mutual interruptions, etc.
* **General metadata**: Data about the conversation audio (collected via PBX) or text chat. Metadata is uploaded to {{ speechsense-name }} together with the conversation audio or text chat and contains its key characteristics, e.g., date, topic, and dialog language.
* **Customer tags** and **Agent tags**: Classifiers applied to conversation audio recognition results or text chat messages. {{ speechsense-name }} scans the dialog for specific keywords, phrases, or intonations, classifies the dialog, and adds a tag to it.
* **Customer tags** and **Agent tags**: Classifiers applied to conversation audio recognition results or text chat messages. {{ speechsense-name }} detects specific keywords, phrases, or intonations in the dialog, classifies and tags the dialog.

{{ speechsense-name }} has preconfigured tags. These can give you a clue as to whether there was an informal greeting or goodbye, whether the agent thanked the customer for waiting, whether it was the customer's repeat call to support, etc. You can learn more about tags [here](../../../speechsense/concepts/tags.md).
{{ speechsense-name }} has preconfigured tags. These can give you a clue as to whether there was an informal greeting or goodbye, whether the agent thanked the customer for waiting, whether it was the customer's repeat call to support, etc. You can learn more about tags [here](../../../speechsense/concepts/tags.md).

* **YandexGPT analysis**: Agent's performance criteria and customer's behavioral characteristics during the dialog, such as whether the agent was polite, whether the customer was on the rude side, etc.
* **Analysis by {{ yagpt-name }}**: Agent's performance criteria and customer's behavioral characteristics during the dialog, such as whether the agent was polite, whether the customer was on the rude side, etc.
2 changes: 1 addition & 1 deletion en/_includes/speechsense/tag/tag-settings.md
Original file line number Diff line number Diff line change
@@ -16,7 +16,7 @@

A tag is assigned the _poor service_ key phrase. The search for this phrase will be performed differently depending on the **{{ ui-key.yc-ui-talkanalytics.tags.words-between-key-value }}** field value:

| Phrase example | Distance: `0` | Distance: `1` | Distance: `2` |
| Example in a dialog | Distance: `0` | Distance: `1` | Distance: `2` |
| ----------- | ----------- | ----------- | ----------- |
| _poor service_ | found | found | found |
| _poor customer service_ | not found | found | found |
26 changes: 13 additions & 13 deletions en/_includes/storage/create-bucket.md
Original file line number Diff line number Diff line change
@@ -6,7 +6,7 @@ To create a [bucket](../../storage/concepts/bucket.md), you need the _minimum_ `

- Management console {#console}

1. In the [management console]({{ link-console-main }}), select the folder where you want to create your bucket.
1. In the [management console]({{ link-console-main }}), select the folder you want to create a bucket in.
1. Select **{{ objstorage-name }}**.
1. Click **{{ ui-key.yacloud.storage.buckets.button_empty-create }}**.
1. On the bucket creation page:
@@ -31,7 +31,7 @@ To create a [bucket](../../storage/concepts/bucket.md), you need the _minimum_ `
* `{{ ui-key.yacloud.storage.bucket.settings.class_value_cold }}`.
* `{{ ui-key.yacloud.storage.bucket.settings.class_value_ice }}`.

The "colder" classes are for long-term storage of objects you intend to use less frequently. The "colder" the storage, the less you pay for it, but also the more expensive it is to read and write data.
"Cold" classes are designed to store objects that you plan to use less frequently for longer periods of time. The "colder" your storage is, the less you pay for storing data; however, the costs of reading and writing data increase.

1. Add [labels](../../storage/concepts/tags.md), if required:
1. Click **{{ ui-key.yacloud.component.label-set.button_add-label }}**.
@@ -86,7 +86,7 @@ To create a [bucket](../../storage/concepts/bucket.md), you need the _minimum_ `
* `cold`: Cold storage.
* `ice`: Ice storage.

The "colder" classes are for long-term storage of [objects](../../storage/concepts/object.md) you intend to use less frequently. The "colder" the storage, the less you pay for it, but also the more expensive it is to read and write data.
"Cold" classes are designed to store [objects](../../storage/concepts/object.md) that you plan to use less frequently for longer periods of time. The "colder" your storage is, the less you pay for storing data; however, the costs of reading and writing data increase.

* `--max-size`: Maximum bucket size, in bytes. Default value: `0` (unlimited).
* Parameters for enabling [public access](../../storage/security/public-access.md) to a bucket:
@@ -101,11 +101,11 @@ To create a [bucket](../../storage/concepts/bucket.md), you need the _minimum_ `
* Parameters to configure the bucket [ACL](../../storage/concepts/acl.md):
* `--acl`: Predefined ACL. For a list of possible values, see [Predefined ACLs](../../storage/concepts/acl.md#predefined-acls). You cannot use this parameter together with the `--grants` parameter.
* `--grants`: Configures permissions for individual users, [service accounts](../../iam/concepts/users/service-accounts.md), [user groups](../../organization/concepts/groups.md), and [public groups](../../storage/concepts/acl.md#public-groups) (a group of all internet users or a group of all authenticated {{ yandex-cloud }} users). You cannot use this parameter together with the `--acl` parameter. The parameter value is specified in the following format: `grant-type=<permission_grantee_type>,grantee-id=<grantee_ID>,permission=<permission_type>`, where:
* `grant-type`: Type of the permission grantee. The possible values are:
* `grant-type`: Permission grantee type. The possible values are:
* `grant-type-account`: User, [service account](../../iam/concepts/users/service-accounts.md), or [user group](../../organization/concepts/groups.md).
* `grant-type-all-authenticated-users`: [Public group](../../storage/concepts/acl.md#public-groups) that includes all authenticated {{ yandex-cloud }} users.
* `grant-type-all-users`: Public group that includes all internet users.
* `grantee-id`: ID of the user, service account, or user group to which you need to grant permission. It is only specified if `grant-type=grant-type-account`.
* `grantee-id`: ID of the user, service account, or user group you need to grant a permission to. Specified only if `grant-type=grant-type-account`.
* `permission`: ACL permission type. Possible values: `permission-full-control`, `permission-write`, `permission-read`. For more information about permissions, see [Permission types](../../storage/concepts/acl.md#permissions-types).

To configure multiple permissions, specify the `--grants` parameter multiple times.
@@ -188,21 +188,21 @@ To create a [bucket](../../storage/concepts/bucket.md), you need the _minimum_ `

Where:
* Possible types of ACL permissions:
* `--grant-read`: Permission to access the list of objects in the bucket, read various bucket settings (e.g., lifecycle, CORS, or static hosting), and read all objects in the bucket.
* `--grant-read`: Permission to access the list of objects in the bucket, read various bucket settings (lifecycle, CORS, or static hosting), and read all objects in the bucket.
* `--grant-write`: Permission to write, overwrite, and delete objects in the bucket. Can only be used together with `--grant-read`.
* `--grant-full-control`: Full access to the bucket and the objects in it.

You can set multiple permissions within the same command.
* The possible permission grantees are:
* `id=<grantee_ID>`: ID of the user, service account, or user group to which you need to grant permission.
* `id=<grantee_ID>`: ID of the user, service account, or user group you need to grant a permission to.
* `uri=http://acs.amazonaws.com/groups/global/AuthenticatedUsers`: [Public group](../../storage/concepts/acl.md#public-groups) that includes all authenticated {{ yandex-cloud }} users.
* `uri=http://acs.amazonaws.com/groups/global/AllUsers`: Public group that includes all internet users.

By default, an empty ACL is created for each new bucket.

{% endcut %}

You can learn more about the `aws s3api create-bucket` command in the [AWS documentation](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3api/create-bucket.html).
For more information about the `aws s3api create-bucket` command, see the [AWS documentation](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3api/create-bucket.html).

- {{ TF }} {#tf}

@@ -276,8 +276,8 @@ To create a [bucket](../../storage/concepts/bucket.md), you need the _minimum_ `
Where:
* `yandex_iam_service_account`: Description of the [service account](../../iam/concepts/users/service-accounts.md) to create and use the [bucket](../../storage/concepts/bucket.md):

* `name`: Service account name.
* `bucket`: Bucket name.
* `name`: Service account name
* `bucket`: Bucket name


By default, a bucket with a dot in the name is only available over HTTP. To provide HTTPS support for your bucket, [upload your own security certificate](../../storage/operations/hosting/certificate.md) to {{ objstorage-name }}.
@@ -290,7 +290,7 @@ To create a [bucket](../../storage/concepts/bucket.md), you need the _minimum_ `
* `cold`: Cold storage.
* `ice`: Ice storage.

The "colder" classes are for long-term storage of objects you intend to use less frequently. The "colder" the storage, the less you pay for it, but also the more expensive it is to read and write data.
"Cold" classes are designed to store objects that you plan to use less frequently for longer periods of time. The "colder" your storage is, the less you pay for storing data; however, the costs of reading and writing data increase.

* `anonymous_access_flags`: [Access](../../storage/concepts/bucket.md#bucket-access) settings:

@@ -300,9 +300,9 @@ To create a [bucket](../../storage/concepts/bucket.md), you need the _minimum_ `

* `tags`: Bucket [labels](../../storage/concepts/tags.md) in `key = "value"` format.

`name`: Required parameter Other parameters are optional. By default, the `max-size` value is `0`, public access to the bucket is disabled, and the storage class is set to `standard`.
`name`: Required parameter. Other parameters are optional. By default, the `max-size` value is `0`, public access to the bucket is disabled, and the storage class is set to `standard`.

For more information about the `yandex_storage_bucket` parameters in {{ TF }}, see the [provider documentation]({{ tf-provider-resources-link }}/storage_bucket).
For more information about the `yandex_storage_bucket` resource parameters in {{ TF }}, see the [relevant provider documentation]({{ tf-provider-resources-link }}/storage_bucket).

1. Create resources:

34 changes: 16 additions & 18 deletions en/_includes/storage/generate-signing-key.md
Original file line number Diff line number Diff line change
@@ -1,27 +1,25 @@
To generate a signing key, you need static access keys for {{ objstorage-name }}. To learn how to get them, see [Before you start](../../storage/s3/index.md#before-you-begin).

Generate a signing key
To generate a signing key:

1. Use the secret key to encode the date:

```
DateKey = sign("AWS4" + "SecretKey", "yyyymmdd")
```
```
DateKey = sign("AWS4" + "SecretKey", "yyyymmdd")
```
1. Encode the region using the `DateKey` obtained in the previous step:
1. Encode the region using the `DateKey` you got in the previous step:
```
RegionKey = sign(DateKey, "{{ region-id }}")
```
```
RegionKey = sign(DateKey, "{{ region-id }}")
```
1. Encode the service using the `RegionKey` obtained in the previous step:
1. Encode the service using the `RegionKey` you got in the previous step:
```
ServiceKey = sign(RegionKey, "s3")
```
```
ServiceKey = sign(RegionKey, "s3")
```
1. Get a signing key:
1. Get the signing key:
```
SigningKey = sign(ServiceKey, "aws4_request")
```
```
SigningKey = sign(ServiceKey, "aws4_request")
```
6 changes: 4 additions & 2 deletions en/_includes/support/notify.md
Original file line number Diff line number Diff line change
@@ -48,7 +48,9 @@ Some {{ yandex-cloud }} maintenance operations may affect the performance or ava

### Infrastructure failure {#infra}

If there is a {{ yandex-cloud }} failure that can potentially affect the security or availability of your data, technical support will notify you by email as soon as the scope and impact of the problem are identified. Failure notifications will be sent to the subscribers of the folder hosting the affected resource.
If there is a {{ yandex-cloud }} failure that can potentially affect the security or availability of your data, our support team will notify you by email as soon as the scope and impact of the problem are identified. Failure notifications will be sent to the subscribers of the folder hosting the affected resource.

Our support team does not send notifications about platform incidents. You can check the availability of services on the platform component status [page](https://status.cloud.yandex.ru/dashboard) or follow the announcements in our [Telegram channel](https://t.me/yandexcloudalerts).

### Information security incident {#security}

@@ -65,4 +67,4 @@ To configure notification methods:
1. Under **{{ ui-key.yacloud_components.settings.section_settings }}**, select the types of notifications to send and channels for receiving them:
* ![image](../../_assets/console-icons/at.svg): Email
* ![image](../../_assets/console-icons/smartphone.svg): Text message
* ![image](../../_assets/console-icons/logo-telegram.svg): Telegram bot message
* ![image](../../_assets/console-icons/logo-telegram.svg): Telegram bot message
10 changes: 5 additions & 5 deletions en/_includes/tracker/color-issue.md
Original file line number Diff line number Diff line change
@@ -4,7 +4,7 @@ By default, issue bars on the chart are colored according to the issue status ty

To select a different color scheme:

1. Above the timeline on the right, click ![](../../_assets/tracker/svg/gantt-settings-button.svg)&nbsp;**{{ ui-key.startrek.ui_components_Gantt.timeline-config }}**.
1. Above the timeline on the right, click ![](../../_assets/tracker/svg/gantt-settings-button.svg)&nbsp;**Chart settings**.
1. Under **{{ ui-key.startrek-backend.fields.issue.paletteColor }}**, you can choose an appropriate color scheme:

{% list tabs %}
@@ -13,10 +13,10 @@ To select a different color scheme:

This option allows you to set issue colors right on the chart.

1. Select **{{ ui-key.startrek.ui_components_Gantt.color-type-by-manual }}**.
1. Select **manual**.
1. Click **Apply**.

Select an issue from the list to the left of the chart and click ![](../../_assets/horizontal-ellipsis.svg) **{{ ui-key.startrek.ui_components_Gantt_IssueActionsCell.issue-action-menu-title }}**. This will open a palette where you can set the issue color.
Select an issue from the list to the left of the chart and click ![](../../_assets/horizontal-ellipsis.svg) **Issue actions menu**. This will open a palette where you can set the issue color.

![](../../_assets/tracker/three-dots-menu.png)

@@ -25,15 +25,15 @@ To select a different color scheme:

This option will be of use if you need to differentiate issues by a certain parameter, such as a queue or tag.

1. Select **{{ ui-key.startrek.ui_components_Gantt.color-type-by-parameter }}**.
1. Select **by task parameters**.
1. Specify the parameter whose values you want to set colors for.
1. Click **Apply**.

- Monochrome

All issue bars on the chart will be blue.

1. Select **{{ ui-key.startrek.ui_components_Gantt.color-type-monochrome }}**.
1. Select **monochrome**.
1. Click **Apply**.

{% endlist %}
2 changes: 1 addition & 1 deletion en/_includes/tracker/external-blockers.md
Original file line number Diff line number Diff line change
@@ -1 +1 @@
* To enable displaying external blockers in the issue list, select **{{ ui-key.startrek.ui_components_Gantt.show-external-blockers }}**.
* To enable displaying external blockers in the issue list, select **Show external blockers**.
2 changes: 1 addition & 1 deletion en/_includes/tracker/gantt-assigned.md
Original file line number Diff line number Diff line change
@@ -6,6 +6,6 @@ On the Gantt chart, you can appoint or change the issue's assignee:

{% note info %}

If you do not see the ![](../../_assets/tracker/svg/pick-user.svg) button on the issue bar, go to ![](../../_assets/tracker/svg/gantt-settings-button.svg)&nbsp;**{{ ui-key.startrek.ui_components_Gantt.timeline-config }}** and select the **assignee** item under **Issue bar**.
If you do not see the ![](../../_assets/tracker/svg/pick-user.svg) button on the issue bar, go to ![](../../_assets/tracker/svg/gantt-settings-button.svg)&nbsp;**Chart settings** and select the **assignee** item under **Issue bar**.

{% endnote %}
2 changes: 1 addition & 1 deletion en/_includes/tracker/gantt-time-scale.md
Original file line number Diff line number Diff line change
@@ -1 +1 @@
To set up the time scale, select **{{ ui-key.startrek.ui_components_Gantt.scale-days }}**, **{{ ui-key.startrek.ui_components_Gantt.scale-month }}**, or **{{ ui-key.startrek.ui_components_Gantt.scale-quarters }}** in the bottom-right corner of the chart. The scale settings persist after refreshing the page or opening the chart again.
To set up the time scale, select **Week**, **Month**, or **Quarter** in the bottom-right corner of the chart. The scale settings persist after refreshing the page or opening the chart again.
2 changes: 1 addition & 1 deletion en/_includes/tracker/gantt-timing-prolongate.md
Original file line number Diff line number Diff line change
@@ -1 +1 @@
* To set up automatic updates of start dates and deadlines for dependent issues, go to ![](../../_assets/tracker/svg/gantt-settings-button.svg)&nbsp;**{{ ui-key.startrek.ui_components_Gantt.timeline-config }}** and select **{{ ui-key.startrek.ui_components_Gantt.shift-blocked-with-blocker }}**. If the deadline of the blocking issue is later than the start date of the dependent issue, this start date is shifted based on the blocking issue's new deadline.
* To set up automatic updates of start dates and deadlines for dependent issues, go to ![](../../_assets/tracker/svg/gantt-settings-button.svg)&nbsp;**Chart settings** and select **Automatically move the deadline of the dependent issue when the blocking issue's deadline changes**. If the deadline of the blocking issue is later than the start date of the dependent issue, this start date is shifted based on the blocking issue's new deadline.
6 changes: 3 additions & 3 deletions en/_includes/tracker/issue-bar.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
Above the timeline on the right, click ![](../../_assets/tracker/svg/gantt-settings-button.svg)&nbsp;**{{ ui-key.startrek.ui_components_Gantt.timeline-config }}** and select a setting in **Issue bar**:
Above the timeline on the right, click ![](../../_assets/tracker/svg/gantt-settings-button.svg)&nbsp;**Chart settings** and select a setting in **Issue bar**:

* To show the issue name on the issue bar, select the **{{ ui-key.startrek.ui_components_Gantt.show-issue-title }}** item.
* To show the issue name on the issue bar, select the **name** item.

* To show the assignee icon on the issue bar, select the **{{ ui-key.startrek.ui_components_Gantt.show-issue-assignee }}** item.
* To show the assignee icon on the issue bar, select the **assignee** item.

* To have the missed deadline property (the difference between the deadline and the current date) highlighted in red on the chart, select **missed deadline**.
10 changes: 5 additions & 5 deletions en/_includes/tracker/issues-table-project.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
* To select the fields you want to see in the issue list table to the left of the chart, click ![](../../_assets/tracker/svg/settings-old.svg). Select the relevant items and click **Apply**.

* To find issues in the list, start typing in the **{{ ui-key.startrek.ui_components_filter-pane.search-placeholder }}** field.
* To find issues in the list, start typing in the **{{ ui-key.startrek.ui_Common_smart-components_filter-pane.search-placeholder }}** field.

* To set up their display order in the list, click ![](../../_assets/tracker/svg/sorting.svg)&nbsp;**{{ ui-key.startrek.ui_components_SortButton.default-title }}**, specify the parameter, and click ![](../../_assets/tracker/svg/new-first.svg). In this case, you will not be able to move issues manually.
* To set up their display order in the list, click ![](../../_assets/tracker/svg/sorting.svg)&nbsp;**{{ ui-key.startrek.ui_Common_smart-components_SortButton.default-title }}**, specify the parameter, and click ![](../../_assets/tracker/svg/new-first.svg). In this case, you will not be able to move issues manually.

* To group issues by their status, assignee, or other parameters, click ![](../../_assets/tracker/svg/group.svg)&nbsp;**Not grouped** and select the appropriate option from the list.

@@ -14,7 +14,7 @@

* To hide the issue list section, click ![](../../_assets/tracker/svg/close-block.svg).

* To change the layout of the issue list, select ![](../../_assets/tracker/svg/flat-list.svg)&nbsp;**{{ ui-key.startrek.ui_components_filter-pane.list-mode-flat }}** or ![](../../_assets/tracker/svg/tree-list.svg)&nbsp;**{{ ui-key.startrek.ui_components_filter-pane.list-mode-tree }}**.{#trees}
* To change the layout of the issue list, select ![](../../_assets/tracker/svg/flat-list.svg)&nbsp;**{{ ui-key.startrek.ui_Common_smart-components_filter-pane.list-mode-flat }}** or ![](../../_assets/tracker/svg/tree-list.svg)&nbsp;**{{ ui-key.startrek.ui_Common_smart-components_filter-pane.list-mode-tree }}**.{#trees}

{% note info %}

@@ -26,7 +26,7 @@

In the tree list, you can create new sub-issues or change links for sub-issues:

* To create a sub-issue, click ![](../../_assets/tracker/svg/icon-add.svg) **{{ ui-key.startrek.ui_components_projects_Table.add-sub-issue }}** next to the issue:
* To create a sub-issue, click ![](../../_assets/tracker/svg/icon-add.svg) **Add sub-issue** next to the issue:

* To create an issue, go to the **New issue** tab. Give your issue a name and press **Enter**.
* If the issue already exists, go to the **Existing issue** tab, specify the issue key or name, and select the issue from the list. You can find the key on the issue page, under the title (for example, `TEST-1234`).
@@ -37,6 +37,6 @@

{% note info %}

You can move issues manually if no sorting parameter is selected in the **{{ ui-key.startrek.ui_components_SortButton.default-title }}** field. By default, manual sorting mode is selected for the list of issues: you can drag issues in the list.
You can move issues manually if no sorting parameter is selected in the **{{ ui-key.startrek.ui_Common_smart-components_SortButton.default-title }}** field. By default, manual sorting mode is selected for the list of issues: you can drag issues in the list.

{% endnote %}
6 changes: 3 additions & 3 deletions en/_includes/tracker/issues-table-queue-filter-project.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
* To select the fields you want to see in the issue list table to the left of the chart, click ![](../../_assets/tracker/svg/settings-old.svg). Select the relevant items and click **Apply**.

* To find issues in the list, start typing in the **{{ ui-key.startrek.ui_components_filter-pane.search-placeholder }}** field.
* To find issues in the list, start typing in the **{{ ui-key.startrek.ui_Common_smart-components_filter-pane.search-placeholder }}** field.

* To set up their display order in the list, click ![](../../_assets/tracker/svg/sorting.svg)&nbsp;**{{ ui-key.startrek.ui_components_SortButton.default-title }}**, specify the parameter, and click ![](../../_assets/tracker/svg/new-first.svg). In this case, you will not be able to move issues manually.
* To set up their display order in the list, click ![](../../_assets/tracker/svg/sorting.svg)&nbsp;**{{ ui-key.startrek.ui_Common_smart-components_SortButton.default-title }}**, specify the parameter, and click ![](../../_assets/tracker/svg/new-first.svg). In this case, you will not be able to move issues manually.

* To group issues by their status, assignee, or other parameters, click ![](../../_assets/tracker/svg/group.svg)&nbsp;**Not grouped** and select the appropriate option from the list.

* To filter the issue list, use the filter builder. For this, on the ![](../../_assets/tracker/svg/filter.svg)&nbsp;**{{ ui-key.startrek.ui_components_IssueTabs.fields-tab }}** panel, select the parameters and specify the values to use for generating an issue list.
* To filter the issue list, use the filter builder. For this, on the ![](../../_assets/tracker/svg/filter.svg)&nbsp;**Parameters** panel, select the parameters and specify the values to use for generating an issue list.

* To swap the list columns, click ![](../../_assets/tracker/svg/settings-old.svg) above the list. Next, in the **Added** section, click the parameter, hold and drag it within the section. Click **Apply**.

4 changes: 2 additions & 2 deletions en/_includes/tracker/on-premise-server.md
Original file line number Diff line number Diff line change
@@ -6,11 +6,11 @@ To connect your own server to {{ tracker-name }}:

1. In the **Platform** field, select the platform your server is connected to.

1. In the **{{ ui-key.startrek.ui_components_admin-repositories_ConnectRepositoryDialog_fields_UrlField.server-url-label }}** field, specify your server address to any repository that can be accessed using a token.
1. In the **Link to repository** field, specify your server address to any repository that can be accessed using a token.

1. Get an OAuth token for your repository on GitLab. For details on how to get a token, see the [GitLab documentation](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html#create-a-personal-access-token). For the proper operation of {{ tracker-name }}, enable the **read_repository** and **read_api** options when setting up permissions.

1. In the **{{ ui-key.startrek.ui_components_admin-repositories_ConnectRepositoryDialog.token-label }}** field, enter the token for connecting to your server.
1. In the **{{ ui-key.startrek.ui_Common_smart-components_admin-repositories_ConnectRepositoryDialog.token-label }}** field, enter the token for connecting to your server.

1. Click **Connect**.

2 changes: 1 addition & 1 deletion en/_includes/tracker/open-personal-settings.md
Original file line number Diff line number Diff line change
@@ -1 +1 @@
In the left-hand panel, click ![](../../_assets/tracker/svg/settings.svg) **{{ ui-key.startrek.ui_components_PageAgileBoard_PageAgileBoardHeader.settings }}**.
In the left-hand panel, click ![](../../_assets/tracker/svg/settings.svg) **{{ ui-key.startrek.ui_Boards_pages_PageAgileBoard_PageAgileBoardHeader.settings }}**.
2 changes: 1 addition & 1 deletion en/_includes/tracker/repository-path.md
Original file line number Diff line number Diff line change
@@ -1 +1 @@
In the left-hand panel, click ![](../../_assets/tracker/svg/still.svg) and select **Admin settings** → ![](../../_assets/tracker/svg/repositories.svg) **{{ ui-key.startrek.ui_components_page-admin_PageAdmin.menu-item-repositories }}** → **{{ ui-key.startrek.ui_components_admin-repositories_ConnectRepositoryDialog.connect }}**.
In the left-hand panel, click ![](../../_assets/tracker/svg/still.svg) and select **Admin settings** → ![](../../_assets/tracker/svg/repositories.svg) **{{ ui-key.startrek.ui_Common_smart-components_page-admin_PageAdmin.menu-item-repositories }}** → **{{ ui-key.startrek.ui_Common_smart-components_admin-repositories_ConnectRepositoryDialog.connect }}**.
48 changes: 24 additions & 24 deletions en/_includes/tracker/task-by-mail.md
Original file line number Diff line number Diff line change
@@ -6,16 +6,16 @@

1. {% include [go to settings](transition-page.md) %}

1. In the top-right corner, click ![](../../_assets/tracker/svg/queue-settings.svg) **{{ ui-key.startrek.ui_components_PageQueue_header.settings }}**.
1. In the top-right corner, click ![](../../_assets/tracker/svg/queue-settings.svg) **{{ ui-key.startrek.ui_Queues_pages_PageQueue_header.settings }}**.

1. Select **{{ ui-key.startrek.ui_components_page-queue-admin_QueueAdminPageContent.menu-item-aliases }}**.
1. Select **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_QueueAdminPageContent.menu-item-aliases }}**.

1. Click **Configure mail**.

1. Set up the mailbox for receiving messages:

1. Under **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesCreateForm.mail-settings-title }}**, in the **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesCreateForm.mail-address }}** field, specify the email address you created in Step 1, including the domain, e.g., `{{ example-account }}`. The **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesCreateForm.mail-login }}** field will be populated automatically.
1. In the **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesCreateForm.mail-password }}** field, provide the password for your email address. If the selected email server allows you to control access to the mailbox by an application password, enter the application's password for email clients in this field.
1. Under **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesCreateForm.mail-settings-title }}**, in the **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesCreateForm.mail-address }}** field, specify the email address you created in Step 1, including the domain, e.g., `{{ example-account }}`. The **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesCreateForm.mail-login }}** field will be populated automatically.
1. In the **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesCreateForm.mail-password }}** field, provide the password for your email address. If the selected email server allows you to control access to the mailbox by an application password, enter the application's password for email clients in this field.

{% note info "If the setup failed with a 404 error" %}

@@ -26,15 +26,15 @@

[Learn more about application passwords in the Yandex ID documentation]({{ link-yandex }}/support/id/authorization/app-passwords.html).

1. Enter the **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesCreateForm.mail-imap }}** and the email server **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesCreateForm.mail-port }}**: you need them to collect emails. You can find this data in your email account settings.
1. To enable SSL encryption, select **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesCreateForm.mail-ssl }}**.
1. If you need to process emails not only from the organization's employees but from external users as well, enable the **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesCreateForm.mail-allow-external }}** setting.
1. Enter the **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesCreateForm.mail-imap }}** and the email server **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesCreateForm.mail-port }}**: you need them to collect emails. You can find this data in your email account settings.
1. To enable SSL encryption, select **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesCreateForm.mail-ssl }}**.
1. If you need to process emails not only from the organization's employees but from external users as well, enable the **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesCreateForm.mail-allow-external }}** setting.

{% cut "Additional parameters" %}

* **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesCreateForm.mail-incoming-folder }}**: Create a folder for emails from {{ tracker-name }} and specify its name. Any emails sent to this folder will automatically be converted to queue issues.
* **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesCreateForm.mail-archive-folder }}**: Create a folder for archiving emails from {{ tracker-name }} and specify its name.
* **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesCreateForm.mail-process-messages-from }}**: Set the date. Emails received prior to this date are not processed and are automatically moved to the **Archive** folder.
* **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesCreateForm.mail-incoming-folder }}**: Create a folder for emails from {{ tracker-name }} and specify its name. Any emails sent to this folder will automatically be converted to queue issues.
* **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesCreateForm.mail-archive-folder }}**: Create a folder for archiving emails from {{ tracker-name }} and specify its name.
* **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesCreateForm.mail-process-messages-from }}**: Set the date. Emails received prior to this date are not processed and are automatically moved to the **Archive** folder.

{% note alert %}

@@ -49,15 +49,15 @@
1. Specify the parameters to create issues from your email with: the issue type and [components](../../tracker/manager/components.md).

1. If you want the issue comments to be also sent as emails, set up a mailbox for sending messages:
1. Under **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesFormSendPanel.send-settings-title }}**, click ![](../../_assets/tracker/svg/add-address.svg) **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesStateList.action-add-mail }}**.
1. In the **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesFormSendPanel.send-mail-login }}** field, specify the email address to send emails as issue comments from, e.g., `{{ example-account }}`.
1. In the **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesFormSendPanel.send-mail-password }}** field, provide the password for your email address.
1. Specify the **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesFormSendPanel.send-mail-smtp }}** and **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesFormSendPanel.send-mail-port }}** to enable sending emails. You can find this data in your email account settings.
1. To enable SSL encryption, select **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesFormSendPanel.send-mail-ssl }}**.
1. Set up **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesFormSendPanel.signature-settings-title }}** for emails to send. Make sure to specify the **{{ ui-key.startrek.ui_components_page-queue-admin_Signature.alias-title }}**, as you will need it to distinguish signatures in the common list. Your email recipients will see the nickname instead of the sender name.
1. Test that everything is up and running: click ![](../../_assets/tracker/svg/send-email.svg) **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesFormSendPanel.test-mail-button }}**.
1. Under **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesFormSendPanel.send-settings-title }}**, click ![](../../_assets/tracker/svg/add-address.svg) **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesStateList.action-add-mail }}**.
1. In the **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesFormSendPanel.send-mail-login }}** field, specify the email address to send emails as issue comments from, e.g., `{{ example-account }}`.
1. In the **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesFormSendPanel.send-mail-password }}** field, provide the password for your email address.
1. Specify the **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesFormSendPanel.send-mail-smtp }}** and **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesFormSendPanel.send-mail-port }}** to enable sending emails. You can find this data in your email account settings.
1. To enable SSL encryption, select **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesFormSendPanel.send-mail-ssl }}**.
1. Set up **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesFormSendPanel.signature-settings-title }}** for emails to send. Make sure to specify the **Alias**, as you will need it to distinguish signatures in the common list. Your email recipients will see the nickname instead of the sender name.
1. Test that everything is up and running: click ![](../../_assets/tracker/svg/send-email.svg) **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesFormSendPanel.test-mail-button }}**.

1. Click **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesCreateForm.save-button }}**. The queue's email address will get running within an hour after creation.
1. Click **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesCreateForm.save-button }}**. The queue's email address will get running within an hour after creation.

1. Enable sending issue comments as emails:
1. In the queue settings, select **Basic settings**.
@@ -73,21 +73,21 @@

1. {% include [go to settings](transition-page.md) %}

1. In the top-right corner, click ![](../../_assets/tracker/svg/queue-settings.svg) **{{ ui-key.startrek.ui_components_PageQueue_header.settings }}**.
1. In the top-right corner, click ![](../../_assets/tracker/svg/queue-settings.svg) **{{ ui-key.startrek.ui_Queues_pages_PageQueue_header.settings }}**.

1. Select **{{ ui-key.startrek.ui_components_page-queue-admin_QueueAdminPageContent.menu-item-aliases }}**.
1. Select **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_QueueAdminPageContent.menu-item-aliases }}**.

1. Check whether your organization has an [email domain]({{ support-business-domain }}) in {{ ya-360 }}. Otherwise, click **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesStateList.action-domain }}** to open {{ ya-360 }} and create a domain. If you already have a email domain set up in another service, you can create a subdomain for it and [connect it to {{ ya-360 }}]({{ support-business-domain }}).
1. Check whether your organization has an [email domain]({{ support-business-domain }}) in {{ ya-360 }}. Otherwise, click **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesStateList.action-domain }}** to open {{ ya-360 }} and create a domain. If you already have a email domain set up in another service, you can create a subdomain for it and [connect it to {{ ya-360 }}]({{ support-business-domain }}).

1. Click **Configure mail**.

1. Set up a mailbox for receiving and sending messages.
1. In the **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesCreateForm.mail-address }}** field, specify a new email address to be used only for the queue.
1. If you need to process emails not only from the organization's employees but from external users as well, enable the **{{ ui-key.startrek.ui_components_page-queue-admin_AliasesCreateForm.mail-allow-external }}** setting.
1. In the **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesCreateForm.mail-address }}** field, specify a new email address to be used only for the queue.
1. If you need to process emails not only from the organization's employees but from external users as well, enable the **{{ ui-key.startrek.ui_Queues_pages_page-queue-admin_AliasesCreateForm.mail-allow-external }}** setting.

1. Specify the parameters with which the issues should be created in the queue: the [issue type](../../tracker/manager/add-ticket-type.md) and [components](../../tracker/manager/components.md).

1. Set up signatures for the sent emails. Make sure to specify the **{{ ui-key.startrek.ui_components_page-queue-admin_Signature.alias-title }}**, as you will need it to distinguish signatures in the common list. Your email recipients will see the nickname instead of the sender name. Check that everything is up and running by sending a test email.
1. Set up signatures for the sent emails. Make sure to specify the **Alias**, as you will need it to distinguish signatures in the common list. Your email recipients will see the nickname instead of the sender name. Check that everything is up and running by sending a test email.

1. Click **Create**. The queue's email address will get running within an hour after creation.

4 changes: 2 additions & 2 deletions en/_includes/tracker/timeline-area.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
On a chart, you can configure the shift logic for dependent and parent issues, as well as issue link display.

Above the timeline on the right, click ![](../../_assets/tracker/svg/gantt-settings-button.svg)&nbsp;**{{ ui-key.startrek.ui_components_Gantt.timeline-config }}** and select a setting in **Issue bar**:
Above the timeline on the right, click ![](../../_assets/tracker/svg/gantt-settings-button.svg)&nbsp;**Chart settings** and select a setting in **Issue bar**:

* To have issues with the _Depends on — Blocks_ link joined with an arrow on the chart, select **{{ ui-key.startrek.ui_components_Gantt.show-links }}**.
* To have issues with the _Depends on — Blocks_ link joined with an arrow on the chart, select **Show blocking links**.

* To automatically move the deadline of the dependent issue when the blocking issue's deadline changes, select the appropriate option.

7 changes: 7 additions & 0 deletions en/_includes/video/add-subtitles-optional.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
(Optional) To add [subtitles](../../video/concepts/videos.md#subtitles) to a video, in the **{{ ui-key.yacloud_video.videos.label_subtitles }}** field, click **{{ ui-key.yacloud_video.common.action_add }}**:

1. In the window that opens, select the subtitle language.
1. Click **Select file** and select the file with subtitles.
1. Click **{{ ui-key.yacloud_video.common.action_create }}**.

Wait for the file to upload.
16 changes: 8 additions & 8 deletions en/_includes/video/get-key.md
Original file line number Diff line number Diff line change
@@ -2,18 +2,18 @@

- {{ video-name }} interface {#console}

1. Open the {{ video-name }} [home page]({{ link-video-main }}).
1. Select a channel.
1. In the ![image](../../_assets/console-icons/antenna-signal.svg) **{{ ui-key.yacloud_video.streams.title_streams }}** tab, select a stream.
1. In the stream settings window that opens, copy the following field values:
1. Open the {{ video-name }} [home page]({{ link-video-main }}).
1. Select a channel.
1. In the ![image](../../_assets/console-icons/antenna-signal.svg) **{{ ui-key.yacloud_video.streams.title_streams }}** tab, select the broadcast you need.
1. In the stream settings window that opens, copy the following field values:

* **{{ ui-key.yacloud_video.stream-lines.label_stream-key }}**.
* **{{ ui-key.yacloud_video.stream-lines.label_server-address }}**.
* **{{ ui-key.yacloud_video.stream-lines.label_stream-key }}**
* **{{ ui-key.yacloud_video.stream-lines.label_server-address }}**

- API {#api}

To get the server address, use the [StreamLineService/Get](../../video/api-ref/grpc/StreamLine/get.md) gRPC API call.
Use the [get](../../video/api-ref/StreamLine/get.md) REST API method for the [StreamLine](../../video/api-ref/StreamLine/index.md) resource or the [StreamLineService/Get](../../video/api-ref/grpc/StreamLine/get.md) gRPC API call.

To get the stream key, use the [StreamLineService/GetStreamKey](../../video/api-ref/grpc/StreamLine/getStreamKey.md) gRPC API call.
Use the [getStreamKey](../../video/api-ref/StreamLine/getStreamKey.md) REST API method for the [StreamLine](../../video/api-ref/StreamLine/index.md) resource or the [StreamLineService/GetStreamKey](../../video/api-ref/grpc/StreamLine/getStreamKey.md) gRPC API call.

{% endlist %}
2 changes: 1 addition & 1 deletion en/_includes/vision/ai-before-beginning.md
Original file line number Diff line number Diff line change
@@ -52,6 +52,6 @@ Get your account data for authentication:
Authorization: Api-Key <API key>
```

Do not specify the folder ID in your requests, as {{ yagpt-name }} uses the folder in which the service account was created.
Do not specify the folder ID in your requests, as the service uses the folder the service account was created in.

{% endlist %}
6 changes: 5 additions & 1 deletion en/_pricing/compute/usd-instance-resources.md
Original file line number Diff line number Diff line change
@@ -19,6 +19,10 @@
| 100% vCPU | {{ sku|USD|compute.vm.cpu.c100.v3|string }} | {{ sku|USD|compute.vm.cpu.c100.preemptible.v3|string }} | {{ sku|USD|v1.commitment.selfcheckout.m6.compute.vm.cpu.c100.standard.v3|string }} | {{ sku|USD|v1.commitment.selfcheckout.y1.compute.vm.cpu.c100.standard.v3|string }} |
| 1 NVIDIA T4 GPU | {{ sku|USD|compute.vm.gpu.standard.v3-t4|string }} | {{ sku|USD|compute.vm.gpu.standard.v3-t4.preemptible|string }} | − | − |
| RAM (for 1 GB) | {{ sku|USD|compute.vm.ram.v3|string }} | {{ sku|USD|compute.vm.ram.preemptible.v3|string }} | {{ sku|USD|v1.commitment.selfcheckout.m6.compute.vm.ram.standard.v3|string }} | {{ sku|USD|v1.commitment.selfcheckout.y1.compute.vm.ram.standard.v3|string }} |
| **Intel Ice Lake with T4i** | Regular VM | Preemptible&nbsp;VM | | |
| 100% vCPU | $0.008400 | $0.008400 | - | - |
| 1 GPU | $1.152000 | $1.152000 | - | - |
| RAM (for 1 GB) | $0.002240 | $0.002240 | - | - |
| **Intel Ice Lake (Compute Optimized)** | Regular VM | Preemptible&nbsp;VM | | |
| 100% vCPU | {{ sku|USD|compute.vm.cpu.c100.highfreq-v3|string }} | - | − | − |
| RAM (for 1 GB) | {{ sku|USD|compute.vm.ram.highfreq-v3|string }} | - | − | − |
@@ -31,4 +35,4 @@
| 1 GPU | $13.338400 | $13.338400 | - | - |
| RAM (for 1 GB) | $0.002240 | $0.002240 | - | - |

^*^ Feature is available on request, subject to technical availability.
^*^ Feature is available on request, subject to technical availability.
40 changes: 20 additions & 20 deletions en/_pricing_examples/managed-kafka/usd-hour.md
Original file line number Diff line number Diff line change
@@ -1,60 +1,60 @@
Cost calculation for {{ KF }} broker hosts:

> 3 × (2&nbsp;×&nbsp;$0.012080 + 8&nbsp;×&nbsp;$0.003200) = $0.149280
> 3 × (2&nbsp;×&nbsp;{{ sku|USD|mdb.cluster.kafka.v3.cpu.c100|string }} + 8&nbsp;×&nbsp;{{ sku|USD|mdb.cluster.kafka.v3.ram|string }}) = {% calc [currency=USD] 3 × (2 × {{ sku|USD|mdb.cluster.kafka.v3.cpu.c100|number }} + 8 × {{ sku|USD|mdb.cluster.kafka.v3.ram|number }}) %}
>
> Total: $0.149280, per hour cost of {{ KF }} broker hosts.
> Total: {% calc [currency=USD] 3 × (2 × {{ sku|USD|mdb.cluster.kafka.v3.cpu.c100|number }} + 8 × {{ sku|USD|mdb.cluster.kafka.v3.ram|number }}) %}, per hour cost of {{ KF }} broker hosts.

Where:
* 3: Number of {{ KF }} broker hosts.
* 2: Number of vCPUs.
* $0.012080: Cost of using 100% vCPU per hour.
* {{ sku|USD|mdb.cluster.kafka.v3.cpu.c100|string }}: Cost of using 100% vCPU per hour.
* 8: Amount of RAM per host (in GB).
* $0.003200: Cost of using 1 GB of RAM at 100% vCPU per hour.
* {{ sku|USD|mdb.cluster.kafka.v3.ram|string }}: Cost of using 1 GB of RAM at 100% vCPU per hour.

Calculating the cost of storage for {{ KF }} broker hosts:

> 3 × 100 × $0.025600 = $7.680000
> 3 × 100 × {{ sku|USD|mdb.cluster.network-hdd.kafka|month|string }} = {% calc [currency=USD] 3 × 100 × {{ sku|USD|mdb.cluster.network-hdd.kafka|month|number }} %}
>
> Total: $7.680000, cost of storage for {{ KF }} broker hosts.
> Total: {% calc [currency=USD] 3 × 100 × {{ sku|USD|mdb.cluster.network-hdd.kafka|month|number }} %}, cost of storage for {{ KF }} broker hosts.

Where:
* 3: Number of {{ KF }} broker hosts.
* 100: Amount of network HDD storage (in GB).
* $0.025600: Cost of using 1 GB of network HDD storage per month.
* {{ sku|USD|mdb.cluster.network-hdd.kafka|month|string }}: Cost of using 1 GB of network HDD storage per month.

Cost calculation for {{ ZK }} hosts:

> 3 × (2 × $0.005600 + 4 × $0.002240) = $0.060480
> 3 × (2&nbsp;×&nbsp;{{ sku|USD|mdb.zk.kafka.v3.cpu.c50|string }} + 4&nbsp;×&nbsp;{{ sku|USD|mdb.zk.kafka.v3.ram|string }}) = {% calc [currency=USD] 3 × (2 × {{ sku|USD|mdb.zk.kafka.v3.cpu.c50|number }} + 4 × {{ sku|USD|mdb.zk.kafka.v3.ram|number }}) %}
>
> Total: $0.060480, per hour cost of {{ ZK }} hosts.
> Total: {% calc [currency=USD] 3 × (2 × {{ sku|USD|mdb.zk.kafka.v3.cpu.c50|number }} + 4 × {{ sku|USD|mdb.zk.kafka.v3.ram|number }}) %}, per hour cost of {{ ZK }} hosts.

Where:
* 3: Number of {{ ZK }} hosts.
* 2: Number of vCPUs.
* $0.005600: Cost of using 50% vCPU per hour.
* {{ sku|USD|mdb.zk.kafka.v3.cpu.c50|string }}: Cost of using 50% vCPU per hour.
* 4: Amount of RAM per host (in GB).
* $0.002240: Cost of using 1 GB of RAM at 50% vCPU per hour.
* {{ sku|USD|mdb.zk.kafka.v3.ram|string }}: Cost of using 1 GB of RAM at 50% vCPU per hour.

Calculating the cost of storage for {{ ZK }} hosts:

> 3 × 10 × $0.104080 = $3.122400
> 3 × 10 × {{ sku|USD|mdb.cluster.network-nvme.kafka|month|string }} = {% calc [currency=USD] 3 × 10 × {{ sku|USD|mdb.cluster.network-nvme.kafka|month|number }} %}
>
> Total: $3.122400, cost of storage for {{ ZK }} hosts.
> Total: {% calc [currency=USD] 3 × 10 × {{ sku|USD|mdb.cluster.network-nvme.kafka|month|number }} %}, cost of storage for {{ ZK }} hosts.

Where:
* 3: Number of {{ ZK }} hosts.
* 10: Amount of SSD network storage (in GB).
* $0.104080: Cost of using 1 GB of network SSD storage per month.
* {{ sku|USD|mdb.cluster.network-nvme.kafka|month|string }}: Cost of using 1 GB of network SSD storage per month.

Total cost calculation:

> 720 × ($0.149280 + $0.060480) + $7.680000 + $3.122400 = $161.829600
> 720 × ({% calc [currency=USD] 3 × (2 × {{ sku|USD|mdb.cluster.kafka.v3.cpu.c100|number }} + 8 × {{ sku|USD|mdb.cluster.kafka.v3.ram|number }}) %} + {% calc [currency=USD] 3 × (2 × {{ sku|USD|mdb.zk.kafka.v3.cpu.c50|number }} + 4 × {{ sku|USD|mdb.zk.kafka.v3.ram|number }}) %}) + {% calc [currency=USD] 3 × 100 × {{ sku|USD|mdb.cluster.network-hdd.kafka|month|number }} %} + {% calc [currency=USD] 3 × 10 × {{ sku|USD|mdb.cluster.network-nvme.kafka|month|number }} %} = {% calc [currency=USD] 720 × ((3 × (2 × {{ sku|USD|mdb.cluster.kafka.v3.cpu.c100|number }} + 8 × {{ sku|USD|mdb.cluster.kafka.v3.ram|number }})) + (3 × (2 × {{ sku|USD|mdb.zk.kafka.v3.cpu.c50|number }} + 4 × {{ sku|USD|mdb.zk.kafka.v3.ram|number }}))) + (3 × 100 × {{ sku|USD|mdb.cluster.network-hdd.kafka|month|number }}) + (3 × 10 × {{ sku|USD|mdb.cluster.network-nvme.kafka|month|number }}) %}
>
> Total: $161.829600, cost of using the cluster for 30 days.
> Total: {% calc [currency=USD] 720 × ((3 × (2 × {{ sku|USD|mdb.cluster.kafka.v3.cpu.c100|number }} + 8 × {{ sku|USD|mdb.cluster.kafka.v3.ram|number }})) + (3 × (2 × {{ sku|USD|mdb.zk.kafka.v3.cpu.c50|number }} + 4 × {{ sku|USD|mdb.zk.kafka.v3.ram|number }}))) + (3 × 100 × {{ sku|USD|mdb.cluster.network-hdd.kafka|month|number }}) + (3 × 10 × {{ sku|USD|mdb.cluster.network-nvme.kafka|month|number }}) %}, cost of using the cluster for 30 days.

Where:
* 720: Number of hours in 30 days.
* $0.149280: Per hour cost of {{ KF }} broker hosts.
* $0.060480: Per hour cost of {{ ZK }} hosts.
* $7.680000: Cost of storage for {{ KF }} broker hosts.
* $3.122400: Cost of storage for {{ ZK }} hosts.
* {% calc [currency=USD] 3 × (2 × {{ sku|USD|mdb.cluster.kafka.v3.cpu.c100|number }} + 8 × {{ sku|USD|mdb.cluster.kafka.v3.ram|number }}) %}: Per hour cost of {{ KF }} broker hosts.
* {% calc [currency=USD] 3 × (2 × {{ sku|USD|mdb.zk.kafka.v3.cpu.c50|number }} + 4 × {{ sku|USD|mdb.zk.kafka.v3.ram|number }}) %}: Per hour cost of {{ ZK }} hosts.
* {% calc [currency=USD] 3 × 100 × {{ sku|USD|mdb.cluster.network-hdd.kafka|month|number }} %}: Cost of storage for {{ KF }} broker hosts.
* {% calc [currency=USD] 3 × 10 × {{ sku|USD|mdb.cluster.network-nvme.kafka|month|number }} %}: Cost of storage for {{ ZK }} hosts.
8 changes: 4 additions & 4 deletions en/_pricing_examples/managed-mongodb/usd-host.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
> 3 × (2&nbsp;×&nbsp;$0.012800 + 8&nbsp;×&nbsp;$0.007200) = $0.249600
> 3 × (2&nbsp;×&nbsp;{{ sku|USD|mdb.cluster.mongodb.v3.cpu.c100|string }} + 8&nbsp;×&nbsp;{{ sku|USD|mdb.cluster.mongodb.v3.ram|string }}) = {% calc [currency=USD] 3 × (2 × {{ sku|USD|mdb.cluster.mongodb.v3.cpu.c100|number }} + 8 × {{ sku|USD|mdb.cluster.mongodb.v3.ram|number }}) %}

> Total: $0.249600, cost of operation of {{ MG }} hosts per hour.
> Total: {% calc [currency=USD] 3 × (2 × {{ sku|USD|mdb.cluster.mongodb.v3.cpu.c100|number }} + 8 × {{ sku|USD|mdb.cluster.mongodb.v3.ram|number }}) %}, cost of operation of {{ MG }} hosts per hour.

Where:
* 3: Number of {{ MG }} hosts
* 2: Number of vCPUs
* $0.012800: Cost of using 100% vCPU per hour
* {{ sku|USD|mdb.cluster.mongodb.v3.cpu.c100|string }}: Cost of using 100% vCPU per hour
* 8: Amount of RAM per {{ MG }} host (in GB)
* $0.007200: Cost of using 1 GB of RAM at 100% vCPU per hour
* {{ sku|USD|mdb.cluster.mongodb.v3.ram|string }}: Cost of using 1 GB of RAM at 100% vCPU per hour
8 changes: 4 additions & 4 deletions en/_pricing_examples/managed-mongodb/usd-storage.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
> 720 × $0.249600 + 100&nbsp;×&nbsp;$0.025600 = $182.272000
> 720 × {% calc [currency=USD] 3 × (2 × {{ sku|USD|mdb.cluster.mongodb.v3.cpu.c100|number }} + 8 × {{ sku|USD|mdb.cluster.mongodb.v3.ram|number }}) %} + 100&nbsp;×&nbsp;{{ sku|USD|mdb.cluster.network-hdd.ch|month|string }} = {% calc [currency=USD] 720 × (3 × (2 × {{ sku|USD|mdb.cluster.mongodb.v3.cpu.c100|number }} + 8 × {{ sku|USD|mdb.cluster.mongodb.v3.ram|number }})) + 100 × {{ sku|USD|mdb.cluster.network-hdd.ch|month|number }} %}
>
> Total: $182.272000, cost of using the cluster for 30 days.
> Total: {% calc [currency=USD] 720 × (3 × (2 × {{ sku|USD|mdb.cluster.mongodb.v3.cpu.c100|number }} + 8 × {{ sku|USD|mdb.cluster.mongodb.v3.ram|number }})) + 100 × {{ sku|USD|mdb.cluster.network-hdd.ch|month|number }} %}, cost of using the cluster for 30 days.

Where:
* 720: Number of hours in 30 days
* $0.249600: Cost of operation of {{ MG }} hosts per hour
* {% calc [currency=USD] 3 × (2 × {{ sku|USD|mdb.cluster.mongodb.v3.cpu.c100|number }} + 8 × {{ sku|USD|mdb.cluster.mongodb.v3.ram|number }}) %}: Cost of operation of {{ MG }} hosts per hour
* 100: Amount of network HDD storage (in GB)
* $0.025600: Cost of using 1 GB of network HDD storage per month
* {{ sku|USD|mdb.cluster.network-hdd.ch|month|string }}: Cost of using 1 GB of network HDD storage per month
Loading

0 comments on commit 57998b5

Please sign in to comment.