Date: Thu, 28 Mar 2024 16:45:59 +0000 (UTC) Message-ID: <1173751484.3329.1711644359572@aws-us-west-2-tungsten-confluence-1.web.codeaurora.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3328_170766107.1711644359571" ------=_Part_3328_170766107.1711644359571 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Title:
Bring Your Own Orchestrator: Yandex.Cloud experience
Abstrac=
t:
Tungsten Fabric plays nice with OpenStack and Kubernetes. The documentation=
(https://tungstenfabric.github.io/website/ also li=
sts BYOO (Bring Your Own Orchestrator), which remains somewhat uncharted sp=
ot on the map. How it really feels to bring a new cloud platform to the pro=
ject? In this talk, we are going to approach the answer from the perspectiv=
e of Yandex.Cloud (https://cloud.yandex.com a newly launched public =
cloud platform from Yandex (NSDQ: YNDX).
The history of Yandex.Cloud begins before Tungsten Fabric project was offic=
ially born, and this gives us an unique opportunity to look at the issues t=
he "community reboot" has solved, as well as to mention the others which st=
ill remain. Being a large project with its own vision on deployment and ope=
rations, Yandex.Cloud stresses components flexibility in terms of architect=
ure and data flows. Finally, Yandex.Cloud environment leans towards IPv6, w=
hich brings us a third set of the problems to cope with.
Speakers*:
- Valentin Sinitsyn, Yandex (valesini@yandex-team.ru)
Full talk/lighting talk: Preferably a full talk
Includes live demo: No