DOCSLIB.ORG

Administering Linux in Production Environments Itinerary

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Administering Linux in Production Environments Itinerary Administering Linux in Production Environments 2 Itinerary Administering Linux in § Introduction Production Environments § Production Environment Features • Recent Kernel Developments • Filesystems: Mundane and Advanced • Disk Striping and RAID Administering • Parallel Processing and Clustering Linux in Æleen Frisch Production • Enterprise Networking Features Environments [email protected] § Deployment Examples www.aeleen.com • File and Print Servers • Enterprise User Authentication x Copyright © 1999-2001, e ponential Consulting, LLC Exponential Consulting, LLC • Beowulf Compute Servers North Haven, Connecticut, USA • Linux and Databases • Linux as an Office PC 2 3 4 What is a Production System? Commercial Applications § Real world § Major applications are available now: § System is a tool • Databases: Oracle, Sybase, DB2, etc. § “Money” is involved • Computational chemistry: Gaussian 98 Administering Administering Linux in Linux in • CAE: MSC:Nastran Production Production Environments Environments • Others § Keeping up Copyright © 1999-2001, Copyright © 1999-2001, • www.linas.org/linux Exponential Consulting, LLC Exponential Consulting, LLC • www.linuxports.com 3 4 Copyright © 1999-2001, Exponential Consulting, LLC. All rights reserved. Administering Linux in Production Environments 5 6 Dressing for Success § Tuxedo vs. Business Suit Recent § ILM: 11/15/2001 Administering Administering Kernel Linux in Linux in Production Production Environments Environments Developments Copyright © 1999-2001, Copyright © 1999-2001, Exponential Consulting, LLC Exponential Consulting, LLC 5 6 7 8 2.4 Kernel 2.4: Numbers § Feature Lists: § 64 GB memory • lwn.net/2001/0111/a/wwo2.4.php3 § >2GB files • January 2001 Linux Magazine § 16 Ethernet adapters Administering Administering Linux in Linux in Production Production § 10 IDE controllers Environments Environments § SMP support • Support for tons of processes Copyright © 1999-2001, Copyright © 1999-2001, Exponential Consulting, LLC Exponential Consulting, LLC • Scheduler improvement § Billions of users/groups 7 8 Copyright © 1999-2001, Exponential Consulting, LLC. All rights reserved. Administering Linux in Production Environments 9 10 Current Linux Limitations 2.4: I/O § Modes: § Memory size: 64 GB • Separate block device and file I/O § File size: 2 TB • Raw devices § Devices: § Filesystem size: 2 TB (VFS limitations) • I2O Administering Administering Linux in Linux in • USB Production § Filesystem block size=Memory page Production Environments Environments • Firewire (IEEE1394) • 4KB (x86) • PC Card • 16KB (IA-64) • Infrared Copyright © 1999-2001, Copyright © 1999-2001, Exponential Consulting, LLC Exponential Consulting, LLC§ APCI support § Graphics: Direct rendering manager 9 10 § SCSI2: Tagged command queuing 11 12 2.4: Networking 2.4: VFS and Related Facilities § Better multiprotocol support § Single buffer for file caching § Rewritten network layer (firewalls, • Eliminates synchronization problems IP masquerading): § Multiple mount points Administering Administering Linux in • Packet filtering Linux in Production Production Environments Environments • Network address translation § LVM in kernel § ATM and others § RAID rewrite Copyright © 1999-2001, Copyright © 1999-2001, Exponential Consulting, LLC § Can now mount NFS3 shares Exponential Consulting, LLC 11 12 Copyright © 1999-2001, Exponential Consulting, LLC. All rights reserved. Administering Linux in Production Environments 13 14 2.4 Bonus Features 2.4.1516 § Memory “Management” § ext3 • New swap space size “recommendations” • “experimental” • Fixed around 2.4.10 § InterMezzo filesystem Administering Administering Linux in Linux in Production Production Environments Environments Copyright © 1999-2001, Copyright © 1999-2001, Exponential Consulting, LLC Exponential Consulting, LLC 12.1 13’ 15 16 Itinerary Filesystems: § The VFS § Local Filesystems § Journaling Filesystems Administering Mundane and Administering Linux in Linux in Production Production Environments Advanced Environments § Network Shared Filesystems § Logical Volume Manager Copyright © 1999-2001, Copyright © 1999-2001, Exponential Consulting, LLC Exponential Consulting, LLC § Distributed Filesystems 14 15 Copyright © 1999-2001, Exponential Consulting, LLC. All rights reserved. Administering Linux in Production Environments 17 18 Spelling 101 Virtual File System (VFS) § Filesystem vs. file system § Kernel subsystem/layer § Provides a consistent interface for low-level file I/O Administering Administering Linux in Linux in Production Production Environments Environments § Filesystem need only implement the required functionality using that interface, and it is automatically supported Copyright © 1999-2001, Copyright © 1999-2001, Exponential Consulting, LLC Exponential Consulting, LLC 16 17 19 20 VFS Details FilesystemData Structures § Structured as an indirection layer § Superblock § Specifies low-level entities (objects) ... • FS metadata: label, block size, size, # inodes, … • Inodes, Files, Directories, Superblock, § Inodes Administering Administering Linux in Linux in Production Production Environments • Extended attributes Environments • Properties: file type, owners, permissions, times, #links, size, ... § ... and required/optional methods for each one • Data or Disk addresses or Single/double indirect Copyright © 1999-2001, Copyright © 1999-2001, Exponential Consulting, LLC Exponential Consulting, LLC § Directory 18 19 • = File that maps file names to inodes Copyright © 1999-2001, Exponential Consulting, LLC. All rights reserved. Administering Linux in Production Environments 21 22 VFS in Action 2.4.15+ § Command/application invokes system call § Journal block device module: designed § VFS looks up filesystem type in kernel table to add generic journaling capabilities to the VFS § Kernel redirects call to FS-supplied method Administering Administering Linux in Linux in Production Production Environments § Method runs and accesses disk Environments • Device drivers issue needed I/O requests § Method returns descriptor to desired object Copyright © 1999-2001, Copyright © 1999-2001, Exponential Consulting, LLC Exponential Consulting, LLC • Descriptor contains pointers to functions for accessing that object as well as related data 20 (e.g.: mounted filesystem, file, inode, dentry) 21 23 24 Filesystems for Local Disks Special filesystems § Many, many supported types: § procfs: /proc • ext2 • minix § Pseudo-device: /dev/pts § devfs: Administering • CD-ROM: iso9660, MS Joliet extensions, Administering Linux in Linux in Production v 2.4: udf for DVD Production Environments Environments • /dev/hda => /dev/ide0/disk0/... • ufs, fat, vfat , umsdos, ntfs, sysv , affs, adfs, hfs, • devfsdto support old device names hpfs, qnx4, ... Copyright © 1999-2001, Copyright © 1999-2001, Exponential Consulting, LLC v 2.4: ufs nextstep extensions, efs, ramfs, jffs, cramfs Exponential Consulting, LLC 22 23 Copyright © 1999-2001, Exponential Consulting, LLC. All rights reserved. Administering Linux in Production Environments 25 26 The ext2 Filesystem Ext2 FS Tools § 2GB files and 4TB filesystem § fsck.ext2 § 255 character filenames § mke2fs § SetGID directory group ownership inheritance § e2label Administering Administering Linux in Linux in Production • Selectable at mount time Production § dumpe2fs Environments Environments § Variable block sizes § tune2fs § Performance optimizations: § resize2fs Copyright © 1999-2001, Copyright © 1999-2001, Exponential Consulting, LLC Exponential Consulting, LLC • Read-ahead • Data block allocation and pre-allocation 24 25 27 28 The mke2fs Command dump2efs dumpe2fs 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09 Filesystem volume name: <none> Last mounted on: <not available> § -b block-size Filesystem UUID: 03d2f865-390a-4a5a -9162 -8f2fc902d3e2 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) • Default: 1024 bytes Filesystem features: (none) Filesystem state: not clean Errors behavior: Continue § -i bytes/inode or -N #inodes Filesystem OS type: Linux Administering Administering Inode count: 264928 Linux in • Default: 1 inode per 4096 bytes Linux in Block count: 528948 Production Production Reserved block count: 26447 Environments Environments Free blocks: 260025 § -m reserve% Free inodes: 184468 First block: 0 Block size: 4096 • Default: 5% Fragment size: 4096 Last mount time: Sun Dec 3 09:33:59 2000 Copyright © 1999-2001, Copyright © 1999-2001, Exponential Consulting, LLC Exponential Consulting, LLC Last write time: Mon Jan 29 17:41:57 2001 § -L label Mount count: 12 Maximum mount count: 20 Last checked: Wed Sep 6 18:54:01 2000 § -c or -l bad-block-file Check interval: 15552000 (6 months) Next check after: Mon Mar 5 17:54:01 2001 26 27 Reserved blocks uid : 0 (user root) Ò -f fragment-size Reserved blocks gid : 0 (group root) Copyright © 1999-2001, Exponential Consulting, LLC. All rights reserved. Administering Linux in Production Environments 29 30 The tune2fs Command Contributed ext2 Tools § -l to list superblock info § ext2fs defrag § Modify attributes (mount read-only?) § ext2fs resize • -c max-mounts § ext2fsed Administering Administering Linux in Linux in Production • -C mount-count Production § ext2undelete Environments Environments • -i check-interval[dmw] • -e error-behavior § See: “Filesystems-HOWTO” (section 6) Copyright © 1999-2001, Copyright © 1999-2001, Exponential Consulting, LLC v continue, remount-ro, panic Exponential Consulting, LLC • -m reserved% or -r reserved-blocks 28 • -g gid and/or -u uid 29 31 32 Journaling
Load more

Recommended publications
  • Stackable File Systems As a Security Tool
    Stackable File Systems as a Security Tool Erez Zadok Computer Science Department, Columbia University [email protected] CUCS-036-99 Abstract Programmers often prefer to use existing system security services, such as file system security, rather than im- plement their own in an application. Traditional Unix security is generally considered inadequate and few operating systems offer enhanced security features such as ACLs[24] or immutable files[12]. Additional file system security features are always sought, but implementing them is a difficult task because modifying and porting existing file systems is costly or not possible. We advocate adding new security features using stackable file systems. As a starting point, we propose a portable, stackable template called the wrapper file system or Wrapfs, a minimal file system from which a wide range of file systems can be prototyped. A developer can modify a copy of the template and add only that which is necessary to achieve the desired functionality. The Wrapfs template takes care of kernel internals, freeing the developer from the details of operating system internals. Wrapfs imposes an overhead of only 5–7%. This paper describes the design, implementation, and porting of Wrapfs. We discuss several prototype file sys- tems written using Wrapfs that illustrate the ease with which security features can be implemented. The examples demonstrate security features such as encryption, access control, intrusion detection, intrusion avoidance, and analy- sis. 1 Introduction Security has become and integral part of computing in recent years. To provide the strongest possible security to users, security solutions sometimes consume a large amount of resources, and may inconvenience their users too much.
    [Show full text]
  • Tree-Like Distributed Computation Environment with Shapp Library
    information Article Tree-Like Distributed Computation Environment with Shapp Library Tomasz Gałecki and Wiktor Bohdan Daszczuk * Institute of Computer Science, Warsaw University of Technology, 00-665 Warsaw, Poland; [email protected] * Correspondence: [email protected]; Tel.: +48-22-234-78-12 Received: 30 January 2020; Accepted: 1 March 2020; Published: 3 March 2020 Abstract: Despite the rapidly growing computing power of computers, it is often insufficient to perform mass calculations in a short time, for example, simulation of systems for various sets of parameters, the searching of huge state spaces, optimization using ant or genetic algorithms, machine learning, etc. One can solve the problem of a lack of computing power through workload management systems used in local networks in order to use the free computing power of servers and workstations. This article proposes raising such a system to a higher level of abstraction: The use in the .NET environment of a new Shapp library that allows remote task execution using fork-like operations from Portable Operating System Interface for UNIX (POSIX) systems. The library distributes the task code, sending static data on which task force is working, and individualizing tasks. In addition, a convenient way of communicating distributed tasks running hierarchically in the Shapp library was proposed to better manage the execution of these tasks. Many different task group architectures are possible; we focus on tree-like calculations that are suitable for many problems where the range of possible parallelism increases as the calculations progress. Keywords: workload management; remote fork; distributed computations; task group communication 1.
    [Show full text]
  • AFS - a Secure Distributed File System
    SLAC-PUB-11152 Part III: AFS - A Secure Distributed File System Alf Wachsmann Submitted to Linux Journal issue #132/April 2005 Stanford Linear Accelerator Center, Stanford University, Stanford, CA 94309 Work supported by Department of Energy contract DE–AC02–76SF00515. SLAC-PUB-11152.txt Part III: AFS - A Secure Distributed File System III.1 Introduction AFS is a secure distributed global file system providing location independence, scalability and transparent migration capabilities for data. AFS works across a multitude of Unix and non-Unix operating systems and is used at many large sites in production for many years. AFS still provides unique features that are not available with other distributed file systems even though AFS is almost 20 years old. This age might make it less appealing to some but with IBM making AFS available as open-source in 2000, new interest in use and development was sparked. When talking about AFS, people often mention other file systems as potential alternatives. Coda (http://www.coda.cs.cmu.edu/) with its disconnected mode will always be a research project and never have production quality. Intermezzo (http://www.inter-mezzo.org/) is now in the Linux kernel but not available for any other operating systems. NFSv4 (http://www.nfsv4.org/) which picked up many ideas from AFS and Coda is not mature enough yet to be used in serious production mode. This article presents the rich features of AFS and invites readers to play with it. III.2 Features and Benefits of AFS AFS client software is available for many Unix flavors: HP, Compaq, IBM, SUN, SGI, Linux.
    [Show full text]
  • Linux for Zseries: Device Drivers and Installation Commands (March 4, 2002) Summary of Changes
    Linux for zSeries Device Drivers and Installation Commands (March 4, 2002) Linux Kernel 2.4 LNUX-1103-07 Linux for zSeries Device Drivers and Installation Commands (March 4, 2002) Linux Kernel 2.4 LNUX-1103-07 Note Before using this document, be sure to read the information in “Notices” on page 207. Eighth Edition – (March 2002) This edition applies to the Linux for zSeries kernel 2.4 patch (made in September 2001) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 2000, 2002. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Summary of changes .........v Chapter 5. Linux for zSeries Console || Edition 8 changes.............v device drivers............27 Edition 7 changes.............v Console features .............28 Edition 6 changes ............vi Console kernel parameter syntax .......28 Edition 5 changes ............vi Console kernel examples ..........28 Edition 4 changes ............vi Usingtheconsole............28 Edition 3 changes ............vii Console – Use of VInput ..........30 Edition 2 changes ............vii Console limitations ............31 About this book ...........ix Chapter 6. Channel attached tape How this book is organized .........ix device driver ............33 Who should read this book .........ix Tapedriverfeatures...........33 Assumptions..............ix Tape character device front-end........34 Tape block
    [Show full text]
  • A Steganographic File System for the Linux Kernel
    A Steganographic File System for the Linux Kernel by Ashley Morgan Anderson The University of Exeter COM3401 Individual Project 11th August 2007 Abstract Encryption is all around us these days, yet the security of private data on home computers is overlooked by many. The presence of cipher-text — in some instances — can make things worse, therefore the only way to overcome this is to hide the data. The Ancient Greeks knew about this risk and as such fabricated some of the most ingenious methods of steganography ever used. However, steganography has come along way in the last 3000 years, and is more important today than ever before (due to tightening restrictions governing encryption). This paper looks at how different mediums have been used to ensure messages and data remain private, as well as proposing a new file system which takes care of hiding files for the user. Whilst not the first, it does include many unique features which are intended to provide a more natural interface. I certify that all material in this project which is not my own work has been identified. ...................................... A.M. Anderson Contents 1 Introduction 1 2 Background 2 2.1 Steganography . 2 2.2 File Systems . 4 2.3 Steganographic File Systems . 6 3 Design 11 3.1 Implemented Design . 11 3.2 Potential Driver Types . 13 3.3 Initial File System . 15 3.4 Encryption . 15 3.5 A Discarded Design . 16 4 Development 17 4.1 The Tools . 17 4.2 The Process . 18 5 Testing 19 5.1 Progressive . 19 5.2 Forensic Analysis .
    [Show full text]
  • Linux Kernal II 9.1 Architecture
    Page 1 of 7 Linux Kernal II 9.1 Architecture: The Linux kernel is a Unix-like operating system kernel used by a variety of operating systems based on it, which are usually in the form of Linux distributions. The Linux kernel is a prominent example of free and open source software. Programming language The Linux kernel is written in the version of the C programming language supported by GCC (which has introduced a number of extensions and changes to standard C), together with a number of short sections of code written in the assembly language (in GCC's "AT&T-style" syntax) of the target architecture. Because of the extensions to C it supports, GCC was for a long time the only compiler capable of correctly building the Linux kernel. Compiler compatibility GCC is the default compiler for the Linux kernel source. In 2004, Intel claimed to have modified the kernel so that its C compiler also was capable of compiling it. There was another such reported success in 2009 with a modified 2.6.22 version of the kernel. Since 2010, effort has been underway to build the Linux kernel with Clang, an alternative compiler for the C language; as of 12 April 2014, the official kernel could almost be compiled by Clang. The project dedicated to this effort is named LLVMLinxu after the LLVM compiler infrastructure upon which Clang is built. LLVMLinux does not aim to fork either the Linux kernel or the LLVM, therefore it is a meta-project composed of patches that are eventually submitted to the upstream projects.
    [Show full text]
  • Administration Guide Administration Guide SUSE Linux Enterprise High Availability Extension 15 SP1 by Tanja Roth and Thomas Schraitle
    SUSE Linux Enterprise High Availability Extension 15 SP1 Administration Guide Administration Guide SUSE Linux Enterprise High Availability Extension 15 SP1 by Tanja Roth and Thomas Schraitle This guide is intended for administrators who need to set up, congure, and maintain clusters with SUSE® Linux Enterprise High Availability Extension. For quick and ecient conguration and administration, the product includes both a graphical user interface and a command line interface (CLI). For performing key tasks, both approaches are covered in this guide. Thus, you can choose the appropriate tool that matches your needs. 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. 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
    [Show full text]
  • Filesystems HOWTO Filesystems HOWTO Table of Contents Filesystems HOWTO
    Filesystems HOWTO Filesystems HOWTO Table of Contents Filesystems HOWTO..........................................................................................................................................1 Martin Hinner < [email protected]>, http://martin.hinner.info............................................................1 1. Introduction..........................................................................................................................................1 2. Volumes...............................................................................................................................................1 3. DOS FAT 12/16/32, VFAT.................................................................................................................2 4. High Performance FileSystem (HPFS)................................................................................................2 5. New Technology FileSystem (NTFS).................................................................................................2 6. Extended filesystems (Ext, Ext2, Ext3)...............................................................................................2 7. Macintosh Hierarchical Filesystem − HFS..........................................................................................3 8. ISO 9660 − CD−ROM filesystem.......................................................................................................3 9. Other filesystems.................................................................................................................................3
    [Show full text]
  • Cryptographic File Systems Performance: What You Don't Know Can Hurt You Charles P
    Cryptographic File Systems Performance: What You Don't Know Can Hurt You Charles P. Wright, Jay Dave, and Erez Zadok Stony Brook University Appears in the proceedings of the 2003 IEEE Security In Storage Workshop (SISW 2003) Abstract interact with disks, caches, and a variety of other com- plex system components — all having a dramatic effect Securing data is more important than ever, yet cryp- on performance. tographic file systems still have not received wide use. In this paper we perform a real world performance One barrier to the adoption of cryptographic file systems comparison between several systems that are used is that the performance impact is assumed to be too high, to secure file systems on laptops, workstations, and but in fact is largely unknown. In this paper we first moderately-sized file servers. We also emphasize multi- survey available cryptographic file systems. Second, programming workloads, which are not often inves- we perform a performance comparison of a representa- tigated. Multi-programmed workloads are becoming tive set of the systems, emphasizing multiprogrammed more important even for single user machines, in which workloads. Third, we discuss interesting and counterin- Windowing systems are often used to run multiple appli- tuitive results. We show the overhead of cryptographic cations concurrently. We expect cryptographic file sys- file systems can be minimal for many real-world work- tems to become a commodity component of future oper- loads, and suggest potential improvements to existing ating systems. systems. We have observed not only general trends with We present results from a variety of benchmarks, an- each of the cryptographic file systems we compared but alyzing the behavior of file systems for metadata op- also anomalies based on complex interactions with the erations, raw I/O operations, and combined with CPU operating system, disks, CPUs, and ciphers.
    [Show full text]
  • Introduction to Linux Virtual Server and High Availability
    Outlines Introduction to Linux Virtual Server and High Availability Chen Kaiwang [email protected] December 5, 2011 Chen Kaiwang [email protected] LVS-DR and Keepalived Outlines If you don't know the theory, you don't have a way to be rigorous. Robert J. Shiller http://www.econ.yale.edu/~shiller/ Chen Kaiwang [email protected] LVS-DR and Keepalived Outlines Misery stories I Jul 2011 Too many connections at zongheng.com I Aug 2011 Realserver maintenance at 173.com quiescent persistent connections I Nov 2011 Health check at 173.com I Nov 2011 Virtual service configuration at 173.com persistent session data Chen Kaiwang [email protected] LVS-DR and Keepalived Outlines Outline of Part I Introduction to Linux Virtual Server Configuration Overview Netfilter Architecture Job Scheduling Scheduling Basics Scheduling Algorithms Connection Affinity Persistence Template Persistence Granularity Quirks Chen Kaiwang [email protected] LVS-DR and Keepalived Outlines Outline of Part II HA Basics LVS High Avaliablity Realserver Failover Director Failover Solutions Heartbeat Keepalived Chen Kaiwang [email protected] LVS-DR and Keepalived LVS Intro Job Scheduling Connection Affinity Quirks Part I Introduction to Linux Virtual Server Chen Kaiwang [email protected] LVS-DR and Keepalived LVS Intro Job Scheduling Configuration Overview Connection Affinity Netfilter Architecture Quirks Introduction to Linux Virtual Server Configuration Overview Netfilter Architecture Job Scheduling Scheduling Basics Scheduling Algorithms Connection Affinity Persistence Template Persistence Granularity Quirks Chen Kaiwang [email protected] LVS-DR and Keepalived LVS Intro Job Scheduling Configuration Overview Connection Affinity Netfilter Architecture Quirks A Linux Virtual Serverr (LVS) is a group of servers that appear to the client as one large, fast, reliable (highly available) server.
    [Show full text]
  • Keepalived User Guide Release 1.4.3
    Keepalived User Guide Release 1.4.3 Alexandre Cassen and Contributors March 06, 2021 Contents 1 Introduction 1 2 Software Design 3 3 Load Balancing Techniques 11 4 Installing Keepalived 13 5 Keepalived configuration synopsis 17 6 Keepalived programs synopsis 23 7 IPVS Scheduling Algorithms 27 8 IPVS Protocol Support 31 9 Configuring SNMP Support 33 10 Case Study: Healthcheck 37 11 Case Study: Failover using VRRP 43 12 Case Study: Mixing Healthcheck & Failover 47 13 Terminology 51 14 License 53 15 About These Documents 55 16 TODO List 57 Index 59 i ii CHAPTER 1 Introduction Load balancing is a method of distributing IP traffic across a cluster of real servers, providing one or more highly available virtual services. When designing load-balanced topologies, it is important to account for the availability of the load balancer itself as well as the real servers behind it. Keepalived provides frameworks for both load balancing and high availability. The load balancing framework relies on the well-known and widely used Linux Virtual Server (IPVS) kernel module, which provides Layer 4 load balancing. Keepalived implements a set of health checkers to dynamically and adaptively maintain and manage load balanced server pools according to their health. High availability is achieved by the Virtual Redundancy Routing Protocol (VRRP). VRRP is a fundamental brick for router failover. In addition, keepalived implements a set of hooks to the VRRP finite state machine providing low-level and high-speed protocol interactions. Each Keepalived framework can be used independently or together to provide resilient infrastructures. In this context, load balancer may also be referred to as a director or an LVS router.
    [Show full text]
  • Ubuntu Server Guide Basic Installation Preparing to Install
    Ubuntu Server Guide Welcome to the Ubuntu Server Guide! This site includes information on using Ubuntu Server for the latest LTS release, Ubuntu 20.04 LTS (Focal Fossa). For an offline version as well as versions for previous releases see below. Improving the Documentation If you find any errors or have suggestions for improvements to pages, please use the link at thebottomof each topic titled: “Help improve this document in the forum.” This link will take you to the Server Discourse forum for the specific page you are viewing. There you can share your comments or let us know aboutbugs with any page. PDFs and Previous Releases Below are links to the previous Ubuntu Server release server guides as well as an offline copy of the current version of this site: Ubuntu 20.04 LTS (Focal Fossa): PDF Ubuntu 18.04 LTS (Bionic Beaver): Web and PDF Ubuntu 16.04 LTS (Xenial Xerus): Web and PDF Support There are a couple of different ways that the Ubuntu Server edition is supported: commercial support and community support. The main commercial support (and development funding) is available from Canonical, Ltd. They supply reasonably- priced support contracts on a per desktop or per-server basis. For more information see the Ubuntu Advantage page. Community support is also provided by dedicated individuals and companies that wish to make Ubuntu the best distribution possible. Support is provided through multiple mailing lists, IRC channels, forums, blogs, wikis, etc. The large amount of information available can be overwhelming, but a good search engine query can usually provide an answer to your questions.
    [Show full text]