Currently vnflcm api operations do not return host-path
in their output inside '_links' href field.
For ex,
"_links": {
"self": {
"href": "/vnflcm/v1/vnf_instances/<vnf-instance>"
}
}
Related operations:
1. Creates a new VNF instance.
2. Show VNF Instance.
3. List VNF Instances.
4. Show VNF LCM operation occurrence.
5. List VNF LCM operation occurrences.
Reviewed: https:/ /review. opendev. org/c/openstack /tacker/ +/785798 /opendev. org/openstack/ tacker/ commit/ 2c68a0a84d2a625 98b9379529008c2 ae1c849ca6
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 2c68a0a84d2a625 98b9379529008c2 ae1c849ca6
Author: Sheel Rana <email address hidden>
Date: Sun Apr 4 22:26:47 2021 +0530
Updated vnflcm api output with host-path
Currently vnflcm api operations do not return host-path
"/vnflcm/ v1/vnf_ instances/ <vnf-instance> "
in their output inside '_links' href field.
For ex,
"_links": {
"self": {
"href":
}
}
This patch updates '_links' href field in vnflcm api output localhost: 9890/vnflcm/ v1/vnf_ instances/<vnf-instance>"
with host-path.
For ex,
"_links": {
"self": {
"href":
"http://
}
}
*here "http:// localhost: 9890/" is just an example of host-path.
Related operations:
1. Creates a new VNF instance.
2. Show VNF Instance.
3. List VNF Instances.
4. Show VNF LCM operation occurrence.
5. List VNF LCM operation occurrences.
Co-Authored-By: Navum Gupta <email address hidden>
Closes-Bug: #1923360 12d6a9fef3c51bf 5ef6b679e05
Change-Id: I245cd2626fac11