Config updates can be time consuming, especially in testing environments
that utilize virt-on-virt. Rather than timing out workers that are taking
a long time to process an update, bump the timeout to 5 minutes and allow
the requesting orchestrator to time out its request at shorter deadlines
instead.
Change-Id: Ibee73d7a43864da645b5d7198a5df2f2bf936ea9
Used for setting up conntrackd between two clustered peers.
Partially-implements: blueprint appliance-ha
Change-Id: Ice3f4dbed02b877bc64ae73879a74acc26cca47e
This adds a new IP manager driver for configuring addresses
and routes via keepalived instead of directly. It used when
the logical resource is configured to be highly-available,
according to configuration pushed by the orchestrator.
We rely on a 'ha_resource' flag attached to the main config
dict to enable it, and use specific HA config about peers and
cluster priority contained in the 'ha_config' section of the
main config.
The resulting keepalived cluster contains a VRRP instance for
each interface, with the exception of the management interface.
Partially-implements: blueprint appliance-ha
Change-Id: I5ababa41d65642b00f6b808197af9b2a59ebc67a
We dont ever actually import this anywhere or depend on it as a python
dependency. Instead, its part of our diskimage-builder elements and
is largely an opinionated deployer choice we've made. The only purpose
having it in requirements.txt is to pull it in during installation, which
should be delegated to ansible/DIB instead.
This also manually sync's global-requirements along with the update.
Closes-bug: #1526527
Change-Id: I834efb47ccda02a5163c5083836ff29fdc3fdd6f
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 adds iputils-ping package to the base package install. It appears
something changed in debian or DIB and this is no longer installed by
default.
Change-Id: I8bf538a9759aaa117edb5abf492c9dc630efc23b
This makes the kernel update task only happen on wheezy and removes
the default release stuff from bird (the newer backports version should be
installed without pinning to that repo)
Change-Id: Id4b997848edee21bdcfa3d9defedc69598eccfad
The appliance currently tries to log to /tmp/gunicorn.log, but thats
misconfigured. This sets gunicorn up to log to /var/log/akanda/ for
both access and error logs and installs and configures logrotate for
those files.
Change-Id: Ie75f305860a0c5204ec8fe5b1af0de03826aa880
The default 30s worker timeout for gunicorn is not sufficient for
some slower environments, as the metadata service takes a while to
restart. This bumps it to 60s to ensure we dont fail config updates
on worker timeouts.
Change-Id: If27329b58d97e6aef687a069615dbda763dba8c1
Closes-bug: #1462100
This change makes the MGT API service fully configurable to either IPv4
or IPv6 address.
Implements blueprint: cloud-init-provisioning
Change-Id: Ibff39030c4e3fe04c3f8cc238508e33d450a4398