You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both the keyserver and keyclients use the same /etc/homeworld/config directory for extracting the configuration of the cluster. I noticed this a potential problem when I tried to delete the keyclient configs from all the nodes in the cluster in Spire as part of #441, but as a result I deleted the keyserver's config on the supervisor as well.
This leads to spire having special cases for the supervisor node, especially when it comes to setting up the key-system, see platform/spire/src/setup.py.
A potential fix would be to separate the configurations of the keyserver and the keyclients, perhaps as subdirectories of /etc/homeworld/config.
This may make it easier to maintain Spire in the future.
The text was updated successfully, but these errors were encountered:
Both the keyserver and keyclients use the same
/etc/homeworld/config
directory for extracting the configuration of the cluster. I noticed this a potential problem when I tried to delete the keyclient configs from all the nodes in the cluster in Spire as part of #441, but as a result I deleted the keyserver's config on the supervisor as well.This leads to spire having special cases for the supervisor node, especially when it comes to setting up the key-system, see
platform/spire/src/setup.py
.A potential fix would be to separate the configurations of the keyserver and the keyclients, perhaps as subdirectories of
/etc/homeworld/config
.This may make it easier to maintain Spire in the future.
The text was updated successfully, but these errors were encountered: