feat: add optional fs-uuid parameter for database initialization #14
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rustybee42
requested changes
May 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are some scenarios where it is helpful to define the
FsUUIDupfront before we have a fully functioning management service. For example when deploying BeeGFS instances using the new BeeGFS Agent service it complicates things if we have to rollout the management service first, determine theFsUUID, then roll out the remaining services. This makes stateless/idempotent reconciliation of file systems impossible as we have to remember if the management service has been initialized and anFsUUIDgenerated.For the example of the BeeGFS Agent, the proposed approach is to have users provide a manifest to CTL that contains one or more file systems mapped by
FsUUID. It is TBD if we will reuse the user definedFsUUIDor always have CTL generate those and insert them into the user manifest.