diff options
| author |   Bozawglanian, Hagop (hb755d) <hb755d@att.com> | 2018-03-12 21:55:55 +0000 |
|---|---|---|
| committer |   steven stark <ss820f@att.com> | 2018-03-15 09:43:38 -0700 |
| commit | 62aa8a359bccd4d79b0c03219f41c03bab2cb6db (patch) | |
| tree | c6d79e19ad8e4ebe7ba7dba6b727fa9e1771c956 | |
| parent | c4ace4929c2b2227c8f4df9eba035a96061424a0 (diff) | |
VNFRQTS - Update wording to clarify for errors
If error or exception leads to corruption of data, processing should be terminated properly.
Change-Id: Ie11a10783d17ae2e33546f8d363792aed6867d5e
Issue-ID: VNFRQTS-184
Signed-off-by: Bozawglanian, Hagop (hb755d) <hb755d@att.com>
Signed-off-by: steven stark <ss820f@att.com>
| -rw-r--r-- | docs/Chapter4.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/Chapter4.rst b/docs/Chapter4.rst index e970e1e..ac65980 100644 --- a/docs/Chapter4.rst +++ b/docs/Chapter4.rst @@ -116,8 +116,8 @@ Application Resilient Error Handling Requirements * 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. -* 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-80070 The VNF **MUST** handle errors and exceptions so that they do not interrupt processing of incoming VNF requests to maintain service continuity (where the error is not directly impacting the software handling the incoming request). +* 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. |