Red Hat Satellite

The implementation process for Red Hat Satellite involves:

1. Server Preparation: Install RHEL on a VM/bare metal with minimum 4 cores, 20+ GB RAM, and storage (400+ GB recommended).

2. Satellite Installation: Use satellite-installer after enabling required repositories1314. Initial configuration (DNS, DHCP, organizations) takes ~1-2 hours.

3. Content Synchronization: Sync repositories from Red Hat CDN or custom sources. This can take 4-6 hours for initial syncs, depending on network speed and repository size.

4. Lifecycle Configuration: Create content views, activation keys, and lifecycle environments.

5. Host Registration: Register clients via global registration or activation keys.

Total time ranges from 6-12 hours for basic setups, with larger deployments (e.g., multi-Capsule) taking days due to content replication.

Red Hat Satellite supports extensive customization:

• UI Customization: Modify headers/footers via rhn.conf and add plugins (e.g., Foreman plug-ins).

• Content Management:

  • Create custom RPM repositories, channels, and sync third-party content (e.g., PostgreSQL).

  • Use SCAP tailoring files to adjust compliance policies.

• Provisioning: Customize Kickstart templates with snippets and integrate Ansible roles for post-provisioning.

• Security Policies: Define custom OpenSCAP profiles.

• API/CLI Integration: Automate via Hammer CLI or REST API.

• Subscription Costs: Priced per socket (e.g., ~$1,813.90 for Satellite bundles). Virtual deployments may use "Virtual Data Center" subscriptions.

• Support: Included with subscriptions; premium support (e.g., 24/7) may incur extra fees.

• Training: Courses like RH404 (~$4,700) or RH053 (free overview).

• Setup: No explicit setup fees, but infrastructure costs (server resources, storage) apply.

• Training:

• • RH053 (Technical Overview): Free on-demand videos.

  • RH403 (Administration): 5-day lab-based course with exam.

• Support:

  • Included 24/7 with subscriptions.

  • Access to Technical Account Managers (TAMs) for critical issues.

  • Community forums and extensive documentation.

• Compliance Auditing: OpenSCAP integration for CIS, HIPAA, PCI-DSS.

• Encryption: SSL/TLS for content sync and client communication.

• Access Control: Role-based permissions and LDAP/AD integration.

• Patch Management: Automated security updates via sync plans.

• Minor Updates: Released every ~3 months (e.g., 6.15 → 6.16), applied via satellite-maintain.

• Major Upgrades: Annual releases; require planning and downtime.

• Management: Use sync plans for automated repository updates and Capsule Servers for staged rollouts.

• Ownership: Customers retain full ownership of data.

• Portability: Export/import manifests and content views for migration. Custom RPMs and SCAP content can be extracted.

• Vertical Scaling: Upgrade server resources (CPU/RAM) as needed.

• Horizontal Scaling: Add Capsule Servers for geographic distribution.

• Subscription Flexibility: Adjust socket counts via Customer Portal.

• Renewal: Annual subscriptions; auto-renewal options available.

• Cancellation: Subscriptions can be terminated, but refunds only for unopened physical media within 30 days.

• End-of-Life Policy: Versions supported for 6-18 months; N-2 support policy.

• Industry Standards: FIPS 140-2, HIPAA, PCI-DSS, GDPR.

• Certifications: NIST SCAP, OSPP, CIS benchmarks.

• Audit Tools: Integrated OpenSCAP reporting and dashboards.