Hello -
I submitted a patch[1] to remove a broken link on the Devstack Gate[2].
As I've learned more about the projects, it looks like much of that
documentation is out of date, and many of the processes described on
that page have been replaced by Nodepool.
Am I understanding that relation
On Mon, 2014-06-09 at 09:31 -0700, Monty Taylor wrote:
> On 06/09/2014 12:11 AM, Jesus M. Gonzalez-Barahona wrote:
> > On Sun, 2014-06-08 at 13:32 -0400, Monty Taylor wrote:
> >> On 06/02/2014 06:32 PM, Jesus M. Gonzalez-Barahona wrote:
> >>> On Mon, 2014-06-02 at 14:31 -0700, Stefano Maffulli wrot
On 2014-06-11 18:00:30 +0800 (+0800), Le Tian Ren wrote:
> This thread is about branching model, since my team just put a
> project on stackforge and ready to create a milestone-proposed
> branch for final release to support openstack icehouse release.
This is probably a topic better addressed by
On Tue, Jun 10, 2014 at 11:51 PM, Carlos Munoz wrote:
> Hi Elizabeth,
>
> I'm free after 11:30 am my Friday.
Great, I'll grab you on IRC then.
--
Elizabeth Krumbach Joseph || Lyz || pleia2
http://www.princessleia.com
___
OpenStack-Infra mailing list
Hi Infra team,
This thread is about branching model, since my team just put a project on
stackforge and ready to create a milestone-proposed branch for final
release to support openstack icehouse release. Now it's time for us to
consider branching stategy(parallel development) on github, guess t
On 2014-06-11 08:15:54 -0400 (-0400), Sean Dague wrote:
[...]
> Do we need more workers? (possibly more workers made this worse)
>
> Is there something else?
[...]
We've increased the ratio of Logstash workers to Elasticsearch
cluster members. Perhaps we need to increase the ES cluster to 8
nodes
We've not drained the Elastic Search Queue in 2 days, even when we've
not been using all our test node cluster capacity. This strikes me as
very bad.
Elastic Recheck really requires that we can stay current on Elastic
Search, and that seems like a less and less likely outcome.
Will turning of CRM
Hi.
There are a lot of projects ignoring the propsed changes from the
proposal bot resulting in review requests with a lot of huge patch sets
(for example https://review.openstack.org/#/c/89750/).
I think we should change the frequency of the propsal "Imported
Translations from Transifex". One ti
