-
Bug
-
Resolution: Done
-
Medium
-
Frankfurt Release
-
None
The response to a GET VNF Packages call to the ETSI Catalog Manager returns generic urls, which in this case point towards the internal msb-iag hostname/port. As shown below:
[{[{ "id": "70873ac7-579c-427c-8a2c-47da6bf35b0f",
"vnfdId": "",
"vnfProductName": "",
"vnfSoftwareVersion": "",
"vnfdVersion": "1.0",
"checksum": {},
"softwareImages": [],
"onboardingState": "ONBOARDED",
"operationalState": "ENABLED",
"_links": {
"self": {
"href": "http://msb-iag:443/api/vnfpkgm/v1/vnf_packages/70873ac7-579c-427c-8a2c-47da6bf35b0f" },
"vnfd": { "href": "http://msb-iag:443/api/vnfpkgm/v1/vnf_packages/70873ac7-579c-427c-8a2c-47da6bf35b0f/vnfd" },
"packageContent": { "href": "http://msb-iag:443/api/vnfpkgm/v1/vnf_packages/70873ac7-579c-427c-8a2c-47da6bf35b0f/package_content" } }}]
Possible solution at this point is to simply replace these self links values in the VNFM Adapter code.
These urls shouldn't be set to internal host/port due to the fact that this information will be passed to an external VNFM.