Language and Page Formatting Options

Red Hat Training

A Red Hat training course is available for Red Hat Satellite

Release Notes

Red Hat Satellite 5.6

Product notes, new features, and known bugs for Red Hat Satellite 5.6

Edition 1

Abstract

This document contains a set of product notes, new features, and known bugs for Red Hat Satellite 5.6

Chapter 1. Introduction

The release notes for Red Hat Satellite 5.6 contains product notes, new features and enhancements, API information, and technical preview information. These release notes also note down major corrections and known bugs in the product.

Chapter 2. Product Notes

  • Satellite 5.6 uses new Enhanced Reporting features that integrate with Subscription Asset Manager (SAM) 1.3 and later. Note that Subscription Asset Manager 1.3 is only supported on a Red Hat Enterprise Linux 6 64-bit architecture only, and likewise for Enhanced Entitlements Reporting features.
  • Satellite 5.6 now uses a PostgreSQL embedded database instead of Oracle Database. As a result, the database path for Satellite 5.6 has changed from /rhnsat to /var/lib/pgsql. Allocate appropriate disk space as needed.
  • Building ISOs with the cobbler buildiso command is supported for Satellite hosts on the x86_64 architecture. This feature is not available for Satellite hosts on the s390x architecture.

Chapter 3. New Features and Enhancements

3.1. New Features

The following new features have been added to Red Hat Satellite 5.6:
  • Embedded database now uses PostgreSQL instead of Oracle. This provides the following database options:
    • Embedded PostgreSQL - PostgreSQL Database contained on the Satellite host.
    • Managed PostgreSQL - PostgreSQL Database managed on an external host created from Satellite installation.
    • External PostgreSQL - User-supplied PostgreSQL database on an external host.
    • External Oracle - User-supplied Oracle database on an external host.
  • The ability to provide online or hot backups of the database for Embedded and Managed PostgreSQL deployments.
  • Enhanced Reporting features that integrate with Subscription Asset Manager 1.3 and later to allow details on subscription reporting over time.
  • ABRT system failure reporting for Satellite clients, which proovides a centralized reporting of detected ABRT crashes.
  • Improved SCAP auditing features and support for XCCDF 1.2 to provide capturing of detailed HTML reports.
  • Inter-Satellite Synchronization now managed within the Web UI, including the ability to preserve Multi-Orgranization permissions and trusts, and mapping them to other Satellites within an Inter-Satellite-Synchronization environment.
  • Provisioning Enhancements:
    • Support for the usage of the cobbler buildiso option for PXE-less provisioning on Satellite hosts using x86_64 architecture.
    • Kickstart profiles can now automatically track to newest kickstart trees when available.
  • Web UI Enhancements.
    • Reband to "Red Hat Satellite" from "Red Hat Network Satellite".

3.2. Audit Reporting

Audit reporting is a new feature in Satellite 5.6 that logs all Satellite users' events and tracks user activity within the Satellite. To use this report, the spacewalk-report needs to be installed.
To audit users:
# spacewalk-report audit-users
user_id,audit_stamp,audit_action,audit_user_id,audit_username,organization_id,username,password
1,2013-07-19 07:57:31,INSERT,-1,SETUP,1,admin,$1$PRZpragf$qn0ADgKNUA8RUK6jWPttG1
2,2013-07-19 10:30:42,INSERT,1,admin,1,mike,$1$7PS2LMpf$3za7fb24Ha0rgPeo39jQM/
2,2013-07-19 10:31:10,DELETE,1,admin,1,mike,$1$7PS2LMpf$3za7fb24Ha0rgPeo39jQM/
To audit servers:
# spacewalk-report audit-servers
server_id,audit_stamp,audit_action,audit_user_id,audit_username,organization_id,architecture,os,release,name,description,info,creator_id,creator_login,auto_update,running_kernel,last_boot,provision_state,channels_last_changed,cobbler_id
1000010000,2013-07-19 07:58:09,INSERT,1,admin,1,x86_64-redhat-linux,fedora-release,19,ibm-ls22-04.rhts.eng.brq.redhat.com,"Initial Registration Parameters:
OS: fedora-release
Release: 19
CPU Arch: x86_64",,1,admin,N,,0,,,
1000010000,2013-07-19 07:58:09,UPDATE,1,admin,1,x86_64-redhat-linux,fedora-release,19,ibm-ls22-04.rhts.eng.brq.redhat.com,"Initial Registration Parameters:
OS: fedora-release
Release: 19
CPU Arch: x86_64",,1,admin,N,,0,,,
1000010000,2013-07-19 07:58:38,UPDATE,-2,CLIENT,1,x86_64-redhat-linux,fedora-release,19,ibm-ls22-04.rhts.eng.brq.redhat.com,"Initial Registration Parameters:
OS: fedora-release
Release: 19
CPU Arch: x86_64",,1,admin,N,3.9.9-302.fc19.x86_64,1374229018.255403,,,
1000010000,2013-07-19 08:00:37,UPDATE,1,admin,1,x86_64-redhat-linux,fedora-release,19,ibm-ls22-04.rhts.eng.brq.redhat.com,"Initial Registration Parameters:
OS: fedora-release
Release: 19
CPU Arch: x86_64",,1,admin,N,3.9.9-302.fc19.x86_64,1374229018,,,
1000010000,2013-07-19 10:36:11,DELETE,1,admin,1,x86_64-redhat-linux,fedora-release,19,ibm-ls22-04.rhts.eng.brq.redhat.com,"Initial Registration Parameters:
OS: fedora-release
Release: 19
CPU Arch: x86_64",,1,admin,N,3.9.9-302.fc19.x86_64,1374229018,,,
To audit server-groups:
# spacewalk-report audit-server-groups
group_id,audit_stamp,audit_action,audit_user_id,audit_username,organization_id,group_name,group_description,max_members,current_members
7,2013-07-22 10:29:23,INSERT,1,admin,1,test-group,test-group,,0
7,2013-07-22 10:30:01,UPDATE,1,admin,1,test-group,test-group,,1
7,2013-07-22 10:30:45,UPDATE,1,admin,1,test-group,test-group,,0
7,2013-07-22 10:30:45,DELETE,1,admin,1,test-group,test-group,,0

Note

Saving the output into a CSV file allows you to view the log results in a human readable format.
For maintenance and database space clean up, archive and delete old entries using the new tool spacewalk-archive-audits.

3.3. New Reports

The following new reports have been added to the spacewalk-report command:
  • inventory - Inventory report
  • custom-info - Display system custom info
  • inactive-systems - Inactive systems in Satellite
  • packages-updates-all - List of packages that can be upgraded
  • packages-updates-newest - List of packages that can be upgraded
  • system-currency - System currency list
  • system-groups - System groups in Satellite
  • system-groups-keys - Activation keys for system groups
  • system-groups-systems - Systems in system groups
  • system-groups-users - System groups users report
  • system-packages-installed - Packages installed on systems

3.4. API Changes

The following changes have been added to the Red Hat Satellite 5.6 API:

New API methods:

  • kickstart.importFile (variant)
  • kickstart.createProfile (variant)
  • kickstart.createProfileWithCustomUrl (variant)
  • kickstart.importRawFile (variant)
  • kickstart.profile.getUpdateType
  • kickstart.profile.setUpdateType
  • org.getCrashFileSizeLimit
  • org.getPolicyForScapFileUpload
  • org.getPolicyForScapResultDeletion
  • org.setCrashFileSizeLimit
  • org.setPolicyForScapFileUpload
  • org.setPolicyForScapResultDeletion
  • sync.master.addToMaster
  • sync.master.create
  • sync.master.delete
  • sync.master.getDefaultMaster
  • sync.master.getMaster
  • sync.master.getMasterByLabel
  • sync.master.getMasterOrgs
  • sync.master.getMasters
  • sync.master.makeDefault
  • sync.master.mapToLocal
  • sync.master.setCaCert
  • sync.master.setMasterOrgs
  • sync.master.unsetDefaultMaster
  • sync.master.update
  • sync.slave.create
  • sync.slave.delete
  • sync.slave.getAllowedOrgs
  • sync.slave.getSlave
  • sync.slave.getSlaveByName
  • sync.slave.getSlaves
  • sync.slave.setAllowedOrgs
  • sync.slave.update
  • system.deleteSystem (variant)
  • system.listAllInstallablePackages
  • system.listPhysicalSystems
  • system.setPrimaryInterface
  • system.crash.createCrashNote
  • system.crash.deleteCrashNote
  • system.crash.getCrashCountInfo
  • system.crash.getCrashNotesForCrash
  • system.crash.getCrashOverview
  • system.crash.getCrashesByUuid
  • system.crash.deleteCrash
  • system.crash.getCrashFile
  • system.crash.getCrashFileUrl
  • system.crash.getLastReportDate
  • system.crash.getTotalCrashCount
  • system.crash.getUniqueCrashCount
  • system.crash.listSystemCrashFiles
  • system.crash.listSystemCrashes
  • system.scap.deleteXccdfScan

Modified API methods:

  • activationkey.addChildChannels
  • activationkey.setDetails
  • channel.software.clone
  • errata.setDetails
  • errata.findByCve
  • kickstart.createProfile
  • kickstart.profile.addScript
  • kickstart.profile.setAdvancedOptions
  • org.delete
  • proxy.listAvailableProxyChannels
  • system.listSystemEvents
  • system.scheduleApplyErrata
  • system.schedulePackageInstall
  • system.scheduleHardwareRefresh
  • system.scheduleReboot
  • system.scheduleScriptRun
  • system.scheduleSyncPackagesWithSystem
  • system.crash.getCrashOverview
  • system.crash.listSystemCrashFiles
  • systemgroup.scheduleApplyErrataToActive

Chapter 4. Technical Preview Features

Technical previews provide early access to upcoming product innovations that enable users to test the functionality of the feature and provide feedback. These features are not fully supported under Red Hat Enterprise Linux Subscription Level Agreements. For more information, see Technical Preview Features Support Scope on the Customer Portal.

4.1. Monitoring with SELinux

Monitoring with SELinux in enforcing mode continues to be offered as a technical preview for Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6 installations of Red Hat Satellite and Red Hat Proxy.

4.2. virt-who

virt-who is an agent for reporting virtual guest IDs to Satellite. virt-who has the ability to scan for third-party hypervisors, registering the hypervisors on the Satellite. virt-who also uploads the list of guest UUIDs associated with the hypervisors.

Note

For this technical preview, the only hypervisor covered is VMWare ESX.
The following sections will set up virt-who on the Satellite server and guest clients.

4.2.1. virt-who Setup

virt-who can be installed on any system except for the hypervisor. The requirements for the system to install virt-who and successfully set it up are as follows:
  • Red Hat Enterprise Linux 6 or above.
  • Access to both the Red Hat Satellite and the hypervisor on port 443, TCP. A Subscription Asset Manager (SAM) system, if one is available, would be suitable.
  • The system must be registered to either Red Hat Network directly or the Red Hat Satellite and subscribed to the RHN Tools channel.

Note

virt-who cannot be installed on the hypervisor since the only supported hypervisor is VMWare ESX and this is a non-Red Hat Enterprise Linux system.
To set up virt-who on the Red Hat Satellite:
  1. Login as root on the Red Hat Satellite.
  2. Install the virt-who package:
    # yum install virt-who
    
  3. Edit the following entries in the /etc/sysconfig/virt-who file:
    # Start virt-who on background, perform doublefork and monitor for virtual guest
    # events (if possible). It is NOT recommended to turn off this option for
    # starting virt-who as service.
    VIRTWHO_BACKGROUND=1
    
    # Enable debugging output.
    # optional
    VIRTWHO_DEBUG=1
    
    # virt-who subscription manager backend, enable ony one option from following 2:
    # Report to Subscription Asset Manager (SAM)
    VIRTWHO_SAM=0
    # Report to Satellite
    VIRTWHO_SATELLITE=1
    
    # Register ESX machines using vCenter
    VIRTWHO_ESX=1
    
    # Option for ESX mode
    VIRTWHO_ESX_ENV=not-used
    VIRTWHO_ESX_SERVER=server_hostname_or_IP
    VIRTWHO_ESX_USERNAME=server_login
    VIRTWHO_ESX_PASSWORD=server_password
    
    # Option for Satellite backend
    VIRTWHO_SATELLITE_SERVER=satellite_hostname
    VIRTWHO_SATELLITE_USERNAME=username
    VIRTWHO_SATELLITE_PASSWORD=password
    
  4. Start the virt-who service:
    service virt-who start
    
    Starting the virt-who service will gather the ESX host/guest UUID information and send the information to the Satellite. It will also scan the /var/lib/virt-who/hypervisor-systemid-[UUID] file to check if the hypervisor has already been registered to the Red Hat Satellite. If it does, the existing hypervisor system information on the Red Hat Satellite is updated. If it does not exist on the Satellite, the new hypervisor wil be registered.

Note

If a hypervisor is deleted, its corresponding file needs to be removed from /var/lib/virt-who/hypervisor-systemid-UUID, and the hypervisor needs to be manually removed via the satellite web UI.

4.2.2. Guest Setup

All virtual systems on the hypervisor need to be registered to the Satellite to make sure that virt-who links these guests to the hypervisor correctly.
To register a guest on the VMWare ESX hypervisor to the Satellite:
  1. Download the SSL cert from the Satellite to the guest system:
    # rpm -Uvh https://satellite_hostname.example.com>/pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm
    
  2. Edit the following entries in the /etc/sysconfig/rhn/up2date:
    serverURL=https://satellite.hostname.example.com
    sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
    
  3. Register the guest to the Satellite by running the command:
    run rhnreg_ks --username sat_username --password sat_password
    

4.2.3. Splice Setup

Splice reporting is also a requirement for a successful virt-who setup. See the Using Subscription Asset Manager Guide for more details on how to set up splice.

4.2.4. Set Up Verification

Once all the configuration has been completed, the following steps should verify that virt-who is detecting all hypervisors and guest clients:
  1. Log in to the Satellite.
  2. Click on Systems to go to the Systems Overview page.
  3. Click on a system name.
  4. Check the following information on the System Details page:
    • Checked-In Time - this field should update every time virt-who is run.
    • System ID - this should match the system ID of the guest client in the hypervisor.
    • Guests - this column is located in the Virtualization subtab. All guest machines from the hypervisor should be listed in this section:
      • Systems that are not registered to the Satellite will appear as "virtual machine from [VMTYPE] hypervisor [UUID]" For example, "VM from esx hypervisor 92ffdfd8-14a2-11e3-ad37-a213e27ebfdc"
      • Systems that are registered to the Satellite will reflect the name given at registration and will link to the Satellite's records of the registered system

Chapter 5. Major Corrections

Major bug fixes for Red Hat Satellite 5.6.
The Red Hat Satellite Proxy did not work properly if separated from a parent by a slow enough network. Consequently, users who attempted to download large repodata files and RPMs experienced timeouts. This update changes both Red Hat Satellite Proxy and Red Hat Enterprise Linux Satellite Client to obey a configured timeout value for connections.

For the Red Hat Satellite Proxy server, the config option to set is proxy.timeout within file /etc/rhn/rhn.conf

For the Red Hat Enterprise Linux clients, the config option to set is timeout within file /etc/yum/pluginconf.d/rhnplugin.conf
Previously, Satellite disabled deferred_segment_creation from external Oracle databases. Satellite now allows external Oracle databases with the deferred_segment_creation feature enabled to be installed.
The spacewalk-report tool now comes with a new option --where-<column-id>. This option supports wildcard string matching useful for searching through the spacewalk-report contents. Wildcards are defined by the SQL standard of the Red Hat Satellite's database backend.
A Web UI subtab and API have been created in Satellite to allow Satellite administrators to view physical systems only, excluding virtual systems. This enhancement allows administrators to sort out physical machines from virtual ones, especially in large scale deployments where the list is very long. This is useful when planning firmware updates that can only be applied on physical hardware only.
Satellite 5.6 now logs Satellite user events. This enhancement tracks what users have done in the Satellite at what particular time.
Database changes from predefined tables are logged by the Satellite auditing feature. In time, the logging data could potentially grow too big and take up excessive disk space in the Satellite database. A new script enables Satellite to purge the audit-log tables on a user set date.
In an Inter-Satellite Synchronization (ISS) between a master and slave, satellite-sync removed any preset privacy attributes. This was being caused by the channel_access DB column, which was not being exported in the channel dumps. Non-identical OrgIDs between one Satellite to the other, which resulted in the database resetting the value to the default attribute ("private").

With Satellite 5.6 the ISS configuration has changed from the manual editing of rhn.conf to using the Web UI pages. The addition of the ability to map organizations from one Satellite to another preserves the organization and channel trust relationships as the content is exported. Preset privacy attributes are preserved during the export.
There was a discrepancy in date and time values when upgrading from 5.5 to 5.6. This discrepancy is due to database schema changes from 5.5 to 5.6. To fix this issue, the spacewalk-report tool now defaults all dates and time values to the UTC timezone to preserve date and time value consistency on database backend reports. Use the --timezone option to set custom time zones to take into account the scope of the report. The list of timezones is specified by Red Hat Satellite's database backend SQL standard.
Satellite 5.6 displayed all client system packages and provided links to all packages, even those not available on the Satellite. Clicking on unavailable packages on the Satellite would produce permission errors. Satellite 5.6 has provided a fix to the issue by rendering all packages not available on the Satellite as non-clickable.
The script previously known as check-oracle-space-usage.sh has been renamed to check-database-space-usage.sh. This scripts runs nightly as a standard cron job for Satellite.
The following changes have been made to the database in Satellite 5.6:
 - The default database directory has changed from /rhnsat/ to /var/lib/pgsql/
 - The datafiles will now extend/increase automatically and no longer require the manual administration to add additional data files for the database.
 - The extend option is no longer available for db-control.
 - The system administrator will need to monitor and administer to disk space allocation for the /var/lib/pgsql/ directory/partition.
 - The nightly cron-job check-oracle-space-usage, previously used to monitor the space allocation for Embedded Oracle, is now used to monitor the overall free space allocated to the partition where the /var/lib/pgsql/ resides.
The --keep-rpms option has been added to the command satellite-sync. When a Satellite administrator performs a satellite-sync on an export, --keep-rpms will prevent the removal of packages from the export after the process.
Satellite 5.6 now supports PostgreSQL database deployments as an option for external database users in addition to Oracle databases. The Satellite 5.6 Embedded Database is also PostgreSQL.
Satellite 5.6 has the ability to perform an online backup of Embedded and ManagedDB database instances. This is provided by the online-backup option to the command line db-control tool.
The Satellite search index engine stored cache data on local disk. For the Satellite 5.6 release, this location has changed from /usr/share/rhn/search/indexes to /var/lib/rhn/search/indexes .
Satellite 5.6 displays packages installed on a registered system which are not present in any of the system's subscribed channels with the option to remove these packages. Satellite 5.6 also displays systems that have extra packages installed.
The option --use-update-date has been added to the spacewalk-clone-by-date command. This option allows users to set the clone date to the date the cloned channel was last updated instead of the default issue date.
When reprovisioning a system on the Web UI, if the kickstart profile selected has partitioning options that might destroy existing attached disks, a warning is issued by the UI. Users are warned that all partitions, including logical disks on attached SANs, will be destroyed. Users are offered the option to remove the disks from the server before kickstarting the machine or edit the kickstart profile's "--clearpart" option.
Red Hat Satellite now scans all published errata for the reboot_required keyword and will display systems which have applied the errata but have not rebooted.
Previously, Enhanced Reporting integration did not include non-Red Hat-based hypervisors. The virt-who package, which is normally supplied within Red Hat Enterprise Linux 6 channels, is available as a technical preview within the RHN Tools channel as part of the Red Hat Satellite 5.6 release. Thus functionality sends the VMWare Host hypervisor information to the Satellite, allowing Host-Guest mappings. This is the same functionality provided in Red Hat Subscription Asset Manager and is a similar functionality provided by the rhn-virtualization-host package for RHEV-H, KVM and Xen Host-Guest mappings.
Satellite 5.6  has the ability to aggregate full SCAP results, collecting OVAL and XCCDF results into a fully downloadable HTML report for each scan. The extended information available in the report can help administrators investigate the possible causes of audit failure.

The organization administrator can configure this feature, setting up file size limits for individual SCAP files. This feature is turned off by default for each organization. It requires the latest spacewalk-oscap packages on the client systems in order to work properly.

Chapter 6. Known Issues

Known issues and workarounds found in Red Hat Satellite 5.6:
Previously, Satellite SCAP results could not be deleted. In Satellite systems where there are a great number of SCAP scans being performed, there is a degradation in web interface performance. The Satellite/Organization administrator may now choose the period of time that a SCAP scan will be retained. When a scan falls out of the retention period, the "delete scan" link appears in the scan details page. Scans from a specific system may also be deleted via the system's scan list page. Please note this feature is still a work in progress and has not been verified.
In Satellite 5.6, administrators can configure kickstart profiles to always point to the newest available kickstart tree, whether it is Red Hat provided or custom kickstart trees. This option can be set at a time of the kickstart profile creation or to an existing kickstart profile. Corresponding API methods have also been updated to add a new field that allows administrators to set the updating behavior. "Newest" is determined by the last modified date for the ks tree.

However, note that kickstart profiles created by directly uploading a ks file cannot use this feature. Since the applicable ks trees are unknown, it cannot be automatically updated.
Systems entitled with the management interface allow administrators to run commands on remote systems.  Prior to this update the output was only logged and available through the Satellite web interface. This change allows remote commands logging on both the Satellite and the system on which they were run. Please note this feature is still a work in progress and has not been verified.
The spacewalk-clone-by-date command does not trigger a repodata refresh task to be picked up by taskomatic immediately after cloning completes. If not other tasks are in queue, it takes approximately 10 minutes after cloning completes before the repodata is generated.

Chapter 7. Documentation Changes

Red Hat Satellite 5.6 documentation have undergone significant changes. Refer to the section below for a list of chapters that have been changed or moved.

7.1. Major Book Changes in the Installation Guide

New content for:
  • PostgreSQL embedded database requirements and installation
  • Enhanced Entitlements Reporting configuration
  • More Additional Requirements including File Permissions, Caching, and Entitlement Certificate Generation from the Customer Portal.
The following chapters have been moved to the Reference Guide:
  • Inter-Satellite Synchronization (merged with Multiple Satellites)
  • All troubleshooting sections

7.2. Major Book Changes in the Getting Started Guide

The following chapters have been moved to the Reference Guide:
  • Multiple Satellites
  • All troubleshooting sections

7.3. Major Book Changes in the Reference Guide

The following chapters have been moved to the Getting Started Guide:
  • Registering Systems to Satellite
  • Managing Virtualized Client Systems
  • System Provisioning
    • Activation Keys
    • Kickstarting
    • Provisioning as a Virtualized Guest
    • Cobbler
    • Reprovisioning
  • Organizations
    • Creating an Organization
    • Managing Organization Entitlements
    • Multiple Organizations
  • Channel Sharing
  • Errata
    • Applying Errata
    • Creating Errata
    • Managing Errata

7.4. Major Book Changes in the Channel Management Guide

The Channel Management Guide has been merged into the Getting Started Guide. The following sections from the Channel Management Guide can now be found in the Getting Started Guide:
  • Managing Base Channels and Child Channels
  • Creating and Managing Custom Channels
  • Pushing Content to Channels

7.5. Major Book Changes in the User Guide

The following chapter has been moved to the Installation Guide:
  • PAM Authentication
The following chapter has been moved to the Reference Guide:
  • RPMs
The following chapters have been moved to the Getting Started Guide:
  • Boot Devices
  • Organizations
    • Creating Organizations
    • Managing Entitlements
    • Configuring Systems in an Organization
    • Users of an Organization
    • Organizational Trusts

7.6. Major Book Changes in the Proxy Installation Guide

The following chapters have been moved to the Reference Guide:
  • RHN Package Manager and Serving Local Packages
    • Creating a Private Channel
    • Uploading Packages
  • Troubleshooting
    • Managing the Proxy Service
    • Log Files
    • Questions and Answers
    • General Problems
    • Host Not Found/Could Not Determine FQDN
    • Connection Errors
    • Caching Issues
    • Proxy Debugging by Red Hat

7.7. Major Book Changes in the Client Configuration Guide

The following chapter has been moved to the Reference Guide:
  • Importing Custom GPG Keys
The following chapters have been moved to the Getting Started Guide:
  • Using RHN Bootstrap
    • Preparing for RHN Bootstrap Installation
    • Generating RHN Bootstrap Scripts
    • Using the RHN Bootstrap Script
    • Configuring RHN Bootstrap Options
  • Manually Scripting the RHN Bootstrap Configuration
  • Sample Bootstrap Configuration

7.8. Major Book Changes in the API Overview

The following changes have been made to the API Overview:
  • The API have been converted to a Red Hat-branded book viewable in HTML, PDF and EPUB formats.
  • New Using XML-RPC with the Red Hat Satellite API chapter.
  • Updated list of methods.

Appendix A. Revision History

Revision History
Revision 0-9.401Thu Aug 20 2015Dan Macpherson
Mass publication of all Satellite 5.6 books
Revision 0-9.4002013-10-31Rüdiger Landmann
Rebuild with publican 4.0.0
Revision 0-9Thu Oct 17 2013Dan Macpherson
Update for cobbler buildiso requirements
Revision 0-8Fri Sep 27 2013Dan Macpherson
Final version of documentation suite
Revision 0-7Tue Sep 24 2013Dan Macpherson
Adding more details to New Features section.
Revision 0-6Mon Sep 23 2013Dan Macpherson
Final Known Issues and API changes
Revision 0-5Sat Sep 21 2013Dan Macpherson
Minor changes to Major Corrections
Revision 0-4Fri Sep 20 2013Dan Macpherson
Adding Major Revisions, Known Bugs, API Methods, New Reports, and New Features
Revision 0-03Wed Sep 18 2013Megan Lewis
Added further documentation change content.
Revision 0-02Wed Sep 18 2013Athene Chan
Added technical preview content.
Added documentation change content.
Revision 0-01Thu Aug 29 2013Athene Chan
Prepared document for publication.

Legal Notice

Copyright © 2013 Red Hat, Inc.
This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.