backend.ai Agent backend abstraction

Currently we use only Docker containers as the kernel session host. However, this may be extended to other type of services, such as cloud vendor-specific remote APIs or local processes for debugging and testing purposes. For instance, we could implement a "data agent" by specializing a subset of agents in a cluster to manage a memory-cached distributed filesystem such as Alluxio.

[ ] Configurable driver selection on startup (via etcd or command-line)
[ ] Report the list of active drivers when sending heartbeats to the manager

Nov 04 '17 07:11 achimnol

With the work related to lablup/backend.ai-agent#66, now we have a working plugin auto-discovery mechanism. Let's use it!

Aug 31 '18 14:08 achimnol

This issue is the precondition to resolve lablup/backend.ai-agent#68.

Aug 31 '18 14:08 achimnol

This is now going to be implemented via lablup/backend.ai-agent#125 and lablup/backend.ai-agent#123.

Aug 15 '19 05:08 achimnol

lablup/backend.ai-agent#123 PR now moved to lablup/backend.ai-agent#128

Aug 16 '19 08:08 kyujin-cho

This is considered done. We are going to expand the format of agent.toml to have explicit backend.xxx sections for backend-specific configurations in #1597.

Apr 25 '24 03:04 achimnol