Chapter 3. Release Information

Previously, the virt-who daemon recognized any file in the /etc/virt-who.d/ directory as a potential configuration file, regardless of extension. With the release of Red Hat Satellite 6.2.9 and virt-who version 0.19 and above, only files with the .conf extension are now recognized as potential configuration files. All configuration files without the .conf extension must be updated to include this extension.

Previously, the virt-who daemon recognized any file in the /etc/virt-who.d/ directory as a potential configuration file, regardless of extension. With the release of Red Hat Satellite 6.2.9 and virt-who version 0.19 and above, only files with the .conf extension are now recognized as potential configuration files. All configuration files without the .conf extension must be updated to include this extension.

Red Hat Satellite 6.2 upgrades to the 3.8 stream of puppet.

Red Hat Satellite 6.2 upgrades to the 3.8 stream of puppet.

This release introduces the ability to export content from one Satellite Server and import it into another server. The content can come from the Library, or can be from a content view. This feature can be used to support populating an air-gapped server with content from another server.

This release introduces the ability to export content from one Satellite Server and import it into another server. The content can come from the Library, or can be from a content view. This feature can be used to support populating an air-gapped server with content from another server.

With this release, the virt-who agent can now be installed on the same machine where the main Satellite Server is hosted.

With this release, the virt-who agent can now be installed on the same machine where the main Satellite Server is hosted.

With this release, the default root password hash has been made SHA256 instead of MD5. This improves the default security of all provisioned hosts.

With this release, the default root password hash has been made SHA256 instead of MD5. This improves the default security of all provisioned hosts.

This release adds a Remote Execution feature that allows users to execute commands against machines under inventory. The commands can be stored as jobs, and can be scheduled to run in the future or on a recurring basis.

This release adds a Remote Execution feature that allows users to execute commands against machines under inventory. The commands can be stored as jobs, and can be scheduled to run in the future or on a recurring basis.

With this release, a "Test Connection" button was added to verify LDAP connection information.

With this release, a "Test Connection" button was added to verify LDAP connection information.

A bootstrap script has been included with Red Hat Satellite 6.2. This script takes a machine that has been provisioned outside of Red Hat Satellite 6.2 and registers the host, installs the appropriate certificates, and configures puppet. If the host was previously registered with Red Ht Satellite 5, the script selects the correct subscriptions based on the channels that are assigned to the host.

A bootstrap script has been included with Red Hat Satellite 6.2. This script takes a machine that has been provisioned outside of Red Hat Satellite 6.2 and registers the host, installs the appropriate certificates, and configures puppet. If the host was previously registered with Red Ht Satellite 5, the script selects the correct subscriptions based on the channels that are assigned to the host.

The hammer command now supports defaults, which can be stored on the file system to make it easier to execute multiple hammer commands in a single session.

The hammer command now supports defaults, which can be stored on the file system to make it easier to execute multiple hammer commands in a single session.

With this release, the content dashboard in Red Hat Satellite 6.1 has now been combined into the main dashboard, providing a single point of summary information for the user.

With this release, the content dashboard in Red Hat Satellite 6.1 has now been combined into the main dashboard, providing a single point of summary information for the user.

With this release, users of Red Hat Satellite 6.2 can sync down repositories protected by basic authentication by providing the username and password in the repository string.

With this release, users of Red Hat Satellite 6.2 can sync down repositories protected by basic authentication by providing the username and password in the repository string.

With this release, content view versions in Red Hat Satellite 6.2 have been improved to show the version of the puppet module that is included.

With this release, content view versions in Red Hat Satellite 6.2 have been improved to show the version of the puppet module that is included.

With this release, the backup script has been updated to perform incremental backups of the raw packages. This speeds up all subsequent backups.

With this release, the backup script has been updated to perform incremental backups of the raw packages. This speeds up all subsequent backups.

With this release, the backup script has been updated to allow for backing up database information. This option improves backup performance for users whose packages are stored on backed-up file systems.

With this release, the backup script has been updated to allow for backing up database information. This option improves backup performance for users whose packages are stored on backed-up file systems.

As part of upgrading to the latest Puppet 3.x version, the hiera package has now been updated to 1.3.

As part of upgrading to the latest Puppet 3.x version, the hiera package has now been updated to 1.3.

This release introduces the ability to provision Red Hat Atomic Host in addition to standard Red Hat Enterprise Linux. This includes syncing down Atomic Content, promoting that content through a lifecycle environment, and provisioning Atomic Hosts.

This release introduces the ability to provision Red Hat Atomic Host in addition to standard Red Hat Enterprise Linux. This includes syncing down Atomic Content, promoting that content through a lifecycle environment, and provisioning Atomic Hosts.