Skip to content

Commit 2d2c580

Browse files
author
DataUI VCS Robot
committed
Release 22.11.2022
* Cloud Backup: added an article about connecting Compute Cloud VMs to Cloud Backup. * Data Transfer: added an article to the Troubleshooting guide * Glossary: added articles for the GPU, Rest API, and MQTT broker * Translations updated. * Fixes and improvements.
1 parent 27c14ca commit 2d2c580

File tree

225 files changed

+7054
-4186
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

225 files changed

+7054
-4186
lines changed
Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{% note warning %}
22

3-
This functionality is only available when agreed upon by your account manager.
3+
This functionality is only available when agreed by your account manager.
44

55
{% endnote %}
66

@@ -10,5 +10,4 @@ which transfers network load from instance cores to dedicated physical server re
1010

1111
[The cost](../../compute/pricing.md#software-accelerated-network) of additional hardware resources depends on the [platform](../../compute/concepts/vm-platforms.md) and the number of VM cores.
1212

13-
To enable a software-accelerated network, [update the settings](../../compute/operations/vm-control/vm-update-resources.md#enable-software-accelerated-network) of the existing VM or select the **Software-accelerated network** option when [creating a new VM](../../compute/operations/vm-create/create-linux-vm.md).
14-
13+
To enable a software-accelerated network, [update the settings](../../compute/operations/vm-control/vm-update-resources.md#enable-software-accelerated-network) of the existing VM or select the **Software-accelerated network** option when [creating a new VM](../../compute/operations/vm-create/create-linux-vm.md).
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
{% cut "Sample data schema" %}
2+
```json
3+
[
4+
{
5+
"name": "request",
6+
"type": "string"
7+
}
8+
]
9+
```
10+
{% endcut %}

en/_includes/data-transfer/kf-yds-evhub-additional-settings.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
12
* **Transformation rules**
23

34
The rules used by Cloud Function to process an incoming stream:
@@ -29,12 +30,16 @@
2930

3031
{% endnote %}
3132

33+
3234
* **Conversion rules**:
3335

3436
* **Data format**: Select one of the available formats:
3537
* `JSON`
3638
* `CSV`
3739

3840
* **Data schema**: Specify the schema as a list of fields or upload a file with a description of the schema in JSON format.
41+
42+
{% include notitle[json-schema-sample](fields/common/ui/json-schema-sample.md) %}
43+
3944
* **Add unmarked columns**: Select this option to have the fields missing in the schema appear in the `_rest` column.
4045
* **Allow null in key columns**: Select this option to allow the `null` value in key columns.
Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
1-
You can upload small amounts of data (up to 100 MB) to your {{ ml-platform-name }} project over the {{ jlab }}Lab interface. If you want to upload larger amounts of data, use your network storages or databases. For larger data volumes, it's also convenient to use [datasets](../../datasphere/concepts/dataset.md).
2-
3-
To upload data to your project over the {{ jlab }}Lab interface:
4-
5-
1. Under the ![folder](../../_assets/datasphere/jupyterlab/folder.svg) **File Browser** section, select the directory to upload a data to.
6-
1. Click ![upload](../../_assets/datasphere/jupyterlab/upload.svg) at the top left.
7-
1. Select the files to upload.
8-
9-
[Learn more about project storage](../../datasphere/concepts/project.md#storage).
10-
11-
{{ ml-platform-name }} lets you upload data from different sources:
12-
13-
* [{#T}](../../datasphere/operations/data/connect-to-s3.md).
14-
* [{#T}](../../datasphere/operations/data/connect-to-google-drive.md).
15-
* [{#T}](../../datasphere/operations/data/connect-to-clickhouse.md).
16-
* [{#T}](../../datasphere/operations/data/connect-to-postgresql.md).
1+
You can upload small amounts of data (up to 100 MB) to your {{ ml-platform-name }} project through the {{ jlab }}Lab interface. If you want to upload larger amounts of data, use your network storages or databases. For larger data volumes, it's also convenient to use [datasets](../../datasphere/concepts/dataset.md).
2+
3+
To upload data to your project through the {{ jlab }}Lab interface:
4+
5+
1. Under the ![folder](../../_assets/datasphere/jupyterlab/folder.svg) **File Browser** section, select the directory to upload a data to.
6+
1. Click ![upload](../../_assets/datasphere/jupyterlab/upload.svg) at the top left.
7+
1. Select the files to upload.
8+
9+
[Learn more about project storage](../../datasphere/concepts/project.md#storage).
10+
11+
{{ ml-platform-name }} lets you upload data from different sources:
12+
13+
* [{#T}](../../datasphere/operations/data/connect-to-s3.md).
14+
* [{#T}](../../datasphere/operations/data/connect-to-google-drive.md).
15+
* [{#T}](../../datasphere/operations/data/connect-to-clickhouse.md).
16+
* [{#T}](../../datasphere/operations/data/connect-to-postgresql.md).
1717
* [{#T}](../../datasphere/operations/data/connect-to-ya-disk.md).

en/_includes/datasphere/migration/release-notes-old.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,3 @@
1-
{% note tip %}
2-
3-
To keep up to date with the latest changes and updates, subscribe to our [{{ ml-platform-full-name }} Community](https://t.me/yandex_datasphere) Telegram news channel.
4-
5-
{% endnote %}
6-
71
## Release 11.01.2022 {#110122}
82

93
1. Added new computing resource configurations:
Lines changed: 72 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,72 @@
1+
# Public materials about {{ ml-platform-name }}
2+
3+
## Conferences and webinars {#conf-and-webinars}
4+
5+
### 2022: Yandex Scale {#yandex-scale-2022}
6+
7+
* {{ ml-platform-full-name }}: new UI and team-based ML development capabilities.
8+
9+
* [Recorded broadcast](https://youtu.be/xzEW5g7WVd4).
10+
11+
### 2022: Announcement {#announcement-2022}
12+
13+
* New version 2.0 of {{ ml-platform-full-name }} service for machine learning developers.
14+
15+
* [Recorded broadcast](https://youtu.be/Mhjkh386Ajw).
16+
17+
### 2021: Yandex Scale {#yandex-scale-2021}
18+
19+
* Cloud generation of laptops: from exercise books to the data realm.
20+
21+
* [Recorded broadcast](https://youtu.be/vKLqfcKXRo8).
22+
23+
* Recommendation system powered by {{ ml-platform-short-name }}.
24+
25+
* [Recorded broadcast](https://youtu.be/oavkOOJMVK8).
26+
27+
* Cloud tools for ML developers, Igor Kuralionok.
28+
29+
* [Recorded broadcast](https://youtu.be/euqmLppB4f0).
30+
31+
### 2021: Meetup {#meetup-2021}
32+
33+
* about:cloud — ML&AI.
34+
35+
* [Recorded broadcast](https://youtu.be/qWO2P0Mc_Bc).
36+
37+
### 2021: Webinar {#webinar-2021}
38+
39+
* Webinar about new {{ ml-platform-short-name }} features for ML development.
40+
41+
* [Recorded broadcast](https://youtu.be/udZcoKwb6aM).
42+
43+
### 2021: Workshop {#workshop-2021}
44+
45+
* Creating a chat QA assistant using {{ ml-platform-full-name }}.
46+
47+
* [Recorded broadcast](https://youtu.be/fHQAT6rYO7c).
48+
49+
### 2020: Yandex Scale {#yandex-scale-2020}
50+
51+
* Presentation on {{ ml-platform-short-name }} technicalities at Yandex Scale 2020.
52+
* [Recorded broadcast](https://youtu.be/5y2-x9GcITs).
53+
54+
* Presentation on {{ ml-platform-short-name }} features at Yandex Scale 2020.
55+
* [Recorded broadcast](https://youtu.be/MtXpZ4RZAjk).
56+
57+
* Presentation on how to implement ML using {{ yandex-cloud }} at Yandex Scale 2020.
58+
* [Recorded broadcast](https://youtu.be/MxuABVNZV38).
59+
60+
### 2020: Webinar {#webinar-2020}
61+
62+
* Practical webinar about new {{ ml-platform-short-name }} features.
63+
64+
* [Recorded broadcast](https://youtu.be/70lIkTJjAZU).
65+
66+
* Webinar on how to use {{ ml-platform-short-name }} to process videos and detect objects in video frames.
67+
68+
* [Recorded broadcast](https://youtu.be/55qc9YHbVwE).
69+
70+
* Practical webinar on data science in {{ yandex-cloud }}.
71+
72+
* [Recorded broadcast](https://youtu.be/5o5OJOwDfaU).
Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
1-
Open the project {{ ml-platform-name }}:
2-
3-
1. {% include [find project](../../_includes/datasphere/ui-find-project.md) %}
4-
1. Click **Open project in {{ jlab }}Lab** and wait for the loading to complete.
1+
Open the project {{ ml-platform-name }}:
2+
3+
1. {% include [find project](../../_includes/datasphere/ui-find-project.md) %}
4+
1. Click **Open project in {{ jlab }}Lab** and wait for it to load.
55
1. Open the notebook tab.
Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
```json
2+
{
3+
"messages":[
4+
{
5+
"billing_account_id":"a6q6***",
6+
"budget_id":"a626***",
7+
"budget_display_name":"name",
8+
"amount":90012.00,
9+
"currency":"RUB",
10+
"period":"2021",
11+
"budgeted_amount":100000.00,
12+
"threshold_amount":90000.00,
13+
"threshold_type":"amount"
14+
}
15+
]
16+
}
17+
```
18+
19+
Where:
20+
21+
* `billing_account_id`: Billing account ID.
22+
* `budget_id`: Budget ID.
23+
* `budget_display_name`: Budget name.
24+
* `amount`: The cost of resources or account balance when notifications were triggered.
25+
* `currency`: Payment currency.
26+
* `period`: Budget tracking period.
27+
* `budgeted_amount`: Budget amount.
28+
* `threshold_amount`: Consumption threshold that triggered notifications.
29+
* `threshold_type`: Threshold type:
30+
* `amount`: Currency.
31+
* `percent`: Percentage.

en/_includes/functions/cr-event.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
## Events for setting up a trigger {#event}
2+
3+
Events with Docker images that can be tracked using a trigger:
4+
* [Creating a Docker image](../../container-registry/operations/docker-image/docker-image-push.md).
5+
* [delete Docker images](../../container-registry/operations/docker-image/docker-image-delete.md).
6+
* Creating a Docker image tag.
7+
* Deleting a Docker image tag.
8+
9+
A Docker image is always pushed with a tag (if no tag is specified, Docker automatically inserts the `latest` tag). Therefore the `CreateImage` event is always paired with `CreateImageTag`. You can add an arbitrary number of tags to a Docker image by pushing the same image with other tags. In this case, only the `CreateImageTag` event will occur, without `CreateImage`.
10+
11+
A tag can go from one Docker image to another. This happens when pushing a new Docker image with a tag that is already used in another Docker image. In this case, the `CreateImage` event will occur for the new Docker image, while changing the tag will trigger two events: `DeleteImageTag` (removing the tag from the old Docker image) and `CreateImageTag` (assigning the tag to the new Docker image).
12+
13+
When you delete a Docker image, all its tags are deleted. This is why deleting a Docker image always triggers the `DeleteImage` event and as many `DeleteImageTag` events as the Docker image had tags at the time of deletion.
14+
15+
### Filtering events {#filter}
16+
17+
Events are filtered using tags and names of Docker images that you push. When using a name and tag at the same time, filtering is done based on the logical `AND`: for the trigger to work, the image must match both the name and tag.

en/_includes/functions/cr-format.md

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
```json
2+
{
3+
"messages": [
4+
{
5+
"event_metadata": {
6+
"cloud_id": "b1gvlrnl************",
7+
"created_at": "2020-09-07T11:09:14Z",
8+
"event_id": "crtpk611************",
9+
"event_type": "yandex.cloud.events.containerregistry.CreateImage",
10+
"folder_id": "b1g88tfl************",
11+
"tracing_context": {
12+
"parent_span_id": "-1491579************",
13+
"span_id": "-7232663************",
14+
"trace_id": "70e7************"
15+
}
16+
},
17+
"details": {
18+
"image_digest": "sha256:45f8f740272f1f2a053eade37d8d************************************",
19+
"image_id": "crti2c9b************",
20+
"registry_id": "crt2504s************",
21+
"repository_name": "crt2504s************/ubuntu",
22+
"tag": "latest"
23+
}
24+
}]
25+
}
26+
```

0 commit comments

Comments
 (0)