On 01/29/2018 10:55 AM, John Spray wrote:
On Mon, Jan 29, 2018 at 9:12 AM, Wido den Hollander <wido@xxxxxxxx> wrote:
Hi,
I'm still working on the 'brag' module for the Mgr to send out a report
every X interval back to the Ceph project so that we get a feeling of how
people use Ceph.
I'd like to store a timestamp of the last report send and then wait for it
to expire before sending a new one.
The interval will be something like a week by default and I'd like to store
it somewhere persistent.
Obviously I can store it in a local variable, but if the Mgr fails or is
restarted so is the module and thus that data is lost.
Is it OK to use the config-key for this? It's not really configuration, but
is it allowed to store such values in there?
Yep!
Awesome! I'll use that to store the timestamp persistently so that I can
access it later.
The "config" naming is a strong hint to programmers that this is not
for bulk data, but ultimately it's all just bytes :-)
True :-) Might want to put a limit on there on the MON (configurable?)
to prevent people from using it as a rather large store.
Wido
John
Thanks,
Wido
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
