doc/packaging/whitepaper.html - view

File: [LON-CAPA] / doc / packaging / Attic / whitepaper.html
Revision 1.1: download - view: text, annotated - select for diffs
Sat Sep 30 13:48:03 2000 UTC (23 years, 7 months ago) by harris41
Branches: MAIN
CVS tags: version_0_4, stable_2002_spring, stable_2002_july, stable_2002_april, stable_2001_fall, STABLE, HEAD

the whole nine yards of packaging.  I (Scott) talk about internal source code
handling, external source code handling, developer communication, and
operating system/CD building info.

<HTML> <HEAD> <TITLE>Packaging, the whole nine yards, White Paper</TITLE> </HEAD> <BODY BGCOLOR=#FFFFFF> <H1>Packaging, the whole nine yards, White Paper</H1> This document is in doc/packaging/whitepaper.html. First generated by Scott Harrison, September 29, 2000. This document is an overview of what needs to be considered in terms of a software development process, from source code creation to CD installation. Suffice it to say, if any of these issues are not resolved, there really is not a sustainable packaging effort that can continue in the future. Shown below is a list of needs and solutions. Hopefully this motivates dialogue, suggestions, and some level of common awareness as to what has been going on. Perhaps there is some disagreement, but hopefully this is somewhat of good start on all of this.. shrug. This is meant to focus and clarify things, not confuse them. I think many of these things have been worked out on many different fronts. However, the name of the game now is to make sure things are going forward to be finished without generating new cans of worms. <CAPTION>Packaging needs, suggested solutions, current status, what remains to do</CAPTION> <TABLE BORDER=2> <TR BGCOLOR=#000000> <TH>Need</TH> <TH>Solution</TH> <TH>Status</TH> <TH>To do</TH> <TR BGCOLOR=#DDDDDD> <TD COLSPAN=4>Internal Source Code The code created and overseen by the development team. Generally as relates to code that implements the LON-CAPA network, instructional content handling, and student evaluation.</TD> <TR> <TD>Internal source code submission</TD> <TD>CVS</TD> <TD>implemented on zaphod</TD> <TD>Eventually port to www.lon-capa.org. Also need to specify process by which users are added/removed from CVS-submission group</TD> </TR> <TR> <TD>Internal source code distribution</TD> <TD>CVS</TD> <TD>implemented on zaphod</TD> <TD>Eventually port to www.lon-capa.org. Need to distribute two versions: LAST-WORKING; and MOST-UP-TO-DATE</TD> </TR> <TR> <TD>Internal source code versioning</TD> <TD>CVS</TD> <TD>implemented on zaphod</TD> <TD>Eventually port to www.lon-capa.org.</TD> </TR> <TR> <TD>Internal source code building</TD> <TD>CVS</TD> <TD>a number of "commands", "Makefile" scripts written with some documentation</TD> <TD>Have a working and understandable set of "commands", "Makefile" scripts written with some documentation. Installation should be done through an RPM LON-CAPA-base.rpm should be generated, and be the basis for an install. Other OS-specific install options could be considered (ie Debian). </TD> </TR> <TR BGCOLOR=#DDDDDD> <TD COLSPAN=4>External Source Code The code created and development overseen by others. Generally as relates to "modular" necessary software packages like kerberos and MySQL, as well as multiple perl modules</TD> </TR> <TR> <TD>External source code distribution</TD> <TD>Anonymous FTP site (www.lon-capa.org)</TD> <TD>External packages have been gathered into directory as source tarballs</TD> <TD>Where/how can I post packages?</TD> </TR> <TR> <TD>External source code submission</TD> <TD>someone with access to www.lon-capa.org</TD> <TD>not done</TD> <TD>Who should do this? shall we do this soon?</TD> </TR> <TR> <TD>External source code versioning</TD> <TD>Use the most up-to-date version that works with LON-CAPA.</TD> <TD>Currently have the most up-to-date versions.</TD> <TD>How often should we update available external source code versions?</TD> </TR> <TR> <TD>External source code building</TD> <TD>Have a README for each software bundle and an automated build script. Generate an RPM.</TD> <TD>RPMs generated. README's and build scripts are currently dispersed in lon-capa mail archives.</TD> <TD>Post README, RPMs, and build scripts on anonymous FTP server.</TD> </TR> <TR BGCOLOR=#DDDDDD> <TD COLSPAN=4>Communication between developers History has shown that there are a host of issues that occur when integrating software applications together with LON-CAPA and the linux distribution. As with most software development projects, the various questions and solutions must not be lost, and there needs to be a system for passing communications between interested developers.</TD> </TR> <TR> <TD>Communication distribution</TD> <TD>Mailman, list@lon-capa.org</TD> <TD>There are archives (including Scott-created search engine) currently for lon-capa@hobbes.lite.msu.edu.</TD> <TD>Need to port to lon-capa.org.</TD> </TR> <TR BGCOLOR=#DDDDDD> <TD COLSPAN=4>Operating System and Installation CD generation The components and installation details of LON-CAPA plus linux operating system to be made available. </TD> </TR> <TR> <TD>Customized Redhat CD image</TD> <TD>Specify RPM sets; synchronize installation indices of RPM sets.</TD> <TD>RPM sets have been well specified; both for LON-CAPA runtime systems, and LON-CAPA development systems. CD images have been compiled and burned. I have a number of HOW-TO's I wrote available on spock.lite.msu.edu web site and CVS.</TD> <TD>Need to post RPM sets to be accessible as updated versions from lon-capa.org. Need to automate and better document CD image generation from internal source, external source, and "original" Redhat CD image.</TD> </TR> <TR> <TD>Installation, Reconfiguration, Updating Software</TD> <TD>Defined interfaces for both text-based and graphical sessions. Must be scripted together to synchronize entire system.</TD> <TD>Interfaces are defined (see CVS repository doc/anaconda_interfaces). Much of the scripting is in place.</TD> <TD>Significantly buggy. <IMG SRC="bug.gif">. Also need some solid documentation.</TD> </TR> <TR> <TD>Operating System HOW-TO & Mechanics</TD> <TD>Specify configuration details about various system services (netatalk, samba, nfs). Have auxiliary scripts available (setuid password synchronization script).</TD> <TD>Much of how to do this is mentioned in the mail archives.</TD> <TD>Need to do it. Also needs to be officially documented and posted on www.lon-capa.org.</TD> </TR> <TR> <TD>Boot everything and continuously monitor: loncron and /etc/rc.d/init.d/</TD> <TD>Run loncron under some random cron scenario (25% chance of being run every hour?) Have all internal package, external package, and operating system services start automatically upon boot (/etc/rc.d/init.d; chkconfig).</TD> <TD>Much of how to do this is mentioned in the mail archives.</TD> <TD>Need to do it. Also need to officially document and post on www.lon-capa.org.</TD> </TR> </TABLE> </BODY> </HTML>