Supports running on multiple clouds #471
Comments
需求背景：sky computing 拆解一下需求
message GetStateRequest {
// Required. The name of state store.
string store_name = 1;
// Required. The key of the desired state
string key = 2;
// (optional) read consistency mode
StateOptions.StateConsistency consistency = 3;
// (optional) The metadata which will be sent to state store components.
map<string, string> metadata = 4;
}得像 dapr 一样 既有name 也有type
|
|
期待 |
跨云部署”样板间“设计交互设计魔改 Istio 的 Bookinfo 演示工程，加入调用 对象存储、pubsub 的功能 架构图： katacoda 教程拿mosn的改一改，见 https://katacoda.com/mosn/courses/istio phase 0. 服务网格流量治理
phase 1. 跨云移植、跨组件的流量治理
需要开发一个复合组件，支持配规则，根据 header 或 metadata 路由
需要开发对upstream 的流量治理。这个比较难做 理论上可以把每个组件”伪装“成 istio 的一个 service, 这样就能用 istio 治理 所有layotto api 的流量。但估计比较难
需要开发一个复合组件 Phase 2. 空计算，移动计算
Phase 3. 空计算，移动数据演示站点在一个或两个云上部署 BookInfo 项目，演示跨云容灾之类的效果。 |
交互设计 v0.2还是给 Istio 的 Bookinfo 加功能，加入调用 对象存储之类的功能： 还是让用户在katacoda 实验室里部署 BookInfo。 但是架构变成：加入一个 preview service, 我们提前部署在两个云上. pros: cons: 对组件的流量治理所以就有第二个问题：我们究竟要不要做”对组件的流量治理“？ 可以在后续迭代再讨论加入”对组件的流量治理“功能，现在先 start from simple, 收集用户需求 milestonephase 1. 在两个云上部署 preview service
phase 2. katacoda 教程
|
|
This issue has been automatically marked as stale because it has not had recent activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue or help wanted) or other activity occurs. Thank you for your contributions. |
|
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue or help wanted. Thank you for your contributions. |
|
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue or help wanted. Thank you for your contributions. |
2022.6.30 Update:
Roadmap
Since katacoda will close:
https://killercoda.com/mosn-tutorial/
https://killercoda.com/mosn-tutorial/course/layotto
layotto_without_xds#714layotto/proxyv2image after new version is released #708English Version:
Layotto was built with a vision to provide applications with the ability to
Write once, Running on any Cloud..Layotto has built a number of APIs and the components corresponding to those APIs, and has quick start documentation to help users get up and running quickly and locally. But for an application to run locally is not enough, the application needs to be deployed on the cloud to provide production level services and Layotto needs to have the ability to run on several cloud platforms.
The initial expectation is that Layotto can be built to run directly on Aliyun, AWS, and enable the component docking capabilities of the corresponding cloud services according to the specified configuration.
Deployment capabilities can be built in phases:
中文版本：
Layotto 建设之初就有一个愿景，期望提供给应用
Write once, Running on any Cloud.的能力。目前 Layotto 已经建设了很多 API，以及这些 API 对应的组件，并且有快速开始文档可以帮助用户快速的在本地运行起来。但对于一个应用来讲，仅在本地跑起来是不够的，应用需要部署在云上提供生产级服务，Layotto 也需要有能在若干云平台上运行起来的能力。
初期期望 Layotto 可以建设在 Aliyun 、AWS 上直接运行，并能根据指定配置启用对应云服务的组件对接能力。
部署能力可以分阶段来建设：
The text was updated successfully, but these errors were encountered: