#3408: Decide where to move contents of osgeo3
-----------------------+---------------------------
Reporter: cvvergara | Owner: sac-tickets@…
Type: task | Status: new
Priority: major | Milestone: Unplanned
Component: SysAdmin | Keywords:
-----------------------+---------------------------
The following containers are running on `osgeo3`
|| dronie-client ||
|| gallery ||
|| geo-docs ||
|| geoserver-cite ||
|| hop ||
|| matrix ||
|| monitor ||
|| nexus-2 ||
|| osgeo3-nginx ||
Tasks:
- Decide to which server are to be moved
- Once decision is made open ticket per container
Options: osgeo7, osgeo8, osgeo9, osgeo6 after been formatted to receive
containers
--
Ticket URL: <Making sure you're not a bot!;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3408: Decide where to move contents of osgeo3
-----------------------+----------------------------
Reporter: cvvergara | Owner: sac-tickets@…
Type: task | Status: new
Priority: major | Milestone: Unplanned
Component: SysAdmin | Resolution:
Keywords: |
-----------------------+----------------------------
Comment (by robe):
I think we can move all these to osgeo6 once osgeo6 has new disks and is
reformatted.
--
Ticket URL: <Making sure you're not a bot!;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3408: Decide where to move contents of osgeo3
-----------------------+--------------------------------------------
Reporter: cvvergara | Owner: sac-tickets@…
Type: task | Status: new
Priority: major | Milestone: Infrastructure Migration 2025
Component: SysAdmin | Resolution:
Keywords: |
-----------------------+--------------------------------------------
Changes (by strk):
* milestone: Unplanned => Infrastructure Migration 2025
--
Ticket URL: <Making sure you're not a bot!;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3408: Decide where to move contents of osgeo3
-------------------------------------+----------------------------
Reporter: cvvergara | Owner: sac-tickets@…
Type: task | Status: new
Priority: major | Milestone:
Component: SysAdmin/Infrastructure | Resolution:
Keywords: |
-------------------------------------+----------------------------
Changes (by strk):
* component: SysAdmin => SysAdmin/Infrastructure
* milestone: Infrastructure Migration 2025 =>
--
Ticket URL: <Making sure you're not a bot!;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3408: Decide where to move contents of osgeo3
-------------------------------------+----------------------------
Reporter: cvvergara | Owner: sac-tickets@…
Type: task | Status: new
Priority: major | Milestone:
Component: SysAdmin/Infrastructure | Resolution:
Keywords: |
-------------------------------------+----------------------------
Comment (by strk):
Gallery was an experiment and is currently down, see
Gallery - OSGeo
hop and osgeo3-nginx are just service containers so not needed when
services move elsewhere, so the real services to move would be:
- dronie-client
- geo-docs
- geoserver-cite
- matrix
- nexus (repo.osgeo.org, docker.osgeo.org)
- monitor (grafana) - does anyone really use it ?
SAC Service Status - OSGeo
This would be a good occasion to drop the "osgeo3" role from ansible and
replace with per-service roles so to abstract them from their actual
deployment host (like it's done for trac and gitea, delegating to a
parametric "nginx proxy" host the installation of the virtual hosts...)
--
Ticket URL: <Making sure you're not a bot!;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.