DOCSLIB.ORG

Deployment Guide Deployment Guide SUSE Linux Enterprise Server 12 SP5

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Deployment Guide Deployment Guide SUSE Linux Enterprise Server 12 SP5 SUSE Linux Enterprise Server 12 SP5 Deployment Guide Deployment Guide SUSE Linux Enterprise Server 12 SP5 Shows how to install single or multiple systems and how to exploit the product- inherent capabilities for a deployment infrastructure. Choose from various approaches, ranging from a local installation or a network installation server to a mass deployment using a remote-controlled, highly-customized, and automated installation technique. 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 xiv 1 Available Documentation xv 2 Giving Feedback xvi 3 Documentation Conventions xvii 4 Product Life Cycle and Support xix Support Statement for SUSE Linux Enterprise Server xix • Technology Previews xx 1 Planning for SUSE Linux Enterprise Server 1 1.1 Considerations for Deployment of a SUSE Linux Enterprise Server 1 1.2 Deployment of SUSE Linux Enterprise Server 1 1.3 Running SUSE Linux Enterprise Server 2 1.4 Registering SUSE Linux Enterprise Server 2 I INSTALLATION PREPARATION 4 2 Installation on AMD64 and Intel 64 5 2.1 System Requirements for Operating Linux 5 Hardware for Intel 64 and AMD64 5 2.2 Installation Considerations 6 Installation Type 6 • Boot Methods 7 • Installation Source 8 • Installation Target 8 • Different Installation Methods 8 2.3 Boot and Installation Media 9 Boot Media 9 • Installation Media 10 iii Deployment Guide 2.4 Installation Procedure 10 Booting from a Local Interchangeable Drive 10 • Installing over the Network 11 2.5 Controlling the Installation 11 Installation on the Computer Console 11 • Installation Using a Serial Console 11 • Installation with SSH 12 • Installation over VNC 12 • Installation with AutoYaST 13 2.6 Dealing with Boot and Installation Problems 13 Problems Booting 13 • Problems Installing 14 • Redirecting the Boot Source to the Boot DVD 14 3 Installation on IBM POWER 15 3.1 Hardware Requirements 15 3.2 Installing SUSE Linux Enterprise Server for POWER 16 3.3 Installing SUSE Linux Enterprise Server 19 3.4 Further Information 22 4 Installation on IBM Z and LinuxONE 23 4.1 General Information and Requirements 23 System Requirements 23 • Installation Types 27 • IPL Options 28 4.2 Preparing for Installation 29 Making the Installation Data Available 30 • Installation Types 36 • Preparing the IPL of the SUSE Linux Enterprise Server Installation System 37 • IPLing the SUSE Linux Enterprise Server Installation System 41 • Network Configuration 46 • Connecting to the SUSE Linux Enterprise Server Installation System 49 • The SUSE Linux Enterprise Server Boot Procedure on IBM Z 51 4.3 The parmfile—Automating the System Configuration 52 General Parameters 53 • Configuring the Network Interface 54 • Specifying the Installation Source and YaST Interface 56 • Example Parmfiles 57 4.4 Using the vt220 Terminal Emulator 58 iv Deployment Guide 4.5 Further Information on IBM Z 59 General Documents about Linux on IBM Z 59 • Technical Issues of Linux on IBM Z 59 • Advanced Configurations for Linux on IBM Z 60 • Virtualization with KVM on IBM Z 60 5 Installation on ARM AArch64 61 5.1 System Requirements for Operating Linux 61 Hardware for ARM AArch64 61 5.2 Installation Considerations 62 Installation Type 62 • Boot Methods 63 • Installation Source 64 • Installation Target 64 • Different Installation Methods 64 5.3 Boot and Installation Media 65 Boot Media 65 • Installation Media 66 5.4 Installation Procedure 66 Booting from a Local Interchangeable Drive 66 • Installing over the Network 67 5.5 Controlling the Installation 67 Installation on the Computer Console 67 • Installation Using a Serial Console 67 • Installation with SSH 68 • Installation over VNC 69 • Installation with AutoYaST 69 5.6 Dealing with Boot and Installation Problems 69 Problems Booting 69 • Problems Installing 70 • Redirecting the Boot Source to the Boot DVD 70 II THE INSTALLATION WORKFLOW 71 6 Installation with YaST 72 6.1 Choosing the Installation Method 72 6.2 System Start-up for Installation 73 IBM Z: System Start-up 73 • PC (AMD64/Intel 64/ARM AArch64): System Start-up 74 • Boot Parameters for Advanced Setups 82 v Deployment Guide 6.3 Steps of the Installation 86 6.4 Installer Self-Update 87 Self-Update Process 88 • Networking during Self-Update 89 • Custom Self-Update Repositories 89 6.5 Language, Keyboard and License Agreement 90 6.6 IBM Z: Disk Activation 91 Configuring DASD Disks 92 • Configuring zFCP Disks 93 6.7 Network Settings 94 6.8 SUSE Customer Center Registration 96 Loading Registration Codes from USB Storage 98 6.9 Extension Selection 99 6.10 System Role 102 6.11 Suggested Partitioning 104 6.12 Clock and Time Zone 109 6.13 Create New User 111 Expert Settings 113 6.14 Password for the System Administrator root 113 6.15 Installation Settings 115 Software 115 • Booting 117 • Security 117 • Kdump 118 • IBM Z: Blacklist Devices 119 • Default systemd Target 119 • Import SSH Host Keys and Configuration 119 • System Information 121 6.16 Performing the Installation 121 IBM Z: IPLing the Installed System 122 • IBM Z: Connecting to the Installed System 124 7 Cloning Disk Images 126 7.1 Cleaning Up Unique System Identifiers 126 vi Deployment Guide III SETTING UP AN INSTALLATION SERVER 128 8 Setting Up the Server Holding the Installation Sources 129 8.1 Setting Up an Installation Server Using YaST 129 8.2 Setting Up an NFS Repository Manually 132 8.3 Setting Up an FTP Repository Manually 134 8.4 Setting Up an HTTP Repository Manually 135 8.5 Managing an SMB Repository 137 8.6 Using ISO Images of the Installation Media on the Server 138 9 Preparing the Boot of the Target System 139 9.1 Setting Up a DHCP Server 139 9.2 Setting Up a TFTP Server 141 Setting Up a TFTP Server Using YaST 141 • Setting Up a TFTP Server Manually 141 9.3 Installing Files on TFTP Server 142 Preparing the Structure 142 • BIOS Files for x86 143 • UEFI Files for x86 144 • UEFI Files for AArch64 144 9.4 PXELINUX Configuration Options 145 9.5 Preparing the Target System for PXE Boot 148 9.6 Booting from CD or USB Drive Instead of PXE 148 9.7 Using Wake-on-LAN for Remote Wakeups 149 Prerequisites 149 • Verifying Wired Ethernet Support 149 • Verifying Wireless Interface Support 150 • Installing and Testing WOL 151 10 Deploying Customized Preinstallations 152 10.1 Preparing the Master Machine 152 vii Deployment Guide 10.2 Customizing the Firstboot Installation 153 Customizing YaST Messages 154 • Customizing the License Action 155 • Customizing the Release Notes 155 • Customizing the Workflow 156 • Configuring Additional Scripts 160 • Providing Translations of the Installation Workflow 161 10.3 Cloning the Master Installation 162 10.4 Personalizing the Installation 162 IV REMOTE INSTALLATION 163 11 Remote Installation 164 11.1 Installation Scenarios for Remote Installation 164 Simple Remote Installation via VNC—Static Network Configuration 164 • Simple Remote Installation via VNC—Dynamic Network Configuration 166 • Remote Installation via VNC—PXE Boot and Wake on LAN 167 • Simple Remote Installation via SSH—Static Network Configuration 168 • Simple Remote Installation via SSH—Dynamic Network Configuration 169 • Remote Installation via SSH—PXE Boot and Wake on LAN 170 11.2 Booting the Target System for Installation 171 Using the Default Boot Options 171 • Using Custom Boot Options 172 11.3 Monitoring the Installation Process 175 VNC Installation 175 • SSH Installation 176 V INITIAL SYSTEM CONFIGURATION 178 12 Setting Up Hardware Components with YaST 179 12.1 Setting Up Your System Keyboard Layout 179 12.2 Setting Up Sound Cards 179 12.3 Setting Up a Printer 183 Configuring Printers 183 • Configuring Printing via the Network with YaST 187 • Sharing Printers Over the Network 188 viii Deployment Guide 12.4 Setting Up a Scanner 189 Configuring an HP All-In-One Device 189 • Sharing a Scanner over the Network 190 • Scanning over the Network 190 13 Advanced Disk Setup 191 13.1 Using the YaST Partitioner 191 Partition Types 193 • Creating a Partition 194 • Editing a Partition 198 • Expert Options 200 • Advanced Options 200 • More Partitioning Tips 201 • Partitioning and LVM 203 13.2 LVM Configuration 204 LVM Configuration with YaST 204 13.3 Soft RAID Configuration with YaST 207 Soft RAID Configuration with YaST 207 • Troubleshooting 209 • For More Information 209 14 Installing or Removing Software 210 14.1 Definition of Terms 210 14.2 Registering an Installed System 211 Registering with YaST 212 • Registering with SUSEConnect 212 14.3 Using the YaST Software Manager 212 Views for Searching Packages or Patterns 213 • Installing and Removing Packages or Patterns
Load more

Recommended publications
  • 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).
    [Show full text]
  • Current Status of OFED in SUSE Linux Enterprise Server
    Current Status of OFED in SUSE Linux Enterprise Server John Jolly Senior Software Engineer SUSE Agenda 2 λAbout SUSE λAbout SUSE Linux Enterprise Server λOFED Integration into SLES λFuture Direction of OFED in SLES SUSE and the Attachmate Group λSUSE , headquartered in Nürnberg / Germany, λis an independently operating business unit of λThe Attachmate Group, Inc. λThe Attachmate Group is a privately held λ1 billion+ $ revenue software company λwith four brands: •Cloud Infrastructure •Enterprise Computing •Integrated Systems SUSE® Linux Enterprise How We Build It Online Repository Source Package Image OBS OBS user submits source to OBS and gets a product SUSE® Linux Enterprise Server 12 Lifecyle Model •13-year lifecycle (10 years general support, 3 years extended support) •5-year lifecycle per Service Pack (2 years general + 3 years extended support) •Long Term Service Pack Support (LTSS) available for all versions, including GA http://www.suse.com/lifecycle/ Unique Tools Included λAppArmor Security Framework -Application confinement λFree High Availability Extension -Cluster Framework, Cluster FS, DRBD, GEO-cluster* λYaST2 systems management -Install, deploy, and configure every aspect of the server λSubscription Management Tool -Subscription and patch management, proxy/mirroring/staging λStarter System for System z -A pre-built installation server, deployable with z/VM tools Features of SLES 12 λLinux Kernel 3.12 λOnly 64-bit kernel -Support of 32-bit application through execution environment λYaST modules written in Ruby λOFED 3.12 -Significant
    [Show full text]
  • SUSE® Linux Enterprise Server ("SLES ™")11 SP1 Novell® Software License Agreement
    SUSE® Linux Enterprise Server ("SLES ™")11 SP1 Novell® Software License Agreement PLEASE READ THIS AGREEMENT CAREFULLY. BY INSTALLING OR OTHERWISE USING THE SOFTWARE (INCLUDING ITS COMPONENTS), YOU AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE WITH THESE TERMS, DO NOT DOWNLOAD, INSTALL OR USE THE SOFTWARE. RIGHTS AND LICENSES This Novell Software License Agreement (“Agreement”) is a legal agreement between You (an entity or a person) and Novell, Inc. (“Novell”). The software product identified in the title of this Agreement, any media and accompanying documentation (collectively the “Software”) is protected by the copyright laws and treaties of the United States (“U.S.”) and other countries and is subject to the terms of this Agreement. Any update or support release to the Software that You may download or receive that is not accompanied by a license agreement expressly superseding this Agreement is Software and governed by this Agreement. If the Software is an update or support release, then You must have validly licensed the version and quantity of the Software being updated or supported in order to install or use the update or support release. The Software is a modular operating system comprised of numerous components that may be accompanied by separate license terms. The Software is a collective work of Novell; although Novell does not own the copyright to every component of the Software, Novell owns the collective work copyright for the Software. Most of the components are open source packages, developed independently, and accompanied by separate license terms. Your license rights with respect to individual components accompanied by separate license terms are defined by those terms; nothing in this agreement shall restrict, limit, or otherwise affect any rights or obligations You may have, or conditions to which You may be subject, under such license terms; however, if You distribute copies of any component independent of the Software, You must remove all Novell trademarks, trade dress, and logos from each copy.
    [Show full text]
  • SUSE Linux Enterprise Server 11 SP4 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 11 SP4
    SUSE Linux Enterprise Server 11 SP4 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 11 SP4 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 http://www.suse.com/company/legal/ . All other third party trademarks are the property of their respective owners. A trademark symbol (®, ™ etc.) denotes a SUSE or Novell trademark; an asterisk (*) denotes a third party trademark. 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 xi 1 Available Documentation xii 2 Feedback xiv 3 Documentation Conventions xv I BASICS 1 1 General Notes on System Tuning 2 1.1 Be Sure What Problem to Solve 2 1.2 Rule Out Common Problems 3 1.3 Finding the Bottleneck 3 1.4 Step-by-step Tuning 4 II SYSTEM MONITORING 5 2 System Monitoring Utilities 6 2.1 Multi-Purpose Tools 6 vmstat 7
    [Show full text]
  • 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.
    [Show full text]
  • Literature Review and Implementation Overview: High Performance
    LITERATURE REVIEW AND IMPLEMENTATION OVERVIEW: HIGH PERFORMANCE COMPUTING WITH GRAPHICS PROCESSING UNITS FOR CLASSROOM AND RESEARCH USE APREPRINT Nathan George Department of Data Sciences Regis University Denver, CO 80221 [email protected] May 18, 2020 ABSTRACT In this report, I discuss the history and current state of GPU HPC systems. Although high-power GPUs have only existed a short time, they have found rapid adoption in deep learning applications. I also discuss an implementation of a commodity-hardware NVIDIA GPU HPC cluster for deep learning research and academic teaching use. Keywords GPU · Neural Networks · Deep Learning · HPC 1 Introduction, Background, and GPU HPC History High performance computing (HPC) is typically characterized by large amounts of memory and processing power. HPC, sometimes also called supercomputing, has been around since the 1960s with the introduction of the CDC STAR-100, and continues to push the limits of computing power and capabilities for large-scale problems [1, 2]. However, use of graphics processing unit (GPU) in HPC supercomputers has only started in the mid to late 2000s [3, 4]. Although graphics processing chips have been around since the 1970s, GPUs were not widely used for computations until the 2000s. During the early 2000s, GPU clusters began to appear for HPC applications. Most of these clusters were designed to run large calculations requiring vast computing power, and many clusters are still designed for that purpose [5]. GPUs have been increasingly used for computations due to their commodification, following Moore’s Law (demonstrated arXiv:2005.07598v1 [cs.DC] 13 May 2020 in Figure 1), and usage in specific applications like neural networks.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • SUSE Openstack Cloud
    Product Flyer SUSE OpenStack Cloud SUSE OpenStack Cloud The digital economy is driving the need for fast IT transformation. Is your business able to keep up? The pace of change can be painful to manage, but it also creates new opportunities. SUSE® OpenStack Cloud provides a Software-Defined Infrastructure-as- a-Service (IaaS) for your data center, with access to pools of IT resources to quickly deploy and run applications. This gives you the flexibility to respond quickly and easily to new demands, providing the ideal platform for increased innovation, while helping you to control and reduce costs. SUSE OpenStack Cloud Product Overview most vibrant open source community at a Glance: SUSE OpenStack Cloud is the open source support, OpenStack is ideal for Open source cloud solution of choice for cloud solution of choice for enterprise developing new, innovative business enterprise businesses. business, helping you respond quickly to workloads and DevOps environments today’s ever-changing business-critical as well as for transforming traditional + Flexibility to respond quickly demands. data centers. SUSE OpenStack Cloud + Increase innovation leveraging the latest enables you to take full advantage technologies + Control and reduce costs SUSE OpenStack Cloud enables you to: of new business opportunities and rapidly evolving technology by Deliver improved agility, innovation enabling you to quickly deploy and and faster time to value to conquer easily manage an OpenStack private today’s competitive, market and cloud infrastructure. With a
    [Show full text]
  • 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,..
    [Show full text]
  • Kernel Module Packages Manual for SUSE Linux Enterprise 12 SP2 Or Later and SUSE Linux Enterprise 15
    SUSE Best Practices Kernel Module Packages Manual for SUSE Linux Enterprise 12 SP2 or later and SUSE Linux Enterprise 15 SUSE Linux Enterprise 12 SP2+, 15 Document Owner: Ann Davis, Senior Software Engineer, SUSE Kernel Module Packages Manual for SUSE Linux Enterprise 12 SP2 or later and SUSE Linux 1 Enterprise 15 SUSE-based distributions use the RPM Package Manager for software management. As such, any external kernel modules (these are kernel modules not included in SUSE kernel packages) should be packaged in RPM packages. These RPMs should be built in accordance with specic guidelines to ensure that the resulting Kernel Module Packages (KMPs) can be installed and updated appropriately, in synchronization with kernel updates. This document species the requirements for RPM packages that contain kernel modules, and describes the processes surrounding those packages including building, signing, installing and upgrading. A complete example is given and explained. This version of the Kernel Module Packages Manual applies to SUSE Linux Enterprise Server 12 (Service Pack 2 and later), and SUSE Linux Enterprise Server 15, and all products based on these versions. Publication Date: July 31, 2019 Contents 1 Scope 4 2 Background 4 3 Kernel Packages 6 4 Kernel Modules 7 5 Kernel Module Packages 8 6 RPM Provides and Requires 12 7 Building Kernel Module Packages 12 8 Signing 14 9 Deploying Kernel Module Packages 18 10 System Installation and Kernel Module Packages 18 Kernel Module Packages Manual for SUSE Linux Enterprise 12 SP2 or later and SUSE
    [Show full text]
  • 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.
    [Show full text]