deepti vaidya wrote: > > > Please find the updated arc-one pager and Find below my answers..
Most of the questions I have are minor, I really suggest working directly with your case owner to go over the spec and polish up the details, it can be far quicker than way instead of a long email thread.. Imported interfaces need the case being imported from. Now 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 most of that Project Private implementation detail? If not, why not? (Listing the package contents is nice though, as it helps notice details. Not a rule but I like to see the cases include the file list or a package map in an appendix just as ancillary information. But not every file in the package is an interface.) > I have expanded the cgi-scripts. Could you please suggest me where else > the cgi-files should go if not under /usr/apache2/2.2/bin. Beyond a file list, it'd be good to explain the delivered functionality a little. The case doesn't really explain what this webapp does or for what users will access it. I can guess it provides some web interface to nagios, but what exactly does it do? Is it an administrative interface where I can configure what to monitor and who gets the notifications? Or a monitoring interface to view the events in real time? All of the above? Or something else? In general the spec is a bit too light on explanations. It doesn't need to have a lot, but a few paragraphs here and there explaining the different parts being delivered, how they work and how they interact with each other would help a lot. A case should be more than just a list of files. Also, I see nagios itself is configured in /etc/nagios, but is there any user-editable configuration associated with the webapp? Does that live in /etc/nagios as well? In any case, since these cgis are a webapp they don't belong in the apache bin directory. The apache bin directory contains CLIs which an Apache httpd user can be expected to run from a shell or script, which these cgis are unlikely to be. Since the rest of the webapp is under /usr/share/nagios why aren't the cgis there as well? Maybe in a 'cgi-bin' subdir? Reading the list of files I gather there are three parts here; the daemon (started via smf), the CLIs and the webapp. How do all these parts fit together? > /usr/bin/nagios uncomitted Executable file > /usr/bin/nagiostats uncomitted Executable file What does the CLIs do? Do they have any options? > Not An Interface > -------------------- > /etc/nagios -- cfg files are copied here > /etc/nagios/objects -- cfg files are copied here 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? 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. Lots of questions above but most are minor. As noted, instead of going through them point by point via email, I suggest it'll be quicker to get together with your case owner and do one pass over the entire spec to polish it up with a bit more info keeping in mind the questions above. That should be the fastest way instead of going into a long email Q&A interaction. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
