DOCSLIB.ORG

SUSE Linux Enterprise Server 15 SP2 Deployment Guide Deployment Guide SUSE Linux Enterprise Server 15 SP2

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

SUSE Linux Enterprise Server 15 SP2 Deployment Guide Deployment Guide SUSE Linux Enterprise Server 15 SP2 This guide details how to install single or multiple systems, and how to exploit the product-inherent capabilities for a deployment infrastructure. Choose from various approaches: local installation from physical installation media, customizing the standard installation images, network installation server, mass deployment using a remote-controlled, highly-customized, automated installation process, and initial system conguration. Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see https://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About This Guide xiii 1 Available Documentation xiv 2 Giving Feedback xv 3 Documentation Conventions xvi 4 Product Life Cycle and Support xviii Support Statement for SUSE Linux Enterprise Server xviii • Technology Previews xix I INSTALLATION PREPARATION 1 1 Planning for SUSE Linux Enterprise Server 2 1.1 Considerations for Deployment of a SUSE Linux Enterprise Server 2 1.2 Deployment of SUSE Linux Enterprise Server 3 1.3 Running SUSE Linux Enterprise Server 3 1.4 Registering SUSE Linux Enterprise Server 4 1.5 Changes in Installation from SUSE Linux Enterprise Server Version 15 4 Unified Installer for SUSE Linux Enterprise-based Products 4 • Installing with Internet Access 5 • Offline Installation 5 • Quarterly Update Media 6 2 Installation on AMD64 and Intel 64 7 2.1 Hardware Requirements 7 2.2 Installation Considerations 8 Installation on Hardware or Virtual Machine 9 • Installation Target 9 2.3 Controlling the Installation 9 iii Deployment Guide 2.4 Booting the Installation System 10 2.5 Dealing with Boot and Installation Problems 11 Problems Booting 12 • Problems Installing 13 • Redirecting the Boot Source to the Installation Medium 13 3 Installation on Arm AArch64 14 3.1 Hardware Requirements 14 3.2 Installation Considerations 16 Installation on Hardware or Virtual Machine 16 • Installation Target 16 3.3 Controlling the Installation 16 3.4 Booting the Installation System 17 3.5 Dealing with Boot and Installation Problems 19 Problems Booting 19 • Problems Installing 20 • Redirecting the Boot Source to the Boot DVD 20 3.6 Raspberry Pi 20 Boot Process 21 • Lack of a Real-Time Clock 23 • Deploying an Appliance Image 24 • Installation from USB Media 24 • Installation from Network 25 • For More Information 25 4 Installation on IBM POWER 27 4.1 Hardware Requirements 27 4.2 Installing SUSE Linux Enterprise Server for POWER 28 4.3 Installing SUSE Linux Enterprise Server 31 4.4 Further Information 35 5 Installation on IBM Z and LinuxONE 36 5.1 System Requirements 36 Hardware 36 • MicroCode Level, APARs, and Fixes 38 • Software 39 5.2 General Information 40 System Requirements 40 • Installation Types 44 • IPL Options 45 iv Deployment Guide 5.3 Preparing for Installation 46 Making the Installation Data Available 46 • Installation Types 53 • Preparing the IPL of the SUSE Linux Enterprise Server Installation System 54 • IPLing the SUSE Linux Enterprise Server Installation System 58 • Network Configuration 63 • Connecting to the SUSE Linux Enterprise Server Installation System 66 • The SUSE Linux Enterprise Server Boot Procedure on IBM Z 69 5.4 Secure boot 69 5.5 I/O device auto-configuration on IBM Z systems 70 5.6 The Parmfile—Automating the System Configuration 71 General Parameters 72 • Configuring the Network Interface 72 • Specifying the Installation Source and YaST Interface 75 • Example Parmfiles 76 5.7 Using the vt220 Terminal Emulator 77 5.8 Further Information on IBM Z 78 General Documents about Linux on IBM Z 78 • Technical Issues of Linux on IBM Z 78 • Advanced Configurations for Linux on IBM Z 79 6 Installation on Hardware Not Supported at Release 80 6.1 Download Kernel Update 80 6.2 Boot Kernel Update 80 II INSTALLATION PROCEDURE 81 7 Boot Parameters 82 7.1 Using the Default Boot Parameters 82 7.2 PC (AMD64/Intel 64/Arm AArch64) 83 The Boot Screen on Machines Equipped with Traditional BIOS 83 • The Boot Screen on Machines Equipped with UEFI 85 v Deployment Guide 7.3 List of Important Boot Parameters 88 General Boot Parameters 88 • Configuring the Network Interface 89 • Specifying the Installation Source 91 • Specifying Remote Access 92 7.4 Advanced Setups 93 Providing Data to Access an RMT Server 93 • Configuring an Alternative Data Server for supportconfig 94 • Using IPv6 for the Installation 94 • Using a Proxy for the Installation 95 • Enabling SELinux Support 95 • Enabling the Installer Self-Update 96 • Scale User Interface for High DPI 96 • Using CPU Mitigations 96 7.5 IBM Z 97 7.6 More Information 99 8 Installation Steps 100 8.1 Overview 100 8.2 Installer Self-Update 101 Self-Update Process 102 • Custom Self-Update Repositories 104 8.3 Language, Keyboard, and Product Selection 105 8.4 License Agreement 107 8.5 IBM Z: Disk Activation 107 Configuring DASD Disks 108 • Configuring zFCP Disks 109 8.6 Network Settings 110 8.7 Registration 111 Registering Manually 112 • Loading Registration Codes from USB Storage 114 • Installing without Registration 115 8.8 Extension and Module Selection 117 8.9 Add-On Product 121 8.10 System Role 123 vi Deployment Guide 8.11 Partitioning 125 Important Information 125 • Suggested Partitioning 127 8.12 Clock and Time Zone 130 8.13 Create New User 131 8.14 Authentication for the System Administrator “root” 134 8.15 Installation Settings 136 Software 136 • Booting 138 • Security 138 • Network Configuration 139 • Kdump 140 • IBM Z: Blacklist Devices 140 • Default systemd Target 140 • Import SSH Host Keys and Configuration 140 • System 141 8.16 Performing the Installation 142 IBM Z: IPLing the Installed System 142 • IBM Z: Connecting to the Installed System 144 9 Registering SUSE Linux Enterprise and Managing Modules/Extensions 146 9.1 Registering During the Installation 147 9.2 Registering during Automated Deployment 147 9.3 Registering from the Installed System 147 Registering with YaST 147 • Registering with SUSEConnect 150 9.4 Managing Modules and Extensions in a Running System 151 Adding Modules and Extensions with YaST 151 • Deleting Modules and Extensions with YaST 152 • Adding/Deleting Modules and Extensions with SUSEConnect 153 10 Expert Partitioner 156 10.1 Using the Expert Partitioner 156 Partition Tables 158 • Partitions 159 • Editing a Partition 163 • Expert Options 165 • Advanced Options 166 • More Partitioning Tips 166 • Partitioning and LVM 169 vii Deployment Guide 10.2 LVM Configuration 169 Create Physical Volume 170 • Creating Volume Groups 170 • Configuring Logical Volumes 171 10.3 Soft RAID 173 Soft RAID Configuration 173 • Troubleshooting 174 • For More Information 175 11 Remote Installation 176 11.1 Overview 176 11.2 Scenarios for Remote Installation 177 Installation from Source Media via VNC 177 • Installation from Network via VNC 178 • Installation from Source Media via SSH 179 • Installation from Network via SSH 180 11.3 Monitoring Installation via VNC 181 Preparing for VNC Installation 181 • Connecting to the Installation Program 182 11.4 Monitoring Installation via SSH 183 Preparing for SSH Installation 183 • Connecting to the Installation Program 183 11.5 Monitoring Installation via Serial Console 184 12 Troubleshooting 185 12.1 Checking Media 185 12.2 No Bootable Drive Available 185 12.3 Booting from Installation Media Fails 186 12.4 Boot Failure 187 12.5 Fails to Launch Graphical Installer 189 12.6 Only Minimalist Boot Screen Started 191 12.7 Log Files 191 viii Deployment Guide III CUSTOMIZING INSTALLATION IMAGES 192 13 Cloning Disk Images 193 13.1 Overview 193 13.2 Cleaning Up Unique System Identifiers 193 14 Customizing Installation Images with mksusecd 195 14.1 Installing mksusecd 195 14.2 Creating a Minimal Boot Image 196 14.3 Setting Default Kernel Boot Parameters 196 14.4 Customizing Modules, Extensions, and Repositories 197 14.5 Creating a Minimal Netinstall ISO 198 14.6 Change Default Repository 198 15 Customizing Installation Images Manually 199 IV SETTING UP AN INSTALLATION SERVER 200 16 Setting Up a Network Installation Source 201 16.1 Setting Up an Installation Server Using YaST 201 16.2 Setting Up an NFS Repository Manually 203 16.3 Setting Up an FTP Repository Manually 206 16.4 Setting Up an HTTP Repository Manually 207 16.5 Managing an SMB Repository 208 16.6 Using ISO Images of the Installation Media on the Server 209 17 Preparing Network Boot Environment 211 17.1 Setting Up a DHCP Server 211 Dynamic Address Assignment 212 • Assigning Static IP Addresses 213 • PXE and AutoYaST Installation Failures 213 ix Deployment Guide 17.2 Setting Up a TFTP Server 214 Installing
Recommended publications
  • IBM Power Systems Private Cloud Solution Is Enhanced to Support Selected SUSE Linux Enterprise Server Subscriptions As Shared Utility Capacity Resources

    IBM Power Systems Private Cloud Solution Is Enhanced to Support Selected SUSE Linux Enterprise Server Subscriptions As Shared Utility Capacity Resources

    IBM United States Hardware Announcement 121-045, dated April 20, 2021 IBM Power Systems Private Cloud Solution is enhanced to support selected SUSE Linux Enterprise Server subscriptions as Shared Utility Capacity resources Table of contents 1 Overview 1 Description 1 Key requirements 2 Order now 1 Effective date Overview The IBM(R) Power(R) Systems Private Cloud Solution with Shared Utility Capacity was initially launched with support to share Base processor and memory hardware resources, as well as AIX(R) and IBM i license entitlements, across a collection of similar Power servers in an enterprise. Now, selected SUSE Linux(R) Enterprise Server (SLES) subscription offerings will be supported as Base and Metered Capacity resources within an IBM Power Enterprise Pool (2.0) of IBM Power System E980 or E950 servers. Key requirements • For Linux metering, HMC 950 is required. Effective date April 30, 2021 Description SUSE Linux Enterprise Server subscription offerings will now be monitored, shared as Base Capacity, and made available as pay-per-use Metered Capacity resources when a Power Enterprise Pool (2.0) consisting of Power E980 or Power E950 systems is started: 5639-15S 5639-12S SUSE Linux Enterprise Server for Power with Base 1 - 2 Socket, Unlimited LPAR and Priority Subscription or Priority Subscription/Support features 5639-SAP SUSE Linux Enterprise Server for SAP Applications for Power with 1 - 2 Socket, Unlimited LPAR and Priority Subscription or Priority Subscription/Support features Base Capacity resources may be shared across systems within a pool. SLES Base subscription entitlement for each system will be set to the number of cores available in the quantity of sockets entitled by the current, valid subscription for that system IBM United States Hardware Announcement 121-045 IBM is a registered trademark of International Business Machines Corporation 1 (the number of cores per chip multiplied by the quantity of sockets acquired in the current subscription).
  • Automatic Dependency Management for Scientific Applications on Clusters

    Automatic Dependency Management for Scientific Applications on Clusters

    Automatic Dependency Management for Scientific Applications on Clusters Ben Tovar, Nicholas Hazekamp, Nathaniel Kremer-Herman, and Douglas Thain btovar,nhazekam,nkremerh,dthain @nd.edu { } Department of Computer Science and Engineering University of Notre Dame Abstract—Software installation remains a challenge in scien- are unprivileged, and multiple incompatible versions may need tific computing. End users require custom software stacks that to exist simultaneously. are not provided through commodity channels. The resulting To address this problem, we present VC3-Builder, a user- effort needed to install software delays research in the first place, and creates friction for moving applications to new resources level system for managing software dependencies across mul- and new users. Ideally, end-users should be able to manage their tiple clusters. VC3-Builder shares some elements of design own software stacks without requiring administrator privileges. with recent systems such as Nix [8] and Spack [10], but it To that end, we describe VC3-Builder, a tool for deploying is more suited for rapid deployment by exploiting pre-existing software environments automatically on clusters. Its primary software where available and using the resources of the cluster application comes in cloud and opportunistic computing, where deployment must be performed in batch as a side effect of job itself to perform parallel and distributed builds. execution. VC3-Builder uses workflow technologies as a means We demonstrate VC3-Builder by several case studies of of exploiting cluster resources for building in a portable way. We complex applications that present a challenge for users to build demonstrate the use of VC3-Builder on three applications with and deploy manually: the MAKER bioinformatics pipeline, the complex dependencies: MAKER, Octave, and CVMFS, building CVMFS distributed filesystem, and the Octave mathematics and running on three different cluster facilities in sequential, parallel, and distributed modes.
  • Android Apps for Absolute Beginners

    Android Apps for Absolute Beginners

    Android Apps for Absolute Beginners ■ ■ ■ Wallace Jackson i Android Apps For Absolute Beginners Copyright © 2011 by Wallace Jackson All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without the prior written permission of the copyright owner and the publisher. ISBN 978-1-4302-3446-3 ISBN 978-1-4302-3447-0 (eBook) Printed and bound in the United States of America (POD) Trademarked names, logos, and images may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, logo, or image we use the names, logos, and images only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights. President and Publisher: Paul Manning Lead Editor: Matthew Moodie Technical Reviewer: Kunal Mittal Editorial Board: Steve Anglin, Mark Beckner, Ewan Buckingham, Gary Cornell, Jonathan Gennick, Jonathan Hassell, Michelle Lowman, Matthew Moodie, Jeff Olson, Jeffrey Pepper, Frank Pohlmann, Douglas Pundick, Ben Renow-Clarke, Dominic Shakeshaft, Matt Wade, Tom Welsh Coordinating Editor: Corbin Collins Copy Editors: Marilyn Smith, Sharon Terdeman, Tracy Brown Compositor: MacPS, LLC Indexer: BIM Indexing & Proofreading Services Artist: April Milne Cover Designer: Anna Ishchenko Distributed to the book trade worldwide by Springer Science+Business Media, LLC., 233 Spring Street, 6th Floor, New York, NY 10013.
  • Remote Management Agent Technical Specifications

    Remote Management Agent Technical Specifications

    Remote Management Agent Technical Specifications HARDWARE REQUIREMENTS These requirements include in-store systems running the Master Agent (MA) or General Agent (GA) The Master Agent (MA) operates on a - TCx Sky Enhanced nominated in store device that runs one - Microsoft Windows of the following operating systems and - Linux provides a consolidated interface to REMS The in-store processor requirements - Processor: minimum 1 GHz processor - Memory: 2 GB The Master Agent memory requirements - Memory: 80 MB w/o any extensions or connected General Agents Note: Memory usage will increase, depending on the number of general agents connected to the Master Agent. The General Agent (GA) runs as a system - TCx Sky Controller service on: - Microsoft Windows system - Linux system - Java virtual machine (JVM) embedded agent The General Agent service requirements - Memory: 40 MB virtual memory running in a TCx Sky or Linux environment - Memory: 70 MB virtual memory running in a Windows environment Note: The MA and GA services cannot be installed on the same computer. The RMA agent (Master or General) This will require additional memory for each terminal. running on the TCx Sky Master Controller is used to manage each terminal in the store. Note: RMA 4.1 supports communication with previous levels of the GA. SOFTWARE REQUIREMENTS Java Install the appropriate Java Runtime Environment (JRE) for your platform on the system, to run Master and General Agents. Note: The JRE will not be shipped/bundled along with RMA version 3.2.2 and later. You will need to provide the JRE. For TCx Sky Remote Management Agents, you will not need to provide the JRE as the OS will facilitate the same.
  • Manjaro Linux

    Manjaro Linux

    MANJAROLINUX USERGUIDE THEMANJARODEVELOPMENTTEAM Copyright © 2018 the Manjaro Development Team. Licensed under the Attribution-ShareAlike 4.0 International Licence (the “Licence”); you may not use this file except in compliance with the License. You may obtain a copy of the Licence at: https://creativecommons.org/licenses/by-sa/4.0/legalcode Unless required by applicable law or agreed to in writing, software distributed under the Licence is distributed on an “as is” basis, without warranties or conditions of any kind, either express or implied. See the Licence for the specific language governing permissions and limitations under the Licence. The source code for this documentation can be downloaded from: https://github.com/manjaro/manjaro-user-guide/ user guide 5 The Manjaro Development Team Core Team Philip Müller Owner, Project Leader, Project Management and Co- ordination, Mirrors Manager, Server Manager, Packager, De- veloper, Web Developer Guillaume Benoit Developer, Moderation Ramon Buldó Developer, Packager Stefano Capitani Maintainer, Packager Bernhard Landauer Community Manager, Packager, Maintainer, Mod- eration, News Rob McCathie Maintainer Marcus Developer, Packager Teo Mrnjavac Developer Alexandre A. Arnt Developer, Moderation Ringo de Kroon Community Hugo Posnic Developer Artwork David Linares Designer Documentation Jonathon Fernyhough Editor of the User Guide 0.8.9-0.8.13, 15.09-15.12, Community Management, Cover art of the User Guide Sabras Wiki Manuel Barrette Editor of the User Guide 16.08-17.1, French transla- tion of the User Guide 17.0-17.1 Alumni Roland Singer Founder, Designer, Developer, Web Developer, Admin- istrator Carl Duff Community, Documentation and Wiki Management, Script- ing and Configuration Cumali Cinnamon and Gnome Community Editions Maintainer 6 manjaro linux Dan S.
  • Le 2016-07-20 REQUEST for PROPOSAL DEMANDE DE PROPOSITION

    Le 2016-07-20 REQUEST for PROPOSAL DEMANDE DE PROPOSITION

    1 1 RETURN BIDS TO: Title - Sujet RETOURNER LES SOUMISSIONS À: Visually Statistically Intelligent Bid Receiving - PWGSC / Réception des Solicitation No. - N° de l'invitation Date soumissions - TPSGC 45045-140073/C 2016-06-10 11 Laurier St. / 11, rue Laurier Client Reference No. - N° de référence du client Place du Portage, Phase III 000006399 Core 0B2 / Noyau 0B2 GETS Reference No. - N° de référence de SEAG Gatineau PW-$$EE-002-30267 Quebec K1A 0S5 File No. - N° de dossier CCC No./N° CCC - FMS No./N° VME Bid Fax: (819) 997-9776 002ee.45045-140073 Solicitation Closes - L'invitation prend fin Time Zone Fuseau horaire at - à 02:00 PM Eastern Daylight Saving REQUEST FOR PROPOSAL on - le 2016-07-20 Time EDT DEMANDE DE PROPOSITION F.O.B. - F.A.B. Proposal To: Public Works and Government Services Canada Plant-Usine: Destination: Other-Autre: We hereby offer to sell to Her Majesty the Queen in right Address Enquiries to: - Adresser toutes questions à: Buyer Id - Id de l'acheteur of Canada, in accordance with the terms and conditions Gabriel (ee div), Peter 002ee set out herein, referred to herein or attached hereto, the Telephone No. - N° de téléphone FAX No. - N° de FAX goods, services, and construction listed herein and on any (873) 469-4654 ( ) ( ) - attached sheets at the price(s) set out therefor. Destination - of Goods, Services, and Construction: Proposition aux: Travaux Publics et Services Destination - des biens, services et construction: Gouvernementaux Canada Nous offrons par la présente de vendre à Sa Majesté la Reine du chef du Canada, aux conditions énoncées ou Specified Herein incluses par référence dans la présente et aux annexes Précisé dans les présentes ci-jointes, les biens, services et construction énumérés ici sur toute feuille ci-annexée, au(x) prix indiqué(s).
  • Build Your Own Linux Distribution

    Build Your Own Linux Distribution

    Build Your Own Linux Distribution . during lunch break Michal Hruˇseck´y openSUSE Community Multiplier Team [email protected] Creating a distribution Distributions characteristics What we need to create our own distribution: Installation wizard Configuration utilities Branding Default configuration Package management Packages and their settings ... 3/20 c Novell Inc. All Right Reserved How to create distribution We want it fast and we don't want to work hard Let's use the others !!! And let's start with LiveCD 4/20 c Novell Inc. All Right Reserved Work to do What can we skip: Installation wizard Configuration utilities Package management Not necessary for LiveCD. What we need: Branding Default configuration Packages and their settings 5/20 c Novell Inc. All Right Reserved Closer look Branding: Just a different default theme We need to adjust/add packages Default configuration: We need to adjust packages Packages and their settings. =) Everything is about packages 6/20 c Novell Inc. All Right Reserved Conclusion We need quite a lot packages but we don't want to work on them by ourself. =) Let's fork Here it comes, let's use work done by somebody else So we need to get a lot of packages, maintain them easily and to be able to collaborate with other packagers =) openSUSE Build Service And we need something to create our LiveCD from our packages =) SUSE Studio 7/20 c Novell Inc. All Right Reserved openSUSE Build Service Build Service To build and publish packages... free and open platform for building packages for various distributions like openSUSE, Fedora, Ubuntu,..
  • Linux – Das Umfassende Handbuch 1.430 Seiten, Gebunden, Mit CD, 14

    Linux – Das Umfassende Handbuch 1.430 Seiten, Gebunden, Mit CD, 14

    Know-howWissen, wie’s für geht. Kreative. Leseprobe In dieser Leseprobe erhalten Sie einen Einstieg in die Linux-Welt und erfahren, wie Sie Audio und Video unter Linux nutzen. Dar- über hinaus lernen Sie die Kommandozentrale kennen: die Shell. Außerdem können Sie einen Blick in das vollständige Inhalts- und Stichwortverzeichnis des Buches werfen. »Was ist Linux?« »Installationsgrundlagen« »Audio und Video« »Die Shell« »Software- und Paketverwaltung« Inhaltsverzeichnis Index Der Autor Leseprobe weiterempfehlen Michael Kofler Linux – Das umfassende Handbuch 1.430 Seiten, gebunden, mit CD, 14. Auflage 2015 49,90 Euro, ISBN 978-3-8362-3775-8 www.rheinwerk-verlag.de/3855 “buch” — 2015/11/5 — 21:54 — page 25 — #19 1 Kapitel 1 Was ist Linux? Um die einleitende Frage zu beantworten, erkläre ich in diesem Kapitel zuerst einige wichtige Begriffe, die im gesamten Buch immer wieder verwendet werden: Betriebs- system, Unix, Distribution, Kernel etc. Ein knapper Überblick über die Merkmale von Linux und die verfügbaren Programme macht deutlich, wie weit die Anwendungs- möglichkeiten von Linux reichen. Es folgt ein kurzer Ausflug in die Geschichte von Linux: Sie erfahren, wie Linux entstanden ist und auf welchen Komponenten es basiert. Von zentraler Bedeutung ist dabei natürlich die General Public License (kurz GPL), die angibt, unter welchen Bedingungen Linux weitergegeben werden darf. Erst die GPL macht Linux zu einem freien System, wobei »frei« mehr heißt als einfach »kostenlos«. 1.1 Einführung Linux ist ein Unix-ähnliches Betriebssystem. Der wichtigste Unterschied gegenüber historischen Unix-Systemen besteht darin, dass Linux zusammen mit dem vollstän- digen Quellcode frei kopiert werden darf. Ein Betriebssystem ist ein Bündel von Programmen, mit denen die grundlegend- Betriebssystem sten Funktionen eines Rechners realisiert werden: die Schnittstelle zwischen Mensch und Maschine (also konkret: die Verwaltung von Tastatur, Bildschirm etc.) und die Verwaltung der Systemressourcen (CPU-Zeit, Speicher etc.).
  • Opensuse Leap to SLES: More Than the Sum of Its Parts

    Opensuse Leap to SLES: More Than the Sum of Its Parts

    openSUSE Leap to SLES: More Than The Sum Of Its Parts... Session TUT-1418 Udo Seidel Jeff Lindholm Tech-Writer and Enterprise Architect Sales Engineering Manager Amadeus SUSE [email protected] [email protected] 1 • Udo Seidel • Jeff Lindholm – SUSE • Teacher for Math and Physics • Detroit, MI USA • Linux and Open Source since 1996 • SUSE Evangelist since 2004 • Linux • Sales Engineering Manager • Software Defined Storage • OpenSUSE Community supporter • Openstack • Technology Focus • Container • Cloud Native Infrastructure • Raspberry Pi and Co • Application Transformation • … • Enterprise Linux • Enterprise Architect and Tech-Writer 2 Agenda 1. DevOPS Experience – Developer Use Case 2. OpenSUSE Community – Flexible Developer Platform 1. OpenSUSE Tumbleweed – Rolling Release 2. OpenSUSE Leap 15 – Stable Release 3. SUSE Linux Enterprise Server 15 4. LEAP SLE Interoperability and Supported Migration Use Cases 5. Demonstration – Leap Migration 6. Questions and Answers 3 4 SUSE Solutions For DevOps A suite of flexible, modular open source solutions CODE PLAN DEPLOY OBS, PackageHub, SUSE SUSE Linux Enterprise SUSE Application Delivery, Manager, Portus, GitHub openSUSE SUSE Public Cloud, SUSE Manager, Salt, Kubernetes BUILD OBS, SUSE Studio, SUSE Manager, KIWI, Docker open source project OPERATE & MONITOR SUSE Manager, SUSE Enterprise Storage, SUSE Application Delivery, TEST & RELEASE Kubernetes openQA, Jenkins 5 SUSE & openSUSE – Working Together Stable code and contributions Mutual collaboration Upstream innovations 6 These common elements are core to all openSUSE and SUSE distributions • YaST • openSUSE Build Service • Stability and testing - openQA 7 The openSUSE Distributions 8 openSUSE Tumbleweed • The Tumbleweed distribution is a pure rolling release version of openSUSE containing the latest stable versions of all software instead of relying on rigid periodic release cycles.
  • What's up with SUSE?

    What's up with SUSE?

    March 11, 2021 What’s up with SUSE? Picture Welcome to TriLug! 1.History of SUSE 2.SUSE Linux Distros 3.Other Products 4.Tease about Rancher Copyright © SUSE 2021 2 Who is this guy? • Joined SUSE in March 2018 • Formerly with Western Digital, SanDisk, Fusion-io, SteelEye Tech.,Sun Microsystems, Lockheed • MS Computer Science, West Virginia • Attending TriLug since 2007 • Takes care of his wife's chickens.... Dwain Sims Sales Engineer [email protected] [email protected] +1 919-480-1774 Copyright © SUSE 2021 3 What means SUSE? Copyright © SUSE 2021 4 S.u.S.E. Roland Dyroff, Thomas Fehr, Burchard Steinbild and Hubert Mantel found S.u.S.E., 1992. SUSE is a German acronym for "Software und System-Entwicklung" (software and systems development). Softlanding Linux System (SLS) was one of the earliest Liunx disros. (Slackware was initially based on SLS) First true S.u.S.E. Liunx distro was 4.2, in 1996. Copyright © SUSE 2021 5 How is SUSE pronounced? Copyright © SUSE 2021 6 Brief History of SUSE Copyright © SUSE 2021 7 A BOUT S US E 28 Years of Leadership in True Open Source 1992 to 2000 2001 to 2010 2011 to Present 2017 to Present Becoming strategic partner of From Linux Pioneer to The Pioneering Enabling an Always Open SAP and building a strong Software-Defined Years Data Center ecosystem Infrastructure and Edge Important Milestones 1992 2010 2020 SUSE brings Linux to the Linux-based solution Acquires enterprise with AWS Rancher Labs 2020 2008 2019 Partnership with SUSE celebrates first year of Joint innovation with SAP EQT independence 8 Copyright © SUSE 2020.
  • SUSE Studio: What's New and Where We Are Heading Building and Running Linux Appliances on the Web

    SUSE Studio: What's New and Where We Are Heading Building and Running Linux Appliances on the Web

    SUSE Studio: What's new and where we are heading Building and running Linux appliances on the web Jan Krupa – Operations Engineer [email protected] SUSE Studio Introduction 3 4 Supported formats • USB Stick / Hard Disk Image • Preload USB Image • Live CD / DVD (.iso) • Preload ISO (.iso) • VMware Workstation / VirtualBox (.vmdk) • OVF Virtual Machine / ESXi (.ovf) • Xen guest (.img) • Hyper-V Virtual Hard Disk (.vhd) • SUSE Cloud / OpenStack / KVM (.qcow2) • Amazon EC2 (.ami) • Microsoft Azure (.vhd) 5 6 Real life example Faulty hard drive Source: https://www.flickr.com/photos/alexmuse/307226463 8 New features New distributions • openSUSE releases • SUSE Linux Enterprise Server releases • SUSE Linux Enterprise Desktop releases 10 Cloud build targets • SUSE Cloud • OpenStack • Amazon EC2 • Microsoft Azure 11 HTTPS-only access Source: https://www.flickr.com/photos/bilal-kamoon/6958578902 12 Testdrive – Increased performance Source: https://www.flickr.com/photos/laserstars/908946494 13 API Source: https://www.flickr.com/photos/mutednarayan/2280385549 14 Webhooks Source: https://www.flickr.com/photos/leecullivan/934664620 15 Projects we work on KIWI openSUSE/kiwi 17 Open Build Service openSUSE/open-build-service 18 KVM 19 Contribute to the documentation Source: https://www.flickr.com/photos/nics_events/2350462608 susestudio/studio-help 20 Where to follow us • Mailing list ‒ http://susestudio.com/forum • Twitter ‒ https://twitter.com/susestudio • Google+ ‒ https://plus.google.com/+susestudio • Facebook ‒ https://www.facebook.com/susestudio 21 Questions? Join our growing community! susestudio.com Thank you..
  • Build Your Own Distro Tired of the Run-Of-The-Mill Stuff on Distrowatch? Why Not Heed Mayank Sharma and Create the Perfect Operating System for You?

    Build Your Own Distro Tired of the Run-Of-The-Mill Stuff on Distrowatch? Why Not Heed Mayank Sharma and Create the Perfect Operating System for You?

    Build your own distro Tired of the run-of-the-mill stuff on Distrowatch? Why not heed Mayank Sharma and create the perfect operating system for you? few issues ago, [LXF171, 50 making it your own – by removing apps and Now traditional wisdom says that creating Distros Tested], we looked at drivers that you don’t need and adding the your own Linux system is a rather difficult the best Linux distributions for ones you do. You’ll also probably change the thing to do and shouldn’t be attempted by A all kinds of users. There were factory-fitted artwork that says more about anyone other than Linux veterans. distros that were designed with ease of use the distro vendor than you. We begin the feature with graphical point- in mind, some focused on productivity, Sure that’s one way to go about it. and-click tools. Yes, you read that right. All it while others catered to specialised use You tweak and customise the distro to suit takes is a couple of clicks to craft your very cases, such as security and privacy your requirements. But wouldn’t it be really own flavour of Linux that you can pass to conscious users. But we can guarantee great if you just create your very own, custom friends and family. We’ve got tools that’ll help that there wasn’t a distro designed Linux distribution? you create and distribute customised spins specifically and entirely for you! based on Ubuntu, Fedora and While most Linux users make do OpenSUSE – the three mainstream with one of the mainstream distros out “We’ve got tools that’ll Linux distributions that house there, there’s always something or the help you create and thousands of open source software in other that’s missing.