Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Metadata API to indicate cluster member specificity #14125

Open
edlerd opened this issue Sep 18, 2024 · 0 comments
Open

Metadata API to indicate cluster member specificity #14125

edlerd opened this issue Sep 18, 2024 · 0 comments
Assignees
Labels
Improvement Improve to current situation

Comments

@edlerd
Copy link
Contributor

edlerd commented Sep 18, 2024

Required information

  • Distribution: snap
  • Distribution version: 6.1

Issue description

The GET 1.0/metadata/configuration response should include an indicator if a field is global or cluster member specific, when LXD is clustered. This information should also be added to the documentation.

For instance, the key config.network-physical.network-conf.keys[18].parent has no notion of being specific per cluster member. When LXD is clustered, the key cannot be set without targetting a specific cluster member. See screenshot below for its current value.

image

@tomponline tomponline added the Improvement Improve to current situation label Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Improvement Improve to current situation
Projects
None yet
Development

No branches or pull requests

3 participants