From 0b5c5dd678fe592b952da66f1547fc77fe3490d6 Mon Sep 17 00:00:00 2001 From: Hagop Bozawglanian Date: Fri, 17 May 2019 20:24:25 +0000 Subject: VNFRQTS - Fixing Metadata for release Issue-ID: VNFRQTS-621 Change-Id: I269f9edd99e34fffb7916ee5ad63fdf35503bc14 Signed-off-by: Hagop Bozawglanian --- docs/Chapter7/Configuration-Management.rst | 160 +++++++++++++++------ docs/Chapter7/Monitoring-And-Management.rst | 42 +++++- docs/Chapter7/PNF-Plug-and-Play.rst | 3 +- .../VNF-On-boarding-and-package-management.rst | 26 ++++ 4 files changed, 189 insertions(+), 42 deletions(-) (limited to 'docs/Chapter7') diff --git a/docs/Chapter7/Configuration-Management.rst b/docs/Chapter7/Configuration-Management.rst index e728871..943f200 100755 --- a/docs/Chapter7/Configuration-Management.rst +++ b/docs/Chapter7/Configuration-Management.rst @@ -100,7 +100,7 @@ configuration update) is audited against the running configuration on the VNF :id: R-20741 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** support APPC/SDN-C ``Configure`` command. @@ -108,7 +108,7 @@ configuration update) is audited against the running configuration on the VNF :id: R-19366 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** support APPC ``ConfigModify`` command. @@ -116,7 +116,7 @@ configuration update) is audited against the running configuration on the VNF :id: R-32981 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** support APPC ``ConfigBackup`` command. @@ -124,7 +124,7 @@ configuration update) is audited against the running configuration on the VNF :id: R-48247 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** support APPC ``ConfigRestore`` command. @@ -132,7 +132,7 @@ configuration update) is audited against the running configuration on the VNF :id: R-94084 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** support APPC/SDN-C ``ConfigScaleOut`` command. @@ -140,7 +140,7 @@ configuration update) is audited against the running configuration on the VNF :id: R-56385 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** support APPC ``Audit`` command. @@ -218,6 +218,7 @@ UpgradePostCheck failed). :target: VNF or PNF :keyword: MUST :introduced: casablanca + :updated: dublin The VNF or PNF **MUST**, if serving as a distribution point or anchor point for steering point from source to destination, support the ONAP Controller's @@ -227,7 +228,7 @@ UpgradePostCheck failed). :id: R-12706 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** support APPC/SDN-C ``QuiesceTraffic`` command. @@ -235,7 +236,7 @@ UpgradePostCheck failed). :id: R-07251 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** support APPC/SDN-C ``ResumeTraffic`` command. @@ -243,7 +244,7 @@ UpgradePostCheck failed). :id: R-83146 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** support APPC ``StopApplication`` command. @@ -251,7 +252,7 @@ UpgradePostCheck failed). :id: R-82811 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** support APPC ``StartApplication`` command. @@ -259,7 +260,7 @@ UpgradePostCheck failed). :id: R-19922 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** support APPC/SDN-C ``UpgradePrecheck`` command. @@ -267,7 +268,7 @@ UpgradePostCheck failed). :id: R-49466 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** support APPC/SDN-C ``UpgradeSoftware`` command. @@ -275,7 +276,7 @@ UpgradePostCheck failed). :id: R-45856 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** support APPC/SDN-C ``UpgradePostCheck`` command. @@ -283,7 +284,7 @@ UpgradePostCheck failed). :id: R-97343 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** support APPC/SDN-C ``UpgradeBackup`` command. @@ -291,7 +292,7 @@ UpgradePostCheck failed). :id: R-65641 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** support APPC/SDN-C ``UpgradeBackOut`` command. @@ -326,7 +327,7 @@ automated fashion. :id: R-41430 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** support APPC/SDN-C ``HealthCheck`` command. @@ -379,6 +380,7 @@ Configuration Management :id: R-88026 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** include a NETCONF server enabling runtime configuration and lifecycle management capabilities. @@ -387,6 +389,7 @@ Configuration Management :id: R-95950 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** provide a NETCONF interface fully defined by supplied YANG models for the embedded NETCONF server. @@ -399,6 +402,7 @@ NETCONF Server Requirements :id: R-73468 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** allow the NETCONF server connection parameters to be configurable during virtual machine instantiation @@ -409,7 +413,7 @@ NETCONF Server Requirements :id: R-90007 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** implement the protocol operation: ``close-session()`` - Gracefully close the current session. @@ -418,7 +422,7 @@ NETCONF Server Requirements :id: R-70496 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** implement the protocol operation: ``commit(confirmed, confirm-timeout)`` - Commit candidate @@ -428,7 +432,7 @@ NETCONF Server Requirements :id: R-18733 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** implement the protocol operation: ``discard-changes()`` - Revert the candidate configuration @@ -438,7 +442,7 @@ NETCONF Server Requirements :id: R-44281 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** implement the protocol operation: ``edit-config(target, default-operation, test-option, error-option, @@ -449,6 +453,7 @@ NETCONF Server Requirements :id: R-60106 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** implement the protocol operation: ``get(filter)`` - Retrieve (a filtered subset of) the running @@ -459,7 +464,7 @@ NETCONF Server Requirements :id: R-29488 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** implement the protocol operation: ``get-config(source, filter`` - Retrieve a (filtered subset of @@ -469,7 +474,7 @@ NETCONF Server Requirements :id: R-11235 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** implement the protocol operation: ``kill-session(session``- Force the termination of **session**. @@ -478,7 +483,7 @@ NETCONF Server Requirements :id: R-02597 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** implement the protocol operation: ``lock(target)`` - Lock the configuration data store target. @@ -487,7 +492,7 @@ NETCONF Server Requirements :id: R-96554 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** implement the protocol operation: ``unlock(target)`` - Unlock the configuration data store target. @@ -496,7 +501,7 @@ NETCONF Server Requirements :id: R-29324 :target: VNF or PNF :keyword: SHOULD - :updated: casablanca + :updated: dublin The VNF or PNF **SHOULD** implement the protocol operation: ``copy-config(target, source)`` - Copy the content of the @@ -506,7 +511,7 @@ NETCONF Server Requirements :id: R-88031 :target: VNF or PNF :keyword: SHOULD - :updated: casablanca + :updated: dublin The VNF or PNF **SHOULD** implement the protocol operation: ``delete-config(target)`` - Delete the named configuration @@ -516,6 +521,7 @@ NETCONF Server Requirements :id: R-97529 :target: VNF or PNF :keyword: SHOULD + :updated: dublin The VNF or PNF **SHOULD** implement the protocol operation: ``get-schema(identifier, version, format)`` - Retrieve the YANG schema. @@ -524,6 +530,7 @@ NETCONF Server Requirements :id: R-62468 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** allow all configuration data to be edited through a NETCONF operation. Proprietary @@ -533,6 +540,7 @@ NETCONF Server Requirements :id: R-01382 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** allow the entire configuration of the VNF or PNF to be retrieved via NETCONF's and , independently @@ -542,6 +550,7 @@ NETCONF Server Requirements :id: R-28756 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** support ``:partial-lock`` and ``:partial-unlock`` capabilities, defined in RFC 5717. This @@ -552,6 +561,7 @@ NETCONF Server Requirements :id: R-83873 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** support ``:rollback-on-error`` value for the parameter to the operation. If any @@ -564,6 +574,7 @@ NETCONF Server Requirements :id: R-68990 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** support the ``:startup`` capability. It will allow the running configuration to be copied to this special @@ -573,6 +584,7 @@ NETCONF Server Requirements :id: R-68200 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** support the ``:url`` value to specify protocol operation source and target parameters. The capability URI @@ -585,6 +597,7 @@ NETCONF Server Requirements :id: R-20353 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** implement both ``:candidate`` and ``:writable-running`` capabilities. When both ``:candidate`` and @@ -594,6 +607,7 @@ NETCONF Server Requirements :id: R-11499 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** fully support the XPath 1.0 specification for filtered retrieval of configuration and other database contents. @@ -608,6 +622,7 @@ NETCONF Server Requirements :id: R-83790 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** implement the ``:validate`` capability. @@ -615,6 +630,7 @@ NETCONF Server Requirements :id: R-49145 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** implement ``:confirmed-commit`` If ``:candidate`` is supported. @@ -623,6 +639,7 @@ NETCONF Server Requirements :id: R-58358 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** implement the ``:with-defaults`` capability [RFC6243]. @@ -631,6 +648,7 @@ NETCONF Server Requirements :id: R-59610 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** implement the data model discovery and download as defined in [RFC6022]. @@ -639,6 +657,7 @@ NETCONF Server Requirements :id: R-93443 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** define all data models in YANG 1.0 [RFC6020] or YANG 1.1 [RFC7950]. A combination of YANG 1.0 and YANG 1.1 modules is @@ -649,6 +668,7 @@ NETCONF Server Requirements :id: R-26115 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** follow the data model update rules defined in [RFC6020] section 10 for YANG 1.0 modules, and [RFC7950] section 11 @@ -659,6 +679,7 @@ NETCONF Server Requirements :id: R-10716 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** support parallel and simultaneous configuration of separate objects within itself. @@ -667,6 +688,7 @@ NETCONF Server Requirements :id: R-29495 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** support locking if a common object is being manipulated by two simultaneous NETCONF configuration operations @@ -679,6 +701,7 @@ NETCONF Server Requirements :id: R-53015 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** apply locking based on the sequence of NETCONF operations, with the first configuration operation locking @@ -688,6 +711,7 @@ NETCONF Server Requirements :id: R-02616 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** permit locking at the finest granularity if a VNF or PNF needs to lock an object for configuration to avoid blocking @@ -700,6 +724,7 @@ NETCONF Server Requirements :id: R-41829 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** be able to specify the granularity of the lock via a restricted or full XPath expression. @@ -708,6 +733,7 @@ NETCONF Server Requirements :id: R-66793 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** guarantee the VNF or PNF configuration integrity for all simultaneous configuration operations (e.g., if a change is @@ -719,6 +745,7 @@ NETCONF Server Requirements :id: R-54190 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** release locks to prevent permanent lock-outs when/if a session applying the lock is terminated (e.g., SSH session @@ -728,6 +755,7 @@ NETCONF Server Requirements :id: R-03465 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** release locks to prevent permanent lock-outs when the corresponding operation succeeds. @@ -736,6 +764,7 @@ NETCONF Server Requirements :id: R-63935 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** release locks to prevent permanent lock-outs when a user configured timer has expired forcing the NETCONF SSH Session @@ -746,6 +775,7 @@ NETCONF Server Requirements :id: R-10173 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** allow another NETCONF session to be able to initiate the release of the lock by killing the session owning the lock, @@ -755,6 +785,7 @@ NETCONF Server Requirements :id: R-88899 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** support simultaneous operations within the context of this locking requirements framework. @@ -763,6 +794,7 @@ NETCONF Server Requirements :id: R-07545 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** support all operations, administration and management (OAM) functions available from the supplier for VNFs or PNFs @@ -772,6 +804,7 @@ NETCONF Server Requirements :id: R-60656 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** support sub tree filtering. @@ -779,6 +812,7 @@ NETCONF Server Requirements :id: R-80898 :target: VNF or PNF :keyword: MUST + :updated: dublin TThe VNF or PNF **MUST** support heartbeat via a with null filter. @@ -786,6 +820,7 @@ NETCONF Server Requirements :id: R-25238 :target: VNF :keyword: MUST + :updated: dublin The VNF or PNF PACKAGE **MUST** validated YANG code using the open source pyang [#7.3.1]_ program using the following commands: @@ -798,6 +833,7 @@ NETCONF Server Requirements :id: R-63953 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** have the echo command return a zero value otherwise the validation has failed. @@ -806,6 +842,7 @@ NETCONF Server Requirements :id: R-26508 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** support a NETCONF server that can be mounted on OpenDaylight (client) and perform the operations of: modify, update, @@ -821,6 +858,7 @@ conform, and those where applicable, that suppliers need to use. :id: R-22700 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** conform its YANG model to RFC 6470, "NETCONF Base Notifications". @@ -829,6 +867,7 @@ conform, and those where applicable, that suppliers need to use. :id: R-10353 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** conform its YANG model to RFC 6244, "An Architecture for Network Management Using NETCONF and YANG". @@ -837,6 +876,7 @@ conform, and those where applicable, that suppliers need to use. :id: R-53317 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** conform its YANG model to RFC 6087, "Guidelines for Authors and Reviewers of YANG Data Model specification". @@ -845,6 +885,7 @@ conform, and those where applicable, that suppliers need to use. :id: R-33955 :target: VNF or PNF :keyword: SHOULD + :updated: dublin The VNF or PNF **SHOULD** conform its YANG model to RFC 6991, "Common YANG Data Types". @@ -853,6 +894,7 @@ conform, and those where applicable, that suppliers need to use. :id: R-22946 :target: VNF or PNF :keyword: SHOULD + :updated: dublin The VNF or PNF **SHOULD** conform its YANG model to RFC 6536, "NETCONF Access Control Model". @@ -861,6 +903,7 @@ conform, and those where applicable, that suppliers need to use. :id: R-10129 :target: VNF or PNF :keyword: SHOULD + :updated: dublin The VNF or PNF **SHOULD** conform its YANG model to RFC 7223, "A YANG Data Model for Interface Management". @@ -869,6 +912,7 @@ conform, and those where applicable, that suppliers need to use. :id: R-12271 :target: VNF or PNF :keyword: SHOULD + :updated: dublin The VNF or PNF **SHOULD** conform its YANG model to RFC 7223, "IANA Interface Type YANG Module". @@ -877,6 +921,7 @@ conform, and those where applicable, that suppliers need to use. :id: R-49036 :target: VNF or PNF :keyword: SHOULD + :updated: dublin The VNF or PNF **SHOULD** conform its YANG model to RFC 7277, "A YANG Data Model for IP Management". @@ -885,6 +930,7 @@ conform, and those where applicable, that suppliers need to use. :id: R-87564 :target: VNF or PNF :keyword: SHOULD + :updated: dublin The VNF or PNF **SHOULD** conform its YANG model to RFC 7317, "A YANG Data Model for System Management". @@ -893,6 +939,7 @@ conform, and those where applicable, that suppliers need to use. :id: R-24269 :target: VNF or PNF :keyword: SHOULD + :updated: dublin The VNF or PNF **SHOULD** conform its YANG model to RFC 7407, "A YANG Data Model for SNMP Configuration", if Netconf used to @@ -906,6 +953,7 @@ NETCONF RFCs. :id: R-33946 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** conform to the NETCONF RFC 4741, "NETCONF Configuration Protocol". @@ -914,6 +962,7 @@ NETCONF RFCs. :id: R-04158 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** conform to the NETCONF RFC 4742, "Using the NETCONF Configuration Protocol over Secure Shell (SSH)". @@ -922,6 +971,7 @@ NETCONF RFCs. :id: R-13800 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** conform to the NETCONF RFC 5277, "NETCONF Event Notification". @@ -930,6 +980,7 @@ NETCONF RFCs. :id: R-01334 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** conform to the NETCONF RFC 5717, "Partial Lock Remote Procedure Call". @@ -938,6 +989,7 @@ NETCONF RFCs. :id: R-08134 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** conform to the NETCONF RFC 6241, "NETCONF Configuration Protocol". @@ -946,6 +998,7 @@ NETCONF RFCs. :id: R-78282 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** conform to the NETCONF RFC 6242, "Using the Network Configuration Protocol over Secure Shell". @@ -987,6 +1040,7 @@ REST APIs :id: R-31809 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** support the HealthCheck RPC. The HealthCheck RPC executes a VNF or PNF Provider-defined VNF or PNF HealthCheck over the @@ -1053,6 +1107,7 @@ Chef Client Requirements :id: R-79224 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** have the chef-client be preloaded with validator keys and configuration to register with the designated @@ -1062,6 +1117,7 @@ Chef Client Requirements :id: R-72184 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** have routable FQDNs for all the endpoints (VMs) of a VNF or PNF that contain chef-clients which are used to register @@ -1072,6 +1128,7 @@ Chef Client Requirements :id: R-47068 :target: VNF or PNF :keyword: MAY + :updated: dublin The VNF or PNF **MAY** expose a single endpoint that is responsible for all functionality. @@ -1080,6 +1137,7 @@ Chef Client Requirements :id: R-67114 :target: VNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** be installed with Chef-Client >= 12.0 and Chef push jobs client >= 2.0. @@ -1091,6 +1149,7 @@ Chef Roles/Requirements :id: R-27310 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF Package **MUST** include all relevant Chef artifacts (roles/cookbooks/recipes) required to execute VNF or PNF actions requested @@ -1100,7 +1159,7 @@ Chef Roles/Requirements :id: R-26567 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF Package **MUST** include a run list of roles/cookbooks/recipes, for each supported VNF or PNF action, that will @@ -1113,6 +1172,7 @@ Chef Roles/Requirements :id: R-98911 :target: VNF or PNF :keyword: MUST NOT + :updated: dublin The VNF or PNF **MUST NOT** use any instance specific parameters for the VNF or PNF in roles/cookbooks/recipes invoked for a VNF or PNF @@ -1122,6 +1182,7 @@ Chef Roles/Requirements :id: R-37929 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** accept all necessary instance specific data from the environment or node object attributes for the VNF or PNF @@ -1131,6 +1192,7 @@ Chef Roles/Requirements :id: R-62170 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** over-ride any default values for configurable parameters that can be set by ONAP in the roles, @@ -1140,6 +1202,7 @@ Chef Roles/Requirements :id: R-78116 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** update status on the Chef Server appropriately (e.g., via a fail or raise an exception) if the @@ -1150,6 +1213,7 @@ Chef Roles/Requirements :id: R-44013 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** populate an attribute, defined as node ['PushJobOutput'] with the desired output on all nodes in the push job @@ -1160,6 +1224,7 @@ Chef Roles/Requirements :id: R-30654 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF Package **MUST** have appropriate cookbooks that are designed to automatically 'rollback' to the original state in case of @@ -1170,6 +1235,7 @@ Chef Roles/Requirements :id: R-65755 :target: VNF or PNF :keyword: SHOULD + :updated: dublin The VNF or PNF **SHOULD** support callback URLs to return information to ONAP upon completion of the chef-client run for any chef-client run @@ -1188,6 +1254,7 @@ Chef Roles/Requirements :id: R-15885 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** Upon completion of the chef-client run, POST back on the callback URL, a JSON object as described in Table @@ -1278,7 +1345,7 @@ Ansible Client Requirements :id: R-32217 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** have routable management IP addresses or FQDNs that are reachable via the Ansible Server for the endpoints (VMs) of a @@ -1290,6 +1357,7 @@ Ansible Client Requirements :id: R-54373 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** have Python >= 2.6 on the endpoint VM(s) of a VNF or PNF on which an Ansible playbook will be executed. @@ -1298,7 +1366,7 @@ Ansible Client Requirements :id: R-35401 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** support SSH and allow SSH access by the Ansible server to the endpoint VM(s) and comply with the Network @@ -1308,7 +1376,7 @@ Ansible Client Requirements :id: R-82018 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** load the Ansible Server SSH public key onto VNF or PNF VM(s) /root/.ssh/authorized_keys as part of instantiation. Alternative, @@ -1331,7 +1399,7 @@ Ansible Client Requirements :id: R-92866 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** include as part of post-instantiation configuration done by Ansible Playbooks the removal/update of the SSH public key from @@ -1345,6 +1413,7 @@ Ansible Client Requirements :target: VNF or PNF :keyword: MUST :introduced: casablanca + :updated: dublin The VNF or PNF **MUST** permit authentication, using root account, only right after instantiation and until post-instantiation configuration is @@ -1355,6 +1424,7 @@ Ansible Client Requirements :target: VNF or PNF :keyword: MUST :introduced: casablanca + :updated: dublin The VNF or PNF **MUST** provide the ability to remove root access once post-instantiation configuration (Configure) is completed. @@ -1363,7 +1433,7 @@ Ansible Client Requirements :id: R-91745 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** update the Ansible Server and other entities storing and using the SSH keys for authentication when the SSH @@ -1377,6 +1447,7 @@ Ansible Client Requirements :target: VNF or PNF :keyword: MUST :introduced: casablanca + :updated: dublin The VNF or PNF **MUST** provide the ability to include a "from=" clause in SSH public keys associated with mechanized user IDs created for an Ansible @@ -1387,6 +1458,7 @@ Ansible Client Requirements :target: VNF or PNF :keyword: MUST :introduced: casablanca + :updated: dublin The VNF or PNF **MUST** define the "from=" clause to provide the list of IP addresses of the Ansible Servers in the Cluster, separated by coma, to @@ -1398,6 +1470,7 @@ Ansible Client Requirements :target: VNF or PNF :keyword: MUST :introduced: casablanca + :updated: dublin The VNF or PNF **MUST** provide Ansible playbooks that are designed to run using an inventory hosts file in a supported format with only IP addresses @@ -1408,6 +1481,7 @@ Ansible Client Requirements :target: VNF or PNF :keyword: MUST :introduced: casablanca + :updated: dublin The VNF or PNF **MUST** provide Ansible playbooks that are designed to run using an inventory hosts file in a supported format; with group names @@ -1419,6 +1493,7 @@ Ansible Client Requirements :target: VNF or PNF :keyword: MUST :introduced: casablanca + :updated: dublin The VNF or PNF **MUST** provide Ansible playbooks that are designed to run using an inventory hosts file in a supported format; with site group that @@ -1437,6 +1512,7 @@ complete the desired action. :target: VNF or PNF :keyword: MUST :introduced: casablanca + :updated: dublin The VNF or PNF **MUST** support Ansible playbooks that are compatible with Ansible version 2.6 or later. @@ -1445,6 +1521,7 @@ complete the desired action. :id: R-40293 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** make available playbooks that conform to the ONAP requirement. @@ -1453,7 +1530,7 @@ complete the desired action. :id: R-49396 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** support each APPC/SDN-C VNF or PNF action by invocation of **one** playbook [#7.3.4]_. The playbook will be @@ -1464,6 +1541,7 @@ complete the desired action. :id: R-33280 :target: VNF or PNF :keyword: MUST NOT + :updated: dublin The VNF or PNF **MUST NOT** use any instance specific parameters in a playbook. @@ -1472,7 +1550,7 @@ complete the desired action. :id: R-48698 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** utilize information from key value pairs that will be provided by the Ansible Server as "extra-vars" during invocation to @@ -1499,6 +1577,7 @@ will be considered to have failed. :id: R-43253 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** use playbooks designed to allow Ansible Server to infer failure or success based on the "PLAY_RECAP" capability. @@ -1511,7 +1590,7 @@ will be considered to have failed. :id: R-50252 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** write to a response file in JSON format that will be retrieved and made available by the Ansible Server if, as part of a VNF @@ -1526,7 +1605,7 @@ will be considered to have failed. :id: R-51442 :target: VNF or PNF :keyword: SHOULD - :updated: casablanca + :updated: dublin The VNF or PNF **SHOULD** use playbooks that are designed to automatically 'rollback' to the original state in case of any errors @@ -1543,7 +1622,7 @@ will be considered to have failed. :id: R-58301 :target: VNF or PNF :keyword: SHOULD NOT - :updated: casablanca + :updated: dublin The VNF or PNF **SHOULD NOT** use playbooks that make requests to Cloud resources e.g. Openstack (nova, neutron, glance, heat, etc.); @@ -1563,7 +1642,7 @@ will be considered to have failed. :id: R-02651 :target: VNF or PNF :keyword: SHOULD - :updated: casablanca + :updated: dublin The VNF or PNF **SHOULD** use available backup capabilities to save a copy of configuration files before implementing changes to support @@ -1575,7 +1654,7 @@ will be considered to have failed. :id: R-43353 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF **MUST** return control from Ansible Playbooks only after all tasks performed by playbook are fully complete, signaling that the @@ -1703,6 +1782,7 @@ performs a full VNF or PNF health check. :target: VNF or PNF :keyword: SHOULD :introduced: casablanca + :updated: dublin The VNF or PNF provider **MUST** deliver a new set of playbooks that includes all updated and unchanged playbooks for any new revision to an @@ -1712,7 +1792,7 @@ performs a full VNF or PNF health check. :id: R-49911 :target: VNF or PNF :keyword: SHOULD - :updated: casablanca + :updated: dublin :introduced: casablanca The VNF or PNF provider **MUST** assign a new point release to the updated diff --git a/docs/Chapter7/Monitoring-And-Management.rst b/docs/Chapter7/Monitoring-And-Management.rst index 2b85a19..da2a2bc 100755 --- a/docs/Chapter7/Monitoring-And-Management.rst +++ b/docs/Chapter7/Monitoring-And-Management.rst @@ -132,6 +132,7 @@ sender and other identifying characteristics related to the domain and event. :validation_mode: in_service :impacts: dcae :keyword: MUST + :updated: dublin The VNF **MUST** produce VES events that include the following mandatory fields in the common event header. @@ -315,6 +316,7 @@ Data Structure Specification of the Event Record :introduced: casablanca :validation_mode: static :impacts: dcae + :updated: dublin The VNF or PNF provider **MUST** provide a YAML file formatted in adherence with the :doc:`VES Event Registration specification <../../../../vnfsdk/model.git/docs/files/VESEventRegistration_3_0>` @@ -332,6 +334,7 @@ Data Structure Specification of the Event Record :introduced: casablanca :validation_mode: static :impacts: dcae + :updated: dublin The VNF or PNF provider **MUST** indicate specific conditions that may arise, and recommend actions that may be taken at specific thresholds, or if specific @@ -354,6 +357,7 @@ These changes may modify any of the following: :introduced: casablanca :validation_mode: in_service :impacts: dcae + :updated: dublin The events produced by the VNF or PNF **MUST** must be compliant with the common event format defined in the @@ -367,6 +371,7 @@ These changes may modify any of the following: :introduced: casablanca :validation_mode: in_service :impacts: dcae + :updated: dublin The VNF or PNF Provider **MAY** require that specific events, identified by their ``eventName``, require that certain fields, which are optional in the common @@ -389,6 +394,7 @@ minimizing changes to data delivery. :impacts: dcae :validation_mode: in_service :introduced: casablanca + :updated: dublin The VNF or PNF **SHOULD** deliver event records that fall into the event domains supported by VES. @@ -426,6 +432,7 @@ particular data sets. :impacts: dcae :validation_mode: none :introduced: casablanca + :updated: dublin The VNF or PNF provider **MUST** reach agreement with the Service Provider on the selected methods for encoding, serialization and data delivery @@ -442,6 +449,7 @@ VNF or PNF Telemetry using VES/JSON Model :impacts: dcae :validation_mode: in_service :introduced: casablanca + :updated: dublin The VNF or PNF **SHOULD** leverage the JSON-driven model, as depicted in Figure 2, for data delivery unless there are specific performance or operational @@ -462,6 +470,7 @@ VNF or PNF Telemetry using Google Protocol Buffers :impacts: dcae :validation_mode: in_service :introduced: casablanca + :updated: dublin The VNF or PNF **MAY** leverage the Google Protocol Buffers (GPB) delivery model depicted in Figure 3 to support real-time performance management (PM) data. @@ -495,6 +504,7 @@ Bulk Telemetry Transmission :introduced: casablanca :impacts: dcae, dmaap :validation_mode: in_service + :updated: dublin The VNF or PNF **MAY** leverage bulk VNF or PNF telemetry transmission mechanism, as depicted in Figure 4, in instances where other transmission methods are not @@ -524,6 +534,7 @@ VNF telemetry via standardized interface :introduced: casablanca :impacts: dcae :validation_mode: in_service + :updated: dublin The VNF or PNF MUST produce heartbeat indicators consisting of events containing the common event header only per the VES Listener Specification. @@ -536,7 +547,7 @@ JSON :id: R-19624 :target: VNF or PNF :keyword: MUST - :updated: casablanca + :updated: dublin The VNF or PNF, when leveraging JSON for events, **MUST** encode and serialize content delivered to ONAP using JSON (RFC 7159) plain text format. @@ -588,6 +599,7 @@ Google Protocol Buffers (GPB) :keyword: MUST :introduced: casablanca :validation_mode: in_service + :updated: dublin The VNF or PNF, when leveraging Google Protocol Buffers for events, **MUST** serialize the events using native Google Protocol Buffers (GPB) according @@ -607,6 +619,7 @@ Google Protocol Buffers (GPB) :keyword: MUST :introduced: casablanca :validation_mode: static + :updated: dublin The VNF or PNF providers **MUST** provide the Service Provider the following artifacts to support the delivery of high-volume VNF or PNF telemetry to @@ -628,6 +641,7 @@ Reporting Frequency :keyword: MUST :introduced: casablanca :validation_mode: in_service + :updated: dublin The VNF or PNF **MUST** report exactly one Measurement event per period per source name. @@ -636,6 +650,7 @@ Reporting Frequency :id: R-98191 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** vary the frequency that asynchronous data is delivered based on the content and how data may be aggregated or @@ -676,6 +691,7 @@ of bulk files. :id: R-88482 :target: VNF or PNF :keyword: SHOULD + :updated: dublin The VNF or PNF **SHOULD** use REST using HTTPS delivery of plain text JSON for moderate sized asynchronous data sets, and for high @@ -685,6 +701,7 @@ of bulk files. :id: R-84879 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** have the capability of maintaining a primary and backup DNS name (URL) for connecting to ONAP collectors, with the @@ -699,6 +716,7 @@ of bulk files. :id: R-81777 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** be configured with initial address(es) to use at deployment time. Subsequently, address(es) may be changed through @@ -710,6 +728,7 @@ of bulk files. :id: R-08312 :target: VNF or PNF :keyword: MAY + :updated: dublin The VNF or PNF **MAY** use another option which is expected to include REST delivery of binary encoded data sets. @@ -718,6 +737,7 @@ of bulk files. :id: R-79412 :target: VNF or PNF :keyword: MAY + :updated: dublin The VNF or PNF **MAY** use another option which is expected to include TCP for high volume streaming asynchronous data sets and for other high volume @@ -728,6 +748,7 @@ of bulk files. :id: R-01033 :target: VNF or PNF :keyword: MAY + :updated: dublin The VNF or PNF **MAY** use another option which is expected to include SFTP for asynchronous bulk files, such as bulk files that contain large volumes @@ -739,6 +760,7 @@ of bulk files. :id: R-63229 :target: VNF or PNF :keyword: MAY + :updated: dublin The VNF or PNF **MAY** use another option which is expected to include REST for synchronous data, using RESTCONF (e.g., for VNF or PNF state polling). @@ -747,6 +769,7 @@ of bulk files. :id: R-03070 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST**, by ONAP Policy, provide the ONAP addresses as data destinations for each VNF or PNF, and may be changed by Policy while @@ -761,6 +784,7 @@ Asynchronous and Synchronous Data Delivery :id: R-06924 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** deliver asynchronous data as data becomes available, or according to the configured frequency. @@ -769,6 +793,7 @@ Asynchronous and Synchronous Data Delivery :id: R-73285 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** must encode, address and deliver the data as described in the previous paragraphs. @@ -777,6 +802,7 @@ Asynchronous and Synchronous Data Delivery :id: R-42140 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** respond to data requests from ONAP as soon as those requests are received, as a synchronous response. @@ -785,6 +811,7 @@ Asynchronous and Synchronous Data Delivery :id: R-34660 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** use the RESTCONF/NETCONF framework used by the ONAP configuration subsystem for synchronous communication. @@ -793,6 +820,7 @@ Asynchronous and Synchronous Data Delivery :id: R-86586 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** use the YANG configuration models and RESTCONF [RFC8040] (https://tools.ietf.org/html/rfc8040). @@ -801,6 +829,7 @@ Asynchronous and Synchronous Data Delivery :id: R-11240 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** respond with content encoded in JSON, as described in the RESTCONF specification. This way the encoding of a @@ -810,6 +839,7 @@ Asynchronous and Synchronous Data Delivery :id: R-70266 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** respond to an ONAP request to deliver the current data for any of the record types defined in @@ -826,6 +856,7 @@ Asynchronous and Synchronous Data Delivery :impacts: dcae :validation_mode: in_service :introduced: casablanca + :updated: dublin The VNF or PNF **SHOULD** deliver all syslog messages to the VES Collector per the specifications in Monitoring and Management chapter. @@ -834,6 +865,7 @@ Asynchronous and Synchronous Data Delivery :id: R-46290 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** respond to an ONAP request to deliver granular data on device or subsystem status or performance, referencing the YANG @@ -843,6 +875,7 @@ Asynchronous and Synchronous Data Delivery :id: R-43327 :target: VNF or PNF :keyword: SHOULD + :updated: dublin The VNF or PNF **SHOULD** use `Modeling JSON text with YANG `_, If YANG models need to be @@ -857,6 +890,7 @@ Security :id: R-42366 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** support secure connections and transports such as Transport Layer Security (TLS) protocol @@ -868,6 +902,7 @@ Security :id: R-44290 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** control access to ONAP and to VNFs or PNFs, and creation of connections, through secure credentials, log-on and exchange mechanisms. @@ -876,6 +911,7 @@ Security :id: R-47597 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** carry data in motion only over secure connections. @@ -883,6 +919,7 @@ Security :id: R-68165 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** encrypt any content containing Sensitive Personal Information (SPI) or certain proprietary data, in addition to applying the @@ -929,6 +966,7 @@ Bulk Performance Measurement :keyword: SHOULD :introduced: casablanca :impacts: dcae, dmaap + :updated: dublin The VNF or PNF **SHOULD** support FileReady VES event for event-driven bulk transfer of monitoring data. @@ -940,6 +978,7 @@ Bulk Performance Measurement :keyword: SHOULD :introduced: casablanca :impacts: dcae, dmaap + :updated: dublin The VNF or PNF **SHOULD** support File transferring protocol, such as FTPES or SFTP, when supporting the event-driven bulk transfer of monitoring data. @@ -950,6 +989,7 @@ Bulk Performance Measurement :keyword: SHOULD :introduced: casablanca :impacts: dcae, dmaap + :updated: dublin The VNF or PNF **SHOULD** support the data schema defined in 3GPP TS 32.435, when supporting the event-driven bulk transfer of monitoring data. diff --git a/docs/Chapter7/PNF-Plug-and-Play.rst b/docs/Chapter7/PNF-Plug-and-Play.rst index e3e642b..ce60f81 100644 --- a/docs/Chapter7/PNF-Plug-and-Play.rst +++ b/docs/Chapter7/PNF-Plug-and-Play.rst @@ -36,7 +36,7 @@ The following are the requirements related to PNF Plug and Play. :target: PNF :keyword: SHOULD :introduced: casablanca - :update: El Alto + :updated: El Alto The following VES Events **SHOULD** be supported by the PNF: pnfRegistration VES Event, HVol VES Event, and Fault VES Event. These are onboarded via @@ -192,6 +192,7 @@ The following are the requirements related to PNF Plug and Play. :target: PNF :keyword: MUST :introduced: casablanca + :updated: dublin The PNF **MUST** support one of the protocols for a Service Configuration message exchange between the PNF and PNF Controller (in ONAP): diff --git a/docs/Chapter7/VNF-On-boarding-and-package-management.rst b/docs/Chapter7/VNF-On-boarding-and-package-management.rst index 662ff53..dc2800a 100755 --- a/docs/Chapter7/VNF-On-boarding-and-package-management.rst +++ b/docs/Chapter7/VNF-On-boarding-and-package-management.rst @@ -119,6 +119,7 @@ Resource Description :id: R-98617 :target: VNF PROVIDER :keyword: MUST + :updated: dublin The VNF Provider **MUST** provide documentation regarding any dependency (e.g. affinity, anti-affinity) the VNF has on other VNFs and resources. @@ -181,6 +182,7 @@ Resource Configuration :id: R-89571 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** support and provide artifacts for configuration management using at least one of the following technologies; @@ -211,6 +213,7 @@ Configuration Management via Chef :id: R-13390 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF provider **MUST** provide cookbooks to be loaded on the appropriate Chef Server. @@ -219,6 +222,7 @@ Configuration Management via Chef :id: R-18525 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF provider **MUST** provide a JSON file for each supported action for the VNF or PNF. The JSON file must contain key value @@ -237,6 +241,7 @@ Configuration Management via Ansible :id: R-75608 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF provider **MUST** provide playbooks to be loaded on the appropriate Ansible Server. @@ -245,6 +250,7 @@ Configuration Management via Ansible :id: R-16777 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF provider **MUST** provide a JSON file for each supported action for the VNF or PNF. The JSON file must contain key value @@ -256,6 +262,7 @@ Configuration Management via Ansible :id: R-46567 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF Package **MUST** include configuration scripts for boot sequence and configuration. @@ -264,6 +271,7 @@ Configuration Management via Ansible :id: R-16065 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF provider **MUST** provide configurable parameters (if unable to conform to YANG model) including VNF or PNF attributes/parameters @@ -310,6 +318,7 @@ Resource Control Loop :id: R-35960 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF Package **MUST** include documentation which must include all events, severity level (e.g., informational, warning, error) and @@ -319,6 +328,7 @@ Resource Control Loop :id: R-42018 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF Package **MUST** include documentation which must include all events (fault, measurement for VNF or PNF Scaling, Syslogs, State Change @@ -340,6 +350,7 @@ Resource Control Loop :id: R-73560 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF Package **MUST** include documentation about monitoring parameters/counters exposed for virtual resource management and VNF or PNF @@ -349,6 +360,7 @@ Resource Control Loop :id: R-90632 :target: VNF :keyword: MUST + :updated: dublin The VNF Package **MUST** include documentation about KPIs and metrics that need to be collected at each VM for capacity planning @@ -358,6 +370,7 @@ Resource Control Loop :id: R-86235 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF Package **MUST** include documentation about the monitoring parameters that must include latencies, success rates, retry rates, load @@ -369,6 +382,7 @@ Resource Control Loop :id: R-33904 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF Package **MUST** include documentation for each KPI, provide lower and upper limits. @@ -387,6 +401,7 @@ Resource Control Loop :id: R-69877 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF Package **MUST** include documentation for each KPI, identify the suggested actions that need to be performed when a @@ -407,6 +422,7 @@ Resource Control Loop :id: R-33694 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF Package **MUST** include documentation to when applicable, provide calculators needed to convert raw data into appropriate reporting @@ -490,6 +506,7 @@ Compute, Network, and Storage Requirements :id: R-26881 :target: VNF :keyword: MUST + :updated: dublin The VNF provider **MUST** provide the binaries and images needed to instantiate the VNF (VNF and VNFC images). @@ -521,6 +538,7 @@ Testing :id: R-04298 :target: VNF :keyword: MUST + :updated: dublin The VNF provider **MUST** provide their testing scripts to support testing. @@ -529,6 +547,7 @@ Testing :id: R-58775 :target: VNF :keyword: MUST + :updated: dublin The VNF provider **MUST** provide software components that can be packaged with/near the VNF, if needed, to simulate any functions @@ -544,6 +563,7 @@ Licensing Requirements :id: R-85653 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF **MUST** provide metrics (e.g., number of sessions, number of subscribers, number of seats, etc.) to ONAP for tracking @@ -553,6 +573,7 @@ Licensing Requirements :id: R-44125 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF provider **MUST** agree to the process that can be met by Service Provider reporting infrastructure. The Contract @@ -562,6 +583,7 @@ Licensing Requirements :id: R-40827 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF provider **MUST** enumerate all of the open source licenses their VNF or PNF(s) incorporate. @@ -570,6 +592,7 @@ Licensing Requirements :id: R-97293 :target: VNF or PNF :keyword: MUST NOT + :updated: dublin The VNF or PNF provider **MUST NOT** require audits of Service Provider's business. @@ -578,6 +601,7 @@ Licensing Requirements :id: R-44569 :target: VNF or PNF :keyword: MUST NOT + :updated: dublin The VNF or PNF provider **MUST NOT** require additional infrastructure such as a VNF or PNF provider license server for VNF or PNF provider @@ -605,6 +629,7 @@ Licensing Requirements :id: R-85991 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF provider **MUST** provide a universal license key per VNF or PNF to be used as needed by services (i.e., not tied to a VM @@ -617,6 +642,7 @@ Licensing Requirements :id: R-47849 :target: VNF or PNF :keyword: MUST + :updated: dublin The VNF or PNF provider **MUST** support the metadata about licenses (and their applicable entitlements) as defined in this -- cgit 1.2.3-korg