openEuler OS Technical Whitepaper
Innovation Projects
(June, 2023)collaborative scheduling of service containers and OSs. • API O&M: Kubernetes-native declarative APIs are used to manage and maintain OSs in a standard manner. • Atomic management: Based on the Kubernetes Features • Compatible with the native Kubernetes system: Capabilities are extended based on extended APIs of native Kubernetes. • Compatible with the openEuler system: Enhanced features (such as hierarchical Lightweight: running in an environment with only tens of KB of memory • Universality » POSIX-compliant APIs » Compatible with multiple instruction set architectures (ISAs) such as x86, AArch64, and Cortex-M0 码力 | 116 页 | 3.16 MB | 1 年前3
Cilium v1.10 Documentationcommunicating with each other? How frequently? What does the service dependency graph look like? What HTTP calls are being made? What Kafka topics does a service consume from or produce to? Network monitoring Is it an application or network problem? Is the communication broken on layer 4 (TCP) or layer 7 (HTTP)? Which services have experienced a DNS resolution problem in the last 5 minutes? Which services monitoring What is the rate of 5xx or 4xx HTTP response codes for a particular service or across all clusters? What is the 95th and 99th percentile latency between HTTP requests and responses in my cluster0 码力 | 1307 页 | 19.26 MB | 1 年前3
Cilium v1.8 Documentationcommunicating with each other? How frequently? What does the service dependency graph look like? What HTTP calls are being made? What Kafka topics does a service consume from or produce to? Network monitoring Is it an application or network problem? Is the communication broken on layer 4 (TCP) or layer 7 (HTTP)? Which services have experienced a DNS resolution problem in the last 5 minutes? Which services monitoring What is the rate of 5xx or 4xx HTTP response codes for a particular service or across all clusters? What is the 95th and 99th percentile latency between HTTP requests and responses in my cluster0 码力 | 1124 页 | 21.33 MB | 1 年前3
Cilium v1.5 Documentationapplica�on is split into small independent services that communicate with each other via APIs using lightweight protocols like HTTP. Microservices applica�ons tend to be highly dynamic, with individual containers that need to be updated with a con�nuously growing frequency. Protocol ports (e.g. TCP port 80 for HTTP traffic) can no longer be used to differen�ate between applica�on traffic for security purposes as contrast to IP address iden�fica�on in tradi�onal systems) and can filter on applica�on-layer (e.g. HTTP). As a result, Cilium not only makes it simple to apply security policies in a highly dynamic environment0 码力 | 740 页 | 12.52 MB | 1 年前3
Cilium v1.11 Documentationcommunicating with each other? How frequently? What does the service dependency graph look like? What HTTP calls are being made? What Kafka topics does a service consume from or produce to? Network monitoring Is it an application or network problem? Is the communication broken on layer 4 (TCP) or layer 7 (HTTP)? Which services have experienced a DNS resolution problem in the last 5 minutes? Which services monitoring What is the rate of 5xx or 4xx HTTP response codes for a particular service or across all clusters? What is the 95th and 99th percentile latency between HTTP requests and responses in my cluster0 码力 | 1373 页 | 19.37 MB | 1 年前3
Cilium v1.6 Documentationapplication is split into small independent services that communicate with each other via APIs using lightweight protocols like HTTP. Microservices applications tend to be highly dynamic, with individual containers that need to be updated with a continuously growing frequency. Protocol ports (e.g. TCP port 80 for HTTP traffic) can no longer be used to differentiate between application traffic for security purposes contrast to IP address identification in traditional systems) and can filter on application-layer (e.g. HTTP). As a result, Cilium not only makes it simple to apply security policies in a highly dynamic environment0 码力 | 734 页 | 11.45 MB | 1 年前3
Cilium v1.9 Documentationcommunicating with each other? How frequently? What does the service dependency graph look like? What HTTP calls are being made? What Kafka topics does a service consume from or produce to? Network monitoring Is it an application or network problem? Is the communication broken on layer 4 (TCP) or layer 7 (HTTP)? Which services have experienced a DNS resolution problem in the last 5 minutes? Which services monitoring What is the rate of 5xx or 4xx HTTP response codes for a particular service or across all clusters? What is the 95th and 99th percentile latency between HTTP requests and responses in my cluster0 码力 | 1263 页 | 18.62 MB | 1 年前3
Cilium v1.7 Documentationapplication is split into small independent services that communicate with each other via APIs using lightweight protocols like HTTP. Microservices applications tend to be highly dynamic, with individual containers that need to be updated with a continuously growing frequency. Protocol ports (e.g. TCP port 80 for HTTP traffic) can no longer be used to differentiate between application traffic for security purposes contrast to IP address identification in traditional systems) and can filter on application-layer (e.g. HTTP). As a result, Cilium not only makes it simple to apply security policies in a highly dynamic environment0 码力 | 885 页 | 12.41 MB | 1 年前3
openEuler 21.03 技术白皮书OpenStack provides IaaS solutions with its mutually supplementary services, which are integrated through APIs. OpenStack Victoria is a stable release in the OpenStack community in 2020, including multiple modules information. • Nova provides VM creation, running, migration, and snapshot services, and provides APIs for interconnecting with controller nodes. The controller nodes deliver tasks and use nova-api for openEuler 21.03 Technical White Paper • Horizon provides a GUI-based operation console. It calls APIs to display and manage internal OpenStack resources. Application Scenarios Application scenario0 码力 | 21 页 | 948.66 KB | 1 年前3
Moxa Industrial Linux 3.0 (Debian 11)
Manual for Arm-based Computers
Version 1.0, January 2023the following steps to connect to the Arm-based computer from your Windows PC. 1. Download PuTTY http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html to set up a serial connection with the Arm-based computer itself. Take the following steps from your Windows PC. Click on the link http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html to download PuTTY (free software) to set changed Using API to Retrieve the MCM Status MCM provides C application programming interfaces (APIs) for developer to retrieve various network and interface status from MCM Please refers to following0 码力 | 111 页 | 2.94 MB | 1 年前3
共 79 条
- 1
- 2
- 3
- 4
- 5
- 6
- 8













