-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hey all,
as per [1], Cisco Nexus ML2 plugin requires a patched version of
ncclient from github. I wonder:
- - whether this information is still current;
- - why don't we depend on ncclient thru our requirements.txt file.
[1]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/08/14 17:12, Henry Gessau wrote:
On 8/12/2014 10:27 AM, Ihar Hrachyshka wrote:
as per [1], Cisco Nexus ML2 plugin requires a patched version of
ncclient from github. I wonder:
- - whether this information is still current;
Please see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 13/08/14 09:28, Angus Lees wrote:
I'm doing various small cleanup changes as I explore the neutron
codebase. Some of these cleanups are to fix actual bugs discovered
in the code. Almost all of them are tiny and obviously correct.
A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
several periodic checks for havana are failing due to missing
libffi-devel or missing rpm/yum tools on bare-centos (sic!) node.
For example, see [1] (rpm/yum missing) and [2] (compile failure due to
missing libffi-devel).
AFAIK there is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 13/08/14 14:07, Daniel P. Berrange wrote:
On Wed, Aug 13, 2014 at 12:55:48PM +0100, Steven Hardy wrote:
On Wed, Aug 13, 2014 at 11:42:52AM +0100, Daniel P. Berrange
wrote:
On Thu, Aug 07, 2014 at 03:56:04AM -0700, Jay Pipes wrote:
That said,
/Ihar
On 12/08/14 16:27, Ihar Hrachyshka wrote:
Hey all,
as per [1], Cisco Nexus ML2 plugin requires a patched version of
ncclient from github. I wonder:
- whether this information is still current; - why don't we depend
on ncclient thru our requirements.txt file.
[1]: https
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
some plugins depend on modules that are not mentioned in
requirements.txt. Among them, Cisco Nexus (ncclient), Brocade
(ncclient), Embrane (heleosapi)... Some other plugins put their
dependencies in requirements.txt though (like Arista
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/08/14 13:09, Osanai, Hisashi wrote:
Hi,
On Tuesday, August 05, 2014 8:57 PM, Ihar Hrachyshka wrote:
Thanks. To facilitate quicker backport, you may also propose
the patch for review yourself. It may take time before stable
maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
+1. [Not being an oslo core in any way,] I think Mike, with all his
prior experience and vision on where oslo.db should strive to, will be
a great addition to the core team.
/Ihar
On 15/08/14 10:21, Roman Podoliaka wrote:
Hi Oslo team,
I
more about that.
- - once all the relevant patches land in affected projects and
devstack, I'm going to introduce a separate gate job to run against
mysqlconnector.
Cheers,
/Ihar
On 22/07/14 15:03, Ihar Hrachyshka wrote:
FYI: I've moved the spec to oslo space since the switch is not
really
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 17/08/14 02:09, Angus Lees wrote:
On 16 Aug 2014 06:09, Doug Hellmann d...@doughellmann.com
mailto:d...@doughellmann.com wrote:
On Aug 15, 2014, at 9:29 AM, Ihar Hrachyshka
ihrac...@redhat.com
mailto:ihrac...@redhat.com wrote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 18/08/14 11:00, Thierry Carrez wrote:
Mark McLoughlin wrote:
[...] I don't see how any self-respecting open-source project can
throw a release over the wall and have no ability to address
critical bugs with that release until the next release
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 14/08/14 18:33, Ben Nemec wrote:
On 08/14/2014 08:37 AM, Ihar Hrachyshka wrote:
Hi all,
some plugins depend on modules that are not mentioned in
requirements.txt. Among them, Cisco Nexus (ncclient), Brocade
(ncclient), Embrane (heleosapi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
I've found out there are no clear public instructions on how to handle
oslo-incubator synchronizations in master and stable branches neither
at [1] nor at [2]. Though my observations show that there is some oral
tradition around community
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 19/08/14 17:33, wrote:
Hi,all I can't found the clear python version? in the document of
the openstack.org?. Colud someone can tell me whether the havana or
the icehouce supports the python 2.7.5?Does it shoudmodify the
code?? to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thanks!
And I'm immediately bumping the version [1] to utilize
raise_on_warnings=False for my mysql-connector effort. :)
[1]: https://review.openstack.org/115626
On 20/08/14 14:38, Victor Sergeyev wrote:
Hello Folks!
Oslo team is pleased to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 20/08/14 15:42, Vijay Venkatachalam wrote:
Hi,
I am writing a unit testcase with context as subnet, code here [1].
When the context exits a delete of subnet is attempted and I am
getting a MismatchError . Traceback posted here [2].
What
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
I've read the proposal for incubator as described at [1], and I have
several comments/concerns/suggestions to this.
Overall, the idea of giving some space for experimentation that does
not alienate parts of community from Neutron is good.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 20/08/14 18:28, Salvatore Orlando wrote:
Some comments inline.
Salvatore
On 20 August 2014 17:38, Ihar Hrachyshka ihrac...@redhat.com
mailto:ihrac...@redhat.com wrote:
Hi all,
I've read the proposal for incubator as described at [1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 21/08/14 08:33, loy wolfe wrote:
It's also unfair that core team reviewers are forced to spend
time on 3rd plugins and drivers under existing process. There are
so many 3rd networking backend technologies, from hardware to
controller, anyone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 21/08/14 02:03, Clark Boylan wrote:
On Mon, Aug 18, 2014, at 01:59 AM, Ihar Hrachyshka wrote: On
17/08/14 02:09, Angus Lees wrote:
On 16 Aug 2014 06:09, Doug Hellmann d...@doughellmann.com
mailto:d...@doughellmann.com wrote:
On Aug 15
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 21/08/14 09:42, Endre Karlson wrote:
Why pymysql over mysql-python?
http://specs.openstack.org/openstack/oslo-specs/specs/juno/enable-mysql-connector.html#problem-description
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 21/08/14 18:34, Dolph Mathews wrote:
On Thu, Aug 21, 2014 at 11:21 AM, Daniel P. Berrange
berra...@redhat.com mailto:berra...@redhat.com wrote:
On Thu, Aug 21, 2014 at 05:05:04PM +0100, Matthew Booth wrote:
I would prefer that you didn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
this week is quite bumpy for unit testing in gate. First, it was
upgrade to new 'tox' version that broke quite some branches.
And today new testtools 0.9.36 were released and were caught by gate,
which resulted in the following unit test
by the following backport:
https://review.openstack.org/116271
/Ihar
On 22/08/14 14:55, Ihar Hrachyshka wrote:
Hi all,
this week is quite bumpy for unit testing in gate. First, it was
upgrade to new 'tox' version that broke quite some branches.
And today new testtools 0.9.36 were released
.
For Neutron, it should be handled by the following backport:
https://review.openstack.org/116271
/Ihar
On 22/08/14 14:55, Ihar Hrachyshka wrote:
Hi all,
this week is quite bumpy for unit testing in gate. First, it was
upgrade to new 'tox' version that broke quite some branches.
And today new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 24/08/14 20:40, Maru Newby wrote:
On Aug 24, 2014, at 5:14 PM, Henry Gessau ges...@cisco.com
wrote:
Ihar Hrachyshka ihrac...@redhat.com wrote:
Now, maybe putting the module into requirements.txt is an
overkill (though I doubt
://review.openstack.org/#/q/I10c58b3af75d3ab9153a8bbd2a539bf1577de328,n,z
/Ihar
On 09/07/14 13:17, Ihar Hrachyshka wrote:
Hi all,
Multiple projects are suffering from db lock timeouts due to
deadlocks deep in mysqldb library that we use to interact with
mysql servers. In essence, the problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/09/14 13:20, Sean Dague wrote:
On 09/12/2014 06:41 AM, Ihar Hrachyshka wrote:
Some updates/concerns/questions.
The status of introducing a new driver to gate is:
- all the patches for mysql-connector are merged in all
projects; - all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/09/14 16:33, Mike Bayer wrote:
I agree with this, changing the MySQL driver now is not an option.
That was not the proposal. The proposal was to introduce support to
run against something different from MySQLdb + a gate job for that
/StableBranch#Proposing_Fixes
On 19/08/14 15:52, Ihar Hrachyshka wrote:
Hi all,
I've found out there are no clear public instructions on how to
handle oslo-incubator synchronizations in master and stable
branches neither at [1] nor at [2]. Though my observations show
that there is some oral
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/09/14 17:30, Mike Bayer wrote:
On Sep 12, 2014, at 10:40 AM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
Signed PGP part On 12/09/14 16:33, Mike Bayer wrote:
I agree with this, changing the MySQL driver now is not an
option
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/09/14 19:08, Doug Hellmann wrote:
On Sep 12, 2014, at 1:03 PM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
Signed PGP part On 12/09/14 17:30, Mike Bayer wrote:
On Sep 12, 2014, at 10:40 AM, Ihar Hrachyshka
ihrac...@redhat.com wrote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/09/14 18:00, Mike Bayer wrote:
On Sep 12, 2014, at 11:56 AM, Johannes Erdfelt
johan...@erdfelt.com wrote:
On Fri, Sep 12, 2014, Doug Hellmann d...@doughellmann.com
wrote:
I don’t think we will want to retroactively change the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 22/09/14 17:07, Radomir Dopieralski wrote:
Horizon's tests were recently broken by a change in the Ceilometer
client that removed a deprecated exception. The exception was
deprecated for a while already, but as it often is, nobody did the
Hi all,
I'm new to openstack and qpid, trying to get more insight into messaging. I've
attempted to verify the fix for the bug 1257293 in LP, but the scenario fails
for me, even though oslo.messaging fix reached github master I used for my
verification attempt.
Briefly, I've repeated actions
I've asked Mark McClain to tag a new release before *specifically* because
we're going to hit the issue. The issue is in both master and stable/havana.
Latest client releases were tagged by Mark, but since he seems to be busy these
days, I think someone should step in and tag and release a new
And for those interested in details:
the issue was triggered by 3799efe792700e773c40cc42c265eee09230 in master
(15a912b1ca3c24ba8851b8b77d6de8027e120d78 in stable/havana). The required fix
in neutronclient that should be released ASAP is:
02baef46968b816ac544b037297273ff6a4e8e1b. I'm going
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/06/14 15:40, Alexei Kornienko wrote:
On 06/10/2014 03:59 PM, Gordon Sim wrote:
On 06/10/2014 12:03 PM, Dina Belova wrote:
Hello, stackers!
Oslo.messaging is future of how different OpenStack components
communicate with each other,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 29/05/14 17:33, Yuriy Taraday wrote:
On Wed, May 28, 2014 at 3:54 AM, Joe Gordon joe.gord...@gmail.com
wrote:
On Fri, May 23, 2014 at 1:13 PM, Nachi Ueno na...@ntti3.com
wrote:
(2) Avoid duplication of works I have several experience of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
I'm currently pushing Neutron to oslo.messaging, and while at it, a
question popped up.
So in oslo-rpc, we have the following notification drivers available:
neutron.openstack.common.notifier.log_notifier
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 17/06/14 00:10, Anita Kuno wrote:
On 06/16/2014 06:02 PM, Kevin Benton wrote:
Hello,
In the Big Switch ML2 driver, we rely on quite a bit of code from
the Big Switch plugin. This works fine for distributions that
include the entire neutron
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 25/06/14 12:59, Sean Dague wrote:
On 06/25/2014 03:56 AM, Martin Geisler wrote:
Mark McLoughlin mar...@redhat.com writes:
On Tue, 2014-06-24 at 13:56 -0700, Clint Byrum wrote:
Excerpts from Mark McLoughlin's message of 2014-06-24
12:49:52
then compare to the iterative
improvements you will push?
Best, -jay
Please share your thoughts on this topic.
Regards, Alexei Kornienko
On 06/16/2014 02:47 PM, Gordon Sim wrote:
On 06/13/2014 02:06 PM, Ihar Hrachyshka wrote:
On 10/06/14 15:40, Alexei Kornienko wrote:
On 06/10/2014 03:59 PM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/27/2014 04:04 PM, Ihar Hrachyshka wrote: On 26/06/14 22:38,
Alexei Kornienko wrote:
Hello Jay,
Benchmark for oslo.messaging is really simple: You create a
client that sends messages infinitively and a server that
processes them. After
:22 PM, Ihar Hrachyshka wrote:
Alexei Kornienko wrote:
Some performance tests may be introduced but they would be more
like functional tests since they require setup of actual messaging
server (rabbit, etc.).
Yes. I think we already have some. F.e.
tests/drivers/test_impl_qpid.__py
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/07/14 15:55, Alexei Kornienko wrote:
Hi,
Thanks for detailed answer. Please see my comments inline.
Regards,
On 07/01/2014 04:28 PM, Ihar Hrachyshka wrote: On 30/06/14 21:34,
Alexei Kornienko wrote:
Hello,
My understanding
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/07/14 10:12, Miguel Angel Ajo wrote:
Shihazhang,
I really believe we need the RPC refactor done for this cycle, and
given the close deadlines we have (July 10 for spec submission and
July 20 for spec approval).
Don't you think it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/07/14 17:14, Alexei Kornienko wrote:
Hi,
Please see some minor comments inline. Do you think we can schedule
some time to discuss this topic on one of the upcoming meetings? We
can come out with some kind of the summary and actions plan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/07/14 19:47, Nader Lahouti wrote:
Hi All and Ihar,
As part of blueprint oslo-messaging the
neutron/openstack/common/rpc tree is removed. I was using
impl_kombu module to process notification from keystone with this
following code
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
at the moment we have several bot jobs that sync contents to affected
projects:
- - translations are copied from transifex;
- - requirements are copied from global requirements repo.
We have another source of common code - oslo-incubator,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/07/14 16:54, Mark McLoughlin wrote:
On Fri, 2014-07-04 at 15:31 +0200, Ihar Hrachyshka wrote:
Hi all, at the moment we have several bot jobs that sync contents
to affected projects:
- translations are copied from transifex
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/07/14 22:28, Jay Pipes wrote:
On 07/07/2014 04:17 PM, Mike Bayer wrote:
On 7/7/14, 3:57 PM, Matt Riedemann wrote:
Regarding the eventlet + mysql sadness, I remembered this [1]
in the nova.db.api code.
I'm not sure if that's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/07/14 22:14, Jay Pipes wrote:
On 07/02/2014 09:23 PM, Mike Bayer wrote:
I've just added a new section to this wiki, MySQLdb + eventlet =
sad, summarizing some discussions I've had in the past couple of
days about the ongoing issue that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/07/14 16:06, Jay Pipes wrote:
On 07/08/2014 04:46 AM, Ihar Hrachyshka wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512
On 07/07/14 22:14, Jay Pipes wrote:
On 07/02/2014 09:23 PM, Mike Bayer wrote:
I've just added a new section
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
Multiple projects are suffering from db lock timeouts due to deadlocks
deep in mysqldb library that we use to interact with mysql servers. In
essence, the problem is due to missing eventlet support in mysqldb
module, meaning when a db lock
into
python-neutron package. AFAIK there is still no bug for that in
Red Hat Bugzilla, so please report one.
Thanks, Kevin Benton
On Mon, Jun 16, 2014 at 3:37 PM, Ihar Hrachyshka
ihrac...@redhat.com wrote:
On 17/06/14 00:10, Anita Kuno wrote:
On 06/16/2014 06:02 PM, Kevin Benton wrote
project though, while
others may need trivial updates);
- - switch defaults in devstack;
- - update documentation to refer to the new library.
Thanks, Roman
On Wed, Jul 9, 2014 at 2:17 PM, Ihar Hrachyshka
ihrac...@redhat.com wrote: Hi all,
Multiple projects are suffering from db lock
(it's default for mysqldb but not mysql-connector).
I've done it in devstack patch for now, but probably it belongs to
oslo.db.
Thanks, Roman
On Wed, Jul 9, 2014 at 2:17 PM, Ihar Hrachyshka
ihrac...@redhat.com wrote: Hi all,
Multiple projects are suffering from db lock timeouts due
]:
https://review.openstack.org/#/q/owner:%22Angus+Lees+%253Cgus%2540inodes.org%253E%22+status:open,n,z
Thanks, Roman
On Wed, Jul 9, 2014 at 5:43 PM, Ihar Hrachyshka
ihrac...@redhat.com wrote: On 09/07/14 15:40, Sean Dague wrote:
On 07/09/2014 09:00 AM, Roman Podoliaka wrote:
Hi Ihar,
AFAIU
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/07/14 08:09, Angus Lees wrote:
On 10 July 2014 00:59, Roman Podoliaka rpodoly...@mirantis.com
wrote:
Not sure what issues you are talking about, but I just replaced
mysql with mysql+mysqlconnector in my db connection string
in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/07/14 11:07, Salvatore Orlando wrote:
The patch for bug 1329564 [1] merged about 11 hours ago. From [2]
it seems there has been an improvement on the failure rate, which
seem to have dropped to 25% from over 40%. Still, since the patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/07/14 13:17, Ihar Hrachyshka wrote:
Hi all,
Multiple projects are suffering from db lock timeouts due to
deadlocks deep in mysqldb library that we use to interact with
mysql servers. In essence, the problem is due to missing eventlet
this mysqldb/eventlet contention in the back of my mind for
some time now. I'm glad to see some work being done in this
area.
Carl
On Fri, Jul 11, 2014 at 7:04 AM, Ihar Hrachyshka
ihrac...@redhat.com wrote:
On 09/07/14 13:17, Ihar Hrachyshka wrote:
Hi all,
Multiple projects are suffering from db
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/07/14 03:17, Mike Bayer wrote:
On 7/11/14, 7:26 PM, Carl Baldwin wrote:
On Jul 11, 2014 5:32 PM, Vishvananda Ishaya
vishvana...@gmail.com
mailto:vishvana...@gmail.com wrote:
I have tried using pymysql in place of mysqldb and in
I'm pretty excited about the possibilities here. I've had
this mysqldb/eventlet contention in the back of my mind for
some time now. I'm glad to see some work being done in this
area.
Carl
On Fri, Jul 11, 2014 at 7:04 AM, Ihar Hrachyshka
ihrac...@redhat.com wrote:
On 09/07/14 13:17, Ihar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/07/14 02:49, Jay Pipes wrote:
On 07/11/2014 08:04 AM, Ihar Hrachyshka wrote: On 09/07/14 13:17,
Ihar Hrachyshka wrote:
Hi all,
Multiple projects are suffering from db lock timeouts due to
deadlocks deep in mysqldb library that we use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 14/07/14 07:45, Thomas Goirand wrote:
On 07/14/2014 12:20 AM, Ihar Hrachyshka wrote:
On 11/07/14 19:20, Clark Boylan wrote:
That said there is at least one other pure python alternative,
PyMySQL. PyMySQL supports py3k and pypy. We should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 14/07/14 15:54, Clark Boylan wrote:
On Sun, Jul 13, 2014 at 9:20 AM, Ihar Hrachyshka
ihrac...@redhat.com wrote: On 11/07/14 19:20, Clark Boylan
wrote:
Before we get too far ahead of ourselves mysql-connector is
not hosted on pypi. Instead
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 15/07/14 20:36, Joshua Harlow wrote:
LGTM.
I'd be interesting in the future to see if we can transparently use
some other serialization format (besides json)...
That's my only compliant is that jsonutils is still named jsonutils
instead
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 14/07/14 22:48, Vishvananda Ishaya wrote:
On Jul 13, 2014, at 9:29 AM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
Signed PGP part On 12/07/14 03:17, Mike Bayer wrote:
On 7/11/14, 7:26 PM, Carl Baldwin wrote:
On Jul 11, 2014 5:32 PM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 16/07/14 01:50, Vishvananda Ishaya wrote:
On Jul 15, 2014, at 3:30 PM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
Signed PGP part On 14/07/14 22:48, Vishvananda Ishaya wrote:
On Jul 13, 2014, at 9:29 AM, Ihar Hrachyshka
ihrac
in bugzilla.
1. https://bugzilla.redhat.com/show_bug.cgi?id=1120332
On Wed, Jul 9, 2014 at 3:29 AM, Ihar Hrachyshka
ihrac...@redhat.com mailto:ihrac...@redhat.com wrote:
Reviving the old thread.
On 17/06/14 11:23, Kevin Benton wrote:
Hi Ihar,
What is the reason to breakup neutron
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 17/07/14 17:12, Kyle Mestery wrote:
On Thu, Jul 17, 2014 at 6:42 AM, Thierry Carrez
thie...@openstack.org wrote:
Kyle Mestery wrote:
As we're getting down to the wire in Juno, I'd like to propose
we have a weekly meeting on the nova-network
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 14/07/14 17:03, Ihar Hrachyshka wrote:
On 14/07/14 15:54, Clark Boylan wrote:
On Sun, Jul 13, 2014 at 9:20 AM, Ihar Hrachyshka
ihrac...@redhat.com wrote: On 11/07/14 19:20, Clark Boylan
wrote:
Before we get too far ahead of ourselves mysql
getting
there.
That's Openstack! Changes take time here.
I look forward to getting this fixed :/
Thanks for tracking oslo.db part of that, I really appreciate that.
On 18 July 2014 21:45, Ihar Hrachyshka ihrac...@redhat.com
mailto:ihrac...@redhat.com wrote:
On 14/07/14 17:03, Ihar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
FYI: I've moved the spec to oslo space since the switch is not really
limited to neutron, and most of coding is to be done in oslo.db
(though not much anyway).
New spec: https://review.openstack.org/#/c/108355/
On 09/07/14 13:17, Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 24/07/14 04:22, Quang Long wrote:
Hi guys, I have a question, if we use OpenStack Havana using
QEMU/KVM Hypervisor and based on Ubuntu 12.04 OS, what OS for
instance can we use when lauch?
I found a link related to this issue, for refrence?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 28/07/14 08:52, Angus Lees wrote:
On Mon, 21 Jul 2014 04:39:49 PM David Kranz wrote:
On 07/21/2014 04:13 PM, Jay Pipes wrote:
On 07/21/2014 02:03 PM, Clint Byrum wrote:
Thanks Matthew for the analysis.
I think you missed something though.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 28/07/14 16:22, Doug Hellmann wrote:
On Jul 28, 2014, at 2:52 AM, Angus Lees g...@inodes.org wrote:
On Mon, 21 Jul 2014 04:39:49 PM David Kranz wrote:
On 07/21/2014 04:13 PM, Jay Pipes wrote:
On 07/21/2014 02:03 PM, Clint Byrum wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 29/07/14 12:15, Daniel P. Berrange wrote:
Looking at the current review backlog I think that we have to
seriously question whether our stable branch review process in
Nova is working to an acceptable level
On Havana
- 43 patches
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 30/07/14 04:00, Kyle Mestery wrote:
I'm personally ok with this hard limit, but I'd really like to
hear from distribution people here to understand their thoughts,
including what versions of dnsmasq ship with their products and how
this would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 29/07/14 18:12, Daniel P. Berrange wrote:
On Tue, Jul 29, 2014 at 08:30:09AM -0700, Jay Pipes wrote:
On 07/29/2014 06:13 AM, Daniel P. Berrange wrote:
On Tue, Jul 29, 2014 at 02:04:42PM +0200, Thierry Carrez
wrote:
Ihar Hrachyshka a écrit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
openstack-dev is for development discussions, not user discussions. A
better place to ask is probably openstack@ [1] or even corresponding
Foreman/RDO community mailing lists.
[1]: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 30/07/14 19:22, Kevin L. Mitchell wrote:
On Wed, 2014-07-30 at 09:01 +0200, Flavio Percoco wrote:
As a stable-maint, I'm always hesitant to review patches I've no
understanding on, hence I end up just checking how big is the
patch, whether
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
in Gerrit UI, I would like to be able to see a separate column with my
votes, so that I have a clear view of what was missed from my eye.
I've looked in settings, and failed to find an option for this.
Is there a way to achieve this?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 31/07/14 12:46, Yuriy Taraday wrote:
On Thu, Jul 31, 2014 at 2:23 PM, Ihar Hrachyshka
ihrac...@redhat.com mailto:ihrac...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512
Hi all,
in Gerrit UI, I would like to be able
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 13/05/14 17:55, Matt Riedemann wrote:
On 5/13/2014 7:35 AM, Doug Hellmann wrote:
On Mon, May 12, 2014 at 3:25 PM, Roman Podoliaka
rpodoly...@mirantis.com wrote:
Hi all,
Yes, once the oslo.db initial release is cut, we expect the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/08/14 16:36, Malawade, Abhijeet wrote:
Hi all,
rpc module is not imported properly in nova, cinder, neutron
projects. It is imported from wrong package.
In oslo-incubator 'rpc' module is used in
openstack/common/service.py file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/08/14 11:22, Osanai, Hisashi wrote:
Hi,
I would like to have the following fix for IceHouse branch because
the problem happens on it but the fix was committed on Juno-2
only. Is there any process to backport fixes to old branches?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/08/14 13:30, Osanai, Hisashi wrote:
Thank you for your quick response.
I don't have enough rights for nominating the bug so I put the tag
icehouse-backport-potential instead.
https://bugs.launchpad.net/ceilometer/+bug/1326250
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/04/14 12:35, Victor Stinner wrote:
(Follow-up of the [olso] use of the oslo namespace package
thread)
Hi,
The openstack.common module also known as Oslo Incubator or
OpenStack Common Libraries has 44 dependencies. IMO we reach a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 30/04/14 23:21, Narasimhan, Vivekanandan wrote:
Hi,
I 've been trying to run test_ovs_neutron_agent.py unit test from
openstack neutron master 'tip', and
am hitting dependency errors for novaclient as here:
Yes, neutron requires
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 15/05/14 20:50, Eduard barrera wrote:
Hi all,
I was wondering what is the meaning of this acronyms... Are they
acronyms, right ?
Quantum Virtual O??
Quantum B Ridge ?
It's bridge.
qg ?
It's gateway.
qve ?
What do they
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 21/05/14 13:20, Abhijeet Jain wrote:
Hi Openstack-developers,
I am Abhijeet Jain. One of the contributor in OpenStack.
I was just working on optimizing the codes in Neutron , Keystone,
Cinder modules. Then, I came across with a very
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
+1, I also don't see any significant value in using generic names
instead of project names, while the drawbacks are obvious.
/Ihar
On 23/05/14 14:30, Sergey Lukjanov wrote:
+1 for using program codename.
So, we'll need to rename some existing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
let me give you some examples of patches that I think do not *require*
any bug or blueprint (though some of them still have an associated bug):
https://review.openstack.org/#/c/90781/ (minor pythonic refactoring)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 28/05/14 23:03, Nachi Ueno wrote:
Hi folks
OK, so it looks like this is consensus in the community,
Link bug or bp for most of commit Exception for not linking bug:
(1) Infra sync (2) minor fix. (typo, small code refactor, fix doc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
the repo is useful when you try to find out what was merged recently
(like in case of a regression). There are two release branches there:
Havana and master, but there is no branch for Icehouse.
May I ask anyone who is in charge of the repo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Do we even apply freeze for test requirements? It should be ok since
it's for tests only. So there is no real impact on deployer side.
Also, depfreeze seems to apply to openstack/requirements repository
only [1], and projects are open to consume
1 - 100 of 908 matches
Mail list logo
