Difference between revisions of "LPIC-306 Objectives V3.0"
FabianThorns (Talk | contribs) (Created page with "__FORCETOC__ ==Introduction== The description of the entire LPIC-3 programme is listed here. <br /><br /> ==Version Information== These objectives are version...") |
FabianThorns (Talk | contribs) |
||
Line 5: | Line 5: | ||
==Version Information== | ==Version Information== | ||
− | These objectives are version | + | These objectives are '''A DRAFT FOR''' version 3.0. |
− | There is also a [[ | + | There is also a [[LPIC305SummaryVersion2To3|summary and detailed information]] on the changes from version 2.0 to 3.0 of the objectives. |
− | The version [[LPIC-304 Objectives | + | The version [[LPIC-304 Objectives V2|2.x objectives]] can be found [[LPIC-304 Objectives V2|here]]. |
<br /> | <br /> | ||
Line 15: | Line 15: | ||
==Translations of Objectives== | ==Translations of Objectives== | ||
The following translations of the objectives are available on this wiki: | The following translations of the objectives are available on this wiki: | ||
− | * [[LPIC- | + | * [[LPIC-305 Objectives V3.0|English]] |
− | * [[LPIC- | + | * [[LPIC-305 Objectives V3.0(JA)|Japanese]] |
<br /> | <br /> | ||
==Objectives== | ==Objectives== | ||
− | ===''Topic | + | ===''Topic 351: High Availability Cluster Management''=== |
− | + | ====<span style="color:navy">351.1 High Availability Concepts and Theory (weight: 5)</span>==== | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | ====<span style="color:navy"> | + | |
{| | {| | ||
| style="background:#dadada" | '''Weight''' | | style="background:#dadada" | '''Weight''' | ||
Line 188: | Line 53: | ||
<br /> | <br /> | ||
− | ====<span style="color:navy"> | + | ====<span style="color:navy">351.2 Load Balanced Clusters (weight: 6)</span>==== |
{| | {| | ||
| style="background:#dadada" | '''Weight''' | | style="background:#dadada" | '''Weight''' | ||
Line 217: | Line 82: | ||
<br /> | <br /> | ||
− | ====<span style="color:navy"> | + | ====<span style="color:navy">351.3 Failover Clusters (weight: 6)</span>==== |
{| | {| | ||
| style="background:#dadada" | '''Weight''' | | style="background:#dadada" | '''Weight''' | ||
Line 255: | Line 120: | ||
<br /> | <br /> | ||
− | + | ===''Topic 352: High Availability Cluster Storage''=== | |
− | + | ====<span style="color:navy">352.1 DRBD / cLVM (weight: 3)</span>==== | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | ===''Topic | + | |
− | ====<span style="color:navy"> | + | |
{| | {| | ||
| style="background:#dadada" | '''Weight''' | | style="background:#dadada" | '''Weight''' | ||
Line 304: | Line 153: | ||
<br /> | <br /> | ||
− | ====<span style="color:navy"> | + | ====<span style="color:navy">352.2 Clustered File Systems (weight: 3)</span>==== |
{| | {| | ||
| style="background:#dadada" | '''Weight''' | | style="background:#dadada" | '''Weight''' | ||
Line 338: | Line 187: | ||
* AFS | * AFS | ||
<br /> | <br /> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 16:46, 3 March 2019
Contents
Introduction
The description of the entire LPIC-3 programme is listed here.
Version Information
These objectives are A DRAFT FOR version 3.0.
There is also a summary and detailed information on the changes from version 2.0 to 3.0 of the objectives.
The version 2.x objectives can be found here.
Translations of Objectives
The following translations of the objectives are available on this wiki:
Objectives
Topic 351: High Availability Cluster Management
351.1 High Availability Concepts and Theory (weight: 5)
Weight | 5 |
Description | Candidates should understand the properties and design approaches of high availability clusters. |
Key Knowledge Areas:
- Understand the most important cluster architectures.
- Understand recovery and cluster reorganization mechanisms.
- Design an appropriate cluster architecture for a given purpose.
- Application aspects of high availability.
- Operational considerations of high availability.
The following is a partial list of the used files, terms and utilities:
- Active/Passive Cluster, Active/Active Cluster
- Failover Cluster, Load Balanced Cluster
- Shared-Nothing Cluster, Shared-Disk Cluster
- Cluster resources
- Cluster services
- Quorum
- Fencing
- Split brain
- Redundancy
- Mean Time Before Failure (MTBF)
- Mean Time To Repair (MTTR)
- Service Level Agreement (SLA)
- Desaster Recovery
- Replication
- Session handling
351.2 Load Balanced Clusters (weight: 6)
Weight | 6 |
Description | Candidates should know how to install, configure, maintain and troubleshoot LVS. This includes the configuration and use of keepalived and ldirectord. Candidates should further be able to install, configure, maintain and troubleshoot HAProxy. |
Key Knowledge Areas:
- Understanding of LVS / IPVS.
- Basic knowledge of VRRP.
- Configuration of keepalived.
- Configuration of ldirectord.
- Backend server network configuration.
- Understanding of HAProxy.
- Configuration of HAProxy.
The following is a partial list of the used files, terms and utilities:
- ipvsadm
- syncd
- LVS Forwarding (NAT, Direct Routing, Tunneling, Local Node)
- connection scheduling algorithms
- keepalived configuration file
- ldirectord configuration file
- genhash
- HAProxy configuration file
- load balancing algorithms
- ACLs
351.3 Failover Clusters (weight: 6)
Weight | 6 |
Description | Candidates should have experience in the installation, configuration, maintenance and troubleshooting of a Pacemaker cluster. This includes the use of Corosync. The focus is on Pacemaker 1.1 for Corosync 2.x. |
Key Knowledge Areas:
- Pacemaker architecture and components (CIB, CRMd, PEngine, LRMd, DC, STONITHd).
- Pacemaker cluster configuration.
- Resource classes (OCF, LSB, Systemd, Upstart, Service, STONITH, Nagios).
- Resource rules and constraints (location, order, colocation).
- Advanced resource features (templates, groups, clone resources, multi-state resources).
- Pacemaker management using pcs.
- Pacemaker management using crmsh.
- Configuration and Management of corosync in conjunction with Pacemaker.
- Awareness of other cluster engines (OpenAIS, Heartbeat, CMAN).
The following is a partial list of the used files, terms and utilities:
- pcs
- crm
- crm_mon
- crm_verify
- crm_simulate
- crm_shadow
- crm_resource
- crm_attribute
- crm_node
- crm_standby
- cibadmin
- corosync.conf
- authkey
- corosync-cfgtool
- corosync-cmapctl
- corosync-quorumtool
- stonith_admin
Topic 352: High Availability Cluster Storage
352.1 DRBD / cLVM (weight: 3)
Weight | 3 |
Description | Candidates are expected to have the experience and knowledge to install, configure, maintain and troubleshoot DRBD devices. This includes integration with Pacemaker. DRBD configuration of version 8.4.x is covered. Candidates are further expected to be able to manage LVM configuration within a shared storage cluster. |
Key Knowledge Areas:
- Understanding of DRBD resources, states and replication modes.
- Configuration of DRBD resources, networking, disks and devices.
- Configuration of DRBD automatic recovery and error handling.
- Management of DRBD using drbdadm.
- Basic knowledge of drbdsetup and drbdmeta.
- Integration of DRBD with Pacemaker.
- cLVM
- Integration of cLVM with Pacemaker.
The following is a partial list of the used files, terms and utilities:
- Protocol A, B and C
- Primary, Secondary
- Three-way replication
- drbd kernel module
- drbdadm
- drbdsetup
- drbdmeta
- /etc/drbd.conf
- /proc/drbd
- LVM2
- clvmd
- vgchange, vgs
352.2 Clustered File Systems (weight: 3)
Weight | 3 |
Description | Candidates should know how to install, maintain and troubleshoot installations using GFS2 and OCFS2. This includes integration with Pacemaker as well as awareness of other clustered filesystems available in a Linux environment. |
Key Knowledge Areas:
- Understand the principles of cluster file systems.
- Create, maintain and troubleshoot GFS2 file systems in a cluster.
- Create, maintain and troubleshoot OCFS2 file systems in a cluster.
- Integration of GFS2 and OCFS2 with Pacemaker.
- Awareness of the O2CB cluster stack.
- Awareness of other commonly used clustered file systems.
The following is a partial list of the used files, terms and utilities:
- Distributed Lock Manager (DLM)
- mkfs.gfs2
- mount.gfs2
- fsck.gfs2
- gfs2_grow
- gfs2_edit
- gfs2_jadd
- mkfs.ocfs2
- mount.ocfs2
- fsck.ocfs2
- tunefs.ocfs2
- mounted.ocfs2
- o2info
- o2image
- CephFS
- GlusterFS
- AFS