diff options
| author |   Steven Wright <sw3588@att.com> | 2018-03-13 12:02:30 +0000 |
|---|---|---|
| committer |   Gerrit Code Review <gerrit@onap.org> | 2018-03-13 12:02:30 +0000 |
| commit | 9eb88e594d2138351ba7fd541ea0840882897685 (patch) | |
| tree | c2e30b865724541209b72ea6e1ef4d4fb7d7dbb6 /docs/Chapter4.rst | |
| parent | cbf6bc11b9e92d6e53499eec6392ecd4d0539533 (diff) | |
| parent | 4186020c04e81ff3d8d624bf92ae6605b37f0868 (diff) | |
Merge "VNFRQTS - R-26371 wording update to clarify req"
Diffstat (limited to 'docs/Chapter4.rst')
| -rw-r--r-- | docs/Chapter4.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/Chapter4.rst b/docs/Chapter4.rst index 745be04..bc4733a 100644 --- a/docs/Chapter4.rst +++ b/docs/Chapter4.rst @@ -113,7 +113,7 @@ applications. Application Resilient Error Handling Requirements -* R-26371 The VNF **MUST** detect connectivity failure for inter VNFC instance and intra/inter VNF and re-establish connectivity automatically to maintain the VNF without manual intervention to provide service continuity. +* R-26371 The VNF **MUST** detect communication failure for inter VNFC instance and intra/inter VNF and re-establish communication automatically to maintain the VNF without manual intervention to provide service continuity. * R-18725 The VNF **MUST** handle the restart of a single VNFC instance without requiring all VNFC instances to be restarted. * R-06668 The VNF **MUST** handle the start or restart of VNFC instances in any order with each VNFC instance establishing or re-establishing required connections or relationships with other VNFC instances and/or VNFs required to perform the VNF function/role without requiring VNFC instance(s) to be started/restarted in a particular order. * R-80070 The VNF **MUST** handle errors and exceptions so that they do not interrupt processing of incoming VNF requests to maintain service continuity. |