Re:Zanzibar: Consistent, Global Authorization System
by jamesblonde on Saturday June 08, 2019 @06:33PM
(#20135644)
And they reveal exactly zero details. I know a bit about it, but not enough to say exactly what semantics it offers to file system clients. I believe it is not POSIX-like, hence the need to layer Spanner and GCS over it.
[ Parent
| on HN ]
Re:Zanzibar: Consistent, Global Authorization System
by shereadsthenews on Saturday June 08, 2019 @07:36PM
(#20135927)
There's been a teensy bit more details than that, e.g. [1]. If you think about exactly the file semantics that Bigtable would require (append, pread) that's exactly what is provided. Note that Colossus and D are two separate things. Google systems can use D without Colossus and a long time ago people used Colossus without D, although today Colossus/D is implied. The presentation gives the broad strokes of how Colossus is able to bootstrap itself from Chubby. It helps if you've also read the Bigtable paper [2].
1: http://www.pdsw.org/pdsw-discs17/slides/PDSW-DISCS-Google-Ke... 2: https://static.googleusercontent.com/media/research.google.c...
Re:Zanzibar: Consistent, Global Authorization System
by the-rc on Saturday June 08, 2019 @08:25PM
(#20136138)
??? The original GFS paper, which the chat references repeatedly, was clear about the semantics not being POSIX-like. The interview mentions that, too, along with stuff like snapshots. Colossus is basically the same, with increased scalability.