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

Add SET_HOSTNAME value to the VM row information in FireEdge #6703

Closed
2 of 3 tasks
brodriguez-opennebula opened this issue Sep 2, 2024 · 0 comments · Fixed by OpenNebula/docs#3059
Closed
2 of 3 tasks

Comments

@brodriguez-opennebula
Copy link
Contributor

brodriguez-opennebula commented Sep 2, 2024

Description
When the context variable SET_HOSTNAME is added to a VM, the hostname is as important as the instance name. It is also more intuitive to search/identify a VM by its hostname

Use case

  • A VM with the context variable SET_HOSTNAME is created
  • In the VM view tab of fireedge this VMs appear with the instance name and, between parenthesis, the value of the SET_HOSTNAME context variable contents

Interface Changes
In fireedge, under the sunstone/vm path, every VM should show the context variable SET_HOSTNAME on parentheses after its instance name. The VM card needs to be expanded on to show additional information.

Additional Context

Progress Status

  • Code committed
  • Testing - QA
  • Documentation (Release notes - resolved issues, compatibility, known issues)
@tinova tinova added this to the Release 6.10.1 milestone Sep 3, 2024
vichansson added a commit to OpenNebula/docs that referenced this issue Sep 24, 2024
Signed-off-by: Victor Hansson <vhansson@opennebula.io>
@vichansson vichansson linked a pull request Sep 24, 2024 that will close this issue
2 tasks
@tinova tinova closed this as completed Sep 24, 2024
tinova pushed a commit to OpenNebula/docs that referenced this issue Sep 24, 2024
Signed-off-by: Victor Hansson <vhansson@opennebula.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants