Skip to content

Commit

Permalink
Release 28.05.2021
Browse files Browse the repository at this point in the history 
* Container Solution: added instruction how to find out COI version.
* Data Transfer: added tutorial how to synchronise data from MySQL using Data Transfer.
* Fixes and improvements.
* Translations updated.
  • Loading branch information
DataUI VCS Robot committed May 28, 2021
1 parent 46be594 commit 750dd01
Show file tree
Hide file tree
Showing 27 changed files with 490 additions and 429 deletions.
Binary file added en/_assets/datalens/solution-10/32-choose-catalog.png
View file
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added en/_assets/datasphere/bug.png
View file
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 10 additions & 2 deletions en/_cli-ref/cli-ref/managed-services/compute/instance/create.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -14,10 +14,18 @@ Syntax:
|----|----|
|`--name`|<b>`string`</b><br/> A name of the instance.|
|`--description`|<b>`string`</b><br/> Specifies a textual description of the instance. --labels key=value[,key=value...] A list of label KEY=VALUE pairs to add.|
|`--zone`|<b>`string`</b><br/> The zone of the instance to create. --metadata key=value[,key=value...] Metadata to be made available to the guest operating system running on the instance. See for details https://cloud.yandex.ru/docs/compute/concepts/vm-metadata --metadata-from-file key=value[,key=value...] Same as --metadata except that the value for the entry will be read from a local file.|
|`--zone`|<b>`string`</b><br/> The zone of the instance to create.|
|`--metadata`|<b>`key=value[,key=value...]`</b><br/> Metadata to be made available to the guest operating system running on the instance. See for details https://cloud.yandex.ru/docs/compute/concepts/vm-metadata|
|`--metadata-from-file`|<b>`key=value[,key=value...]`</b><br/> Same as --metadata except that the value for the entry will be read from a local file.|
|`--ssh-key`|<b>`string`</b><br/> Creates user 'yc-user' and adds SSH key from specified file to authorized keys using cloud-config. If your need more flexibility, use cloud-config passed in 'user-data' metadata key.|
|`--public-ip`| If true, one-to-one NAT public IP will be created for the default network interface. Cannot be passed together with --network-interface|
|`--public-address`|<b>`string`</b><br/> If set, one-to-one NAT public IP will be created for the default network interface with the specified value. Cannot be passed together with --network-interface --create-disk PROPERTY=VALUE[,PROPERTY=VALUE...] Creates and attaches persistent disks to the instance. Possible property names: name Specifies the name of the disk. type The type of the disk. To get a list of available disk types, run 'yc compute disk-type list'. The default disk type is network-hdd. size The size of the disk in GB. You can also use M and T suffixes to specify smaller or greater size respectively. If not specified, inferred size is used. If the disk is created from a snapshot, disk size of the snapshot is used. If the disk is created from an image, size of the image is used.If no source is specified, default disk size is used. block-size Specifies the block size of the disk in bytes. You can also use K and M suffixes. snapshot-name A source snapshot used to create the disk. snapshot-id An ID of the source snapshot used to create the disk. image-name A source image used to create the disk. image-id An ID of the source image used to create the disk. image-family An image family that is used to create the disk. image-folder-id The folder ID that is used to resolve references for image-name or image-family. disk-placement-group-id An ID of the placement group to create the disk in disk-placement-group-name A placement group to create the disk in device-name Specifies a unique serial number of your choice that is reflected into the /dev/disk/by-id/ tree of a Linux operating system running within the instance. auto-delete Specifies if this persistent disk will be automatically deleted when the instance is deleted. --attach-disk PROPERTY=VALUE[,PROPERTY=VALUE...] Attaches persistent disks to the instances. The specified disks must already exist. Possible property names: disk-name The disk to attach to the instance. disk-id An ID of the disk to attach to the instance. device-name Specifies a unique serial number of your choice that is reflected into the /dev/disk/by-id/ tree of a Linux operating system running within the instance. auto-delete Specifies if this persistent disk will be automatically deleted when the instance is deleted. --create-boot-disk PROPERTY=VALUE[,PROPERTY=VALUE...] Creates a new disk and uses it as a boot disk of the instance. Possible property names: name Specifies the name of the disk. type The type of the disk. To get a list of available disk types, run 'yc compute disk-type list'. The default disk type is network-hdd. size The size of the disk in GB. You can also use M and T suffixes to specify smaller or greater size respectively. If not specified, inferred size is used. If the disk is created from a snapshot, disk size of the snapshot is used. If the disk is created from an image, size of the image is used.If no source is specified, default disk size is used. block-size Specifies the block size of the disk in bytes. You can also use K and M suffixes. snapshot-name A source snapshot used to create the disk. snapshot-id An ID of the source snapshot used to create the disk. image-name A source image used to create the disk. image-id An ID of the source image used to create the disk. image-family An image family that is used to create the disk. image-folder-id The folder ID that is used to resolve references for image-name or image-family. disk-placement-group-id An ID of the placement group to create the disk in disk-placement-group-name A placement group to create the disk in device-name Specifies a unique serial number of your choice that is reflected into the /dev/disk/by-id/ tree of a Linux operating system running within the instance. auto-delete Specifies if this persistent disk will be automatically deleted when the instance is deleted. --use-boot-disk PROPERTY=VALUE[,PROPERTY=VALUE...] Uses an already existing disk as a boot disk of the instance. Possible property names: disk-name The disk to attach to the instance. disk-id An ID of the disk to attach to the instance. device-name Specifies a unique serial number of your choice that is reflected into the /dev/disk/by-id/ tree of a Linux operating system running within the instance. auto-delete Specifies if this persistent disk will be automatically deleted when the instance is deleted. --network-settings PROPERTY=VALUE[,PROPERTY=VALUE...] Network settings for the instance. Possible property names: type Type of a network for virtual machine instance. Values: standard, software-accelerated --network-interface PROPERTY=VALUE[,PROPERTY=VALUE...] Adds a network interface to the instance. Possible property names: subnet-name Specifies the subnet that the interface will be part of. subnet-id Specifies the ID of the subnet that the interface will be part of. address Assigns the given internal address to the instance that is created. If no address is specified, some unassigned address from the subnet is used. ipv4-address Assigns the given internal IPv4 address to the instance that is created. If 'auto' used as value, some unassigned address from the subnet is used. nat-ip-version Specifies IP version for One-to-One NAT. Can be 'ipv4'. This flag can be applied to network interfaces with ipv4 address. nat-address Specifies public IP address for One-to-One NAT. This flag can be applied to network interfaces with ipv4 address. security-group-ids Security groups for the network interface, security-group-ids=[id1,id2],security-group-ids=id3 |
|`--public-address`|<b>`string`</b><br/> If set, one-to-one NAT public IP will be created for the default network interface with the specified value. Cannot be passed together with `--network-interface`|
|`--create-disk`|<b>`PROPERTY=VALUE[,PROPERTY=VALUE...]`</b><br/> Creates and attaches persistent disks to the instance.<br/> Possible property names: <ul><li>`name`<br/> Specifies the name of the disk.</li><li>`type`<br/> The type of the disk. To get a list of available disk types, run 'yc compute disk-type list'. The default disk type is network-hdd.</li><li>`size`<br/> The size of the disk in GB. You can also use M and T suffixes to specify smaller or greater size respectively. If not specified, inferred size is used. If the disk is created from a snapshot, disk size of the snapshot is used. If the disk is created from an image, size of the image is used. If no source is specified, default disk size is used.</li><li>`block-size`<br/> Specifies the block size of the disk in bytes. You can also use K and M suffixes. </li><li>`snapshot-name`<br/> A source snapshot used to create the disk.</li><li>`snapshot-id`<br/> An ID of the source snapshot used to create the disk.</li><li>`image-name`<br/> A source image used to create the disk.</li><li>`image-id`<br/> An ID of the source image used to create the disk.</li><li>`image-family`<br/> An image family that is used to create the disk.</li><li>`image-folder-id`<br/> The folder ID that is used to resolve references for image-name or image-family.</li><li>`disk-placement-group-id`<br/> An ID of the placement group to create the disk in</li><li>`disk-placement-group-name`<br/> A placement group to create the disk in</li><li>`device-name`<br/> Specifies a unique serial number of your choice that is reflected into the /dev/disk/by-id/ tree of a Linux operating system running within the instance.</li><li>`auto-delete`<br/> Specifies if this persistent disk will be automatically deleted when the instance is deleted.</li></ul>|
|`--attach-disk`|<b>`PROPERTY=VALUE[,PROPERTY=VALUE...]`</b><br/> Attaches persistent disks to the instances. The specified disks must already exist.<br/>Possible property names:<ul><li>`disk-name`<br/> The disk to attach to the instance.</li><li>`disk-id`<br/> An ID of the disk to attach to the instance.</li><li>`device-name`<br/> Specifies a unique serial number of your choice that is reflected into the /dev/disk/by-id/ tree of a Linux operating system running within the instance.</li><li>`auto-delete`<br/> Specifies if this persistent disk will be automatically deleted when the instance is deleted.</li></ul>|
|`--create-boot-disk`|<b>`PROPERTY=VALUE[,PROPERTY=VALUE...]`</b><br/> Creates a new disk and uses it as a boot disk of the instance.<br/> Possible property names:<ul><li>`name`<br/> Specifies the name of the disk.</li><li>`type`<br/> The type of the disk. To get a list of available disk types, run 'yc compute disk-type list'. The default disk type is network-hdd.</li><li>`size`<br/> The size of the disk in GB. You can also use M and T suffixes to specify smaller or greater size respectively. If not specified, inferred size is used. If the disk is created from a snapshot, disk size of the snapshot is used. If the disk is created from an image, size of the image is used.If no source is specified, default disk size is used.</li><li>`block-size`<br/> Specifies the block size of the disk in bytes. You can also use K and M suffixes.</li><li>`snapshot-name`<br/> A source snapshot used to create the disk.</li><li>`snapshot-id`<br/> An ID of the source snapshot used to create the disk.</li><li>`image-name`<br/> A source image used to create the disk.</li><li>`image-id`<br/> An ID of the source image used to create the disk.</li><li>`image-family`<br/> An image family that is used to create the disk.</li><li>`image-folder-id`<br/> The folder ID that is used to resolve references for image-name or image-family.</li><li>`disk-placement-group-id`<br/> An ID of the placement group to create the disk in</li><li>`disk-placement-group-name`<br/> A placement group to create the disk in</li><li>`device-name`<br/> Specifies a unique serial number of your choice that is reflected into the /dev/disk/by-id/ tree of a Linux operating system running within the instance.</li><li>`auto-delete`<br/> Specifies if this persistent disk will be automatically deleted when the instance is deleted.</li></ul>|
|`--use-boot-disk`|<b>`PROPERTY=VALUE[,PROPERTY=VALUE...]`</b><br/> Uses an already existing disk as a boot disk of the instance.<br/> Possible property names:<ul><li>`disk-name`<br/> The disk to attach to the instance.</li><li>`disk-id`<br/> An ID of the disk to attach to the instance.</li><li>`device-name`<br/> Specifies a unique serial number of your choice that is reflected into the /dev/disk/by-id/ tree of a Linux operating system running within the instance.</li><li>`auto-delete`<br/> Specifies if this persistent disk will be automatically deleted when the instance is deleted.</li></ul>|
|`--network-settings`|<b>`PROPERTY=VALUE[,PROPERTY=VALUE...]`</b><br/> Network settings for the instance.<br/>Possible property names:<ul><li>`type`<br/> Type of a network for virtual machine instance. Values: standard, software-accelerated</li></ul>|
|`--network-interface`|<b>`PROPERTY=VALUE[,PROPERTY=VALUE...]`</b><br/> Adds a network interface to the instance.<br/>Possible property names:<ul><li>`subnet-name`<br/> Specifies the subnet that the interface will be part of.</li><li>`subnet-id`<br/> Specifies the ID of the subnet that the interface will be part of.</li><li>`address`<br/> Assigns the given internal address to the instance that is created. If no address is specified, some unassigned address from the subnet is used.</li><li>`ipv4-address`<br/> Assigns the given internal IPv4 address to the instance that is created. If 'auto' used as value, some unassigned address from the subnet is used.</li><li>`nat-ip-version`<br/> Specifies IP version for One-to-One NAT. Can be 'ipv4'. This flag can be applied to network interfaces with ipv4 address.</li><li>`nat-address`<br/> Specifies public IP address for One-to-One NAT. This flag can be applied to network interfaces with ipv4 address.</li><li>`security-group-ids`<br/> Security groups for the network interface, `security-group-ids=[id1,id2],security-group-ids=id3`</li></ul> |
|`--memory`|<b>`byteSize`</b><br/> Specifies how much memory instance should have.|
|`--cores`|<b>`int`</b><br/> Specifies how many CPU cores instance should have.|
|`--core-fraction`|<b>`int`</b><br/> If provided, specifies baseline performance for a core in percent.|
Expand Down
5 changes: 5 additions & 0 deletions en/_includes/container-registry/lifecycle-restrictions.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{% note warning %}

You can only set a lifecycle policy for [a repository](../../container-registry/concepts/repository.md). The policy applies to Docker images whose names match the repository name exactly. There is no support for prefix matching. You can't set a policy for a repository group, registry, folder, or cloud.

{% endnote %}
2 changes: 1 addition & 1 deletion en/_includes/datasphere/install-dependencies-steps.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ To install a package:
%pip install seaborn
```
You can use various options that the [pip install](https://pip.pypa.io/en/stable/reference/pip_install/) command supports. See a [usage examples](https://pip.pypa.io/en/stable/reference/pip_install/#pip-install-examples) of the command.
You can use various options that the [pip install](https://pip.pypa.io/en/stable/cli/pip_install/) command supports. See a [usage examples](https://pip.pypa.io/en/stable/cli/pip_install/#pip-install-examples) of the command.
1. Run the cell. To do this, click ![Run](../../_assets/datasphere/jupyterlab/run.svg).
Expand Down
11 changes: 11 additions & 0 deletions en/_includes/datasphere/notebook-support.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
To contact technical support in the service:

1. Click ![image](../../_assets/datasphere/bug.png) in the lower-right corner of the notebook window or select **Report a bug** in the **Help** menu.

1. In the window that opens, describe your problem in the **Bug** and **Give us more detail** fields.

1. Click **Report a bug**.
You'll receive your request number by email.

You can monitor the request status via the Yandex.Cloud mobile app for [iOS](https://apps.apple.com/app/yandex-cloud/id1515465314) or [Android](https://play.google.com/store/apps/details?id=ru.yandex.cloud) and in the [Support]({{ link-console-support }}) section in the management console.

Loading

0 comments on commit 750dd01

Please sign in to comment.