I think you should update the current reviews (new patch set, not additional
I like those changes: +2
From: Doug Wiegley [mailto:do...@a10networks.com]
Sent: Sunday, August 10, 2014 12:51 AM
To: OpenStack Development Mailing List (not for usage
Thanks Brandon for constant improvisation.
I agree with Doug. Please update current one. We already hv more number of
reviews :-). It will be difficult to manage if we add more.
Sent using CloudMagic
On Sun, Aug 10, 2014 at 3:23 AM, Doug Wiegley
I took a look at https://review.openstack.org/#/c/105331/ and had one minor
issue which I think can be addressed. Prior to approving we need to understand
what the state of the V2 API will be.
From: Vijay Venkatachalam
Li Ma, Mike [Wilson | Bayer], and Roman Podoliaka,
A similar topic came up in Atlanta at a database panel I participated in. Jay
Pipes had organized it as part of the ops track and Peter Boros (of Percona)
and I were on the panel. The issue of what to do about the database under
On Aug 10, 2014, at 9:59 AM, Amrith Kumar amr...@tesora.com wrote:
To Mike Bayer’s point about data distribution and transaction management;
yes, we handle all the details relating to handling data consistency and
providing atomic transactions during Insert/Update/Delete operations.
Thanks for all the detailed analysis, Mike W, Mike B, and Roman.
For a production-ready database system, replication is a must I think. So, the
questions are which replication mode is suitable for OpenStack and which way is
suitable for OpenStack to improve performance and scalability of DB
On Aug 10, 2014, at 11:17 AM, Li Ma skywalker.n...@gmail.com wrote:
How about Galera multi-master cluster? As Mike Bayer said, it is virtually
synchronous by default. It is still possible that outdated rows are queried
that make results not stable.
not sure if I said that :). I know
I 'm trying to create a simple stack with heat.
The template contains SoftwareConfig, SoftwareDeployment and a single
The problem is that the SoftwareDeployment resource is always in progress !
After waiting for more than an hour the stack deployment failed and I got
I want to get more eyes on a design change being proposed for the API
Reference Listing page, http://developer.openstack.org/api-ref.html.
To see the new output, look at this screenshot:
On 02/08/14 04:07, Allison Randal wrote:
A few of us have been independently experimenting with Ansible as a
backend for TripleO, and have just decided to try experimenting
together. I've chatted with Robert, and he says that TripleO was always
intended to have pluggable backends (CM layer),
I have concluded the api testing of LBaaS v2. All the operations on all the
resources pass the api test. The test passes both with JSON and XML
interfaces. I now will move on to scenario testing
The extensions to the neutron clients in tempest are verified to work and
good to merge. Please
On Sun, Aug 10, 2014 at 2:33 AM, Jeremy Stanley fu...@yuggoth.org wrote:
On 2014-08-08 09:06:29 -0400 (-0400), Russell Bryant wrote:
We've seen several times that building and maintaining 3rd party
CI is a *lot* of work.
Building and maintaining *any* CI is a *lot* of work, not the
On Fri, Aug 8, 2014 at 7:06 PM, Thierry Carrez thie...@openstack.org wrote:
Michael Still wrote:
[...] I think an implied side effect of
the runway system is that nova-drivers would -2 blueprint reviews
which were not occupying a slot.
(If we start doing more -2's I think we will need to
One question from me:
Will there be later fixes to remove oslo.config dependency/usage from
I still don't understand how oslo.concurrency can be used as a library
with the configuration being set in a static manner via oslo.config
(let's use the example of `lock_path` @
Does anyone know why in instance_group.py, why do we have the following
logic for transferring metadetails to metadata? Why not transfer metadata
directly from client?
On Friday, August 08, 2014 9:20 PM, Chris Dent wrote:
These may not be directly what you want, but are something worth
tracking as you explore and think.
Thank you for your help.
I will brush up my thought (shift to pollster) with the fixes which
you pointed out.
I was asking this because I got a -2 for
https://review.openstack.org/109505 , just want to know why this new term
metadetails was invented when we already have details, metadata,
system_metadata, instance_metadata, and properties (on images and
2014-08-11 10:09 GMT+08:00 Jay
On 09/08/14 05:09, Russell Bryant wrote:
On 08/06/2014 01:41 PM, Jay Pipes wrote:
On 08/06/2014 01:40 AM, Tom Fifield wrote:
On 06/08/14 13:30, Robert Collins wrote:
On 6 August 2014 17:27, Tom Fifield t...@openstack.org wrote:
On 06/08/14 13:24, Robert Collins wrote:
What happened to
not sure if I said that :). I know extremely little about galera.
Hi Mike Bayer, I'm so sorry I mistake you from Mike Wilson in the last post.
:-) Also, say sorry to Mike Wilson.
I’d totally guess that Galera would need to first have SELECTs come from a
slave node, then the moment it sees
Sorry for the slow reply*. We ran into some trouble with our CI system
after an upgrade to nova's requirements broke our system.
Everything is back up and running now and we've caught up on missed jobs
(including your recheck). My apologies for the hassle. Let me know if
Mail list logo