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>"
}
}
This patch updates '_links' href field in vnflcm api output
with host-path.
For ex,
"_links": {
"self": {
"href":
"http://localhost:9890/vnflcm/v1/vnf_instances/<vnf-instance>"
}
}
*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 <navum.gupta@india.nec.com>
Closes-Bug: #1923360
Change-Id: I245cd2626fac1112d6a9fef3c51bf5ef6b679e05
This feature will enable the client to use this API to perform the
following operations:
- allow client to change the external connectivity of a VNF
instance
- VNFM support to change port/network
- VNFM also supports to change ip address/mac address/
allowed_address_pair
The operations provided through additional attributes are below:
- Grant(POST)
- VNF instances (GET)
- Individual VNF Instances (GET)
- Notification Endpoint (POST)
Modified .zuul.yaml to disable image_volume_cache, since cache
Volume remains during Terminate implementation and responds to
Heat Stack deletion failure without erasing volume type.
Implements: blueprint support-change-external-connectivity
Spec: https://specs.openstack.org/openstack/tacker-specs/specs/wallaby/support-change-external-VNF-connectivity-operation.html
Change-Id: Ie6b8b2b46b6de24e2d2d0a8bccef87bbdfa39191
- Added support for getting Individual VNF LCM
operation occurrence by its ID
- The query information is enhanced by improving
filtering expressions and operators
- Attributes are also added including (but not
limited to):
* grant_id
* _links
* >retry
* >fail
* changedExtConnectivity
- This patch has 2 BP features (Get VNFM LCM Operation
Occurence and attributes of Change External Connectivity
are also added). Since both features are related, they are
merged to one patch. This is why this patch have 2 BPs.
- Filtering for the following attributes:
operationParams, error, resourceChanges and
changedInfo is only limited to the parent
attribute. Currently, child attributes/nested
attributes are not searchable.
Implements: blueprint support-fundamental-lcm
Implements: blueprint support-change-external-connectivity
Spec: https://specs.openstack.org/openstack/tacker-specs/specs/wallaby/support-fundamental-vnf-lcm-based-on-ETSI-NFV.html
Spec: https://specs.openstack.org/openstack/tacker-specs/specs/wallaby/support-change-external-VNF-connectivity-operation.html
Change-Id: Ie9b07c203807d08857be65298d9128b026a8fd37
In this patch, multiple failures in VNF lifecycle such as Scale,
Rollback and Heal are fixed.
The fixed cases are the following:
- It cannot set correct value to operation_params due to the lack
of parameter setting in sending Notification.
- 409 error occurs due to incorrect STATUS setting in Rollback.
- Scale fails since instance_id/aspect_id cannot be set correctly.
- HOT creation in Scale fails since API information cannot be set
correctly.
- In the case including recreating stack such as Heal, a waiting
process fails due to un-updated instance_id.
- Scale/Rollback fail since instance_id cannot be held during
Instantiation.
- Rollback fails due to incorrect state holding during
Instantiation.
- Uploading package in separate mode fails due to incorrect
package extraction.
Additionally, the following modifications are also done.
- instance_id setting process is enhanced.
- Mismatches of definition in some arguments are resolved.
- Incorrectly merged code into the master is fixed.
- Setting of STATUS name during Rollback is fixed.
- Mock is added due to the modification of this patch.
- Definition of column in DB migration is fixed.
Change-Id: If538956c433e803149ad109672eed678dcae63e9
Closes-bug: #1902194
Execution "openstack vnflcm create" raises some package errors.
In order to avoid them, the exception process in vnflcm creation
is fixed.
Closes-bug: #1898963
Closes-bug: #1899112
Closes-bug: #1899134
Additional Information:
---------------------------------------
- vnf_lcm_subscription.id was decoded. The code we developed in
advance was created on the premise of varbinary and there was an
unmatch, therefore, at first, the DB type was matched. To modify
the code correctly, id decode was removed.
- Spec (Support LCM notifications for VNF based on ETSI NFV-SOL
specification)
There was a discrepancy with the content and I fixed the registered
migration, but the procedure was incorrect, so it was restored.
- Spec (Support LCM notifications for VNF based on ETSI NFV-SOL
specification)
I found that some columns were not added to the DB due to a mismatch
with the contents, so I am adding a new migration file. Also, since
the type definition was different for the already registered columns,
it was also corrected.
Change-Id: I0ee9d7e1e0c4ea26dd5894ad4fca302fe9bfd4d1
Supported the following operations to get the VNF package
information from NFVO when starting LCM operation.
- VNF packages (GET)
- VNF package content (GET)
- VNFD in an individual VNF package (GET)
- Individual VNF package artifact (GET)
Implements: blueprint support-vnfm-operations
Spec: https://specs.openstack.org/openstack/tacker-specs/specs/victoria/support-sol003-vnfm-operations.html
Change-Id: Ibdafdda815f8e130226b9d8eef4f18639f01292c
Sheel Rana
Aldinson Esto
Koichi Edagawa
tpatil
Niraj