On 2016-05-04 10:52:56 +1000 (+1000), Michael Still wrote:
> The instance of stackalytics run by the openstack-infra team seems to be
> gummed up.
[...]
As is likely noted elsewhere, stackalytics.com is not run by the
Infra team but rather by Mirantis. There is a
stackalytics.openstack.org
On Wed, May 4, 2016 at 11:03 AM, Davanum Srinivas wrote:
> Michael,
>
> The stackalytics bots do not have access to gerrit at the moment. We
> noticed it last friday and talked to infra folks:
>
>
Michael,
The stackalytics bots do not have access to gerrit at the moment. We
noticed it last friday and talked to infra folks:
http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2016-04-29.log.html#t2016-04-29T14:24:07
Ilya Shakat helps a lot with the existing instance
The instance of stackalytics run by the openstack-infra team seems to be
gummed up. It alleges that the last time there was a nova code review was
April 17, which seems... unlikely.
Who looks after this thing so I can ping them gently?
Thanks,
Michael
--
Rackspace Australia
On Tue, May 3, 2016 at 10:19 AM, Paul Belanger wrote:
> On Tue, May 03, 2016 at 10:01:06AM -0700, Elizabeth K. Joseph wrote:
>> On Mon, May 2, 2016 at 11:55 AM, Spencer Krum wrote:
>> > I think this is a good conversation to have. I would recommend we
On 05/03/2016 02:19 PM, Morgan Fainberg wrote:
> On Tue, May 3, 2016 at 10:19 AM, Paul Belanger
> wrote:
>
>> On Tue, May 03, 2016 at 10:01:06AM -0700, Elizabeth K. Joseph wrote:
>>> On Mon, May 2, 2016 at 11:55 AM, Spencer Krum
>> wrote:
I
On Tue, May 3, 2016 at 10:19 AM, Paul Belanger
wrote:
> On Tue, May 03, 2016 at 10:01:06AM -0700, Elizabeth K. Joseph wrote:
> > On Mon, May 2, 2016 at 11:55 AM, Spencer Krum
> wrote:
> > > I think this is a good conversation to have. I would
On Tue, May 03, 2016 at 10:01:06AM -0700, Elizabeth K. Joseph wrote:
> On Mon, May 2, 2016 at 11:55 AM, Spencer Krum wrote:
> > I think this is a good conversation to have. I would recommend we start
> > a thread-per-conference for simplicity. Folks can use this to
On Mon, May 2, 2016 at 11:55 AM, Spencer Krum wrote:
> I think this is a good conversation to have. I would recommend we start
> a thread-per-conference for simplicity. Folks can use this to coordinate
> attendance, ensure we submit unique presentations, and to help each
>
In the past, we have had a dedicated mailing list for high performance
computing. With the use of tags on subject lines and the formation of the
scientific working group at Austin, it is proposed to delete the HPC list.
Activity has been very low with only call for papers on the list since the
Hi all!
At the summit, a few people asked us about StoryBoard meetings (and the
next StoryBoard meetup). So here are the details:
IRC Meetings (text shamelessly copied from wiki):
-
StoryBoard holds public weekly meetings in #openstack-meeting,
What options do I have for storing the new watchdog image(s) while they
get cached?
As I can see all the current images are loaded dynamically from the web,
so I guess that I shouldn't add mine directly to any (devstack or
tempest) repo.
Can [1] be the solution?
--
Ferenc
[1]
On Tue, May 03, 2016 at 04:57:02PM +1000, Joshua Hesketh wrote:
> Hey,
>
> Yolanda is helping repair this. Basically the log filesystem needs
> repairing and should be back shortly.
Thanks for the prompt response.
Yours Tony.
signature.asc
Description: PGP signature
Hey,
Yolanda is helping repair this. Basically the log filesystem needs
repairing and should be back shortly.
Cheers,
Josh
On Tue, May 3, 2016 at 4:27 PM, Tony Breeds wrote:
> So the subject says it all really ;P
>
> The last batch of periodic-stable jobs all failed
So the subject says it all really ;P
The last batch of periodic-stable jobs all failed reporting 'UNSTABLE' as the
result.
The ones I checked had missing log files.
eg
http://lists.openstack.org/pipermail/openstack-stable-maint/2016-May/004275.html
I reported this on IRC but just in case
15 matches
Mail list logo