All Red Hat customers are eligible (though customers without active Satellite subscriptions will need to contact support rather than using the self-service enrollment form, and we encourage Beta users to open tickets through Red Hat support.
Satellite executes what would traditionally be called “systems management” work related to Red Hat infrastructure on bare metal, virtualized or on in the cloud. Many organizations leverage both Satellite and CloudForms to provide end-to-end management of their infrastructure. CloudForms provides a centralized view and centralized control/orchestration of all workloads across private and public cloud infrastructures. Satellite performs software management, configuration management, subscription management & provisioning for Red Hat infrastructure. Both are offered as components of Red Hat Cloud Infrastructure (RHCI), an integrated set of Red Hat technologies.
Red Hat Satellite 5.5 and earlier versions are no longer supported. Red Hat Satellite and Proxy 5.6 and 5.7 support ends in January 201@Extended Lifecycle Support (ELS) for Satellite/Proxy 5.8 can be purchased to extend support until the end of May 2020.
Red Hat Satellite Proxy Server as a federation device for Red Hat Satellite has been replaced by Red Hat Satellite Capsule Server. The capsule server is similar to the proxy server, but uses a different architecture. If you are transitioning from Red Hat Satellite 5 to Red Hat Satellite 6, any deployed proxy servers must also be transitioned to capsule servers.
Yes, high availability is documented and supported through a certified Red Hat reference architecture. This reference architecture provides step-by-step instructions for deploying a Red Hat Enterprise Linux cluster for Red Hat Satellite Server, as well as a combination of Red Hat Enterprise Linux cluster and load balancing to support an active/active and highly available capsule.
June 15, 2016.
Beta releases are made available only for testing purposes. Red Hat provides Beta releases and revisions from Beta repositories. This Beta is not an officially supported repository, and these releases cannot be considered for a production environment.
Key projects include: Foreman, Puppet, Katello, Pulp, and Candlepin.
Red Hat Satellite executes what would traditionally be called system management work—related to Red Hat infrastructure—on bare metal, virtualized servers, or in the cloud. Many organizations use both to provide end-to-end infrastructure management. Red Hat CloudForms provides a centralized view and control or orchestration of all workloads across private and public cloud infrastructures while Red Hat Satellite performs software, configuration, and subscription management, as well as provisioning for Red Hat infrastructure. Both products are offered in Red Hat Cloud Infrastructure, an integrated set of Red Hat technologies.
Yes. There is no direct upgrade available from Beta 1 to Beta @Some improvements and enhancements have been made related directly to installation, so the customer experience related to Beta 2 install should be improved from Beta @For customers who want the best experience, we highly recommend Beta @The entire community of Satellite users can also benefit from the feedback.
1) Supported upgrade paths for Satellite 6.2 GA:
2) Unsupported upgrade paths:
3) Capsule needs to be the same version as Satellite i.e. cannot run Capsule 6.1 with Satellite 6.2 or vice versa.
Red Hat Satellite 6.2 GA: July 27, 2016
Red Hat Satellite 6.1 GA: August 12, 2015
Red Hat Satellite 6.0 GA: September 10, 2014
No, Beta 2 must be a new installation.
Bare metal, Red Hat Enterprise Virtualization, Red Hat OpenStack® Platform, and VMWare.
All Red Hat Satellite components (such as Foreman, Puppet, Katello, Pulp, and Candlepin) and their usage are supported within the context of Red Hat Satellite only. Third party usage of any components falls beyond supported usage.
Red Hat Satellite 6 includes a redesigned product architecture to manage new types of content on a wide variety of platforms, including bare-metal, private, and public clouds. Red Hat Satellite 6.2 builds on that release with the following features:
For customers with active Satellite subscriptions, enrollment in the public Beta is self-service via Customer Portal : just log in as an Org Admin user, and click on the "Enroll" button on the Public Beta Landing Page and complete the form.
Once successfully enrolled, participants will be have the following subscriptions added to their account:
The public Beta release will add the following entitlements to the customer’s account:
April 27, 2016.
The Satellite 6.2 public Beta is supported in non-production settings at a Severity 4 level.
Yes. You can continue the original Satellite 6.2 Beta (released April 28). Per standard guidelines with Red Hat Beta programs, those subscriptions will expire 90 days after being deployed. We do encourage you to instead download Beta 2, which can be deployed for the remainder of the 90 day Beta subscription.
Please note: Beta 2 bits will be published to the same Beta repository, but are not compatible with the initial Beta. If you wish to remain on the initial Beta, you will need to disable further updates from this repository. Once you decide to try Beta 2, you can re-install (see: Can I upgrade from Public Beta 1 to Public Beta 2?
Beta 2 includes numerous fixes and enhancements, including the following:
Yes. Red Hat Satellite versions 5.6 and above are capable of RHEL 7 content and systems management.
The product architectures differ between Red Hat Satellite 5 and Red Hat Satellite @Red Hat Satellite 6.x releases requires a fresh install. As a result, upgrading in place from Red Hat Satellite 5.x to Red Hat Satellite 6.x is not possible. Current Red Hat Satellite 5 customers will have many options to manage their Red Hat Enterprise Linux environment with Red Hat Satellite 6.