Add file to the reno documentation build to show release notes for
stable/wallaby.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/wallaby.
Sem-Ver: feature
Change-Id: I07255d22a0bcfcf9cd577e81bccf4b1bc9586b93
This update is to fix styles and revise some descriptions to be
concise in the second paragraph in draft verion of releasenote
for wallaby[1].
[1] https://docs.openstack.org/releasenotes/tacker/
Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
Change-Id: Iba1069db766770434dc9d126de33d646fc228485
- Added support for the following attributes:
*operationStates
*vnfInstanceSubscriptionFilter
- The filtering criteria is enhanced by adding the
above attributes to effectively send_notifications
- We also updated the following table in DB:
vnf_lcm_filters
Implements: blueprint support-fundamental-lcm
Spec: https://specs.openstack.org/openstack/tacker-specs/specs/wallaby/support-fundamental-vnf-lcm-based-on-ETSI-NFV.html
Change-Id: Iebe70c43ef1a5b653f8ec204b1b3a79ca882399f
Usage guide for ETSI Change external VNF connectivity is added in
user docs.
This patch describes the procedure for Change external VNF
connectivity operation.
Change-Id: I6f90d8b21f08e27bea60df66479e7951cbad7b5b
This feature will enable the client to use this API to initiate
retrying Change VNF External VNF Connectivity operation when it
fails.
It is based on the ETSI NFV specification that retry can be used
when a VNF lifecycle operation is in a FAILED_TEMP state.
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: Ia1d907922cdb701586f15c4840848fa8402ded3b
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
This functionality will enable tacker to test the
notification during register Subscription.
if VNFM cannot receive success response
(204 no content), VNFM will be failed Subscription
Request
- As sending management of this API, we apply
legacy CONF.
(retry_num,retry_wait, there are defined in
vnf_lcm group.)
- As sending control of this API, we add new
CONF(test_callback_uri)
- We modify(add) Notification(GET) process to
current send_notification.
Implements: blueprint support-fundamental-lcm
Spec: https://specs.openstack.org/openstack/tacker-specs/specs/wallaby/support-fundamental-vnf-lcm-based-on-ETSI-NFV.html
Change-Id: I2a1db1b34b687748ad939b0c867b2d78f45622da
Usage guide for ETSI NFV-SOL VNF Error-handling is added in user
docs.
Add usages for `retry` and `fail` error handling operations.
Change-Id: Ib9b93a8dd8ad6ae85cde154803c22d02bdb0b6d7
In this implementation, tacker support only "fixedAddresses" parameter.
This patch support "numDynamicAddresses" parameter in
IpOverEthernetAddress, modify to be accepted API Request.
*In this patch, support for addressRange has been postponed.
It is defined into ipAddress parameter by
ETSI SOL003 -> v2.6.1 -> 4.4.1.10c.
IpOverEthernetAddressData
-> ipAddresses
-> numDynamicAddresses
And, modify the LCM user data route so that it can use
IpOverEthernetAddressData.
Change-Id: I3f6ba1f4e1bacf1fc5295726afc7ffd8626db444
- 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
CLI commands developed in Wallaby are added in CLI doc.
This patch adds the following CLI commands:
* Retry
* Fail
* Change External VNF Connectivity
* List LCM Operation Occurrences
* Show LCM Operation Occurrence
Change-Id: If374a9cdce2e30b5f9883e21b1f7ffe500982551
When sending notifications, the API is sent using requests.session.
Currently, no timeout value is set. Therefore, if there is no
response from the connected server, it will not be able to close
its own socket even if it terminates abnormally.
To resolve the problem, we add vnf_lcm.retry_timeout to tacker.conf.
When submitting the API, the timeout value is set to the requests
api. We set the default value to 10 seconds (with 3 tries).
Closes-Bug: #1911124
Change-Id: I63078635a8db5669dbd94ecf8c69bb3946ae0347
After scale_out, tacker is getting stack_id from heat_client.
However stack_id is not in heat.metadata.
This will cause other lcm operations to this vnf_instance
fail(like heal)
For vnf_instances creted by instantiate interface,
this problem does not happen because after instantiate,
tacker will get stack_id from vnfc_res_info, not asking
heat.
This patch fixes this bug by change get stack_id logic after
scale_out by getting physical_resource_id from
target Heat AutoScalingGroup resource(vnfc_res_info)
Closes-Bug: #1919434
Change-Id: I12fe98e51930c48da8540368c6b38f8254b0b68b
OpenStack Release Bot
LiangLu