Show Table of Contents Hide Table of Contents English 日本語 English Multi-page HTML Single-page HTML PDF ePub Planning for Red Hat Satellite 6I. Satellite 6 Architecture1. Introduction to Red Hat Satellite 61.1. System Architecture1.2. System Components1.3. Supported Usage1.4. Supported Client Architectures1.4.1. Content Management1.4.2. Host Provisioning1.4.3. Configuration Management2. Capsule Server Overview2.1. Capsule Features2.2. Capsule Types2.3. Capsule Networking3. Organizations, Locations, and Life Cycle Environments3.1. Organizations3.2. Locations3.3. Life Cycle Environments4. Host Grouping Concepts4.1. Host Group Structures5. Provisioning Concepts5.1. PXE Booting5.1.1. PXE Sequence5.1.2. Requirements5.2. Kickstart5.2.1. Workflow6. Content Delivery Network StructureII. Satellite 6 Deployment Planning7. Deployment Considerations7.1. Satellite Server Configuration7.2. Satellite Server with External Database7.3. Locations and Topology7.4. Content Sources7.5. Content Life Cycle7.6. Content Deployment7.7. Provisioning7.8. Role Based Authentication7.9. Additional Tasks8. Common Deployment Scenarios8.1. Single Location8.2. Single Location with Segregated Subnets8.3. Multiple Locations8.4. Disconnected Satellite8.5. Capsule with External ServicesA. Technical Users Provided and Required by SatelliteB. Glossary of TermsLegal Notice Planning for Red Hat Satellite 6 Red Hat Satellite 6.6Planning Satellite 6 DeploymentRed Hat Satellite Documentation Teamsatellitefirstname.lastname@example.orgLegal NoticeAbstract This document explains architecture concepts of Red Hat Satellite 6 and provides recommendations for your deployment planning. I. Satellite 6 Architecture Where did the comment section go?Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.