new versions can no longer decode some pre-hammer ObjectStore::Transaction

Specifically the collection attr operations are no longer supported.

drop coll_t 'foo' and 'bar'

These are no longer valid, but we want to keep testing all of the other
old encoded instances.  Just drop them since we don't care about whether
they decode in real clusters.

Signed-off-by: Sage Weil <sage@redhat.com>

drop compat with very old ObjectStore::Transaction

Signed-off-by: Sage Weil <sage@redhat.com>

MDiscoverReply encoding changed

0.80-rc1-35-g4812150

Signed-off-by: Sage Weil <sage@inktank.com>

remove 0.41*, 0.43*

These are old releases and we cover these object types later.

Signed-off-by: Sage Weil <sage@inktank.com>

note MonCap incompat around 0.63

Merge remote-tracking branch 'cc/cuttlefish'

0.61.4-60-g24c59be

note inode_backpointer_t incompat back in 0.56-629

Signed-off-by: Sage Weil <sage@inktank.com>

0.66-500-g93b3e63

note MMonSync incompat change with new scrub

MForward incompat

We changed MonCap[s] encoding and bumped the protocol.  Note the incompat
chagne.

Signed-off-by: Sage Weil <sage@inktank.com>

note forward_incompat changes for single-paxos at 0.54-2289-gbeafca5

Signed-off-by: Joao Eduardo Luis <joao.luis@inktank.com>

v0.52 objects

(Actually, these were generated just before v0.52 release.)

add MonMap v2

OSDMap and OSDMap::Incremental instances with new osd uuid fields.

add prune-archive.sh

prune archive

10 objects per type, version

adding corpus for 0.43

Signed-off-by: Yehuda Sadeh <yehuda.sadeh@dreamhost.com>

note forward_incompat changes from osd_peer_stat_t at 0.41-306-gfbbbd01

osd_peer_stat_t isn't in the old corpus, but it was contained by messages
that used it; mark those as forward_incompat (meaning new code won't
understand the old data).

We did this because it's an on-wire incompatibility only, and a new
feature bit protects us there.

restructure hierarchy

archive/$version/objects/$type/...

0.41-98-g00a2e84

getting started