Attention integration-devs, Autorelease neon-mvn35-openjdk8 failed to build odl-integration-all from integration in build 25. Attached is a snippet of the error message related to the failure that we

Adding Venkat to thread for openstack_ha stuff. [16] is the line defining the openstack image name. That vm is built by a different job using packer. It takes a centos base, updates packages adds

Hi, Jamo and Sam I have always floating IP issue in my setup [1], you can see my topo details in [1], so I want to duplicate ODL csit test topo to find the difference, I find 1node topo in [2] and

Attention integration-devs, Autorelease fluorine-mvn35-openjdk8 failed to build odl-integration-compatible-with-all from integration in build 24. Attached is a snippet of the error message related to

Attention integration-devs, Autorelease neon-mvn35-openjdk8 failed to build odl-integration-all from integration in build 23. Attached is a snippet of the error message related to the failure that we

Hi, Not sure if this is the correct list, but the first lispflowmapping sodium validate autorelease job failed with a

I will start joining once the meeting is re-scheduled. With the current slot, I have conflicts. Thanks, Faseela

Sam and Jamo, openstack client in cperf container works after export those openstack environment variables, thank you two so much. 发件人: Sam Hague [mailto:shague@...] 发送时间:

Yes that's fine with me. Thanh

It looks like we have a winner: Thu 3:00 PM ADT / Thu 9:30AM IST / Thu 4:00 AM UTC / Wed 11:00 PM EST / Wed 8:00 PM PST We can discuss in tomorrow’s call when we will start using the new time. BTW

As Jamo mentioned, OpenStack CLI runs the native openstack cli and not running commands in a ssh connection to the openstack control node. The openstack cli has it's own messaging layer. There is

Hi Yi, the CSIT code is expected the openstack client to be available on the system running robot. That is the most efficient way we found to run the commands. Before (so there still may be

Hi, all I find all the Openstack cmds aren’t run in SSH session, I’m wondering why ODL csit suite can work normally. Per my test, Process.Run Process will never run in current SSH connection,

I think this is related to the transactions not commit in 5 seconds, hence masters are not created. This is interesting, as it starts happening for the same transaction on all shard members and these

Hi everybody, FYI I have just tried OFP cluster test with "tell-based"

Hi, Autorelease compilation (in master) is failing locally.. Is there way I can get last stable code? Steps Tried: git clone https://git.opendaylight.org/gerrit/p/odlparent.git git

Hi Luis, thanks for great explanation. Regarding webserver, we were playing with idea to use it to dispatch HTTP requests to our binaries (python) via CGI during tests. BR, Richard

Hi Richard, better send these kind of questions to the integration list (in cc) as I may not have all the answers. CSIT normally uses 3 VM types: controller (builder), test tools (mininet) and robot,

Hi all, Since now we have committers from East Coast, West Coast, India and Australia, I think we should revisit the time for the integration call. For that I created this doodle poll with the only

+1, this approach looks very neat.