Estimation of availability and reliability in CurveBS CurveBS uses the RAFT protocol to maintain consistency of stored data. It generally takes the form of 3 replicas of data. If one replica fails required to handle the failure according to the actual situation of the system. Estimation of availability and reliability in the three- replicas case Assume that the total number of disks in Curve

Distribution 6 High Availability of Registry Agenda 1 Container Image Basics 2 Project Harbor Introduction 3 Consistency of Images 4 Security 5 Image Distribution 6 High Availability of Registry 2 Project Harbor Introduction 3 Consistency of Images 4 Security 5 Image Distribution 6 High Availability of Registry Project Harbor • An open source enterprise-class registry server. • Initiated 2 Project Harbor Introduction 3 Consistency of Images 4 Security 5 Image Distribution 6 High Availability of Registry Consistency of Container Images • Container images are used throughout the life

CURVE: a High-performance Software-Defined storage for Cloud Native applications Xiang Dong Architect, Netease Hangzhou Research InstituteAgenda � Why develop storage Design objectives Achievements file systemopen-source storage ● Requirements ○ Cloud Native ○ Easy operation and maintenance ○ High performance ● CEPH ○ Complex and Large amount of codes ○ system maintenance are difficult in corner block Storage for KVM / Kubernetes / iSCSI Design objectives ● Thin provisioning storage pools ● High performance ● Easy maintenance ● Cloud NativeAgenda Why develop storage Design objectives �

on ssl_ca_file = 'root.crt' ssl_cert_file = 'server.crt' ssl_key_file = 'server.key' ssl_ciphers = 'HIGH:MEDIUM:+3DES:!aNULL' ssl_prefer_server_ciphers = on ssl_min_protocol_version = 'TLSv1.3' ... For agents and active proxies. At least one trapper process must be running to display server availability and view queue in the frontend. The upper limit used to be 255 before version 1.8.5. 59 资源不可用期间， Zabbix 多少秒检查一 次资源是否可用。 UnavailableDelay no 1-3600 60 How often host is checked for availability during the unavailability period, in seconds. UnreachableDelay 否 -3600 5 资源不可达期间， Zabbix 多少秒检查一

agents and active proxies. At least one trapper process must be running to display server availability and view queue in the frontend. The upper limit used to be 255 before version 1.8.5. 35 资源不可用期间， Zabbix 多少秒检查一 次资源是否可用。 UnavailableDelay no 1-3600 60 How often host is checked for availability during the unavailability period, in seconds. UnreachableDelay 否 -3600 5 资源不可达期间， Zabbix 多少秒检查一 多少秒检查一 次资源是否可达。 UnreachableDelay no 1-3600 15 How often host is checked for availability during the unreachability period, in seconds. UnreachablePeriod 否 -3600 5 主机不可用多少秒后， 即视为主机不可用。 UnreachablePeriod

Application Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Mass data high concurrency in OLTP scenarios . . . . . . . . . . . . . . . . . . . 22 Mass data real‐time analysis Re ad /w ri te S pl it ti ng Read/write splitting can be used to cope with business access with high stress. Sharding‐ Sphere provides flexible read/write splitting capabilities and can achieve read Connections Count Cost More Less Heterogeneous language Java Only Any Performance Low loss Relatively High loss Decentralization Yes No Static entry No Yes 3.2 Using ShardingSphere-Proxy ShardingSphere‐Proxy

agents and active proxies. At least one trapper process must be running to display server availability and view queue in the frontend. The upper limit used to be 255 before version 1.8.5. 35 资源不可用期间， Zabbix 多少秒检查一 次资源是否可用。 UnavailableDelay no 1-3600 60 How often host is checked for availability during the unavailability period, in seconds. UnreachableDelay 否 -3600 5 资源不可达期间， Zabbix 多少秒检查一 多少秒检查一 次资源是否可达。 UnreachableDelay no 1-3600 15 How often host is checked for availability during the unreachability period, in seconds. UnreachablePeriod 否 -3600 5 主机不可用多少秒后， 即视为主机不可用。 UnreachablePeriod

nature ● Storage engine redesign & reimplementation ○ Save more CPU, RAM & IOPS ○ Scale to far high number of time series ○ Better performance in face of pod churn ● Improved staleness semanticPrometheus of the dataHigh Availability ● Too critical, should be the last one standing… ● But there are... ○ hardware failures ○ software failures ○ Maintenance and upgradesHigh Availability ● In the old days prometheus prometheus prometheus GrafanaHigh Availability ● In the old days... ○ Adding more independent replicas prometheus prometheus

agents and active proxies. At least one trapper process must be running to display server availability and view queue in the frontend. The upper limit used to be 255 before version 1.8.5. 37 资源不可用期间， Zabbix 多少秒检查一 次资源是否可用。 UnavailableDelay no 1-3600 60 How often host is checked for availability during the unavailability period, in seconds. UnreachableDelay 否 -3600 5 资源不可达期间， Zabbix 多少秒检查一 多少秒检查一 次资源是否可达。 UnreachableDelay no 1-3600 15 How often host is checked for availability during the unreachability period, in seconds. UnreachablePeriod 否 -3600 5 主机不可用多少秒后， 即视为主机不可用。 UnreachablePeriod

VMware SIG Deep Dive into Kubernetes Scheduling Performance and high availability options for vSphere Steve Wong, Hui Luo VMware Cloud Native Applications Business Unit November 12, 2018 2 Open across availability zones, while still respecting resource access and availability concerns. When Kubernetes runs on vSphere, the hypervisor platform also supports an underlying tier of high availability ​This session will explain the options to gain better performance, resource optimization and availability through tuning of vSphere, and Kubernetes configuration and labeling. This is applicable to any