Sanjay and Ginnie, Thanks for the responses.
The only question still in my mind is whether or not we need multiple webservers to accomplish the logging and install. It seems to me that we might want to allow for the ability to have multiple log servers and multiple install servers, however, by default we should have a single webserver doing both. Does that make sense? Thanks, John On 03/14/10 11:13 AM, sanjay nadkarni wrote: > On 03/12/10 05:51 PM, Virginia Wray wrote: >> Hi John - >> >> Thanks for your feedback. See my responses inline... >> ginnie >> >> >> On 03/12/10 13:37, John Fischer wrote: >>> Ginnie, >>> >>> Good presentation yesterday. You answered several questions that I had >>> about the specification document you created. Some still remain which >>> is why I am emailing you. >>> >>> If I am reading the document correctly the remote client initiates when >>> the log is stored on the server. This could be either post execution >>> or with each step of the install. Is that correct? (sections 7/8-ish) >> The remote client actually initiates when the client boots. Logging >> initiates once the >> logger has successfully created an http handle and has been able to >> make a connection >> to the logging server. As a log message is generated, it is sent to >> the remote log location. >> The reason for doing it this way is so that if the execution fails, we >> won't lose the logging info. >>> >>> In the Server Side section (8.2) the document states that there will >>> be 2 servers--1 for install and 1 for logging. Why not simply have a >>> single server which handles both? Or at least the install server >>> should be configurable to handle the logging. >> Are you talking about physical machines? There is only one machine >> that is >> acting as a server for both. > Installadm will be enhanced to setup up logging when an install service > is created. The idea is to make this seamless. >>> >>> I notice that there are several references to /etc/netboot or >>> logserver_rootdir. Will these directories be an SMF property which >>> is configurable and can be pulled from SMF within an application? >>> (i.e., not hard coded) >> The /net/netboot references come from the installadm design doc that >> Dave Miner >> has authored. I don't know how he will be managing it. I'm leveraging >> what he >> will already have in place. >>> >>> It looks like the project will be using multicast DNS. Will the project >>> be using dns-sd or a new Python module like pyBonjour? Architecturally >>> we should not use the output from dns-sd because it is labeled as >>> Not An Interface and might change out from under us. >> We talked about mDNS. We aren't using that. We are hoping to use the >> WANboot >> functionality for both SPARC and x86 which has a different type of >> implementation. > mDNS has subnet limitations which we want to avoid hence it was > considered and then dropped. > > -Sanjay > >>> >>> Thanks, >>> >>> John >> >
