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 1619673 - [RFE] feature request to schedule a capsule sync.
Summary: [RFE] feature request to schedule a capsule sync.
Keywords:
Status: CLOSED DUPLICATE of bug 1305040
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Foreman Proxy
Version: 6.3.0
Hardware: x86_64
OS: Linux
low
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-21 12:47 UTC by sandeep mutkule
Modified: 2021-09-09 15:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-21 17:06:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description sandeep mutkule 2018-08-21 12:47:07 UTC 
1. Proposed title of this feature request
Ans] Schedule capsule synchronization

2. What is the nature and description of the request?
Ans] Being able to plan sync of Satellite / Capsule. At this time, syncs are running as soon as we publish a new content view. If the capsule is behind a slow connection, it could impact production.

3. Why does the customer need this? (List the business requirements here)
Ans] The Satellite is in Tours, France. The Capsule is in Lyon, France. Bandwidth between Tours and Lyon is not high enough to support sync and the production. When Satellite and Capsule are syncing it use all the bandwidth. Production is impacted.

4. How would the customer like to achieve this? (List the functional requirements here)
Ans] N/A

7. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Ans] I think Red Hat can test it without us.

8. Is there already an existing RFE upstream or in Red Hat Bugzilla?
Ans] I don’t know.

9. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
Ans] Satellite 6.3.x ? 6.4 ? 6.5 ?

10. Is the sales team involved in this request and do they have any additional input?
Ans] IBM salesman and RedHat sales team are in Cc of this mail.

11. List any affected packages or components.
Ans] N/A

12. Would the customer be able to assist in testing this functionality if implemented?
Ans] We could help to testing if needed.
Comment 1 Rich Jerrido 2018-08-21 17:06:29 UTC 

*** This bug has been marked as a duplicate of bug 1305040 ***
Note You need to log in before you can comment on or make changes to this bug.