Am 01/04/15 um 04:10 schrieb Kevin Benton:
It's worth pointing out here that the in-tree OVS solution controls traffic
using iptables on regular bridges too. The difference between the two
occurs when it comes to how traffic is separated into different networks.
It's also worth noting that DVR
Am 24/03/15 um 22:22 schrieb Joe Gordon:
On Tue, Mar 24, 2015 at 1:13 PM, Doug Hellmann d...@doughellmann.com
wrote:
We have a cross-project spec up for review discussing a change in the
release process precipitated by the fact that we are now capping library
versions in stable branch test
Am 05/03/15 um 17:52 schrieb Doug Hellmann:
On Thu, Mar 5, 2015, at 11:37 AM, Ian Cordasco wrote:
The clients in general do not back port patches. Someone should work with
stable-maint to raise the cap in Icehouse and Juno. I suspect, however,
that those caps were added due to the client
?
On 3/5/15, 10:28, Dr. Jens Rosenboom j.rosenb...@x-ion.de wrote:
Am 05/03/15 um 06:02 schrieb Nikhil Komawar:
The python-glanceclient release management team is pleased to announce:
python-glanceclient version 0.16.1 has been released on Thursday,
Mar 5th around 04:56 UTC.
The release
Am 14/01/15 um 05:17 schrieb Adam Gandelman:
So eventlet 0.16.x has started hitting slaves and breaking stable branches
(its not like we weren't warned :\ )
https://bugs.launchpad.net/nova/+bug/1410626
Should hopefully be resolved by eventlet versions caps in icehouse + juno's
requirements:
Am 06/01/15 um 18:01 schrieb Daniel P. Berrange:
On Tue, Jan 06, 2015 at 05:36:38PM +0100, Ihar Hrachyshka wrote:
On 01/06/2015 05:33 PM, Daniel P. Berrange wrote:
On Tue, Jan 06, 2015 at 10:21:10AM -0600, Matt Riedemann wrote:
Odd...eventlet 0.16.0 was released on 12/30 and the eventlet.util
Am 06/01/15 um 04:40 schrieb Rajdeep Dua:
Getting this error while running stack.sh in devstack
Could not find a version that satisfies the requirement
SQLAlchemy=0.8.99,=0.9.99,=0.8.4,=0.9.7 (from keystone==2014.2.dev114)
(from versions: 0.4.2p3, 0.4.7p1, 0.5.4p1, 0.5.4p2, 0.1.0, 0.1.1, 0.1.2,
As this may affect a reasonable percentage of the target audience, I
would like to make everyone aware of
https://github.com/blog/1938-vulnerability-announced-update-your-git-clients
While github.com claim to have patched their servers, people using other
repos may want to be extra cautious.
