LB Admin Meeting – Proposed Agenda (Sepetember 22)

General

• Satish to give a short update what is changed in the last few weeks.
• Talk about the way to configure error pages. There is no way to generated error page information now. Should we be reading this information from deployment descriptors.

CLI

• New options (lbenableallinstances and lbenableallapplications) for create-http-lb-config.
• The options make the command configure-http-lb-config not very useful? This command was provided as convenience command. Should we expose this command?

GUI

• GUI should make Auto Apply as false by default
• GUI should also enable "Apply Changes", even when Auto Apply is enabled.
• GUI should provide a feature to enable/disable applications/instances in LB
• GUI should provide option to save loadbalancer.xml into a local file rather than storing on to DAS.

Testing

• Test LB on WS 7.0 (both HTTP and HTTPS)
• Test HTTP connection in addition to HTTPS.
• Test various scenarios for auto apply feature (some of them already may have been tested)
  • deploy/undeploy app
  • add/delete a instance
  • add/delete cluster
  • disable/enable server/instance
• Test various error scenarios (404, other 4XX, 500 and other 5XX etc)& error pages
• Others.

Installation

• Installer should support LB plugin with certificates and ready

for auto apply. (WS 7.0 has CLI and can easily be supported)

Documentation

• Lot of places sample commands need to be provided - for example dotted commands for setting health checker properties etc.
• Provide mapping between loadbalancer.xml and CLI commands/GUI tasks
• Document the new commands and options
• Provide lot of background information like architecture - see feedback http://blogs.oracle.com/sv96363/entry/load_balancer_administration_current_status from User Experience Group.