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

Info about costs when instantiate a vm in Sunstone #6639

Open
2 of 3 tasks
dcarracedo opened this issue Jul 1, 2024 · 1 comment · Fixed by OpenNebula/docs#3170 or OpenNebula/docs#3169
Open
2 of 3 tasks

Comments

@dcarracedo
Copy link
Contributor

dcarracedo commented Jul 1, 2024

Description
When the user instantes a vm, should appear the costs of the memory, cpu and disks at the same way that appears on Ruby Sunstone.

To Reproduce

  1. Log in FireEdge Sunstone.
  2. Create a virtual machine template and fill cpu, memory and disk costs.
  3. Instantiate the template. The costs should appear as following Ruby Sunstone screenshot:
    image

image

Expected behavior
That the costs appears when the user tries to instantiate a template. Also, the cost should change if the user changes the value of cpu, memory or costs.

Additional tasks
Add a screenshot of the vm instantiate with costs in the Users and Gruops > Showback section:
Screenshot from 2024-07-12 12-50-38

Details

  • Affected Component: FireEdge Sunstone
  • Hypervisor: N/A
  • Version: 6.8

Progress Status

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

jimfreeman commented Sep 5, 2024

As the Cloud View is not currently available in new Sunstone, I also want to propose we add a total of the running costs as well to the VM deployment wizard on all views.

When using the old version of Sunstone, on the Cloud view, this was at the top of the page, but this would be really useful for end-users to be able to know what the total cost of building virtual machines would be whilst going through the deployment process.

jloboescalona2 added a commit to jloboescalona2/docs that referenced this issue Jan 23, 2025
jloboescalona2 added a commit to jloboescalona2/docs that referenced this issue Jan 23, 2025
@tinova tinova closed this as completed Jan 23, 2025
tinova pushed a commit to OpenNebula/docs that referenced this issue Jan 23, 2025
tinova pushed a commit to OpenNebula/docs that referenced this issue Jan 23, 2025
tinova pushed a commit to OpenNebula/docs that referenced this issue Jan 23, 2025
@tinova tinova reopened this Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment