Support deploying Kubernetes cluster VNF which has a storage server
with Cinder volume. This feature enables users to deploy CNF which
has PersistentVolume on it. The following changes are added for
MgmtDriver.
1.Create a storage server VM with Cinder volume.
2.Expose Cinder volume as NFS shared directories in the storage
server.
3.Register NFS shared directories as Kubernetes PersistentVolumes.
4.Install NFS client on newly created Master/Worker VMs in all LCM
operations.
Implements: blueprint pv-k8s-cluster
Change-Id: Iaab9b6393e6f2007c637f83a82de0d27cf9db257
This patch implements spec
Support deployed Kubernetes cluster using the images in a Docker
private registry with MgmtDriver in blueprint bp/cir-k8s-cluster.
It includes mgmt_driver scripts of deploying a Docker private
registry to vm created by openstack_driver.
Support instantiate/terminate/heal function.
It includes mgmt_driver scripts of deploying kubernetes cluster
that can use images in Docker private registry to vm created by
openstack_driver.
Support instantiate/terminate/scale/heal function.
It also includes a shell script that actual install kubernetes
cluster and configure environment to support Docker private registry
on vm.
Implements: blueprint cir-k8s-cluster
Change-Id: I7adab1d1eaa491a37399d0b615cbee4c6ae86657
This patch and "Sample script for deploying k8s with kubespray",
"Sample script for scaling k8s with kubespray" are actually the
same one. For the convenience of review, they
were submitted separately.
This patch is only about the content of heal k8s nodes. However,
since the processing of scale_start is similar to heal_start,
and the processing of scale_end is similar to the processing of
heal_end, the code of scale has been refactored and the common
processing is extracted as a common method. At the same time,
when CNF needs to perform `heal_entire`, the configuration file
of Load Balancer needs to be re-modified, so heal-related
processing is added to the example MgmtDriver of CNF's `NodePort`.
Because the input parameter of terminate and heal is limited,
the type of this parameter is also modified. In
`NFV-SOL003 v2.6.1`[1], the `additionalParams`'s type is
`KeyValuePairs`, so we changed the additionalParams's type from
`list` to `dict` in heal_vnf_request. In order not to affect
the original function, we modified the original additional_params
to legacy_additional_params and retained the original processing,
and revised the UT code.
[1] https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf
Implements: blueprint k8s-mgmtdriver-kubespray
Change-Id: Ibf8b56904b1326f5c7d323c9295d10e303f4b4b8
This patch provides a base to support multi version API.
The existing code of functions for SOL specification was hard to
understand and enhance since it is based on the code of legacy tacker
API and they are connected with each other complicatedly.
Therefore the code for SOL specification is newly created which
is independent to the legacy tacker API so that it will be easy to
maintain and enhance.
This patch supports vnflcm v2 API (api_version 2.0.0) as a starting
point. It supports less functions than the exsisting v1 API at the
moment(Xena) but it will catch up with by the next release (Y).
This patch makes supporting another API version easy when it will
be supported in the future. Possibly it may thought to add v1 API to
this code base.
TODO: enhance UT/FT
UT/FT is not sufficient at the moment. Additional UTs and FTs will
be provided with another patches.
Implements: blueprint multi-version-api
Implements: blueprint support-nfv-solv3-start-and-terminate-vnf
Implements: blueprint support-nfv-solv3-query-vnf-instances
Implements: blueprint support-nfv-solv3-query-operation-occurrences
Implements: blueprint support-nfv-solv3-subscriptions
Change-Id: If76f315d8b3856e0eef9b8808b90f0b15d80d488
Implements new interface for Kubernetes VIM to handle Helm chart.
It enables Users to include Helm chart files as MCIOP in their VNF
Packages, to instantiate and to terminate CNF with them.
And update sample of MgmtDriver to install and configure Helm package
for using Helm cli command in the deployed Kubernetes cluster VNF, and
to restore the registered helm repositories and charts after the master
node is healed.
Implements: blueprint helmchart-k8s-vim
Change-Id: I8511b103841d5aba7edcf9ec5bb974bfa3a74bb2
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
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
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
This patch implements spec
Support deploying Kubernetes cluster with MgmtDriver
in blueprint bp/cnf-support-with-etsi-nfv-specs.
It includes sample mgmt_driver scripts of deploying
kubernetes cluster to vm created by openstack_driver.
Support instantiate/terminate/scale/heal function.
It also includes a shell script that actual install
kubernets cluster on vm, and an use guide to show
how to use this sample script.
Implements: bp/cnf-support-with-etsi-nfv-specs
Change-Id: I4d0085ffa3b4c90741ebb169b96f69113e2bb6d7
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
Implements Container based VNF scale operation support with ETSI
NFV-SOL003 v2.6.1 VNF Lifecycle Management. Users can scale the number
of pod replicas managed by controller resources such as Kubernetes
Deployment, StatefulSet, and ReplicaSet.
Other changes:
* Check the vnf_state before scale operation in controller as other
LCM operations.
* Enable to store multiple flavour to `vnfd_attribute` when
`Conductor._onboard_vnfd()` method called.
* For FT, sqlalchemy is used, which calls functions in pymysql.py,
so the dependency module PyMySQL needs to be added.
Implements: blueprint support-cnf-scale
Spec: https://specs.openstack.org/openstack/tacker-specs/specs/wallaby/support-cnf-scale.rst
Change-Id: I739fa60a18323b248bc913f6062ef2138ad2e6ee
* Enable VNF vendors to customize configuration methods
for applications via MgmtDriver
* Load LCM interface from vnfd file
* Call LCM methods from vnflcm_driver
* Fix unitentional mgmt_calls in vnflcm_driver._scale_vnf_pre
Note:
* For UT, sqlalchemy is used, which calls functions in pymysql.py,
so the dependency module PyMySQL needs to be added.
* The previous implementation of ``cfg.CONF.tacker.infra_driver``
depends on the default config in legacy ``VNFMPlugin`` class in
tacker/vnfm/plugin.py, so we need to fix this here.
* Due to drop unitentional mgmt_calls, it makes compatibility breakage
for some scale actions calls and third party driver support. This
backward incompatibility was decided to keep since it is not long
time since last change(Victoria release)
Change-Id: Ib4ad3eb9e0a84d1a5e807d2e6004e6b2c02bf3cf
In python 3, all strings are considered as unicode string.
This patch drops the explicit unicode literal (u'...')
or (u"..") appearances from the unicode strings.
Note: The scope of the patch is to drop unicode literal prefix
from python source code files, documentation and comment are overlook.
Change-Id: I66389d3f4b236a50bd3f193d4e67c2ac10e6ca24
This patch attaches already created volume to vnf using volume id.
The existing volume id can be added to tosca.nodes.BlockStorage node,
in this case, no new volume will be created while vnf deployment.
Implementation:
* Set tosca.nodes.BlockStorage.Tacker "size" required as false,
this override property definition mention in
tosca.nodes.Storage.BlockStorage present in tosca parser.
Please refer [1] for tosca.nodes.Storage.BlockStorage details.
* Add a local dictionary to store volume id present in
tosca.nodes.BlockStorage.Tacker. This dictionary is use in
to determine cinder volume mapping.
Additionally update block_storage_usage_guide.rst with changes
required to attach existing volume.
Added cinderclient in test_requirement for functional test case.
Add release notes for feature.
[1]: http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/csprd01/TOSCA-Simple-Profile-YAML-v1.2-csprd01.html
Change-Id: If5d386a64f98603de843f96287c1e296ae6a2e1f
Implements: blueprint attach-existing-volume
As per the community goal of migrating the policy file
the format from JSON to YAML[1], we need to do two things:
1. Change the default value of '[oslo_policy] policy_file''
config option from 'policy.json' to 'policy.yaml' with
upgrade checks.
2. Deprecate the JSON formatted policy file on the project side
via warning in doc and releasenotes.
Also replace policy.json to policy.yaml ref from doc and tests.
[1]https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html
Change-Id: I6fc6f7d95e4efde6ea3bd0f1e4134aa54ce3889a
Convert softwareImage properties such as 'min_disk', 'min_ram' and
'size' to bytes before storing it to 'vnf_software_images' db table.
Since the size in bytes will be a large number, the type of
'min_disk' and 'min_ram' columns of 'vnf_software_images' tables has
been changed to BigInt.
Closes-Bug: #1879436
Co-Authored-By: Prashant Bhole <prash.bhole@gmail.com>
Change-Id: I3bf839783863f84f507d9b15c6eab6250d9f5d30
Add file to the reno documentation build to show release notes for
stable/victoria.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/victoria.
Change-Id: I63ec18766b5a3782ff464fb4f6b505b1504c1523
Sem-Ver: feature
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
Remove docs requirements from lower-constraints, they are not needed
during install or test but only for docs building.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I785707fd8bc6608285c97ff273152db52a11079d
Add file to the reno documentation build to show release notes for
stable/ussuri.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/ussuri.
Change-Id: Ia3de19ad3bbbb5c85025ed0d9e9dfd872ebe6c9d
Sem-Ver: feature
As per ETSI GS NFV-SOL 005 V2.4.1 (2018-02) table 9.4.2.3.2-2, GET Vnf
Packages should return list of all Vnf packages, but as per current
implemention this api is returning dictionory with resource name as key
i.e {'vnf_packages': [{vnf_package1}, {vnf_package2},...]}. Hence
removing the resource key and returning api response as a list.
As per process to fix this issue we need to provide micro version
support in tacker as well as in python-tackerclient for command.
The list api was part of VNF package api which released in train cycle.
But we can not instantiate, terminate and Heal VNF as these feature is
not released yet and about to release in U cycle. The changes we have
proposed will be useful after U release and that is why we think we
should do these change without micro version support.
Closes-bug: #1871054
Change-Id: I7f5105fc7a49f9d31fb32119c725dae0421cfde7
Add file to the reno documentation build to show release notes for
stable/train.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/train.
Change-Id: I93da104660009f8780852410cfb6f1a5ababbd37
Sem-Ver: feature
Following are the list of documents updated for vnf package feature
usage:
1. api-reference document
2. release notes
Partial-Implements: blueprint tosca-csar-mgmt-driver
Change-Id: I82fc2e9d3f39e78b24eeb8034b0f611798c1aeb8
Some options are now automatically configured by the version 1.20:
- project
- html_last_updated_fmt
- latex_engine
- latex_elements
- version
- release.
Change-Id: Iae2061c63ba1eee98d979a22daf04756c485192b
