Optimum Satellite Capsule sync strategies

Solution Verified - Updated

Environment

  • Red Hat Satellite 6.9

Issue

  • Which Capsule sync strategy is the most optimum after publishing and promoting content in Satellite?

Resolution

  • There are two methods you can adopt for syncing Satellite Capsules.

  • Option A:

    1. By default, each Content View (CV) and Composite Content View (CCV) promotion automatically triggers a sync job to each Capsule.

  • Option B:

    1. Disable automatic Capsule sync.
    2. Promote all the content in Satellite
    3. Sync the Capsules at the end of the last CV or CCV to be promoted.
    4. Re-enable automatic Capsule sync.

  • Both options work well and Red Hat does not recommend one over the other as a preferred option.

  • Note: Option A might redundantly trigger some Capsule syncs that will be replaced by a new content sync e.g. if you re-publish/promote some content several times.

  • Note: Option B gives you more control, but the Capsule sync might redundantly attempt to sync other repositories which are already synced on the Capsule.

    • With this option it can be argued that resource contention is reduced as the publish/promote and Capsule sync tasks are not running at the same time.
    • Due to the optimisations made and the possible repetitive CV publish/promotes that would trigger redundant Capsule syncs in option A, this gives option B a slight edge.

  • Satellite 6.9 added a number of improvements for Capsule sync.

For more KB articles/solutions related to Red Hat Satellite 6.x Capsule Sync Issues, please refer to the Consolidated Troubleshooting Article for Red Hat Satellite 6.x Capsule Sync Issues

SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.