-
Bug
-
Resolution: Done
-
Medium
-
Casablanca Release
-
VNFRQTS Sprint 13
in R-89571: The xNF MUST support and provide artifacts for configuration management using at least one of the following technologies; a) Netconf/YANG, b) Chef, or c) Ansible.
So an PNF should support one the protocols. However, R-256347 has different statement: "The PNF MUST support the Ansible protocol for a Service Configuration message exchange between the PNF and PNF Controller (in ONAP)."
R-256347 is not inline with R-89571, which must be reworded or removed.
================== Proposed Change ======================
Requirement: R-256347
target: PNF
keyword: MUST
introduced: casablanca
The PNF MUST support one of the Ansible protocols for a Service Configuration message exchange between the PNF and PNF Controller (in ONAP): a) Netconf/YANG, b) Chef, or c) Ansible.
Note: this exchange may be either Ansible, Chef, or NetConf depending on the PNF. Note: The PNF Controller may be VF-C, APP-C or SDN-C based on the PNF and PNF domain. Note: for R3 (Casablanca) only Ansible is supported.
================== End of Proposed Change =================