CEPH filesystem development
 help / color / mirror / Atom feed
From: Mykola Golub <mgolub@mirantis.com>
To: Andreas-Joachim Peters <andreas.joachim.peters@cern.ch>
Cc: Loic Dachary <loic@dachary.org>,
	Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: RFC: new rados whereis command
Date: Fri, 26 Dec 2014 09:54:10 +0200	[thread overview]
Message-ID: <20141226075409.GA22340@gmail.com> (raw)
In-Reply-To: <5499EB3C.2040602@dachary.org>

On Tue, Dec 23, 2014 at 11:22:52PM +0100, Loic Dachary wrote:
> Hi Andreas,
> 
> I took a closer look at https://github.com/ceph/ceph/pull/2730
> implementing rados whereis [--dns] and I think it deserves a
> discussion here. If I understand correctly, it relies on a new
> function of the rados API:
> 
>   typedef struct whereis {
>     int64_t osd_id;                              //< ID of the OSD hosting this object
>     std::string osd_state;                       //< state of the OSD - either 'active' or 'inactive'

Wouldn't it be better to use enum instead of string for state?

>     int64_t pg_seed;                             //< Seed of the PG hosting this object
>     std::string ip_string;                       //< Ip as string
>     std::vector<std::string> host_names;         //< optional reverse DNS HostNames
>     std::map<std::string, std::string> user_map; //< optional user KV map
>     void resolve();                              //< reverse DNS OSD IPs and store in HostNames
>   } whereis_t;
> 
>   static int whereis(IoCtx &ioctx, const std::string &oid, std::vector<whereis_t> &locations);

-- 
Mykola Golub

  parent reply	other threads:[~2014-12-26  7:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-23 22:22 RFC: new rados whereis command Loic Dachary
2014-12-25 12:52 ` Wido den Hollander
2014-12-26  7:54 ` Mykola Golub [this message]
2014-12-29 20:08 ` Sage Weil
2015-01-09 15:21   ` Andreas Joachim Peters

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=20141226075409.GA22340@gmail.com \
    --to=mgolub@mirantis.com \
    --cc=andreas.joachim.peters@cern.ch \
    --cc=ceph-devel@vger.kernel.org \
    --cc=loic@dachary.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox