Selection of feature requests following 6+ months of daily usage

[aioue]

Description

Hi!
Enterprise license user here (@nbi.ac.uk). I started using OpenNebula earlier this year and have been keeping notes of features I'd like to see:

• [Feature] [Sunstone UI] Add radio button options to migrate/live-migrate to automatically spread load or conserve hosts, like when instantiating
• [Feature] [Sunstone UI] Add option to simplify the power options for users, to suspend, stop, force stop, and terminate. (Match AWS/Google standards to reduce training requirements)
• [Feature] [Sunstone UI] Show "permission error: <API-FooMethod> not allowed" rather than no data when permissions are not sufficient. (Match AWS/Google standards)
• [Feature] [Sunstone UI] When there is enough horizontal space, add sparkline graphs to each VM in the VM list to show recent CPU, RAM, and disk usage
• [Feature] [Ansible Collection] community.general.one_vm instantiation from template should allow passing specific security groups by name, not just ID
• [Feature] [Ansible Collection] community.general.one_vm CPU_MODEL section should be supported
• [Bug/Feature] [Ansible Collection] one_template "Fetch the TEMPLATE by name" example doesn't work and asks for a template. Allow a wildcard and/or regex expression when searching
• [Feature] [opennebula-tools CLI] Allow ONE_AUTH env var to be the credentials string itself, as well as a path to the key
• [Feature] [opennebula-tools CLI] Better CLI error handling when run without elevated privileges e.g. rescue in split': bad URI -> ONE_URL not found. Are you root?
• [Feature] [opennebula-tools CLI] arm64 builds of the client tools (onevm, onetemplate etc)
• [Feature] [OpenNebula Knowledgebase] Refresh Guacamole KB article, add Linux VDI specific section, and confirm compatibility with the latest LTS (6.10)

Use case
Happy to explain use case on any features further.

Interface Changes

Additional Context

Progress Status

• Code committed
• Testing - QA
• Documentation (Release notes - resolved issues, compatibility, known issues)

[rsmontero]

@aioue THANK YOU very much for the feedback!!!

I'll comment on some of the suggested features:

1. ARM support. This is in our radar and something in our short term roadmap. We are aiming for full support of ARM architectures. Currently we have deamon/CLI builds, but had some problems to implement the full QA/Certification platform for ARM builds. We hopefully have this ready for 7.0. This is being track in Support for ARM architectures #5671, I'll mark this done as duplicated here.

2. Ansible. This is also one thing we want to improve. Our plan is a full redesign of the roles to better accommodate this new features. This effort is part of OneDeploy project. I copied your feedback there Consider implementing a set of OpenNebula modules in Python one-deploy#70. I'll mark this done as duplicated here, as well.

[rsmontero]

[Feature] [opennebula-tools CLI] Allow ONE_AUTH env var to be the credentials string itself, as well as a path to the key.

This feature implies some security issues. The environment of a process can be easily seen with any user, e.g. with ps. In general, it is not recommended to include passwords in an environment variable for this reason. What is your specific use case for this?

[rsmontero]

[Feature] [opennebula-tools CLI] Better CLI error handling when run without elevated privileges e.g. rescue in split': bad URI -> ONE_URL not found. Are you root?

When is this ONE_URL error shown? (i.e. what command are you running to get this error?) I think it may be related to the ansible modules

[aioue]

Thanks @rsmontero ! Appreciate your reply and actions. Good to know I didn't waste my time cataloging everything.

1. ARM support. Any chance of getting access to the arm64 CLI builds (onevm, onetemplate etc), please? That's all I really need at the moment. Nodes are all x86, but I manage them from ARM.

2. ONE_AUTH env var. I'm developing locally via a devcontainer, and everything is passed through via environment vars apart from the credentials where the credentials have to be injected into the filesystem. Would make things cleaner and more consistent to be able to pass user and pass as an env var. It's all running locally (the same security as if I was running the tools directly on my laptop terminal), so I 100% recognise the security implications for a remote VM, but I'd like to have the choice on my local machine.

3. ONE_URL error. Yes I wasn't clear. Happens when cli command e.g. onegate vm show is run on a marketplace Ubuntu image with the tools installed, but not executed by root (where the one-context vars are available).