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 will fix the exception that occurs when editing Grant transmission
data during Anti Affinity verification.
Co-authored-By: Hiroo Kitamura <hiroo.kitamura@ntt-at.co.jp>
Closes-Bug: #1923136
Change-Id: If0d02d1cab40b0bf9be9bc6825d96cdfaa5ea495
The "test_instantiate_terminate_vnf_with_vnflcmnoop" method of
multinode-sol job occasionally fails.
After vnf termination, "instantiationState" becomes "NOT_INSTANTIATED".
However, the "vnflcmOpOccs.operation_state" is not "COMPLETED" at this
point and sleep for 20 seconds before assert operation_state.
If stack deletion is not completed within 20 seconds sleep, reading
"PROCESSING" when asserting operation_state results in misjudgment and
an error.
This patch resolves the error by waiting until "COMPLETED" instead of
sleeping.
Change-Id: I5c5ec2f457d235c95627e2c339b477a191b24945
The current tacker returns 500 Internal Server Error to requests with
invalid filter conditions where a VNFID is not UUID. However, as the
error is caused by a bad request, the status code should be 400.
This bug occurs because data types of 'id' and 'vnfd_Id' in TackerObject
are 'string' which don't match the data types in DB, i.e., UUID. In
order to fix this bug, those data types in TackerObject are changed to
'uuid'.
Closes-Bug: 1924666
Closes-Bug: 1926632
Change-Id: I8decbb42d661a44c6c382cb1abbfc37d95084ffb
To install heat-translator and tosca-parser from git repos, dedicated
scripts for the tasks were added in [1]. Then it was replaced with
smarter way using `git_clone_by_name` in [2]. So, we don't need to have
changes by [1] anymore.
[1] https://review.opendev.org/c/openstack/tacker/+/765296
[2] https://review.opendev.org/c/openstack/tacker/+/787322
Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
Change-Id: I0a842843443bf5b2dd267b57b3e3dcc66a5198cf
The oslo.reports library provides some options under the [oslo_reports]
section. This change ensures these parameters are rendered by
the oslo-config-generator command.
Change-Id: If1cd703bf06c76fa23c567e61434ef703c24daa0
This patch fixes the problem that cnf rollback operation does not
delete the kubernetes resource created during instantiation.
Closes-Bug: #1933305
Change-Id: Iecd8f11f5d51a49999f4f0e31a16f41438834f8a
The oslo.service library provides a separate entrypoint to load options
for periodic tasks. Because Tacker imports periodic tasks mechanism
from the library, the related options should be loaded as well.
Change-Id: Ic6de82be9d1bed1c557c53216caabcbf9e944e3f
This patch changes the following to support helm chart spec and
to test instantiate/terminate cnf with helm chart.
* Add `extra` field to vims db.
* Add `setup-helm` task to ansible-playbook roles.
[On controller-k8s node]
* Create and setup helm user for executing helm command.
* Install helm.
* Create folder for putting local helm chart.
* Enable password authentication in sshd_config and restart sshd.
[On controller node]
* Update Vims DB of vim-kubernetes to modify extra field that include
helm access information.
Implements: blueprint helmchart-k8s-vim
Change-Id: Iaf7c11c5bedb77e9cd21074be2b4f73528aa2ce7
Due to a bug in heat project, the some FTs don't pass.
This patch temporarily skip fail tests that until the bug is resolved.
* Due to heat bug reported in [1].
functional.legacy.vnfm.test_vnf_placement_policy.VnfTestCreate
- test_create_delete_vnf_with_placement_policy_affinity()
- test_create_delete_vnf_with_placement_policy_anti_affinity()
- test_vnf_with_policy_anti_affinity_insufficient_comp_nodes()
Skip should be removed as soon as the bug is resolved.
[1] https://storyboard.openstack.org/#!/story/2009164
Change-Id: I8784603c875a93790014930004b90c39155c9e71
ABCs in collections should be imported from collections.abc and direct
import from collections is deprecated since Python 3.3.
Closes-Bug: #1936667
Change-Id: Iafc013cb9b454bc5251d126643f68f3112dafa54
The current `Tacker User Guide` page doesn't have `Getting Started` for
ETSI NFV-SOL Tacker.
Added `Getting Started with ETSI NFV-SOL Tacker`.
Also, added sample files, such as a VIM config file, VNF packages and a
VNF instantiation parameters file, to the `samples` directory, which
are referred from the `Getting Started` page.
Change-Id: I58dadaa6c99fc45a34d87218c4d943e2572aa0a1
Signed-off-by: Hiromu Asahina <hiromu.asahina.az@hco.ntt.co.jp>
We've been using old cirros-0.4.0 for long time, and don't need to fix
the version of cirros to 0.4.0. This patch is update to the latest
0.5.2.
Most of the changes in this patch is replacing `image`, `hash` and
`version` in TOSCA definition files. The rest of them are:
* Replace images. First one is only an actual image, and rest of them
are empty text files which is a trick for reducing total size in
tacker repo. So, text files are not replaced, but renamed simply.
* tacker/tests/etc/samples/etsi/nfv/common/Files/images/cirros-0.5.2-x86_64-disk.img
* samples/vnf_packages/Files/images/cirros-0.5.2-x86_64-disk.img
* tacker/tests/etc/samples/etsi/nfv/test_csar_utils_data/sample_vnfpkg_no_meta_single_vnfd/Files/images/cirros-0.5.2-x86_64-disk.img
* tacker/tests/etc/samples/sample_vnf_package_csar_in_meta_and_manifest/Files/images/cirros-0.5.2-x86_64-disk.img
* Update functional tests verifying images. A refactor of defining
package size is included.
* Update devstack script, and helper scripts under `contrib` dir.
* Update API references and documents describing usage of the image.
Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
Implements: blueprint update-cirros-052
Change-Id: I081b791dc986ab10f4845784b3e19dbb626e3cac
This patch fixes misspelled words such as parameter name
"cert_verify" and "instance" found incorrect in Tacker
Legacy User Guide.
Closes-Bug: #1940230
Change-Id: I37d61805bf492d28362183e91f21e18cf95cc0c6
When getting information about multiple VNF instances with invalid
attribute selector or invalid attribute-based filtering parameters,
tacker return a response with HTTP Code 200 and all information
about VNF instances. However, according to the specification file,
the HTTP code 400 Bad Request shall be returned.
To fix this bug, this patch adds a new check for this api`s
parameters. If it contains unsupported parameters, the HTTP code
400 Bad Request will be returned.
Closes-Bug: #1938108
Change-Id: I3cca6d6fa664dd8f88791516042892369e4972a2
The current `Install via Devstack` page doesn't have a hardware
requirement which may cause installation failure or poor performance.
Added a table that shows hardware requirements.
Also, the current document mentioned `ussuri` in sentences, but it's too
old. Updated the version referred in sentences from `ussuri` to the
latest release `wallaby`.
Change-Id: Ifd916c96e8f90d7abb411d3eb0669e8ac3b0cf84
Signed-off-by: Hiromu Asahina <hiromu.asahina.az@hco.ntt.co.jp>
Accroding to the NFV-SOL 013v2.6.1 Section 6, modify the API's
response body format when error happened.
Add title, status and detail attributes and delete problem type,
code and message attributes in the response body when error happened.
And also change the "Content-Type" from "application/json" to
"application/problem+json".
Closes-Bug: #1930647
Change-Id: Ic5f08ca924d14a382baeb77470aa3430e317315f
This patch will fix the issue about Healing not being
able to update to the new image.
Closes-Bug: #1924215
Change-Id: I3de1a532e33ae25638a452db4b9e18626de8df42
This change is to update python-cinderclient to 8.0.0 because cinder
dropped v2 API and doesn't support its client for the API. It also
updates depending packages as below.
* python-cinderclient 8.0.0 depends on pbr>=5.5.0
* python-cinderclient 8.0.0 depends on oslo.utils>=4.8.0
* python-cinderclient 8.0.0 depends on stevedore>=3.3.0
* python-cinderclient 8.0.0 depends on requests>=2.25.1
* python-cinderclient 8.0.0 depends on keystoneauth1>=4.3.1
Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
Change-Id: Id01fe417acf4da4e5360dfba3bc2cc96df2b6889
The current document doesn't have an overview of VNF LCM operations,
e.g., Deployment, Scaling and Healing. For example, the VNF scaling
creates/changes VMs with OpenStack Heat API and users have to confirm
results of an operation with `openstack stack` command, but the
relationship between OpenStack Tacker and OpenStack Heat is not
explicitly described.
For ease of understanding, added diagrams and brief explanation of the
LCM operations listed below.
- ETSI NFV-SOL VNF Deployment as VM with TOSCA
- ETSI NFV-SOL VNF Deployment as VM with LCM operation user data
- ETSI NFV-SOL CNF (Containerized VNF) Deployment
- ETSI NFV-SOL VNF Healing
- ETSI NFV-SOL VNF Scaling
- ETSI NFV-SOL CNF Healing
- ETSI NFV-SOL CNF Scaling
Change-Id: I3ddf9e5ec68c0e84ccc9df4fea9ee274562a3e88
Zuul