When a VSP csar is onboarded in SDC onboarding, the original unaltered csar is to be sent to a location for storage.
It is yet to be decided what the storage solution will be, but most likely is a persistent volume. There should be flexibility in the solution to allow different storage solutions be used.

The details of the storage solution to be specified by configuration. It shall be valid for no storage solution to be configured, in which case there is no change to existing functionality.

Care should be taken to not parse the full original csar into memory to avoid OOM.

Proposed Implementation:

• During the execution of the OrchestrationTemplateCandidateImpl.upload() method:
  • Send the unaltered csar to the storage solution using th details from configuration - asynchronously
  • an OrchestrationTemplateCandidate Element is stored in the DB to persist info on the received package for later processing.
  • Add to this the creation of a sub-element  to the OrchestrationTemplateCandidate of new element type UNALTERED_PACKAGE containing details of the original csar on the storage solution if a storage solution is configured