The Model Loader currently pulls AAI model XML artifacts straight from SDC.

For the Amsterdam release we propose that SDC should not be the supplier of the AAI specific model XMLs, but these should be generated from the TOSCA files contained within the SDC CSAR artifacts.

The Babel service has been created to translate the CSAR files into AAI model XML, so the Model Loader need to be updated with the following flow:

1. Pull CSAR artifact from SDC
2. Supply CSAR file to Babel service using a synchronous REST call
3. Receive generated AAI model XML artifacts from Babel service
4. Deploy AAI model XML to AAI

The Model Loader should publish a deploy failure event back to SDC should the Babel service return an error response, or if the Babel service is not available.