Project

General

Profile

Release Status » History » Version 4

Tom Clegg, 04/05/2014 01:15 PM

1 1 Tom Clegg
h1. Release Status
2
3 4 Tom Clegg
Arvados is currently (April 2014) ready for adventurous users to try out, but not ready for day to day production use.  If you are interested in helping to *design and improve* Arvados, you can do that now.
4 1 Tom Clegg
5
Some components have been implemented, and we are running them in our own test/production environments.
6
* REST API server
7
* Client-side pipeline manager
8 4 Tom Clegg
* Workbench web application
9 1 Tom Clegg
10 4 Tom Clegg
Some components currently exist only as prototypes from the Free Factories predecessor project. Porting these to Arvados is one of our current development efforts.
11 1 Tom Clegg
* Keep server
12
* Crunch MapReduce job manager
13
14
Some components have not been implemented yet. We think it's important to describe them to establish scope, even though they are currently vaporware. We also hope to attract early feedback.
15
* Lightning
16
* Compact genome format
17
18
APIs are in active development.
19 4 Tom Clegg
* REST API is getting stable but isn't at 1.0 yet. A more powerful graph API is also in development.
20
* Keep client API is stable, but system-facing API (e.g., related to garbage collection) are still in development.
21
* Crunch API (job task environment) is mostly stable, but containerizing workers/tasks may motivate some changes.
22 1 Tom Clegg
23
SDKs are in active development.
24 4 Tom Clegg
* Rails SDK (an ActiveRecord-like interface) is not yet packaged separately from the Workbench app.
25
* Ruby SDK is stable but lacks a native Keep client.
26
* Python SDK (based on the Google API client) is stable but should gain an alternative (less verbose) calling syntax and better integration of data APIs with Collections.
27
* Command line tool should gain an alternative (less verbose, less quoting-intensive) calling syntax.
28 1 Tom Clegg
29
Documentation is in active development.
30 4 Tom Clegg
* Tutorials and examples are continuously improved as APIs improve and stabilize
31
* Install docs are terse but functional
32 1 Tom Clegg
* API docs need to be filled in (many models are currently documented only as source code in /services/api/)
33
* Admin docs are a placeholder