puppetlabs/vmpooler
2
0
Fork 0
mirror of https://github.com/puppetlabs/vmpooler.git synced 2026-01-27 02:18:41 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

(POOLER-181) Separate Dashboard from api

Browse source 
Allow the dashboard to run separately from the API, so that the
dashboard can be scaled appropriately.

Note - this implementation actually co-runs the api in the dashboard
instance to re-use the api code for the dashboard endpoints and other
v1 endpoints collecting the operating information.
This commit is contained in:
John O'Connor 2020-07-03 20:02:57 +01:00
parent 6d01079f4a
commit 1073629c13
3 changed files with 16 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

15
lib/vmpooler/api.rb
View file

@ -3,7 +3,7 @@
module Vmpooler
class API < Sinatra::Base
# Load API components
%w[helpers dashboard reroute v1 request_logger].each do |lib|
%w[helpers reroute v1 request_logger dashboard].each do |lib|
require "vmpooler/api/#{lib}"
end
# Load dashboard components
@ -42,12 +42,17 @@ module Vmpooler
use Prometheus::Middleware::Exporter, path: metrics.endpoint
end
if torun.include? :api
# Determine which parts of the API to actually run.
# The Dashboard also runs the API parts for its own "self-referencing" purposes, i.e. to re-use those parts
# that allow it to pull the information from redis.
if (torun & %i[api dashboard]).any?
# Enable API request logging only if required
use Vmpooler::API::RequestLogger, logger: logger if config[:config]['request_logger']
use Vmpooler::API::RequestLogger, logger: logger if config[:config]['request_logger'] && (torun.include? :api)
use Vmpooler::Dashboard
use Vmpooler::API::Dashboard
if torun.include? :dashboard
use Vmpooler::Dashboard
use Vmpooler::API::Dashboard
end
use Vmpooler::API::Reroute
use Vmpooler::API::V1
end