Skip to content

Provide a Checksum box for Template/ISO registration #9843

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

Closed
kiranchavala opened this issue Oct 23, 2024 · 1 comment · Fixed by #10725
Closed

Provide a Checksum box for Template/ISO registration #9843

kiranchavala opened this issue Oct 23, 2024 · 1 comment · Fixed by #10725

Comments

@kiranchavala
Copy link
Contributor

ISSUE TYPE

Improvement request

COMPONENT NAME

Component: Improvement, UI

CLOUDSTACK VERSION

Cloudstack version 4.19.1

SUMMARY

Provide a Checksum box for Template/ISO registration

Currently, Md5/Checksum textbox is shown only during the following methods in the UI

  1. Registration of direct download enabled Template

Checksum-DirectDownload template

  1. Registration of Kubernetes ISO

Checksum-kubernetesiso

  1. Volume registration via URL

Checksum-Volume register

  1. Volume Upload

Checksum-upload volume

Improvement

The checksum text box should be shown in the following methods

  1. Normal template registration and upload of template

Checksum-template

  1. Normal ISO registration, Direct download ISO registration, and upload of ISO

Checksum-Normal-iso

Currently, the API'S supports the checksum parameter for template and iso

https://cloudstack.apache.org/api/apidocs-4.19/apis/registerTemplate.html

https://cloudstack.apache.org/api/apidocs-4.19/apis/registerIso.html

https://cloudstack.apache.org/api/apidocs-4.19/apis/getUploadParamsForTemplate.html

https://cloudstack.apache.org/api/apidocs-4.19/apis/getUploadParamsForIso.html

@DaanHoogland
Copy link
Contributor

fixed in #10725

@github-project-automation github-project-automation bot moved this from ready for Review to Done in Apache CloudStack BugFest - Issues May 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment