diff options
author | 2018-03-13 12:02:15 +0000 | |
---|---|---|
committer | 2018-03-13 12:02:15 +0000 | |
commit | cbf6bc11b9e92d6e53499eec6392ecd4d0539533 (patch) | |
tree | 5c50d7cadd3d4ca768dc7a3bae1782ed3b2462ec /docs/Chapter4.rst | |
parent | 94bdfe8a4807d25be1ec2bd4616edf6f6b67b4ec (diff) | |
parent | e2181627463f3dad926c63e49d34407bc3ad1771 (diff) |
Merge "VNFRQTS - Clarification for retries"
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 e24553d..745be04 100644 --- a/docs/Chapter4.rst +++ b/docs/Chapter4.rst @@ -117,7 +117,7 @@ Application Resilient Error Handling Requirements * 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. -* R-32695 The VNF **MUST** provide the ability to modify the number of retries, the time between retries and the behavior/action taken after the retries have been exhausted for exception handling to allow the NCSP to control that behavior. +* R-32695 The VNF **MUST** provide the ability to modify the number of retries, the time between retries and the behavior/action taken after the retries have been exhausted for exception handling to allow the NCSP to control that behavior,where the interface and/or functional specification allows for altering behaviour. * R-48356 The VNF **MUST** fully exploit exception handling to the extent that resources (e.g., threads and memory) are released when no longer needed regardless of programming language. * R-67918 The VNF **MUST** handle replication race conditions both locally and geo-located in the event of a data base instance failure to maintain service continuity. * R-36792 The VNF **MUST** automatically retry/resubmit failed requests made by the software to its downstream system to increase the success rate. |