Release 10.06.2021

yfm-team · Jun 10, 2021 · f40561b · f40561b
1 parent 81fa9f9
commit f40561b
Show file tree

Hide file tree

Showing 38 changed files with 381 additions and 105 deletions.
diff --git a/.yfm b/.yfm
@@ -1,7 +1,7 @@
 allowHTML: true
 connector:
-    type: github
-    github: 
+    type: gitHub
+    gitHub: 
         endpoint: https://api.github.com
         owner: yandex-cloud
         repo: docs
diff --git a/en/_assets/datalens/solution-02/19-choose-line-chart.png b/en/_assets/datalens/solution-02/19-choose-line-chart.png
diff --git a/en/_assets/datalens/solution-02/24-choose-barchart.png b/en/_assets/datalens/solution-02/24-choose-barchart.png
diff --git a/en/_assets/datalens/solution-02/28-choose-pivot.png b/en/_assets/datalens/solution-02/28-choose-pivot.png
diff --git a/en/_assets/datalens/solution-02/33-choose-heatmap.png b/en/_assets/datalens/solution-02/33-choose-heatmap.png
diff --git a/en/_includes/mdb/instance-types-code.md b/en/_includes/mdb/instance-types-code.md
@@ -8,7 +8,6 @@ Configuration types:
 
   {% note info %}
 
-  Hosts with a guaranteed vCPU share under 100% can't be used in multi-host clusters.
+  Hosts with a guaranteed vCPU share under 50% can't be used in multi-host clusters.
 
   {% endnote %}
-
diff --git a/en/_includes/mdb/mkf-conn-strings.md b/en/_includes/mdb/mkf-conn-strings.md
@@ -1686,4 +1686,3 @@
   ```
 
 {% endlist %}
-
diff --git a/en/_includes/tutorials/data-from-ch-visualization.md b/en/_includes/tutorials/data-from-ch-visualization.md
@@ -196,7 +196,7 @@ To visualize sales by brands and product categories, create a [chart](../../data
 
     ![image](../../_assets/datalens/solution-02/25-replace-field1.png)
 
-1. Replace payment types for product categories in Colors. Drag **ProductCategory** from the **Dimensions** section to the **X** section and hold it over the **PaymentType** field until it turns red.
+1. Replace payment types for product categories in **Colors**. Drag **ProductCategory** from the **Dimensions** section to the **Colors** section and hold it over the **PaymentType** field until it turns red.
 
     ![image](../../_assets/datalens/solution-02/26-replace-field2.png)
 
@@ -261,8 +261,6 @@ To visualize the density of orders on the Moscow map, create a [chart](../../dat
 
     ![image](../../_assets/datalens/solution-02/33-choose-heatmap.png)
 
-1. Delete the **Sales** field from the **Colors** section.
-
 1. Select the **Points (heat map)** layer type.
 
 1. Add the delivery point coordinates to the map. To do this, drag the **DeliveryAddressCoord** field from the **Dimensions** section to the **Points (heat map)** section.

diff --git a/en/datasphere/tutorials/video-recognition.md b/en/datasphere/tutorials/video-recognition.md
@@ -39,7 +39,7 @@ To get an idea of how the problem might be solved:
    https://github.com/MaxKhlupnov/ImageClassificationML
    ```
 
-   Wait until cloning is complete. It may take some time. Once the operation is completed, the ![folder](../../_assets/datasphere/jupyterlab/folder.svg) **File Browser** section will show the cloned repository's folder.
+   Wait until cloning is complete. It may take some time. Once the operation is completed, in the ![folder](../../_assets/datasphere/jupyterlab/folder.svg) **File Browser** section, a folder of the cloned repository will appear.
 
 1. Open the **ImageClassificationML** folder and then the `yc.config` file. Replace the file contents with lines from the local file that include your static access key.
 
@@ -217,14 +217,14 @@ There are several practical uses of the model you built:
 
   ```python
   from sparkdl import readImages, KerasImageFileTransformer
-  
+
   # load cctv image body from S3 and return image tensor
 
   def load_image_body_and_process(uri):
       import PIL.image
       from keras.applications.imagenet_utils import preprocess.input
   ...
-  
+
   # load cctv images in batch (from S3 or copy to local hdfs)
 
   image_uri_dataset = readImages("/cctv-in/*.jpg")
@@ -242,3 +242,4 @@ There are several practical uses of the model you built:
   predictions = estimator.fit(image_uri_dataset)
   ```
 
+
diff --git a/en/managed-clickhouse/concepts/update-policy.md b/en/managed-clickhouse/concepts/update-policy.md
@@ -1,8 +1,9 @@
 # {{ CH }} versioning policy
 
-{{ CH }} has a frequent release policy. In {{ mch-name }}, a limited set of {{ CH }} versions is available for use, and this set is continually maintained to ensure it is up to date. If the {{ CH }} version used in a {{ mch-name }} cluster becomes outdated, the cluster's version gets updated.
+{{ CH }} has a frequent release policy. In {{ mch-name }}, a limited set of {{ CH }} versions is available, which is continually updated. If the {{ CH }} version used in a {{ mch-name }} cluster becomes obsolete, it gets updated.
 
 Updating to current versions allows you to get new functionality, patches, and security fixes, which improves the overall stability of the cluster.
+
 Each {{ CH }} version supported by {{ mch-name }} undergoes comprehensive testing.
 
 You can be confident that your data will remain safe and accessible after updating to a new supported version of {{ CH }}.
@@ -17,13 +18,13 @@ You can be confident that your data will remain safe and accessible after updati
 
   Two LTS versions are supported: the current one and the previous one.
 
-  When a new LTS version is released in {{ mch-name }}, the previous LTS version is deprecated. Users with clusters deployed on the current LTS version are notified that support for this version will be discontinued in 6 months.
+  When a new LTS version is released in {{ mch-name }}, the oldest available LTS version stops being supported.
 
 - **Interim**.
 
-  The three latest interim {{ CH }} versions that are not LTS versions are supported.
+  The three latest {{ CH }} versions, including interim ones, are supported. If one of these versions is an LTS version, only two interim versions are supported.
 
-  When a new interim version of {{ CH }} is released in {{ mch-name }}, the oldest of the three supported interim versions is deprecated.
+  When a new interim {{ CH }} version is released in {{ mch-name }}, the oldest interim version stops being supported.
 
 You can manually [change the cluster version](../operations/cluster-version-update.md) to one of the supported versions.
 
@@ -46,7 +47,7 @@ You can manually [change the cluster version](../operations/cluster-version-upda
 
   {% note warning %}
 
-  Notifications about the scheduled update of clusters using a deprecated LTS version are sent to users **2 months**, **1 month**, and **1 week** before the update.
+  Notifications about the scheduled update of clusters using a deprecated LTS version are sent to users **2 months** and **1 week** before the update.
 
   {% endnote %}
 

diff --git a/en/managed-kafka/concepts/network.md b/en/managed-kafka/concepts/network.md
@@ -8,7 +8,7 @@ When creating a cluster, you can:
 * Set subnets in all availability zones.
 * Turn on public access to the cluster from outside {{ yandex-cloud }}.
 
-If hosts are present in the {{ ZK }} cluster, each of the three {{ ZK }} hosts uses its dedicated availability zone and the subnet selected in it. For more information, see [{#T}](../concepts/index.md).
+If hosts are present in the {{ ZK }} cluster, each of the three {{ ZK }} hosts uses its dedicated availability zone and the subnet selected in it. For more information, see [{#T}](index.md).
 
 ## Hostname and FQDN {#hostname}
 
@@ -17,10 +17,30 @@ If hosts are present in the {{ ZK }} cluster, each of the three {{ ZK }} hosts u
 
 You can use the FQDN to access the host within a single cloud network. Read more in the [{{ vpc-full-name }} documentation](../../vpc/).
 
-## Public access to the cluster {public-access-to-a-cluster}
+## Public access to clusters {#public-access-to-a-cluster}
 
 All [broker hosts](brokers.md) in the cluster are available from outside {{ yandex-cloud }} if you request public access when [creating a cluster](../operations/cluster-create.md). To connect to such a cluster, use the FQDN of one or more of the cluster's broker hosts.
 
 You can't request public access after creating a cluster.
 
 When you delete a cluster with public access enabled, all public IP addresses assigned to this cluster are revoked.
+
+## Security groups {#security-groups}
+
+{% include [sg-rules-limits](../../_includes/mdb/sg-rules-limits.md) %}
+
+{% note tip %}
+
+When connecting to a cluster from within its cloud network, be sure to [configure](../operations/connect.md#configuring-security-groups) security groups both for the cluster and the connecting host.
+
+{% endnote %}
+
+Specifics of working with security groups:
+
+- Security group settings only affect the capacity to connect to the cluster. They do not affect cluster operation: replication of topic sections by broker hosts, connections between brokers and {{ ZK }} hosts, and other features.
+
+- Even if the cluster and the connecting host are in the same security group, the connection won't be possible unless rules that allow traffic between the host and cluster are set up in this group.
+
+  However, by default, those rules are contained in the security group that is added automatically when creating a cloud network. Those are the `Self` rules that allow unlimited traffic within a group.
+
+For more information, see the [Virtual Private Cloud documentation](../../vpc/concepts/security-groups.md).
diff --git a/en/managed-kafka/operations/cluster-create.md b/en/managed-kafka/operations/cluster-create.md
@@ -119,6 +119,143 @@ A cluster in {{ mkf-name }} is one or more broker hosts where topics and their p
 
     To create a cluster:
 
+    1. In the configuration file, describe the parameters of resources that you want to create:
+
+        {% include [terraform-create-cluster-step-1](../../_includes/mdb/terraform-create-cluster-step-1.md) %}
+
+        Example configuration file structure:
+
+        ```hcl
+        terraform {
+          required_providers {
+            yandex = {
+             source = "yandex-cloud/yandex"
+            }
+          }
+        }
+        
+        provider "yandex" {
+          token = "<OAuth or static key of service account>"
+          cloud_id  = "<cloud ID>"
+          folder_id = "<folder ID>"
+          zone      = "<availability zone>"
+        }
+        
+        resource "yandex_mdb_kafka_cluster" "<cluster name>" {
+          environment = "<PRESTABLE or PRODUCTION>"
+          name        = "<cluster name>"
+          network_id  = "<network ID>"
+          security_group_ids = ["<list of security groups>"]
+        
+          config {
+            assign_public_ip = "<public access to the cluster: true or false>"
+            brokers_count    = <number of brokers>
+            version          = "<Apache Kafka version: 2.1 or 2.6>"
+            kafka {
+              resources {
+                disk_size          = <storage size in GB>
+                disk_type_id       = "<storage type: network-ssd, network-hdd, or local-ssd>"
+                resource_preset_id = "<host class>"
+              }
+            }
+        
+            zones = [
+              "<availability zones>"
+            ]
+          }
+        }
+        
+        resource "yandex_vpc_network" "<network name>" {
+          name = "<network name>"
+        }
+        
+        resource "yandex_vpc_subnet" "<subnet name>" {
+          name           = "<subnet name>"
+          zone           = "<availability zone>"
+          network_id     = "<network ID>"
+          v4_cidr_blocks = ["<range>"]
+        }
+        ```
+
+        For more information about resources that can be created using Terraform, see the [provider documentation](https://registry.terraform.io/providers/yandex-cloud/yandex/latest/docs/resources/mdb_kafka_cluster).
+
+    1. Make sure that the configuration files are correct.
+
+        {% include [terraform-create-cluster-step-2](../../_includes/mdb/terraform-create-cluster-step-2.md) %}
+
+    1. Create a cluster.
+
+        {% include [terraform-create-cluster-step-3](../../_includes/mdb/terraform-create-cluster-step-3.md) %}
+
+- Terraform
+
+    {% include [terraform-definition](../../solutions/_solutions_includes/terraform-definition.md) %}
+
+    If you don't have Terraform, [install it and configure the provider](../../solutions/infrastructure-management/terraform-quickstart.md#install-terraform).
+
+    To create a cluster:
+
+    1. In the configuration file, describe the parameters of resources that you want to create:
+
+        {% include [terraform-create-cluster-step-1](../../_includes/mdb/terraform-create-cluster-step-1.md) %}
+
+        Example configuration file structure:
+
+        ```go
+        terraform {
+          required_providers {
+            yandex = {
+             source = "yandex-cloud/yandex"
+            }
+          }
+        }
+        
+        provider "yandex" {
+          token = "<OAuth or static key of service account>"
+          cloud_id  = "<cloud ID>"
+          folder_id = "<folder ID>"
+          zone      = "<availability zone>"
+        }
+        
+        resource "yandex_mdb_kafka_cluster" "<cluster name>" {
+        environment = "<PRESTABLE or PRODUCTION>"
+        name        = "<cluster name>"
+        network_id  = "<network ID>"
+        
+        config {
+          assign_public_ip = "<public access to the cluster: true or false>"
+          brokers_count    = <number of brokers>
+          version          = "<Apache Kafka version: 2.1 or 2.6>"
+          kafka {
+            resources {
+              disk_size          = <storage size in GB>
+              disk_type_id       = "<storage type: network-ssd, network-hdd, or local-ssd>"
+              resource_preset_id = "<host class>"
+            }
+          }
+        
+          zones = [
+            "<availability zones>"
+            ]
+          }
+        }
+        
+        resource "yandex_vpc_network" "<network name>" {
+          name = "<network name>"
+        }
+        
+        resource "yandex_vpc_subnet" "<subnet name>" {
+          name           = "<subnet name>"
+          zone           = "<availability zone>"
+          network_id     = "<network ID>"
+          v4_cidr_blocks = ["<range>"]
+        }
+        ```
+
+    If you don't have Terraform, [install it and configure the provider](../../solutions/infrastructure-management/terraform-quickstart.md#install-terraform).
+
+    To create a cluster:
+
     1. In the configuration file, describe the parameters of resources that you want to create:
 
         {% include [terraform-create-cluster-step-1](../../_includes/mdb/terraform-create-cluster-step-1.md) %}
@@ -197,6 +334,12 @@ If you specified security group IDs when creating a cluster, you may also need t
 
 {% endnote %}
 
+{% note warning %}
+
+If you specified security group IDs when creating a cluster, you may also need to [re-configure security groups](connect.md#configuring-security-groups) to connect to the cluster.
+
+{% endnote %}
+
 ## Examples {#examples}
 
 ### Creating a single-host cluster {#creating-a-single-host-cluster}
@@ -238,7 +381,7 @@ If you specified security group IDs when creating a cluster, you may also need t
 - Terraform
 
   Let's say we need to create a {{ mkf-name }} cluster with the following characteristics:
-    - In the cloud with the ID `{{ tf-cloud-id }}`.
+    - In the cloud with ID `{{ tf-cloud-id }}`.
     - In the folder with the ID `{{ tf-folder-id }}`.
     - With the name `mykf`.
     - In the `PRODUCTION` environment.