abaco
abaco copied to clipboard
TACC
Actor Based Co(mputing)ntainers
Likely should add more metrics to the metrics store.
New Tapis search specification has a spec for selecting, sorting, and a new feature called `startAfter`. Abaco is out-of-date on these and needs them added to keep inline with the...
For the purposes of reporting and debugging, I propose to include the short hash of the active container as `_abaco_container_hash` in the execution's environment variables. We would extend `agavepy.actors` to...
So that every single Abaco actor image doesn't have to be publicly accessible, add support for authenticated access to Docker registries.
Though Abaco allows us to build event-driven systems, we can't learn information about its state without polling. This puts load on the system and introduces latency to downstream consumers in...
We cannot easily stop an actor (temporarily) from accepting new work. This can be inconvenient when trying to test parallel sets of linked actors. It would be handy to be...
Currently, when the first worker on a given docker host is created for an actor, the actor's image is pulled from the docker hub. If the image has been updated...
I'm noticing that users are adopting increasing amounts of orchestration as they build and deploy and use Abaco. A limitation of the current system is that one must poll for...
Currently, images are not removed at any time by Abaco processes, including on actor delete. One challenge is that multiple actors can be registered with the same image. Another issue...
The actor `state` variable is super-useful, but is limited to single-worker actors. Some developers have routed around this limitation by imitating the state variable with the Agave `metadata` service, namespacing...