z.archive.ovsdb-dev@lists.opendaylight.org

Home Messages Hashtags Subgroups

This group is locked. No changes can be made to the group while it is locked.

Expanded

Between

and

Re: [release] Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb Robert Varga <nite@...> #4835 On 09/03/2019 03:24, Jenkins wrote: Attention ovsdb-devs, Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb in build 33. Attached is a snippet of the error message related to the failure that we were able to automatically parse as well as console logs. Console Logs: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-sodium-mvn35-openjdk11/33 I finally was able to look at it a bit, and things are gradually improving. ETA Wednesday. Bye, Robert signature.asc signature.asc
[release] Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb Jenkins <jenkins-dontreply@...> #4834 Attention ovsdb-devs, Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb in build 33. Attached is a snippet of the error message related to the failure that we were able to automatically parse as well as console logs. Console Logs: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-sodium-mvn35-openjdk11/33 Jenkins Build: https://jenkins.opendaylight.org/releng/job/autorelease-release-sodium-mvn35-openjdk11/33/ Please review and provide an ETA on when a fix will be available. Thanks, ODL releng/autorelease team error.log.gz error.log.gz
Re: Vote on Anil for OVSDB PTL Sam Hague #4833 +1 toggle quoted message Show quoted text On Fri, Mar 8, 2019, 3:13 AM Stephen Kitt <skitt@...> wrote: On Fri, Mar 08, 2019 at 12:19:54PM +0530, Vishal Thapar wrote: > Please vote +1/-1 for Anil Vishnoi as OVSDB PTL. +1 Regards, Stephen
Re: Vote on Anil for OVSDB PTL Stephen Kitt <skitt@...> #4832 On Fri, Mar 08, 2019 at 12:19:54PM +0530, Vishal Thapar wrote: Please vote +1/-1 for Anil Vishnoi as OVSDB PTL. +1 Regards, Stephen signature.asc signature.asc
Vote on Anil for OVSDB PTL Vishal Thapar <vthapar@...> #4831 Hi OVSDB committers, Please vote +1/-1 for Anil Vishnoi as OVSDB PTL. Thanks and Regards, Vishal Thapar.
[release] Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb Jenkins <jenkins-dontreply@...> #4830 Attention ovsdb-devs, Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb in build 32. Attached is a snippet of the error message related to the failure that we were able to automatically parse as well as console logs. Console Logs: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-sodium-mvn35-openjdk11/32 Jenkins Build: https://jenkins.opendaylight.org/releng/job/autorelease-release-sodium-mvn35-openjdk11/32/ Please review and provide an ETA on when a fix will be available. Thanks, ODL releng/autorelease team error.log.gz error.log.gz
[release] Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb Jenkins <jenkins-dontreply@...> #4829 Attention ovsdb-devs, Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb in build 31. Attached is a snippet of the error message related to the failure that we were able to automatically parse as well as console logs. Console Logs: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-sodium-mvn35-openjdk11/31 Jenkins Build: https://jenkins.opendaylight.org/releng/job/autorelease-release-sodium-mvn35-openjdk11/31/ Please review and provide an ETA on when a fix will be available. Thanks, ODL releng/autorelease team error.log.gz error.log.gz
Re: Purpose of HWvTEP implementation suneelu #4828 Hi 1rving, Point no 2 is partially true. It is to enable vm workloads to have l2 communication with physical servers / sriov workloads behind the TOR devices within the same datacenter environment. Thanks, Suneelu toggle quoted message Show quoted text From: ovsdb-dev-bounces@... [mailto:ovsdb-dev-bounces@...] On Behalf Of 1rving Sent: Sunday, March 03, 2019 10:04 PM To: ovsdb-dev <ovsdb-dev@...> Cc: netvirt-dev <netvirt-dev@...> Subject: [ovsdb-dev] Purpose of HWvTEP implementation Hi guys. I got an idea to add a HWvTEP device into a "NetVirt with OpenStack" scenario, but so far I cannot see the advantages from this action. So I start to consider the purpose of OVSDB HWvTEP scenario. The purpose is 1 or 2? 1. The efficiency of overlay encapsulation, maybe VXLAN. 2. "The idea behind hardware VTEPs is to create an overlay network that connects VMs and Physical Servers and make them think that they’re in the same L2 network even if they’re on opposite sides of the globe." Any ideas would be appreciated. BR, 1rving
[release] Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb Jenkins <jenkins-dontreply@...> #4827 Attention ovsdb-devs, Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb in build 29. Attached is a snippet of the error message related to the failure that we were able to automatically parse as well as console logs. Console Logs: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-sodium-mvn35-openjdk11/29 Jenkins Build: https://jenkins.opendaylight.org/releng/job/autorelease-release-sodium-mvn35-openjdk11/29/ Please review and provide an ETA on when a fix will be available. Thanks, ODL releng/autorelease team error.log.gz error.log.gz
Re: 答复: [lists.opendaylight.org代发][netvirt-dev] Purpose of HWvTEP implementation Yi Yang #4826 Hi, Irving Hardware VTEP just bridges VM VXLAN network to physical VLAN network in order that VM can communicate with physical servers each other, the result is they look like being in the same virtual network or same VLAN network. http://kimizhang.com/neutron-l2-gateway-hp-5930-switch-ovsdb-integration/ and https://docs.openstack.org/networking-l2gw/latest/readme.html are good guides to you, 发件人: netvirt-dev-bounces@... [mailto:netvirt-dev-bounces@...] 代表 1rving 发送时间: 2019年3月4日 0:34 收件人: ovsdb-dev <ovsdb-dev@...> 抄送: netvirt-dev <netvirt-dev@...> 主题: [lists.opendaylight.org代发][netvirt-dev] Purpose of HWvTEP implementation Hi guys. I got an idea to add a HWvTEP device into a "NetVirt with OpenStack" scenario, but so far I cannot see the advantages from this action. So I start to consider the purpose of OVSDB HWvTEP scenario. The purpose is 1 or 2? 1. The efficiency of overlay encapsulation, maybe VXLAN. 2. "The idea behind hardware VTEPs is to create an overlay network that connects VMs and Physical Servers and make them think that they’re in the same L2 network even if they’re on opposite sides of the globe." Any ideas would be appreciated. BR, 1rving smime.p7s smime.p7s
[release] Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb Jenkins <jenkins-dontreply@...> #4824 Attention ovsdb-devs, Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb in build 28. Attached is a snippet of the error message related to the failure that we were able to automatically parse as well as console logs. Console Logs: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-sodium-mvn35-openjdk11/28 Jenkins Build: https://jenkins.opendaylight.org/releng/job/autorelease-release-sodium-mvn35-openjdk11/28/ Please review and provide an ETA on when a fix will be available. Thanks, ODL releng/autorelease team error.log.gz error.log.gz
Purpose of HWvTEP implementation "1rving <418624178@...> #4825 Hi guys. I got an idea to add a HWvTEP device into a "NetVirt with OpenStack" scenario, but so far I cannot see the advantages from this action. So I start to consider the purpose of OVSDB HWvTEP scenario. The purpose is 1 or 2? 1. The efficiency of overlay encapsulation, maybe VXLAN. 2. "The idea behind hardware VTEPs is to create an overlay network that connects VMs and Physical Servers and make them think that they’re in the same L2 network even if they’re on opposite sides of the globe." Any ideas would be appreciated. BR, 1rving
[release] Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb Jenkins <jenkins-dontreply@...> #4823 Attention ovsdb-devs, Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb in build 23. Attached is a snippet of the error message related to the failure that we were able to automatically parse as well as console logs. Console Logs: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-sodium-mvn35-openjdk11/23 Jenkins Build: https://jenkins.opendaylight.org/releng/job/autorelease-release-sodium-mvn35-openjdk11/23/ Please review and provide an ETA on when a fix will be available. Thanks, ODL releng/autorelease team error.log.gz error.log.gz
Re: OVSDB node-id format Vishal Thapar <vthapar@...> #4822 On Tue, Feb 26, 2019 at 11:12 AM S Suresh <sureshkumarr.s@...> wrote: Hi, Regarding the below configuration API, http://localhost:8181/restconf/config/network-topology:network-topology/topology/ovsdb:1/node/ovsdb:%2F%2FHOST1 In this, ovsdb://HOST1 is a "node-id" What is the format for node-id?? is it mandatory to use in this format. I mean "ovsdb://" Yes. Or simply can i use "ovsdb:host1" No. Thanks suresh _______________________________________________ ovsdb-dev mailing list ovsdb-dev@... https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev
Re: How to manage the switches which is not created by ODL? suresh #4821 This question has been answered in earlier posts in user mail thread. Sorry, ignore this email. toggle quoted message Show quoted text On Tue, Feb 26, 2019 at 12:08 PM S Suresh <sureshkumarr.s@...> wrote: Hi, My sceanario is as below, I do have my existing bridges in OVSDB host (created by other tools(mininet or manually)) I have connected ODL to manage this OVSDB host. I could able to get the existing bridges in OPERATIONAL data store. But in config datastore its not listing. I am not able to configure it(lets say modify the SDN controller IP) or DELETE it. How to do it? Thanks suresh
How to manage the switches which is not created by ODL? suresh #4820 Hi, My sceanario is as below, I do have my existing bridges in OVSDB host (created by other tools(mininet or manually)) I have connected ODL to manage this OVSDB host. I could able to get the existing bridges in OPERATIONAL data store. But in config datastore its not listing. I am not able to configure it(lets say modify the SDN controller IP) or DELETE it. How to do it? Thanks suresh
OVSDB node-id format suresh #4819 Hi, Regarding the below configuration API, http://localhost:8181/restconf/config/network-topology:network-topology/topology/ovsdb:1/node/ovsdb:%2F%2FHOST1 In this, ovsdb://HOST1 is a "node-id" What is the format for node-id?? is it mandatory to use in this format. I mean "ovsdb://" Or simply can i use "ovsdb:host1" Thanks suresh
[release] Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb Jenkins <jenkins-dontreply@...> #4818 Attention ovsdb-devs, Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb in build 21. Attached is a snippet of the error message related to the failure that we were able to automatically parse as well as console logs. Console Logs: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-sodium-mvn35-openjdk11/21 Jenkins Build: https://jenkins.opendaylight.org/releng/job/autorelease-release-sodium-mvn35-openjdk11/21/ Please review and provide an ETA on when a fix will be available. Thanks, ODL releng/autorelease team error.log.gz error.log.gz
[release] Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb Jenkins <jenkins-dontreply@...> #4817 Attention ovsdb-devs, Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb in build 20. Attached is a snippet of the error message related to the failure that we were able to automatically parse as well as console logs. Console Logs: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-sodium-mvn35-openjdk11/20 Jenkins Build: https://jenkins.opendaylight.org/releng/job/autorelease-release-sodium-mvn35-openjdk11/20/ Please review and provide an ETA on when a fix will be available. Thanks, ODL releng/autorelease team error.log.gz error.log.gz
Re: Require help for OVSDB configuration Vishal Thapar <vthapar@...> #4816 Hi Suresh, The documentation is correct, you're not specifying the media type [application/json] correctly. Correct syntax would depend on the client you're using to make PUT call. Easy way is to use Postman using collections mentioned in https://docs.opendaylight.org/en/stable-fluorine/user-guide/ovsdb-user-guide.html#references If you're using curl, you need to use -H "Content-Type: application/json". Regards, Vishal. toggle quoted message Show quoted text On Mon, Feb 25, 2019 at 9:53 AM S Suresh <sureshkumarr.s@...> wrote: Hi, I am newbie, and trying to use ODL OVSDB feature. I follow this tutorial, https://docs.opendaylight.org/en/stable-fluorine/user-guide/ovsdb-user-guide.html and when i try to PUT API http://localhost:8181/restconf/config/network-topology:network-topology/topology/ovsdb:1/node/ovsdb: %2F%2FHOST1 Body: { "network-topology:node": [ { "node-id": "ovsdb://HOST1", "connection-info": { "ovsdb:remote-port": "6640", "ovsdb:remote-ip": "192.168.122.1" } } ] } I get HTTP ERROR CODE 415 unsupported media type error. In the ODL log, I see below exceptions. 2019-02-25T09:46:50,986 \| DEBUG \| qtp132936849-76 \| ContainerResponse \| 60 - com.sun.jersey.jersey-server - 1.19.4 \| Mapped exception to response: 415 (Unsupported Media Type) javax.ws.rs.WebApplicationException: null at com.sun.jersey.server.impl.uri.rules.TerminatingRule.accept(TerminatingRule.java:66) [60:com.sun.jersey.jersey-server:1.19.4] at com.sun.jersey.server.impl.uri.rules.ResourceObjectRule.accept(ResourceObjectRule.java:100) [60:com.sun.jersey.jersey-server:1.19.4] at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) [60:com Can you please help with correct documentation. Thanks suresh _______________________________________________ ovsdb-dev mailing list ovsdb-dev@... https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev

21 - 40 of 4855

Home Hashtags Subgroups Terms