Re: Change in json to connect with southbound


Edward Warnicke <hagbard@...>
 

Doh... before was:

{
  "network-topology:node": [
        {
            "node-id": "ovsdb://10.10.10.10:16640",
            "ovsdb:port": 16640,
            "ovsdb:ip": "127.0.0.1"
        }
    ]
}

On Tue, Apr 14, 2015 at 10:24 AM, Multanen, Eric W <eric.w.multanen@...> wrote:

Before and After looks the same J

 

From: ovsdb-dev-bounces@... [mailto:ovsdb-dev-bounces@...] On Behalf Of Edward Warnicke
Sent: Tuesday, April 14, 2015 10:22 AM
To: ovsdb-dev@...
Subject: [ovsdb-dev] Change in json to connect with southbound

 

Guys,

 

     Yesterday, in order to more cleanly capture both the remote/local IP of a connection,

we shifted to putting that stuff under a container called ConnectionInfo in the ovsdb-node.

 

As a result, the json to connect changed from:

 

{

  "network-topology:node": [

        {

            "node-id": "ovsdb:/127.0.0.1: 16640",

            "connection-info": {

              "ovsdb:remote-port": 16640,

              "ovsdb:remote-ip": "127.0.0.1"

            }

        }

    ]

}

 

to 

 

{

  "network-topology:node": [

        {

            "node-id": "ovsdb://10.10.10.10:16640",

            "connection-info": {

              "ovsdb:remote-port": 16640,

              "ovsdb:remote-ip": "127.0.0.1"

            }

        }

    ]

}

 

Note the new enclosing connection-info.  Since there was some confusion, wanted to let folks know :)

 

(P.S.  this should already be fixed in the POSTMAN in the repo :) ).


Join z.archive.ovsdb-dev@lists.opendaylight.org to automatically receive all group messages.