On Mon, Apr 1, 2019, 04:11 Fabian Thorns <[email protected]> wrote: > I just wanted to point out that there is an updated version of the > LPIC-305 objectives draft... The following changes were made compared to > the initial version of the draft: > * cLVM was dropped from 352.1 >
So, this one is where I'd like to focus on. I don't think we can do everything that, say RH436, does. But I think there are some very necessary 'identification/knowledge' (weight 1) that should be included. Understand that Cluster LVM (CLVM, and the daemon, clvmd) enables a lot of multi-host communication, and introduces a lot of extensions. E.g., if you ever read my work, you'll see I have "vgchange -al[ny]" and "lvchange -al[ny]". The first thing people ask me is, "what does 'l' mean?" There is also the fact that pvmove, among other operations, works differently for clustered LVM, basically using cluster mirroring. I.e., it has to mirror an extent as it does a pvmove, then break it after the move, and that means cluster mirroring is involved. Pacemaker is also heavily involved in managing these services as well. So, again, I don't know if we need to cover everything, but the concepts of local v. clustered LVM identification, and what functions of Pacemaker are used to manage things like the CLVM and the Distributed Lock Manager (DLM) so people don't mess with them, might be a good 'identification/knowledge' level weight (1). If anything, to save my sanity, as I catch people not realizing what that little 'c' flag means when they run 'vgs.'
_______________________________________________ lpi-examdev mailing list [email protected] https://list.lpi.org/mailman/listinfo/lpi-examdev
