Hi Ginnie, My comments/questions inline...
> Hi Sarah > > thanks for the review. See my comments inline. > ginnie >> >> >> Hi Ginnie, >> >> This is looking really good. I do have some comments and questions: >> >> Section 8: >> Remote Logging: >> -It isn't clear to me exactly how this would work. You indicate that >> when a client boots it would be able to setup remote logging, >> possibly via wanboot.conf. How would a client get a wanboot.conf file >> if it was booted from media? Does remote logging mean network boot? I >> don't think that is what you mean, so can you clarify this a bit more? > The context that we've been looking at has been AI and VMC. The plan > for both is to make use of the wanboot.conf file, AI via the network > and VMC via including the wanboot.conf file on the AI image it uses. > The wanboot method enables us to log across subnets. > > Bootable AI could be extended to have an option to do remote logging. > For other media installs, we would have to take a look at it. If wanboot.conf is going to be used, and network booting isn?t required, then we need to specify how other clients utilize wanboot logging. I think for consumers of logging this information is important. >> -You responded to John F with: >> >Installadm will be enhanced to setup up logging when an install service >> >is created. The idea is to make this seamless. >> >> It looks as if you are proposing to set a logging service up >> automatically with the setup of an AI service. Why would we do that >> by default? Is it expected that AI clients will automatically log >> remotely? > That's the design choice Dave, Sanjay and I made. It seems like less > configuration overhead to accomplish both in one step. It is available > and in place if the AI clients invoke remote logging.bt So, maybe I am not understanding something.. and if so, feel free to tell me :-). The logging service that is going to be setup with installadm, does that restrict the remote logging location to be the install server? Can you describe how the client would set the location of the remote log? >> If that is the thought, what are the implications from a security >> point of view to our customers if this is the choice. > From my reading of wanboot, and I admit that I'm still learning about > it, there are secure wanboot installation configuration set ups that > are available. I would like us to be sure that we understand there are no security issues with automatically setting up this logging service. If you could add this data to the doc when you have it that would be great. >> -General question.. what if the user has a webserver setup somewhere >> but they don't want to setup the wanboot logging server? Couldn't we >> just write the file remotely to the server that is setup already? >> Perhaps I don't understand exactly how the wanboot logging server >> helps or what it provides exactly. > The wanboot.conf file includes the url of the remote server, so that > the client knows where to log to. The logging service will log where > it is told to log. It just needs the location information to log to. > That's one reason I left the init_handler() arguments as kwargs in > 11.2. I thought it would be good to leave the options open. >> Section 8.1 Client Side >> -It might be good for the client to check network connectivity before >> making a request to add the http handler. > Ok. I'll update the order of the list. >> -Also, since logging goes through the engine, would the engine >> connect to the remote logging service as opposed to the client? And >> error if it couldn't add the handler? > In order for the http handler to be added, it requires the url as a > parameter. The engine will have to query the network and get the > wanboot.conf file. The > url is located in the wanboot.conf file. Then it will pass that info > to the logger on the system where the engine is running. There is no > logging module on the server side. The logger sets up and opens the > handler, passes the preamble to verify that information can be passed. > Then that handler waits for information to be passed. It's passed via > http. On the receiving end there is a CGI script that deposits the > information into the default file location. So, I am not sure you answer answers my question :-). Are you saying the application instantiates remote logging via the engine, with add_handler()? If so, that's fine, just not clear to me. thanks, sarah *****
