deepti vaidya wrote: > On a procedural note, this "Fast Track" was filed on November 5th and has gone through many rounds of questions and now 2.5 months later still has some of the same questions open.
I'm not particularly inclined to derail it because I suspect all the answers are straighforward, but it shouldn't take this long to get them. If this case is to ever close, the project team needs to put in a bit of effort into fleshing out the details. > >jv01: The spec lists every *.cgi as a public interface, which might be > > the case but more likely is not. Is all this webapp > > implementation really a public interface? Isn't some or most of > > that Project Private implementation detail? If not, why not? > > cgi files are used by web server. They are exported interfaces to apache > webserver. > Since it is used by webserver, it is public interface.. That's not what public interface means. Are the *.cgi scripts public interfaces for users/customers? To give a simple example, if your app has a cgi called "balance.cgi" and you intend to document to customers that you will support them for writing scripts which retrieve the uri "/balance.cgi?account=123" then both the script name "balance.cgi" and the parameter "account" are public interfaces. If you don't intend to document and support some/all the cgi's for this kind of usage then they are not public interfaces. Maybe some subset is documented by name? > >jv02: What do the CLIs do? Do they have any options? > > > /usr/bin/nagios > > > /usr/bin/nagiostats > > These are CLI executables with options. So, where are these options documented? Do all the options have the same stability? In Jan.6th email John asked for manpages, which will presumably document the CLI options, but there are no manpages yet in the case dir or email trail. > >jv03: The config files are not an interface? That may be true (if > > customers are not supposed to configure things themselves), but > > seems... odd. What goes there and how is it used? > > > > > Not An Interface > > > -------------------- > > > /etc/nagios -- cfg files are copied here > > > /etc/nagios/objects -- cfg files are copied here > > The cfg files contain the path of different files, eg., path of log > file, path of resource file, path of lock file etc... It is not manually > written by user. These files get created while compiling the package at > the package creation time. So, if these files are generated at compile-time and not modified afterwards, why are they under /etc/nagios/? Sounds like they can be read-only files somewhere under /usr (probably under /usr/share/nagios/)? John's email from Jan.6th also makes this observation. No response yet from project team. > >jv04: I also noticed the case imports PHP. But the webapp is shown as > > being implemented by cgi scripts? What is the PHP connection > > here? I didn't see any php files in the list. > > PHP server is used to access the dashboard of the nagios interface Something is missing here or in the docs, please provide a complete answer. > >jv05: Stability not given for the smf FMRI in exported interfaces. > > Stability is Stable. Ok! -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
