...

• To increase the number of parallel uploads, multiple SSVMs needs to be created. This will be handled automatically by the management server using the SSVM scale up mechanism (system.vm.auto.reserve.capacity, secstorage.capacity.standby and secstorage.session.max configuration variables). More uploads for a SSVM results in more polling related agent commands going to the SSVM and that should exhaust the session.max limit and result in spawning new SSVM. The SSVM selector logic then should pick up an SSVM during the request.
• TBD: number of parallel uploads a single SSVM can handle

UI Changes

A new UI to upload volume/template which should be able to accept "browse and upload" file.

UI flow:

"browse and upload" file. Existing UI for volume/template upload will be extended with the browser-based upload functionality.

UI flow:

1. User navigates to the Templates page then clicks on "Register template" (existing screen)
2. Register template form pops up (existing screen)
3. User has now the choice to provide URL of the template (existing functionality) or Upload File from Browser (new functionality)
4. Selects File Upload from Browser then specifies the template file (Browse...) to be uploaded
5. User fills in other existing form fields
6. User clicks OK to submit the form
7. Browser UI requests an unique upload URL using Browser UI requests the upload form by doing the getUploadParams api call
8. Management server returns an upload url, payload JSON string which should be passed on to the upload url while doing the upload
9. UI shows an upload dialog with a way to browse and upload file
10. User chooses a file and posts on the urlBrowser starts uploading using POST request to the upload URL
11. The post request completes once the template is downloaded/error.
12. The user can close the dialog (POST request should still be active) and use list template/volume API result to check the status of it

...