CEPH filesystem development
 help / color / mirror / Atom feed
From: Mykola Golub <mgolub@mirantis.com>
To: ceph-devel@vger.kernel.org
Cc: Jason Dillaman <dillaman@redhat.com>, Josh Durgin <jdurgin@redhat.com>
Subject: CEPH_RBD_API: options on image create
Date: Wed, 30 Sep 2015 09:50:45 +0300	[thread overview]
Message-ID: <20150930065044.GA14958@gmail.com> (raw)

Hi,

It was mentioned several times eralier that it would be nice to pass
options as key/value configuration pairs on image create instead of
expanding rbd_create/rbd_clone/rbd_copy for every possible
configuration override.

What do you think about this API?

Introduce rbd_image_options_t and functions to manipulate it:

int rbd_image_options_create(rbd_image_options_t* opts);

void rbd_image_options_destroy(rbd_image_options_t opts);

int rbd_image_options_set(rbd_image_options_t opts, int optname,
                          const void* optval, size_t optlen);

int rbd_image_options_get(rbd_image_options_t opts, int optname,
                          void* optval, size_t* optlen);

void rbd_image_options_iterate(rbd_image_options_t opts,
                               void (*func)(int* optname, void* optval, size_t* optlen));

Functions that return a value return 0 on success, and -ERROR on
failure.

optname is a constant like RBD_OPTION_STRIPE_UNIT,
RBD_OPTION_STRIPE_COUNT...

Pass options as additional argument to rbd_create, rbd_clone (and may
be rbd_copy) functions:

int rbd_create4(rados_ioctx_t io, const char *name, uint64_t size,
	        uint64_t features, int *order, rbd_image_options_t opts);

int rbd_clone3(rados_ioctx_t p_ioctx, const char *p_name,
               const char *p_snapname, rados_ioctx_t c_ioctx,
               const char *c_name, uint64_t features, int *c_order,
               rbd_image_options_t opts);

int rbd_copy3(rbd_image_t src, rbd_image_t dest, rbd_image_options_t opts); // possibly


Example:

rbd_image_options_t opts;
int r;
r = rbd_image_options_create(&opts);
assert(r == 0);
uint64_t stripe_unit = 65536;
r = rbd_image_options_set(opts, RBD_OPTION_STRIPE_UNIT,
                          &stripe_unit, size_of(stripe_unit));
assert(r == 0);
uint64_t stripe_count = 16;
r = rbd_image_options_set(opts, RBD_OPTION_STRIPE_COUNT,
                          &stripe_count, size_of(stripe_count));
assert(r == 0);
const char* journal_object_pool = "journal";
r = rbd_image_options_set(opts, RBD_OPTION_JOURNAL_OBJECT_POOL,
                          journal_object_pool, strlen(journal_object_pool) + 1);
assert(r == 0);
r = rbd_create4(io, name, size, features, int *order, rbd_image_options_t opts);

cleanup:
rbd_image_options_destroy(opts);

-- 
Mykola Golub

             reply	other threads:[~2015-09-30  6:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30  6:50 Mykola Golub [this message]
2015-10-14 19:34 ` CEPH_RBD_API: options on image create Jason Dillaman
2015-10-15  3:12   ` Josh Durgin
2015-10-15  6:56     ` Mykola Golub
2015-10-15  6:33   ` Mykola Golub
2015-10-15 12:05     ` Jason Dillaman
2015-10-15 12:33       ` Mykola Golub
2015-10-15 12:47         ` Jason Dillaman
2015-10-15 13:28           ` Mykola Golub
2015-10-15 13:45             ` Sage Weil
2015-10-15 18:29               ` Josh Durgin
2015-10-16  5:32                 ` Mykola Golub
2015-10-24 13:16                   ` Mykola Golub

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=20150930065044.GA14958@gmail.com \
    --to=mgolub@mirantis.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dillaman@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox