-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 The bot was proposing when it was still master. After you branched out stable/kilo, you should have sticked to the deps that belong

[cc odl neutron-dev, Ankur, Isaku] indeed! It is ironic reading this… and then looking at the ‘owner' of the commit that caused all this mess [1]. That aside; I have very little experience on

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 So that's a problem. You don't even have a common pbr version that would satisfy both projects. The fix is obvious: make stable/kilo requirements in

They do not for requirements.txt: $ diff requirements.txt.neutron requirements.txt.networking-odl | grep pbr < pbr!=0.7,<1.0,>=0.6 > pbr<2.0,>=1.3 $ diff test-requirements.txt.neutron

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Are your repo [test-]requirements.txt synchronized with neutron's kilo requirements? They should, otherwise it won't be ever

That is the issue. This happens because OFFLINE=True and there is still something in pbr requirements that is looking for a version of pbr that is not used in stable/kilo. I suspect this is happening

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Looking at the logs in the email thread: 2015-08-05 14:59:53.160 | Download error on https://pypi.python.org/simple/pbr/: [Errno 110] Connection timed

Hi Kyle, I recall talking to you and “lifeless” about an issue with pbr versioning in stable/kilo for networking-odl. That seems to be an issue [1], still; making it impossible for folks to use

Hi Flavio, It was a pleasure to meet you in the Submit, I really enjoyed there. Sure, It looks very interesting and I will start with the demo. Best, Marcelo -- Marcelo Amaral, PhD Candidate BSC

[add cc: ovsdb-dev] np! I have never had much luck on ‘moving’ branches in devstack after doing a stack. Having said that, it is likely that you resolved the pbr issue by grabbing pbr from master

Filed https://bugs.opendaylight.org/show_bug.cgi?id=4132 Let me know if I'm missing some required info. Thanks, Tim Rozet Red Hat SDN Team

yes, Manipulate the values from xml files or through restconf. User can change these value at run time as well. We need to make sure that we keep this user param config subsystem module separate from

Anil, Ed, what does this look like to move it to ovsdb? Is it something like we move the properties into the config subsystem and the user manipulates the values from the xml files? Thanks, Sam

[cc: ovsdb-dev] Hi Marcelo, It was really nice meting at the Summit! Sorry for not having a lot of extra time to mingle. You mentioned you were looking for some work on ovsdb L3 and I thought of a

point noted, and we were planning to do it in this release :) Anil -- Thanks Anil

Hi Eric, As we talked in the meeting, here is the email I sent earlier on the ml [1] that refers to the script that pretends to have openstack around ODL. For more info on using it, take a look at the

Hi all, here are the topics for this week. Add to the list if there is anything you would like to dicsuss. 1. Task status updates: please update the Trello cards 2. Bug updates: please grab a bug if

I will take a look at this in the weekend. BR/Luis

Eric, yeah, that was the fix we had to make to networking-odl - remove the 1.3 requirement. We added that to the summit15demo branch so maybe that is why Flavio's setup didn't work for you. The patch