[LU-1303] LOD/OSP Implementation

• Type: New Feature
• Resolution: Fixed
• Priority: Critical
• Fix Version/s: Lustre 2.4.0

Epic/Theme

ORI-4

• Assignee: Alex Zhuravlev
• Reporter: Mikhail Pershin

Description

Lustre 2.0 uses old Release 1.8 client-side stack components to connect to the OSTs for stripe object pre-creation and orphan management. Remove these components, replacing them with a new subsystem that implements transactional access to non-local OSDs to ensure a rigorous separation of client/server and server/server protocols which avoids existing recovery race conditions.

Issue Links

• Trackbacks: Lustre Community Development in Progress Features are being developed for future Lustre releases both at Whamcloud and by other organizations in the Lustre community. These will be eligible for inclusion in future Lustre releases as per our processes

Comments

[Andreas Dilger]

There are a number of generated compile warnings in the code that need to be fixed due to LOD/OSP workarounds that need to be removed, such as:

#if LUSTRE_VERSION_CODE < OBD_OCD_VERSION(2, 3, 50, 0)
        if (rc == 0 && ma->ma_valid & MA_COOKIE && ma->ma_valid & MA_LOV &&
            ma->ma_valid & MA_FLAGS && ma->ma_attr_flags & MDS_UNLINK_DESTROY)
                /* Since echo client is incapable of destorying ost object,
                 * it will destory the object here. */
                rc = mdd_lovobj_unlink(env, mdd, mdd_cobj, la, ma, 1);
#else   
#warning "please remove this after 2.4 (LOD/OSP)."
#endif          

I've submitted http://review.whamcloud.com/3741 to bump the version check to 2.3.55, to give the LOD/OSP patches a chance to land, but they should be removed as the LOD/OSP code is landed.