Difference between revisions of "LPIC-301(ES)"
(→Topic 301: Concepts, Architecture and Design) |
|||
Line 55: | Line 55: | ||
====<span style="color:navy">301.2 Directory Design</span>==== | ====<span style="color:navy">301.2 Directory Design</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 2 | | style="background:#eaeaea" | 2 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be able to design an implement an LDAP directory, while planning an appropriate Directory Information Tree to avoid redundancy. Candidates should have an understanding of the types of data which are appropriate for storage in an LDAP directory | | style="background:#eaeaea" | Candidates should be able to design an implement an LDAP directory, while planning an appropriate Directory Information Tree to avoid redundancy. Candidates should have an understanding of the types of data which are appropriate for storage in an LDAP directory | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave:''' |
* Define LDAP directory content | * Define LDAP directory content | ||
* Organize directory | * Organize directory | ||
Line 73: | Line 73: | ||
====<span style="color:navy">301.3 Schemas</span>==== | ====<span style="color:navy">301.3 Schemas</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 3 | | style="background:#eaeaea" | 3 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be familiar with schema concepts, and the base schema files included with an OpenLDAP installation | | style="background:#eaeaea" | Candidates should be familiar with schema concepts, and the base schema files included with an OpenLDAP installation | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave:''' |
* LDAP schema concepts | * LDAP schema concepts | ||
* Create and modify schemas | * Create and modify schemas | ||
Line 97: | Line 97: | ||
====<span style="color:navy">302.1 Compiling and Installing OpenLDAP</span>==== | ====<span style="color:navy">302.1 Compiling and Installing OpenLDAP</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 3 | | style="background:#eaeaea" | 3 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be able to compile and install OpenLDAP from source and from packages | | style="background:#eaeaea" | Candidates should be able to compile and install OpenLDAP from source and from packages | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave:''' |
* Compile and configure OpenLDAP from source | * Compile and configure OpenLDAP from source | ||
* Knowledge of OpenLDAP backend databases | * Knowledge of OpenLDAP backend databases | ||
Line 119: | Line 119: | ||
====<span style="color:navy">302.2 Developing for LDAP with Perl and C</span>==== | ====<span style="color:navy">302.2 Developing for LDAP with Perl and C</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 1 | | style="background:#eaeaea" | 1 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be able to write basic Perl scripts to interact with an LDAP directory | | style="background:#eaeaea" | Candidates should be able to write basic Perl scripts to interact with an LDAP directory | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave:''' |
* Syntax of Perl's Net::LDAP module | * Syntax of Perl's Net::LDAP module | ||
* Write Perl scripts to bind, search, and modify directories | * Write Perl scripts to bind, search, and modify directories | ||
Line 138: | Line 138: | ||
====<span style="color:navy">303.1 placeholder</span>==== | ====<span style="color:navy">303.1 placeholder</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 0 | | style="background:#eaeaea" | 0 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | This objective dropped due to JTA results | | style="background:#eaeaea" | This objective dropped due to JTA results | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave:''' |
* N/A | * N/A | ||
'''The following is a partial list of the used files, terms and utilities:''' | '''The following is a partial list of the used files, terms and utilities:''' | ||
Line 151: | Line 151: | ||
====<span style="color:navy">303.2 Access Control Lists in LDAP</span>==== | ====<span style="color:navy">303.2 Access Control Lists in LDAP</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 2 | | style="background:#eaeaea" | 2 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be able to plan and implement access control lists | | style="background:#eaeaea" | Candidates should be able to plan and implement access control lists | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave:''' |
* Plan LDAP access control lists | * Plan LDAP access control lists | ||
* Grant and revoke LDAP access permissions | * Grant and revoke LDAP access permissions | ||
Line 176: | Line 176: | ||
====<span style="color:navy">303.3 LDAP Replication</span>==== | ====<span style="color:navy">303.3 LDAP Replication</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 5 | | style="background:#eaeaea" | 5 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be familiar with the various replication strategies available with OpenLDAP | | style="background:#eaeaea" | Candidates should be familiar with the various replication strategies available with OpenLDAP | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave''' |
* Replication concepts | * Replication concepts | ||
* Configure OpenLDAP replication | * Configure OpenLDAP replication | ||
Line 205: | Line 205: | ||
====<span style="color:navy">303.4 Securing the Directory</span>==== | ====<span style="color:navy">303.4 Securing the Directory</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 4 | | style="background:#eaeaea" | 4 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be able to configure encrypted access to the LDAP directory, and restrict access at the firewall level | | style="background:#eaeaea" | Candidates should be able to configure encrypted access to the LDAP directory, and restrict access at the firewall level | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave:''' |
* Securing the directory with SSL and TLS | * Securing the directory with SSL and TLS | ||
* Firewall considerations | * Firewall considerations | ||
Line 229: | Line 229: | ||
====<span style="color:navy">303.5 LDAP Server Performance Tuning</span>==== | ====<span style="color:navy">303.5 LDAP Server Performance Tuning</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 2 | | style="background:#eaeaea" | 2 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be capable of measuring the performance of an LDAP server, and tuning configuration directives | | style="background:#eaeaea" | Candidates should be capable of measuring the performance of an LDAP server, and tuning configuration directives | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave''' |
* Measure LDAP performance | * Measure LDAP performance | ||
* Tune software configuration to increase performance | * Tune software configuration to increase performance | ||
Line 246: | Line 246: | ||
====<span style="color:navy">303.6 OpenLDAP Daemon Configuration</span>==== | ====<span style="color:navy">303.6 OpenLDAP Daemon Configuration</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 2 | | style="background:#eaeaea" | 2 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should have knowledge of the common slapd.conf configuration directives, and be familiar with the basic slapd command line options | | style="background:#eaeaea" | Candidates should have knowledge of the common slapd.conf configuration directives, and be familiar with the basic slapd command line options | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave''' |
* slapd.conf configuration directives | * slapd.conf configuration directives | ||
* slapd.conf database definitions | * slapd.conf database definitions | ||
Line 267: | Line 267: | ||
====<span style="color:navy">304.1 Searching the Directory</span>==== | ====<span style="color:navy">304.1 Searching the Directory</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 2 | | style="background:#eaeaea" | 2 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be able to use advanced options for search the LDAP directory | | style="background:#eaeaea" | Candidates should be able to use advanced options for search the LDAP directory | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave:''' |
* Use OpenLDAP search tools with basic options | * Use OpenLDAP search tools with basic options | ||
* Use OpenLDAP search tools with advanced options | * Use OpenLDAP search tools with advanced options | ||
Line 286: | Line 286: | ||
====<span style="color:navy">304.2 LDAP Command Line Tools</span>==== | ====<span style="color:navy">304.2 LDAP Command Line Tools</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 1 | | style="background:#eaeaea" | 1 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be familiar with the OpenLDAP command line tools | | style="background:#eaeaea" | Candidates should be familiar with the OpenLDAP command line tools | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave:''' |
* Use the ldap* tools to access and modify the directory | * Use the ldap* tools to access and modify the directory | ||
* Use the slap* tools to access and modify the directory | * Use the slap* tools to access and modify the directory | ||
Line 308: | Line 308: | ||
====<span style="color:navy">304.3 Whitepages</span>==== | ====<span style="color:navy">304.3 Whitepages</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 1 | | style="background:#eaeaea" | 1 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be able to build and maintain a whitepages service | | style="background:#eaeaea" | Candidates should be able to build and maintain a whitepages service | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave''' |
* Plan whitepages services | * Plan whitepages services | ||
* Configure whitepages services | * Configure whitepages services | ||
Line 326: | Line 326: | ||
====<span style="color:navy">305.1 LDAP Integration with PAM and NSS</span>==== | ====<span style="color:navy">305.1 LDAP Integration with PAM and NSS</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 2 | | style="background:#eaeaea" | 2 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be able to configure PAM and NSS to retrieve information from an LDAP directory | | style="background:#eaeaea" | Candidates should be able to configure PAM and NSS to retrieve information from an LDAP directory | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave''' |
* Configure PAM to use LDAP for authentication | * Configure PAM to use LDAP for authentication | ||
* Configure NSS to retrieve information from LDAP | * Configure NSS to retrieve information from LDAP | ||
Line 345: | Line 345: | ||
====<span style="color:navy">305.2 NIS to LDAP Migration</span>==== | ====<span style="color:navy">305.2 NIS to LDAP Migration</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 1 | | style="background:#eaeaea" | 1 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be able to plan and implement a NIS migration strategy, including a NIS to LDAP gateway | | style="background:#eaeaea" | Candidates should be able to plan and implement a NIS migration strategy, including a NIS to LDAP gateway | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave''' |
* Analyze NIS structure prior to migration to LDAP | * Analyze NIS structure prior to migration to LDAP | ||
* Analyze NIS structure prior to integration with LDAP | * Analyze NIS structure prior to integration with LDAP | ||
Line 364: | Line 364: | ||
====<span style="color:navy">305.3 Integrating LDAP with Unix Services</span>==== | ====<span style="color:navy">305.3 Integrating LDAP with Unix Services</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 1 | | style="background:#eaeaea" | 1 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be able to integrate LDAP authentication with a number of common Unix services | | style="background:#eaeaea" | Candidates should be able to integrate LDAP authentication with a number of common Unix services | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave''' |
* Integrate SSH with LDAP | * Integrate SSH with LDAP | ||
* Integrate FTP with LDAP | * Integrate FTP with LDAP | ||
Line 387: | Line 387: | ||
====<span style="color:navy">305.4 Integrating LDAP with Samba</span>==== | ====<span style="color:navy">305.4 Integrating LDAP with Samba</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 1 | | style="background:#eaeaea" | 1 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be able to integrate LDAP with Samba services | | style="background:#eaeaea" | Candidates should be able to integrate LDAP with Samba services | ||
|} | |} | ||
− | ''' | + | ''' Areas de Conocimiento Clave:''' |
* Migrate from smbpasswd to LDAP | * Migrate from smbpasswd to LDAP | ||
* Understand OpenLDAP Samba schema | * Understand OpenLDAP Samba schema | ||
Line 405: | Line 405: | ||
====<span style="color:navy">305.5 Integrating LDAP with Active Directory</span>==== | ====<span style="color:navy">305.5 Integrating LDAP with Active Directory</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 2 | | style="background:#eaeaea" | 2 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be able to integrate LDAP with Active Directory Services | | style="background:#eaeaea" | Candidates should be able to integrate LDAP with Active Directory Services | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave:''' |
* Kerberos integration with LDAP | * Kerberos integration with LDAP | ||
* Cross platform authentication | * Cross platform authentication | ||
Line 424: | Line 424: | ||
====<span style="color:navy">305.6 Integrating LDAP with Email Services</span>==== | ====<span style="color:navy">305.6 Integrating LDAP with Email Services</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 1 | | style="background:#eaeaea" | 1 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be able to integrate LDAP with email services | | style="background:#eaeaea" | Candidates should be able to integrate LDAP with email services | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave:''' |
* Plan LDAP schema structure for email services | * Plan LDAP schema structure for email services | ||
* Create email attributes in LDAP | * Create email attributes in LDAP | ||
Line 447: | Line 447: | ||
====<span style="color:navy">306.1 Measure Resource Usage</span>==== | ====<span style="color:navy">306.1 Measure Resource Usage</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 4 | | style="background:#eaeaea" | 4 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be able to measure hardware resource and network bandwidth usage | | style="background:#eaeaea" | Candidates should be able to measure hardware resource and network bandwidth usage | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave''' |
* Measure CPU usage | * Measure CPU usage | ||
* Measure memory usage | * Measure memory usage | ||
Line 472: | Line 472: | ||
====<span style="color:navy">306.2 Troubleshoot Resource Problems</span>==== | ====<span style="color:navy">306.2 Troubleshoot Resource Problems</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 4 | | style="background:#eaeaea" | 4 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be able to identify and troubleshoot resource problems | | style="background:#eaeaea" | Candidates should be able to identify and troubleshoot resource problems | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave:''' |
* Match / correlate system symptoms with likely problems | * Match / correlate system symptoms with likely problems | ||
* Identify bottlenecks in a system | * Identify bottlenecks in a system | ||
Line 489: | Line 489: | ||
====<span style="color:navy">306.3 Analyze Demand</span>==== | ====<span style="color:navy">306.3 Analyze Demand</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 2 | | style="background:#eaeaea" | 2 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be able to analyze capacity demands | | style="background:#eaeaea" | Candidates should be able to analyze capacity demands | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave:''' |
* Identify capacity demands | * Identify capacity demands | ||
* Detail capacity needs of programs | * Detail capacity needs of programs | ||
Line 513: | Line 513: | ||
====<span style="color:navy">306.4 Predict Future Resource Needs</span>==== | ====<span style="color:navy">306.4 Predict Future Resource Needs</span>==== | ||
{| | {| | ||
− | | style="background:#dadada" | ''' | + | | style="background:#dadada" | '''Peso''' |
| style="background:#eaeaea" | 1 | | style="background:#eaeaea" | 1 | ||
|- | |- | ||
− | | style="background:#dadada; padding-right:1em" | ''' | + | | style="background:#dadada; padding-right:1em" | '''Descripcion''' |
| style="background:#eaeaea" | Candidates should be able to monitor resource usage to predict future resource needs | | style="background:#eaeaea" | Candidates should be able to monitor resource usage to predict future resource needs | ||
|} | |} | ||
− | ''' | + | '''Areas de Conocimiento Clave''' |
* Predict capacity break point of a configuration | * Predict capacity break point of a configuration | ||
* Observe growth rate of capacity usage | * Observe growth rate of capacity usage |
Revision as of 00:55, 6 July 2011
Contents
- 1 Introducción
- 2 Información de la Versión
- 3 Apéndice
- 4 Traducción de Objetivos
- 5 Objectives
Introducción
La capacidad de planificación es el arte y la ciencia de no quedarse sin recursos en el futuro previsible. A menudo se hace de manera informal, mediante la medición de los recursos que un programa necesita, normalmente después de haberse quedado sin algo.
Si usted hace una tabla de la cantidad de CPU, memoria y E / S de ancho de banda que un programa necesita para hacer alguna unidad de trabajo, se puede estimar cuánto va a necesitar en alguna carga mayor en el futuro. Alternativamente, puede utilizar las mediciones para determinar una máquina nueva para el programa, o para estimar cuán grande tendrá que ser la máquina necesaria para consolidar sus programas y otros.
Estimaciones informales de hojas de cálculo son a menudo suficientes para calculos y la planificación futura, pero no tienen ninguna garantía de exactitud y no dicen:
- En que carga el programa se sobrecarga, ni
Para ello, utilice uno de los programas que resolver el problema. Hay productos comerciales para hacerlo en Linux, pero por lo menos exite un un solver de colas de red (queuing network solver), Perl:: PDQ por Neil Gunther. Estos generarn modelos matemáticos adecuados, así que usted puede predecir el desempeño del programa bajo carga, y calcular la caída en el rendimiento mientras el programa se sobrecarga.
Información de la Versión
Estos son los objetivos versión 1.0.1.
Apéndice
Apéndice ( 1ro de Abril de 2010)
- C++ es C en desarollo
Traducción de Objetivos
Las siguientes traducciones de los objetivos se encuentran disponibles en esta wiki:
- English
- Spanish
Objectives
Topic 301: Conceptos, Arquitectura y Diseño
301.1 LDAP Concepts and Architecture
Peso | 3 |
Descripcion | Candidates should be familiar with LDAP and X.500 concepts |
Areas de Conocimiento Clave:
- LDAP and X.500 technical specification
- Attribute definitions
- Directory namespaces
- Distinguished names
- LDAP Data Interchange Format
- Meta-directories
- Changetype operations
The following is a partial list of the used files, terms and utilities:
- LDIF
- Meta-directory
- changetype
- X.500
- /var/lib/ldap/*
301.2 Directory Design
Peso | 2 |
Descripcion | Candidates should be able to design an implement an LDAP directory, while planning an appropriate Directory Information Tree to avoid redundancy. Candidates should have an understanding of the types of data which are appropriate for storage in an LDAP directory |
Areas de Conocimiento Clave:
- Define LDAP directory content
- Organize directory
- Planning appropriate Directory Information Trees
The following is a partial list of the used files, terms and utilities:
- Class of Service
- Directory Information Tree
- Distinguished name
- Container
301.3 Schemas
Peso | 3 |
Descripcion | Candidates should be familiar with schema concepts, and the base schema files included with an OpenLDAP installation |
Areas de Conocimiento Clave:
- LDAP schema concepts
- Create and modify schemas
- Attribute and object class syntax
The following is a partial list of the used files, terms and utilities:
- Distributes schema
- Extended schema
- Object Identifiers
- /etc/ldap/schema/*
- Object class
- Attribute
- include directive
Topic 302: Installation and Development
302.1 Compiling and Installing OpenLDAP
Peso | 3 |
Descripcion | Candidates should be able to compile and install OpenLDAP from source and from packages |
Areas de Conocimiento Clave:
- Compile and configure OpenLDAP from source
- Knowledge of OpenLDAP backend databases
- Manage OpenLDAP daemons
- Troubleshoot errors during installation
The following is a partial list of the used files, terms and utilities:
- make
- gpg
- rpm
- dpkg
- bdb
- slapd
- slurpd
302.2 Developing for LDAP with Perl and C
Peso | 1 |
Descripcion | Candidates should be able to write basic Perl scripts to interact with an LDAP directory |
Areas de Conocimiento Clave:
- Syntax of Perl's Net::LDAP module
- Write Perl scripts to bind, search, and modify directories
The following is a partial list of the used files, terms and utilities:
- Net::LDAP
- using Perl with Net::LDAP
- using C with libldap
Topic 303: Configuration
303.1 placeholder
Peso | 0 |
Descripcion | This objective dropped due to JTA results |
Areas de Conocimiento Clave:
- N/A
The following is a partial list of the used files, terms and utilities:
- N/A
303.2 Access Control Lists in LDAP
Peso | 2 |
Descripcion | Candidates should be able to plan and implement access control lists |
Areas de Conocimiento Clave:
- Plan LDAP access control lists
- Grant and revoke LDAP access permissions
- Access control syntax
The following is a partial list of the used files, terms and utilities:
- ACL
- slapd.conf
- anonymous
- users
- self
- none
- auth
- compare
- search
- read
- write
303.3 LDAP Replication
Peso | 5 |
Descripcion | Candidates should be familiar with the various replication strategies available with OpenLDAP |
Areas de Conocimiento Clave
- Replication concepts
- Configure OpenLDAP replication
- Execute and manage slurpd
- Analyze replication log files
- Understand replica hubs
- LDAP referrals
- LDAP sync replication
The following is a partial list of the used files, terms and utilities:
- slurpd
- slapd.conf
- master / slave server
- consumer
- replica hub
- one-shot mode
- referral
- syncrepl
- pull-based / push-based synchronization
- refreshOnly and refreshAndPersist
- replog
303.4 Securing the Directory
Peso | 4 |
Descripcion | Candidates should be able to configure encrypted access to the LDAP directory, and restrict access at the firewall level |
Areas de Conocimiento Clave:
- Securing the directory with SSL and TLS
- Firewall considerations
- Unauthenticated access methods
- User / password authentication methods
- Maintanence of SASL user DB
- Client / server certificates
The following is a partial list of the used files, terms and utilities:
- SSL / TLS
- Security Strength Factors (SSF)
- SASL
- proxy authorization
- StartTLS
- slapd.conf
- iptables
303.5 LDAP Server Performance Tuning
Peso | 2 |
Descripcion | Candidates should be capable of measuring the performance of an LDAP server, and tuning configuration directives |
Areas de Conocimiento Clave
- Measure LDAP performance
- Tune software configuration to increase performance
- Understand indexes
The following is a partial list of the used files, terms and utilities:
- index
- slapd.conf
- DB_CONFIG
303.6 OpenLDAP Daemon Configuration
Peso | 2 |
Descripcion | Candidates should have knowledge of the common slapd.conf configuration directives, and be familiar with the basic slapd command line options |
Areas de Conocimiento Clave
- slapd.conf configuration directives
- slapd.conf database definitions
- slapd and its command line options
- Analyze slapd log files
The following is a partial list of the used files, terms and utilities:
- slapd.conf
- slapd
- /var/lib/ldap/*
- loglevel
Topic 304: Usage
304.1 Searching the Directory
Peso | 2 |
Descripcion | Candidates should be able to use advanced options for search the LDAP directory |
Areas de Conocimiento Clave:
- Use OpenLDAP search tools with basic options
- Use OpenLDAP search tools with advanced options
- Optimize LDAP search queries
- Knowledge of search filters and their syntax
The following is a partial list of the used files, terms and utilities:
- ldapsearch
- index
- search filter syntax
- slapd.conf
304.2 LDAP Command Line Tools
Peso | 1 |
Descripcion | Candidates should be familiar with the OpenLDAP command line tools |
Areas de Conocimiento Clave:
- Use the ldap* tools to access and modify the directory
- Use the slap* tools to access and modify the directory
The following is a partial list of the used files, terms and utilities:
- ldap.conf
- ldapsearch
- ldapadd
- ldapmodify
- ldapdelete
- ldapmodrdn
- slapindex
- slapadd
- slapcat
304.3 Whitepages
Peso | 1 |
Descripcion | Candidates should be able to build and maintain a whitepages service |
Areas de Conocimiento Clave
- Plan whitepages services
- Configure whitepages services
- Configure clients to retrieve data from whitepages services
The following is a partial list of the used files, terms and utilities:
- whitepages
- Outlook
Topic 305: Integration and Migration
305.1 LDAP Integration with PAM and NSS
Peso | 2 |
Descripcion | Candidates should be able to configure PAM and NSS to retrieve information from an LDAP directory |
Areas de Conocimiento Clave
- Configure PAM to use LDAP for authentication
- Configure NSS to retrieve information from LDAP
- Configure PAM modules in various Unix environments
The following is a partial list of the used files, terms and utilities:
- PAM
- NSS
- /etc/pam.d/*
- /etc/nsswitch.conf
305.2 NIS to LDAP Migration
Peso | 1 |
Descripcion | Candidates should be able to plan and implement a NIS migration strategy, including a NIS to LDAP gateway |
Areas de Conocimiento Clave
- Analyze NIS structure prior to migration to LDAP
- Analyze NIS structure prior to integration with LDAP
- Automate NIS to LDAP migration
- Create a NIS to LDAP gateway
The following is a partial list of the used files, terms and utilities:
- NIS
- NIS to LDAP gateway
- slapd.conf
- /etc/yp/*
305.3 Integrating LDAP with Unix Services
Peso | 1 |
Descripcion | Candidates should be able to integrate LDAP authentication with a number of common Unix services |
Areas de Conocimiento Clave
- Integrate SSH with LDAP
- Integrate FTP with LDAP
- Integrate HTTP with LDAP
- Integrate FreeRADIUS with LDAP
- Integrate print services with LDAP
The following is a partial list of the used files, terms and utilities:
- sshd.conf
- ftp
- httpd.conf
- radiusd.conf
- cupsd.conf
- ldap.conf
305.4 Integrating LDAP with Samba
Peso | 1 |
Descripcion | Candidates should be able to integrate LDAP with Samba services |
Areas de Conocimiento Clave:
- Migrate from smbpasswd to LDAP
- Understand OpenLDAP Samba schema
- Understand LDAP as a Samba password backend
The following is a partial list of the used files, terms and utilities:
- smb.conf
- smbpasswd
- samba3.schema
- slapd.conf
305.5 Integrating LDAP with Active Directory
Peso | 2 |
Descripcion | Candidates should be able to integrate LDAP with Active Directory Services |
Areas de Conocimiento Clave:
- Kerberos integration with LDAP
- Cross platform authentication
- Single sign-on concepts
- Integration and compatibility limitations between OpenLDAP and Active Directory
The following is a partial list of the used files, terms and utilities:
- Kerberos
- Active Directory
- single sign-on
- DNS
305.6 Integrating LDAP with Email Services
Peso | 1 |
Descripcion | Candidates should be able to integrate LDAP with email services |
Areas de Conocimiento Clave:
- Plan LDAP schema structure for email services
- Create email attributes in LDAP
- Integrate Postfix with LDAP
- Integrate Sendmail with LDAP
The following is a partial list of the used files, terms and utilities:
- Postfix
- Sendmail
- schema
- SASL
- POP
- IMAP
Topic 306: Capacity Planning
306.1 Measure Resource Usage
Peso | 4 |
Descripcion | Candidates should be able to measure hardware resource and network bandwidth usage |
Areas de Conocimiento Clave
- Measure CPU usage
- Measure memory usage
- Measure disk I/O
- Measure network I/O
- Measure firewalling and routing throughput
- Map client bandwidth usage
The following is a partial list of the used files, terms and utilities:
- iostat
- vmstat
- pstree
- w
- lsof
- top
- uptime
- sar
306.2 Troubleshoot Resource Problems
Peso | 4 |
Descripcion | Candidates should be able to identify and troubleshoot resource problems |
Areas de Conocimiento Clave:
- Match / correlate system symptoms with likely problems
- Identify bottlenecks in a system
The following is a partial list of the used files, terms and utilities:
- swap
- processes blocked on I/O
- blocks in
- blocks out
306.3 Analyze Demand
Peso | 2 |
Descripcion | Candidates should be able to analyze capacity demands |
Areas de Conocimiento Clave:
- Identify capacity demands
- Detail capacity needs of programs
- Determine CPU / memory needs of programs
- Assemble program needs into a complete analysis
The following is a partial list of the used files, terms and utilities:
- PDQ
- CPU usage
- memory usage
- appropriate measurement time
- trend
- model
- what-if
- validate
- performance equation
306.4 Predict Future Resource Needs
Peso | 1 |
Descripcion | Candidates should be able to monitor resource usage to predict future resource needs |
Areas de Conocimiento Clave
- Predict capacity break point of a configuration
- Observe growth rate of capacity usage
- Graph the trend of capacity usage
The following is a partial list of the used files, terms and utilities:
- diagnose
- predict growth
- average
- resource exhaustion