Ginnie,
Thanks for the feedback.
John
On 05/ 5/10 12:02 PM, Ginnie Wray wrote:
Hi John -
I have a couple of comments/questions....
Is there going to be a dependency for the SMF AI server service on the
Apache SMF service? it seems like there should be from the way I'm
interpreting the design.
Absolutely, there needs to be a dependency that the Apache service is
running.
In the Considerations section, after reading it a couple of times, my
assumption is that you're exploring options for managing the dynamic
content, but you don't really say that. Is that correct?
Yes. But it will be managing the static content. However, since the
static content is
via Apache already that part is already accomplished and not changing.
Since you call out scalability and reliability in the purpose section,
address it explicitly somewhere. I didn't get a clear sense of how
this solution addresses this.
OK. I can see that one.
thanks,
ginnie
On 05/04/10 10:26, John Fischer wrote:
All,
After additional research I have redesigned the solution that I was
proposing. The original design had CherryPy as a back end to an
Apache webserver using mod_wsgi. This added to the architectural
complexity of the Automated Installation Webserver rather then
simplifying it.
The redesigned solution is to simply use Apache and cgi-bin scripts
to accomplish the same tasks. Further details can be found at:
http://hub.opensolaris.org/bin/download/Project+caiman/auto_install/AI-Webserver-Specification.odt
Or
http://hub.opensolaris.org/bin/download/Project+caiman/auto_install/AI-Webserver-Specification.pdf
When doing the additional research it was noted that the solution
was 27% (or .25 seconds) per request slower. However, when viewing
this performance regression on a single request compared to the
overall installation of a client (30 minutes or longer) the regression
was deemed acceptable.
Much of the current code that is used within the current CherryPy
implementation will be reused. However, the CherryPy integration
code will not be. Again, this solution is to reduce the complexity of
the server.
A sample implementation of the GET request for the manifest files
(i.e., http://<host>:<port>/) is available upon request. This sample
was used to help determine the performance and resource impact
of the changes being proposed.
Comments/Questions welcomed.
Thanks,
John
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
