DOCSLIB.ORG

Red Hat Satellite 6.7 Provisioning Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Red Hat Satellite 6.7 Provisioning Guide Red Hat Satellite 6.7 Provisioning Guide A guide to provisioning physical and virtual hosts on Red Hat Satellite Servers. Last Updated: 2021-05-14 Red Hat Satellite 6.7 Provisioning Guide A guide to provisioning physical and virtual hosts on Red Hat Satellite Servers. Red Hat Satellite Documentation Team [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. The OpenStack ® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community. All other trademarks are the property of their respective owners. Abstract The Red Hat Satellite Provisioning Guide has instructions on provisioning physical and virtual hosts. This includes setting up the required network topology, configuring the necessary services, and providing all of the other configuration information to provision hosts on your network. Table of Contents Table of Contents .C . H. .A . P. .T .E . R. 1.. .I .N . T. .R .O . .D . U. .C . T. .I O. N. 5. 1.1. PROVISIONING OVERVIEW 5 1.2. NETWORK BOOT PROVISIONING WORKFLOW 5 .C . H. .A . P. .T .E . R. 2. C. .O . .N . F. .I G. .U . .R .I .N . G. P. .R . O. .V . I. S. I.O . .N . I.N . .G . .R . E. .S .O . .U . R. .C . E. .S . 8. 2.1. PROVISIONING CONTEXTS 8 2.2. SETTING THE PROVISIONING CONTEXT 8 2.3. CREATING OPERATING SYSTEMS 8 2.4. UPDATING THE DETAILS OF MULTIPLE OPERATING SYSTEMS 9 2.5. CREATING ARCHITECTURES 10 2.6. CREATING HARDWARE MODELS 11 2.7. USING A SYNCED KICKSTART REPOSITORY FOR A HOST’S OPERATING SYSTEM 11 2.8. ADDING INSTALLATION MEDIA TO SATELLITE 12 2.9. CREATING PARTITION TABLES 13 2.10. DYNAMIC PARTITION EXAMPLE 14 2.11. PROVISIONING TEMPLATES 14 2.12. TYPES OF PROVISIONING TEMPLATES 15 2.13. CREATING PROVISIONING TEMPLATES 16 2.14. CLONING PROVISIONING TEMPLATES 17 2.15. CREATING COMPUTE PROFILES 18 2.16. SETTING A DEFAULT ENCRYPTED ROOT PASSWORD FOR HOSTS 18 2.17. USING NOVNC TO ACCESS VIRTUAL MACHINES 18 .C . H. .A . P. .T .E . R. 3. C. O. .N . F. .I G. U. .R . I.N . G. N. E. T. .W . .O . .R .K . I.N . .G . .2 . 0. 3.1. NETWORK RESOURCES 20 3.2. SATELLITE AND DHCP OPTIONS 21 3.3. TROUBLESHOOTING DHCP PROBLEMS IN SATELLITE 22 3.4. PREREQUISITES FOR IMAGE BASED PROVISIONING 23 3.5. CONFIGURING NETWORK SERVICES 24 3.5.1. DHCP, DNS, and TFTP Options for Network Configuration 25 3.5.2. Using TFTP Services through NAT 26 3.6. ADDING A DOMAIN TO SATELLITE SERVER 26 3.7. ADDING A SUBNET TO SATELLITE SERVER 27 .C . H. .A . P. .T .E . R. 4. .U . S. .I N. .G . .I N. F. O. B. .L .O . .X . .A . S. D. .H . C. .P . .A . N. .D . .D . N. S. .P . R. .O . V. .I .D . E. .R .S . .2 . 9. 4.1. LIMITATIONS 29 4.2. PREREQUISITES 29 4.3. INSTALLING THE INFOBLOX CA CERTIFICATE ON CAPSULE SERVER 29 4.4. INSTALLING THE DHCP INFOBLOX MODULE 30 4.5. INSTALLING THE DNS INFOBLOX MODULE 31 .C . H. .A . P. .T .E . R. 5. C. .O . .N . F. .I G. .U . .R .I .N . G. I.P . X. .E . .T . O. R. .E . D. .U . C. .E . .P . R. .O . V. .I S. .I O. N. .I N. .G . T. I.M . .E . S. .3 . 2. 5.1. SETTING UP THE DISCOVERY SERVICE FOR IPXE 33 5.2. CHAINBOOTING VIRTUAL MACHINES 33 5.3. CHAINBOOTING SATELLITE SERVER TO USE IPXE DIRECTLY 35 5.4. CHAINBOOTING RED HAT SATELLITE CAPSULE TO USE IPXE DIRECTLY 37 .C . H. .A . P. .T .E . R. 6. .P .R . O. V. .I S. .I O. .N . .I N. .G . .B . A. .R . E. M. E. T. .A . L. H. .O . S. .T . S. .3 . 9. 6.1. PREREQUISITES FOR BARE METAL PROVISIONING 39 6.2. CONFIGURING THE SECURITY TOKEN VALIDITY DURATION 40 6.3. CREATING HOSTS WITH UNATTENDED PROVISIONING 40 6.4. CREATING HOSTS WITH PXE-LESS PROVISIONING 41 1 Red Hat Satellite 6.7 Provisioning Guide 6.5. DEPLOYING SSH KEYS DURING PROVISIONING 44 .C . H. .A . P. .T .E . R. 7. C. .O . .N . F. .I G. .U . .R .I .N . G. T. .H . E. D. .I S. .C . O. .V . E. .R . Y. S. .E .R . V. .I C. .E . .4 . 5. 7.1. INSTALLING THE DISCOVERY SERVICE 46 7.2. THE PROVISIONING TEMPLATE PXELINUX DISCOVERY SNIPPET 46 7.3. AUTOMATIC CONTEXTS FOR DISCOVERED HOSTS 47 7.4. DISCOVERY TEMPLATES AND SNIPPETS SETTINGS 47 7.5. CREATING HOSTS FROM DISCOVERED HOSTS 48 7.6. CREATING DISCOVERY RULES 50 7.7. IMPLEMENTING PXE-LESS DISCOVERY 51 7.8. BUILDING A DISCOVERY IMAGE 53 7.9. UNATTENDED USE, CUSTOMIZATION, AND IMAGE REMASTERING 55 7.10. EXTENDING THE DISCOVERY IMAGE 57 7.11. TROUBLESHOOTING DISCOVERY 58 .C . H. .A . P. .T .E . R. 8. .U . S. I. N. .G . .A . .R . E. .D . .H . A. .T . .I M. A. .G . E. B. .U . I.L . D. .E . R. .I .M . A. .G . .E . F. .O . .R . P. .R . O. V. .I S. .I O. .N . I. N. .G . .5 . 9. .C . H. .A . P. .T .E . R. 9. .P .R . O. V. .I S. .I O. .N . .I N. .G . .V . I.R . T. .U . A. .L . .M . .A . C. .H . I.N . E. .S . .O . N. K. .V . M. .( .L .I .B .V . I. R. .T .) . .6 .0 . 9.1. CONFIGURING SATELLITE SERVER FOR KVM CONNECTIONS 61 9.2. ADDING A KVM CONNECTION TO SATELLITE SERVER 61 9.3. ADDING KVM IMAGES TO SATELLITE SERVER 62 9.4. ADDING KVM DETAILS TO A COMPUTE PROFILE 63 9.5. CREATING HOSTS ON KVM 64 .C . H. .A . P. .T .E . R. 1.0 . .. P. .R . O. .V . I. S. I.O . .N . I.N . .G . .V . I.R . T. .U . A. .L . M. A. .C . H. .I .N . E. .S . O. N. R. .E . D. H. .A . T. V. .I R. .T .U . A. .L . I.Z . A. .T .I .O . N. .6 . 7. 10.1. ADDING THE RED HAT VIRTUALIZATION CONNECTION TO SATELLITE SERVER 68 10.2. PREPARING CLOUD-INIT IMAGES IN RED HAT VIRTUALIZATION 69 10.3. ADDING RED HAT VIRTUALIZATION IMAGES TO SATELLITE SERVER 69.
Load more

Recommended publications
  • Types of LMS Deployment & Common Features
    Types of LMS Deployment & Common Features Daisyane Barreto, Amy Rottmann, & Salena Rabidoux In cooking, you have many different types of tools you can use to make a meal. For example, you have mixers, measuring cups, cutting boards, and so many other tools. Each tool is designed to meet the needs of the cooker and serve a specific purpose in the cooking process. An LMS is not different in that sense. There are several types of LMSs in the market being used for educational as well as training purposes, and one of the most difficult choices for organizations and institutions to make is deciding the type of LMS to select based on deployment or license (Pappas, 2014). Of course, many other factors (e.g., pricing, support, additional features, and others) must be considered and weighed in this decision. Still, the cost combined with financial and technical requirements are still the main focus when selecting an LMS (Croitoru & Dinu, 2016). Indeed, it is important to analyze and examine the type of LMS deployment because of its influence in the overall cost as well as other relevant requirements that can inform the decision about an LMS. There are two main types of LMS deployment you need to be familiar with: (1) proprietary, and (2) open-source. Within those two solutions, there are two other distinct categories to be considered: (a) Software as a Service (SaaS) or cloud-based system and (b) Installed LMS. In order to determine what type of LMS is beneficial to an organization or institution, a clear understanding of the advantages and disadvantages of each solution must be reviewed.
    [Show full text]
  • IBM Cloud Satellite: Delivering True Hybrid Multicloud Capabilities
    Produced by TIMOTHYH/ADOBE IBM Cloud Satellite: delivering true hybrid multicloud capabilities without geographical boundaries Produced by True hybrid capabilities delivered via public cloud and on-premise systems IBM Cloud Satellite enables organisations to enjoy the benefits of consistent and flexible public cloud services wherever in the world they want them, confident in the knowledge that compliance with local security and regulations is being managed by IBM Cloud rganisations are increasingly moving IT workloads to the cloud to achieve “Consistency benefits including flexibility, scale and consistent application performance O wherever their operations are located. means the same set of services, But for many IT leaders, retaining some applications and data in-house is essential – perhaps for regulatory compliance or local security needs. wherever you need According to TechTarget’s annual IT priorities research, 34% of European IT them, whether on leaders are increasing their cloud spending in 2020, even though 46% of the IBM Cloud, on organisations surveyed say that on-premise systems will remain their primary environment. Not surprisingly, therefore, a quarter of IT chiefs are prioritising someone else’s hybrid cloud. cloud, on-premise, But hybrid setups can suffer from inconsistent user experiences and fragmented or in a third-party visibility. Systems management can be challenging in a mixed cloud and on-premise environment, and more so when using multiple public cloud providers. datacentre” IBM Cloud aims to tackle this issue with its new offering, IBM Cloud Satellite, Dave Tropeano, which brings the benefits of cloud to in-house IT systems, delivering services IBM Cloud that are consistent, flexible and compliant with security and regulatory rules, while ensuring organisations are not restricted by location.
    [Show full text]
  • Red Hat Virtualization 4.3 Planning and Prerequisites Guide
    Red Hat Virtualization 4.3 Planning and Prerequisites Guide Planning for the Installation and Configuration of Red Hat Virtualization 4.3 Last Updated: 2019-05-09 Red Hat Virtualization 4.3 Planning and Prerequisites Guide Planning for the Installation and Configuration of Red Hat Virtualization 4.3 Red Hat Virtualization Documentation Team Red Hat Customer Content Services [email protected] Legal Notice Copyright © 2019 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, 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]
  • Spacewalk for Oracle® Linux Installation Guide for Release 2.6
    The software described in this documentation is either no longer supported or is in extended support. Oracle recommends that you upgrade to a current supported release. Spacewalk for Oracle® Linux Installation Guide for Release 2.6 E85212-14 August 2020 The software described in this documentation is either no longer supported or is in extended support. Oracle recommends that you upgrade to a current supported release. Oracle Legal Notices Copyright © 2020, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.
    [Show full text]
  • Oracle® Linux Virtualization Manager Release Notes for Release 4.2.8
    Oracle® Linux Virtualization Manager Release Notes for Release 4.2.8 F15084-02 September 2019 Oracle Legal Notices Copyright © 2019, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S.
    [Show full text]
  • Satellite 6 User Guide
    Satellite 6 User Guide ID Client Delivery 08.06.2017 pdf generated on July 7, 2017 Satellite 6 User Guide ETH Z¨urich Table of Contents 1 Concepts 3 1.1 Terminology . .3 1.2 Description of Key Elements . .3 1.2.1 Life Cycle Management . .3 1.2.2 Content View . .3 1.2.3 Types of Hosts . .4 1.2.4 Types of Host Groups . .4 1.2.5 Operating System . .5 1.2.6 Activation Key . .6 1.2.7 Installation Object Hierarchy . .6 1.2.8 Parameter Hierarchy . .7 1.2.9 Configuration Parameters . .7 1.2.10 Users and Roles . .7 1.3 Installation . .8 1.3.1 Manual Installation . .8 1.3.2 Automated Installation . .8 2 Step by Step 9 2.1 Environment Preparation . .9 2.1.1 Operating System and Templates . 10 2.2 Boot Process and Installation . 10 2.3 Managing Systems . 11 2.3.1 Managing Software . 11 2.3.2 Collection Membership . 11 2.4 Configuration . 12 2.4.1 Concepts . 12 2.4.2 Preparing Puppet Modules . 12 2.4.3 Parameters . 12 2.4.4 Updating Modules . 12 2.4.5 Host Group . 13 3 Task Reference 13 3.1 Create Activation Key . 14 3.2 Create Subnet . 15 3.3 Create Hostgroup . 16 3.4 Create Host . 17 3.5 Install Host . 18 3.6 Create Content View . 19 3.7 Use Lifecycle . 20 4 Troubleshooting 21 4.1 Enable Reinstallation of Hosts . 21 4.2 Enable Errata through Content Views . 21 4.3 Enable Build is not Available .
    [Show full text]
  • Red Hat Satellite Power User Tips and Tricks
    RED HAT SATELLITE POWER USER TIPS AND TRICKS Zero to Production in a Day Thomas Cameron, RHCA, RHCDS, RHCSS, RHCVA, RHCX Digital Transformation Strategist Rich Jerrido, RHCA, RHCDS, RHCSS, RHCVA Red Hat Satellite Technical Marketing Manager May 2, 2017 AGENDA AGENDA Hold on Tight, We’re Gonna be MOVING! About Us Satellite – A Brief History Installation The Manifest Products Syncing Content Locations Lifecycle Environments Content Views Puppet AGENDA Hold on Tight, We’re Gonna be MOVING! Subnets Host Collections Domains Installation Media Provisioning Templates Operating Systems Activation Keys Host Groups Compute Resources Build a New Host ABOUT US ABOUT US Who Are We, and Why Should You Listen To Us? Rich Jerrido ● [email protected], @sideangleside on Twitter ● X years at Red Hat, from sales engineer to technical leader for systems management ● Live in Philly, work globally ● Former United States Marine Thomas Cameron ● [email protected], @thomasdcameron on Twitter ● 11 years at Red Hat, from sales engineer to digital transformation strategist ● Live in Austin, work globally ● Former police of=cer ABOUT SATELLITE Where Did It Come From? Where is it Going? Initially designed re-using code from rhn.redhat.com (RHAS 2.1) First released as a set of perl scripts and tarballs ● Required in depth experience, close work with the RHN engineering team, and the tears of baby Jesus Initially closed source due to inclusion of proprietary database from The Vendor Who Shall Not Be Named ● But OSS DB tech caught up, and v. 5 was fully Open Source ABOUT SATELLITE Where Did It Come From? Where is it Going? Relatively monolithic design, new features (monitoring, API support, etc.) were bolted on over time ABOUT SATELLITE Where Did It Come From? Where is it Going? Relatively monolithic design, new features (monitoring, API support, etc.) were bolted on over time ABOUT SATELLITE Where Did It Come From? Where is it Going? Version 5 is very full featured, supporting physical and virtual machine provisioning Not designed for cloud scale, though.
    [Show full text]
  • Foreman Basics Be Smart
    Foreman Basics Be smart. Think open source. Foreman - Basics Lifecycle management of physical and virtual machines made easy! Agenda Introduction to Foreman Architecture Setup Provisioning Configuration Monitoring Advanced features Introduction to Foreman What's it all about? Facts Project started in 2009 Licensed under the GPLv3 Development pushed by Red Hat Very active & helpful community Overview Tool for provisioning of VMs & bare metal Provides config management & monitoring integration Rails & JavaScript application Exposes a web interface, REST API & CLI Ecosystem Foreman Smart Proxy (foreman-proxy) Katello Tons of plugins Strong suite Very flexible Offers tons of features Active development & open community Modular setup, start small then expand Strong suite Can serve as a source of truth (CMDB) Can be used as an ENC Proper ACL implementation Enterprise Support available (Red Hat Satellite 6) Weak spots Somewhat steep learning curve Can be quite tricky to debug an issue API has room for improvement Offers sometimes too many possible ways to implement a task Architecture Overview of the different components Bird's-eye view Foreman Heart of the whole stack Stores all resources & information Rails stack, use Passenger + nginx / Apache to run it Stores most data in a DB (SQLite, MySQL or PostgreSQL) Local or LDAP users for authentication Smart Proxy Small autonomous HTTP application Exposes a REST API to provide different services Allows Foreman to control components in isolated networks Also called foreman-proxy Smart Proxy DHCP DNS TFTP BMC / IPMI Puppet / Salt / Chef / Ansible Realm / FreeIPA Smart Proxy - DHCP Takes care of reserving the required IPs Provides IP auto-assignment Supports ISC DHCP, MS DHCP & libvirt More providers can be installed or developed (e.g.
    [Show full text]
  • Before Peer Production: Infrastructure Gaps and the Architecture of Openness in Synthetic Biology
    BEFORE PEER PRODUCTION: INFRASTRUCTURE GAPS AND THE ARCHITECTURE OF OPENNESS IN SYNTHETIC BIOLOGY David Singh Grewal* In memoriam Mark Fischer (1950 – 2015)µ * Professor of Law, Yale Law School, and Director, BioBricks Foundation. The views expressed here are my own, and do not reflect the views of any of the organizations or entities with which I am or have been affiliated. Among those to whom I owe thanks, I am especially grateful to Drew Endy, President of the BioBricks Foundation (BBF) who worked to educate me about synthetic biology, and later invited me to join the board of directors of the BBF, and to the late Mark Fischer, who was the lead drafter (along with Drew Endy, Lee Crews, and myself) of the BioBrick™ Public Agreement, and to whose memory this Article is dedicated. I am also grateful to other past and present directors and staff of the BBF, including Richard Johnson, Linda Kahl, Tom Knight, Thane Krier, Nathalie Kuldell, Holly Million, Jack Newman, Randy Rettberg, and Pamela Silver. I have benefitted from conversations about synthetic biology and open source theory with a number of other scientists, including Rob Carlson, George Church, Jason Kelly, Manu Prakash, Zach Serber, Reshma Shetty, Christina Smolke, Ron Weiss and with a number of lawyers, scholars, and open source advocates including Yochai Benkler, James Boyle, Daniela Cammack, Paul Cammack, Paul Goldstein, Hank Greely, Janet Hope, Margot Kaminski, Mark Lemley, Stephen Maurer, Eben Moglen, Lisa Ouellette, Jedediah Purdy, Arti Rai, Pamela Samuelson, Jason Schultz, and Andrew Torrance, and especially Talli Somekh, who first introduced me to synthetic biology and noted the connections between my work in network theory and new developments in biotechnology.
    [Show full text]
  • An Overview of Security in the Freebsd Kernel 131 Dr
    AsiaBSDCon 2014 Proceedings March 13-16, 2014 Tokyo, Japan Copyright c 2014 BSD Research. All rights reserved. Unauthorized republication is prohibited. Published in Japan, March 2014 INDEX P1A: Bold, fast optimizing linker for BSD — Luba Tang P1B: Visualizing Unix: Graphing bhyve, ZFS and PF with Graphite 007 Michael Dexter P2A: LLVM in the FreeBSD Toolchain 013 David Chisnall P2B: NPF - progress and perspective 021 Mindaugas Rasiukevicius K1: OpenZFS: a Community of Open Source ZFS Developers 027 Matthew Ahrens K2: Bambi Meets Godzilla: They Elope 033 Eric Allman P3A: Snapshots, Replication, and Boot-Environments—How new ZFS utilities are changing FreeBSD & PC-BSD 045 Kris Moore P3B: Netmap as a core networking technology 055 Luigi Rizzo, Giuseppe Lettieri, and Michio Honda P4A: ZFS for the Masses: Management Tools Provided by the PC-BSD and FreeNAS Projects 065 Dru Lavigne P4B: OpenBGPD turns 10 years - Design, Implementation, Lessons learned 077 Henning Brauer P5A: Introduction to FreeNAS development 083 John Hixson P5B: VXLAN and Cloud-based networking with OpenBSD 091 Reyk Floeter INDEX P6A: Nested Paging in bhyve 097 Neel Natu and Peter Grehan P6B: Developing CPE Routers based on NetBSD: Fifteen Years of SEIL 107 Masanobu SAITOH and Hiroki SUENAGA P7A: Deploying FreeBSD systems with Foreman and mfsBSD 115 Martin Matuška P7B: Implementation and Modification for CPE Routers: Filter Rule Optimization, IPsec Interface and Ethernet Switch 119 Masanobu SAITOH and Hiroki SUENAGA K3: Modifying the FreeBSD kernel Netflix streaming servers — Scott Long K4: An Overview of Security in the FreeBSD Kernel 131 Dr. Marshall Kirk McKusick P8A: Transparent Superpages for FreeBSD on ARM 151 Zbigniew Bodek P8B: Carve your NetBSD 165 Pierre Pronchery and Guillaume Lasmayous P9A: How FreeBSD Boots: a soft-core MIPS perspective 179 Brooks Davis, Robert Norton, Jonathan Woodruff, and Robert N.
    [Show full text]
  • MASS-MIGRATION of 5000 SERVERS to FOREMAN/KATELLO with BOOTSTRAP.PY Evgeni Golov
    MASS-MIGRATION OF 5000 SERVERS TO FOREMAN/KATELLO WITH BOOTSTRAP.PY Evgeni Golov 1 $ WHOAMI Evgeni Golov Software Engineer at Red Hat ex-Consultant at Red Hat Debian and Grml Developer ♥ FOSS ♥ ♥ automation ♥ 2 SITUATION 10k RHEL (5k RHEL5, 4k RHEL6, 1k RHEL7) most of them subscribed to Satellite5/Spacewalk want to move to Satellite6/Foreman this requires a plan 3 TOOLING Satellite 6.1 (Foreman 1.7, Katello 2.2) this was done about a year ago the learnings also apply to Foreman itself bootstrap.py script for registration of machines to Foreman/Katello at that time not even part of the Katello project mimicks the idea of bootstrap.sh from Spacewalk 4 BOOTSTRAP.PY install katello-ca-consumer RPM subscribe the machine using subscription- manager or rhn-migrate-classic-to- rhsm congure katello-agent congure Puppet 5 STEP 1: EL5?! ain't nobody got time for that just let it bit-rot on the old infra there is an migration to EL6/7 planned anyways (guess who is still up and running today?) no need to care for the old content but also no insight if there are any gotchas 6 STEP 2: SIZE THE INFRASTRUCTURE main VM: 12vCore, 32GB RAM, 1TB ash 6 proxies: 8vCore, 24GB RAM, 500G ash rough setup: no machines connect directly to Foreman no more than 1000 clients per proxy most machines don't do Puppet 7 STEP 3: WAIT FOR FIREWALLS there is always a rewall somewhere and it for sure will make you unhappy request the new rewall rules early and broadly (allow ALL the networks!) 8 STEP 4: DESIGN CONTENT the old setup provided almost only RHEL, apps were delivered
    [Show full text]
  • Red Hat: Collaborative Solutions for Innovative Government
    RED HAT: COLLABORATIVE SOLUTIONS FOR INNOVATIVE GOVERNMENT BROCHURE INDUSTRY OVERVIEW RED HAT FAST FACTS Innovation creates opportunity and challenge. Exciting new technology concepts, such as bimodal IT, • Founded in 1993 digital transformation, containers, cloud computing, and big data, offer multiple avenues for federal agencies to improve operational efficiencies and mission performance, but charting a secure and • Annual revenues exceed $2B affordable path forward is not always clear. Plus, tight budgets leave little room for error. You don’t • Red Hat solutions are being want to get locked into solutions that will limit options or prove expensive to modify once in place, used throughout the federal but neither can you afford to stand still in today’s rapidly evolving IT landscape. government, from processing How can you maximize the benefits of today’s innovative technologies while avoiding the risks, Medicare claims at CMS to including costly vendor lock-in? Red Hat takes the best innovation from the open source commu- handling airplane traffic nity, stabilizes it, and makes it consumable for your mission. Red Hat® open source solutions provide at FAA to enhancing every the security and performance government agencies require, while offering more value per dollar tactical vehicle in the DoD, than proprietary solutions and greater flexibility to evolve with technical and mission requirements. and in all 50 states. As a result, agencies are using Red Hat in all 50 states and throughout the federal government — to process Medicare claims at the Centers for Medicare & Medicaid Services (CMS), handle airplane WHAT WE DELIVER: traffic at the Federal Aviation Administration (FAA), and enhance every tactical vehicle in the • Cloud computing Department of Defense (DoD).
    [Show full text]