Difference between revisions of "LPIC-306 Objectives V3.0"

From LPI Wiki
Jump to: navigation, search
(353.2 Ceph Storage Clusters (weight: 9))
(354.1 Single Node High Availability (weight: 2))
Line 272: Line 272:
 
|}
 
|}
 
'''Key Knowledge Areas:'''
 
'''Key Knowledge Areas:'''
* Understand and monitor S.M.A.R.T values using smartmontools
+
* Understand and monitor S.M.A.R.T values using smartmontools, including triggering frequent disk checks
 
* Configure system shutdown at specific UPC events
 
* Configure system shutdown at specific UPC events
 
* Configure monit for alerts in case of resource exhaustion
 
* Configure monit for alerts in case of resource exhaustion
Line 279: Line 279:
 
* /etc/smartd.conf
 
* /etc/smartd.conf
 
* smartd
 
* smartd
* nvme
+
* nvme-cli
 
* apcupsd
 
* apcupsd
 
* apctest
 
* apctest

Revision as of 16:44, 17 March 2019

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: 6)

Weight 6
Description Candidates should understand the properties and design approaches of high availability clusters.

Key Knowledge Areas:

  • Understand the goals of High Availability and Site Reliability Engineering
  • Understand common cluster architectures
  • Understand recovery and cluster reorganization mechanisms
  • Design an appropriate cluster architecture for a given purpose
  • Understand application aspects of high availability
  • Understand 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 (Node and Resource Level Fencing)
  • Split brain
  • Redundancy
  • Mean Time Before Failure (MTBF)
  • Mean Time To Repair (MTTR)
  • Service Level Agreement (SLA)
  • Disaster Recovery
  • Replication
  • Session handling


351.2 Load Balanced Clusters (weight: 9)

Weight 9
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: 9)

Weight 9
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:

  • Understand the architecture and components of Pacemaker (CIB, CRMd, PEngine, LRMd, DC, STONITHd)
  • Manage Pacemaker cluster configurations
  • Understand Pacemaker resource classes (OCF, LSB, Systemd, Service, STONITH, Nagios)
  • Manage Pacermaker resources
  • Manage resource rules and constraints (location, order, colocation).
  • Manage advanced resource features (templates, groups, clone resources, multi-state resources)
  • Obtain node information and manage node health
  • Manage quorum and fencing in a Pacermaker cluster
  • Configure the Split Brain Detector on shared storage
  • Configure Quorum disks
  • Manage Pacemaker using pcs
  • Manage Pacemaker using crmsh
  • Configure and management of corosync in conjunction with Pacemaker
  • Awareness of Pacemaker ACLs
  • Awareness of other cluster engines (OpenAIS, Heartbeat, CMAN)

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
  • stonith
  • ocf:pacemaker:ping
  • ocf:pacermaker:NodeUtilization
  • ocf:pacermaker:ocf:SysInfo
  • ocf:pacemaker:HealthCPU
  • ocf:pacemaker:HealthSMART
  • sbd
  • mkqdisk


Topic 352: High Availability Cluster Storage

352.1 DRBD / cLVM (weight: 6)

Weight 6
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 9.0.x is covered. Candidates are further expected to be able to manage LVM configuration within a shared storage cluster.

Key Knowledge Areas:

  • Understanding of the DRBD architecture
  • Understanding of DRBD resources, states and replication modes
  • Configuration of DRBD resources, disks and devices
  • Configuration of DRBD networking connections and meshes
  • Configuration of DRBD automatic recovery and error handling
  • Managing of DRBD using drbdadm
  • Basic knowledge of drbdsetup and drbdmeta
  • Restore and verify the integrity of a DRBD device after an outage
  • Integration of DRBD with Pacemaker
  • Understanding of cLVM and manage LVM volumes on a shared block device
  • 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
  • /etc/drbd.d/
  • /proc/drbd
  • LVM2
  • clvmd
  • vgchange, vgs


352.2 Clustered File Systems (weight: 4)

Weight 4
Description Candidates should be able to install, maintain and troubleshoot GFS2 and OCFS2 filesystems. This includes integration with Pacemaker as well as awareness of other clustered filesystems available on Linux.

Key Knowledge Areas:

  • Understand the principles of cluster file systems and distributed file systems
  • Understand the Distributed Lock Manager
  • 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, such as AFS

The following is a partial list of the used files, terms and utilities:

  • mkfs.gfs2
  • mount.gfs2
  • fsck.gfs2
  • gfs2_grow
  • gfs2_edit
  • gfs2_jadd
  • mkfs.ocfs2
  • mount.ocfs2
  • fsck.ocfs2
  • tunefs.ocfs2
  • mounted.ocfs2
  • o2info
  • o2image



Topic 353: Distributed Storage

353.1 GlusterFS Storage Clusters (weight: 5)

Weight 5
Description Candidates should be able to manage and maintain a GlusterFS storage cluster.

Key Knowledge Areas:

  • Understand the architecture and components of GlusterFS
  • Manage GlusterFS peers, trusted storge pools, bricks and volumes
  • Mount and use an existing GlusterFS
  • Configure high availability aspects of GlusterFS
  • Scale up a GlusterFS cluster
  • Restore and verify the integrity of a GlusterFS cluster after an outage
  • Awareness of GNFS

Partial list of the used files, terms and utilities:

  • gluster (including relevant subcommands)


353.2 Ceph Storage Clusters (weight: 9)

Weight 9
Description Candidates should be able to manage and maintain a Ceph Cluster. This includes the configuration of RGW, RDB devices and CephFS.

Key Knowledge Areas:

  • Understand the architecture and components of Ceph
  • Manage OSD, MON and MDS
  • Understand and manage placement groups and pools
  • Understand storage backends (FileStore and BlueStore)
  • Initialize a Ceph cluster
  • Create and manage Rados Block Devices
  • Create and manage CephFS volumes, including snapshots
  • Mount and use an existing CephFS
  • Understand and adjust CRUSH maps
  • Configure high availability aspects of Ceph
  • Scale up a Ceph cluster
  • Restore and verify the integrity of a Ceph cluster after an outage

Partial list of the used files, terms and utilities:

  • ceph-deploy (including relevant subcommands)
  • ceph.conf
  • ceph (including relevant subcommands)
  • rados (including relevant subcommands)
  • rdb (including relevant subcommands)
  • cephfs (including relevant subcommands)
  • ceph-authtool
  • ceph-crushtool



Topic 354: Node High Availability

354.1 Single Node High Availability (weight: 2)

Weight 2
Description Candidates should be able to monitor a local node for potential hardware failures and resource shortages.

Key Knowledge Areas:

  • Understand and monitor S.M.A.R.T values using smartmontools, including triggering frequent disk checks
  • Configure system shutdown at specific UPC events
  • Configure monit for alerts in case of resource exhaustion

The following is a partial list of the used files, terms and utilities:

  • smartctl
  • /etc/smartd.conf
  • smartd
  • nvme-cli
  • apcupsd
  • apctest
  • monit


354.2 Advanced RAID (weight: 2)

Weight 2
Description Candidates should be able to manage software raid devices on Linux. This includes advanced features such as partitonable RAIDs and RAID containers as well as recovering RAID arrays after a failure.

Key Knowledge Areas:

  • Manage RAID devices using various raid levels, including hot spare discs, partitionable RAIDs and RAID containers
  • Add and remove devices from an existing RAID
  • Change the RAID level of an existing device
  • Recover a RAID device after a failure
  • Understand various metadata formats and RAID geometries
  • Understand availability and performance properties of various raid levels
  • Configure mdadm monitoring and reporting

The following is a partial list of the used files, terms and utilities:

  • mdadm
  • /proc/mdstat
  • /proc/sys/dev/raid/*
  • Partiton types 0xFD and 0xDA


354.3 Advanced LVM (weight: 3)

Weight 3
Description Candidates should be able to configure LVM volumes. This includes managing LVM snapshot and RAIDs.

Key Knowledge Areas:

  • Understand and manage LVM, including linear and striped volumes
  • Understand and manage LVM snapshots
  • Understand and manage LVM RAIDs

The following is a partial list of the used files, terms and utilities:

  • /etc/lvm/lvm.conf
  • pvcreate
  • vgcreate
  • vgreduce
  • lvconvert
  • lvcreate
  • lvextend


354.4 Network High Availability (weight: 5)

Weight 5
Description Candidates should be able to configure redundant networking connections and manage VLANs.

Key Knowledge Areas:

  • Understand and configure bonding network interface
  • Network bond modes and algorithms (active-backup, blance-tlb, balance-alb, 802.3ad, balance-rr, balance-xor, broadcast)
  • Configure switch configuration for high availability, including RSTP
  • Configure VLANs on regular and bonded network interfaces
  • Persist bonding and VLAN configuration
  • Understand the principle of autonomous systems and BGP to manage redundant uplinks

The following is a partial list of the used files, terms and utilities:

  • bonding.ko (including relevant module options)
  • /etc/network/interfaces
  • /etc/sysconfig/networking-scripts/ifcfg-*
  • nmcli
  • /sys/class/net/bonding_masters
  • /sys/class/net/bond*/bonding/miimon
  • /sys/class/net/bond*/bonding/slaves
  • ifenslave
  • ip



Topic 355: Backup and Disaster Recovery

355.1 TBD: Backup (weight: TBD)

Weight TBD
Description

Key Knowledge Areas: The following is a partial list of the used files, terms and utilities:

355.2 Disaster Recovery (weight: TBD)

Weight TBD
Description

Key Knowledge Areas: The following is a partial list of the used files, terms and utilities: