cated somewhere in other parts of the
tree? I lean toward leaving just a one liner main() under
neutron/cmd/... that calls to 'real' main() located in a different
place in the tree.
Comments?
/Ihar
On 02/13/2015 04:37 PM, Ihar Hrachyshka wrote:
> On 02/13/2015 02:33 AM, Kevin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/16/2015 04:13 PM, James Page wrote:
> Hi Folks
>
> The split-out drivers for vpn/fw/lb as-a-service all make use of a
> generated egg of the neutron git repository as part of their unit
> test suite dependencies.
>
> This presents a bit of a c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/13/2015 11:13 PM, Paul Michali wrote:
> I see that in tox.ini, several commands have lockutils-wrapper
> prefix on them in the neutron-vpnaas repo. Seems like this was
> added as part of commit 88e2d801 for Migration to
> oslo.concurrency.
Those
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for the write-up! See inline.
On 02/13/2015 04:34 PM, Robert Li (baoli) wrote:
> Hi,
>
> while trying to integrate dibbler client with neutron to support
> PD, we countered a few issues with the dibbler client (and server).
> With a neutron ro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/13/2015 02:33 AM, Kevin Benton wrote:
> Why did the services fail with the stdlib patched? Are they
> incompatible with eventlet?
It's not like *service entry points* are not ready for neutron.* to be
monkey patched, but tools around it (flake8
espace problem, what kinds of statistics get broken by
>> moving ports into namespaces now?, the short-term fix could be
>> using vets, but “namespaceable” OVS ports would be perfect, yet I
>> understand the change is a big feature.
>>
>> If we had 1 & 3, may be 4 wo
till need namespaces for e.g. DHCP namespaces,
or in any other cases where we need to run a service that is not capable
of binding to a specific interface.
>
> [1] https://github.com/justinpettit/ovs/tree/conntrack
>
> Miguel Ángel Ajo
>
> On Friday, 13 de February de 2015
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi neutroners,
we** had several conversations recently with our Red Hat fellows who
work on openvswitch (Jiri Benc and Jiri Pirko) regarding the way
neutron utilizes their software. Those were beneficial to both sides
to understand what we do right an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
there were some moves recently to make monkey patching strategy sane
in neutron.
This was triggered by some bugs found when interacting with external
oslo libraries [1], and a cross project spec to make eventlet usage
sane throughout the proj
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/11/2015 12:09 AM, Sean Dague wrote:
> On 02/10/2015 05:47 PM, Ihar Hrachyshka wrote:
>> So cool! A comment inline.
>>
>> On 02/10/2015 11:26 PM, James E. Blair wrote:
>>> Hi,
>>
>>> We have added
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So cool! A comment inline.
On 02/10/2015 11:26 PM, James E. Blair wrote:
> Hi,
>
> We have added support for cross-repo dependencies (CRD) in Zuul.
> The important bits:
>
> * To use them, include "Depends-On: " in the
> footer of your commit messag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
my name was called out here, so I think I need to present my thoughts
on the matter. :) And sorry for writing too many words below.
===
As a disclaimer, I was not the one to support long support term for
stable branches. On the previous summit,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/07/2015 05:09 AM, masoom alam wrote:
> Hi every one,
>
> Can any one spot why the following bug will appear in Openstack
> leaving all services of Neutron to unusable state?
>
> To give you an idea that I was trying:
>
> "I tried to config
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/06/2015 06:47 PM, Eren Türkay wrote:
> Hello,
>
> I was having serious network issues using GRE and I have been
> tracking it for a few weeks. Finally, I solved the issue but it
> needs a proper fix. To summarize, I need a way to set MTU setting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/05/2015 09:14 AM, Andreas Scheuring wrote:
> Hi,
>
> is there a central place where I can find a matrix (or something
> similar) that shows what is currently supposed to work in the sense
> of IPv6 Networking?
>
> I also had a look at a couple
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'd like to ask grant for exception for the following patches:
- - https://review.openstack.org/#/c/149818/ (FIPs are messed up and/or
not working after L3 HA failover; makes L3 HA feature unusable)
- - https://review.openstack.org/152841 (i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/04/2015 12:03 PM, Alan Pevec wrote:
>>> Dependencies in requirements.txt do not seem to be used in
>>> stable/icehouse gate jobs, recent pip freeze in
>>> stable/icehouse shows: ... oslo.config==1.6.0 # git sha
>>> 99e530e django-openstack-auth=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/04/2015 11:20 AM, Alan Pevec wrote:
>> Bumping minimal oslo.config version due to the issue in
>> django-openstack-auth seems like a wrong way to do it.
>
> Dependencies in requirements.txt do not seem to be used in
> stable/icehouse gate jobs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/12/2014 07:43 AM, YAMAMOTO Takashi wrote:
> hi,
>
> good to hear. do you have any estimate when it will be available?
> will it cover dom0 side of the code found in
> neutron/plugins/openvswitch/agent/xenapi?
We also have rootwrap script just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/29/2015 08:18 PM, Ryan Hsu wrote:
> Hi All,
>
> There was a change [1] 2 days ago in django-openstack-auth that
> introduces a new requirement oslo.config>=1.6.0 to the project,
> which is now present in the 1.1.9 release of django-openstack-aut
On 01/29/2015 05:57 PM, Roman Podoliaka wrote:
Jeremy,
I don't have exact numbers, so yeah, it's just an assumption based on
looking at the nova-api/scheduler logs with connection_debug set to
100.
But that's a good point you are making here: it will be interesting to
see what difference enabli
On 01/29/2015 01:00 AM, Doug Hellmann wrote:
You will all, I am sure, be relieved to know that the oslo.vmware release today
was the last library that needed to be released with namespace package changes.
There are a few more patches to land to the requirements list to update the
minimum requi
On 01/28/2015 09:50 AM, Kevin Benton wrote:
Hi,
Approximately a year and a half ago, the default DHCP lease time in
Neutron was increased from 120 seconds to 86400 seconds.[1] This was
done with the goal of reducing DHCP traffic with very little
discussion (based on what I can see in the revi
The issue is still there, and I haven't heard anything from infra.
Updates, anyone?
/Ihar
On 01/21/2015 11:56 AM, Ihar Hrachyshka wrote:
Hi all,
Any updates from infra on why it occurs? It's still one of the issues
that make periodic stable jobs fail.
We also have other failu
Proposed the version skip in master:
https://review.openstack.org/#/c/149996/
On 01/26/2015 11:49 AM, Ihar Hrachyshka wrote:
On 01/26/2015 11:00 AM, Julie Pichon wrote:
On 26/01/15 06:34, A mailing list for the OpenStack Stable Branch test
reports. wrote:
Build failed.
- periodic-horizon
On 01/26/2015 11:00 AM, Julie Pichon wrote:
On 26/01/15 06:34, A mailing list for the OpenStack Stable Branch test
reports. wrote:
Build failed.
- periodic-horizon-docs-icehouse
http://logs.openstack.org/periodic-stableperiodic-horizon-docs-icehouse/9382030/
: SUCCESS in 4m 14s
- periodic-hor
Hi Andreas,
On 01/26/2015 10:58 AM, Andreas Scheuring wrote:
Hi Ihar,
we're currently running stable/juno devstack on rhel7 base. But I see
troubles to get it running on the master branch due to bug 1408297.
The fix for this bug increases the minimal dnsmasq version for master
branch up to 2.6
On 01/23/2015 05:38 PM, Mike Bayer wrote:
Doug Hellmann wrote:
We put the new base class for RequestContext in its own library because
both the logging and messaging code wanted to influence it's API. Would
it make sense to do this database setup there, too?
whoa, where’s that? is this an os
thing I would like to add is that the deadline for stable/juno is only
one week away - hence, it raises the urgency to call for action.
Thanks
-Sukhdev
On Jan 21, 2015 1:43 PM, "Ihar Hrachyshka" <mailto:ihrac...@redhat.com>> wrote:
>
> Hi all,
>
> as per:
https
Hi all,
as per:
https://github.com/openstack/neutron-specs/blob/master/specs/kilo/core-vendor-decomposition.rst,
neutron is going to spin off vendor plugins into separate trees outside
of neutron core team control. This raises several questions on how we
are going to handle stable branches th
On 01/20/2015 05:40 PM, Paul Michali wrote:
Review https://review.openstack.org/#/c/146508/ is adding support for
StrongSwan VPN, which needs mount bind to be able to specify different
paths for config files.
The code, which used some older patch, does a test for /proc/1/ns/net,
instead of /p
Unit tests should run successfully in a very limited environment, with
no sudo, namespaces etc. Some packagers even run unit tests as part of
their build process in hardened environment (I know Debian does, and
some teams from Red Hat consider it too, like Neutron).
So if it really needs to in
Hi all,
Any updates from infra on why it occurs? It's still one of the issues
that make periodic stable jobs fail.
We also have other failures due to missing packages on nodes. F.e.,
keystone python-ldap installation failing due to missing devel files for
openldap:
http://logs.openstack.org
Hi Kyle/all,
(we were going to walk thru that on Mon, but since US is on vacation
today, sending it via email to openstack-dev@.)
So I've talked to Doug Hellmann from oslo, and here is what we have in
our oslo queue to consider:
1. minor oslo.concurrency cleanup for *aas repos (we need to d
On 01/15/2015 01:42 PM, Sean Dague wrote:
The stable/havana branch of devstack was deleted when the stable/havana
branches of the projects were end of lifed.
That said, tag is still there:
http://git.openstack.org/cgit/openstack-dev/devstack/tag/?id=havana-eol
___
On 01/14/2015 01:44 PM, Daniel P. Berrange wrote:
On Wed, Jan 14, 2015 at 07:39:59AM -0500, Sean Dague wrote:
On 01/14/2015 04:08 AM, Dr. Jens Rosenboom wrote:
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
On 01/09/2015 01:02 PM, Ihar Hrachyshka wrote:
I think we should have some common document (etherpad?) with branch
status and links.
OK, I moved forward and created an Etherpad. I also filed it in with
current state. Please fill it in with updates.
https://etherpad.openstack.org/p/stable
On 01/14/2015 11:15 AM, Jakub Libosvar wrote:
On 01/14/2015 10:58 AM, yatin kumbhare wrote:
Many of them on gerrit page.
Mine is also one of them.
https://review.openstack.org/#/c/145290/
Regards,
Yatin
The cause is that nova-compute cannot start on stable/juno branch:
http://logs.openstack.o
You can get Python 2.7 via SCL:
https://www.softwarecollections.org/en/scls/rhscl/python27/
On 01/12/2015 05:32 PM, Igor Kalnitsky wrote:
Hi, Roman,
Indeed, we have to go forward and drop python 2.6 support. That's how
it supposed to be, but, unfortunately, it may not be as easy as it
seems at
g the appropriate
namespace so that we don't have the wrong usage sneak in.
I haven't gotten any rules written yet. Have had to attend to a family
commitment the last few days. Hope that I can tackle the namspace changes
next week.
Jay
On 01/08/2015 12:24 PM, Ihar Hrachyshka wrote:
On 01/0
On 01/09/2015 02:33 PM, Andreas Jaeger wrote:
On 01/09/2015 02:25 PM, Ihar Hrachyshka wrote:
Hi all,
I assumed that we still support py26 for clients, but then I saw [1]
that removed corresponding tox environment from ironic client.
What's our take on that? Shouldn't clients sti
Hi all,
I assumed that we still support py26 for clients, but then I saw [1]
that removed corresponding tox environment from ironic client.
What's our take on that? Shouldn't clients still support Python 2.6?
[1]:
https://github.com/openstack/ironic-python-agent/commit/d95a99d5d1a62ef5c085ce
On 01/09/2015 11:44 AM, Thierry Carrez wrote:
Hi stable-maint people,
We seem to still have a number of issues with stable branch in the gate,
both in Icehouse and Juno. I'd like to help where I can but I have a bit
of a hard time tracking down the remaining failures and things that have
already
On 01/08/2015 07:03 PM, Doug Hellmann wrote:
I’m not sure that’s something we need to enforce. Liaisons should be updating
projects now as we release libraries, and then we’ll consider whether we can
drop the namespace packages when we plan the next cycle.
Without a hacking rule, there is a c
to be safe. Shouldn't take a ton of effort.
Jay
On Jan 8, 2015 12:03 PM, "Doug Hellmann" <mailto:d...@doughellmann.com>> wrote:
> On Jan 8, 2015, at 11:29 AM, Ihar Hrachyshka
mailto:ihrac...@redhat.com>> wrote:
>
> On 01/05/2015 04:51 PM, Doug H
On 01/05/2015 04:51 PM, Doug Hellmann wrote:
As each library is released, we will send release notes to this list, as usual. At that point
the Oslo liaisons should start planning patches to change imports in their projects from
"oslo.foo" to “oslo_foo". The old imports should still work for now
On 01/07/2015 03:21 PM, Ihar Hrachyshka wrote:
Hi all,
I've found out that dnsmasq < 2.67 does not work properly for IPv6
clients when it comes to MAC address matching (it fails to match, and
so clients get 'no addresses available' response). I've requested
version
hursday, 8 de January de 2015 at 12:36, Ihar Hrachyshka wrote:
The problem is probably due to the fact that some operators may run
neutron from git and manage their dependencies in some other way;
or distributions may suck sometimes, so packagers may miss the
release note and fail to upgrade d
o the operators?
On Wed, Jan 7, 2015 at 6:57 AM, Kyle Mestery <mailto:mest...@mestery.com>> wrote:
On Wed, Jan 7, 2015 at 8:21 AM, Ihar Hrachyshka
mailto:ihrac...@redhat.com>> wrote:
Hi all,
I've found out that dnsmasq < 2.67 does not work pro
Hi all,
I've found out that dnsmasq < 2.67 does not work properly for IPv6
clients when it comes to MAC address matching (it fails to match, and so
clients get 'no addresses available' response). I've requested version
bump to 2.67 in: https://review.openstack.org/145482
Now, since we've alr
Hi,
FYI I've created draft release notes for 2014.2.2:
https://wiki.openstack.org/wiki/ReleaseNotes/2014.2.2
I assume that Trove will be released for 2014.2.2, so I've added it to
the list of projects.
Feel free to add more notes there.
/Ihar
___
On 01/06/2015 08:32 PM, Adam Gandelman wrote:
Hiya-
Flavio has been actively involved in stable branch maintenance for as
long as I can remember, but it looks like his +2 abilities were
removed after the organizational changes made to the stable
maintenance teams. He has expressed interest i
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 import is
still in the libvirt host module, but this isn't blowing up in the Jenkins
runs, so what's different? The
On 01/06/2015 12:04 PM, foss geek wrote:
Dear All,
Is it possible to configure neutron to take VM ip from external DHCP
server?
I am having All In One openstack env deployed using devstack icehouse.
I am looking for an option to integrate it with external DHCP server.
At the moment, there
On 01/06/2015 03:09 AM, Matt Riedemann wrote:
On 1/5/2015 2:16 PM, Doug Hellmann wrote:
On Jan 5, 2015, at 12:22 PM, Doug Hellmann
wrote:
On Jan 5, 2015, at 12:00 PM, Matt Riedemann
wrote:
There is a deprecation warning in pip 6.0.6 which is making the
py26 (on stable branches) an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 23/12/14 08:17, Thomas Goirand wrote:
> On 12/19/2014 11:55 PM, Ihar Hrachyshka wrote:
>> Note that OSLO_PACKAGE_VERSION is not public.
>
> Well, it used to be public, it has been added and discussed a few
> years ago becau
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/11/14 20:26, Thomas Goirand wrote:
> On 11/01/2014 11:29 PM, Kashyap Chamarthy wrote:
>> On Sat, Nov 01, 2014 at 09:13:21PM +0800, Thomas Goirand wrote:
>>> Hi,
>>>
>>> I was wondering if some distribution OpenStack package
>>> maintainers wou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I suspect that's some Red Hat distro, and radvd lacks SELinux context
set to allow neutron l3 agent to spawn it.
On 18/12/14 15:50, Jerry Zhao wrote:
> It seems that radvd was not spawned successfully in l3-agent log:
>
> Dec 18 11:23:34 ci-overclo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 16/12/14 13:41, Doug Hellmann wrote:
>
> On Dec 16, 2014, at 7:27 AM, Ihar Hrachyshka
> wrote:
>
>> Signed PGP part On 16/12/14 12:50, Doug Hellmann wrote:
>>>
>>> On Dec 16, 2014, at 5:13 AM, Ihar Hrachys
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 16/12/14 12:52, Doug Hellmann wrote:
>
> On Dec 16, 2014, at 5:22 AM, Ihar Hrachyshka
> wrote:
>
>> Signed PGP part On 15/12/14 17:22, Doug Wiegley wrote:
>>> Hi Ihar,
>>>
>>> I’m actually in f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 16/12/14 12:50, Doug Hellmann wrote:
>
> On Dec 16, 2014, at 5:13 AM, Ihar Hrachyshka
> wrote:
>
>> Signed PGP part On 15/12/14 18:57, Doug Hellmann wrote:
>>> There may be a similar problem managing dependencies
.
>
> Thanks, doug
>
>
> On 12/15/14, 6:15 AM, "Ihar Hrachyshka"
> wrote:
>
> Hi all,
>
> the question arose recently in one of reviews for neutron-*aas
> repos to remove all oslo-incubator code from those repos since
> it's duplicated
option 2, but it implies a few things
>>> about your time, and I wanted to chat with you before
>>> presuming.
>>>
>>> Maintenance can not involve breaking changes. At this point,
>>> the co-gate will block it. Also, oslo graduation changes will
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I was (rightfully) asked to share my comments on the matter that I
left in gerrit here. See below.
On 12/12/14 22:40, Sean Dague wrote:
> On 12/12/2014 01:05 PM, Maru Newby wrote:
>>
>> On Dec 11, 2014, at 2:27 PM, Sean Dague wrote:
>>
>>> On 12/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 14/12/14 09:45, Thomas Goirand wrote:
> Hi,
>
> As I am slowing fixing all systemd issues for the daemons of
> OpenStack in Debian (and hopefully, have this ready before the
> freeze of Jessie), I was wondering what kind of Type= directive to
> p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 15/12/14 15:15, Ihar Hrachyshka wrote:
> - it's a delusion that there will be no neutron-main syncs that
> will break neutron-*aas repos ever.
OK, I've just decided to check whether my (non-native speaker)
understanding of th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
the question arose recently in one of reviews for neutron-*aas repos
to remove all oslo-incubator code from those repos since it's
duplicated in neutron main repo. (You can find the link to the review
at the end of the email.)
Brief hostory
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Reading the latest comments at
https://github.com/PyMySQL/PyMySQL/issues/275, it seems to me that the
issue is not to be solved in drivers themselves but instead in
libraries that arrange connections (sqlalchemy/oslo.db), correct?
Will the proposed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/12/14 00:05, Mathieu Gagné wrote:
> We recently had an issue in production where a user had 2
> "default" security groups (for reasons we have yet to identify).
This is probably the result of the race condition that is discussed in
the thread:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/12/14 22:12, Jeremy Stanley wrote:
> On 2014-12-10 16:07:35 -0500 (-0500), Jay Pipes wrote:
>> On 12/10/2014 04:05 PM, Jeremy Stanley wrote:
>>> I think the bigger question is whether the lack of a quota
>>> implementation for everything a ten
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
+100. I vote -1 there and would like to point out that we *must* keep
history during the split, and split from u/s code base, not random
repositories. If you don't know how to achieve this, ask oslo people,
they did it plenty of times when graduating
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/12/14 21:58, Doug Hellmann wrote:
> As we’ve discussed a few times, we want to isolate applications
> from the configuration options defined by libraries. One way we
> have of doing that is the ConfigFilter class in oslo.config. When a
> regula
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/12/14 16:59, Vadivel Poonathan wrote:
> Hi Kyle and all,
>
> Was there any conclusion in the design summit or the meetings
> afterward about splitting the vendor plugins/drivers from the
> mainstream neutron and documentation of out-of-tree
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/12/14 14:22, Alan Pevec wrote:
> Hi all,
>
> here are exception proposal I have collected when preparing for
> the 2014.2.1 release, stable-maint members please have a look!
>
>
> General: cap Oslo and client library versions - sync from
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> On Thursday, 4 de December de 2014 at 15:06, Miguel Ángel Ajo
> wrote:
>
>>
>>
>> During Juno, we introduced the enhanced security groups rpc
>> (security_groups_info_for_devices) instead of
>> (security_group_rules_for_devices), and the ipset
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/12/14 14:22, Alan Pevec wrote:
> Hi all,
>
> here are exception proposal I have collected when preparing for
> the 2014.2.1 release, stable-maint members please have a look!
>
>
> General: cap Oslo and client library versions - sync from
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/12/14 21:19, Kyle Mestery wrote:
> On Mon, Dec 1, 2014 at 6:12 AM, Assaf Muller
> wrote:
>>
>>
>> - Original Message -
>>>
>>> My proposal here, is, _let’s not deprecate this setting_, as
>>> it’s a valid use case of a gateway confi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
It's weird: we run python33 job for gate but not checks. Adding Cyril
Roelandt who ported the library to py3 to CC.
On 01/12/14 23:40, Thomas Goirand wrote:
> On 12/01/2014 06:19 PM, Ihar Hrachyshka wrote:
>> Indeed, the revie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Are we going to have stable releases for those branches?
On 01/12/14 15:19, Doug Hellmann wrote:
> As part of setting up version caps for Oslo and client libraries in
> the stable branches, we discovered that the fact that we do not
> always create
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Indeed, the review queue is non-responsive. There are other patches in
the queue that bit rot there:
https://review.openstack.org/#/q/status:open+project:stackforge/sqlalchemy-migrate,n,z
I guess since no one with a +2 hammer systematically monitor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 28/11/14 01:26, Angus Lees wrote:
> Context: https://review.openstack.org/#/c/135616
>
> As far as I can make out, the fix for CVE-2014-7821 removed a backslash
> that effectively disables the negative look-ahead assertion that
> verifies that ho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 27/11/14 19:10, Thomas Goirand wrote:
> On 11/28/2014 12:06 AM, Ihar Hrachyshka wrote:
>> On 27/11/14 12:09, Thomas Goirand wrote:
>>> On 11/27/2014 12:31 AM, Donald Stufft wrote:
>>>>
>>>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 27/11/14 12:09, Thomas Goirand wrote:
> On 11/27/2014 12:31 AM, Donald Stufft wrote:
>>
>>> On Nov 26, 2014, at 10:34 AM, Thomas Goirand
>>> wrote:
>>>
>>> Hi,
>>>
>>> I tried to package suds-jurko. I was first happy to see that
>>> there was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
+2
On 27/11/14 10:15, Alan Pevec wrote:
> +1
>
> ___ OpenStack-dev
> mailing list OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-BEGIN PGP S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
we've introduced a regression when backporting the following patch [1]
which shows up as metadata proxy process not spawned for networks with
a ipv6 subnet. There was no official Juno release that would include
the patch though, yet. The iss
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 21/10/14 11:52, Steven Hardy wrote:
> On Mon, Oct 20, 2014 at 03:27:19PM -0700, Joe Gordon wrote:
>> On Mon, Oct 20, 2014 at 11:12 AM, gordon chung
>> wrote:
>>
>>> The issue I'm highlighting is that those projects using the
>>> code now
>> have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 16/11/14 20:17, Jay S. Bryant wrote:
> All,
>
> This is a question I have been struggling with for Cinder recently.
> Where do we draw the line on backports. How do we handle config changes?
>
> One thing for Cinder I am also considering, in ad
tor periodic jobs failures and enlist
> the help of others in order to fix the branches in case of
> breakage. They should also raise flags if for some reason they are
> blocked and don't receive enough support, in which case early
> abandon of the branch will be considered. Adam Gan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 14/11/14 09:14, Flavio Percoco wrote:
> On 13/11/14 23:25 +, Amrith Kumar wrote:
>> At the suggestion of Doug Hellmann, and relative to a
>> conversation with him and Flavio at Summit. Doug suggested that I
>> pose this question on the dev mai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 14/11/14 02:36, Fei Long Wang wrote:
> Greetings,
>
> Recently, I'm working on fixing Nova evacuate bugs for RBD. And
> both the two patches have been merged in Kilo[1,2]. But during
> backporting them to Juno/Icehouse, one patch got a document b
and submitted a fix for this problem since it
> was introduced by my previous patch.
>
> https://bugs.launchpad.net/neutron/+bug/1392564
> https://review.openstack.org/#/c/134432/
>
> It will be great if you can have a look at the fix and comment.
> Thanks!
>
> Xu Han
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Robert, Miguel,
do you plan to take care of the bug and the fix, or you need help? RDO
depends on the fix, also we should introduce the fix before the next
Juno release that includes the bad patch, so I would be glad to step
in if you don't have spar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 13/11/14 18:17, stuart.mcla...@hp.com wrote:
> All,
>
> The 0.1.9 version of glance_store, and glance's master branch both
> contain some fixes for the Swift multi-tenant store.
>
> This security related change hasn't merged to glance_store yet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/11/14 15:17, Sean Dague wrote:
>
> 1) just delete the trove exercise so we can move forward -
> https://review.openstack.org/#/c/133930 - that will need to be
> backported as well.
The patch is merged. Do we still need to backport it baring
the 2nd fix, let's wait for the 1st one to merge and repeat
benchmarking.
Cheers,
/Ihar
On 11/11/14 20:39, Ihar Hrachyshka wrote:
> Forwarding to openstack-dev since openstack-stable-maint is now
> read-only.
>
> Forwarded Message Subject: Re:
> [Op
From: Kevin Benton
To: openstack-stable-ma...@lists.openstack.org
CC: Ihar Hrachyshka
Hi,
There are two main patches that I am interested in back-porting to
improve the performance of the DB queries issued frequently by L2 agents
while they are hosting VMs. These are not one-time
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> -- Forwarded message -- From: Dave Walker
> To: openstack-stable-maint
> Date: Mon, 10 Nov 2014
> 21:52:23 + Subject: New config options, no default change
>
> Hi,
>
> Looking at a stable/juno cinder proposed change[0], I ca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/11/14 10:41, Alan Pevec wrote:
> 2014-11-11 7:26 GMT+01:00 :
>> - periodic-glance-python26-juno
>> http://logs.openstack.org/periodic-stable/periodic-glance-python26-juno/d0ea683
>> : FAILURE in 21m 09s - periodic-glance-python27-juno
>> http:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The failure is due to glance_store 0.1.9 released yesterday. It's not
specific to Juno. I've created a bug:
https://bugs.launchpad.net/glance/+bug/1391437 and marked it as Critical.
On 11/11/14 07:26, jenk...@openstack.org wrote:
> Build failed.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
FYI we'll need the following review for oslo-incubator to merge before
projects are able to consume the new library:
https://review.openstack.org/#/c/122796/3
On 24/10/14 19:12, Doug Hellmann wrote:
> The Oslo team is pleased to announce the releas
701 - 800 of 932 matches
Mail list logo
