VMware SIG Purpose, Projects managed, How to join ## The Roadmap Moving “Out of Tree”: vSphere cloud provider + storage (CSI) ## How to Get Information on an ongoing basis The VMware SIG How to Contribute instance ## SIG Sponsored projects ## vSphere cloud provider (In-tree and Out-of-tree) - A cloud provider is a Kubernetes controller that runs cloud provider-specific loops required for the functioning of kube-controller-manager to cloud-provider specific code. In order to free the Kubernetes project of this dependency, the cloud-controller-manager was introduced. ## CSI provider for vSphere - Container Storage

components: • A pluggable ordering service establishes consensus on the order of transactions and then broadcasts blocks to peers. • A pluggable membership service provider is responsible for associating entities network with cryptographic identities. • An optional peer-to-peer gossip service disseminates the blocks output by ordering service to other peers. • Smart contracts (“chaincode”) run within a container decoupled from the peers that execute transactions and maintain the ledger. Specifically, the ordering service. Since consensus is modular, its implementation can be tailored to the trust assumption of a particular

components: • A pluggable ordering service establishes consensus on the order of transactions and then broadcasts blocks to peers. - A pluggable membership service provider is responsible for associating network with cryptographic identities. - An optional peer-to-peer gossip service disseminates the blocks output by ordering service to other peers. - Smart contracts (“chaincode”) run within a container decoupled from the peers that execute transactions and maintain the ledger. Specifically, the ordering service. Since consensus is modular, its implementation can be tailored to the trust assumption of a particular

components: • A pluggable ordering service establishes consensus on the order of transactions and then broadcasts blocks to peers. - A pluggable membership service provider is responsible for associating network with cryptographic identities. - An optional peer-to-peer gossip service disseminates the blocks output by ordering service to other peers. - Smart contracts (“chaincode”) run within a container decoupled from the peers that execute transactions and maintain the ledger. Specifically, the ordering service. Since consensus is modular, its implementation can be tailored to the trust assumption of a particular

cppcon_add_library(service LIBRARIES Asio::asio) add_subdirectory(tests)

components: • A pluggable ordering service establishes consensus on the order of transactions and then broadcasts blocks to peers. - A pluggable membership service provider is responsible for associating network with cryptographic identities. - An optional peer-to-peer gossip service disseminates the blocks output by ordering service to other peers. - Smart contracts (“chaincode”) run within a container decoupled from the peers that execute transactions and maintain the ledger. Specifically, the ordering service. Since consensus is modular, its implementation can be tailored to the trust assumption of a particular

## Observability on Service Mesh 吴晟 Apache SkyWalking 创始人、PPMC Microsoft MVP 比特大陆 资深技术专家 Tetrate ## Skywalking ## CLOUD NATIVE COMPUTING FOUNDATION  Service B ### SkyWalking 6.0 Observability Analysis

## Service Mesh in China 宋净超（Jimmy Song） Tetrate  ## Agenda • ServiceMesher • 行业现状 · 资料分享 · 社区计划  ServiceMesher 2018 年 5 月至今 ## ServiceMesher 大事记 • 2017 年 12 月，由数人云发起的 meetup，下一代微服务：Service Mesh is Coming • 2018 年 5 月，servicemesher.com 上线及 ServiceMesher 公众号开通 • 2018 年 5 月，ServiceMesher

## 微博Service Mesh实践 —Weibo Mesh ## 微博搜索/丁振凯 2018.07.29 ## 内容提要 CONTENTS  1. 跨语言服务化的必要性及难点  ## Service Mesh与微服务的切分 ![Image](/uploads/documents/3/f/9/ path: com.weibo.api.FeedService basicRefer: api-core-basicRefer motan2://127.0.0.1:agent_port/service=path?group=group ## 正向代理流程 ![Image](/uploads/documents/3/f/9/1/3f919351e88389811ca804a10272f5d0/p29_1

Service Mesh Meetup #5 广州站 ## 唯品会Service Mesh的实践分享 郑德惠 2019.1.6 • 唯品会内部Service Mesh的演进 • 与Istio的区别 • 实践中踩过的坑 • 今年规划（Roadmap） ## 内部Service Mesh的演进 ### 服务化体系1.0 Service Registry Service Config 服务路由网络传输 • OSP (Open Service Platform) • Thrift over Netty • 基于Java语法的DSL • Zookeeper 服务元数据下发 - 胖客户端 • 基本服务治理功能 ## 缺点 • 语言单一 · 升级困难 • 复杂代码嵌入对客户端进程影响大 ### 服务化体系2.0 - Service Mesh雏形 ![Image](/ 尽量减少外部组件依赖。业务/运维总会有各种特殊的需求，依赖外部组件会给自定义需求带来障碍。 - 保持客户端选择proxy的自由度和灵活性，在我们的实践中好处大于坏处 #### 胖客户端 vs. service mesh vs. cluster ||胖客户端|Sidecar（物理机）Daemonset（云）|Cluster（HTTP）| |---|---|---|---| |接入难度|容易。打入依