Ensure repositories are in sync across replicas
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
As a user managing multiple large scale pulp instances I need to be able to insure replicas are in sync with one another.
I want to be able to observe some value like a check sum for each of the repositories being synced that I can compare OR have some other metric that can show that a repository is in sync with the main repository.
This can be important when rolling out changes and knowing the state of each replica.
We could use the existing API to gather some metrics for each repository but this probably would not give us total confidence repositories were fully in sync.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing API and how it exposes repository synchronization state. Determine whether a repository checksum or another metric can provide sufficient confidence that each replica matches the main repository. Done means defining and implementing a reliable way to compare synchronization state across replicas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100