Project

General

Profile

Release Status » History » Version 9

Brett Smith, 07/27/2015 07:53 PM

1 1 Tom Clegg
h1. Release Status
2
3 9 Brett Smith
Arvados is still in beta, but can be used for day-to-day production work.  If you are interested in helping to *design and improve* Arvados, please [[IRC and Mailing Lists|join us]] on IRC or on the mailing lists.
4 1 Tom Clegg
5 9 Brett Smith
The following core components have been implemented:
6 1 Tom Clegg
* REST API server
7
* Client-side pipeline manager
8 9 Brett Smith
* Workbench Web front-end
9
* Keep server and proxy
10
* FUSE driver
11 1 Tom Clegg
* Crunch job manager
12 9 Brett Smith
* Node Manager
13 1 Tom Clegg
14 9 Brett Smith
The following core components are still under development:
15
* Data Manager: Data Manager has the logic to determine which Keep blocks should be moved or removed.  However, integration work with the Keep daemon is ongoing.
16 1 Tom Clegg
17 9 Brett Smith
Most APIs are stable, with only back-end support or critical bugfixes anticipated.
18
* The Arvados REST API is not officially v1.0 but very stable.
19
* Keep client API is stable.  System-facing API (e.g., related to garbage collection) is still in development.
20
* Crunch v1 API (job task environment) is very stable.
21 1 Tom Clegg
22 9 Brett Smith
SDKs are stabilizing but may receive further development based on need.
23
* Python SDK is stable.  The next major planned development is a new API to define and dispatch Crunch work.
24 4 Tom Clegg
* Ruby SDK is stable but lacks a native Keep client.
25 9 Brett Smith
* Go SDK is stable but lacks higher-level API interfaces.
26
* CLI SDK is stable but could use a number of interface and implementation improvements:
27
** Incorporate core commands like @arv copy@, @arv edit@, and resource manipulation into the Python SDK, to trim down the installation requirements for client software.
28
** Provide nicer options to let users query and manipulate resources with less inline JSON.
29
* Rails SDK (an ActiveRecord-like interface) is not yet packaged separately from the Workbench app.
30 1 Tom Clegg
31 4 Tom Clegg
Documentation is in active development.
32 9 Brett Smith
* Tutorials and examples are pretty settled, but improve along with supporting SDKs and tools.
33
* Install docs are incomplete, but improving rapidly and a major focus area.
34
* API docs are uneven.  Important models like Collection and Job are well-documented, but others only provide a basic field overview with no details.
35
* Admin docs are a terse cookbook and could use expansion.
36 1 Tom Clegg
37 9 Brett Smith
Last update: July 2015