All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Josh Durgin <jdurgin@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: [Ceph-qa] ceph-qa-suite branching (merge it into ceph.git?)
Date: Wed, 13 Apr 2016 23:59:44 +0200	[thread overview]
Message-ID: <570EC150.1020305@dachary.org> (raw)
In-Reply-To: <570EB787.9090208@redhat.com>



On 13/04/2016 23:17, Josh Durgin wrote:
> On 04/13/2016 02:09 PM, Loic Dachary wrote:
>>
>>
>> On 13/04/2016 22:12, Josh Durgin wrote:
>>> On 04/13/2016 11:38 AM, Sage Weil wrote:
>>>> On Wed, 13 Apr 2016, Samuel Just wrote:
>>>>> It also doesn't seem like it would actually present a problem in any case.
>>>>
>>>> The reason we didn't do this before was because we wanted to revise tests
>>>> independently of the thing being tested.  But as John points out,
>>>> specifying a test branch should accomplish that, at least for testing.
>>>>
>>>> It might be nice to preserve the ability specify an alternate repo with
>>>> totally out-of-tree tests.  Maybe that can be done with a simple reorg of
>>>> the repo, like putting everything under qa/, so that tasks/ and suites/
>>>> don't appear at the top level (of ceph.git or ceph-qa-suite.git).
>>>
>>> It'll also be quite helpful to specify an alternate repo (not just
>>> branch) for testing suite changes without pushing to the main ceph.git
>>> and triggering gitbuilder builds.
>>
>> We can keep the current --ceph-qa-suite-git-url argument for that. Or do you have something else in mind ?
> 
> I wasn't aware of that - looks like it's just a teuthology-openstack
> option. I was thinking we should have the same option for teuthology-suite.

Right. The teuthology-openstack option sets the ceph_qa_suite_git_url configuration option from ~/.teuthology.yaml which is not OpenStack specific. A naive implementation in teuthology-suite would be to replace the value in ~/.teuthology.yaml in the same way teuthology-openstack does it. It would however be problematic for a long lived cluster with multiple users racing with each other. A better implementation would be to have that as part of the config.yaml.

-- 
Loïc Dachary, Artisan Logiciel Libre
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-04-13 21:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13 10:52 ceph-qa-suite branching (merge it into ceph.git?) John Spray
2016-04-13 12:45 ` Sage Weil
     [not found] ` <570E4843.8000102@dachary.org>
2016-04-13 13:58   ` [Ceph-qa] " Gregory Farnum
2016-04-13 18:31     ` John Spray
2016-04-13 18:35       ` Samuel Just
2016-04-13 18:38         ` Sage Weil
2016-04-13 18:50           ` John Spray
2016-04-13 18:54           ` Gregory Farnum
2016-04-13 19:00             ` Sage Weil
2016-04-13 19:06               ` Samuel Just
2016-04-13 20:12           ` Josh Durgin
2016-04-13 20:16             ` Samuel Just
     [not found]             ` <570EB571.10907@dachary.org>
2016-04-13 21:11               ` Samuel Just
2016-04-13 21:17               ` Josh Durgin
2016-04-13 21:59                 ` Loic Dachary [this message]
     [not found] ` <CAKPXa=Y5rJ4ygM9Sdvys+86RwufnKopTOkMNdPHcpCh5bFbQ0w@mail.gmail.com>
2016-04-13 18:10   ` Fwd: " Vasu Kulkarni
2016-04-13 18:23     ` Samuel Just
2016-04-13 18:57       ` Vasu Kulkarni
2016-04-13 18:46   ` John Spray
2016-04-13 19:06     ` Vasu Kulkarni
2016-04-13 19:09       ` [Ceph-qa] " Sage Weil
2016-04-13 19:08     ` Josh Durgin
2016-04-13 19:18     ` Abhishek Lekshmanan

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=570EC150.1020305@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=jdurgin@redhat.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.