Docker orchestration for EEA main portal services
- Dedicated Rancher Environment (recommended)
- Register dedicated
db
hosts with labels:db=yes
(PostgreSQL) - Register dedicated
backend
hosts with label:backend=yes
(Plone) - Register dedicated
frontend
hosts with label:frontend=yes
(Varnish, Apache, HAProxy)
Note: See EEA SVN for
answers.txt
files
- From Rancher Catalog > Library deploy:
- Rancher NFS
- From Rancher Catalog > EEA deploy:
- EEA WWW - Volumes
- DB Volume Driver:
external
- DB Volume Driver:
- EEA WWW - Sync
- Get
SSH Public Key (rsync-client)
fromWWW AWS > www-sync > rsync-client > www-sync-rsync-client-1 > Console
SSH Public Key (PostgreSQL)
DISABLED- Make sure that
rsync-client
on www-aws can connect to thisrsync-server
. - Make sure that
rsync-client
can connect torsync-server
from devel environment
- Get
- EEA WWW - Volumes
Note: See EEA SVN for
answers.txt
files
- From Rancher Catalog > EEA deploy:
- EEA - PostgreSQL
- Name:
www-postgres
- Name:
- EEA - PostgreSQL
Note: See EEA SVN for
answers.txt
files
- From Rancher Catalog > EEA deploy:
- EEA - WWW (Plone)
Note: See EEA SVN for
answers.txt
files
- From Rancher Catalog > EEA deploy:
- EEA - Frontend
- EEA - Load Balancer
-
Within Rancher UI press the available upgrade buttons
-
Confirm the upgrade
-
Or roll-back if something goes wrong and abort the upgrade procedure
-
Start Plone instance in
debug
mode$ rancher exec -it www-plone/debug-instance bash $ bin/instance fg
-
Now, via Rancher UI:
- Within
www-plone/debug-instance
stack findexposed
port for8080
and click on it.
- Within