...

• 1: This state transition happens, when the user initiates the post request
• 2: Post request is active SSVM agent is downloading validation or downloading the template but, not done yet
• 3: on successful completion of template installation to secondary storage
• 4: This can happen in multiple ways:
  • user stopped/canceled the post request before completion
  • SSL handshake failed
  • params validation with PSK failed
  • downloading uploading the template failed due to a network issue
  • secondary storage is not accessible
  • there isn't enough space in secondary storage and hence agent cant write to it.
    All these errors have the same state as there isnt any way to recover from them or the handling isnt different for these. Additional error message information will be provided in the form of a message will be provided for the respective errors.

• 5: The post request hasn't happened and the timeout has reached

...

1. A new SSVM template is required.
2. setting up https on SSVM, opening the relevant ports doing the SSL handshake
   1. http://www.symantec.com/connect/articles/apache-2-ssltls-step-step-part-1
3. initial keystore exchange and authentication using the keystore
4. understanding template code 

Future

1. Download Upload progress to the user (http://creativejs.com/tutorials/advanced-uploading-techniques-part-1/ )
2. split upload and join in apache so as to not hit browser timeouts

3. post url should be active only for one time call - return proper error message on subsequent calls - how do we determine if its already used?

4. Admin to list all the uploads happening and cancel any if required?

5. Partial data upload and template cleanup (can be due to SSVM to agent restart or network error)

Open Questions

1. Multipart form data - Can this go in multiple connections?

2. SSVM storage issue. What should we tell the user? How can we notify the admin to recover from it?

3. Should there be an unencrypted HTTP version of the post?  No for now

4. No. of parallel uploads SSVM can handle? a default value should be provided to tune the apache to handle those many parallel connections. These should be determined based on the CPU RAM of SSVM - a proper error message to the user on reaching this limit

   expires support for the post url to SSVM Apache