All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Spray <john.spray@redhat.com>
To: "Handzik, Joe" <joseph.t.handzik@hp.com>, Sage Weil <sweil@redhat.com>
Cc: "gmeno@redhat.com" <gmeno@redhat.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
	"Dan Mick (dmick@redhat.com)" <dmick@redhat.com>
Subject: Re: Thoughts about metadata exposure in Calamari
Date: Sat, 06 Jun 2015 01:38:38 +0100	[thread overview]
Message-ID: <5572410E.9060806@redhat.com> (raw)
In-Reply-To: <73364EFF-DAC3-41F1-816A-DCE5426D4F2B@hp.com>



On 05/06/2015 20:33, Handzik, Joe wrote:
> I err in the direction of calling 'osd metadata' too, but it does mean that Calamari will need to add that call in (I'll leave it to Gregory to say if that is particularly undesirable). Do you think it would be worthwhile to better define the metadata bundle into a structure, or is it ok to leave it as a set of string pairs?

Versioning of the metadata is something to consider. The "osd metadata" 
stuff is outside the osdmap epochs, so anything that is consuming 
updates to it is stuck with doing some kind of full polling as it 
stands.  It might be that some better interface with versions+deltas is 
needed for a management layer to efficiently consume it.

A version concept where the version is incremented when an OSD starts or 
updates its metadata could make synchronization with a management layer 
much more efficient.  Efficiency matters here when we're calling on the 
mons to serialize data for potentially 10000s of OSDs into JSON whenever 
the management layer wants an update.

John

  parent reply	other threads:[~2015-06-06  0:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05 18:39 Thoughts about metadata exposure in Calamari Handzik, Joe
2015-06-05 19:24 ` Sage Weil
2015-06-05 19:33   ` Handzik, Joe
2015-06-05 22:33     ` Gregory Meno
2015-06-06  0:38     ` John Spray [this message]
2015-06-08 19:50       ` Handzik, Joe
2015-06-08 19:54         ` Dan Mick
2015-06-08 20:02           ` Handzik, Joe
2015-06-08 20:07             ` Dan Mick
2015-06-08 20:10               ` Handzik, Joe

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=5572410E.9060806@redhat.com \
    --to=john.spray@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dmick@redhat.com \
    --cc=gmeno@redhat.com \
    --cc=joseph.t.handzik@hp.com \
    --cc=sweil@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.