This patch fixes the issue that k8s failed to initialize object due
to version upgrade. Skip initial validation by setting the
`client_side_validation` parameter and remove the must_param
variable that was previously set in order to pass the validation.
In kubernetes v23.3.0, 'available_replicas' must be set into status
of `StatefulSet`, so this patch also add a kuryr-kubernetes versioned
parameter temporarily to .zuul.yaml to make the response returned
by kubernetes correct.
Closes-Bug: #1968103
Change-Id: I9495ce0f0893e5f9a1d6c52b98c3db3928bd95a3
Update usage guide on the priority of namespaces used by tacker
when deploying CNF and how to specify the target namespace in
InstantiateVnfRequest to deploy CNF on Kubernetes VIM.
Implements: blueprint k8s-namespace
Change-Id: I6030582c9929e321058ec3f6307d7b76d99b600a
The name of “change_ext_conn” is wrongly mentioned
in document.
It correct values as per the operation run flow
is “change-ext-conn”
Closes-Bug: 1967049
Change-Id: If7a8f46777d24cd0648fd4fbe734568c44ec1eff
Unittests for privsep and rootwrap fail if it runs on non-linux env
such as MacOS, or other than devstack environment. It's because
`oslo.privsep` and its tool are not installed properly in tox env.
So, skip the tests on other than devstack env to avoid such a failure.
This patch also modifies `pypath` in initialization of Privcontext
because its fstring cannot be expanded correctly in some environment
and tests are failed.
Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
Change-Id: I1e160500c30c379645bc19a67c429e9b2f12dcda
This patch implements the following APIs defined in ETSI NFV-SOL003
v3.3.1 5.5.2.11a with 'Kubernetes' vim.
1. Create VNF
2. Instantiate VNF
3. Change Current VNF Package
4. Terminate VNF
5. Delete VNF
Retry and rollback operation of change current vnf package API with
'Kubernetes' vim are also supported.
There are the following points to note.
1. Currently only 'RollingUpdate' is supported for
CNF deployment update.
2. 'Instantiate' VNF cannot rollback and retry with 'Kubernetes'
vim. It will be supported in future.
Implements: blueprint upgrade-vnf-package
Change-Id: Iae477cb4347ae01718d8dbf6ab8b2289e1758039
This patch implements change current vnf package task
defined in ETSI NFV-SOL003 v3.3.1 5.5.2.11a.
Retry and rollback operation of change current vnf package
API are also supported.
Note that currently only 'RollingUpdate' is supported for
VNF image's update.
This patch refactors the userdata_utils file and writes
the common methods into the new common/common_script_utils.py
file, so some changes are made to the existing instantiate
code.
Implements: blueprint upgrade-vnf-package
Change-Id: Ic810a3e9063e660e43e094d65111340d92917cf0
This patch contains a sample VNF Package that has ansible driver
artifacts. It will be a useful reference for users who choose to use
ansible to configure their target VNFs.
User document of ansible driver usage will be added.
It describes the conditions for running the script, how to create the
package, and an example of how it works.
Implements: blueprint add-ansible-mgmt-driver-sample
Spec: https://review.opendev.org/c/openstack/tacker-specs/+/814689
Change-Id: Ibbb9115a938de19e48f06c59af6bd7e7b222706d
Added a sample Ansible Driver as an option for users
who want to use ansible for configuration of VNFs.
In this Sample Ansible Driver, the following key LCMs
are supported:
- instantiate_end
- scale_start
- scale_end
- heal_end
- terminate_start
Implements: blueprint add-ansible-mgmt-driver-sample
Spec: https://review.opendev.org/c/openstack/tacker-specs/+/814689
Change-Id: I539f1ab5442196865155f12fe0b2b4106feedeae
Some parameters are missed in the example of a config file that is
automatically generated [1]. Therefore, users cannot see all available
parameters in the document.
To fix this problem, this patch adds the following missed namespaces to
``etc/config-generator.conf`` and adds the entry points [2] to
``setup.cfg`` and appropriate modules.
- tacker.auth
- tacker.conductor.conductor_server
- tacker.plugins.fenix
- tacker.sol_refactored.common.config
- tacker.vnfm.infra_drivers.openstack.translate_template
- tacker.vnfm.nfvo_client
For ease of maintenance, the contents of ``config-generator.conf`` and
``setup.cfg`` were sorted in alphabetical order.
Note that although the following modules register config parameters, but
excluded from this patch as the parameters are generated dynamically.
- tacker.api.vnflcm.v1.router
- tacker.api.vnfpkgm.v1.router
[1]
https://docs.openstack.org/tacker/latest/configuration/sample_config.html
[2]
https://docs.openstack.org/oslo.config/latest/cli/generator.html#defining-option-discovery-entry-points
Closes-bug: #1962728
Signed-off-by: Hiromu Asahina <hiromu.asahina.az@hco.ntt.co.jp>
Change-Id: I83e816448e7445d565302f1d6794b51b6effae01
Sometimes API layer can add restrictions to not allow
resource creation with the resource code name like vnf
creation with 'VNF' itself. There is no such restriction
in tacker and we can test it explicitly.
This commit modifies an existing test to create vnf with
the name 'VNF' which will verify the things. We do not need
to add a separate test for that as it can be verified in one
of the existing tests itself.
Change-Id: I41ea57ef9a5c35c124d4fa43f8c3b9498bd80c2c
setup-multi-tenant-vim role is needed for only multi tenant
jobs and for existing jobs we do not need to run this role.
Current way run it for all the jobs, this commit makes it
configurable and multi tenant job will configure it to true.
Change-Id: I6ab577232b93bbb6ab8a21fe7ad5876b5a7ab7bc
Added a sample VNF package for practical use cases.
In this sample, the use cases listed below is supported.
- using multiple deployment flavours
- deploying VNF connected to an external network
- deploying VNF as HA cluster
- deploying scalable VNF
Implements: blueprint add-vnf-package-sample-for-practical-use-cases
Spec: https://review.opendev.org/c/openstack/tacker-specs/+/814511
Change-Id: I1c55e028b96ba3c1ad26270d359e0b1165670078
Update usage guide on how to deploy CNF using helm chart to
pre-specify parameters for the number of replicas for scaling.
And this patch contains some revises for appearance.
Change-Id: I2da15230d9636adbba9012acabb53db579147368
Add file to the reno documentation build to show release notes for
stable/yoga.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/yoga.
Sem-Ver: feature
Change-Id: I1c713ecf2e6c41fc308d40f58f5f3de7f65243cd
This patch adds functional test cases to validate instantiate CNF
functionality in a multi-tenant environment.
Validates CNF instantiation is only allowed when CNF and VIM
belongs to same tenant.
Implements: blueprint k8s-namespace
Change-Id: I800b497ea6fa8f4978eb551558f0257e3d82a4ee
This patch provides Tacker documents for enhance operations(heal,
scale, update, changeextconn) in V2-API. The specification about new
API is added to API Reference. Also, update operation is added to
Tacker Use Cases Guide and CLI Reference.
This patch also includes changes to the user data script.
Implements: blueprint support-nfv-solv3-change-external-connectivity
Implements: blueprint support-nfv-solv3-heal-vnf
Implements: blueprint support-nfv-solv3-modify-vnf
Implements: blueprint support-nfv-solv3-scale-vnf
Change-Id: I6adefc59903a4c8305a66c224c086af4b86812df
Zuul
karolinku
zhangboye
Ken Fujimoto
Yi Feng
Renu
Yasufumi Ogawa
Tsukasa Inoue
Aldinson Esto
Hiromu Asahina
OpenStack Proposal Bot
Ghanshyam Mann
Masaki Oyama
Ayumu Ueha
OpenStack Release Bot
Tetsuro Kaneko