dave
/
docker-artifact
1
0
Fork 0
Code Issues 4 Pull Requests Releases Wiki Activity

Replication #2

New Issue
Closed
opened 2018-10-28 14:50:29 -07:00 by dave · 1 comment
dave commented 2018-10-28 14:50:29 -07:00
Owner
Copy Link

Support relaying builds to replicas of the repo.

Design:

  • Database push queue - when some new image is uploaded, have a queue entry added referencing it
  • Some periodic task watches this queue and calls a normal "POST /addpkg" request on targets
  • How to do multi-master?
  • If artifact already exists, return "409 Conflict". Sender accepts this as a success, receiver doesn't add to the replication queue.
Support relaying builds to replicas of the repo. Design: * Database push queue - when some new image is uploaded, have a queue entry added referencing it * Some periodic task watches this queue and calls a normal "POST /addpkg" request on targets * How to do multi-master? * If artifact already exists, return "409 Conflict". Sender accepts this as a success, receiver doesn't add to the replication queue.
dave commented 2020-01-30 23:33:33 -08:00
Author
Owner
Copy Link

no longer necessary with the current design

no longer necessary with the current design
dave closed this issue 2020-01-30 23:33:33 -08:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
dpedu/docker-provider
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: dave/docker-artifact#2
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?