Talk:LPIC-2 Objectives V4 - Revision history

Alessandro: 208.1 Implementing a web server - Proposed update

2015-04-27T16:04:40Z

208.1 Implementing a web server - Proposed update

← Older revision		Revision as of 16:04, 27 April 2015
Line 83:		Line 83:

	--[[User:EricDeschamps\|EricDeschamps]] 11:04, 5 April 2013 (EDT)		--[[User:EricDeschamps\|EricDeschamps]] 11:04, 5 April 2013 (EDT)

			==== 208.1 Implementing a web server ====
			#Proposed update
			[https://www.lpi.org/study-resources/lpic-2-202-exam-objectives/] and [http://wiki.lpi.org/wiki/LPIC-2] both list Apache mod_ssl configuration item <code>SSLCertificateChainFile</code> in the list of "things to know". However, I can read in [http://httpd.apache.org/docs/2.4/en/mod/mod_ssl.html] that:

			SSLCertificateChainFile is deprecated

			SSLCertificateChainFile became obsolete with version 2.4.8, when
			SSLCertificateFile was extended to also load intermediate CA
			certificates from the server certificate file.

			I think we should take notice and plan the removal of this item from the objectives.

			--[[User:Alessandro\|Alessandro]] 10:12, 27 April 2015 (EDT)

GMatthewRice: moved Talk:LPIC-2 to Talk:LPIC-2 Objectives V4 over redirect

2015-02-11T11:59:23Z

moved Talk:LPIC-2 to Talk:LPIC-2 Objectives V4 over redirect

← Older revision		Revision as of 11:59, 11 February 2015
(No difference)

GMatthewRice: moved Talk:LPIC-2 Objectives V4 to Talk:LPIC-2

2014-01-17T18:56:42Z

moved Talk:LPIC-2 Objectives V4 to Talk:LPIC-2

← Older revision		Revision as of 18:56, 17 January 2014
(No difference)

GMatthewRice: /* 213/214.4 Predict Future Resource Needs */

2013-06-15T14:21:57Z

213/214.4 Predict Future Resource Needs

← Older revision		Revision as of 14:21, 15 June 2013
Line 1:		Line 1:
			Anonymous:
			Notes: on Device Mapper coverage

			Based on reading through the current [1] and Wiki [2] developments, I have the following recommendation.

			- Create a new, separate Objective in Section 204
			- Suggested "Section 204.4 Device Mapper" follows [A]
			- From other 204 Sections ...
			- Remove Device Mapper (e.g., /dev/mapper)
			- Remove WWID/WWN and SCSI ID (e.g., scsi_id)
			- NOTE: Do not remove iSCSI** (although may belong in another section)

			**NOTE: Given the details involved with iSCSI initiator (client), among other options, consider moving iSCSI initator (plus any other "network storage client" boot/config/init) to its own, separate Section 204 (204.5?). This e-mail only covers Device Mapper and its facilities, which I suggest for Section 204.4.

			[1] http://www.lpi.org/linux-certifications/programs/lpic-2/exam-201/#section-203
			[2] http://wiki.lpi.org/wiki/LPIC-2_Objectives#Topic_203:_Filesystem_and_Devices

			[A] Objective "Suggestion" w/extra detail (beyond what would be published)

			Objective 204.4 Device Mapper

			Weight: 1 (as 204.2 Today) or 2 (as 204.2 Wiki/Future)

			NOTE: 1-2 is _less_ than other 204 Sections

			Description: Candidates should be able to use DeviceMapper facilities and userspace to identify, filter, blacklist, whitelist and resolve presentation of block devices, including for virtualization guests, LVM mappings, multitarget mappings (SCSI/SAS) and multipath mappings (FC/SAN).

			NOTE: This section is _not_ for things done with udev, but _only_ DeviceMapper-specific facilities and userspace.

			- Command: dmsetup
			E.g., dmsetup [info\|ls]

			- Command: scsi_id
			E.g., scsi_id --page=0x8[0\|3] --device=(device)

			- Path(s): /dev/disk/by-[id\|label\|path\|uuid]/
			These should be self-explanatory ;)

			- Path(s): /dev/mapper/
			Moved from LVM Section, which is more for LVM operations

			- Path(s): /sys/block/
			Block device paths -- e.g., often symlinks to /sys/devices

			- Path(s): /sys/devices/
			Device bus/host/lun paths -- e.g., Bus/HBA as well as c:t:d:s

			- Config*: lvm.conf
			Limited to: volume_list, filter, issue_discards

			- Config*: multipath.conf
			Limited to: wwid and alias only

			- Runtime: /var/lib/multipath/bindings
			Limited to: wwid-only


			*lvm.conf _limited_ to:
			- Section "activation" (VG/LV activation options)
			- Option "volume_list" (VG implicit whitelist)
			- Section "device" (PV/device options)
			- Option "filter" (device blacklist and/or whitelist)
			- Option "issue_discards" (NAND EEPROM SSD lifespan/perf)
			- Option "preferred_names" (path order of preference)

			LVM NOTE: Remember, "volume_list" and/or "filter" is often used to ensure virtualization hosts do _not_ access Physical Volumes (and active Volume Groups) for their virtualization guests.

			*multipath.conf _limited_ to:
			- Section "blacklist" (blacklist)
			- Option "wwid" (blacklist)
			- Section "multipaths / multipath" (whitelist/alias in stanza)
			- Option "wwid" (whitelist)
			- Option "alias" (label)

			LVM NOTE: It's also important to "filter" Devices so they are only found on select devices for multitarget (SCSI/SAS) and multipath (FC/SAN).


	==== 213/214.4 Predict Future Resource Needs ====		==== 213/214.4 Predict Future Resource Needs ====

EricDeschamps: comment about 213/214.4 objective

2013-04-05T15:04:45Z

comment about 213/214.4 objective

New page

==== 213/214.4 Predict Future Resource Needs ====

Could anyone give good source to prepare courses for this topic? I could not for myself.

If this is too tricky to find source, i think we should avoid the topic.

--[[User:EricDeschamps|EricDeschamps]] 11:04, 5 April 2013 (EDT)