Project

General

Profile

Controller architecture transition » History » Version 2

Tom Clegg, 01/14/2019 06:35 PM

1 1 Tom Clegg
h1. Controller architecture transition
2
3
Implement rpc package (forward requests to a remote cluster) -- incl. fill in all remaining options/response structs in arvados package
4
5
Implement initial pgdb package that wraps an rpc.DBClient pointing to the local RailsAPI
6
7
Implement router package
8
9
Update controller to pass non-federated APIs to router (instead of proxying the incoming HTTP request to rails)
10
11
Move existing federation behavior to federation.DBClient
12
13
In pgdb, implement "run test in a transaction" framework
14
15
In pgdb, implement a simple set of APIs (specimens?) incl. audit logs and scope/permission checks
16 2 Tom Clegg
17
To avoid superfluous nil checks in pgdb, eliminate pointers in fields that don't have a distinct meaningful null value (arvados.Collection, RuntimeConstraints, Log, etc.)
18 1 Tom Clegg
19
Port remaining APIs to pgdb/rpc/federation
20
* specimens/humans
21
* links
22
* collections
23
* containers/requests
24
* jobs/pipelines
25
* groups