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