This patch will change the proccessing of Placement Constraints
from VDU name to Aspect Definition. There is also an error in the
judgment logic when setting Availavility_zone information from
the Zone information of GrantRes, so the judgment logic is also
fixed.
Closes-Bug: #1924216
Change-Id: I5635f1b430f0b2f6e8b4c4ef50ca0864a8dd6230
This patch will fix the issue about Healing not being
able to update to the new image.
Closes-Bug: #1924215
Change-Id: I3de1a532e33ae25638a452db4b9e18626de8df42
Grant for 3rd-party NFVO is improved. Process related to placement
constraints is supported. This enables interoperability with
3rd-party NFVO which enables them to deploy each VM in the VNF after
setting the zone information based on the grant response from NFVO.
Co-authored-By: Yasufumi Ogawa <yasufum.o@gmail.com>
Implements: blueprint support-placement-constraints
Change-Id: Ibd8c5cae985766d5bd5e73276920fd4c28d6e87f
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
Implements Container based VNF heal operation support with ETSI
NFV-SOL002 and SOL003 v2.6.1 VNF Lifecycle Management. For "Heal VNFC
with SOL002", users can heal Pod (mapped as VNFC) that is singleton or
created using controller resources such as Kubernetes Deployment,
DaemonSet, StatefulSet and ReplicaSet. For "Heal VNF instance with
SOL003", users can heal entire VNF instance by termination and
instantiation of the VNF.
Other changes:
* Store Pod information to vnfcResourceInfo after instantiation.
* Update vnfcResourceInfo after scale operation.
Implements: blueprint support-cnf-heal
Spec: https://specs.openstack.org/openstack/tacker-specs/specs/wallaby/support-cnf-heal.html
Change-Id: I62bf8d67eb9b3889f2ae69be9bb45363d083f48e
Previously get_base_nest_hot_dict() was called by vnflcm_driver
and openstack infra_driver redundantly.
This patch remove calling get_base_nest_hot_dict() from
vnflcm_driver because HOT is openstack specific.
base_hot_dict parameter of infra_driver interface is removed
at the same time.
Note that vnf_package_path parameter is passed to infra_driver
always since it is used by both openstack and kubernetes.
Change-Id: I94fc914f58747ae75651480ec11b177140fa849a
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
As the last update for dropping Python2 support, remove helper functions
introduced to run unittests on both of py2 and py3 with six.
Closes-bug: #1778644
Change-Id: Ie75879f33edeeaa94247fec2d665fd1a4266c700
Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
This fix will allow Instantiation to be successful when
Multiple Base Hot is defined in the VNFD Package.
Closes-Bug: # 1895830
https://bugs.launchpad.net/tacker/+bug/1895830
Change-Id: I2d5e677820a4978d609ab492aa64cdc5269fd5c9
The number of getting image URL is expected as `2`, but notactually
in test_pre_instantiation_vnf_image_with_file(). The value can be `1`
or `2` for `tox -e py36` or `tox -e lower-constraints`. It might be
because of a difference of versions of modules imported in
the test cases.
This update is just a quick fixing to avoid the issue. So, it could be
happened again possibly if the versions of modules are changed.
Closes-Bug: #1885523
Change-Id: I302607f636d6d96baa544ccad600bb21fdf18da2
Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
Picked up unused fuctions with vulture [1].
In this patch, from the picked up functions,
the inner-functions prefixed with '_' are deleted as dead code.
Only target the inner-function of unittest and functional-test.
Other functions are left because it's difficult
to determine if they should be mechanically deleted.
[1] https://pypi.org/project/vulture/
Change-Id: I0deb0bdc9e7a7dd1cf7f98f22686ca7727088e22
Closes-Bug: #1879871
Now that we no longer support py27, we can use the standard library
unittest.mock module instead of the third party mock lib.
Change-Id: I130c03e12ddc53ce7ced728a43b10b142f7b066f
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Co-Authored-By: Hiroo Kitamura <hiroo.kitamura@ntt-at.co.jp>
Implement new method of VNF lifecycle management using LCM operation
user data.
Change-Id: Ib2fbe341b5d26758f0b48dc19e3e05810c2c830f
Blueprint: support-etsi-nfv-specs
Implemented instantiate vnf instance API.
* GET /vnflcm/v1/vnf_instances/{vnf_instance_id}/instantiate
Co-authored-By: Nitin Uikey <nitin.uikey@nttdata.com>
Co-authored-By: tpatil <tushar.vitthal.patil@gmail.com>
Co-authored-By: Ajay Parja <ajay.parja@nttdata.com>
Co-authored-By: Shubham Potale <shubham.potale@nttdata.com>
Co-authored-By: Sameer Thakur <sameer.thakur@nttdata.com>
Updated lower-constraints openstacksdk version to 0.44.0 as it
includes fix[1] which is required to create images from filename
which further requires to upgrade os-service-types, keystoneauth1
and decorato to higher versions.
[1] : https://review.opendev.org/#/c/710368
Change-Id: Ic30f8d730d54e3af1345816ffa1bfb702cd00694
Blueprint: support-etsi-nfv-specs
This patch fix bugs regarding bytestring "mgmt_ip_address" and
assertion test for bytestring "req.body".
Change-Id: I76424f64b2e436da05f9871adfa11b8bef9a3939
vnf-update don't change heat stack's state.
But update_wait function currently check stack's state.
Therefore update_wait always raise exception,when tacker
execute update. The reason that this function execute
check process is because vdu_autoheal action shares
update_wait with update action.
this commit splits update_wait into heal_wait and update_wait.
Closes-Bug:#1837205
Change-Id: I7ab059bb30b5de38943555883a92d77a64a56d34
Added new unit tests to cover create_wait, update_wait, delete_wait,
scale and scale_wait methods. Added heat-client fixture for writing
test cases. Also removed unreachable code in openstack module.
Change-Id: I9c1b5fe2e4efb41368d53cdac8dbbd49eea4b60a
Aldinson Esto
Ayumu Ueha
Itsuro Oda
Koichi Edagawa
Yasufumi Ogawa
Hiroo Kitamura
Sean McGinnis
tpatil
Niraj
Keiko Kuriu
Hiroya Nakaya
shubham potale
yong sheng gong