Page MenuHomeDevCentral

Provide a PaaS front-end role
AbandonedPublic

Authored by dereckson on Jun 3 2020, 17:43.
Tags
None
Referenced Files
F10639363: D2293.diff
Mon, Jul 21, 01:00
F10638926: D2293.id5779.diff
Mon, Jul 21, 00:32
Unknown Object (File)
Thu, Jul 17, 13:58
Unknown Object (File)
Tue, Jul 15, 10:21
Unknown Object (File)
Tue, Jul 15, 09:16
Unknown Object (File)
Thu, Jul 10, 17:06
Unknown Object (File)
Thu, Jul 10, 15:47
Unknown Object (File)
Thu, Jul 10, 15:33
Subscribers
None

Details

Summary

Currently, each Docker engine software receives a nginx front-end.

This change consolidates them in a specific role, to allow to move
the Docker engines into the private part.

Ref T1616

Test Plan

Browse each vhost and ensure it serves a 200, not a 502/504.

Diff Detail

Repository
rOPS Nasqueron Operations
Lint
Lint Passed
Unit
No Test Coverage
Branch
paas-docker-frontend
Build Status
Buildable 3567
Build 3816: arc lint + arc unit

Event Timeline

dereckson created this revision.

Hmmm, no autosave on this Atom

Date. No need for dirs variable.

roles/paas-frontend/nginx/config.sls
64
76

The issue with this idea is we've to load balance more than HTTP:

  • various XMPP ports for OpenFire
  • SSH port 5022 for DevCentral

Not currently in scope as:

  • most services switch to localhost or 172.27.27.5 to listen to services
  • we first need a correct load balancer solution, with keepalive
  • we also need to load balance non-HTTP ports (XMPP ports for openfire, 5022 for devcentral)
  • to rebase this change against webserver-core won't be efficient

Plan is instead to first create a general load balancer role, then move paas-docker nginx on it