Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1958115 - [RFE] - Red Hat Satellite 7.x High Availability and Sync Features
Summary: [RFE] - Red Hat Satellite 7.x High Availability and Sync Features
Keywords:
Status: CLOSED DUPLICATE of bug 1789905
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.9.0
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Devendra Singh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-07 08:59 UTC by Anand Jambhulkar
Modified: 2023-01-20 17:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-07 09:23:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.