All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Cutler <ncutler@suse.cz>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Fwd: EXT: [ceph-users] ceph-lvm - a tool to deploy OSDs from LVM volumes
Date: Wed, 21 Jun 2017 13:25:00 +0200	[thread overview]
Message-ID: <b3eb845a-b70a-d2c8-b8b2-0ac75f1b6c4a@suse.cz> (raw)
In-Reply-To: <CAC-Np1wAh5mewdgKOosHc=b8WrRZW+zUuosoaB-FmmX1g4fLLA@mail.gmail.com>

> My position is that a small, python-only, with no direct bindings to
> Ceph other than the CLI, should probably have the
> freedom of staying out of tree, and that it can keep up with older
> versions, and release often when bugs come up (as you've mentioned
> happened
> with ceph-deploy)

Release often in a single codestream? In other words, you are not 
planning to maintain separate codestreams for each stable branch of Ceph?

By the way, is there any other use for ceph-volume, other than as a tool 
for deploying OSDs? If not, I don't see the "no direct bindings to 
Ceph". It is bound to Ceph directly in that Ceph is the only reason for 
its existence.

Nathan

  reply	other threads:[~2017-06-21 11:25 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
2017-06-20 20:40                       ` Nathan Cutler
2017-06-20 21:38                         ` Alfredo Deza
2017-06-21 11:25                           ` Nathan Cutler [this message]
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=b3eb845a-b70a-d2c8-b8b2-0ac75f1b6c4a@suse.cz \
    --to=ncutler@suse.cz \
    --cc=ceph-devel@vger.kernel.org \
    /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.