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.

Sign up for GitHub

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

Jump to bottom

Flexible declaration of resources used by an edgeless_node at run-time #131

Closed

ccicconetti opened this issue Feb 1, 2024 · 1 comment · Fixed by #144

Assignees

Labels

Member

ccicconetti commented Feb 1, 2024

Currently, the settings of a node include the full list of resources that it hosts and their configuration, where applicable.

This does not scale well as new resources are being added, which is expected to happen soon (next few months).

I suggest changing the approach so that:

a node does not create any resource by default;
if a user wants to create a resource associated with a node, they add the relevant configuration to the TOML file.

ccicconetti added the edgeless_node label

ccicconetti self-assigned this

ccicconetti mentioned this issue

Stabilize Resource Abstraction #122

Open

Member Author

ccicconetti commented Feb 1, 2024

Linked: #122

ccicconetti linked a pull request

that will close this issue

Refactor edgeless_node_d TOML configuration file #144

Merged

ccicconetti closed this as completed in #144

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment