1. Manuals
  2. Brands
  3. Red Hat Manuals
  4. Server
  5. RED HAT NETWORK SATELLITE 5.3.0
  6. Deployment manual

Red Hat NETWORK SATELLITE 5.3.0 Deployment Manual

Hide thumbs Also See for RED HAT NETWORK SATELLITE 5.3.0:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Reference Manual, Configuration Manual
Red Hat Network
Satellite 5.3
Deployment Guide
Red Hat Network Satellite

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the RED HAT NETWORK SATELLITE 5.3.0 and is the answer not in the manual?

Questions and answers

Related Manuals for Red Hat RED HAT NETWORK SATELLITE 5.3.0

Summary of Contents for Red Hat RED HAT NETWORK SATELLITE 5.3.0

  • Page 1 Red Hat Network Satellite 5.3 Deployment Guide Red Hat Network Satellite...
  • Page 2 Deployment Guide Red Hat Network Satellite 5.3 Deployment Guide Red Hat Network Satellite Edition 1 Copyright © 2010 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/.

  • Page 3: Table Of Contents

    Introduction 1. More to Come ....................... vii 1.1. Send in Your Feedback ..................vii I. Satellite Administration 1. Users 1.1. Adding Users ....................... 3 1.2. Deleting and Deactivating Users ................3 1.2.1. Deactivating Users ..................3 1.2.2. Deleting Users ..................4 1.3.
  • Page 4 Deployment Guide 5. Provisioning with Satellite 5.1. Requirements ..................... 33 5.2. Definitions and Terms ..................33 5.3. Provisioning Scenarios Supported ............... 34 5.4. Overview of Preparing a Satellite for Provisioning ..........34 5.5. Kickstart Trees And Software Content ..............34 5.5.1.
  • Page 5 Index...

  • Page 7: Introduction

    Red Hat Network Satellite. 1.1. Send in Your Feedback If you would like to make suggestions about the Red Hat Network Satellite Reference Guide, please submit a report in Bugzilla (http://bugzilla.redhat.com/bugzilla/) against the component Documentation_Deployment_Guide (Product: Red Hat Network Satellite, Version: 531).
  • Page 8 viii...

  • Page 9: Satellite Administration

    Part I. Satellite Administration This part describes some general practices for Satellite administration, including backing up and restoring Satellite databases, user and organization administration, and more.

  • Page 11: Users

    Chapter 1. Users The Users tab at the top of the Satellite navigation bar allows administrators to manage Satellite users. These pages enable you to grant and edit permissions for those who administer your system groups. Click on the User List to modify users within your organization. 1.1.

  • Page 12: Deleting Users

    Chapter 1. Users The user no longer appears in the Active Users list. Click the Deactivated link from the User List menu to view the deactivated user. At any time, you can reactivate the user from the Deactivated list by clicking the checkbox next to the user and clicking Reactivate.
  • Page 13 Assigning User Roles • Configuration Administrator — This role enables the user to manage the configuration of systems in the organization using the RHN Satellite interface. • Monitoring Administrator — This role allows for the scheduling of probes and oversight of other monitoring infrastructure.

  • Page 15: Satellite Operation Guidance

    Chapter 2. Satellite Operation Guidance Red Hat Network (RHN) is the environment for system-level support and management of Red Hat systems and networks of systems. Red Hat Network brings together the tools, services, and information repositories needed to maximize the reliability, security, and performance of their systems. To use RHN, system administrators register software and hardware profiles, known as System Profiles, of their client systems with Red Hat Network.

  • Page 16: Backing Up The Embedded Database

    Chapter 2. Satellite Operation Guidance 2.2.1. Backing up the Embedded Database To backup the Embedded RHN Satellite database, perform the following tasks: 1. Stop the Satellite Server: rhn-satellite stop 2. Create the Backup using db-control. Switch to the Oracle user before executing the db-control utility.
  • Page 17 • /var/www/cobbler/ If possible, back up /var/satellite/, as well. In case of failure, this will save lengthy download time. Since /var/satellite/ (specifically /var/satellite/redhat/NULL/ and /var/ satellite/rhn/) is primarily a duplicate of Red Hat's RPM repository, it can be regenerated with satellite-sync.

  • Page 18: Restoring The Embedded Database

    Chapter 2. Satellite Operation Guidance 2.2.3. Restoring the Embedded Database RHN Database Control makes Embedded Database restoration a relatively simple process. 1. First, stop the database and related services with the following command: rhn-satellite stop 2. Restore the Backup with db-control — Switch to the Oracle user and use the following command, replacing directory with the directory that contains the backup: su - oracle db-control restore [directory]...

  • Page 19: Monitoring The Satellite

    Monitoring the Satellite #!/bin/bash rsync -avz /tmp/db-backup-$(date "+%F") [destination] &> /dev/null #!/bin/bash scp -r /tmp/db-backup-$(date "+%F") [destination] &> /dev/null In addition, a clean up script to remove older backup directories should be utilized to prevent the storage from filling up. 2.3.
  • Page 20 Chapter 2. Satellite Operation Guidance Note To ensure that PAM authentication functions properly, install the pam-devel package. Set up a PAM service file (usually /etc/pam.d/rhn-satellite) and have the Satellite use it by adding the following line to /etc/rhn/rhn.conf: pam_auth_service = rhn-satellite This assumes the PAM service file is named rhn-satellite.

  • Page 21: Rpm Building

    The directory listing for the defined top level directory (/home/rpmbuild/rpmbuild in the example above) must have the same directory layout that is present under /usr/src/redhat. Appendix B contains a very basic RPM spec file which can be used a basis when starting to craft real spec files needed locally.

  • Page 22: Rpm Spec File Example

    Chapter 2. Satellite Operation Guidance rpm --resign package.rpm rhnpush --server=http[s]://satellite.server/APP package.rpm --channel=custom-channel-name The following commands will verify an RPM package located in the current directory: rpm –qip pakcage.rpm rpm -K package.rpm 2.5.3. RPM Spec File Example The following is a basic example of an RPM spec file. When building, it should be located in the directory SPECS under the _topdir as defined in user's .rpmmacros file and the corresponding source and patch files should in the SOURCES directory.

  • Page 23: Kickstart

    Kickstart 2.6. Kickstart System kickstarting is essential part of automated installation and efficient system provisioning. PXE combined with remote hardware management provides fully automated solution for kickstarting. However, parts of the network might not have PXE/DHCP functionality available so also CD/USB booting might be needed in some cases.

  • Page 24: Creating Usb Boot Media

    Chapter 2. Satellite Operation Guidance 2.6.4. Creating USB Boot Media Creating bootable USB image can done with the following commands after the preparations above. Be extremely careful when carrying out these command as root (required for most critical parts) since they access device files and may irrecoverably damage your system! The example below uses /dev/ loop0 for mounting, make sure you use the device which the command losetup -f prints.
  • Page 25 Kickstart Boot Menu Example MENU TITLE Red Hat Enterprise Linux Installation TIMEOUT 100 ALLOWOPTIONS 0 NOESCAPE 1 PROMPT 0 MENU MASTER PASSWD password LABEL RHEL MENU LABEL TS 1.0 RHEL 5.4 x86_64 KERNEL menu.c32 APPEND rhel5.cfg # ISO/EXTLINUX LABEL LOCAL MENU LABEL Boot from local hard disk LOCALBOOT 0 # PXELINUX...

  • Page 27: Multiple Organizations

    Chapter 3. Multiple Organizations RHN Satellite supports the creation and management of multiple organizations within one Satellite installation, allowing for the division of systems, content, and subscriptions across different organizations or specific groups. This chapter summarizes the basic setup tasks and concepts of multiple organization creation and management within RHN Satellite.

  • Page 28: Creating An Organization

    Chapter 3. Multiple Organizations • Activation Keys — The number of activation keys available to the organization. • Kickstart Profiles — The number of kickstart profiles available to the organization. • Configuration Channels — The number of Configuration Channels available to the organization. From this page, you can delete the organization by clicking the Delete Organization link.

  • Page 29: Managing Entitlements

    Managing Entitlements d. Enter the First Name and Last Name of the organization administrator. 3. Click the Create Organization button to complete the process. Once the new organization is created, the Organizations page will display with the new organization listed. Satellite Administrators should consider reserving the organization 1 Organization Administrator account for themselves to have the option of logging into this organization for various reasons.

  • Page 30: Admin -> Subscriptions -> System Entitlements

    Chapter 3. Multiple Organizations The Organizations subtab allows Satellite administrators to adjust the number of software channels available to each organization. Type in the number (within the range listed in Possible Values) and click the Update button for that organization. Note Organization Administrators that create a custom channel can only use that channel within their organization unless an Organizational Trust is established between the organizations...

  • Page 31: Configuring Systems In An Organization

    Configuring Systems in an Organization 3.4. Configuring Systems in an Organization Now that an organization has been created and requisite entitlements assigned to it, you can then assign systems to each organization. There are two basic ways to register a system against a particular organization: 1.
  • Page 32 Chapter 3. Multiple Organizations If you are the Organization Administrator, you can click the username to display the User Details page for the user. Note You must be logged in as the Organization Administrator to edit the User details for an organization.

  • Page 33: Organizational Trusts

    Chapter 4. Organizational Trusts IT deployments are not one-dimensional. Within any organization, the IT infrastructure truly needs to be managed in a multitenant / multi-organizational structure. Whether the division is bureaucratic (organizational departments, offices, subsidiaries) or functional (Web apps, databases, desktops, business processes) Red Hat Network Satellite enables administrators to divide their deployments into organized containers.

  • Page 34: Organization Trust Relationships

    Chapter 4. Organizational Trusts Figure 4.1. Organizational Trusts 4. Click the checkbox next to the names of the organizations you want to be in the organizational trust with the current organization 5. Click the Modify Trusts button 4.2. Organization Trust Relationships Organizations can share their resources with each other by establishing an organizational trust relationship.

  • Page 35: System Migration

    System Migration • Private — Make the channel private so that it cannot be accessed by any organizations except the owning organization. • Protected — Allow the channel to be accessed by specific trusted organizations of your choice. • Public — Allow all organizations within the trust to access the custom channel. Trusted Organizations that are granted access to the custom content using the protected or public access modes can allow their client systems to install and update packages from the shared channel.
  • Page 36 Chapter 4. Organizational Trusts For example, if the Finance department (created as an organization in RHN Satellite with OrgID 2) wants to migrate a workstation (with SystemID 10001020) from the Engineering department, but the Finance Organization Administrator does not have shell access to the RHN Satellite server. The RHN Satellite hostname is satserver.example.com.
  • Page 37 System Migration Satellite Administrators that need to migrate several systems at once can use the --csv option of migrate-system-profile to automate the process using a simple comma-separated list of systems to migrate. A line in the CSV file should contain the ID of the system to be migrated as well as destination organization's ID in the following format: systemId,to-org-id The systemId, for example could be 1000010000, while the to-org-id could be 3.

  • Page 39: Satellite Provisioning

    Part II. Satellite Provisioning This part describes how to manage, allocate resources, and deploy servers and systems using Satellite, including kickstarting physical and virtual server systems, and provisioning supported systems that have no previous operating system installed (also called bare metal provisioning).

  • Page 41: Provisioning With Satellite

    Chapter 5. Provisioning with Satellite All organizations need simple, yet powerful tools to deploy Red Hat Enterprise Linux systems. For many years, Red Hat Network Satellite has empowered companies to build repeatable, predictable and reliable deployment processes to ensure rapid repurposing of Linux servers and desktops. Whether you have 10 systems or 10,000 systems, RHN Satellite can help you achieve this goal in a disciplined fashion.

  • Page 42: Provisioning Scenarios Supported

    Chapter 5. Provisioning with Satellite 5.3. Provisioning Scenarios Supported • New Installations — Starting with Satellite 5.3.0 it is possible to provision systems that have not previously had any operating system installed (also known as bare metal installations). • Virtual Installations — Satellite supports KVM, Xen fully-virtualized guests, and Xen para-virtualized guests.
  • Page 43 Manually Installed Kickstart Trees beta distribution's contents to /var/satellite/custom-distro/rhel-i386-server-5.3- beta/ 4. Create a custom software channel with the Satellite web interface. (Navigate to Channel => Manage Software Channels => Create Channel) and create a base channel with an appropriate name and label. In keeping with the example RHEL beta version above, we might use the label rhel-5.3-beta.

  • Page 44: Required Distribution Files

    Chapter 5. Provisioning with Satellite Figure 5.1. Creating Kickstart Distribution 5.5.3. Required Distribution Files Satellite expects certain files to exist in specified locations within the Kickstart Tree and these locations will differ depending on the architecture of the system. The table below spells out where kernel and initrd are expected to reside for the different architectures.

  • Page 45: Kickstart Profiles

    It is highly recommended that you review the "Kickstart Installations" Chapter of the Red Hat Enterprise Linux Installation Guide available at the following URL: http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Guide-en-US/ch- kickstart2.html This guide discusses all of the options available for customizing the installation.
  • Page 46 Chapter 5. Provisioning with Satellite 5.6.2.1. Wizard Style Kickstarts To create a wizard style Kickstart: 1. Click on Systems => Kickstart => create a new kickstart profile 2. Provide an appropriate label, select the desired base channel and distribution 3. Select the Virtualization Type desired 4.
  • Page 47 Creating Kickstart Profiles lang en_US keyboard us zerombr clearpart --all part / --fstype=ext3 --size=200 --grow part /boot --fstype=ext3 --size=200 part swap --size=1000 --maxsize=2000 bootloader --location mbr timezone America/New_York auth --enablemd5 --enableshadow rootpw --iscrypted $1$X/CrCfCE$x0veQO88TCm2VprcMkH.d0 selinux --permissive reboot firewall --disabled skipx key --skip %packages @ Base...

  • Page 48: Templating

    Chapter 5. Provisioning with Satellite 5.7. Templating One of the more powerful new features in Satellite 5.3 is Cheetah based kickstart templating. With this new capability, you can include variables, snippets (see below), and flow control statements such as for loops and if statements in your kickstart files. 5.7.1.

  • Page 49: Snippets

    Snippets 5.7.3. Snippets Snippets are similar to variables but can span many lines and can include variables in them. They can be included in a kickstart profile by using the text $SNIPPET('snippet_name'). You may make a snippet for a certain package list, one for a particular %post script, or for any text that would normally be included in a kickstart file.
  • Page 50 Chapter 5. Provisioning with Satellite Figure 5.3. Kickstart Snippets For more information, refer to https://fedorahosted.org/cobbler/wiki/KickstartSnippets. 5.7.3.1. Default Snippets There are many snippets that ship by default and may be used in kickstarts written on or uploaded to the Satellite server. You may want to look at a template from a wizard style kickstart located in /var/ lib/rhn/kickstarts/wizard/ and see what default snippets are used and how they are used.

  • Page 51: Kickstarting A Machine

    Kickstarting a Machine %post echo $foo > /tmp/foo.txt The templating engine would try to find a variable named $foo and would fail if foo did not exist as a variable. There are a few ways to escape the $ symbol so it shows up as a bash variable. The simplest is with a backslash: %post echo \$foo >...
  • Page 52 Chapter 5. Provisioning with Satellite with the Red Hat Enterprise Linux 5.2 i386 installation disc. When the boot prompt comes up, simply type: linux ks=http://satellite.example.com/path/to/kickstart The system will boot, download the kickstart, and re-install itself. 5.8.1.2. PXE Booting PXE booting is a very convenient method of installing and reinstalling your physical systems, but does come with a few requirements: •...
  • Page 53 Bare Metal 4. Finally, the DHCP server refers to the boot image file (in this case, at /var/lib/tftpboot/ pxelinux.0. 5.8.1.2.2. Xinetd and TFTP Xinetd is a daemon that manages a suite of services, including TFTP, the FTP server used for transferring the boot image to a PXE client.
  • Page 54 Chapter 5. Provisioning with Satellite If you have an existing firewall ruleset using IPTables, you need to add the following rules to open the requisite Cobbler-related ports. The following lists each of the requisite rules with their associated service. • For TFTP: /sbin/iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 69 -j ACCEPT /sbin/iptables -A INPUT -m state --state NEW -m udp -p udp --dport 69 -j ACCEPT •...
  • Page 55 Bare Metal 5.8.1.2.5. Cobbler configuration Cobbler is already set up to generate PXE configurations, but you may want to adjust the pxe_just_once configuration option depending on how your machines BIOSes are configured, for the best possible PXE workflow. A common setup has PXE occur first in the BIOS order, effectively not booting off the local disk unless the PXE server instructs the system to do so remotely.

  • Page 56: Re-Provisioning

    Chapter 5. Provisioning with Satellite can be made without having to re-burn the CD. If you create a new kickstart profile and want to use it via the cobbler boot ISO, you will need to recreate a fresh disc. Note Due to issues with the version of syslinux shipped with Red Hat Enterprise Linux 4, this command will not work unless the Satellite is running on Red Hat Enterprise Linux 5.

  • Page 57: Virtualized Guest Provisioning

    Virtualized Guest Provisioning • Go to Systems => Kickstart => Profiles • Select on the desired profile • Select System Details => File Preservation • Select your file preservation list Note File preservation lists are only available on Wizard-style kickstarts and are only available during re-provisioning.

  • Page 58: Provisioning Through An Rhn Proxy

    Chapter 5. Provisioning with Satellite best to configure host networking to create an actual bridge if outside networking is desired — and it almost always is — xenbr0 is an actual bridge, and usage is recommended if it exists). • Virtual Storage Path (Path to either a file, LVM Logical Volume, directory, or block device with which to store the guest's disk information, such as /dev/sdb, /dev/LogVol00/mydisk, VolGroup00, or /var/lib/xen/images/myDisk) 5.8.4.

  • Page 59: Cobbler On The Command Line

    Cobbler On the Command Line XML-RPC Namespace Usage kickstart.profile.keys list, add (associate), and remove (disassociate) activation keys associated to a kickstart profile. kickstart.profile.software manipulate the list of packages associated to a kickstart profile. kickstart.profile.system manage file preservations, manage cryptography keys, enable/ disable config management and remote commands, setup partitioning schemes, and setup locale information associated to a given kickstart profile.

  • Page 60: Cobbler Command Line: Next Steps

    Chapter 5. Provisioning with Satellite sudo cobbler profile edit --name=profile-name --virt-ram=1024 5.9.3. Cobbler Command Line: Next Steps Setting a system (see pxe_just_once above) to be reinstalled at next reboot: sudo cobbler system edit --name=system-name --netboot-enabled=1 Assigning a system to a new profile for reinstallation: sudo cobbler system edit --name=system-name --profile=new-profile-name --netboot-enabled=1 Listing all systems assigned to a particular profile: sudo cobbler system find --profile=profile-name...

  • Page 61: Other Cobbler Settings

    Other Cobbler settings • distributions: $tree_name:$org_id:$org_name (if manually created) Or $tree_name (if synced by Satellite Sync) • profiles: $profile_name:$org_id:$org_name You will encounter these names if you choose to interact with Cobbler directly at the command line. Note that it is important that you do not alter Satellite generated names so long as you want to allow Satellite to maintain the objects in question.

  • Page 62: Troubleshooting

    Chapter 5. Provisioning with Satellite koan --replace-self --server=satellite.example.org --system=system-name Reboot after running the above command to install the new OS. This can also be used with upgrade kickstarts if desired (for instance, to upgrade a large number of machines between RHEL 4 and RHEL You can provision a virtual guest by using one of the following methods: koan --virt --server=satellite.example.org --profile=profile-name koan --virt --server=satellite.example.org --system=system-name...

  • Page 63: Anaconda Content Errors

    Anaconda content errors +--------------------------------------------------------------+ You can check the following items: 1. Verify httpd is running on your RHN Satellite 2. Verify cobblerd is running 3. Verify you can fetch the above file using wget from a different host. For example: wget http://satellite.example.com/cblr/svc/op/ks/profile/rhel5-i386-u3:1:Example-Org 4.
  • Page 64 Chapter 5. Provisioning with Satellite +--------+ +-------+ | Reboot | | Retry | +--------+ +-------+ +------------------------------------------------------------+ Clients will fetch content from RHN Satellite based on the --url parameter contained within the kickstart. For example: url --url http://satellite.example.com/ks/dist/ks-rhel-i386-server-5-u3 If you receive errors from Anaconda stating it can't find images or packages you should first check that the above URL will generate a 200 response: wget http://satellite.example.com/ks/dist/ks-rhel-i386-server-5-u3 --2009-08-19 15:06:55--...

  • Page 65: Cobbler Log Files

    5.10.5. Tracebacks from Taskomatic If you receive emails such as: Subject: WEB TRACEBACK from satellite.example.com Date: Wed, 19 Aug 2009 20:28:01 -0400 From: RHN Satellite <dev-null@redhat.com> To: admin@example.com java.lang.RuntimeException: XmlRpcException calling cobbler. com.redhat.rhn.manager.kickstart.cobbler.CobblerXMLRPCHelper.invokeMethod(CobblerXMLRPCHelper.java:72) at com.redhat.rhn.taskomatic.task.CobblerSyncTask.execute(CobblerSyncTask.java:76) com.redhat.rhn.taskomatic.task.SingleThreadedTestableTask.execute(SingleThreadedTestableTask.java:54)

  • Page 66: Directory Structure For Kickstarts And Snippets

    Chapter 5. Provisioning with Satellite wget http://satellite.example.com/pub/RHN-ORG-TRUSTED-SSL-CERT -O /usr/share/rhn/RHN-ORG- TRUSTED-SSL-CERT perl -npe 's/RHNS-CA-CERT/RHN-ORG-TRUSTED-SSL-CERT/g' -i /etc/sysconfig/rhn/* rhnreg_ks --serverUrl=https://satellite.example.com/XMLRPC --sslCACert=/usr/share/rhn/RHN- ORG-TRUSTED-SSL-CERT --activationkey=1-c8d01e2f23c6bbaedd0f6507e9ac079d # end Red Hat management server registration Breaking this down into the 4 steps you have: 1) mkdir -p /usr/share/rhn/ Creating a directory to house the custom SSL cert used by the RHN Satellite 2) wget http://satellite.example.com/pub/RHN-ORG-TRUSTED-SSL-CERT -O /usr/share/rhn/RHN-ORG- TRUSTED-SSL-CERT...
  • Page 67 Directory structure for Kickstarts and Snippets Raw Kickstarts: /var/lib/rhn/kickstarts/upload/$profile_name--$org_id.cfg Wizard Kickstarts: /var/lib/rhn/kickstarts/wizard/$profile_name--$org_id.cfg • Snippets — Cobbler Snippets are stored in /var/lib/rhn/kickstarts/snippets. Cobbler accesses snippets in this structure via a symbolic link in /var/lib/cobbler/snippets callled spacewalk — thus /var/lib/cobbler/snippets/spacewalk. Satellite's RPMs expect Cobbler's kickstart and snippet directories to be in their default locations —...

  • Page 69: Working With Multiple Satellites

    Part III. Working with multiple Satellites This part describes how to work with multiple Satellite instances, including managing Satellite interaction with Red Hat Network Hosted, the remote network from which Satellite receives supported errata and content updates officially from Red Hat, Inc.

  • Page 71: Inter-Satellite Sync (Iss)

    Chapter 6. Inter-Satellite Sync (ISS) As an organization grows, so does complexity of the deployed systems. Red Hat Network Satellite deployment can grow with your IT infrastructure. One capability that assists with managing scale and complexity is the deployment of multiple RHN Satellites configured to communicate with each other. Each Satellite manages a segment of an organization's deployment, minimizing the inefficiencies of both massive scaling and dispersed data centers.

  • Page 72: Configuring The Master Rhn Satellite Server

    Chapter 6. Inter-Satellite Sync (ISS) Figure 6.2. Master Server and Slave Peers that include their own custom content In this example, the master Satellite is the development channel, from which content is distributed to all production slave Satellites. Some slave Satellites have extra content not present in master Satellite channels.

  • Page 73: Configuring The Slave Rhn Satellite Servers

    Configuring the Slave RHN Satellite Servers allowed_iss_slaves= By default, no slave Satellites are specified to sync from the master server, so you must enter the hostname of each slave Satellite server, separated by commas. For example: allowed_iss_slaves=slave1.satellite.example.org,slave2.satellite.example.org Once you finished configuring the rhn.conf file, restart the httpd service by issuing the following command: service httpd restart 6.4.

  • Page 74: Syncing Between A Development Staging Server And A Production Satellite

    Figure 6.4. Syncing from RHN Hosted and a Satellite Staging Server Normally, the administrator runs: satellite-sync -c your-channel This command downloads directly from data from rhn_parent (usually RHN Hosted, rhn.redhat.com). Then, to sync from the staging Satellite server address , the administrator runs: satellite-sync --iss-parent=staging-satellite.example.com -c custom-channel 6.5.2.
  • Page 75 Synchronizing by Organization The aim is for Satellite sync to be able to import content with respect to org_id. This targets two sets of users. One is the disconnected Multi-Org case, where the main source of content for the user is either to get content from channel dumps or to export them from connected satellites and import it to the Satellite.

  • Page 77: Revision History

    Appendix A. Revision History Revision 1.0 Mon Dec 7 2009...
  • Page 79 Index changing email address, 4 changing password, 4 deactivate user, 3 delete user (RHN Satellite only), 4 email address changing, 4 PAM authentication implementation, 11 reference guide bug reporting, vii Satellite Administrator, 4 user deactivate, 3 delete (RHN Satellite only), 4 user roles, 4 users, 3 changing email address, 4...

Table of Contents