Hi - I've been thinking more about the problem statement. I would like to broaden and hone it at the same time. Here is what I've come up with, and I welcome any feedback:
"To provide a mechanism for delivering the AI manifest and install image to the AI client which is scalable, delivers high performance, and provides a good user experience." I've used the term mechanism instead of webserver so that we leave options open. I think "delivers high performance" is a little vague, but I think that can be solved by defining what high performance means. I was talking with Sanjay, and he asked me a couple of questions - 1. For what we are doing, is it worth having an entire webserver to do this? 2. In the user environment, is the data that we are dealing with going to be static or dynamic? thanks, ginnie On 05/06/09 18:53, Sundar Yamunachari wrote: > Hi, > > The meeting minutes are posted at > http://www.opensolaris.org/os/project/caiman/auto_install/AI_mtg/Minutes/web_server_meeting_minutes_May_06_2009 > > > > Thanks, > Sundar > > Sundar Yamunachari wrote: >> Hi, >> We will meet at 3:00 p.m PT to discuss web server simplification >> for Automated Installer. The concall information is as follows: >> >> Wed, 5/6 >> Duration: 30 minutes >> 3 p.m PT/4:00 p.m MT/ 6:00 p.m ET >> >> USA Toll-Free: 866-545-5227 >> USA Caller Paid/International Toll: 215-446-3648 >> ACCESS CODE: 6345177 >> >> Thanks, >> Sundar >> >> Sundar Yamunachari wrote: >>> Problem(s): >>> >>> 1. The Automated Installer currently has two web servers. The >>> first one is an Apache web server running on a fixed port to serve >>> the clients programs and tools (solaris.zlib and solarismisc.zlib) >>> required for automated installer.The second one is a light weight >>> web server based on CherryPy and used for serving install manifests >>> to the AI clients. Having two web servers confuses the the users. >>> >>> 2. For each install service, the server tools creates a new AI >>> web server (CherryPy based) on a separate port. If there are number >>> of install services running on a system, we could have quite a few >>> AI web server processes running on the system. Finding the port >>> numbers of a particular web server and debugging any problems >>> becomes cumbersome. >>> >>> What we want to see: >>> >>> Have a single web server running on a fewer ports (one should be >>> ideal) serving both install files and AI manifests. >>> >>> Possible solutions: >>> >>> 1. Use CherryPy web server to serve both AI install files and AI >>> manifests. >>> Advantages: >>> - Flexible for adding the features we need. >>> - Light-weight (Use only the code we need) >>> >>> Disadvantages: >>> - We have to maintain the code >>> - We have to create packages for other operating systems >>> (Solaris 10 and Linux) >>> - Is it scalable? >>> - Features may need to be added >>> >>> 2. Use Apache to serve both AI install files and AI manifests. >>> Advantages: >>> - The code is reliable and been there for a while >>> - Packages are available for other operating systems (Solaris >>> 10 and Linux) >>> - Configuration can be tuned to provide a scalable install server >>> - Modules are available for most of the useful tasks >>> >>> Disadvantages: >>> - Lose some flexibility - If the required feature is not >>> available, then it becomes little tedious. >>> >>> 3. Use a different web server other than Apache and CherryPy >>> - Need to be investigated. >>> >>> >>> Next steps: >>> >>> 1. Investigate whether Apache web server can do all the tasks >>> required to serve AI manifest to the clients? What is the risk? >>> 2. Investigate whether AI web server can do the following: >>> - The tasks to serve AI install programs and tools to the >>> clients (allow directory traversing) >>> - To run cgi-bin programs (needed for SPARC wanboot-cgi) >>> - Creating SVR4 and Linux packaging needed for running on >>> other operating systems >>> 3. Is there any other web server we want to look at? >>> _______________________________________________ >>> caiman-discuss mailing list >>> caiman-discuss at opensolaris.org >>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >> >> > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss -- Ginnie
