Page Comparison

Configuration & Persistency Service

Discussion about Messageflows for CMNotify from VES-Collector to "RuntimeDB". 

• Options:
  • RuntimeDB listen on DMaaP as described: 
    ARCHCOM: InfoFlow - RunTime Config DB Information Flow#3.1FLOW1:VESInformationFlowCMNotify-WritingtoRunTimeDB 
    • Fits to the overall ONAP architecture
  • SDN-R listen on DMaaP and a function or µService updates RuntimeDB 
    • Comment: such function or µService for sure under the responsibility for RuntimeDB - SDN-R is not involved - however such function or µService coudl or could not deploy together with SDN-R → this could be a deployment option and would need to be configured by OOM helm charts.
    • This option is not discussed and specificed and does not fit much into the ONAP architecture. 

Discussion about Messageflow from "RuntimeDB" to NetConf Servers

• According to ARCHCOM: InfoFlow - RunTime Config DB Information Flow#3.1FLOW4:ControllerSendingConfigurationInfoUpdateFlow-WritingtoRunTimeDB the controller listen on a related topic and forwards the message body to the addressed NetConf Server. Details need to be specified - SDN-R has the infrastructure for this message flow available.

Info found after the meeting (not discussed)

• 2020-04-29: Configuration & Persistency Service

  • TSC to approve proposed project

Yang error messages - RFC7950

yang defined error-messages are supported for the following yang statements.

• 7.5.4. The must's Substatements
• 9.2.4.1. The range's Substatements
• 9.4.4.1. The length's Substatements
• 9.4.5.1. The pattern's Substatements

Example:

[...]
must "./ssh-connections + ./tls-connections <= 100" {

   error-message "The total number of connections (SSH + TLS) needs to be less than or equal with 100.";
}
[...]

Result in odl-restconf-nb-baermann

{
"errors": {
  "error": [
    {
      "error-type": "application",
      "error-tag": "operation-failed",
      "error-message": "Commit of transaction org.opendaylight.netconf.sal.connect.netconf.sal.tx.WriteCandidateRunningTx@2aa1fb85 failed",
      "error-info": "RemoteDevice{NTS-manager}:RPC during tx failed. The total number of connections (SSH + TLS) 
                     needs to be less than or equal with 100."
    }
    ]
  }
}

Result in odl-restconf-nb-RFC8040

{
  "errors": {
    "error": [
      {
        "error-type": "application",
        "error-message": "RemoteDevice{NTS-manager}:RPC during tx failed. The total number of connections (SSH + TLS) 
                          needs to be less than or equal with 100.",
        "error-tag": "operation-failed",
         "error-info": "TransactionCommitFailedException{message=Commit of transaction 
                        org.opendaylight.netconf.sal.connect.netconf.sal.tx.WriteCandidateRunningTx@adb0c99 failed, 
                        errorList=[RpcError [message=Commit of transaction 
                        org.opendaylight.netconf.sal.connect.netconf.sal.tx.WriteCandidateRunningTx@adb0c99 failed, 
                        severity=ERROR, errorType=APPLICATION, tag=operation-failed, applicationTag=null, info=null, 
                        cause=NetconfDocumentedException{message=RemoteDevice{NTS-manager}:RPC during tx failed. The total number 
                        of connections (SSH + TLS) needs to be less than or equal with 100., errorType=APPLICATION, 
                        errorTag=OPERATION_FAILED, errorSeverity=ERROR, errorInfo={}}]]}"
      }
    ]
  }
}

Geo-redundancy

>> goes to next meeting

Overview

Impact on SDN-R

--

see: SDN-R Geo-Redundancy