Bug 1958115

Summary: [RFE] - Red Hat Satellite 7.x High Availability and Sync Features
Product: Red Hat Satellite Reporter: Anand Jambhulkar <ajambhul>
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Devendra Singh <desingh>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.9.0CC: aperotti, ehelms
Target Milestone: UnspecifiedKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-06-07 09:23:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Anand Jambhulkar 2021-05-07 08:59:43 UTC 
Description of problem:
----------------------

For upcoming Satellite 7.x major release the customer would like to ask some HA features not at the moment available in Satellite 6.x:

1) Satellite Master HA: we need the master machine not to be unique but, even in a master/slave pattern, have a continous alignment between 2 (or more) instances. This would allow Satellite to be deployed on physical machines or other cloud/virtualization platforms that don't have stretched storage backend.

2) Capsule Sync: at the moment, when Satellite syncs upstream repos, or a user uploads an RPM to the master, the capsule are not immediately synced and that's no option to force that specific repo/package sync, nor an API to monitor if a specific repo/rpm is synced everywhere. This makes impossible to make Satellite capsule the central repo in a build pipeline (I create rpm, push to satellite, install on a machine for automatic test).
Comment 1 Andrea Perotti 2021-06-07 09:23:53 UTC 

*** This bug has been marked as a duplicate of bug 1789905 ***