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 . 21 4.4 Host is not Registered after Installation . 21 4.5 Error 500 while Installing Host . 21 ID Client Delivery { 1 { 08.06.2017 Satellite 6 User Guide ETH Z¨urich 5 Example Code 21 5.1 Partitioning . 21 ID Client Delivery { 2 { 08.06.2017 Satellite 6 User Guide ETH Z¨urich 1 Concepts 1.1 Terminology Activation Key allows hosts to access certain repositories Channel collection of repositories Content Host a view which gives more information about the host's software Content View a view of repository content in a specific version (used in lifecycle) Generic Image used for new installations of hosts Hammer powerful CLI tool for accessing the satellite Hostcollection control groups of hosts with actions, i.e update all erratas (freely selective) Hostgroup all similar hosts belong in one host group, a template for installation Lifecycle usually used for controlled staging like (dev - tst - qss - prd) Location subselection (works like a filter) Manifest used upstream per organization to attach subscriptions Organization separating the satellite trough organizations Syncplan scheduled syncronization of the channels Tasks satellite handles jobs with workers through tasks 1.2 Description of Key Elements 1.2.1 Life Cycle Management Satellite 6 emphasises the aspects of life cycle management much more than Satellite 5 did. Satellite 6 bundles the content of software repositories and configuration settings to a content view. Changes like addition or removal of channels are documented by versioning. Systems can use a life cylce environment called Library, which provides the latest state of updates for a given software channel. The behaviour is very similar to the default practice in Satellite 5: whenever updates are available, they can be installed by either pulling from the client system or by pushing them from the Satellite GUI. Satellite 5 provided cloning of channels, which could be used to freeze channel contents and to provide a well defined and tested state of software versions. In Satellite 6 this concept is more elaborated and, if desired, allows for the definition of several consecutive states, like the often used steps of testing { quality assurance { production. 1.2.2 Content View A content view is a collection of sources for a managed system. Items belonging to a content view are ® software channels ® configuration packages The state of the collection is subject to versioning. To make changed packages visible to clients, a new version of the content view has to be published. Systems with the same content view assigned always get the same software version, independent of the current states of the software channels used by the view. Every organization has a Default Organization View which cannot be changed { it is not visible in the list of created content views, it can only be assigned to hosts, host groups and activation ID Client Delivery { 3 { 08.06.2017 Satellite 6 User Guide ETH Z¨urich keys. This view always points to the latest content and is not subject to versioning. This behavior corresponds to the standard use case in Satellite 5, if no cloned channels were used. Keep in mind that versioned content views only provide updates which were available at the time the content view was published. To include the latest updates, you have to publish a new minor version. 1.2.3 Types of Hosts In Satellite 6, the term host is used in two different, but complementary definitions, called host and content host. Host is the term for basic definitions mainly used during system installation and provisioning, including: ® operating system and lifecycle environment ® disk partitioning ® network interface information ® provisioning parameters: system language, console keyboard layout ® activation keys (must be set as key { value pair, no GUI available) Content Host is used in the context of package management. Typical management tasks are ® package installation ® errata management 1.2.4 Types of Host Groups As a consequence of the two types of hosts, groups of hosts have changed too in comparison with Satellite 5. Host Group bundles hosts, therefore the settings of a host group apply during the installation process. All systems in a host group share the same installation parameters, but individual systems may have parameters assigned which override group parameters. Examples are ® initial lifecycle environment and content view ® subnet and domain ® operating system, partitioning and root password ® activation keys Host group membership is exclusive, a host may not be member of more than one group. Activation keys are important for further configuration steps, see below. Host Collection is a group construct for actions during the lifetime of systems, similar to the groups used in Satellite 5. Host collections consist of content hosts and allow to ® install software ® apply erratas ID Client Delivery { 4 { 08.06.2017 Satellite 6 User Guide ETH Z¨urich ® manage subscriptions ® assign lifecycle environments and content views Systems may be members of several host collections. The initial association with host collections is done by the use of activation keys. Examples for host collections are systems of ® same functionality (all web servers, all cluster nodes etc.) ® same lifecycle state (testing, production) ® same customer, if you manage systems in behalf of others Host collections are similar to system groups in Satellite 5. However the possibility to combine groups with boolean operations has gone, as has the System Set Manager, so you may have to create more host collections in Satellite 6 than Satellite 5 system groups. 1.2.5 Operating System An operating system object defines a basic set of parameters which are used to install a host. Every host or host group must have such an object assigned. Some of the elements of an operating system are obvious: ® the OS family (RHEL, Fedora etc.) ® OS version ® architecture (32 or 64 bit) Other elements we usually do not associate directly with the term operating system, they rather describe how the installation will be performed: ® disk partitioning ® installation medium ® scripts for controlling the setup from initial PXE to final provisioning: templates ® parameters to customize installation and configuration All of these configuration elements are preset in an operating system object, but can be over- written in host groups or individual hosts. Except for the templates: such scripts can only be defined in the context of operating systems. However, the parameters evaluated in these scripts can be redefined in host groups and hosts. A customized OS definition is available: the operating system RedHat 7.3 ETH customized has some configurable parameters: ® console keyboard layout: keyboard defaults to sg-latin1 ® time zone: time-zone defaults to Europe/Zurich ® SSH access from Satellite: allow sat root access defaults to blank (off) ID Client Delivery { 5 { 08.06.2017 Satellite 6 User Guide ETH Z¨urich 1.2.6 Activation Key Activation keys bundle configuration options related to software channel subscriptions, and association to host collections. They can be used as options for host and host group objects, or for registration on the Satellite for systems installed manually. Activation keys perform several important steps at the end of an installation: ® subscribing to the license management ® attaching software channels ® assigning to one or more host collections If used for manual registration, they also set lifecylce environments and content views. These options are ignored if the installation has been prepared on the satellite, the mandatory con- figuration options in hosts and host groups take precedence. Keep in mind that you can use several activation key for a host. This allows you to split configuration facets and reuse them for different host and host groups. Imagine a host collection UpdateAll which is associated to a activation key UpdateKey. The key has no other assignments: no subscriptions or product content (channels). If this key is assigned to each host definition, preferably by assigning the key to every host group, all of your systems will be member of a collection which allows you to initialize an update process on all systems you are responsible for. Other keys could be used to initiate updates on subsets of systems, assign basic software channels, or add optional channels. 1.2.7 Installation Object Hierarchy Up to here, we have a clear hierarchy: host groups contain hosts, and hosts have an operating system assigned.