Support credentials update with GSet scheme #135
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-s3-gw#135
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Is your feature request related to a problem? Please describe.
Accessbox is an object that contains bearer tokens signed for specific gateway keys. Address of accessbox object (cid/oid) is used as access key id for S3 credentials. There is a case when storage network is expanded with new S3 gateways. New S3 gateways can't use existing accessboxes because they don't contain suitable bearer tokens. The only way to handle this case is to issue new tokens.
Describe the solution you'd like
Use 2PSet object versioning scheme for accessbox objects.
S3 Gateway:
Filename
of access key id in the accessbox container.S3 Authmate:
Describe alternatives you've considered
Tree service looks like a suitable place for accessbox versions, but there are some concerns on tree service data restore after the loss. So tree service isn't preferable option here.
Additional context
It takes about 5-6 seconds to find latest version of the accessbox out of 1000 versions with 2PSet. Seems okay for now.
It seems we are about to use
GSet
(not2PSet
)Support credentials update with 2PSet schemeto Support credentials update with GSet schemeAccessBox
latest version #335