-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/10/14 09:08, Osanai, Hisashi wrote:
Hi,
I would like to know the minimum python support version for juno. I
checked the following memo. My understanding is python 2.6 support
will be supported in juno and also dropped before kilo so it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/10/14 12:55, Thomas Goirand wrote:
Hi,
When building the latest release (eg: Juno RC1) of Taskflow 0.4,
needed by Cinder, I've notice failures due to the impossibility to
do:
from kombu import message
More in details, the failure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
I guess the following review is meant:
https://review.openstack.org/#/c/125075/
I went thru each of the failure for the patch (no dependency failures
checked), and here are some damned lies (c) about those failures:
- - bug 1323658: 2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/10/14 18:04, Akihiro Motoki wrote:
Hi,
To display localized strings, we need to compile translated
message catalogs (PO files) into compiled one (MO files). I would
like to discuss and get a consensus who and when generate compiled
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Red Hat should be fine with the change. We're going to ship Juno for
Fedora 21+ and EL7 only (no EL6), and they both have the needed
versions packaged [1].
[1]: https://admin.fedoraproject.org/updates/python-django-nose
On 02/10/14 16:29,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/10/14 18:12, Akihiro Motoki wrote:
Thanks all for your input. This topic was also discussed in the
I18N team meeting this week.
All opinions I got so far are same and we seem to have a
consensus. - not to have mo files (compile message
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
tl;dr we should enforce utf8 on server and client sides of db
connection, and this requires changes to docs and oslo.db. The latter
may require raising effective libpq version dep to 9.1+.
Recently I was working on making sure we always
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/10/14 15:11, Jay Pipes wrote:
On 10/06/2014 08:30 AM, Ihar Hrachyshka wrote: Hi all,
tl;dr we should enforce utf8 on server and client sides of db
connection, and this requires changes to docs and oslo.db. The
latter may require raising
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/10/14 17:56, Doug Hellmann wrote:
The Oslo team is responsible for managing code shared between
projects. There are a LOT more projects than Oslo team members, so
we created the liaison program at the beginning of the Juno cycle,
asking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/10/14 19:10, Mike Bayer wrote:
On Oct 6, 2014, at 9:56 AM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
But we can do better. We should also enforce utf8 on client
side, so that there is no way to run with a different encoding
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/10/14 06:51, thanh le giang wrote:
Hi all
I want to add a plugin to the Public Neutron Repository. Although I
have read the gerrit workflow and Neutron Development page
(https://wiki.openstack.org/wiki/NeutronDevelopment), I don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/10/14 21:01, Roman Podoliaka wrote:
Hi all,
Last Friday we decided to find a better time for the weekly team
meeting. Keeping in mind that DST ends soon (October the 26th in
Europe, November the 2nd in the US), I think, we can choose
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/10/14 22:25, Dirk Müller wrote:
2014-10-02 14:19 GMT+02:00 Duncan Thomas
duncan.tho...@gmail.com:
Hi,
What is actually needed is those who rely on the stable
branch(es) existence need to step forward and dedicate resources
to it.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/10/14 09:30, Christian Berendt wrote:
After proposing a change to Horizon to remove the @author tags from
the header of Python files
(https://review.openstack.org/#/c/126656/) Matthias Runge proposed
to discuss this first on the mailing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/10/14 18:05, Mike Bayer wrote:
On Oct 7, 2014, at 8:29 AM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
That said, I wonder how we're going to manage cases when those
*global* settings for the whole server should be really limited
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/10/14 01:55, Vasudevan, Swaminathan (PNB Roseville) wrote:
Hi Folks,
./run_tests.sh fails to create the .venv with the latest neutron
repo.
It fails at MySQL-python.
Does anyone know what is broken.
You probably miss
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/10/14 10:32, Chen CH Ji wrote:
There used to method in oslo-incubator like
https://wiki.openstack.org/wiki/Oslo#Syncing_Code_from_Incubator
or '_https://review.openstack.org/#/c/78429/_ ' we can use
however, I was told to submit patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/10/14 23:44, Doug Hellmann wrote:
On Oct 9, 2014, at 4:30 PM, Matt Riedemann
mrie...@linux.vnet.ibm.com wrote:
The sqlalchemy-migrate project is basically maintenance mode and
the core team [1] is kind of a weird mix of people - all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/10/14 21:29, Mike Bayer wrote:
So so far, everyone seems really positive and psyched about the
proposal.
It looks like providing some options for how to use would be best,
that is provide decorators and context managers.
Now the thing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/10/14 20:21, Joshua Harlow wrote:
On Oct 10, 2014, at 3:13 AM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
On 09/10/14 21:29, Mike Bayer wrote:
So so far, everyone seems really positive and psyched about
the proposal.
It looks like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
introducing a new auxiliary feature (e.g. a new messaging backend;
some specific configuration of common services, like multiple workers
in neutron; a new db driver supported by oslo.db; a plugin that lacks
its own third-party CI like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 22/10/14 02:26, Maru Newby wrote:
We merged caching support for the metadata agent in juno, and
backported to icehouse. It was enabled by default in juno, but
disabled by default in icehouse to satisfy the stable maint
requirement of not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 24/10/14 11:56, Miguel Angel Ajo Pelayo wrote:
- Original Message -
Hi Miguel,
while we'd need to hear from the stable team, I think it's not
such a bad idea to make this tool available to users of pre-juno
openstack releases.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 22/10/14 12:07, Thierry Carrez wrote:
Ihar Hrachyshka wrote:
[...] For stable branches, we have so called periodic jobs that
are triggered once in a while against the current code in a
stable branch, and report to openstack-stable-maint
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 27/10/14 02:18, Li Tianqing wrote:
Hello, Right now, we test neutron under havana release. We
configured network_device_mtu=1450 in neutron.conf, After create
vm, we found the vm interface's mtu is 1500, the ping, ssh, is ok.
But if we scp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 25/10/14 00:16, James E. Blair wrote:
Andrea Frittoli andrea.fritt...@gmail.com writes:
I also believe we can find ways to make post-merge / periodic
checks useful. We need to do that to keep the gate to a sane
scale.
Yes, we have a plan
-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
-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
On 11/11/14 10:41, Alan Pevec wrote:
2014-11-11 7:26 GMT+01:00 jenk...@openstack.org:
- periodic-glance-python26-juno
http://logs.openstack.org/periodic-stable/periodic-glance-python26-juno/d0ea683
: FAILURE in 21m 09s -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
-- Forwarded message -- From: Dave Walker
em...@daviey.com To: openstack-stable-maint
openstack-stable-ma...@lists.openstack.org Date: Mon, 10 Nov 2014
21:52:23 + Subject: New config options, no default change
Hi,
From: Kevin Benton blak...@gmail.com
To: openstack-stable-ma...@lists.openstack.org
CC: Ihar Hrachyshka ihrac...@redhat.com
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
.
As for 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:
[Openstack-stable-maint] Neutron
-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 in
-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
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
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
On 11/14/2014 05:54 AM, Ihar Hrachyshka
-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 build
-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 mailing
case early
abandon of the branch will be considered. Adam Gandelman
volunteered to be the stable/juno champion. Ihar Hrachyshka (was)
volunteered to be the stable/icehouse champion.
5. To set expectations right and evolve the meaning of stable
over time to gradually mean more not changing, we
-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
-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
-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 z...@debian.org
wrote:
Hi,
I tried to package suds-jurko. I was first happy to see that
there was some
-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:
On Nov 26, 2014, at 10:34 AM, Thomas Goirand
z...@debian.org wrote
-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
-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
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 review queue is non-responsive
-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 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 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
regular
-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
-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 tenant
-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
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
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
-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 the meaning of the word
-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
put on
-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 s...@dague.net wrote:
not involve breaking changes. At this point,
the co-gate will block it. Also, oslo graduation changes will
have to be made in the services repos first, and then Neutron.
Thanks, doug
On 12/15/14, 6:15 AM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
Hi all,
the question arose recently
AM, Ihar Hrachyshka ihrac...@redhat.com
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 in neutron main repo. (You can find the link to the
review at the end of the email.)
Brief
-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 ihrac...@redhat.com
wrote:
Signed PGP part On 15/12/14 18:57, Doug Hellmann wrote:
There may be a similar problem managing dependencies on
libraries
-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 ihrac...@redhat.com
wrote:
Signed PGP part On 15/12/14 17:22, Doug Wiegley wrote:
Hi Ihar,
I’m actually in favor of option 2, but it implies a few things
-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 ihrac...@redhat.com
wrote:
Signed PGP part On 16/12/14 12:50, Doug Hellmann wrote:
On Dec 16, 2014, at 5:13 AM, Ihar Hrachyshka
ihrac...@redhat.com wrote
-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
-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 would be
-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 because of issues I had
On 01/23/2015 05:38 PM, Mike Bayer wrote:
Doug Hellmann d...@doughellmann.com 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,
-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
-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==1.1.9 #
-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 for
-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 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 of
-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-auth.
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
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
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
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
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 ihrac...@redhat.com
mailto:ihrac...@redhat.com wrote:
Hi all,
as per:
https://github.com
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:
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
-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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/17/2015 04:19 PM, Salvatore Orlando wrote:
My opinions inline.
On 17 February 2015 at 16:04, Ihar Hrachyshka ihrac...@redhat.com
mailto:ihrac...@redhat.com wrote:
Hi,
response was huge so far :) so to add more traction, I have
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 Benton wrote:
Why did the services
-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
On 02/20/2015 12:02 PM, Eduard Matei wrote:
Hi,
I'm trying to install devstack and it keeps failing with:
2015-02-20 07:26:12.693 | ++ is_fedora 2015-02-20 07:26:12.693 | ++
[[ -z Ubuntu ]] 2015-02-20 07:26:12.693 | ++ '[' Ubuntu = Fedora
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/18/2015 05:07 PM, Michael Krotscheck wrote:
You got my intention right: I wanted to understand better what
lead some people to create a private channel, what were their
needs.
I'm in a passworded channel, where the majority of members
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/18/2015 08:14 AM, YAMAMOTO Takashi wrote:
hi,
On Wednesday, 18 de February de 2015 at 07:00,
yamam...@valinux.co.jp wrote:
hi,
i want to add an extra requirement specific to OVS-agent.
(namely, I want to add ryu for
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
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
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
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
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
-
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 d...@doughellmann.com
wrote:
On Jan 5, 2015, at 12:00 PM, Matt Riedemann
mrie...@linux.vnet.ibm.com wrote:
There is a deprecation warning in pip 6.0.6
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
to enforce using 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
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
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
___
101 - 200 of 908 matches
Mail list logo
