-
Notifications
You must be signed in to change notification settings - Fork 3
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
Acquiring nodes should be made easier to the user #62
Labels
Comments
eduble
added a commit
that referenced
this issue
Feb 3, 2022
When a user creates a virtual node, it now belongs to him (before, it was created as "free", since it booted the default image of "waltplatform" user). This is a first improvement related to issue #62.
eduble
added a commit
that referenced
this issue
Feb 11, 2022
When a user creates a virtual node, it now belongs to him (before, it was created as "free", since it booted the default image of "waltplatform" user). This is a first improvement related to issue #62.
eduble
added a commit
that referenced
this issue
Mar 16, 2023
When a user creates a virtual node, it now belongs to him (before, it was created as "free", since it booted the default image of "waltplatform" user). This is a first improvement related to issue #62.
eduble
added a commit
that referenced
this issue
Mar 16, 2023
When a user creates a virtual node, it now belongs to him (before, it was created as "free", since it booted the default image of "waltplatform" user). This is a first improvement related to issue #62.
eduble
added a commit
that referenced
this issue
May 2, 2023
This commit also introduces the keyword 'free-nodes', for use in `walt node acquire free-nodes` for instance. Fixes #62.
eduble
added a commit
that referenced
this issue
May 2, 2023
This commit also introduces the keyword 'free-nodes', for use in `walt node acquire free-nodes` for instance. Fixes #62.
eduble
added a commit
that referenced
this issue
May 15, 2023
This commit also introduces the keyword 'free-nodes', for use in `walt node acquire free-nodes` for instance. Fixes #62.
eduble
added a commit
that referenced
this issue
May 15, 2023
This commit also introduces the keyword 'free-nodes', for use in `walt node acquire free-nodes` for instance. Fixes #62.
eduble
added a commit
that referenced
this issue
May 30, 2023
This commit also introduces the keyword 'free-nodes', for use in `walt node acquire free-nodes` for instance. Fixes #62.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Node owership and how to acquire nodes may seem complicated at first for the new user. It should be improved.
Currently,
walt node create
creates virtual nodes with their default imagewaltplatform/<node-type>-default
, thus they appear asfree
nodes and they do not belong to the user who creates them. They are hidden when user typeswalt node show
without--all
option, which is quite unexpected.This could be changed by associating these new virtual nodes to image
<user>/<node-type>-default
instead. If this image is missing, it would be automatically cloned from default imagewaltplatform/<node-type>-default
.A command
walt node acquire <node-set>
should also be provided.It would do the following:
<node-set>
belong to another user (i.e. a real user, notwaltplatform
), ask confirmation, and if yes, continue.<node-set>
already belong to current user, a warning would be printed and these nodes would be ignored in the following step<user>/<node-type>-default
(cloned if missing, as for virtual nodes above) and then rebooted.A keyword
free-nodes
could be introduced, to allow for instancewalt node acquire free-nodes
.Help message of
walt node show
when user has no nodes yet should be updated to proposewalt node acquire
.walt node show
could have another option--free
to show free nodes only, and not the nodes belonging to other users.A command
walt node release <node-set>
could also be proposed as an alias towalt node boot <node-set> default
.The text was updated successfully, but these errors were encountered: