DOCSLIB.ORG

SUSE Linux Enterprise Server: Upgrades & Migrations

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
SUSE Linux Enterprise Server: Upgrades & Migrations SUSE Linux Enterprise Server: Upgrades & Migrations TUT1146 Paul McKeith – Sales Engineer [email protected] Thorsten Kukuk – Senior Architect [email protected] 1 Agenda 1. Destination: SLES 12 or SLES 15? 2. Upgrade or Fresh Installation? 3. Upgrade Paths / Methods 4. Upgrade / Migration Process Tips 5. Appendix: SLES Support Lifecycle 2 SUSE Enterprise Linux 12 or 15? 3 Support Pack or Major Version Upgrade? What are your goals? GOAL: Maintain Support • End of Life / Lifecycle & Longevity • IHV & ISV Certification Requirements • Regulatory or Enterprise Policy Compliance • Compatible yet secure via backports GOAL: New OS Features - May require SLE 15 GOAL: New Hardware Support - May require SLE 15 GOAL: Minimize Uncertainty • If its not broke, don’t fix nor secure it! (example: TLS 1.2) 4 Server Platform Product Support Lifecycle SUSE ten year support commitment for SUSE Linux Enterprise 11, 12, and 15 https://www.suse.com/support/policy/ 6 Server Platform Product Support Lifecycle SUSE thirteen year support commitment for SUSE Linux Enterprise 11, 12, and 15 https://www.suse.com/support/policy/ 8 More time! Long Term Service Pack Support (LTSS) An option that provides up to 3 years of continued access to technical support, maintenance and security patches beyond general support expiration date. • For vanilla SLES 11,12, & 15 + SLES for SAP 11 SP4 • https://www.suse.com/products/long-term-service-pack-support/ Extended Support Pack Overlay Support (ESPOS) Total of 4.5 years of service pack support (1.5 yrs General + 3 yrs ESPOS). • Now included with SLES for SAP 12 & 15 • https://www.suse.com/c/suse-linux-enterprise-server-for-sap-applications- support-update/ 9 SLES 12 is not SLES 11 SP4.5 Binary incompatible (shared libraries) New features requiring major changes to base system Introduction of systemd Filesystem changes Old cruft removed Chance to resolve old mistakes 10 SLES 15 is not SLES 12 SP5.5, but… • Differences far less than between 11 & 12 • Filesystem changes • ReiserFS (no longer supported) • BTRFS sub-volumes / file locations • Next step with systemd • Hardware support (see slide: Hardware 2/3) • Processors, NVDIMM • Security, Performance • Multi-modal OS – The Foundation for the Modern Enterprise • Software Defined Infrastructure (SDI) – Containers, Kubernetes, Software Defined Storage • Cloud Native Application Delivery – DevOps & CI/CD 11 Workloads What is running on your system? “Small” services like DNS? “Big” services like SAP, Oracle, etc… How long can the services be down? Is your 3rd Party Software supported on SLES12 / SLES15? Some ISVs don't support a general major upgrade of OS and will require a fresh install Adjustment to configuration of third party packages may be needed 12 Hardware (1/3) How old is your hardware? Architecture changes i586 (32bit) to x86_64 POWER: big-endian to little-endian Support for old graphic cards removed Token ring no longer supported (SLES 12) Support of some disk controllers is may be removed by your IHV YES Certified Hardware: https://www.suse.com/partners/ihv/yes/ 13 Hardware (2/3) Upgrading to New Hardware too? • Today SLES 12 SP5 & SLES 15 have the same kernel • Similar but different hardware support • This will increasingly diverge over time • Intel Optane Non-volatile DIMM (NVDIMM) - SLES 12 SP4 & 15 • New x86 processors from Intel (e.g. Cascade Lake) and AMD (e.g. ROME) • Processor vulnerability OS (software) vs. on silicon mitigations • YES Certified Hardware: https://www.suse.com/partners/ihv/yes/ 14 Hardware (3/3) Do you have enough free disk space? RPMs and data are continuously growing Fresh Install will “reset” the baseline OS Binaries and Data separation BTRFS snapshot(s) rpm cache 15 SUSE Linux Enterprise Server 12 SP5 or SLES 15? General Considerations Align decision with deployment lifecycle and ISV requirements • SLES 12 will reach end of all general support 31 Oct 2024 (last SP) • SLES 15 will reach end of all general support 31 Jul 2028 • SAP Note: 2255581, 2578899 • Other ISVs SLES 15 Highlights… 16 SUSE Linux Enterprise 15+ • Kernel 4.12 (GA), 4.14 (SP1), 5.x (SP2) • Unified Installer (15) • Next step for systemd (15) • init scripts have been removed • innserv-compat for 3rd party • systemd-timer is replacing cron • reiserfs NOT supported • Modules Changes (15 sp1) • # zypper search-packages <pkg> 17 SUSE Linux Enterprise 15+ • 389 Directory Server replaces OpenLDAP (15) • Firewalld replaces SUSE Firewall2 (15 sp1) • RMT (15 sp1) replaces SMT • Salt management • Python 3 (15 sp1) • Chrony replaces ntpd (15) • NGINX is fully supported (15) • OpenSSL 1.0x is legacy (15) • OpenJDK 11 (15 sp1) 18 SUSE Linux Enterprise 15+ • File Placement (LSB is dead) • Improved separation of binaries and data… • BTRFS Snapshot and Rollback • BTRFS sub-volume layout (15) • /var no longer in snapshots • RPM database: /usr/lib/sysimage • Others • Transactional Updates • SP1 Technology Preview (15 sp1) • Atomic updates + health check scripts 19 For more information (1/2)… 20 For more information (2/2)… https://www.suse.com/betaprogram/sle-beta/ 21 Upgrade or Fresh Installation? 23 Upgrade or Fresh Installation? Every workload is different with unique combinations, SUSE can only generally inform and advise. Ask yourself… Why am I upgrading? • Bug Fixes • New Features • Optimize Performance • Multiple major versions behind • Compliance & Support • Security Concerns • How good is your current setup documented? • Any things you always wanted to have setup differently? 24 Upgrade Considerations (1/2) Old “stuff” will remain rd No longer maintained / no updates/security fixes but old 3 party apps may still work Possible package conflicts (ACPI) See slide: Upgrade (2/2) to identify orphaned packages Package Configuration Changes Old and new changes will be saved in new files during upgrade process for your reference See slide: Upgrade (2/2) to identify these files. rd Adjustment to configuration of 3 party packages may be needed Obsolete packages could still be the default and/or referenced by scripts requiring manual clean-up 25 Upgrade Considerations (2/2) Database migration See slide: Upgrade (1/2) for more information reiserfs Filesystem SLES 12 = compatible; SLES 15 = unsupported Some new features will NOT be useable Full system rollback for SLE12/15 depends on grub2, btrfs subvolume layout New XFS on disk format Full root filesystem encryption including /boot IPv6 support for e.g. iSCSI (could be archived by reconfiguration) Updating RPMs takes longer than fresh installation! 26 Fresh Installation Considerations (1/2) Generally recommended when skipping major versions All new features are useable New / updated filesystems reiserfs no longer supported in SLES 15 btrfs use cases: snapshot / rollback, transactional updates Re-design Opportunities Think about new disk / partition layout Think about package & module (SLES 15) selections No “old stuff” left behind Good or bad? 27 Fresh Installation Considerations (2/2) Completely fresh installation of third party software Step by step and test along the way Simplified Abort / Roll-back via Blue-Green approach Helpful if BTRFS is NOT in use or not enough free space available for snapshot / rollback Shared storage for data – Be careful # rsync -r Manual migration of configuration files and data to new system Tuning & optimization opportunity OS binaries & application data separation opportunity Must select the desired packages, patterns, modules 28 Upgrade or Fresh Install to SLES 15 SP1? General Recommendations (see slides: Upgrade Paths & Methods) If on SLES 11 SP4 or older and your destination is SLES 15 SP1: • Recommend fresh installation – not required; from 11 SP4 • Upgrade SLES 8 to SLES 11 SP4 first then 15? – not recommended If system was installed before SLES 12 SP2: • Recommend fresh installation – not required (btrfs initial snapshot) If system was installed with SLES 12 SP2 or later: • Upgrade from 12 SP3 LTSS, SP4 LTSS or SP5 otherwise fresh installation Fresh Installation Required for: SLES 11 32-bit to SLES 12 / 15 x86-64bit POWER big-endian to little endian 29 Upgrade Paths & Methods 30 Online vs Offline Upgrade Online – server up / running • Minor version (SP) upgrades only. Executed on an “up and running” system. Example: zypper and YaST online update connected via SUSE Customer Center (SCC), Subscription Mirroring Tool (SMT), Repository Mirroring Tool (RMT), Salt Policy via SUSE Manager. Offline – server down / not running • Major and minor version upgrades. Example: Installer for target release operating system is booted with DVD installation media, PXE/network boot, or via local bootloader to perform the upgrade. 31 Supported Paths to SLES 12 SP5 LTSS? 33 Supported Paths to SLES 15 SP1 NEW SP5? LTSS? https://documentation.suse.com/sles/15-SP1/single-html/SLES-upgrade/#sec-upgrade-paths-supported 35 Supported Scenarios (1/3) Major Version Upgrades: • From current SP versions that are still within General or LTSS support lifecycle at time of each new release (including SPs) • Offline Migration: • Boot from DVD, ISO image, USB stick, Network (PXE/tftp), AutoYaST with (autoupgrade=1 boot parameter) • Online Migration: • Not supported • SUSE Manager • Mass scripted upgrades (AutoYaST) 36 Supported Scenarios (2/3) Minor Version / Service Pack (SP) Upgrades: • Skipping of 1 (SLES 15) or 2 SPs (SLES 12). • Online Migration: • YaST or zypper migration (12 or 15) via # zypper migration • zypper distribution upgrade (12 or 15) via # zypper
Load more

Recommended publications
  • Questions for Openshift
    www.YoYoBrain.com - Accelerators for Memory and Learning Questions for OpenShift Category: Default - (402 questions) OpenShift:&nbsp; 2 primary tools to serve 1. container runtime - creates containers in application in OpenShift platform Linux 2. orchestration engine - manage cluster of servers running containers OpenShift:&nbsp; routing layer a software load balancer, when an application is deployed in OpenShift, a DNS entry is created and added to the load balancer, which interfaces with the Kubernetes service OpenShift:&nbsp; log into cluster and create oc&nbsp;login -u dev -p dev http://....:8443 user named dev with password dev OpenShift:&nbsp; what is the default port for 8443 OpenShift cluster OpenShift:&nbsp; what is a cluster's initial All All identity provider user name/password configuration allows any user and password combination to log in. OpenShift:&nbsp; ____ are the fundamental projects way applications are organized OpenShift:&nbsp; to create a project called oc&nbsp;new-project image-update image-update --display-name='My image update project' OpenShift:&nbsp; how to change to project oc&nbsp;project myProj myProj OpenShift:&nbsp; each application application source code deployment's image is created using _____ custom base image called a builder image and ____ OpenShift:&nbsp; the component that build config controls the creation of your application containers is _____ OpenShift:&nbsp; ____ contains all the info build config needed to build an application using its source code OpenShift:&nbsp; 4 things in build config 1. URL for the application source code 2. Name of builder image to use 3. Name of the application container image that is created 4.
    [Show full text]
  • Vulnerability Summary for the Week of June 5, 2017
    Vulnerability Summary for the Week of June 5, 2017 Please Note: • The vulnerabilities are categorized by their level of severity which is either High, Medium or Low. • The CVE identity number is the publicly known ID given to that particular vulnerability. Therefore, you can search the status of that particular vulnerability using that ID. • The CVSS (Common Vulnerability Scoring System) score is a standard scoring system used to determine the severity of the vulnerability. High Vulnerabilities Primary CVSS Source & Patch Vendor -- Product Description Published Score Info In Apache Hadoop 2.8.0, 3.0.0-alpha1, and 3.0.0-alpha2, the LinuxContainerExecutor runs docker commands as root with CVE-2017-7669 insufficient input validation. When the docker BID(link is feature is enabled, authenticated users can run 2017-06- external) apache -- hadoop commands as root. 04 8.5 MLIST CVE-2017-9364 Unrestricted File Upload exists in BigTree CONFIRM(link CMS through 4.2.18: if an attacker uploads an is external) bigtreecms -- 'xxx.pht' or 'xxx.phtml' file, they could bypass 2017-06- CONFIRM(link bigtree_cms a safety check and execute any code. 02 7.5 is external) CVE-2017-9435 Dolibarr ERP/CRM before 5.0.3 is vulnerable CONFIRM(link to a SQL injection in user/index.php is external) (search_supervisor and search_statut 2017-06- CONFIRM(link dolibarr -- dolibarr parameters). 05 7.5 is external) CVE-2014-9923 In NAS in all Android releases from CAF BID(link is using the Linux kernel, a Buffer Copy external) without Checking Size of Input vulnerability 2017-06- CONFIRM(link google -- android could potentially exist.
    [Show full text]
  • Guide to Open Source Solutions
    White paper ___________________________ Guide to open source solutions “Guide to open source by Smile ” Page 2 PREAMBLE SMILE Smile is a company of engineers specialising in the implementing of open source solutions OM and the integrating of systems relying on open source. Smile is member of APRIL, the C . association for the promotion and defence of free software, Alliance Libre, PLOSS, and PLOSS RA, which are regional cluster associations of free software companies. OSS Smile has 600 throughout the World which makes it the largest company in Europe - specialising in open source. Since approximately 2000, Smile has been actively supervising developments in technology which enables it to discover the most promising open source products, to qualify and assess them so as to offer its clients the most accomplished, robust and sustainable products. SMILE . This approach has led to a range of white papers covering various fields of application: Content management (2004), portals (2005), business intelligence (2006), PHP frameworks (2007), virtualisation (2007), and electronic document management (2008), as well as PGIs/ERPs (2008). Among the works published in 2009, we would also cite “open source VPN’s”, “Firewall open source flow control”, and “Middleware”, within the framework of the WWW “System and Infrastructure” collection. Each of these works presents a selection of best open source solutions for the domain in question, their respective qualities as well as operational feedback. As open source solutions continue to acquire new domains, Smile will be there to help its clients benefit from these in a risk-free way. Smile is present in the European IT landscape as the integration architect of choice to support the largest companies in the adoption of the best open source solutions.
    [Show full text]
  • Red Hat Directory Server 11 Installation Guide
    Red Hat Directory Server 11 Installation Guide Instructions for installing Red Hat Directory Server Last Updated: 2021-04-23 Red Hat Directory Server 11 Installation Guide Instructions for installing Red Hat Directory Server Marc Muehlfeld Red Hat Customer Content Services [email protected] Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Red Hat Enterprise Linux 6 6.4 Release Notes
    Red Hat Enterprise Linux 6 6.4 Release Notes Release Notes for Red Hat Enterprise Linux 6.4 Edition 4 Last Updated: 2017-10-20 Red Hat Enterprise Linux 6 6.4 Release Notes Release Notes for Red Hat Enterprise Linux 6.4 Edition 4 Red Hat Engineering Content Services Legal Notice Copyright © 2012 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Centos System Administration Essentials
    www.it-ebooks.info CentOS System Administration Essentials Become an efficient CentOS administrator by acquiring real-world knowledge of system setup and configuration Andrew Mallett BIRMINGHAM - MUMBAI www.it-ebooks.info CentOS System Administration Essentials Copyright © 2014 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: November 2014 Production reference: 1181114 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-78398-592-0 www.packtpub.com Cover image by Bartosz Chucherko ([email protected]) [ FM-2 ] www.it-ebooks.info Credits Author Project Coordinator Andrew Mallett Neha Thakur Reviewers Proofreaders Jonathan
    [Show full text]
  • Red Hat Jboss Fuse 6.3 Security Guide
    Red Hat JBoss Fuse 6.3 Security Guide Making it safe for your systems to work together Last Updated: 2017-11-09 Red Hat JBoss Fuse 6.3 Security Guide Making it safe for your systems to work together JBoss A-MQ Docs Team Content Services [email protected] Legal Notice Copyright © 2016 Red Hat. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent.
    [Show full text]
  • Installation Guide
    Red Hat Directory Server 10 Installation Guide Updated for Directory Server 10.6 Last Updated: 2020-12-07 Red Hat Directory Server 10 Installation Guide Updated for Directory Server 10.6 Marc Muehlfeld Red Hat Customer Content Services [email protected] Petr Bokoč Red Hat Customer Content Services Tomáš Čapek Red Hat Customer Content Services Petr Kovář Red Hat Customer Content Services Ella Deon Ballard Red Hat Customer Content Services Legal Notice Copyright © 2020 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
    [Show full text]
  • Vysok´E Uˇcení Technick´E V Brnˇe N´Astroj Pro
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Digital library of Brno University of Technology VYSOKEU´ CENˇ ´I TECHNICKE´ V BRNEˇ BRNO UNIVERSITY OF TECHNOLOGY FAKULTA INFORMACNˇ ´ICH TECHNOLOGI´I USTAV´ INFORMACNˇ ´ICH SYSTEM´ U˚ FACULTY OF INFORMATION TECHNOLOGY DEPARTMENT OF INFORMATION SYSTEMS NASTROJ´ PRO KONTROLU STAVU VSECHˇ REPLIK VE FREEIPA INFRASTRUKTUREˇ A TOOL TO CHECK STATUS OF ALL REPLICAS IN THE FREEIPA INFRASTRUCTURE DIPLOMOVA´ PRACE´ MASTER’S THESIS AUTOR PRACE´ Bc. DAVID SPˇ UREK˚ AUTHOR VEDOUC´I PRACE´ Ing. JAN ZELENY´ SUPERVISOR BRNO 2013 Abstrakt Tato diplomov´apr´acese zab´yv´amoˇznostmizjiˇstˇen´ıstavu vˇsech replik ve FreeIPA infras- truktuˇre. Na ´uvod pr´acejsou vysvˇetleny d˚uleˇzit´epojmy jako FreeIPA, FreeIPA infras- truktura a replika. FreeIPA server se skl´ad´az nˇekolika souˇc´ast´ı,kter´ebudou pops´any po- drobnˇeji.N´astroj navrˇzen´yv t´etopr´acivyuˇz´ıv´aSNMP pro sledov´an´ıstavu sluˇzebbˇeˇz´ıc´ıch na FreeIPA serveru. N´astroj m´advˇez´akladn´ıˇc´asti,kter´ymijsou konfigurace SNMP agenta a uˇzivatelsk´erozhran´ı. Abstract This master's thesis deals with possibilities how to check status of all replicas in FreeIPA infrastructure. At the begining of the thesis some important terms like FreeIPA, FreeIPA infrastructure and replica are explained. FreeIPA is a composition of several components which will be described. The tool designed in this master thesis uses SNMP for tracking a status of FreeIPA services. Two main parts of the tool are SNMP agent's configuration and user interface. Kl´ıˇcov´aslova FreeIPA, stav replik, stav sluˇzeb,SNMP.
    [Show full text]
  • Red Hat Enterprise Linux 7 7.1 Release Notes
    Red Hat Enterprise Linux 7 7.1 Release Notes Release Notes for Red Hat Enterprise Linux 7.1 Last Updated: 2018-05-18 Red Hat Enterprise Linux 7 7.1 Release Notes Release Notes for Red Hat Enterprise Linux 7.1 Red Hat Customer Content Services Legal Notice Copyright © 2015-2017 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Error Detection and Correction Suite for Freeipa Infrastructure
    MASARYK UNIVERSITY FACULTY OF INFORMATICS Û¡¢£¤¥¦§¨ª«¬­Æ°±²³´µ·¸¹º»¼½¾¿Ý Error detection and correction suite for FreeIPA infrastructure BACHELOR THESIS Tomáš Babej Brno, spring 2015 Declaration Hereby I declare, that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Tomáš Babej Advisor: Ing. Mgr. et Mgr. Zdenˇek Ríha,ˇ Ph.D. i Acknowledgment I would like to express my gratitude towards everybody who supported my during writing of the thesis. I want to thank Ing. Mgr. et Mgr. Zdenˇek Ríha,ˇ Ph.D. for his help and patient, prompt responses during supervision of my thesis. Additionally, I’m grateful for the support and technological help received from the FreeIPA developers, namely Ing. Petr Špaˇcek,Ing. Martin Košek and MSc. Alexander Bokovoy. ii Abstract The aim of this thesis is to implement a pluggable troubleshooting tool that collects and analyzes information about FreeIPA deployment. The thesis provides a detailed view on the architecture of FreeIPA servers and clients, their interaction and the technologies they are based on. Afterwards, high- level design and implementation details are featured, which serves as a guide for further extension by FreeIPA developers. iii Keywords FreeIPA, LDAP, Kerberos, PKI, Cockpit, troubleshooting, pluggable, tool iv Contents 1 Goal of the Thesis ...........................1 2 Foundational technologies ......................3 2.1 Lightweight Directory Access Protocol . .3 2.1.1 Directory services . .3 2.1.2 Structure of a LDAP directory .
    [Show full text]
  • Latest Release
    RavadaVDI Sep 22, 2021 Administrator Documentation 1 Ravada delivers 3 2 Who is Ravada meant for? 5 3 Ravada VDI documentation 7 3.1 Install Ravada..............................................7 3.2 Install Ravada in Ubuntu.........................................8 3.3 Install Ravada in Debian......................................... 10 3.4 Install Ravada on Fedora......................................... 12 3.5 Install Ravada - Ubuntu Xenial..................................... 15 3.6 Install Ravada from dockers....................................... 15 3.7 Running Ravada in production...................................... 17 3.8 log file.................................................. 19 3.9 Post Install Recomendations....................................... 20 3.10 Development release........................................... 20 3.11 Add KVM storage pool......................................... 24 3.12 Apache.................................................. 25 3.13 How to import a Virtualbox image.................................... 27 3.14 How to create a Virtual Machine..................................... 28 3.15 How to dump a hard drive to Ravada.................................. 29 3.16 How to Install a LDAP Server...................................... 29 3.17 How to add a KVM template....................................... 30 3.18 New ISO image............................................. 31 3.19 How to import a OpenGnsys image................................... 32 3.20 Integrating Ravada and OpenGnsys..................................
    [Show full text]