| Serge Bazanski | 4abeb13 | 2022-10-11 11:32:19 +0200 | [diff] [blame^] | 1 | BMaaS Server |
| 2 | === |
| 3 | |
| 4 | Background |
| 5 | --- |
| 6 | |
| 7 | This server provides an interface to the BMaaS database/state over a gRPC API. Most components of the BMaaS system talk to the database directly whenever possible. Everything else communicates through this server. |
| 8 | |
| 9 | Currently this is: |
| 10 | |
| 11 | 1. Agents running on machines, as they should only be allowed to access/update information about the machine they're running on, and they're generally considered untrusted since they run on end-user available machines. |
| 12 | |
| 13 | In the future this server will likely also take care of: |
| 14 | |
| 15 | 1. A debug web API for developers/administrators to inspect database/BMDB state. |
| 16 | 2. Periodic batch jobs across the entire BMDB, like consistency checks. |
| 17 | 3. Exporting BMDB state into monitoring systems. |
| 18 | 4. Coordinating access to the BMDB systems if the current direct-access-to-database architecture stops scaling. |
| 19 | |
| 20 | Running |
| 21 | --- |
| 22 | |
| 23 | bazel run //cloud/bmaas/server/cmd -- -srv_dev_certs -bmdb_eat_my_data |
| 24 | |
| 25 | Although that's not very useful in itself currently. Instead, most functionality is currently exercised through automated tests. |
| 26 | |
| 27 | TODO(q3k): document complete BMaaS dev deployment (multi-component, single BMDB). |