[SAC] [OSGeo] #2697: Dedicated lxd container for id.osgeo.org

#2697: Dedicated lxd container for id.osgeo.org
---------------------------+--------------------------------------
Reporter: robe | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2022-I
Component: Systems Admin | Keywords:
---------------------------+--------------------------------------
id.osgeo.org is currently running on old-web. Which I think might be the
only thing still running on it.

I think it's best to start off clean with a new debian 11 container and
retire old-web.

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2697&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

#2697: Dedicated lxd container for id.osgeo.org
---------------------------+---------------------------------------
Reporter: robe | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2022-I
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+---------------------------------------

Comment (by strk):

Isn't it overkill to have a full container (rootfs) for just a bunch of
cgi-bin files ?

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2697#comment:1&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

#2697: Dedicated lxd container for id.osgeo.org
---------------------------+---------------------------------------
Reporter: robe | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2022-I
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+---------------------------------------

Comment (by robe):

No. I consider id.osgeo.org very critical piece of our infrastructure,
just as secure is.
Both are actually pretty simple.

The idea that a python upgrade could break id.osgeo.org scares me.

Alternatively I suppose we could just run it in docker, but that I would
find kinda confusing. Like if it were running on dronie-server, I would
be constantly thinking where is id.osgeo.org.

Anyway you decide. I just like the idea the core pieces of our infra have
a dedicated home and can't be broken by other things being installed on
them.

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2697#comment:2&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

#2697: Dedicated lxd container for id.osgeo.org
---------------------------+---------------------------------------
Reporter: robe | Owner: sac@…
     Type: task | Status: closed
Priority: normal | Milestone: Sysadmin Contract 2022-I
Component: Systems Admin | Resolution: duplicate
Keywords: |
---------------------------+---------------------------------------
Changes (by strk):

* status: new => closed
* resolution: => duplicate

Comment:

This was a duplicate of #2546 which is now fixed

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2697#comment:3&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.