Re:Understanding Google’s File System (2020)
by rajamaka on Thursday September 01, 2022 @08:42AM
(#32675515)
I mean creating a lifecycle rule on a ln s3 bucket is pretty easy
Re:Understanding Google’s File System (2020)
by xyzzy_plugh on Thursday September 01, 2022 @10:58PM
(#32686089)
The scope is entirely different. You can't grant privileges to create lifecycle rules on a subtree of a bucket. You set the rules on the entire bucket.
It's practically useless by comparison.
Re:Understanding Google’s File System (2020)
by KaiserPro on Thursday September 01, 2022 @10:09AM
(#32676416)
yes, but its per bucket rather than namespace/key. plus IAMs is a pain in the arse to setup
Re:Understanding Google’s File System (2020)
by rfoo on Thursday September 01, 2022 @04:44PM
(#32682902)
> NFS style approaches assume that I will give every user an unprivileged user on their local machine
With Kerberos it kinda works, each client is bound to a UID instead of blindly trusting the client, but very few people nowadays deploy this ancient tech (and it's fragile).
Re:Understanding Google’s File System (2020)
by mohon on Thursday September 01, 2022 @08:44AM
(#32675530)
Is the permission also use Zanzibar? or is it using a different thing?
Re:Understanding Google’s File System (2020)
by pclmulqdq on Thursday September 01, 2022 @11:38PM
(#32686299)
If you work at G, you should be able to see how D does permissions by looking at its ACL checking code (start with one of the files in the D server code that defines an op, and you can get to the permissions code pretty quickly). There's a lot of code in Colossus/D that is special because it has to be able to come up in a nearly empty cluster.
I also miss being able to write files with /ttl=72h/ anywhere in the path and knowing they will be cleaned up automatically without me doing any more work. In contrast S3 just rots. Need to find an intern to write an SQS pipeline to schedule file deletions :)