satellite 6 user guide - eth z documents/satellite_6_user_guide.pdfsatellite 6 user guide eth zuric...

Satellite 6 User Guide

ID Client Delivery

08.06.2017

pdf generated on July 7, 2017

Satellite 6 User Guide ETH Zurich

Table of Contents

1 Concepts 31.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2 Description of Key Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.2.1 Life Cycle Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2.2 Content View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2.3 Types of Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2.4 Types of Host Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2.5 Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2.6 Activation Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.2.7 Installation Object Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . 61.2.8 Parameter Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2.9 Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2.10 Users and Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.3.1 Manual Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.3.2 Automated Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2 Step by Step 92.1 Environment Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.1.1 Operating System and Templates . . . . . . . . . . . . . . . . . . . . . . 102.2 Boot Process and Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.3 Managing Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.3.1 Managing Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3.2 Collection Membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.4 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4.1 Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4.2 Preparing Puppet Modules . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4.3 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4.4 Updating Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4.5 Host Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 Task Reference 133.1 Create Activation Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.2 Create Subnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.3 Create Hostgroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.4 Create Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.5 Install Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.6 Create Content View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.7 Use Lifecycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4 Troubleshooting 214.1 Enable Reinstallation of Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.2 Enable Errata through Content Views . . . . . . . . . . . . . . . . . . . . . . . 214.3 Enable Build is not Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.4 Host is not Registered after Installation . . . . . . . . . . . . . . . . . . . . . . . 214.5 Error 500 while Installing Host . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

ID Client Delivery – 1 – 08.06.2017


5 Example Code 215.1 Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21



1 Concepts

1.1 Terminology

Activation Key allows hosts to access certain repositoriesChannel collection of repositoriesContent Host a view which gives more information about the host’s softwareContent View a view of repository content in a specific version (used in lifecycle)Generic Image used for new installations of hostsHammer powerful CLI tool for accessing the satelliteHostcollection 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 installationLifecycle usually used for controlled staging like (dev - tst - qss - prd)Location subselection (works like a filter)Manifest used upstream per organization to attach subscriptionsOrganization separating the satellite trough organizationsSyncplan scheduled syncronization of the channelsTasks 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 contentview. Changes like addition or removal of channels are documented by versioning. Systemscan use a life cylce environment called Library, which provides the latest state of updates fora 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 systemor by pushing them from the Satellite GUI.Satellite 5 provided cloning of channels, which could be used to freeze channel contents and toprovide a well defined and tested state of software versions. In Satellite 6 this concept is moreelaborated and, if desired, allows for the definition of several consecutive states, like the oftenused 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 contentview 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 viewassigned always get the same software version, independent of the current states of the softwarechannels used by the view.Every organization has a Default Organization View which cannot be changed – it is not visiblein the list of created content views, it can only be assigned to hosts, host groups and activation



keys. This view always points to the latest content and is not subject to versioning. Thisbehavior 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 thetime the content view was published. To include the latest updates, you have to publish a newminor version.

1.2.3 Types of Hosts

In Satellite 6, the term host is used in two different, but complementary definitions, called hostand 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 comparisonwith Satellite 5.

Host Group bundles hosts, therefore the settings of a host group apply during the installationprocess. All systems in a host group share the same installation parameters, but individualsystems 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 thegroups used in Satellite 5. Host collections consist of content hosts and allow to

ä install software

ä apply erratas



ä manage subscriptions

ä assign lifecycle environments and content views

Systems may be members of several host collections. The initial association with hostcollections 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 tocombine groups with boolean operations has gone, as has the System Set Manager, so youmay 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 anoperating 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 ratherdescribe 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 bedefined in the context of operating systems. However, the parameters evaluated in these scriptscan be redefined in host groups and hosts.A customized OS definition is available: the operating system RedHat 7.3 ETH customized hassome 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)



1.2.6 Activation Key

Activation keys bundle configuration options related to software channel subscriptions, andassociation 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. Theseoptions 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 splitconfiguration facets and reuse them for different host and host groups.Imagine a host collection UpdateAll which is associated to a activation key UpdateKey. Thekey has no other assignments: no subscriptions or product content (channels). If this key isassigned to each host definition, preferably by assigning the key to every host group, all of yoursystems will be member of a collection which allows you to initialize an update process on allsystems you are responsible for.Other keys could be used to initiate updates on subsets of systems, assign basic softwarechannels, 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 operatingsystem assigned.

Host Group

Parameter Partition Table Host

contains many

Operating System

uses

Parameter Partition Table

uses

Templates Partition Table Parameter

Figure 1: Hierarchy of installation objects



1.2.8 Parameter Hierarchy

If we look at the configuration parameters and where we can overwrite settings, the hierarchyis different.

Host Group

Parameter Operating System Partition Table Operating System

overrides

Host

overrides

Parameter Partition Table Operating System

Templates Partition Table Parameter

Figure 2: Hierarchy of parameter overrides

The installation process is controlled by many variables which can be defined on different levelsof the container hierarchy. The evaluation of the parameter values applied to a host differsfrom the container hierarchy:

1. operating systems define installations scripts, parameters and partition tables.

2. host groups use a selected operating system, and may override parameters and partition-ing.

3. hosts may override operating system, parameters and partitioning inherited from hostgroup or operating system definitions.

There are further levels where parameters can be set, but not all are accessible for customers ofthe Satellite. Examples are global objects like locations, which can be configured by the serviceprovider only.

1.2.9 Configuration Parameters

System can be configured by two types of parameters:

Simple parameters are configuration options evaluated in the installation and provisioningscripts. As a consequence, they have no effect after an installation has been completed.

Puppet parameters See section 2.4

Parameters can be accessed and modified either in host or host group configuration screensdirectly, or by using Config Groups.



1.2.10 Users and Roles

User accounts are created in the Satellite system, credentials are then taken from the centralidentity management system LDAPS. Users can be member of user groups, both single usersand groups can be used as owner of a host.Satellite accounts have user roles assigned which allow for two levels of users:

ETH User is the basic role. It allows for all the tasks necessary to prepare activation keyshost objects, host groups and collections, install systems and manage erratas.

ETH Admin adds permissions to maintain infrastructure objects like products and channels,subnets, or kickstart configurations.

User accounts can be valid in more than one organization, but will have the same role level inevery organization.More user roles are available for particular tasks, like managing containers or compute clusters.User management is not accessible to customers yet. Please contact [email protected] for accountrequests.

1.3 Installation

Similarly to the installation process with Satellite 5, you first need a boot medium. There arethree types of installation with three different installation media:

1. Boot ISO without any automatisms

2. Customized boot ISO generated by Satellite 6

3. Generalized boot ISO, fully automatized

1.3.1 Manual Installation

This installation procedure is recommended only for users which have no account on the Satelliteand therefore no access to the GUI.Installation is initiated by booting with a minimal boot ISO and a reference to the packagerepository on the Satellite, or a full OS DVD. System configuration like partitioning or softwareselection has to be done interactively in a GUI. After the installation, registration has to bedone manually. Activation keys may be used to configure further software channels or add thesystem to host collections.

1.3.2 Automated Installation

If a system has been fully registered as a host object, you can use a generic boot ISO. Thisboot disk does not contain any system specific information, it can be used for whatever systemyou intend to install. The Satellite recognizes the calling system regardless of architecture, OSversion or system configuration. By assigning the host object to a host group, and by optionallyoverriding configuration parameters, further customization is possible.For the configuration process to be able to correctly configure the network, the MAC address,IP address and subnet information has to be defined in the host object. Additionally, theDHCP for your network must be configured to deliver a IP address.There is also a boot image for PXE available which has been derived from the general bootISO. TODO offer ways to access.



2 Step by Step

This chapter describes the steps necessary for setting up a single or a group of systems. Thisprocedure is recommended whenever you plan to install more then one system. But even ifyou intend to install just one system: following these steps allows you to easily repeat theinstallation if something goes wrong or you just want to tweak some parameters and rerun theinstallation.

2.1 Environment Preparation

Subnet Make sure the network is definded where the system will belong to. See section 3.2for reference where to create a subnet.

Host group Create a host group if not already done. As long as you don’t use different systemsto test new updates and run productive services, the Library lifecycle environment is thecorrect choice, as is the Default Organization View.

See section 3.3 for reference where to create a host group. This example uses the mostcommon entries for demonstration purposes.

Partioning If you don’t want to use the default partitioning scheme, you may

1. create your own partitioning definitions as objects and reuse them for different in-stallations

2. add a specific partitioning scheme directly in a host definition

An complex example of partitioning has been added in section 5.1.

Lifecycle environment If you need a staged lifecylcle environment, prepare the environmentas described in TODO.

Content view If you don’t have particular requirements for a staged livecycle environment,stick to the Default Organization View. This view will offer you the latest patches withoutthe need to manually propagate a content view to a new version.

Host collection While not mandatory, the use of host collections is recommended. See section1.2.4 for the functionality of host collections.

Activation keys At least one activation key should be prepared. Whether you use one or moreactivation keys depends on your requirements. Your activation key(s) should provide atleast one host collection where the system will be assigned to after the installation.

Parameter Settings Basic variables and Puppet smart parameters are preset with defaultvalues. You have to adopt them if the defaults do not satisfy your needs, in the Host andhost group objects.

Take care that the environment and content view assigned to a activation key match theenvironment and content view used in host groups and hosts. The input field for activationskeys in the host group configuration offers you matching keys, but you also can enter additionalkeys not matching anything. For example, this may be useful for if an additional keys onlytask is to put your host into a certain host collection.



The host group settings, activation keys tab contains an important check you should take careof. The link Reload data will perform a test of the activation keys entered above and determineif the key names are entered correctly and if they resolve to valid subscriptions. For a systemto be registered as desired you should see one or more items in a bullet list. Each of them is akey recognized and used during subsequent content registration. Note that keys used just forassignment to a host collection do not show up in this list, but still will be used as expected.

2.1.1 Operating System and Templates

Operating System is a low level object which bundles general settings used during installationlike

ä operating system, obviously

ä partitioning

ä configurable parameters used in

ä scripts used during bootstrap and installation (templates)

Most of the setting can be overwritten in objects which use an operating system as a buildingblock; see section 1.2.8 for a description of the parameter hierarchy.Templates is a term for used for scripts used during installation of a system. They are theequivalent to kickstart and snippet files used in Satellite 5.Important: while access to templates can be limited to particular organizations, their namesare global. Always prefix own templates with your organization string to prevent name colli-sions, as in ID-BD-myCustomSnippet.If you need to customize templates, probably the script type of primary interest is the provin-sioning template. It performs tasks like

ä network configuration

ä applying the partition table

ä setting keyboard and timezone

ä installing packages

Scripts can be included with the snippet directive which reduces the modification to the maintemplate.

2.2 Boot Process and Installation

Enable system build For an installation, the Satellite must be ready to accept an installationrequest. This is done by activating Build in the host object. See section 3.5 for a guidethrough the interface.

Get boot medium If everything is configured correctly, the click on Build should have re-vealed a menu where installation media are offered. If the MAC address of the system isknown to the DHCP and the correct IP address can be assigned to the system, downloadthe Generic Boot Image and make it accessible to your system to be installed.



If IP address and DNS name are not managed by a MAC address entry in the DNS, youmust use the system specific boot disk which contains the information necessary for acorrect network configuration.

Boot system Boot your system either from boot medium or, in case of PXE, from network.

The boot disk (mounted as boot medium or requested by PXE) loads an iPXE executablewhich either uses the information stored on the boot disk to configure the network interface,or in case of the generic boot disk, uses the DHCP service. Then iPXE HTTP request isissued to the Satellite with the MAC address as argument. This enables the Satellite to choosethe environment configured for the client system. The installation process will now take placewithout the need for any further manual intervention.Supposed one of the activation keys is connected to a subscription, any erratas which are partof the content view in use are applied:

ä Systems which belong to the Default Organization View will receive the latest updates.

ä Systems assigned to a versioned content view will get exactly the updates defined in thatcontent view.

Finally, the Katello agent will be installed. This is the equivalent to the osad process usedwith Satellite 5: a daemon which communicates with the server, performs installation tasksand reports back which packages and erratas are installed.After a successful installation, the state of the host object changes back to its normal state.To perform another installation, you must put it into build mode again. As a consequence, theSatellite recognizes repeated installations of the same system, and the licensing subscriptionwill be reused.

2.3 Managing Systems

2.3.1 Managing Software

The differences to the errata management provided by Satellite 5 are marginal. Erratas canbe pushed for single content hosts or for several hosts by using host collections. Similarly, newsoftware packages can be installed for a content host, or for a complete host collection.

2.3.2 Collection Membership

Systems can be assigned to multiple host collections, primarily during the installation process,but also later. Here are some example how host collections may be used:

House keeping Group systems of the same type in collections, i.e. web servers. If you wantto install new software later, using collections makes sure all systems are affected.

Patch job invocation a collection Update contains all systems you regularly want to update.If combined with versioned content views, each systems gets exactly the updates it issupposed to get.

Life cycle management Add systems of the same stage (testing, production etc.) to corre-sponding collections.



2.4 Configuration

Currently the only configuration management system supported directly in Satellite is Puppet.Ansible is announced, and of course are you free to use any system independently of Satellite.Some modules will be prepared and ready to use, but you can also use your own modules.The following chapters will discuss Puppet.

2.4.1 Concepts

Puppet modules are imported into Satellite, where they are bundled and versioned. Hosts geta set of well defined modules applied, using different versions for different hosts is possible.Satellite can extract parameters from templates and present them in the web GUI for configu-ration.Despite the management of Puppet modules takes place in the Content menu, configurationsare applied to systems in the Host section, not the Content Host section.If puppet modules are assigned to a host, the puppet agent will be installed automatically.Make sure the Red Hat Satellite 6 Tools RPMs repository is available for the host.

2.4.2 Preparing Puppet Modules

A description of how to bring modules into Satellite can be found in the Red Hat documenta-tion1. The guide describes how to create a Puppet module, upload it into a product or pull itfrom a repository. There is a helper command pulp-puppet-module-builder which allows you tocreate a module repository directly from a git repository, see the guide for more information.

2.4.3 Parameters

Go to Environments and on the environment you want to use click on Classes. Select a class,you get a list of all parameters defined for this class. Make sure

ä on tab Puppet Class, the host groups you want to use this classe are assigned

ä on tab Smart Class Parameter, Default behavior, the option ”Override” is selected forevery paramater you want to be able to customize in host groups or single hosts

2.4.4 Updating Modules

The update cycle consists of

1. Create a new module version

2. Update your module repository

3. Sync the repository to the Satellite

4. Publish a new version of the content view

Don’t forget to update the module version in metadata.json, or it will not be recognized as achange!

1https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html-single/puppet_

guide/


https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html-single/puppet_guide/

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html-single/puppet_guide/


2.4.5 Host Group

As in general it is recommended to use Host Groups to assign Puppet parameters to hosts. Hostswill inherit parameter which have been configured to host groups. While basic configurationsettings like timezone or console keyboard layout are well suited for host/hostgroup basedconfiguration, more flexibility can be achieved with Config Groups.Set the input fields

ä Content Source

ä Puppet CA

ä Puppet Master

to the Satellite capsule used by your systems (usually the main Satellite).Don’t use a puppet content view in the Content View field! You must use a content view whichhas software packages used for the installation, this will usually be Library.

2.4.6 Config Groups

This function allows you to add functionality based on puppet modules to systems. You canadd puppet modules (with or without class parameters) to a config group. After at least oneconfig group has been created, the Puppet Classes tab of a host group or a single host will allowyou to add config groups.

3 Task Reference

The following chapters give you an overview over basic tasks in Satellite 6

ä 3.1 Create Activation Key

ä 3.2 Create Subnet

ä 3.3 Create Hostgroup

ä 3.4 Create Host

ä 3.5 Install Host

ä 3.6 Create Contentview

ä 3.7 Lifecycle



3.1 Create Activation Key

Login to https://id-sat-prd.ethz.ch ä Content ä Activation Key ä New Activation Key

Activation Keys

Name ORG-activation-key

Host Limit Unlimited hosts: �

Environment � Library

Content View Default Organization View

Subscription ä Add

Puppet Forge

� 1 0 out of ...

EPEL 7

� 1 0 out of ...

Red Hat Enterprise Linux Academic Site Subscription...

� 1 0 out of ...

Product Content

- Red Hat Enterprise Linux Server

Red Hat Satellite Tools 6.2 (For RHEL 7 Server) (RPMs)

Enabled? Override to Yes

Red Hat Enterprise Linux 7 Server (Kickstart)


- Puppet Forge

Puppet Forge


- Product XXX

Channel XXX


Table 1: Create Activation Key


https://id-sat-prd.ethz.ch


3.2 Create Subnet

Login to https://id-sat-prd.ethz.ch ä Infrastructure ä Subnets ä New Subnet

Subnet

Name * mysubnet

Network address * xxx.xxx.xxx.0

Network mask * 255.255.255.x

Gateway address xxx.xxx.xxx.1

Primary DNS server 192.168.98.12

IPAM None

Boot mode Static

Domains

Domain � ethz.ch

Locations

Locations Your Location

Organizations

Organization Your Organization

Table 2: Create Subnet




3.3 Create Hostgroup

Login to https://id-sat-prd.ethz.ch ä Configure ä Host groups ä New Host Group

Host Group

Name * myhostgroup

Lifecycle Environment Library


Network

Domain ethz.ch

Operating System

Architecture x86 64

Operating System RedHat 7.3

Media Selection All Media

Partition Table Kickstart default

Root Password * * * * *

Locations

Locations Your Location

Organizations

Organization Your Organization

Table 3: Create Hostgroup




3.4 Create Host

Login to https://id-sat-prd.ethz.ch ä Hosts ä All Hosts ä New Host

Host

Name * id-host-01

Organization * Your Organization

Location * Your Location

Host Group Webserver

Lifecycle Environment Library


Interfaces

MAC address 00:00:00:00:00:00

DNS name id-host-01

Domain ethz.ch

Subnet ID Subnet (xxx.xxx.xxx.0/24)

IP address 129.132.179.xxx

Table 4: Create Host




3.5 Install Host

New Host Installation

1. Make sure you’ve created the host in the webinterface.

2. Download generic image [ID portal].

3. Boot new machine with generic ISO and let the installation run through.

Reinstallation of Host

1. Login to https://id-sat-prd.ethz.ch ä Hosts ä All Hosts ä select your host ä

Build

2. Insert generic boot image from [ID portal].

3. Start automated installation.In case that’s not possible:

ä select your host ä Edit ä Manage

4. Repeat steps above.




3.6 Create Content View

Create content views only if you want to manage package versions manually. If you intend touse the latest versions anyway, use the built in default organization view. Otherwise:Login to https://id-sat-prd.ethz.ch ä Content ä Content View ä + Create New View

Name * Rhel7 Web

Label * Rhel7 Web

Select all repos which should to be included:Yum Content ä Repositories ä Add

� Name Description ...

� EPEL 7 ... ...

� Red Hat Enterprise Linux Server ...

... ... ... ...

+ Add Repositories

You may want to enable errata to be installed.

Yum Content ä Filters ä + New Filter

Name * enable errata

Content Type * Errata - By Date and Type

Inclusion Type * Include

Define Start Date ä Save ä Publish New Version

Table 5: Create Content View




3.7 Use Lifecycle

Login to https://id-sat-prd.ethz.ch ä Content ä Lifecycle Environment ä + New En-vironment Path

Name * DEV

Label * DEV

Description develop

content ä Lifecycle Environment ä + Add New Environment

Name * TST

Label * TST

Description test

Repeat steps for QSS and PRD.

Table 6: Use Lifecycle




4 Troubleshooting

4.1 Enable Reinstallation of Hosts

For reinstallation of host, you need to enable build via the webinterface. Hostgroups are kindof templates for the reinstallation of new hosts and are not associated by default for contenthosts.

4.2 Enable Errata through Content Views

Add filter in content view where you can allow all errata to be installed.

4.3 Enable Build is not Available

If your host was orginally build on Satellite 5, you need to do following:Host ä Edit ä Manage (top right)You can now allow building again.

4.4 Host is not Registered after Installation

To have a complete self-installation you need to asign a hostgroup with an activation key tothe host.

4.5 Error 500 while Installing Host

If your error looks something likeGET /unattended/provision?token=7d6a15c0-903a-4338-843f-dadb88c2208a&static=yes¨you need to set a subnet in the interface section of your host.

5 Example Code

5.1 Partitioning

clearpart --drives=hda,hdc

zerombr

# Raid 1 IDE config

part raid.11 --size 1000 --asprimary --ondrive=hda



part raid.14 --size 8000 --ondrive=hda

part raid.15 --size 16384 --grow --ondrive=hda

part raid.21 --size 1000 --asprimary --ondrive=hdc



part raid.24 --size 8000 --ondrive=hdc

part raid.25 --size 16384 --grow --ondrive=hdc

# You can add --spares=x



raid / --fstype xfs --device root --level=RAID1 raid.11 raid.21

raid /safe --fstype xfs --device safe --level=RAID1 raid.12 raid.22

raid swap --fstype swap --device swap --level=RAID1 raid.13 raid.23

raid /usr --fstype xfs --device usr --level=RAID1 raid.14 raid.24

raid pv.01 --fstype xfs --device pv.01 --level=RAID1 raid.15 raid.25

# LVM configuration so that we can resize /var and /usr/local later

volgroup sysvg pv.01

logvol /var --vgname=sysvg --size=8000 --name=var

logvol /var/freespace --vgname=sysvg --size=8000 --name=freespacetouse

logvol /usr/local --vgname=sysvg --size=1 --grow --name=usrlocal

This example is taken from the Red Hat Linux installation manual.


satellite 6 user guide - eth z documents/satellite_6_user_guide.pdfsatellite 6 user guide eth zuric...

Documents