-
Notifications
You must be signed in to change notification settings - Fork 667
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Loading status checks…
Merge branch 'yandex-cloud:master' into master
Showing
1,876 changed files
with
110,494 additions
and
31,431 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 %} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 %} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 %} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 }}. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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**. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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). | ||
|
1 change: 1 addition & 0 deletions
1
en/_includes/compute/create/change-custom-disk-settings-image.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
1 change: 1 addition & 0 deletions
1
en/_includes/compute/create/change-custom-disk-settings-storages.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
87
en/_includes/compute/create/create-vm-with-gpu-console.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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) %} | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
14
en/_includes/compute/create/section-storages-secondary-disk.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 }}**. |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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) %} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 %} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 }}**. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 | | ||
+----------------------+-----------------+---------------+---------+---------------+--------------+ | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 }}**. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
93
en/_includes/compute/oslogin-connect-with-exported-cert.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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**. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 changes: 1 addition & 1 deletion
2
en/_includes/data-transfer/fields/postgresql/ui/connection-manager.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 %} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
42 changes: 22 additions & 20 deletions
42
en/_includes/instance-groups/create-fixed-group-via-concole.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 %} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 }} | |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 }} | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 }}). |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 }}). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 %} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 %} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 %} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
17
en/_includes/organization/os-login-cli-organization-list.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 | | ||
+----------------------+-------------------------+-------------------------+ | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
11
en/_includes/organization/os-login-roles-needed-for-vm-access.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 %} |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 %} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 %} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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") | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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**. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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) **{{ 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) **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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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) **{{ 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) **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**. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 }}**. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 }}**. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,60 +1,60 @@ | ||
Cost calculation for {{ KF }} broker hosts: | ||
|
||
> 3 × (2 × $0.012080 + 8 × $0.003200) = $0.149280 | ||
> 3 × (2 × {{ sku|USD|mdb.cluster.kafka.v3.cpu.c100|string }} + 8 × {{ 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 × {{ sku|USD|mdb.zk.kafka.v3.cpu.c50|string }} + 4 × {{ 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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,10 +1,10 @@ | ||
> 3 × (2 × $0.012800 + 8 × $0.007200) = $0.249600 | ||
> 3 × (2 × {{ sku|USD|mdb.cluster.mongodb.v3.cpu.c100|string }} + 8 × {{ 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 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,9 @@ | ||
> 720 × $0.249600 + 100 × $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 × {{ 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 |
Oops, something went wrong.