Newer versions of paramiko (pulled in via ansible install)
now require libffi-dev to build.
Closes-bug: #1583321
Change-Id: If3794ededacfcf53857328a19627cf0331878822
With the switch to rootwrap, the API service now runs as the gunicorn
user but /etc/nginx/sites-enabled is still owned by root. This updates
the DIB element to ensure its writable by gunicorn for config rendering.
Also makes a trivial update to releasenotes to remove the UNRELEASED
flag from mitaka.
Change-Id: Ieac128e47a44dd48acd00f68cd8e3a9ca15441ec
Closes-bug: #1558577
We've been maintaining our own element for this but should be using the
one in upstream DIB. The URL for get-pip.py is outdated and overriding
the functional element in DIB-proper.
Change-Id: I592015061d83c2e8dfb3ddd94cf29cd5013311c1
Closes-bug: #1536410
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
This checks in diskimage-builder elements from the akanda-appliance-builder
repository, which we'll be merging with this one.
Co-Authored-By: David Lenwell <dlenwell@gmail.com>
Co-Authored-By: Mark McClain <mark@mcclain.xyz>
Change-Id: Ic53dec0ff675be1e38babc893820f27561cfd774
Partial-Bug: #1464359