From 62f00e10d62e6a3c64801d70f370acdbc16ff51b Mon Sep 17 00:00:00 2001 From: Yasufumi Ogawa Date: Thu, 17 Oct 2024 15:45:50 +0900 Subject: [PATCH] Add placeholder for 2025.1 release Setup for the release under spec/2025.1, and fix warnings happened recently from the old specs having footnotes which is not referenced. Change-Id: I4b85316db93083b87f1d8cbcb3dab636cd549327 --- doc/source/index.rst | 1 + specs/2024.1/v2-api-horizon/index.rst | 1 - specs/2024.2/perf-improve-list-apis/index.rst | 2 +- specs/2025.1/index.rst | 9 ++ specs/2025.1/placeholder.rst | 124 ++++++++++++++++++ specs/newton/tacker-vnffg.rst | 1 - specs/pike/vnffg-scaling.rst | 2 +- .../kubernetes-type-for-containerized-VNF.rst | 1 - specs/queens/update-vnffg.rst | 1 - .../support-etsi-nfv-based-errorhandling.rst | 3 - 10 files changed, 136 insertions(+), 9 deletions(-) create mode 100644 specs/2025.1/index.rst create mode 100644 specs/2025.1/placeholder.rst diff --git a/doc/source/index.rst b/doc/source/index.rst index 209ba82a..1e6ac8d6 100644 --- a/doc/source/index.rst +++ b/doc/source/index.rst @@ -22,6 +22,7 @@ Specifications :glob: :maxdepth: 2 + specs/2025.1/index specs/2024.2/index specs/2024.1/index specs/2023.2/index diff --git a/specs/2024.1/v2-api-horizon/index.rst b/specs/2024.1/v2-api-horizon/index.rst index a8c2b5ce..7d9bab44 100644 --- a/specs/2024.1/v2-api-horizon/index.rst +++ b/specs/2024.1/v2-api-horizon/index.rst @@ -744,5 +744,4 @@ References .. [#v2_api] https://docs.openstack.org/api-ref/nfv-orchestration/v2/vnflcm.html .. [#paper_using_tacker] Lakshmanan S, Zhang M, Majumdar S, Jarraya Y, Pourzandi M, Wang L. Caught-in-Translation (CiT): Detecting Cross-level Inconsistency Attacks in Network Functions Virtualization (NFV). IEEE Transactions on Dependable and Secure Computing. 2023 Sep 29. -.. [#bp_horizon_testing] https://blueprints.launchpad.net/tacker/+spec/tacker-horizon-unittests .. [#tacker_cli] https://docs.openstack.org/tacker/latest/cli/index.html diff --git a/specs/2024.2/perf-improve-list-apis/index.rst b/specs/2024.2/perf-improve-list-apis/index.rst index 16a2825f..f4b60ab2 100644 --- a/specs/2024.2/perf-improve-list-apis/index.rst +++ b/specs/2024.2/perf-improve-list-apis/index.rst @@ -68,7 +68,7 @@ for considering the usage it actually. #. Refactor filtering Tacker supports a set of attributes for filtering as defined -in ETSI NFV SOL013 [#sol013]. +in ETSI NFV SOL013 [#sol013]_. In the implementation of filtering for these attributes, it does not use any filtering of database, but is done in Tacker's side after retrieving all the entries from the database. diff --git a/specs/2025.1/index.rst b/specs/2025.1/index.rst new file mode 100644 index 00000000..52c3c678 --- /dev/null +++ b/specs/2025.1/index.rst @@ -0,0 +1,9 @@ +============================ +Tacker 2025.1 Specifications +============================ + +.. toctree:: + :glob: + :maxdepth: 1 + + * diff --git a/specs/2025.1/placeholder.rst b/specs/2025.1/placeholder.rst new file mode 100644 index 00000000..9aaa6f08 --- /dev/null +++ b/specs/2025.1/placeholder.rst @@ -0,0 +1,124 @@ +.. + This work is licensed under a Creative Commons Attribution 3.0 Unported + License. + + http://creativecommons.org/licenses/by/3.0/legalcode + +================== +(Placeholder Spec) +================== + +This file is just a placeholder for the specs directory. +It will be removed soon after some spec is merged. + +The latest spec template is found at ``specs/template.rst`` +in the ``tacker-specs`` repository. + +Problem description +=================== + +Sphinx toctree complains if no file exists in a directory +specified in toctree glob. + +Use Cases +--------- + +None + +Proposed change +=============== + +Add this file. Please remove later when the another spec is approved. + +Alternatives +------------ + +None + +Data model impact +----------------- + +None + +REST API impact +--------------- + +None + +Security impact +--------------- + +None + +Notifications impact +-------------------- + +None + +Other end user impact +--------------------- + +None + +Performance Impact +------------------ + +None + +Other deployer impact +--------------------- + +None + +Developer impact +---------------- + +None + +Upgrade impact +-------------- + +None + + +Implementation +============== + +Assignee(s) +----------- + +None + +Work Items +---------- + +None + + +Dependencies +============ + +None + + +Testing +======= + +None + + +Documentation Impact +==================== + +None + +References +========== + +None + + +History +======= + +None diff --git a/specs/newton/tacker-vnffg.rst b/specs/newton/tacker-vnffg.rst index 3789d00f..c3c65de4 100644 --- a/specs/newton/tacker-vnffg.rst +++ b/specs/newton/tacker-vnffg.rst @@ -937,7 +937,6 @@ References .. [#first] https://datatracker.ietf.org/doc/draft-ietf-sfc-nsh/?include_text=1 .. [#second] https://github.com/pritesh/ovs/tree/nsh-v8 -.. [#third] https://wiki.openstack.org/wiki/Tacker/API .. [#fourth] https://github.com/openstack/networking-sfc/blob/master/doc/source/api.rst .. [#fifth] https://github.com/opendaylight/sfc .. [#sixth] https://tools.ietf.org/html/draft-ietf-netmod-acl-model-05 diff --git a/specs/pike/vnffg-scaling.rst b/specs/pike/vnffg-scaling.rst index 62b9d9a4..f897ac65 100644 --- a/specs/pike/vnffg-scaling.rst +++ b/specs/pike/vnffg-scaling.rst @@ -15,7 +15,7 @@ Problem description Currently, Tacker has already supported scaling function for individual VNFs by using alarm driver. However, when doing scaling in or out, the new-added or deleted instances' CP -cannot be added or removed to/from Neutron SFC port-pair group.[#second]_ +cannot be added or removed to/from Neutron SFC port-pair group [#second]_. This spec is supposed to provide scaling for VNFFG in single site, multi-sites support will be taken into account in the future. In addtition, diff --git a/specs/queens/kubernetes-type-for-containerized-VNF.rst b/specs/queens/kubernetes-type-for-containerized-VNF.rst index d593ba31..b7f8351f 100644 --- a/specs/queens/kubernetes-type-for-containerized-VNF.rst +++ b/specs/queens/kubernetes-type-for-containerized-VNF.rst @@ -455,5 +455,4 @@ Yes. We have to describe how to use containerized VNF's References ========== .. [#first] https://kubernetes.io/ -.. [#second] http://docs.oasis-open.org/tosca/tosca-nfv/v1.0/csd04/tosca-nfv-v1.0-csd04.html#_Toc482896065 .. [#third] http://www.etsi.org/deliver/etsi_gs/NFV-SWA/001_099/001/01.01.01_60/gs_NFV-SWA001v010101p.pdf diff --git a/specs/queens/update-vnffg.rst b/specs/queens/update-vnffg.rst index 63401bff..09effa3c 100644 --- a/specs/queens/update-vnffg.rst +++ b/specs/queens/update-vnffg.rst @@ -303,4 +303,3 @@ References ========== .. [#first] https://opendev.org/openstack/networking-sfc/src/branch/master/doc/api_samples -.. [#second] https://specs.openstack.org/openstack/tacker-specs/specs/newton/tacker-vnffg.html diff --git a/specs/victoria/support-etsi-nfv-based-errorhandling.rst b/specs/victoria/support-etsi-nfv-based-errorhandling.rst index e44066f9..cc994ca6 100644 --- a/specs/victoria/support-etsi-nfv-based-errorhandling.rst +++ b/specs/victoria/support-etsi-nfv-based-errorhandling.rst @@ -272,9 +272,6 @@ References ========== .. [#etsi_nfv] https://www.etsi.org/technologies-clusters/technologies/NFV -.. [#NFV-SOL002] - https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.06.01_60/gs_nfv-sol002v020601p.pdf - (Chapter 5: VNF Lifecycle Management interface) .. [#NFV-SOL003] https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_nfv-sol003v020601p.pdf (Chapter 5: VNF Lifecycle Management interface)