Bug 614593

Summary: Add to Satellite Guide - Running on virtual instances
Product: Red Hat Satellite 5 Reporter: Clifford Perry <cperry>
Component: DocumentationAssignee: John Ha <jha>
Status: CLOSED CURRENTRELEASE QA Contact: Martin Minar <mminar>
Severity: medium Docs Contact:
Priority: high    
Version: 540CC: adstrong, mkoci, mminar
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: Fixed in the 5.4.0 Release - GA'd 2010-10-27
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 614594 (view as bug list) Environment:
Last Closed: 2010-10-28 14:57:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 608749, 614594    

Description Clifford Perry 2010-07-14 20:06:56 UTC
Description of problem:
With the release of Satellite 5.4 we plan to add a statement of support for Satellite, such that if Satellite is installed on a supported RHEL version + arch combination, and the RHEL OS is installed on a physical or virtualized environment that Red Hat supports for that OS version, then by default, Satellite Engineering also supports Satellite in that environment, even if we have not specifically tested it. 

Historically in the past we would only say 'supported' after doing exhustive testing on first Xen (Sat 5.1/5.2+), then VMware (Sat 5.3+) and KVM (Sat 5.3+), now we will include any virtualized environment, such as HyperV & Virtage. In short any published document from Red Hat for either RHEL 5 or 6 that indicates that Red Hat Support will support RHEL deployed in that environment is enough for Satellite to also be considered supported as well. 

I would suggest adding a text similar to the following to the requirements section for Satellite installation"

"Satellite can be installed on Red Hat Enterprise Linux 5 or 6 OS in any supported by Red Hat virtualized environment, this includes Xen, KVM & VMware. Please be aware that for production deployments we recommend for you to deploy Satellite as the sole application running on the underlying physical hardware to avoid contention issues. Functional support does not always equate to performance and you may need to carefully consider your virtualized environment of choice and tuning guide lines. "


Cliff. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 6 Martin Minar 2010-09-27 09:32:28 UTC
Verified in Satellite-5.4.0-RHEL5-re20100924.0.

Comment 7 Clifford Perry 2010-10-28 14:57:32 UTC
The 5.4.0 RHN Satellite and RHN Proxy release has occurred. This issue has been resolved with this release. 


RHEA-2010:0801 - RHN Satellite Server 5.4.0 Upgrade
https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10332

RHEA-2010:0803 - RHN Tools enhancement update
https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10333

RHEA-2010:0802 - RHN Proxy Server 5.4.0 bug fix update
https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10334

RHEA-2010:0800 - RHN Satellite Server 5.4.0
https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10335

Docs are available:

http://docs.redhat.com/docs/en-US/Red_Hat_Network_Satellite/index.html 

Regards,
Clifford