Yes, Device Mapper Multipath I/O (dm-mpio), that is quite a bit objective on its own, but very, very necessary in Enterprise environments -- especially for virtualization hosts (if one is using VM) and related cloud infrastructure, but also high performance computing (HPC) and other environments.
Although it's gotten better now in more recent kernel and userspace releases, as Device Specific Modules (DSM) and related tunings can usually be automatically detected and support loaded for the underlying topology and devices. It's usually just a matter of WWNs and a few other things. Way, way better and more automated than just a decade ago. -- Sent from my Essential PH-1, please excuse any typos Bryan J Smith - http://linkedin.com/in/bjsmith On Mon, Apr 1, 2019, 04:32 Ortwin Ebhardt <[email protected]> wrote: > Hello Thomas, > > I’ve been recently a bit tangled up, so it may be my points have been > discussed in the oast and I missed it. If so, sorry for redundancy. > > > > After studying the objectives I am missing multipath. As we are dealing > with High Availability for Network, Storage and even resources, I think > accessibility for iSCSI or FC should be addressed, too. > > > > Ortwin Ebhardt > > Senior Consultant > > > Capricorn Consulting GmbH > An Krietes Park 6 > 28307 Bremen > > > Telefon: +49 421 98981-642 > > E-Mail: [email protected] > > Internet: www.capricorn.de > > Gerne laden wir Sie zur Sophos Endkunden-Roadshow 2019 ein! Themen, > Termine und Anmeldung finden Sie hier > <https://events.sophos.com/DialogfuerIT-Sicherheit2019&id=98304-4798>. > > Geschäftsführer: Thomas Bargfrede, Dipl.-Ing. Axel Buschmann, > Thomas von Massenbach, Thomas Heuermann > Registergericht: Amtsgericht Bremen, HRB 31421 > > > Unsere Informationspflicht nach Art. 13 DSGVO finden Sie hier > <https://www.capricorn.de/datenschutz-kurz.html> > > *Hinweis* > > Diese elektronische Nachricht ist vertraulich und ausschließlich für den > Adressaten bestimmt. Falls Sie nicht der beabsichtigte Empfänger der > Nachricht sind, ist jede Veröffentlichung, > Vervielfältigung, Verbreitung oder Nutzung des Inhalts der Nachricht > verboten. > Falls Sie die Nachricht versehentlich erhalten haben, informieren Sie die > Capricorn Consulting GmbH bitte > unverzüglich telefonisch oder per E-Mail. > > This electronic mail is intended to be for the use of the individual or > entity named above. If you are not the intended recipient of the > information, be aware that any disclosure, copying, > distribution or use of the contents of this information is prohibited. If > you have received this electronic mail in error, please notify the > Capricorn Consulting GmbH by telephone or email. > > > > *Von:* lpi-examdev <[email protected]> * Im Auftrag von *Fabian > Thorns > *Gesendet:* Montag, 1. April 2019 11:11 > *An:* LPI Exam Development <[email protected]> > *Betreff:* Re: [lpi-examdev] LPIC-305 High Availability > > > > Hello, > > > > I just wanted to point out that there is an updated version of the > LPIC-305 objectives draft: > > > > https://wiki.lpi.org/pubwiki/index.php?title=LPIC-305_Objectives_V3.0 > > > > This draft no longer contains the disaster discovery topic as we were not > able to identify a clear set of commonly used tools. Instead, we increased > the weight of several objectives (namely 351.1, 351.2, 351.3, 353.1, 353.2, > 354.3 and 354.4) where we would like to go into more details. > > > > The following changes were made compared to the initial version of the > draft: > > > > * cLVM was dropped from 352.1 > > > > * DRBD was extended in 352.1 to also cover quorum and handler for split > brain and fencing > > * QUESTION: What's you opinion on LINSTOR? For now, we test knowledge of > its architecture and features, but we don't go into any details in this > revision since the tool is quite new. Would you go into more details? > > > > * Replacing failed bricks and recovering from physical media failure is > now included in 353.1 > > > > * ceph-volumes and concepts of ceph updates were added to 353.2 > > > > * 354.3 was extended to also cover extending, growing, shrinking and > moving LVM volumes as well as managing LVM pools > > > > * 354.4 now includes systemd-networkd and the implementation of BGP for > internal high availability (assigning floating IPs) > > > > * Pacemaker integration of various topics is now consolidated in 351.3 > > > > So far, this draft has not received any feedback on this list. I'd be glad > to get some opinions on this proposal, so please feel free to speak up :) > > > > Fabian > > > > > > On Tue, Mar 5, 2019 at 10:04 AM Fabian Thorns <[email protected]> wrote: > > Hello again, > > > > you might have noticed that the proposal on the pure virtualization 304 > exam left some spare objectives on High Availability. Another outcome of a > lot of the discussions we've had around this was that we should keep High > Availability in LPIC-3 but consider making it an own exam. > > > > Here is how a pure High Availability exam could be similar to: > > > > https://wiki.lpi.org/wiki/LPIC-305_Objectives_V3.0 > > > > The diff to 304v2 is here: > > > > > https://wiki.lpi.org/pubwiki/index.php?title=LPIC-305_Objectives_V3.0&type=revision&diff=&oldid=5138 > > > > Besides some small changes, mostly in the field of Pacemaker, you'll see > that we've added distributed storage to this exam. One might argue this is > again a rather arbitrary combination just like the old 304 exam; however, > storage is an important component of any HA stack and, in return, any > highly available storage requires certain HA measures. Feel free to discuss > this combination. > > > > Please note that this draft is not complete yet, it *DOES NEED YOUR > FEEDBACK*. There are eight weights which are not assigned to a real > objective yet. I've parked them in the potential topic 'Backup and Disaster > Recovery', but I am not sure whether or not that is a good idea. My concern > is that there is not the 'one', most prominent tool in that area. Just take > backup as an example, what should we cover, Bacula, Bareos, Amanda, > BackupPC? And once you have touched Veeam+VMware, would you still prefer > the open source tools (this is no statement about my personal preferences, > btw)? > > > > Where would you like these weights to be put? Remember, this will be a new > exam, so we can do ANYTHING we want :) > > > > Finally, I would be interested in knowing you thoughts on the term SRE and > if we should try to leverage this buzzword's momentum for the new 305 exam. > > > > Fabian > > > > -- > > Fabian Thorns <[email protected]> GPG: F1426B12 > > Director of Certification Development, Linux Professional Institute > > > > > -- > > Fabian Thorns <[email protected]> GPG: F1426B12 > > Director of Certification Development, Linux Professional Institute > > > _______________________________________________ > lpi-examdev mailing list > [email protected] > https://list.lpi.org/mailman/listinfo/lpi-examdev
_______________________________________________ lpi-examdev mailing list [email protected] https://list.lpi.org/mailman/listinfo/lpi-examdev
