433a4c7190
This introduces the ability to create service manager drivers to handle managing advanced services within the akanda-appliance. It splits some common things into a System manager. Existing stuff that is router-specific is moved to a Router manager and we begin implementing LBAAS drivers using Nginx. At the moment, configuration for which drivers are loaded by the appliance code itself is stored in /etc/default/akanda-appliance. This is setup by a DIB_* variable and accessed by the appliance via environment variable. We should improve this later when we need to expose richer configuration to the appliance. We could and should work on the API for this. Currently, our v1 API is entirely router-specific. This adds to that and allows the RUG to attach other advanced service configuratino data to the config object it pushes. If the corresponding service's driver has been enabled in the appliance, it will attempt to find that data and configure the advanced service accordingly. Ideally, longterm we want a v2 API that can reference all services the same. There's a few ugly compat hacks added here to maintain compatability with where the RUG expects certain router resources to be. We can evolve this over time. Partially-implements: blueprint appliance-provisioning-driver Depends-on: Ic19a883f56fb6d65a83b1f4d93b581f9e242d97f Change-Id: I6048789ec15fad1dbc899cbbd82508433cb96d44 |
||
|---|---|---|
| .. | ||
| akanda | ||
| ansible | ||
| debug-user | ||
| nginx | ||
| nginx-plus | ||
| pip-and-virtualenv | ||