Attached are some preliminary objectives for Web Services. There is a
*lot* of content we must address here for Apache, and thus these
definitely need flushed out. I'd rather not have just one objective to
cover all the apache related issues, so I attempted to organize into two,
server install/configuration specifics and customization, options, and
such like that. (Though I didn't do a good job, and it needs
re-addressing).
Please review, provide technical detail, and otherwise comment on these.
Again, I'd like us to start filtering out the ambiguity of these
objectives and fill in the gaps.
Thanks.
-Kara
---------- Forwarded message ----------
Date: Mon, 4 Jun 2001 12:45:34 -0500 (CDT)
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Preliminary Kernel Objectives
In order to assist in speedy objective development, I've tried to start
developing some preliminary objectives for our tasks, based on the most
recent organizational structure. (I've only received one response to the
last thread on organizing!)
The objectives are definitely not complete in current form, nor are they
the concrete foundation we're forced to work with. The tasks are our
foundation (also attached). The goal is to create objectives which cover
these tasks and fill in the technical gaps and details.
Our Level 1 objectives
(http://www.lpi.org/http://www.lpi.org/p-obj-101.html and p-obj-102.html)
should provide a good outline for what form and style objectives should be
written in. I've modified slightly (including bullets for specified files
and tools covered) but the rest should be developed in the same fashion as
the current Level 1 objectives. There's no need to obsess over this step
at this stage, as I plan to have this completed in a stage of formal
review.
I would like either comments, changes, and additions as well as assistance
completing (technically) the objectives I've posted; your comments and
submissions for replacement or additional objectives; and your comments
for supplementary objectives (if any).
Please begin by reviewing the current objectives for Level 1 at the URLs
listed above. Next review the task file for this group. Finally, review
the preliminary objectives file and comment. Please note that the
preliminary objectives file associates the current task numbers with the
affiliated objective. Please continue to refer to these task IDs when
commenting, reorganizing, etc. objectives.
I will continue submitting preliminary objective files for various
categories today and tomorrow. I would like good discussion and progress
toward finalizing objectives in progress by Wednesday. By Friday, those of
you interested in the contract positions to finalize objectives should be
able to begin review. By next week, I would like to publish our objectives
for public review and begin collecting preliminary items.
The next 10 days are going to be crazy, and I greatly appreciate your time
and dedication to development. We are moving extremely quickly, and
everyone is very excited about our current developments!
Please contact me if you are available 6/8 - 6/12 for contract objective
review and development. I apologize that this will encompass a weekend,
but it is necessary for succeeding with our current development schedule.
Slots are filling for the Item Writing session planned for the week of
June 18. If you had hoped to participate in this event, please contact me
to discuss availability, expenses, etc. It is likely that a two team
approach (6/18 - 6/20, 6/20 - 6/22) will be used, allowing for flexible
travel arrangements.
--
Kara Pritchard Phone: 618-398-7360
Author, RHCE Exam Cram
Director of Exam Development http://www.lpi.org/
Site Manager http://www.LinuxUsersGroups.org/
--
3.6.1 Monitor Apache load and performance by reading Apache's access.log
file.
3.6.2 Set user restrictions on directories by editing .htaccess files in the
web directories.
3.6.3 Install and configure mod_perl in Apache
3.6.4 Install and configure PHP3 to work with Apache.
3.6.6 Set up user authentication under Apache by enabling mod_auth and
creating htpasswd and htgroup files
3.6.7 Install a new module in Apache.
3.6.10 Add virtual hosts for the apache webserver in httpd.conf
3.6.11 Create a SSL certificate for Apache
3.6.12 Add SSL definitions to Apache's httpd.conf
3.6.13 Set up the maximum number of requests with MaxKeepAliveRequests
3.6.14 Configure the minimum and maximum numbers of spare servers waiting for
requests with MinSpareServers and MaxSpareServers in httpd.conf
3.6.15 Set up the number of servers to start with StartServers in httpd.conf
3.6.16 Determine the maximum number of httpd servers to run with MaxClients
in httpd.conf
3.6.17 Add Redirect statements to the Apache config file httpd.conf
3.19.1 Edit the "acl" and "http_access" entries in squid.conf to implement an
access policy for Squid.
3.19.2 lo Install and set up an authenticate_program on Squid to implement
user-level access, and implement this using "acl" and "http_access".
3.19.3 Optimize Squid by editing /etc/squid.conf to change memory usage
requirements and responsiveness.
Web Services
[3.6.1, 3.6.2, 3.6.3, 3.6.4, 3.6.6, 3.6.7, 3.6.13, 3.6.14, 3.6.15, 3.6.16
Obj : Implementing a Web Server
Install and configure an Apache web server. Includes monitoring
Apache load and performance, restricting user access, configuring
mod_perl and PHP support, setting up user authentication, configuring
options such as maximum requests, minimum and maximum servers, and
clients in Apache's configuration files.
Includes files and tools such as:
* access.log
* .htaccess
* httpd.conf
* mod_auth
* htpasswd
* htgroup
*
[3.6.10, 3.6.11, 3.6.12, 3.6.17
Obj : Maintaining a Web Server
Configure Apache to use virtual hosts for websites without dedicated
IP addresses. Create an SSL certificate for Apache and define SSL
definitions in Apache's configuration files. Customize file access
by implementing redirect statements in Apache's configuration files.
Includes files and tools such as:
* httpd.conf
*
[3.19.1, 3.19.2, 3.19.3
Obj : Implementing a Proxy Server
Install and configure a proxy server using squid. Includes
implementing access policies, authentication, and utilizing memory
usage.
Includes files and tools such as:
* squid.conf
* acl
* http_access
*
