From: Andrew Schoen <aschoen@redhat.com>
To: Nathan Cutler <ncutler@suse.cz>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Fwd: EXT: [ceph-users] ceph-lvm - a tool to deploy OSDs from LVM volumes
Date: Tue, 20 Jun 2017 09:43:02 -0500 [thread overview]
Message-ID: <CAEPMp+41hTKanCsxJ7r-YA7k11QFQczGPXaiwmYptW9viFAEAQ@mail.gmail.com> (raw)
In-Reply-To: <09d01c0c-b5f0-519e-0687-c8117e1fc2ce@suse.cz>
On Tue, Jun 20, 2017 at 2:12 AM, Nathan Cutler <ncutler@suse.cz> wrote:
> On 06/19/2017 10:24 PM, John Spray wrote:
>>
>> Testing: being separate is only easier if you're only doing python
>> unit testing.
>
>
> Hear hear! I do a lot of functional/integration/regression testing and can
> confirm that it became a whole lot easier when ceph-qa-suite was moved
> in-tree.
Comparing ceph-qa-suite to a contained python module isn't quite a
fair comparison though. For upstream testing of ceph-volume (if it
existed outside ceph.git) you'd simply install it with pip. A jenkins
job that built every branch of ceph-volume.git and pushed them to
shaman would be easy enough as well if that's what's preferred.
Honestly, I think all manner of testing (including functional) becomes
easier with this out of ceph.git. Especially when it comes to testing
something inside of a container.
Best,
Andrew
next prev parent reply other threads:[~2017-06-20 14:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 18:11 EXT: ceph-lvm - a tool to deploy OSDs from LVM volumes Warren Wang - ISD
[not found] ` <A5E80C1D-74F4-455B-8257-5B9E2FF6AB39-dFwxUrggiyBBDgjK7y7TUQ@public.gmane.org>
2017-06-16 18:23 ` Alfredo Deza
2017-06-16 18:42 ` EXT: [ceph-users] " Sage Weil
[not found] ` <CAC-Np1yqCZO7CzEjTV+hrNve857BtM_rZ+LxAi6Vf9UJkPM04g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-16 19:37 ` EXT: " Willem Jan Withagen
2017-06-19 13:27 ` John Spray
[not found] ` <CALe9h7cV6U3A_OT9R8tv_yPoGG9zFaWF3qXV5cwYK0KM-NDu4g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-19 14:13 ` Alfredo Deza
[not found] ` <CAC-Np1yiRgkmhZCOij9qSBmqUo-YYtErWXk2gevYuvWKrYFyeg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-19 15:37 ` Willem Jan Withagen
2017-06-19 17:57 ` EXT: [ceph-users] " Alfredo Deza
2017-06-19 18:57 ` Willem Jan Withagen
2017-06-19 16:55 ` John Spray
2017-06-19 17:53 ` Alfredo Deza
2017-06-19 18:41 ` Andrew Schoen
2017-06-19 20:24 ` Fwd: " John Spray
2017-06-19 21:14 ` Alfredo Deza
2017-06-19 21:58 ` Sage Weil
2017-06-20 14:09 ` Alfredo Deza
2017-06-21 12:33 ` Alfredo Deza
2017-06-20 7:12 ` Fwd: " Nathan Cutler
2017-06-20 14:43 ` Andrew Schoen [this message]
2017-06-20 20:40 ` Nathan Cutler
2017-06-20 21:38 ` Alfredo Deza
2017-06-21 11:25 ` Nathan Cutler
2017-06-21 11:47 ` ceph-deploy hammer support Nathan Cutler
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=CAEPMp+41hTKanCsxJ7r-YA7k11QFQczGPXaiwmYptW9viFAEAQ@mail.gmail.com \
--to=aschoen@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ncutler@suse.cz \
/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.