|
Re: How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?
Yang, Yi Y <yi.y.yang@...>
Anil, thank you so much, I checked it again, I can get openflow node ID using datapath-id.
Another question is how I map an OVS port like “tap1” to openflow tp id like “openflow:1:2”?
In openflow network topology, l2switch can host nodes that connect to openflow switch, but in OVSDB network topology, I can’t get similar piece. It will be very great if ovsdb can add them. Now I can see full network topology by openflow network topology, but OVSDB can’t provide info of VMs connected to ovs bridge.
{ "node-id": "host:00:00:00:00:00:01", "termination-point": [ { "tp-id": "host:00:00:00:00:00:01" } ], "host-tracker-service:id": "00:00:00:00:00:01", "host-tracker-service:addresses": [ { "id": 7, "mac": "00:00:00:00:00:01", "ip": "10.0.0.1", "first-seen": 1431084716588, "last-seen": 1431084716588 } ], "host-tracker-service:attachment-points": [ { "tp-id": "openflow:1:1", "corresponding-tp": "host:00:00:00:00:00:01", "active": true } ] }
From: Anil Vishnoi [mailto:vishnoianil@...]
Sent: Thursday, June 04, 2015 3:53 PM To: Vishal Thapar Cc: Yang, Yi Y; ovsdb-dev@... Subject: Re: [ovsdb-dev] How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?
Hi Yi/Vishal,
Please refer to ./southbound/southbound-api/src/main/yang/ovsdb.yang file. Southbound plugin augment bridge operational data to topology tree
augment "/topo:network-topology/topo:topology/topo:node" { description "Augmentation for bridge nodes managed by ovsdb"; ext:augment-identifier "ovsdb-bridge-augmentation"; uses ovsdb-bridge-attributes; }
Ovsdb-bridge-attributes contains operational data of the bridge and it has datapath-id as one of the element.
leaf datapath-id { description "Datapath-id of the bridge"; type datapath-id; }
You can use this datapath-id to determine the Openflow registration id "openflow:<datapath-id>".
Thanks Anil
On Thu, Jun 4, 2015 at 12:05 PM, Vishal Thapar <vishal.thapar@...> wrote:
-- Thanks Anil |
|
|
|
Re: How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?
Anil Vishnoi
I believe not, for that you will have to read the ovsdb node and iterate through all the bridge created on that ovsdb node and match based on the data path id. On Thu, Jun 4, 2015 at 1:29 PM, Vishal Thapar <vishal.thapar@...> wrote:
--
Thanks Anil |
|
|
|
Re: How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?
Vishal Thapar <vishal.thapar@...>
Hi Anil,
Thanks, this is very helpful. One more question, is there any similar mapping of OF Node Id to OVSDB Bridge node?
Regards, Vishal.
From: Anil Vishnoi [mailto:vishnoianil@...]
Sent: 04 June 2015 13:23 To: Vishal Thapar Cc: Yang, Yi Y; ovsdb-dev@... Subject: Re: [ovsdb-dev] How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?
Hi Yi/Vishal,
Please refer to ./southbound/southbound-api/src/main/yang/ovsdb.yang file. Southbound plugin augment bridge operational data to topology tree
augment "/topo:network-topology/topo:topology/topo:node" { description "Augmentation for bridge nodes managed by ovsdb"; ext:augment-identifier "ovsdb-bridge-augmentation"; uses ovsdb-bridge-attributes; }
Ovsdb-bridge-attributes contains operational data of the bridge and it has datapath-id as one of the element.
leaf datapath-id { description "Datapath-id of the bridge"; type datapath-id; }
You can use this datapath-id to determine the Openflow registration id "openflow:<datapath-id>".
Thanks Anil
On Thu, Jun 4, 2015 at 12:05 PM, Vishal Thapar <vishal.thapar@...> wrote: +1
I’d also like to know answer to this.
From:
ovsdb-dev-bounces@... [mailto:ovsdb-dev-bounces@...]
On Behalf Of Yang, Yi Y
Hello, guys
I need to get openflow node ID for an OVSDB bridge node, in my test environment, I can see node info in MDSAL network topology flow:1 anf ovsdb:1 when I add a new bridge by command “sudo ovs-vsctl add-br br1”, I also can see node info in MDSAL inventory, but I can’t see augmentation for node in inventory, I noticed ovsdb/plugin-mdsal-adapter/src/main/yang/ovsdb-node-inventory.yang augmented inventory node:
augment /inv:nodes/inv:node { ext:augment-identifier "ovsdb-managed-node"; // when "/inv:nodes/inv:node/flowcapable:manufacturer = '*'"; container ovsdb-bridge { uses ovsdb-bridge-attributes; } }
augment /inv:nodes/inv:node { ext:augment-identifier "ovsdb-capable-node"; uses ovsdb-node-attributes; }
Anybody knows why? In karaf, what feature should I install for this. Here are ovsdb features I have installed.
opendaylight-user@root>feature:list -i | grep ovsdb odl-ovsdb-southbound-api | 1.1.0-SNAPSHOT | x | odl-ovsdb-southbound-1.1.0-SNAPSHOT | OpenDaylight :: southbound :: api odl-ovsdb-southbound-impl | 1.1.0-SNAPSHOT | x | odl-ovsdb-southbound-1.1.0-SNAPSHOT | OpenDaylight :: southbound :: impl odl-ovsdb-southbound-impl-rest | 1.1.0-SNAPSHOT | x | odl-ovsdb-southbound-1.1.0-SNAPSHOT | OpenDaylight :: southbound :: impl :: REST odl-ovsdb-southbound-impl-ui | 1.1.0-SNAPSHOT | x | odl-ovsdb-southbound-1.1.0-SNAPSHOT | OpenDaylight :: southbound :: impl :: UI opendaylight-user@root>
-- Thanks Anil |
|
|
|
Re: How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?
Anil Vishnoi
Hi Yi/Vishal, Please refer to ./southbound/southbound-api/src/main/yang/ovsdb.yang file. Southbound plugin augment bridge operational data to topology tree augment "/topo:network-topology/topo:topology/topo:node" { description "Augmentation for bridge nodes managed by ovsdb"; ext:augment-identifier "ovsdb-bridge-augmentation"; uses ovsdb-bridge-attributes; } Ovsdb-bridge-attributes contains operational data of the bridge and it has datapath-id as one of the element. leaf datapath-id { description "Datapath-id of the bridge"; type datapath-id; } You can use this datapath-id to determine the Openflow registration id "openflow:<datapath-id>". Thanks Anil On Thu, Jun 4, 2015 at 12:05 PM, Vishal Thapar <vishal.thapar@...> wrote:
--
Thanks Anil |
|
|
|
Re: How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?
Vishal Thapar <vishal.thapar@...>
+1
I’d also like to know answer to this.
From: ovsdb-dev-bounces@...
[mailto:ovsdb-dev-bounces@...] On Behalf Of Yang, Yi Y
Sent: 04 June 2015 04:44 To: ovsdb-dev@... Subject: [ovsdb-dev] How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?
Hello, guys
I need to get openflow node ID for an OVSDB bridge node, in my test environment, I can see node info in MDSAL network topology flow:1 anf ovsdb:1 when I add a new bridge by command “sudo ovs-vsctl add-br br1”, I also can see node info in MDSAL inventory, but I can’t see augmentation for node in inventory, I noticed ovsdb/plugin-mdsal-adapter/src/main/yang/ovsdb-node-inventory.yang augmented inventory node:
augment /inv:nodes/inv:node { ext:augment-identifier "ovsdb-managed-node"; // when "/inv:nodes/inv:node/flowcapable:manufacturer = '*'"; container ovsdb-bridge { uses ovsdb-bridge-attributes; } }
augment /inv:nodes/inv:node { ext:augment-identifier "ovsdb-capable-node"; uses ovsdb-node-attributes; }
Anybody knows why? In karaf, what feature should I install for this. Here are ovsdb features I have installed.
opendaylight-user@root>feature:list -i | grep ovsdb odl-ovsdb-southbound-api | 1.1.0-SNAPSHOT | x | odl-ovsdb-southbound-1.1.0-SNAPSHOT | OpenDaylight :: southbound :: api odl-ovsdb-southbound-impl | 1.1.0-SNAPSHOT | x | odl-ovsdb-southbound-1.1.0-SNAPSHOT | OpenDaylight :: southbound :: impl odl-ovsdb-southbound-impl-rest | 1.1.0-SNAPSHOT | x | odl-ovsdb-southbound-1.1.0-SNAPSHOT | OpenDaylight :: southbound :: impl :: REST odl-ovsdb-southbound-impl-ui | 1.1.0-SNAPSHOT | x | odl-ovsdb-southbound-1.1.0-SNAPSHOT | OpenDaylight :: southbound :: impl :: UI opendaylight-user@root> |
|
|
|
How do I map OVSDB bridge node to openflow node for getting an OVSDB bridge's openflow node ID?
Yang, Yi Y <yi.y.yang@...>
Hello, guys
I need to get openflow node ID for an OVSDB bridge node, in my test environment, I can see node info in MDSAL network topology flow:1 anf ovsdb:1 when I add a new bridge by command “sudo ovs-vsctl add-br br1”, I also can see node info in MDSAL inventory, but I can’t see augmentation for node in inventory, I noticed ovsdb/plugin-mdsal-adapter/src/main/yang/ovsdb-node-inventory.yang augmented inventory node:
augment /inv:nodes/inv:node { ext:augment-identifier "ovsdb-managed-node"; // when "/inv:nodes/inv:node/flowcapable:manufacturer = '*'"; container ovsdb-bridge { uses ovsdb-bridge-attributes; } }
augment /inv:nodes/inv:node { ext:augment-identifier "ovsdb-capable-node"; uses ovsdb-node-attributes; }
Anybody knows why? In karaf, what feature should I install for this. Here are ovsdb features I have installed.
opendaylight-user@root>feature:list -i | grep ovsdb odl-ovsdb-southbound-api | 1.1.0-SNAPSHOT | x | odl-ovsdb-southbound-1.1.0-SNAPSHOT | OpenDaylight :: southbound :: api odl-ovsdb-southbound-impl | 1.1.0-SNAPSHOT | x | odl-ovsdb-southbound-1.1.0-SNAPSHOT | OpenDaylight :: southbound :: impl odl-ovsdb-southbound-impl-rest | 1.1.0-SNAPSHOT | x | odl-ovsdb-southbound-1.1.0-SNAPSHOT | OpenDaylight :: southbound :: impl :: REST odl-ovsdb-southbound-impl-ui | 1.1.0-SNAPSHOT | x | odl-ovsdb-southbound-1.1.0-SNAPSHOT | OpenDaylight :: southbound :: impl :: UI opendaylight-user@root> |
|
|
|
stable/lithium branch created
Flavio Fernandes <ffernand@...>
Hi folks,
Now that we have a lithium branch for ovsdb project, be mindful that: 1) if your changes are needed in lithium, make sure you submit 2 gerrits: for stable/lithium and for master; cherry-pick is a handy way of accomplishing that. 2) make sure to associate changes for lithium with a bug number, and try to be as descriptive as possible in the commit message that the fix is about. We need to increasingly restrict what goes into stable/lithium to err on the side of stability. Thanks, — flavio |
|
|
|
OVSDB M5 Status
Sam Hague
0, Any issue testing with Karaf 3.0.3 (Not tested/Tested No issue/list of issues)
- Using karaf-parent and karaf-empty for pax-exam integration tests causing the follow error. There were issues with karaf 3.0.3 not finding artifacts that are in the repo. 2015-05-15 09:24:13,557 | WARN | Event Dispatcher | AetherBasedResolver | 3 - org.ops4j.pax.logging.pax-logging-api - 1.8.1 | Error resolving artifactorg.opendaylight.ovsdb:features-ovsdb:xml:features:1.1.0-SNAPSHOT:Could not find artifact org.opendaylight.ovsdb:features-ovsdb:xml:features:1.1.0-SNAPSHOT in defaultlocal (file:/home/shague/git/ovsdb/openstack/net-virt-it/target/exam/ce0ef120-c073-4219-9867-8fb6038c9e53/system/) shaded.org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact org.opendaylight.ovsdb:features-ovsdb:xml:features:1.1.0-SNAPSHOT in defaultlocal (file:/home/shague/git/ovsdb/openstack/net-virt-it/target/exam/ce0ef120-c073-4219-9867-8fb6038c9e53/system/) ... 2015-05-15 09:24:13,570 | WARN | Event Dispatcher | FeaturesServiceImpl | 20 - org.apache.karaf.features.core - 3.0.3 | Unable to add features repository mvn:org.opendaylight.ovsdb/features-ovsdb/1.1.0-SNAPSHOT/xml/features at startup java.io.IOException: Error resolving artifact org.opendaylight.ovsdb:features-ovsdb:xml:features:1.1.0-SNAPSHOT: Could not find artifact org.opendaylight.ovsdb:features-ovsdb:xml:features:1.1.0-SNAPSHOT in defaultlocal (file:/home/shague/git/ovsdb/openstack/net-virt-it/target/exam/ce0ef120-c073-4219-9867-8fb6038c9e53/system/) 1, Code Freeze has been met (i.e. only bug fixes is allowed from now on) Yes/No No: Monday 6/1/15 OVSDB has adsal dependencies that were removed from controller. The stable/lithium branch has been pulled but master has issues as noted. 2, Stability branch (stable/lithium) is cut and local project versions bumped on master complete. Yes/No a) Please provide gerrit patch URL for version bump. pending on: https://lists.opendaylight.org/pipermail/release/2015-May/002315.html 3, String Freeze (all externally visible strings frozen to allow for translation & documentation) Yes/No Yes 4, Documentation complete. (Only editing and enhancing should take place after this point) Yes/No a) Please provide github location URL for documentations, if your document status in [0] is not merged or under review https://git.opendaylight.org/gerrit/#/c/18486/ https://git.opendaylight.org/gerrit/#/c/20328/ 5, Integration & System test a) Each user-facing feature system test complete Yes/No yes b) Test run on code merge, upstream project code merge, release weekly Yes/No (Please provide a merge job link) https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-daily-master/ https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-daily-full-integration/ https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-integration-master/ https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-openstack-gerrit/ |
|
|
|
OVSDB M5 status missing
George Zhao <George.Y.Zhao@...>
Hi Sam and Flavio
Could you give an update for M5 status, at least what is blocking OVSDB for giving M5 status.
Thanks, George |
|
|
|
Re: [yangtools-dev] [controller-dev] JVM shutting down after installing openflowplugin feature
Moiz Raja (moraja) <moraja@...>
Here is the bug -> https://bugs.opendaylight.org/show_bug.cgi?id=3401
From: Robert Varga <nite@...>
Date: Wednesday, May 27, 2015 at 5:21 PM To: Edward Warnicke <hagbard@...>, Moiz Raja <moraja@...> Cc: "openflowplugin-dev@..." <dev@...>, controller-dev <controller-dev@...>, "ovsdb-dev@..." <ovsdb-dev@...>, "Luhrsen, Jamo" <james.luhrsen@...>, "yangtools-dev@..." <yangtools-dev@...> Subject: Re: [yangtools-dev] [controller-dev] JVM shutting down after installing openflowplugin feature THANK YOU.
For the record, Import-Package is only ever needed if you consume a package which happens to have an '.impl' component in its name. As per OSGi, that implies implementation-level dependency and is discouraged. The fix is to use some creativity in naming your packages :) Bye, Robert P.S.: Yes, maven-bundle-plugin has had some issues, but are running a very recent version, so no, you should not use Import-Package unless absolutely necessary. On 05/28/2015 02:14 AM, Edward Warnicke wrote:
|
|
|
|
Re: [yangtools-dev] [controller-dev] JVM shutting down after installing openflowplugin feature
Robert Varga <nite@...>
THANK YOU.
For the record, Import-Package is only ever needed if you consume a package which happens to have an '.impl' component in its name. As per OSGi, that implies implementation-level dependency and is discouraged. The fix is to use some creativity in naming your packages :) Bye, Robert P.S.: Yes, maven-bundle-plugin has had some issues, but are running a very recent version, so no, you should not use Import-Package unless absolutely necessary. On 05/28/2015 02:14 AM, Edward Warnicke wrote:
|
|
|
|
Re: [controller-dev] [yangtools-dev] JVM shutting down after installing openflowplugin feature
Edward Warnicke <hagbard@...>
YES :) Ed On Wed, May 27, 2015 at 5:14 PM, Moiz Raja (moraja) <moraja@...> wrote:
|
|
|
|
Re: [controller-dev] [yangtools-dev] JVM shutting down after installing openflowplugin feature
Moiz Raja (moraja) <moraja@...>
We should. Another tracking bug?
From: Edward Warnicke <hagbard@...>
Date: Wednesday, May 27, 2015 at 5:12 PM To: Moiz Raja <moraja@...> Cc: "Luhrsen, Jamo" <james.luhrsen@...>, "openflowplugin-dev@..." <dev@...>, controller-dev <controller-dev@...>, "yangtools-dev@..." <yangtools-dev@...>, "ovsdb-dev@..." <ovsdb-dev@...> Subject: Re: [controller-dev] [yangtools-dev] JVM shutting down after installing openflowplugin feature Can we add Import-Package to the cleanse-with-fire list?
Ed
On Wed, May 27, 2015 at 5:10 PM, Moiz Raja (moraja)
<moraja@...> wrote:
|
|
|
|
Re: [controller-dev] [yangtools-dev] JVM shutting down after installing openflowplugin feature
Edward Warnicke <hagbard@...>
Can we add Import-Package to the cleanse-with-fire list? Ed On Wed, May 27, 2015 at 5:10 PM, Moiz Raja (moraja) <moraja@...> wrote:
|
|
|
|
Re: [controller-dev] [yangtools-dev] JVM shutting down after installing openflowplugin feature
Moiz Raja (moraja) <moraja@...>
21276 should fix it. I was slow with pushing a similar patch of my own :)
From: Edward Warnicke <hagbard@...>
Date: Wednesday, May 27, 2015 at 5:09 PM To: Moiz Raja <moraja@...> Cc: "Luhrsen, Jamo" <james.luhrsen@...>, "openflowplugin-dev@..." <dev@...>, controller-dev <controller-dev@...>, "yangtools-dev@..." <yangtools-dev@...>, "ovsdb-dev@..." <ovsdb-dev@...> Subject: Re: [controller-dev] [yangtools-dev] JVM shutting down after installing openflowplugin feature I think that either this patch:
or this patch (preferred):
On Wed, May 27, 2015 at 4:55 PM, Moiz Raja (moraja)
<moraja@...> wrote:
|
|
|
|
Re: [controller-dev] [yangtools-dev] JVM shutting down after installing openflowplugin feature
Edward Warnicke <hagbard@...>
I think that either this patch: or this patch (preferred): On Wed, May 27, 2015 at 4:55 PM, Moiz Raja (moraja) <moraja@...> wrote:
|
|
|
|
Re: Flow Delete notification provides rootPath, but no rootNode
Tony Tkacik -X (ttkacik - PANTHEON TECHNOLOGIES@Cisco) <ttkacik@...>
Lithium implementation API should provide getDataBefore(), so it seems to me as some change in clustering or bug in data stores / event translation.
Could you provide more logs from that run to beter analyze the issue.
Tony
From: Anil Vishnoi [mailto:vishnoianil@...]
Sent: Monday, May 25, 2015 2:18 PM To: Tony Tkacik -X (ttkacik - PANTHEON TECHNOLOGIES at Cisco) Cc: controller-dev@...; ovsdb-dev@...; Sam Hague Subject: Flow Delete notification provides rootPath, but no rootNode
Hi Tony,
I am seeing following exception when ovsdb project delete openflow rules through openflowplugin.
Looks like notification provides the RootPath, but RootNode is null. Just want to understand In what scenario this can be possible?
And looking at the API description of getDataBefore(), it looks like it's not necessary to implement this API for any implementation. I assume then forwarding rule manager should not do a hard check on it, it should avoid any action if RootNode is null, because that's possible scenario?
-- Thanks Anil |
|
|
|
Flow Delete notification provides rootPath, but no rootNode
Anil Vishnoi
Hi Tony, I am seeing following exception when ovsdb project delete openflow rules through openflowplugin. Looks like notification provides the RootPath, but RootNode is null. Just want to understand In what scenario this can be possible? And looking at the API description of getDataBefore(), it looks like it's not necessary to implement this API for any implementation. I assume then forwarding rule manager should not do a hard check on it, it should avoid any action if RootNode is null, because that's possible scenario? Thanks Anil |
|
|
|
Re: DevStack public/physical bridge question
alagalah <alagalah@...>
toggle quoted message
Show quoted text
On 5/23/15, 7:33 AM, "alagalah" <alagalah@...> wrote:
/opt/stack/networking-odl/devstack/settings.odl:ODL_PROVIDER_MAPPINGS=${OD |
|
|
|
Re: DevStack public/physical bridge question
alagalah <alagalah@...>
/opt/stack/networking-odl/devstack/settings.odl:ODL_PROVIDER_MAPPINGS=${ODL
toggle quoted message
Show quoted text
_PROVIDER_MAPPINGS:-physnet1:eth1} Didn’t realize there were local.conf settings in devstack and devstack settings in the neutron driver itself. On 5/23/15, 7:22 AM, "alagalah" <alagalah@...> wrote:
Hi there, |
|
|