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

Naming of 'Ethernet' within Address Ranges #6955

Open
3 tasks
jimfreeman opened this issue Feb 27, 2025 · 0 comments
Open
3 tasks

Naming of 'Ethernet' within Address Ranges #6955

jimfreeman opened this issue Feb 27, 2025 · 0 comments

Comments

@jimfreeman
Copy link

/!\ To report a security issue please follow this procedure:
[https://github.com/OpenNebula/one/wiki/Vulnerability-Management-Process]

Description

Less of a bug and more of a naming suggestion. When adding an address range to an Virtual Network, there is the option to select "Ethernet". While this is in our documentation, I feel it is not so clear for those using the Sunstone UI. I would like to suggest that, from a pure label perspective, we rename "Ethernet" to something like "Ethernet / DHCP", "Just MAC / DHCP", etc.

Or perhaps (incase there are underling areas that would be affected), we could provide an information bubble that can provide some more context to these Address Range options.

To Reproduce

  • Create Virtual Network
  • Click "Addresses"
  • Click "+ Address Range"
  • A dialogue box appears with the options to be selected

Expected behavior

Generally to make it more clear what the "Ethernet" option does. I believe the most popular use case for this is when an external DHCP server is used.

Details

  • Affected Component: Sunstone
  • Hypervisor: KVM (But probably related to all)
  • Version: 6.10.3

Additional context

N/A

Progress Status

  • Code committed
  • Testing - QA
  • Documentation (Release notes - resolved issues, compatibility, known issues)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants