10 Steps to Build an SOE How Red Hat Satellite 6 Supports Setting up a Standard Operating Environment Dirk Herrmann Principal Software Engineer Benjamin Kruell Senior Domain Architect Version 1.0 19th August 2015 100 East Davie Street Raleigh NC 27601 USA Phone: +1 919 754 3700 Phone: 888 733 4281 Fax: +1 919 754 3701 PO Box 13588 Research Triangle Park NC 27709 USA Linux is a registered trademark of Linus Torvalds. Red Hat, Red Hat Enterprise Linux and the Red Hat "Shadowman" logo are registered trademarks of Red Hat, Inc. in the United States and other countries. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. UNIX is a registered trademark of The Open Group. Intel, the Intel logo and Xeon are registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. VMware, VMware Tools, vSphere, vCetner, and ESXi are registered trademarks of VMware, Inc. Docker and the Docker logo are trademarks or registered trademarks of Docker, Inc. ITIL® is a Registered Trade Mark of AXELOS Limited. All other trademarks referenced herein are the property of their respective owners. © 2015 by Red Hat, Inc. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, V1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/). The information contained herein is subject to change without notice. Red Hat, Inc. shall not be liable for technical or editorial errors or omissions contained herein. Distribution of modified versions of this document is prohibited without the explicit permission of Red Hat Inc. Distribution of this work or derivative of this work in any standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from Red Hat Inc. The GPG fingerprint of the [email protected] key is: CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E www.redhat.com ii [email protected] Executive Summary Over time the complexity of IT infrastructures increases. Businesses that used to run on a small number of physical servers a decade ago have had to add more servers to grow and keep up with new technology. The advent of virtualization adds another layer of complexity to an already complicated, multi-vendor environment. The result is an environment that is difficult to navigate and control and increasing labor costs. With labor costs making up nearly 60% of overall IT infrastructure costs, the price of complexity adds up quickly. Standardized operating environments help businesses operate effectively and efficiently. Red Hat solutions provide additional benefits, such as improved Total Cost of Ownership (TCO), better IT productivity, and increased agility, which all drive your business forward. Red Hat Enterprise Linux with Red Hat Satellite provides an ideal platform for standardized operating environments with lower TCO and greater IT efficiency and productivity. We can improve your bottom line and increase your business' agility and competitiveness. This solution guide provides an example of an implementation based on a sample customer scenario that includes a distributed datacenter topology, sample applications, and an example of an IT organization and its roles. It is an end-to-end story starting with a fresh installation of Satellite 6 and a step-by-step configuring of all necessary Satellite 6 entities, up to an up-and-running infrastructure with servers and applications and their ongoing maintenance. Most parts of the setup can be automated with the powerful hammer command-line interface, which is documented in this reference architecture. Nearly all Satellite entities are covered. For the most critical ones (content views, host groups, and lifecycle environments), multiple scenarios are illustrated. By using this comprehensive documentation, customers can configure Red Hat Satellite 6 in a way that best fits their needs. The following sections provide a brief overview of each of the ten steps and include the core content items, the Satellite 6 entities covered, and the achievements for each step. Step 1: Set up your System Management Infrastructure. Perform a basic configuration of Sat6 and its embedded Capsule. We also create an organization and import the subscription manifest. Corresponding Satellite 6 Entities: Satellite 6 Installer, Organization, and Subscription Manifest Outcome: You now have an up-and-running system management infrastructure and your Red Hat subscription manifest uploaded and activated. Step 2: Map your Location and Datacenter Topology. Configure two datacenters with different underlying virtualization platforms (RHEV and RHELOSP), one with a DMZ. [email protected] III www.redhat.com Corresponding Entities: Capsules and their corresponding Locations, Subnets, and Domains. Outcome: You now have three different Capsules to manage the three different locations. Step 3: Define Your Definitive Media Library Content. Import software content into Satellite 6, focusing on different software entry points and formats. The content includes RPM packages and Puppet modules for Red Hat, third-party, and custom applications. Corresponding Entities: Products, Repositories, Third-party and custom GPG Keys and Sync Plans. Outcome: You have defined multiple custom and third-party Products and Repositories, successfully imported their corresponding content, and enabled continual updates of content using synchronization plans. Step 4: Define your Content lifecycle. Learn the differences between content views and composite content views. Learn how to use them and lifecycle environments to match your particular scenario. Outcome: You have created lifecycle environments and their paths, which allow you to segregate the duties of the different stack layers (Example: the OS and the applications running on top of it) and to create independent release cycles for each of them. Step 5: Define your Core Build. Define your OS-deployment (core build) configuration and its corresponding content items. Create, publish, and promote content views using sample Puppet modules, Config Groups and Content Views. Outcome: You have created two different core-build (OS) definitions for applications running on top of the OS. The core build consists of Red Hat Enterprise Linux, third-party packages, and some sample Puppet modules used to make the core build definition more flexible. Step 6: Define Your Application Content. Learn about application layer content views (profiles). Learn how to assemble them with the Core Build content views from Step 5. You can also learn about roles and profiles and the separation of responsibilities between the OS and applications. Corresponding Entities: Sample Puppet modules for roles and profiles, Config Groups and Composite Content Views. Outcome: You now have 5 different applications, including some common infrastructure services and a two-tier web application. Step 7: Automate your provisioning. Configure the automated provisioning to deploy the composite content views created earlier. Learn about different scenarios for host groups and enhanced provisioning that uses dynamic partition tables and Foreman hooks. Corresponding Entities: PXE & Boot ISO, Provisioning Templates, Host Groups & Activation Keys, Global Parameters & Smart Class Parameters, and Foreman Hooks www.redhat.com iv [email protected] Outcome: You have configured all entities required to provision new servers and to deploy the composite content views created earlier by using Satellite 6 provisioning templates and parameters. Step 8: Map your IT organization and roles to your Satellite setup. Map typical IT organizations and roles to Satellite 6 roles and the RBAC model. Corresponding Entities: Users & User Groups, Roles and RBAC (roles, permissions, filters). Outcome: You have 5 sample roles that reflect the typical roles of a two-dimensional responsibility matrix. This matrix is used to separate responsibilities and to reduce the complexity of visible entities in the UI. Step 9: Manage the Content Lifecycle Continuously. Manage the Satellite 6 content lifecycle, including errata management, content view update operations, and puppet module changes. Corresponding Entities: Errata Management, including Errata notification emails, Content Dashboard and Incremental Updates. Outcome: You know how to execute different content update scenarios and the new errata management features of Satellite 6.1. Step 10: Automate and extend your setup outlines possible enhancements (based on the setup chosen in earlier steps). Some examples include: Importing existing hosts, Using the host discovery features, Using Satellite 6 to support various IT processes. Outcome: You have some ideas for enhancing the setup created in the earlier steps of this document. [email protected] v www.redhat.com Table of Contents Executive Summary.......................................................................................... III About this Document.......................................................................................... 1 Target Audience...................................................................................................................... 1 ACME as a customer (and content) journey.......................................................................... 2 Comments and Feedback...................................................................................................... 2 Staying In Touch....................................................................................................................