diff options
| author |   Bozawglanian, Hagop (hb755d) <hb755d@att.com> | 2018-03-12 21:40:55 +0000 |
|---|---|---|
| committer | Bozawglanian, Hagop (hb755d) <hb755d@att.com> | 2018-03-12 21:48:13 +0000 |
| commit | e2181627463f3dad926c63e49d34407bc3ad1771 (patch) | |
| tree | 7e86212f56f09209c8689376fcce676be03a88d8 | |
| parent | f0cb47a2abc99fb0b02cc66ce9dbddae03dcf67a (diff) | |
VNFRQTS - Clarification for retries
The reason for this is that there will be a number of internal retry Timers in a vendors implementation that will not make sense to expose externally, also where specifications have specified restricted retry behaviour.
Change-Id: I5ba140b0008eb0595f094e25b48f9828eeb63165
Issue-ID: VNFRQTS-183
Signed-off-by: Bozawglanian, Hagop (hb755d) <hb755d@att.com>
| -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 2d99043..9ffc79b 100644 --- a/docs/Chapter4.rst +++ b/docs/Chapter4.rst @@ -112,7 +112,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. |