. . . . . . . . . . . . . . . . . . . . . . . . . 05 Push vs . Pull-Based Architecture . . . . . . . . . . . . . . . . . . . . . . include continuous integration / continuous delivery (CI/CD), choosing between pull- or push-based architecture, and observability. Getting Started with GitOps Looking for an In-Depth Introduction to GitOps are property of their respective companies. Push vs. Pull-Based Architecture Push vs . Pull-Based Architecture Adopting a cloud-native architecture is not without its challenges. While the benefits are

Introduction Background Operations & observability Outro Working assumptions & concepts Prometheus is a pull-based system Black-box monitoring: Looking at a service from the outside (Does the server answer to

Supply Chain 005 Community-certified openEuler Distributions 006 openEuler Open Source OS Architecture 007 3 Scenario-specific Innovations 008 Server 009 DPUDirect 009 eNFS 011 HPCRunner OpenHarmony, achieving ecosystem interoperability through shared capabilities. With a unified OS architecture supporting all mainstream computing architectures, openEuler is one of the best open source Lego-style architecture, making it ideal for servers, cloud computing, edge computing, and embedded systems. This white paper aims to provide a comprehensive overview of openEuler's architecture and its

development of the architecture precede sprint development. Alternatively, a program can initially use a traditional approach to build the initial increment that meets the baseline architecture requirements deliverables (e.g., code)?  Is there a clear owner of the program (or broader enterprise) architecture?  Is there a clear, early commitment from user representatives and the broader user base? enterprise architectures, frameworks, standards, or interfaces?  Can the development team access architecture documents and systems?  Are owners/representatives from these enterprise areas involved in

1 Homepage: Rules-Requires-Root: no Package: debhello Architecture: any Multi-Arch: foreign Depends: ${misc:Depends}, ${shlibs:Depends} Description: auto-generated 模板文件中的“Section: unknown”部分不做修改的话， 后续的 lintian 错误可能导致构建失败。 因为这是个 ELF 二进制可执行文件软件包，debmake 命令设置了“Architecture: any”和“Multi-Arch: foreign”两项。同时，它将所需的 substvar 参数设置为“Depends: ${shlibs:Depends}, ${misc:Depends}”。 Homepage: https://salsa.debian.org/debian/debmake-doc Rules-Requires-Root: no Package: debhello Architecture: any Multi-Arch: foreign Depends: ${misc:Depends}, ${shlibs:Depends} Description: Simple packaging

Paper 1 openEuler 21.03 Technical White Paper CONTENTS 01 / Introduction 02 / Platform Architecture 03 / Operating Environment 04 / Kernel Innovations 05 / Cloud Base 06 / Flourishing Ecosystem In the openEuler community, global developers join hands to build an open, diversified, and architecture-inclusive software innovation ecosystem. openEuler is an innovative platform driven by community diversified computing architectures. openEuler supports the x86 architecture represented by Intel and Zhaoxin and the ARM architecture represented by Kunpeng and Phytium. In addition, an RISC-V trial

ni.com whoami Introduction NI Linux Real-TIme contributions OPKG ni.com Agenda History Architecture Solvers Future Work Questions ni.com History ni.com Ipkg (2001) • Itsy Bitsy Package December) • Mature • Robust solver backend • Basic package manager features done History ni.com Architecture ni.com Development Philosopy IPKG tries to be like Debian, as much as possible. In fact, the Original IPKG FAQ Architecture ni.com Why yet another Package Manager? MACHINE = quemux86_64 EXTRA_IMAGE_FEATURES ?= “package-management” IMAGE = core-image-minimal Architecture package_ipk package_deb

openEuler 21.09 Technical White Paper 3 Scenario-Specific Innovations 19 Introduction 02 Platform Architecture 05 Operating Environments 08 Kernel Innovations 10 Cloud Base 14 Enhanced Features 22 Community openEuler 21.09 Technical White Paper 01 Scenario-Specific Innovations 19 Introduction 02 Platform Architecture 05 Operating Environments 08 Kernel Innovations 10 Cloud Base 14 Enhanced Features 22 Community a portal available to global developers, with the goal of building an open, diversified, and architecture-inclusive software ecosystem for all digital infrastructure scenarios. It has a rich history of

Debian 打包教程 12 / 90 源码包范例（wget_1.12-2.1.dsc） Format: 3.0 (quilt) Source: wget Binary: wget Architecture: any Version: 1.12-2.1 Maintainer: Noel Kothe Homepage: http://www.gnu.org/software/wget/ info2man Standards-Version: 3.8.4 Homepage: http://www.gnu.org/software/wget/ Package: wget Architecture: any Depends: ${shlibs:Depends}, ${misc:Depends} Description: retrieves files from the web Wget Debian 打包教程 18 / 90 架构 (Architecture)：全部 (all) 或任意 (any) 有两种程序文件包： ▶ 每种 Debian 架构上有不同内容的软件包 ▶ 例如：C 语言编程 ▶ debian/control 文件内 Architecture: any ▶ 或者，仅在某几种架构下可用： Architecture: amd64 i386 ia64 hurd-i386

(可參考dpkg-source(1) 有更詳盡的解說) Debian 套件打包教學指南 12 / 90 原始碼套件範例 Format: 3.0 (quilt) Source: wget Binary: wget Architecture: any Version: 1.12 -2.1 Maintainer: Noel Kothe Homepage: http :// www.gnu.org/software/wget/ info2man Standards -Version: 3.8.4 Homepage: http :// www.gnu.org/software/wget/ Package: wget Architecture : any Depends: ${shlibs:Depends}, ${misc:Depends} Description : retrieves files from the web Wget Debian 套件打包教學指南 18 / 90 Architecture: all or any 有兩種二進制套件: ▶ 套件內容會隨著不同的 Debian 平台架構而有所差異 ▶ 範例: C 程式 ▶ debian/control 中描述 Architecture: any ▶ 或者只運行在某些特定的平台架構中: Architecture: amd64 i386 ia64 hurd-i386