swift-container-sync(1)

πŸ¦‹ swift-container-sync(1) πŸ¦‹

hi bestie!! you just opened swift-container-sync(1), straight out of the OpenStack Swift manual, and honestly? it's giving background-mirroring main character energy. let's get into it πŸ’…


✨ NAME ✨

swift-container-sync β€” OpenStack Swift container sync. that's the whole vibe. it syncs containers. periodt. πŸŽ€


πŸŽ€ SYNOPSIS πŸŽ€

swift-container-sync [CONFIG] [-h|--help] [-v|--verbose] [-o|--once]

so you've got a CONFIG argument, plus three little flags: -h / --help, -v / --verbose, and -o / --once. that's it, that's the lineup. copy it character for character, bestie, i don't make the rules 🌸


πŸ’– DESCRIPTION πŸ’–

okay so here's the tea, and it's genuinely good tea:

Swift has a feature where all the contents of a container can be mirrored to another container through background synchronization. iconic, no notes.

Swift cluster operators configure their cluster to allow/accept sync requests to/from other clusters, and the user specifies where to sync their container to along with a secret synchronization key. a SECRET. SYNCHRONIZATION. KEY. iykyk πŸ”‘

so what does swift-container-sync actually do? it does the job of sending updates to the remote container. no cap. and the way it pulls that off is:

  • it scans the local devices for container databases πŸ”
  • and it checks for x-container-sync-to and x-container-sync-key metadata values

and if those exist? newer rows since the last sync will trigger PUTs or DELETEs to the other container. boom. that's the whole mechanism. it's literally that. 🫢


πŸ“š DOCUMENTATION πŸ“š

want the deep lore? more in depth documentation in regards to swift-container-sync, and also about OpenStack Swift as a whole, can be found at:

go read them, they're lowkey worth it 🌈


πŸ‘€ SEE ALSO πŸ‘€


okay bestie that's the whole page, we ate and left no crumbs πŸ‘‘ this one's from the Linux manual, dated 8/26/2011, and it belongs to OpenStack Swift. byeeee, go sync something πŸ’œβœ¨