|
Re: [release] Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb
I finally was able to look at it a bit, and things are gradually
improving. ETA Wednesday.
Bye,
Robert
I finally was able to look at it a bit, and things are gradually
improving. ETA Wednesday.
Bye,
Robert
|
By
Robert Varga <nite@...>
·
#4835
·
|
|
[release] Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb
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
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
|
By
Jenkins <jenkins-dontreply@...>
·
#4834
·
|
|
Re: Vote on Anil for OVSDB PTL
+1
By
Sam Hague
·
#4833
·
|
|
Re: Vote on Anil for OVSDB PTL
+1
Regards,
Stephen
By
Stephen Kitt <skitt@...>
·
#4832
·
|
|
Vote on Anil for OVSDB PTL
Hi OVSDB committers,
Please vote +1/-1 for Anil Vishnoi as OVSDB PTL.
Thanks and Regards,
Vishal Thapar.
Hi OVSDB committers,
Please vote +1/-1 for Anil Vishnoi as OVSDB PTL.
Thanks and Regards,
Vishal Thapar.
|
By
Vishal Thapar <vthapar@...>
·
#4831
·
|
|
[release] Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb
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
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
|
By
Jenkins <jenkins-dontreply@...>
·
#4830
·
|
|
[release] Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb
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
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
|
By
Jenkins <jenkins-dontreply@...>
·
#4829
·
|
|
Re: Purpose of HWvTEP implementation
Hi1rving,
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
Hi1rving,
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
|
By
suneelu
·
#4828
·
|
|
[release] Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb
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
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
|
By
Jenkins <jenkins-dontreply@...>
·
#4827
·
|
|
Re: 答复: [lists.opendaylight.org代发][netvirt-dev] Purpose of HWvTEP implementation
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
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
|
By
Yi Yang
·
#4826
·
|
|
[release] Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb
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
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
|
By
Jenkins <jenkins-dontreply@...>
·
#4824
·
|
|
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
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
|
By
"1rving <418624178@...>
·
#4825
·
|
|
[release] Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb
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
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
|
By
Jenkins <jenkins-dontreply@...>
·
#4823
·
|
|
Re: OVSDB node-id format
Yes.
No.
By
Vishal Thapar <vthapar@...>
·
#4822
·
|
|
Re: How to manage the switches which is not created by ODL?
This question has been answered in earlier posts in user mail thread.
Sorry, ignore this email.
This question has been answered in earlier posts in user mail thread.
Sorry, ignore this email.
|
By
suresh
·
#4821
·
|
|
How to manage the switches which is not created by ODL?
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
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
|
By
suresh
·
#4820
·
|
|
OVSDB node-id format
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
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
|
By
suresh
·
#4819
·
|
|
[release] Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb
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
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
|
By
Jenkins <jenkins-dontreply@...>
·
#4818
·
|
|
[release] Autorelease sodium-mvn35-openjdk11 failed to build southbound-impl from ovsdb
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
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
|
By
Jenkins <jenkins-dontreply@...>
·
#4817
·
|
|
Re: Require help for OVSDB configuration
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
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
|
By
Vishal Thapar <vthapar@...>
·
#4816
·
|