Increase Netconf CSIT Coverage (INTTEST-81)

[INTTEST-112] create-device RPC to mount and ensure NETCONF-670 is fixed Created: 06/Jul/20  Updated: 06/Jul/20

Status: Open
Project: integration-test
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Sub-task Priority: Medium
Reporter: Jamo Luhrsen Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

there is a create-device RPC to create a netconf mount. I don't know if it's used
anywhere in CSIT, but that would be the first step for this task.

once we have that working, we need to ensure two different config options work
in the original POST body. They come from the netconf-node-optional yang.

netconf-node-optional:ignore-missing-schema-sources
netconf-node-optional:datastore-lock

an example body that should work (fails at this point until NETCONF-670 is fixed) is
like this:

{
    "input": {
        "login-password": {
            "password": "password",
            "username": "username"
        },
        "netconf-node-optional:ignore-missing-schema-sources": {
            "reconnect-time": 5000,
            "allowed": true
        },
        "netconf-node-optional:datastore-lock": {
            "datastore-lock-allowed": true
        }
        "netconf-node-topology:node-id": "{{node}}",
        "actor-response-wait-time": 900,
        "concurrent-rpc-limit": 0,
        "host": "{{testtool-ip}}",
        "sleep-factor": 1,
        "port": 17830,
        "tcp-only": false,
        "connection-timeout-millis": 20000,
        "max-connection-attempts": 0,
        "keepalive-delay": 300,
        "schema-cache-directory": "MX2020-19.3R2.9",
        "between-attempts-timeout-millis": 2000,
        "schemaless": false,
        "default-request-timeout-millis": 600000
    }
}

The URI to send the POST will be like this:

http://{{controller-ip}}:8181/restconf/operations/netconf-node-topology:create-device

Generated at Wed Feb 07 20:04:36 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.