Feb 22, 2007

From OpenLiberty.org Wiki

Back to Meeting Minutes←

Present on the call: Asa Hardcastle, Conor Cahill, AJ From Spain, Derrick Harcey

Test Harness' / Hosting

conor: should get multiple impls for testing

Asa: what have you used

conor: has his own test harness that is script based, with test drivers for discovery, authentication, etc. Test harness compares output from tool with fuzzy comparison with known good results.

Asa: two things intereste in doing: 1) getting as many test harnesses together as possible, 2) working on architecture document. Would it be useful to get access to a hosted test server to use for testing.

Derrick: can stand up a test server on set of static IPs.

Asa: HP has made available SelectFederation available (curtis is assisting). and Liberty is willing to pay for hosting.

Derrick: Can set up Sun product, and make other OSS software available as well. Access to testers can be provisioned.

conor: except that some companies make it difficult to host applictions inside their domain. Need shell and ssh access.

Asa: so we can make hosting avail where necessary

Derrick: to be clear, hosts he is provide are personal not Sun, so he can host OSS too. May be useful to have distributed servers to give more real world access.

Asa: So to summarize

• Connor - can install on a host somewhere if ssh/shell access ispossible

• AJ - might be able to make hosting available, via virtual servers if necessary (parallels or VMware). just need to know the memory requirements, disk, etc. Will check with mgmt and report the particulars.

• Asa - his sysadmin will manage a machine if he has full access. This host will probably be Redhat.

Derrick: Don't want to necessarily "standardize" on a platform

Conor: just to be clear, we are just talking about hosting for implementations we will be testing against. The actual OL code will be platform agnostic.

Conor: testing always becomes interactive. So it helps if you have someone on the receiving end that can look at the log. So you might want to have some automated means of accessing the logs.

Asa: like emailing the logs

Conor: whatever, but it may go above and beyond what you get in the off-the-shelf system.

Asa: sounds like conor's stuff is well suited to this

Conor: it is on the client side, but on the host side it may need some work. Also creates multiple accounts for testers so they don't collide under simultaneous access.

Asa: in the beginning, people who are developing the test implementation will be pretty intermittently testing, so it won't be a big burden initially to have people

Derrick: can set up servers, possible giving root access withing zones. Is there any code useful at this time.

Arch Doc Outline

Asa: Template for architecture that seems relevant. Added to the wiki. Just a rough map of what the arch document should contain. More news next week. This week we are integrating the HP select federation implementation donated for testing.

Asa: first deliverable is the architecture doc. No code yet, but will start coding soon as a test of architecture dev, but not necessarily useful for others to begin with. As the arch document starts getting some depth, getting contributions from people regarding existing code or approaches that might fit into this layering.

Conor: So asa should walk through conor test code, and conor can help with that.

Asa: Outline for Arch document is on the wiki now, so feel free to look and add things.