swift-object-server(1)
β¨ swift-object-server(1) β¨
okay bestie, sit DOWN because we're about to talk about the OpenStack Swift object server and it's genuinely iconic π (this is the swift-object-server page from the OpenStack Swift manual, btw β iykyk)
πΈ NAME πΈ
swift-object-server β OpenStack Swift object server. that's it. that's the name. short, sweet, slays. π
π SYNOPSIS π
swift-object-server [CONFIG] [-h|--help] [-v|--verbose]
so you run the thing, you optionally hand it a CONFIG, and you've got -h|--help and -v|--verbose if you need them. periodt. β¨
π¦ DESCRIPTION π¦
The Object Server is a very simple blob storage server β and when i say simple i mean it, no cap. its whole job description is: store objects, retrieve objects, delete objects, all on your local devices. three things. main character energy but make it minimal. π
Here's the tea on how it actually stores stuff π: objects live as binary files on the filesystem, and the metadata lives in the file's extended attributes (xattrs). that's the whole architecture. it's giving "i put your data here and i wrote a lil note on it."
β οΈ IMPORTANT bestie: this means the underlying filesystem you pick for your object servers has to support xattrs on files. some filesystems, like ext3, have xattrs turned off by default π so double check that before you come crying to me.
Each object gets stored using a path derived from the object name's hash plus the operation's timestamp. and the golden rule? last write always wins π which guarantees the latest object version is the one that gets served. no ambiguity, no drama, no "wait which one is current" β the newest one ate, and it's serving. π₯
Deletions get the same treatment, which is lowkey genius: a deletion is also treated as a version of the file. specifically, it's a 0 byte file ending with .ts β and .ts stands for tombstone π (spooky but functional). why bother? because this ensures deleted files are replicated correctly and older versions don't magically reappear due to failure scenarios. no zombie objects in THIS house. π§βοΈπ«
π DOCUMENTATION π
want more depth? more lore? more of the good stuff? the in-depth docs about swift-object-server β and about OpenStack Swift as a whole β live at:
go read them, they're right there, treat yourself π«Ά
β SEE ALSO β
object-server.conf(5)β the config file bestie, go look at it
k bye love u, go store some blobs responsibly πβ¨ππ¦πΈπ
this was the swift-object-server(1) page β part of OpenStack Swift, on Linux, dated 8/26/2011 πΈ
π¦ where this page comes from
- debian bookworm: swift-object 2.30.1-0+deb12u1 Β· Apache-2
- debian bookworm: swift-object 2.30.1-0+deb12u3 Β· Apache-2
- debian trixie: swift-object 2.35.1-0+deb13u3 Β· Apache-2
- debian trixie: swift-object 2.35.1-0+deb13u4 Β· Apache-2
- nixos 26.05: python3.13-swift 2.37.1
- nixos 26.05: python3.14-swift 2.37.1
- nixpkgs unstable: python3.13-swift 2.38.3
- nixpkgs unstable: python3.14-swift 2.38.3
- ubuntu jammy: swift-object 2.29.1-0ubuntu1 Β· Apache-2
- ubuntu jammy: swift-object 2.29.2-0ubuntu1.1 Β· Apache-2
- ubuntu noble: swift-object 2.33.0-0ubuntu1 Β· Apache-2
- ubuntu noble: swift-object 2.33.0-0ubuntu1.1 Β· Apache-2
- ubuntu questing: swift-object 2.36.0-0ubuntu1
- ubuntu questing: swift-object 2.36.0-0ubuntu1.1
- ubuntu resolute: swift-object 2.37.1-0ubuntu2 Β· Apache-2
- ubuntu resolute: swift-object 2.37.1-0ubuntu2.1 Β· Apache-2
- ubuntu stonking: swift-object 2.38.2-0ubuntu1 Β· Apache-2
- Copyright (c) 2010-2011 OpenStack Foundation
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms