Bug 880669
| Summary: | RFE: satellite-sync should be able to fully synchronize content between two SW-servers | ||
|---|---|---|---|
| Product: | [Community] Spacewalk | Reporter: | Stepan <rogov> |
| Component: | Server | Assignee: | Tomas Lestach <tlestach> |
| Status: | CLOSED DEFERRED | QA Contact: | Red Hat Satellite QA List <satqe-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.8 | CC: | failshell, mzazrivec, rbremer |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
Feature:
satellite-sync should be be able to synchronize also kickstarts profiles, kickstart distributions, SSL keys and activation keys for custom channels(not only for official Red Hat content).
Reason:
This can be useful in case of bad connection, or if possible just a temporary connection between the spacewalk servers. In cases where the proxy is not enough, because proxy refers to the primary server for repositories metadata, packages are not in the cache and kickstarts.
Result (if any):
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-03-23 12:22:13 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 737830 | ||
|
Description
Stepan
2012-11-27 14:58:36 UTC
I too am looking for this functionality. I am currently trying to build a hub and spoke model of geographically separated spacewalk servers that all sync from the hub. This allows for local kickstart, meta data, and errata to be hosted on each spacewalk spoke system instead of going to the hub (as would happen with a spacewalk proxy). It looks like the functionality is there, just that anything that is not an official "Redhat" distribution is marked as NON-RELAVENT. I would expect a satellite-sync to be capable of completely syncing 2 spacewalk systems. I would need that feature also. I'm disappointed to find out it does not. Especially after deploying a second server. I too am looking for this as the growth of spacewalk added additional non-rhel distributions into its capability mix this functionality is a necessity. For a network with multiple operating centres this is a major drawback for a Spacewalk implementation. From this enhancement request it looks like it is not even on the roadmap yet. +1 for needed functionality Spacewalk project as an upstream for Red Hat Satellite 5 product is going to be End Of Life on May 31 2020. Spacewalk 2.10 has been released as the last release of this project. https://github.com/spacewalkproject/spacewalk/wiki/ReleaseNotes210 Any new feature will not be included therefore closing remaining RFEs to set expectations properly. |