Page History

...

When the management server receives getUploadParams api call, it selects SSVM and secondary store in the zone requested by the user and returns a POST url to that SSVM. There can be multiple SSVMs in the same zone. Management servers decides which SSVM to handle this based on the load. SSVM agent will be able to return the status of the upload at any point using the in memory hash map if the download is in progress or by the file status on the secondary storagekeep track of the uploads and returns the status to the management server. If the template/volume is selected to be cross-zone, it will uploaded to one zone and then copied to other zones from it. 

management server owns the state machine lifecycle of the volume/template. It polls the SSVM agent(using DownloadProgressCommand of the agent) to get the status and updates it. Failure at any point during the form upload to ssvm apache would return error to the user and UPLOAD_ERROR when the management server pings for download status.

Polling starts after the successful return of the getUploadParams. The polling starts after an initial delay of 100ms and in intervals of 1000msn ms. The management server polls 5 x times before it changes the state to ERROR. (we may need to add new configurations to handle this polling) 

If the management server itself goes down during the upload, if the timeout hasnt crossed, it will poll for the status once its up. Otherwise the state of the template will be transitioned to ERROR. In a load balanced situation where the management server handling the ssvm upload goes down, the status wont be updated unless the SSVM is connected to a new management server.

...