DOCSLIB.ORG

Debian on Civil Infrastructure Systems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Debian on Civil Infrastructure Systems Yoshitake Kobayashi, CIP TSC chair DebConf17, 12 August 2017 What is CIP? • One of the most conservative open source project in the Linux Foundation • One of the most important project for our civilization DebConf17, Montrial, CANADA 4 Our Civilization is run by Linux DebConf17, Montrial, CANADA 5 https://www.airpano.com/360Degree-VirtualTour.php?3D=San-Francisco-USA Our Civilization is run by Debian DebConf17, Montrial, CANADA 6 https://www.airpano.com/360Degree-VirtualTour.php?3D=San-Francisco-USA Transport Energy Industry Others Industry automation Healthcare Rail automation Power Generation Vehicle control CNC control Building automation Automatic ticket gates Turbine Control Industrial communication Broadcasting DebConf17, Montrial, CANADA 7 https://www.airpano.com/360Degree-VirtualTour.php?3D=San-Francisco-USA CIP members are interested in Debian DebConf17, Montrial, CANADA 8 Why Debian is one of the most important distribution? • Large community-driven ecosystem • To ensure “free software only” in “main” • License checks / discussions ([email protected]) • CPU architecture support (x86, ARM, PPC64, …) • Popular in embedded (Raspbian, Armbian, …) • Long-term support (Debian-LTS) • Scales up and down • Successfully used in several of our products DebConf17, Montrial, CANADA 9 There are issues to be solved… https://www.airpano.com/360Degree-VirtualTour.php?3D=SanDebConf17,-Francisco- USAMontrial, CANADA 10 A Railway System: 25-50 years products life-cycle with very reluctant nature for product update and upgrade of hardware and base software platform Image: http://www.deutschebahn.com/contentblob/10862328/20160301+Stw+M%C3%BClheim+Innenansicht+1+(1)/data.jpg DebConf17, Montrial, CANADA 11 Railway Example 3 – 5 years development time 2 – 4 years customer specific extensions 1 year initial safety certifications / authorization 3 – 6 months safety certifications / authorization for follow-up releases (depending on amount of changes) 25 – 50 years lifetime Image: http://www.deutschebahn.com/contentblob/10862328/20160301+Stw+M%C3%BClheim+Innenansicht+1+(1)/data.jpg DebConf17, Montrial, CANADA 12 The Problems we face … • The systems that support our modern civilization need to survive for a VERY LONG TIME. Until now the corresponding industrial grade super long term maintenance has been done individually by each company. • These systems not only have to survive for a long time, they must be “INDUSTRIAL GRADE” (robust, secure and reliable). And at the same time the industry will also need to catch up with the latest technology trends DebConf17, Montrial, CANADA 14 The Solutions we need … LONG TERM INDUSTRIAL Collaborative MAINTENACE GRADE Development • We need a Collaborative framework to maintain the same open source based system for many, many, many years to keep it secure, robust and reliable. • AND most importantly, we need to do this collaboratively in the upstream communities, not locally. DebConf17, Montrial, CANADA 15 CIP is our solution… Establishing an Open Source Base Layer of industrial-grade software to enable the use and implementation of software building blocks for Civil Infrastructure Systems https://www.cip-project.org/ DebConf17, Montrial, CANADA 16 What is CIP? • One of the most conservative open source project in the Linux Foundation • CIP aims to • Provide an open source base layer for CIP related embedded systems • Work closely with the upstream community • CIP does not aim to • Create a new Linux distribution DebConf17, Montrial, CANADA 17 What is “Open Source Base Layer (OSBL)”? • OSBL is a set of industrial grade core open source software components, Non-CIP packages tools and methods Linux distribution (e.g. Debian) may extend/include CIP packages. User User space • Open source based CIP Reference Filesystem image with SDK Open reference (CIP Core packages) implementation Source • Start from a minimal set Base Layer for controllers in CIP SLTS Kernel industrial grade systems Kernel CIP Reference Hardware Hardware DebConf17, Montrial, CANADA 18 An example of minimal package set for CIP base layer CIP will start with a minimal set of packages. “CIP kernel” and “CIP core” packages run on hardware. Candidates for initial component set Keep these packages for Reproducible build • Kernel • Flex • Git • pax-utils CIP • Kernel Linux kernel + backported patches • Bison • Glib • Pciutils • PREEMPT_RT patch • autoconf • Gmp • Perl • Bootloader • automake • Gzip • pkg-config • U-boot • bc • gettext • Popt • Shells / Utilities • bison • Kbd • Procps • Busybox Dev • Bzip2 • Libibverbs • Quilt • Base libraries packages • Curl • Libtool • Readline CIP Core • Glibc Packages • Db • Libxml2 • sysfsutils • Tool Chain • Dbus • Mpclib • Tar • Binutils • GCC • Expat • Mpfr4 • Unifdef • Security • Flex • Ncurses • Zlib • OpenSSL • gawk • Make • Gdb • M4 NOTE: The maintenance effort varies considerably for different packages. DebConf17, Montrial, CANADA 19 Development plan CIP will increase the development effort to create a industrial grade common base-layer add. pkgs add. pkgs Core Core Core Packages Packages Packages Kernel Kernel Kernel (SLTS) (SLTS) (SLTS) Phase 1: Phase 2: Phase 3: • Define supported kernel • Patch collection, stabilization, back • Domain specific enhancements, subsystems, arch. port of patches for CIP kernel e.g. communication protocols, • Initial SLTS component selection packages industrial IoT middleware • Select SLTS versions • Support more subsystems • Optionally: more subystems • Set-up maintenance • Additional core packages • Optionally: more core packages infrastructure (build, test) DebConf17, Montrial, CANADA 20 Using Debian on Civil Infrastructure Systems DebConf17, Montrial, CANADA 21 How we use Debian for embedded systems • Customization • Tests • Kernel • Documentation • Change kernel options • Open source software licenses • Change Linux kernel version compliance • Modify the kernel source code • Export control classification • Packages • Change compile option • Change package dependencies DebConf17, Montrial, CANADA 22 Creating Debian-based images for embedded systems • There are several way to create Debian-based images for embedded systems Native/Cross-build Debian Install Debian (Pre-rebuild + Cross-build Source code packages) Install Debian Install Native/Cross-build Source Code (Pre(Prebuild-build + Cross-build (CIP kernel, etc.) packages) + Install Target Systems DebConf17, Montrial, CANADA 23 Why Debian is one of the most important distribution? • Large community-driven ecosystem • To ensure “free software only” in “main” • License checks / discussions ([email protected]) • CPU architecture support (x86, ARM, PPC64, …) • Popular in embedded (Raspbian, Armbian, …) • Long-term support (Debian-LTS) • Scales up and down • Successfully used in several of our products • CIP does not want to re-invent the wheel DebConf17, Montrial, CANADA 24 CIP current scope and status DebConf17, Montrial, CANADA 26 Scope of activities App container App Framework infrastructure (mid-term) (optionally, mid-term) Tools Concepts Build environment Functional safety Shared config. (e.g. yocto recipes) architecture/strategy, Domain Specific communication Multimedia (e.g. OPC UA) & logging including compliance Test automation w/ standards (e.g., NERC CIP, IEC61508) Middleware/Libraries Tracing & reporting Long-term support User User space tools Strategy: security patch Configuration management Safe & Secure management Monitoring Security Update Standardization Device management collaborative effort with (update, download) others Real-time / Real-time support Application life- safe virtualization cycle management License clearing Export Control Kernel space Kernel Linux Kernel Classification On device software stack Product development and maintenance DebConf17, Montrial, CANADA 27 Technical topics and related projects (Feb. 2017 version) * Topics will be added or removed to reflect CIP technical interests Application support Infrastructure and Services App Framework HMI Framework FW update App deployment Middleware / Tools Coherent Security Mechanisms Build and production Yocto Project Debian build system Domain specific and IoT communication Configuration/Device management Multimedia Common issues OPC UA TSN Echonet OM2M Configuration Industrial Zeroconf Y2038 Testing Industrial special-purpose protocols Avnu LTP kselftest KernelCI Fuego CIP test suite Linux Kernel RTOS `I Support Security Functional Safety Userland Isolation Kernel Isolation SLTS Backwards compatibility Anomaly detection Live patching Monitoring/error detection SafeG LXC Cgroups LSM SELinux SIL2LinuxMP SIL3 support w Jailhouse Development process Communication SIL2 support SIL3 support Real-time support Monitoring / Tracing GPGPU/FPGA real-time RT/non-RT communication Ftrace ktap Heterogeneous Legal topics SPDX FOSSology Computing Xenomai PREEMPT-RT RAS License Clearing Export Control SoC FPGA Hardware / SoC (x86 or ARM based) Legend To be specified / implemented by CIP Integration / cooperation DebConf17, Montrial, CANADA 28 Scope of activities App container App Framework infrastructure (mid-term) (optionally, mid-term) Tools Concepts Build environment Functional safety Shared config. (e.g. yocto recipes) architecture/strategy, Domain Specific communication Multimedia (e.g. OPC UA) & logging including compliance Test automation w/ standards (e.g., NERC CIP, IEC61508) Middleware/Libraries Tracing & reporting Long-term support User User space tools Strategy: security patch
Recommended publications
  • Increasing Automation in the Backporting of Linux Drivers Using Coccinelle

    Increasing Automation in the Backporting of Linux Drivers Using Coccinelle

    Increasing Automation in the Backporting of Linux Drivers Using Coccinelle Luis R. Rodriguez Julia Lawall Rutgers University/SUSE Labs Sorbonne Universites/Inria/UPMC/LIP6´ [email protected] [email protected] [email protected], [email protected] Abstract—Software is continually evolving, to fix bugs and to a kernel upgrade. Upgrading a kernel may also require add new features. Industry users, however, often value stability, experience to understand what features to enable, disable, or and thus may not be able to update their code base to the tune to meet existing deployment criteria. In the worst case, latest versions. This raises the need to selectively backport new some systems may rely on components that have not yet been features to older software versions. Traditionally, backporting has merged into the mainline Linux kernel, potentially making it been done by cluttering the backported code with preprocessor impossible to upgrade the kernel without cooperation from the directives, to replace behaviors that are unsupported in an earlier version by appropriate workarounds. This approach however component vendor or a slew of partners that need to collaborate involves writing a lot of error-prone backporting code, and results on developing a new productized image for a system. As an in implementations that are hard to read and maintain. We example, development for 802.11n AR9003 chipset support consider this issue in the context of the Linux kernel, for which on the mainline ath9k device driver started on March 20, older versions are in wide use. We present a new backporting 2010 with an early version of the silicon, at which point the strategy that relies on the use of a backporting compatability most recent major release of the Linux kernel was v2.6.32.
  • Contributor's Guidelines

    Contributor's Guidelines

    Contributor’s Guidelines Release 17.11.10 Feb 27, 2020 CONTENTS 1 DPDK Coding Style1 1.1 Description.......................................1 1.2 General Guidelines..................................1 1.3 C Comment Style...................................1 1.4 C Preprocessor Directives..............................2 1.5 C Types.........................................4 1.6 C Indentation......................................7 1.7 C Function Definition, Declaration and Use.....................9 1.8 C Statement Style and Conventions......................... 11 1.9 Python Code...................................... 13 2 Design 14 2.1 Environment or Architecture-specific Sources.................... 14 2.2 Library Statistics.................................... 15 2.3 PF and VF Considerations.............................. 16 3 Managing ABI updates 18 3.1 Description....................................... 18 3.2 General Guidelines.................................. 18 3.3 What is an ABI..................................... 18 3.4 The DPDK ABI policy................................. 19 3.5 Examples of Deprecation Notices.......................... 20 3.6 Versioning Macros................................... 20 3.7 Setting a Major ABI version.............................. 21 3.8 Examples of ABI Macro use............................. 21 3.9 Running the ABI Validator............................... 25 4 DPDK Documentation Guidelines 27 4.1 Structure of the Documentation........................... 27 4.2 Role of the Documentation.............................
  • Introducting Innovations in Open Source Projects

    Introducting Innovations in Open Source Projects

    Introducing Innovations into Open Source Projects Dissertation zur Erlangung des Grades eines Doktors der Naturwissenschaften (Dr. rer. nat.) am Fachbereich Mathematik und Informatik der Freien Universität Berlin von Sinan Christopher Özbek Berlin August 2010 2 Gutachter: Professor Dr. Lutz Prechelt, Freie Universität Berlin Professor Kevin Crowston, Syracuse University Datum der Disputation: 17.12.2010 4 Abstract This thesis presents a qualitative study using Grounded Theory Methodology on the question of how to change development processes in Open Source projects. The mailing list communication of thirteen medium-sized Open Source projects over the year 2007 was analyzed to answer this question. It resulted in eight main concepts revolving around the introduction of innovation, i.e. new processes, services, and tools, into the projects including topics such as the migration to new systems, the question on where to host services, how radical Open Source projects can change their ways, and how compliance to processes and conventions is enforced. These are complemented with (1) the result of five case studies in which innovation introductions were conducted with Open Source projects, and with (2) a theoretical comparison of the results of this thesis to four theories and scientific perspectives from the organizational and social sciences such as Path Dependence, the Garbage Can model, Social-Network analysis, and Actor-Network theory. The results show that innovation introduction is a multifaceted phenomenon, of which this thesis discusses the most salient conceptual aspects. The thesis concludes with practical advice for innovators and specialized hints for the most popular innovations. 5 6 Acknowledgements I want to thank the following individuals for contributing to the completion of this thesis: • Lutz Prechelt for advising me over these long five years.
  • Debian Packaging Tutorial

    Debian Packaging Tutorial

    Debian Packaging Tutorial Lucas Nussbaum [email protected] version 0.27 – 2021-01-08 Debian Packaging Tutorial 1 / 89 About this tutorial I Goal: tell you what you really need to know about Debian packaging I Modify existing packages I Create your own packages I Interact with the Debian community I Become a Debian power-user I Covers the most important points, but is not complete I You will need to read more documentation I Most of the content also applies to Debian derivative distributions I That includes Ubuntu Debian Packaging Tutorial 2 / 89 Outline 1 Introduction 2 Creating source packages 3 Building and testing packages 4 Practical session 1: modifying the grep package 5 Advanced packaging topics 6 Maintaining packages in Debian 7 Conclusions 8 Additional practical sessions 9 Answers to practical sessions Debian Packaging Tutorial 3 / 89 Outline 1 Introduction 2 Creating source packages 3 Building and testing packages 4 Practical session 1: modifying the grep package 5 Advanced packaging topics 6 Maintaining packages in Debian 7 Conclusions 8 Additional practical sessions 9 Answers to practical sessions Debian Packaging Tutorial 4 / 89 Debian I GNU/Linux distribution I 1st major distro developed “openly in the spirit of GNU” I Non-commercial, built collaboratively by over 1,000 volunteers I 3 main features: I Quality – culture of technical excellence We release when it’s ready I Freedom – devs and users bound by the Social Contract Promoting the culture of Free Software since 1993 I Independence – no (single)
  • Impacting the Bioscience Progress by Backporting Software for Bio-Linux

    Impacting the Bioscience Progress by Backporting Software for Bio-Linux

    Impacting the bioscience progress by backporting software for Bio-Linux Sasa Paporovic [email protected] v0.9 What is Bio-Linux and what is it good for - also its drawbacks: If someone says to use or to have a Linux this is correct as like it is imprecise. It does not exist a Linux as full functional operating system by itself. What was originally meant by the term Linux was the operating system core[1]. The so called kernel, or in a case of a Linux operating system the Linux kernel. It is originally designed and programmed by Linus Torvalds, who is also today the developer in chef or to say it with his words, he is the “alpha-male” of all developers[2]. Anyway, what we have today are Distributions[3]. It has become common to call them simply “a Linux”. This means that there are organizations out there, mostly private, some funded and some other commercial, which gather all what is needed to design around the Linux kernel a full functional operating system. This targets mostly Software, but also web and service infrastructure. Some of them have a history that is nearly as long as the Linux kernel is alive, like Debian. Some others are younger like Ubuntu and some more others are very young, like Bio-Linux[4]. The last Linux, the Bio-Linux, especially its latest version Bio-Linux 7 we are focusing here[5]. In year 2006 Bio-Linux with the work of Tim Booth[42] and team gives its rising[6] and provide an operating system that was and still specialized in providing a bioinformatic specific software environment for the working needs in this corner of bioscience.
  • Oracle Unbreakable Linux: an Overview

    Oracle Unbreakable Linux: an Overview

    Oracle Unbreakable Linux: An Overview An Oracle White Paper September 2010 Oracle Unbreakable Linux: An Overview INTRODUCTION Oracle Unbreakable Linux is a support program that provides enterprises with industry-leading global support for the Linux operating system at significantly lower costs. The support program, which is available for any customer whether or not they’re running Oracle Unbreakable Linux currently includes support for three architectures: x86; x86-64 (e.g. the latest Intel Xeon and AMD Opteron chips, as used by most Linux customers); and Linux Itanium (ia64). The program offers support for any existing Red Hat Enterprise Linux installations and for new installations of Oracle Linux, an open source Linux operating system that is fully compatible— both source and binary—with Red Hat Enterprise Linux. Complete Support for the Complete Software Stack Oracle’s industry-leading support organization offers expertise that looks at the entire application stack running on top of Linux; only Oracle delivers complete support for the complete software stack—database, middleware, applications, management tools, and the operating system itself. By delivering enterprise-class quality support for Linux, Oracle addresses a key enterprise requirement from customers. When problems occur in a large, complex enterprise environment, it’s often impossible to reproduce such occurrences with very simple test cases. Customers need a support vendor who understands their full environment, and has the expertise to diagnose and resolve the problem by drawing from their knowledge of and familiarity with their framework, as opposed to requesting a simple reproducible test case. Another customer demand is for bug fixes to happen in a timely manner, as customers cannot always afford to wait for months to get a fix delivered to them.
  • A Guide to Kernel Exploitation Attacking the Core (2011

    A Guide to Kernel Exploitation Attacking the Core (2011

    A Guide to Kernel Exploitation This page intentionally left blank A Guide to Kernel Exploitation Attacking the Core Enrico Perla Massimiliano Oldani Technical Editor Graham Speake AMSTERDAM • BOSTON • HEIDELBERG • LONDON • • • NEW YORK OXFORD PARIS SAN DIEGO SYNGRESS SAN FRANCISCO • SINGAPORE • SYDNEY • TOKYO ® Syngress is an imprint of Elsevier Acquiring Editor: Rachel Roumeliotis Development Editor: Matthew Cater Project Manager: Julie Ochs Designer: Alisa Andreola Syngress is an imprint of Elsevier 30 Corporate Drive, Suite 400, Burlington, MA 01803, USA © 2011 Elsevier Inc. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or any information storage and retrieval system, without permission in writing from the publisher. Details on how to seek permission, further information about the Publisher’s permissions policies and our arrangements with organizations such as the Copyright Clearance Center and the Copyright Licensing Agency, can be found at our website: www.elsevier.com/permissions. This book and the individual contributions contained in it are protected under copyright by the Publisher (other than as may be noted herein). Notices Knowledge and best practice in this field are constantly changing. As new research and experience broaden our understanding, changes in research methods or professional practices, may become necessary. Practitioners and researchers must always rely on their own experience and knowledge in evaluating and using any information or methods described herein. In using such information or methods they should be mindful of their own safety and the safety of others, including parties for whom they have a professional responsibility.
  • BIND 9 Administrator Reference Manual

    BIND 9 Administrator Reference Manual

    BIND 9 Administrator Reference Manual BIND 9.11.31 (Extended Support Version) Copyright (C) 2000-2021 Internet Systems Consortium, Inc. ("ISC") This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain one at http://mozilla.org/MPL/2.0/. Internet Systems Consortium, Inc. PO Box 360 Newmarket, NH 03857 USA https://www.isc.org/ Contents 1 Introduction 1 1.1 Scope of Document . .1 1.2 Organization of This Document . .1 1.3 Conventions Used in This Document . .1 1.4 The Domain Name System (DNS) . .2 DNS Fundamentals . .2 Domains and Domain Names . .2 Zones . .3 Authoritative Name Servers . .3 The Primary Server . .3 Secondary Servers . .4 Stealth Servers . .4 Caching Name Servers . .4 Forwarding . .5 Name Servers in Multiple Roles . .5 2 BIND Resource Requirements7 2.1 Hardware requirements . .7 2.2 CPU Requirements . .7 2.3 Memory Requirements . .7 2.4 Name Server-Intensive Environment Issues . .7 2.5 Supported Operating Systems . .8 iii BIND 9.11.31 CONTENTS CONTENTS 3 Name Server Configuration9 3.1 Sample Configurations . .9 A Caching-only Name Server . .9 An Authoritative-only Name Server . .9 3.2 Load Balancing . 10 3.3 Name Server Operations . 11 Tools for Use With the Name Server Daemon . 11 Diagnostic Tools . 11 Administrative Tools . 12 Signals . 13 4 Advanced DNS Features 15 4.1 Notify . 15 4.2 Dynamic Update . 15 The Journal File . 16 4.3 Incremental Zone Transfers (IXFR) . 16 4.4 Split DNS .
  • Unix to Linux Migration

    Unix to Linux Migration

    UNIX TO LINUX MIGRATION RICHARD KEECH ABSTRACT This paper aims to show the benefits of choosing Linux and migrating existing UNIX environments to the Linux platform. This applies in particular to migrations from RISC-based platforms. It also shows the extent to which Linux is now a trusted, mainstream platform and how any technical risks associated with migrations can be mitigated. This paper addresses a technical audience. www.redhat.com UNIX to Linux migration | Richard Keech TABLE OF CONTENTS AIMS Page 3 INTRODUCTION TO LINUX Page 3 OpEN SOURCE AND LINUX Page 4 RED HAT ENTErprISE LINUX Page 5 UNIX VS LINUX Page 8 TrENDS Page 9 Server Virtualization Page 9 Clustering Page 10 Rapid provisioning and appliance OS Page 10 Instrumentation and debugging Page 10 MIGRATION CONSIDERATIONS Page 11 Qualify the stack Page 11 Porting Page 12 Training Page 12 Prepare a Linux standard build Page 12 Pilot deployment Page 13 CONCLUSIONS Page 13 REFERENCES Page 14 2 www.redhat.com UNIX to Linux migration | Richard Keech AIMS This paper aims to give an introduction to Linux for the technically inclined and educated reader at a level that can allow proper comparisons with UNIX. The paper provides an outline of the key considerations in selecting Linux and migrating from UNIX to Red Hat Enterprise Linux. The intended audience of this paper is enterprise infrastructure architects. INTRODUCTION TO LINUX Benefits. The Linux platform offers a low-risk, robust, and value-for-money alternative to traditional UNIX. Linux is now sufficiently mature enough to handle the most demanding workloads at a much lower cost than proprietary UNIX offerings.
  • Ubuntu-Packaging-Guide.Pdf

    Ubuntu-Packaging-Guide.Pdf

    Ubuntu Packaging Guide Release 1.0.3 bzr711 ubuntu14.04.1 Ubuntu Developers August 31, 2021 CONTENTS 1 Articles 2 1.1 Introduction to Ubuntu Development..................................2 1.2 Getting Set Up..............................................4 1.3 Fixing a bug in Ubuntu..........................................8 1.4 Packaging New Software......................................... 14 1.5 Security and Stable Release Updates.................................. 17 1.6 Patches to Packages........................................... 19 1.7 Fixing FTBFS packages......................................... 22 1.8 Shared Libraries............................................. 23 1.9 Backporting software updates...................................... 25 2 Knowledge Base 26 2.1 Communication in Ubuntu Development................................ 26 2.2 Basic Overview of the debian/ Directory............................... 26 2.3 ubuntu-dev-tools: Tools for Ubuntu developers............................. 32 2.4 autopkgtest: Automatic testing for packages.............................. 34 2.5 Using Chroots.............................................. 36 2.6 Setting up sbuild............................................. 37 2.7 KDE Packaging............................................. 40 3 Further Reading 42 i CONTENTS Ubuntu Packaging Guide Welcome to the Ubuntu Packaging and Development Guide! This is the official place for learning all about Ubuntu Development and packaging. After reading this guide you will have: • Heard about the most important players,
  • NXP Powerpoint Template Confidential 16:9 Widescreen

    NXP Powerpoint Template Confidential 16:9 Widescreen

    ONL/ONIE ON QorIQ AND QorIQ LS SERIES FTF-DES-N1842 DR. XIN-XIN YANG SOFTWARE ENGINEERING MANAGER FTF-DES-N1842 MAY 17, 2016 PUBLIC USE AGENDA • What is ONL/ONIE • Why ONL/ONIE in NXP • Backport – Kernel Rebase • ONL/ONIE Development and Upstreaming • Plan & Roadmap • Summary 1 PUBLIC USE #NXPFTF 1 PUBLIC USE #NXPFTF WHAT IS ONL/ONIE 2 PUBLIC USE #NXPFTF ONL is a Linux Distribution for Bare Metal Switches • A collection of software packages, utilities, drivers, and abstractions to run on OCP, bare metal, “brite box” hardware - i.e., a “NOS” that ONIE would install - Network forwarding devices built from commodity components • ONL uses ONIE to install onto on-board flash memory • Open Network Linux is a part of the Open Compute Project and is a component in a growing collection of open source and commercial projects http://opennetlinux.org/ 3 PUBLIC USE #NXPFTF Why Not Use an Existing Linux Distribution • Does build on existing distribution – Debian Wheezy • Need to create ONIE installers for many platforms • Need to manage switch-specific hardware (e.g.,SFPs) • Switches are very similar to servers, but not quite 4 PUBLIC USE #NXPFTF Why Use ONL? • Help ecosystem focus on innovation - Many annoying software details to run an OCP switch - Building platform drivers not high value asset; should be common • Enables a reference NOS implementation - Hardware without software is useless - Package up details and best practices into one place • Help bootstrap the Open ecosystem and OCP adoption - Allows commercial companies and DYI-folks to build
  • Architettura Cloud Per Lo Sviluppo Multi-Piattaforma Di Sistemi Operativi: Principi Generali

    Architettura Cloud Per Lo Sviluppo Multi-Piattaforma Di Sistemi Operativi: Principi Generali

    Alma Mater Studiorum · Universita` di Bologna SCUOLA DI SCIENZE Corso di Laurea Magistrale in Informatica Architettura cloud per lo sviluppo multi-piattaforma di Sistemi Operativi: Principi generali Relatore: Presentata da: Chiar.mo Prof. Ettore Di Giacinto Alessandro Amoroso I Sessione 2015-2016 Introduzione Negli ultimi anni si `evisto emergere la cultura DevOps nell'industria IT. Analizzeremo l'applicazione di questa metodologia nei cicli di rilascio e di compilazione dei pacchetti di una Distribuzione Linux. Vengono studiate le strategie e i metodi adottati delle principali distribuzioni. Si propone quindi un nuovo approccio sfruttando le tecnologie del campo DevOps introducendo un alto grado di scalabilit`a,flessibilit`ae riproducibilit`aanche in ambienti Cloud. I vantaggi di questo metodo sono fasi di building, testing e rilascio in maniera rapida, efficiente e affidabile. Vedremo quindi come questo ap- proccio aumenta l'automatizzazione nei cicli produttivi per la realizzazione della Distribuzione Sabayon Linux e per la definizione di un'infrastruttura automatizzata attualmente in production. i Indice 1 Introduzione 1 1.1 Contesto . .2 1.1.1 Sistemi operativi Linux . .2 1.2 Cloud computing . .6 1.3 Ciclo di sviluppo di un sistema operativo . .7 1.3.1 Gestione del parco Software . .7 1.3.2 Il sistema di rilascio . .9 1.3.3 Il Kernel . .9 1.4 Scopo del Lavoro . 10 1.4.1 Struttura della tesi . 11 2 Analisi dei sistemi esistenti 13 2.1 Distribuzioni Linux . 13 2.1.1 Fedora Linux . 14 2.1.2 Debian Linux . 14 2.1.3 Gentoo Linux . 15 2.2 Gestione del Parco Software .