Page History

...

Management server owns the lifecycle of volume/template (initially gets created with upload state as "NOT_UPLOADED"). It polls the SSVM agent (using an already existing agent command) to get the status and triggers appropriate state transitions. Polling starts after the successful completion of the getUploadParams API. The polling 'interval' and 'timeout' are determined by global configuration parameters (TBD - add configuration details).

Failure at any point during the upload process to SSVM would result in upload state getting transitioned to "UPLOAD_ERROR" (refer to the state machine below). Also if the upload is not completed within 'timeout' configuration the state transitions to "UPLOAD_ERROR". This will take care of SSVM agent failure/SSVM failure scenarios.

...

The SSVM agent will listen for any connections from Apache web server (using the NioServer utility). It will be using the localhost and port number (come from a configuration - TBD specify details) to listen.

SSVM apache proxies the data from https to http url on localhost:port using ProxyPass.

...

No schema changes. Some configuration items will be created.

Configurations

...

The following new configurations will be added

• Global configuration to limit the max upload size of template/volume - maxupload.post.uploadmax.size
• hidden configuration to save sha1 PSK on the management server - upload.post.psk
• management server upload polling interval and polling timeout - upload.post.interval, upload.post.timeout
• time interval at which the GC or cleanup thread should run - upload.post.gc.interval

...