* Dave Miner (dminer at opensolaris.org) wrote: > On 02/ 9/10 01:21 PM, Virginia Wray wrote: > ... > >http://hub.opensolaris.org/bin/view/Project+caiman/Logging > > > > Thanks for starting the review early on. Some comments: > > I'm not sure that I understand the difference between the bulleted > list in section 3 (which appear to be requirements) and section 5, > Design Requirements. Can you help differentiate? > > Section 3: Don't understand the last requirement in the bulleted > list - "... without the overhead of output". What does this mean? > > Section 6: Are the interfaces here meant to be Python interfaces, C > interfaces, or ? Going a bit further, I don't get the purpose of > Find_Component or Register_Component. Finally, won't we also need > interfaces for locating and displaying logs (how would the GUI > installer at least replicate what it currently offers in displaying > the log)? > > Section 7: I think some elaboration on the networking scenarios that > are expected to work is in order. Are you intending that remote > logging could cross a firewall? If so, what are the technologies > that are used, and what server-side support is required?
I agree with this. It would be nice to know what "logging to a remote instance" is going to look like (especially for VMC). Will there be some sort of "logging server application" that will have to run on the remote location to process remote logging requests or some other mechanism? Will each user that's interested in remote logging have to provide this application or are we going to provide something? For VMC, currently there is no way to easily monitor the progress of the virtual machine installation since the install is happening inside of VirtualBox via the Automated Installer underneath Distribution Constructor. Distribution Constructor also can't act upon any installation failures that occur inside the VM since it has no insight into what's going on (it's a cross your fingers and hope everything goes to plan. If the VM shuts itself down, assume that the Install was a success which is certainly not guaranteed to be true). Presumably, a remote logging feature would allow the AI invocation running inside of VirtualBox to send it's logs "up the stack" as it were so that installation issues can be dealt with in Distribution Constructor as well as have a record in the DC logs of how the actual VM installation went. Is this design going to allow for such a thing? Thanks, -- Glenn
