OSAF Hosted Service Alpha Release Definition

Acceptance criteria

Upstream

• The public service is running a publicly released, unpatched version of the OSAF Cosmo+Scooby product.
• It's possible to run a CMP query to fetch the list of all user accounts stored in any database.

Email

• It is possible to submit an email to a personalized address and have it be included in a collection.

Scaling

• Cosmo user and user profile data is stored in a MySQL^? database.
• There is a "Central DB" available which stores user profile data, database location info, and Tomcat sessions info.
• Cosmo can perform requests against different backend databases depending on which user a request is for.
• Cosmo is stateless and can accept requests for any user or operation in the cluster.
• The server infrastructure will have withstood a stress-test simulating 25 average write transactions per second.

Customer support

• Service customers can ask for customer support via a web form and via email.
• There is a defined Terms of Service.

Ops

• HTTP traffic (Scooby, CalDAV, Atom) will be directed through a load balancer.
• SSL decryption will happen on a separate physical host from Cosmo application logic.
• All HTTP accesses are fully logged in Extended Common Log Format, and additional information about each transaction is kept including duration served.
• Backups of all user data is taken daily and stored offsite.
• All production hosts are located at GNi in San Francisco.

Aprovals

• KEI IT has signed off on the runbook.
• PPD has signed off on the visual design of all service pages.
• Sheila Mooney, as Product Manager, has signed off that product requirements are met.

Implementation

• The load balancer will be implemented by a single machine running Pound, a SSL decryption and HTTP load balancing engine