Red Hat Training
A Red Hat training course is available for Red Hat Satellite
Provisioning Guide
A guide to provisioning physical and virtual hosts from Red Hat Satellite servers.
Edition 1
Abstract
Chapter 1. Introduction to Provisioning Using Red Hat Satellite
1.1. Creating a Red Hat Enterprise Linux Host
1.2. Setting up the Network Topology
- Hostname: satellite.example.org
- IP address = 172.17.13.2
- Netmask: 255.255.255.0
1.3. Registering and Configuring the Host
1.3.1. Registering to Red Hat Subscription Management
subscription_manager register
command to register your Satellite:
# subscription-manager register Username: demouser Password: The system has been registered with ID: 541084ff2-44cab-4eb1-9fa1-7683431bcf9a
1.3.2. Identifying the Satellite Subscription
# subscription-manager list --all --available Subscription Name: Red Hat Satellite Provides: Oracle Java (for RHEL Server) Red Hat Satellite 6 Beta Red Hat Enterprise Linux Server Red Hat Satellite Red Hat Enterprise Linux Load Balancer (for RHEL Server) SKU: MCT0370 Pool ID: 8a85f9874152663c0541943739717d11 Available: 3 Suggested: 1 Service Level: Premium Service Type: L1-L3 Multi-Entitlement: No Ends: 10/07/2014 System Type: Physical
Important
# subscription-manager attach --pool=8a85f9874152663c0541943739717d11 Successfully attached a subscription for: Red Hat Satellite
# subscription-manager list --consumed +-------------------------------------------+ Consumed Subscriptions +-------------------------------------------+ Subscription Name: Red Hat Satellite Provides: Red Hat Satellite Red Hat Enterprise Linux Server Red Hat Software Collections (for RHEL Server) Red Hat Satellite Beta Red Hat Satellite 6 Beta Red Hat Software Collections Beta (for RHEL Server) Red Hat Satellite Capsule Beta Red Hat Enterprise Linux Load Balancer (for RHEL Server) Red Hat Satellite with Embedded Oracle Red Hat Satellite Capsule Red Hat Enterprise Linux High Availability (for RHEL Server) SKU: MCT0370 Contract: 10293569 Account: 5361051 Serial: 1653856191250699363 Pool ID: 8a85f9874152663c0541943739717d11 Active: True Quantity Used: 1 Service Level: Premium Service Type: L1-L3 Status Details: Starts: 10/08/2013 Ends: 10/07/2014 System Type: Physical
1.3.3. Configuring Repositories
# subscription-manager repos --disable=* # subscription-manager repos --enable rhel-6-server-rpms \ --enable rhel-server-rhscl-6-rpms --enable rhel-6-server-satellite-6.0-rpms
1.3.4. Installing Satellite 6
# yum install katello
Chapter 2. Configuring Red Hat Satellite Services
2.1. Configuring DNS, DHCP, and TFTP
named
) to provide authoritative DNS services for the example.org
domain and the 172.17.13.x subnet. This requires setting up a DNS zone for forward lookups, which will be contained in the example.org
zone file. Additionally, a DNS zone for reverse lookups will be created for the 172.17.13.x subnet, which will be contained in the 13.17.172.in-addr.arpa
reverse zone file. This ensures that hosts provisioned from Satellite use the correct name resolution parameters. This section also describes how to configure the TFTP proxy so that hosts can boot using PXE.
- Have access to IP addresses in the range 172.17.13.100 to 172.17.13.150 for DHCP.
- Use the Satellite (
satellite.example.org
at 172.17.13.2) for DNS. - Receive a
pxelinux.0
file from Satellite (satellite.example.org
at 172.17.13.2) to enable PXE-booting. - Have host names of
hostname.example.org
, where hostname is configured when the host is provisioned.
Important
2.1.1. Satellite Configuration Options
katello-installer
command uses Puppet; consequently, it will install additional packages (bind, dhcp, xinetd, and so on) and configure them to add the requested functionality.
katello-installer --help
.
Table 2.1. Satellite Configuration Options
Option
|
Description
|
Value
|
---|---|---|
--foreman-admin-username | The user name for the initial administrator. | (User specified) |
--foreman-admin-password | The password for the initial administrator. | (User specified) |
--capsule-dns | Enable DNS proxy capability. | yes |
--capsule-dns-interface | Which interface named should listen on. | eth0 |
--capsule-dns-zone | The Forward DNS zone that the Satellite will host. | example.org |
--capsule-dns-forwarders | The DNS server that unknown queries are forwarded to. | 172.17.13.1 |
--capsule-dns-reverse | The Reverse DNS zone the Satellite hosts. This is usually the first three octets of the IP address (172.17.13) reversed, and appended with ".in-addr.arpa". | 13.17.172.in-addr.arpa |
--capsule-dhcp | Enable DHCP proxy capability. | yes |
--capsule-dhcp-interface | The interface that DHCP listens on. | eth0 |
--capsule-dhcp-range | The range of IP addresses to issue to clients. | 172.17.13.100 172.172.13.150 |
--capsule-dhcp-gateway | The default gateway IP to issue to clients. | 172.17.13.1 |
--capsule-dhcp-nameservers | The host that the clients should use for name resolution. This should be configured with the Satellite's IP in this deployment model. | 172.17.13.2 |
--capsule-tftp | Enable TFTP proxy capability. This is needed to PXE boot the clients. | yes |
--capsule-tftp-servername | Set the TFTP host name. Set this to match the server's host name (satellite.example.org). | $(hostname) |
--capsule-puppet | Enable the Puppet Master. | yes |
--capsule-puppetca | Enable the Puppet CA. | yes |
2.1.2. Configuring Satellite Services
katello-installer
command as root, using the specified options to configure the required services on the Satellite server. Remember to substitute your desired administrator user name and password.
Important
- If you have already installed Satellite using the instructions in the Installation Guide, do not include the
--foreman-admin-username
and--foreman-admin-password
options in the following command. - If you do not specify the administrator user name and password, the default user
admin
is created, and the password is automatically generated. The credentials are displayed at the end of the installation process. Make a note of this password. You can also retrieve the password fromadmin_password
parameter in the/etc/katello-installer/answers.katello-installer.yaml
file.
katello-installer \ --foreman-admin-username admin-username \ --foreman-admin-password admin-password \ --capsule-dns true \ --capsule-dns-interface eth0 \ --capsule-dns-zone example.org \ --capsule-dns-forwarders 172.17.13.1 \ --capsule-dns-reverse 13.17.172.in-addr.arpa \ --capsule-dhcp true \ --capsule-dhcp-interface eth0 \ --capsule-dhcp-range "172.17.13.100 172.17.13.150" \ --capsule-dhcp-gateway 172.17.13.1 \ --capsule-dhcp-nameservers 172.17.13.2 \ --capsule-tftp true \ --capsule-tftp-servername $(hostname) \ --capsule-puppet true \ --capsule-puppetca true
katello-installer
displays the status of the installation.
Success! * Katello is running at https://satellite.example.org Default credentials are 'admin:*******' * Capsule is running at https://satellite.example.org:9090 * To install additional capsule on separate machine continue by running:" capsule-certs-generate --capsule-fqdn "$CAPSULE" --certs-tar "~/$CAPSULE-certs.tar" The full log is at /var/log/katello-installer/katello-installer.log
2.2. Associating Objects with the Default Organization and Location
Procedure 2.1. To Specify the Default Location:
- On the main menu, click Administer → Locations and then click
Default_Location
in the Name column. - Click Organizations to display the list of organizations.
- Click
Default_Organization
to add it to the Selected items list, and then click Submit.
Procedure 2.2. To Specify the Default Organization:
- On the main menu, click Administer → Organizations and then click
Default_Organization
in the Name column. - Click Locations to display the list of available locations.
- Click
Default_Location
to add it to the Selected items list, and then click Submit.
Procedure 2.3. To Associate the Domain with the Default Organization:
- On the main menu, click Infrastructure → Domains to open the Domains screen.
- Click
example.org
in the Description column. This opens the Edit Domain screen where you can update the details of the domain. - On the Domain tab, change the DNS domain to reflect the host name of the Satellite.
- Set the DNS Capsule value to the Satellite server.
- On the Locations tab, click Default_Location to add it to the Selected items list. This associates the domain with the default location.
- On the Organizations tab, click Default_Organization to add it to the Selected items list. This associates the domain with the default organization.
- Click Submit to apply your changes.
Procedure 2.4. To Select the Default Subnet:
- On the main menu, click Infrastructure → Subnets.
- Click New Subnet and then complete the following information. Remember to update the details to suit your own deployment:
- Name: Provisioning_Net
- Network address: 172.17.13.0
- Network mask: 255.255.255.0
- Gateway Address: 172.17.13.1
- Primary DNS Server: 172.17.13.2
- Secondary DNS Server: Leave blank
- Start of IP Range: 172.17.13.100
- End of IP Range: 172.17.13.150
- VLAN ID: Leave blank
- Click Submit.
- Click Provisioning_Net to edit the subnet.
- On the Domains tab, select example.org
- On the Capsules tab, change the DNS, DHCP, and TFTP capsules to reflect the host name of the Satellite.
- On the Locations tab, select Default_Location under All items to associate the domain with the default location.
- On the Organizations tab, select Default_Organization under All items to associate the domain with the default organization.
Procedure 2.5. To Associate Installation Media with Organizations and Locations:
- On the main menu, click Hosts → Installation Media
- In the Name column, click the name of the media that you want to use.
- On the Locations tab, add the required location to the list of selected items.
- On the Organizations tab, add the required organization to the list of selected items, and then click Submit.
Chapter 3. Importing Subscriptions and Synchronizing Content
3.1. Creating a Manifest
Procedure 3.1. To Create a Manifest for Satellite 6:
- Navigate to access.redhat.com and click SUBSCRIPTIONS on the main menu.
- In the Red Hat Subscription Management section, under Subscription Management Applications, click Satellite.
- Locate the system for which you need to create a manifest. Ensure you select the correct version.
- For each subscription that you want to attach, select the check box for that subscription, and specify the quantity of subscriptions to attach.
- Click Attach Selected.
Note
It can take several minutes for all the subscriptions to attach. Refresh the screen every few minutes until you receive confirmation that the subscriptions are attached. - After the subscriptions have been attached, click Download Manifest and save the manifest file to a known location.
3.2. Uploading a Manifest to your Satellite Server
Procedure 3.2. To Upload a Manifest to your Satellite Server:
- If you have not already selected the correct Organization, click Any Context → Any Organization → Default_Organization.
- Click Content → Red Hat Subscriptions.
- Click Manage Manifest to open the Subscriptions page.
- Click Browse to select a suitable manifest, and then click Open.
- Click Upload to upload the manifest to the Satellite server.
3.3. Enabling Red Hat Repositories
- Red Hat Enterprise Linux 6 Server (Kickstart): This allows Satellite to kickstart a host. This is roughly analogous to a Satellite 5 "kickstart tree."
- Red Hat Enterprise Linux 6 Server (RPMs): This provides ongoing content and errata. This is roughly analogous to the Satellite 5 "rhel-x86_64-server-6" channel.
- Red Hat Enterprise Linux 6 Server - Satellite Tools (RPMs): This provides supporting software, such as Puppet and katello-agent. This is roughly analogous to the Satellite 5 "rhn-tools-rhel-x86_64-server-6" channel.
Procedure 3.3. To Enable Red Hat Repositories:
- Select Content → Red Hat Repositories.
- On the Kickstarts tab, navigate to Red Hat Enterprise Linux Server → Red Hat Enterprise Linux 6 Server (Kickstart) and select the Red Hat Enterprise Linux 6 Server Kickstart x86_64 6.5 (or later) repository.
Important
Do NOT select the 6Server Kickstart repository; future versions of Satellite hide these unnecessary Kickstart repositories. - On the RPMs tab, navigate to Red Hat Enterprise Linux Server → Red Hat Enterprise Linux 6 Server (RPMs) and select the Red Hat Enterprise Linux 6 Server RPMs x86_64 6Server repository.
- On the RPMs tab, navigate to Red Hat Enterprise Linux Server → Red Hat Enterprise Linux 6 Server - Satellite Tools (RPMs) and select the Red Hat Enterprise Linux 6 Server - Satellite Tools RPMs x86_64 repository.
3.4. Creating Custom Products and Repositories
Procedure 3.4. To Create a Custom Product:
- Click Content → Products and then click New Product.
- Enter
Custom Products
in the Name field. The label is automatically generated. You do not need to enter a GPG key, synchronization plan or description. - Click Save.
- After the screen refreshes, click Create Repository.
- Enter
Puppet Modules
for the name. The label is automatically generated. - In the Type field, select
puppet
. Leave the URL field blank. - Click Save.
Procedure 3.5. To Upload a Puppet Module to the Repository:
- Download the motd puppet module from https://forge.puppetlabs.com/jeffmccune/motd. The file that you download will have a
.tar.gz
extension. - Click Content → Products and then click Custom Products in the Name field.
- On the Repositories tab, click Puppet Modules to modify the Puppet Modules repository.
- In the Upload Puppet Module section, click Browse, and navigate to the motd module that you downloaded.
- Click Upload.
3.5. Synchronizing Content
Procedure 3.6. To Synchronize Repositories to Your Satellite:
- Click Content → Sync Status to display the list of available products.
- Navigate to Red Hat Enterprise Linux Server → 6Server → x86_64.
- Select the following products:
- Red Hat Enterprise Linux 6 Server RPMs x86_64 6Server.
- Red Hat Enterprise Linux 6 Server - Satellite Tools RPMs x86_64.
- Navigate to Red Hat Enterprise Linux Server → 6.6 → x86_64 and select Red Hat Enterprise Linux 6 Server Kickstart x86_64 6.6.
- Click Synchronize Now.
Chapter 4. Content Management and Promotion
4.1. Creating Application Life Cycle Environments
Procedure 4.1. To Create an Application Life Cycle Environment:
- Click Content → Life Cycle Environments to open the Life Cycle Environment Paths screen.
- Click Add New Environment to display the New Environment page. The Library is the origin of all content that you can use in your environments.
- Type
Dev
in the Name field; the label is automatically populated with the same name, but you can change it to suit your needs. You can add a description of your environment if desired. - Click Save to save the new environment and return to the previous page.
- Click Add New Environment again and this time create an environment called
QA
. - Click Save.
4.2. Creating Content Views
Procedure 4.2. To Create a Content View:
- Click Content → Content Views and then click Create New View.
- Type RHEL6 x86_64 in the Name field; the label is automatically populated.
- Ensure the Composite View check box is cleared, and then click Save.
4.3. Adding Red Hat Enterprise Linux Repositories
Procedure 4.3. To Add the Red Hat Enterprise Linux RPM Repositories:
- On the Content Selection screen, on the Add tab, select the check box next to each of the following repositories:
- Red Hat Enterprise Linux 6 Server Kickstart x86_64 6Server
- Red Hat Enterprise Linux 6 Server RPMs x86_64 6Server
- Red Hat Enterprise Linux 6 Server - Satellite Tools RPMs x86_64
- Click Add Repositories. After the page has refreshed, you can see the list of repositories in your Content View on the List/Remove tab.
4.4. Adding Puppet Modules
Procedure 4.4. To Add a Puppet Module:
- Ensure you are still on the Content Views page; on the main menu, click Content → Content Views.
- On the Puppet Modules tab, click Add New Module to display a list of available Puppet Modules. You can use the Filter field to help locate the required module.
- Click Select Version to select the motd module.
- Click Select Version next to the version of the module that you want to add.
Note
If you select "Use Latest" when you select which Puppet module version to use, it means that whenever a new version of the Content View is published, the latest version of that module is included in the published view.
4.5. Publishing a Content View
Procedure 4.5. To Publish a Content View to the Library:
- Click Content → Content Views to display the Content Views page.
- Click the name of the Content View that you want to publish.
- Click Publish New Version to display the Publish New Version page. This specifies the version and allows you to enter a comment to reflect any changes made to the content view.
- Click Save to publish the Content View to the Library. You can monitor the publication progress on the screen that appears.
- When the publishing process is complete, click Promote to display the list of available Promotion Paths (Library -> Dev -> QA).
- Select the check box for the Dev environment, and then click Promote Version.
4.6. Creating and Editing Activation Keys
Procedure 4.6. To Create an Activation Key:
- On the main menu, click Content → Activation Keys and then click New Activation Key.
- In the Name field, type
ak-Reg_to_Dev
. - For the purposes of this example, clear the Content Host Limit check box.You can use this field to control how many times a given Activation Key is used. For example, if you associate the key with a subscription that has a limited quantity, you can set the limit on the Activation Key to eliminate exceeding that quantity.
- Select the check box for the Dev environment.
- In the Content View drop-down list, select the RHEL 6 x86_64 Content View, and then click Save.
Procedure 4.7. To Edit Activation Key Parameters:
- On the Activation Keys page, click Subscriptions → Add to display the list of available subscriptions.
- Select the check box next to each subscription that you want to attach to each host that uses this activation key.
- Click Add Selected.
Chapter 5. Finalizing Provisioning Configuration
5.1. Creating Provisioning Templates
Procedure 5.1. To Create a Provisioning Template:
- On the main menu, click Hosts → Provisioning Templates.
- In the Name column, click Satellite Kickstart Default in the list of provisioning templates. This displays the configuration tabs where you can customize the template.
- On the Association tab, select RHEL Server 6.5 from the list of applicable operating systems, and then click Submit.
- In the Name column, click Kickstart default PXELinux in the list of provisioning templates.
- On the Association tab, select RHEL Server 6.5 from the list of applicable operating systems, and then click Submit.
- On the main menu, click Hosts → Operating Systems and then click RHEL Server 6.5. This displays the configuration tabs where you can customize the operating system.
- On the Partition Table tab, select Kickstart Default.
- On the Installation Media tab, ensure Default_Organization/Library/Red_Hat_6_Server_Kickstart_x86_64_6Server is visible and selected.
- On the Templates tab, select
Kickstart default PXELinux
from the PXELinux drop-down list. - Select
Satellite Kickstart Default
from the Provision drop-down list, and then click Submit.
5.2. Creating Host Groups
Procedure 5.2. To Create a Host Group:
- On the main menu, click Configure → Host Groups, and then click New Host Group.
- On the Host Group tab, complete the following values:
- Name: RHEL6Server-x86_64
- Lifecycle Environment: Default_Organization/DEV
- Content View: RHEL_6_x86_64
Note
This field only appears after you enter a value in the Life Cycle Environment field. - Content Source: The FQDN of your Capsule (which may be the Satellite Server).
- Puppet CA: The FQDN of your Satellite.
- Puppet Master: The FQDN of your Satellite.
- On the Puppet Classes tab, select the motd puppet module from the list of available classes.
- On the Network tab, select the following values:
- Domain: example.org
- Subnet: Provisioning_Net
- Realm: For the purposes of this example, leave this field blank. If you have configured realm management, for example IPA, select the appropriate realm here.
- On the Operating System tab, select the following values:
- Architecture: x86_64
- Operating system: RHEL Server 6.5
- Media: Default_Organization/Library Red Hat Server 6.5 x86_64. In this example, this is automatically populated.
Note
If this field is not automatically populated, it means the Organization and Location associations are not correctly configured. See Procedure 2.5, “To Associate Installation Media with Organizations and Locations:”. - Partition table: Kickstart default
- Root password: changeme
- On the Locations tab, select Default_location.
- On the Organizations tab, select Default_Organization.
- On the Activation Keys tab, select ak-Reg_To_Dev from the Activation Keys list.
- Click Submit.
Chapter 6. Provisioning Hosts
6.1. Provisioning a Host Using PXE
Procedure 6.1. To Provision a Host:
- On the main menu, click Hosts → New Host to open the New Host page.
- On the Host tab, complete the following values:
- Name: Choose a suitable name for your host. For example,
host1.example.org
. - Host Group: Select RHEL6Server-x86_64
Note
New hosts inherit the default values configured for the host group. This means you can quickly build a host without reentering those values. - Content Source: The $FQDN of your Satellite. This is automatically selected based on the Host Group.
- On the Network tab, complete the following values:
- MAC Address: The MAC address of the new host. The Satellite server reserves a DHCP address using this value. Ensure you enter it correctly.
- Subnet:
Provisioning_Net
This value is automatically populated. - IP Address: This value is automatically populated.
Do not make any changes to the Puppet Classes, Operating System, Parameters, or Additional Information tabs. - Click Submit.
- Power on your host (either physical host or virtual machine); it will PXE-boot and begin its installation process.
6.2. Provisioning a Host Using a Boot Disk
Table 6.1. Comparison of Boot Image Type Characteristics
Type | Generic | DHCP Required | DHCP Reservation | Preregister Host | Operating System Specific |
---|---|---|---|---|---|
Host-specific image | No | No | No | Yes | No |
Full host image | No | Yes | No | Yes | Yes |
Generic image | Yes | Yes | No | Yes | No |
6.2.1. Prerequisites
- Regardless of image type you use, the host must be registered to Satellite before you boot from the image. Hosts are identified by their MAC or IP address to provide the correct provisioning template if the host is in build mode.
- For host-specific images, ensure the host IP addresses and subnets are populated, and the subnet's gateway, subnet mask, and DNS resolvers are correctly configured. Navigate to Infrastructure → Subnets to configure these values.
- To permit access to images for non-administrative users, add the "Boot disk access" role to a user or add the "download_bootdisk" permission to an existing role.
- Ensure that the appropriate iPXE provisioning templates are available. Red Hat Enterprise Linux uses the "Kickstart default iPXE" template.
Note
gPXE images are currently unsupported.Host and generic image types are based on iPXE technology, which supports a different set of hardware drivers from PXELinux. See http://ipxe.org/appnote/hardware_drivers for the list of supported hardware.If you encounter issues with iPXE, full host images contain built-in kernels and RAM disks and can load on any kind of network card, including those without PXE support. - Ensure that the appropriate standard templates are available. Red Hat Enterprise Linux uses uses "Kickstart RHEL default" as the provisioning template.
Important
network --bootproto <%= @static ? "static" : "dhcp" %> --hostname <%= @host %> <%= " --ip=#{@host.ip} --netmask=#{@host.subnet.mask} --gateway=#{@host.subnet.gateway} --nameserver=#{@host.subnet.dns_primary},#{@host.subnet.dns_secondary}" if @static %>
6.2.2. Creating Boot Disk Images
Note
6.2.2.1. Creating Host-specific Images
Procedure 6.2. To Create a Host-specific Image Using the Web UI:
- Navigate to Hosts → All hosts and click the appropriate host name.
- Click Boot disk and then click Host hostname image.
hammer
CLI tool, run the following command:
# hammer bootdisk host --host client.example.com
# foreman-rake bootdisk:generate:host NAME=client.example.com OUTPUT=/tmp
OUTPUT
to a suitable destination path, either a directory or a file. The foreman
user must have write access to the specified destination.
6.2.2.2. Creating Full Host Images
Procedure 6.3. To Create a Full Host Image Using the Web UI:
- Navigate to Hosts → All hosts and click the appropriate host name.
- Click Boot disk and then click Full Host hostname image.
hammer
CLI tool, run the following command:
# hammer bootdisk host --host client.example.com --full true
# foreman-rake bootdisk:generate:full_host NAME=client.example.com
6.2.2.3. Creating Generic Images
Procedure 6.4. To Create a Generic Image from the Web UI:
- Navigate to Hosts → All hosts and click the appropriate host name.
- Click Boot disk and then click Generic image.
hammer
CLI tool, run the following command:
# hammer bootdisk generic
# foreman-rake bootdisk:generate:generic
6.2.2.4. Creating USB Images
isohybrid
command, which means that the resulting file is also bootable as a disk, and suitable for copying to a USB device.
# dd if=fqdn.iso of=/dev/sdX
6.3. Provisioning Hosts with Static IP Addresses
6.3.1. Using Custom Templates to Assign Static IP Addresses
Procedure 6.5. To Edit a PXE Template:
- Navigate to Hosts → All Hosts and click the name of the host whose template you want to edit.
- Click the Templates tab to display the list of available template types.
- Click Edit for the PXELinux Template type. The template displays in the template editor.
- Make the required changes and then click Submit. See Example 6.1, “Editing the PXE Template to Assign Static IP Addresses” for an example of how to update a PXE template.
Example 6.1. Editing the PXE Template to Assign Static IP Addresses
default linux label linux kernel <%= @kernel %> <% if @host.operatingsystem.name == 'Fedora' and @host.operatingsystem.major.to_i > 16 -%> append initrd=<%= @initrd %> ks=<%= foreman_url('provision')%>&static=yes ks.device=bootif network ks.sendmac <% elsif @host.operatingsystem.name != 'Fedora' and @host.operatingsystem.major.to_i >= 7 -%> append initrd=<%= @initrd %> ks=<%= foreman_url('provision')%>&static=yes network ks.sendmac <% else -%> append initrd=<%= @initrd %> ks=<%= foreman_url('provision')%>&static=yes ksdevice=bootif network kssendmac <% end -%> IPAPPEND 2
6.3.2. Using Host Parameters to Assign Static IP Addresses
if
statement in conjunction with host parameters to set a static IP address.
Example 6.2. Using Host Parameters to Assign Static IP Addresses
<% if @host.params['my_param_deploy_static'] == "true" -%> network --bootproto <%= "static --ip=#{@host.ip} --netmask=#{@host.subnet.mask} --gateway=#{@host.subnet.gateway} --nameserver=#{[@host.subnet.dns_primary,@host.subnet.dns_secondary].reject{|n| n.blank?}.join(',')}" %> --hostname <%= @host %> <% else -%> network --bootproto 'dhcp' --hostname <%= @host %> <% end -%>
6.3.3. Using Subnets to Set Static IP Addresses
Procedure 6.6. To Specify Static Boot Mode by Default:
- Navigate to Infrastructure → Subnets and click the name of the subnet that you want to configure. To create a new subnet, follow the steps in Procedure 2.4, “To Select the Default Subnet:”.
- On the Subnet tab, select
Static
from the Boot mode drop-down list, and then click Submit.
Appendix A. Glossary of Terms
- Activation Key
- A registration token used in a Kickstart file to control actions at registration. These are similar to Activation Keys in Red Hat Satellite 5, but provide a subset of features because Puppet controls package and configuration management after registration.
- Application Life Cycle Environment
- An Application Life Cycle Environment represents a step, or stage, in a promotion path through the Software Development Life Cycle (SDLC). Promotion paths are also known as development paths. Content such as packages and Puppet modules move through life cycle environments by publishing and promoting Content Views. All Content Views have versions, which means you can promote a specific version through a typical promotion path; for example, from development to test to production. Channel cloning implements this concept in Red Hat Satellite 5.
- Attach
- The process of associating a Subscription to a Host that provides access to RPM content.
- Capsule
- A Capsule is an additional server that can be used in a Red Hat Satellite 6 deployment to facilitate content federation and distribution in addition to other localized services (Puppet Master,
DHCP
,DNS
,TFTP
, and more). - Catalog
- A Catalog is a document that describes the desired system state for one specific computer. It lists all of the resources that need to be managed, as well as any dependencies between those resources.
- Compute Profile
- Compute Profiles specify default attributes for new virtual machines on a compute resource.
- Compute Resource
- A Compute Resource is virtual or cloud infrastructure, which Red Hat Satellite 6 uses for deployment of hosts and systems. Examples include Red Hat Enterprise Virtualization Manager, OpenStack, EC2, and VMWare.
- Content
- Content includes software packages (RPM files) and Puppet modules. These are synchronized into the Library and then promoted into Life Cycle Environments using Content Views so that they can be consumed by Hosts.
- Content Delivery Network (CDN)
- The Content Delivery Network (CDN) is the mechanism used to deliver Red Hat content in a geographically co-located fashion. For example, content that is synchronized by a Satellite in Europe pulls content from a source in Europe.
- Content Host
- A Content Host is the part of a host that manages tasks related to content and subscriptions.
- Content View
- A Content View is a definition of content that combines products, packages, and Puppet modules with capabilities for intelligent filtering and creating snapshots. Content Views are a refinement of the combination of channels and cloning from Red Hat Satellite 5.
- External Node Classifier
- An External Node Classifier is a Puppet construct that provides additional data for a Puppet Master to use when configuring Hosts. Red Hat Satellite 6 acts as an External Node Classifier to Puppet Masters in a Satellite deployment.
- Facter
- Facter is a program that provides information (facts) about the system on which it is run; for example, Facter can report total memory, operating system version, architecture, and more. Puppet modules enable specific configurations based on host data gathered by Facter.
- Hammer
- Hammer is a command line tool for Red Hat Satellite 6. Use Hammer to manage Red Hat Satellite 6 as a standard CLI, for scripts, and also through an interactive shell.
- Hiera
- Hiera is a key/value look-up tool for configuration data which allows keeping site-specific data out of puppet manifests.
- Host
- A Host refers to any system, either physical or virtual, that Red Hat Satellite 6 manages.
- Host Collection
- A Host Collection is equivalent to a Satellite 5 System Group, that is, a user defined group of one or more Hosts.
- Host Group
- A Host Group is a template for building a Host. This includes the content view (which defines the available RPM files and Puppet modules) and the Puppet classes to apply (which ultimately determines the software and configuration).
- Location
- A Location is collection of default settings that represent a physical place. These can be nested so that you can set up an hierarchical collection of locations. For example, you can set up defaults for "Middle East", which are refined by "Tel Aviv", which are further refined by "Data Center East", and then finally by "Rack 22".
- Library
- The Library contains every version, including the latest synchronized version, of the software that the user will ever deploy. For an Information Technology Infrastructure Library (ITIL) [1] organization or department, this is the Definitive Media Library [2] (previously named the Definitive Software Library).
- Manifest
- A Manifest transfers subscriptions from the Customer Portal to Red Hat Satellite 6. This is similar in function to certificates used with Red Hat Satellite 5.For more information about certificates and subscription types, see:
- Organization
- An Organization is an isolated collection of systems, content, and other functionality within a Satellite 6 deployment.
- Product
- A collection of content repositories. Products can be Red Hat products or newly-created products made up of software and configuration content.
- Promote
- The act of moving a content view comprised of software and configuration content from one Application Life Cycle Environment to another, such as moving from development to QA to production.
- Provisioning Template
- A Provisioning Template is a user-defined template for Kickstart files, snippets, and other provisioning actions. In Satellite 6 they provide similar functionality to Kickstart Profiles and cobbler Snippets in Red Hat Satellite 5.
- Pulp Node
- A Pulp Node is a Capsule Server component that mirrors content. This is similar to the Red Hat Satellite 5 Proxy. The main difference is that content can be staged on the Pulp Node before it is used by a Host.
- Puppet Agent
- The Puppet Agent is an agent that runs on a Host and applies configuration changes to that Host.
- Puppet Master
- A Puppet Master is a Capsule Server component that provides Puppet manifests to Hosts for execution by the Puppet Agent.
- Puppet Module
- A Puppet Module is a self-contained bundle of code and data that you can use to manage resources such as users, files, and services.
- Repository
- A Repository provides storage for a collection of content. For example, a YUM repository or a Puppet repository.
- Role
- A Role specifies a collection of permissions that are applied to a set of resources, such as Hosts.
- Smart Proxy
- A Smart Proxy is a Capsule Server component that can integrate with external services, such as
DNS
orDHCP
. - Smart Variable
- A Smart Variable is a configuration value that controls how a Puppet Class behaves. This can be set on a Host, a Host Group, an Organization, or a Location.
- Standard Operating Environment (SOE)
- A Standard Operating Environment (SOE) is a controlled version of the operating system on which applications are deployed.
- Subscription
- Subscriptions are the means by which you receive content and service from Red Hat.
- Synchronizing
- Synchronizing refers to mirroring content from external resources into the Red Hat Satellite 6 Library.
- Synchronization Plans
- Synchronization Plans provide scheduled execution of content synchronization.
- User Group
- A User Group is a collection of roles which can be assigned to a collection of users. This is similar to a Role in Red Hat Satellite 5.
- User
- A user is anyone registered to use Red Hat Satellite. Authentication and authorization is possible through built-in logic, through external LDAP resources, or with Kerberos.
Appendix B. Revision History
Revision History | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Revision 1.2-10 | Tue Jul 14 2015 | David O'Brien | |||||||||
| |||||||||||
Revision 1.2-9 | Fri Jun 19 2015 | David O'Brien | |||||||||
| |||||||||||
Revision 1.2-8 | Sun Jun 14 2015 | David O'Brien | |||||||||
| |||||||||||
Revision 1.2-7 | Sun Jun 14 2015 | David O'Brien | |||||||||
| |||||||||||
Revision 1.2-6 | Fri May 15 2015 | David O'Brien | |||||||||
| |||||||||||
Revision 1.2-5 | Mon May 11 2015 | David O'Brien | |||||||||
| |||||||||||
Revision 1.2-4 | Thu Apr 16 2015 | David O'Brien | |||||||||
| |||||||||||
Revision 1.2-3 | Wed Apr 8 2015 | Megan Lewis | |||||||||
| |||||||||||
Revision 1.2-2 | Fri Apr 3 2015 | David O'Brien | |||||||||
| |||||||||||
Revision 1.2-1 | Tue Mar 31 2015 | David O'Brien | |||||||||
| |||||||||||
Revision 1.2-0 | Thu Feb 22 2015 | David O'Brien | |||||||||
| |||||||||||
Revision 1.1-1 | Mon Dec 22 2014 | David O'Brien | |||||||||
| |||||||||||
Revision 1.1-0 | Wed Dec 10 2014 | David O'Brien | |||||||||
| |||||||||||
Revision 1.0-0 | Wed Nov 26 2014 | David O'Brien | |||||||||
| |||||||||||
Revision 0.1-1 | Thu Nov 20 2014 | David O'Brien | |||||||||
| |||||||||||
Revision 0.1-0 | Fri Oct 17 2014 | David O'Brien | |||||||||
|