From: Ken Dreyer <kdreyer@redhat.com>
To: Loic Dachary <loic@dachary.org>,
Yuri Weinstein <yuri.weinstein@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: new testing lab (was: Re: Testing the next giant release)
Date: Thu, 08 Jan 2015 08:50:22 -0700 [thread overview]
Message-ID: <54AEA73E.2010504@redhat.com> (raw)
In-Reply-To: <54ADC3FB.1050201@dachary.org>
On 01/07/2015 04:40 PM, Loic Dachary wrote:
> Great, thanks, I did not know about this one :-)
>
> On 08/01/2015 00:29, Yuri Weinstein wrote:
>> Look for them in new Octo lab - http://pulpito.ceph.redhat.com/
Not everyone in the community is going to know about the Octo lab, and
that URL is unavailable outside of Red Hat's network. I want to be
sure we're explaining this for everyone's benefit here.
In contrast to our "Sepia" lab in Irvine, the "Octo lab" is a new set
of hardware in Raleigh that we've been using in order to run some
other Teuthology tests. As part of the Inktank acquisition by Red Hat,
we've begun migrating some Teuthology tests onto this new hardware.
It's simply a matter of the current hardware's old age and the desire
to move to "something else" before we find ourselves at point where QA
is completely blocked on broken boxes or we're losing data.
A side-effect of this change is that some of our Teuthology test runs
are currently unavailable to the public. (If you've run across Ceph
Redmine tickets recently that mention hostnames like
"*.ceph.redhat.com" you'll know what I'm talking about.)
Obviously we want to make our tests as public as possible just as we
strove to do with the older public "sepia" lab in Irvine.
Sandon Van Ness has been working hard to bring up a second Raleigh lab
that will feature new Seamicro hardware and be as open to the
community as sepia is. Things are still in flux regarding the exact
hostnames, but the current plan is to refer to this lab as "typica" to
distinguish the Raleigh machines from the "sepia" machines in Irvine.
If you're interested in our test labs or other public Ceph
infrastructure, we have a public IRC channel, and it's #sepia on OFTC.
You're welcome to hang out and watch us discuss teuthology failures :)
- Ken
next prev parent reply other threads:[~2015-01-08 15:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 14:02 Testing the next giant release Loic Dachary
[not found] ` <CAFd2DpShjeBXQ5YPfWLVq2zsSTZDBzyZuvo40kOhzVy2fTdmCA@mail.gmail.com>
2015-01-07 22:28 ` Loic Dachary
2015-01-07 22:34 ` Yuri Weinstein
2015-01-07 22:53 ` Tamil Muthamizhan
2015-01-07 23:03 ` Loic Dachary
2015-01-07 23:29 ` Yuri Weinstein
2015-01-07 23:40 ` Loic Dachary
2015-01-08 15:50 ` Ken Dreyer [this message]
2015-01-08 9:39 ` Loic Dachary
2015-01-08 16:10 ` Loic Dachary
2015-01-12 14:23 ` Loic Dachary
2015-01-09 11:06 ` Loic Dachary
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54AEA73E.2010504@redhat.com \
--to=kdreyer@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=loic@dachary.org \
--cc=yuri.weinstein@inktank.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.