From: David Zafman <dzafman@redhat.com>
To: Sage Weil <sage@newdream.net>, Marcus Watts <mwatts@redhat.com>
Cc: ceph-devel@vger.kernel.org, haomai@xsky.com
Subject: Re: wip-addr
Date: Mon, 12 Oct 2015 10:42:58 -0700 [thread overview]
Message-ID: <561BF122.5050809@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1510091446090.29929@cobra.newdream.net>
I don't understand how encode/decode of entity_addr_t is changing
without versioning in the encode/decode. This means that this branch is
changing the ceph-objectstore-tool export format if
CEPH_FEATURE_MSG_ADDR2 is part of the features. So we could bump
super_header::super_ver if the export format must change.
Now that I look at it, I'm sure I can clear the watchers and
old_watchers in object_info_t during export because that is dynamic
information and it happens to include entity_addr_t. I need to verify
this, but that may be the only reason that the objectstore tool needs a
valid features value to be passed there.
David
On 10/9/15 2:49 PM, Sage Weil wrote:
>> 2.
>> >(about line 2067 in src/tools/ceph_objectstore_tool.cc)
>> >(use via ceph cmd?) tools - "object store tool".
>> >This has a way to serialize objects which includes a watch list
>> >which includes an address. There should be an option here to say
>> >whether to include exported addresses.
> I think it's safe to use defaults here.. what do you think, David?
next prev parent reply other threads:[~2015-10-12 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 23:24 wip-addr Marcus Watts
2015-10-09 21:49 ` wip-addr Sage Weil
[not found] ` <CACJqLyZh4WQZv_3isjXJy=t6YL700C2GjWuen-QG1D5=RkKHYw@mail.gmail.com>
2015-10-10 3:20 ` wip-addr Haomai Wang
2015-10-10 12:07 ` wip-addr Sage Weil
2015-10-12 17:42 ` David Zafman [this message]
2015-10-12 18:04 ` wip-addr Sage Weil
-- strict thread matches above, loose matches on Subject: below --
2015-08-24 18:01 wip-addr Sage Weil
2015-08-25 10:06 ` wip-addr Marcus Watts
2015-08-25 14:08 ` wip-addr Sage Weil
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=561BF122.5050809@redhat.com \
--to=dzafman@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=haomai@xsky.com \
--cc=mwatts@redhat.com \
--cc=sage@newdream.net \
/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.