Difference between revisions of "SAC Meeting 2019-02"
Jump to navigation
Jump to search
Line 12: | Line 12: | ||
* [https://trac.osgeo.org/osgeo/ticket/2205 2205] Regina completed install of Ubuntu 18.04.1 on OSGeo7 on Samsung drive and also installed zfsutils-linux and lxd. | * [https://trac.osgeo.org/osgeo/ticket/2205 2205] Regina completed install of Ubuntu 18.04.1 on OSGeo7 on Samsung drive and also installed zfsutils-linux and lxd. | ||
Regina completed install of nginx lxd container, and nextcloud.osgeo.org (which proxies thru the nginx container), started setting up a debian10 lxd container for ssh access (not completed) | Regina completed install of nginx lxd container, and nextcloud.osgeo.org (which proxies thru the nginx container), started setting up a debian10 lxd container for ssh access (not completed) | ||
− | + | , docker template container completed and used to build dronie server / agent | |
− | + | * Discovered nginx the way currently set up can't see external ip - need to do differently than just proxying port which means we'll need a dedicated IP for nginx | |
− | + | * Can we ask OSUOSL for an extra ip | |
NEXT STEPS: For robe - setup container downloads.osgeo.org (for testing first with no data) and with nginx will require LDAP ssh (requires figuring out theldap/ ssh issue on lxd) | NEXT STEPS: For robe - setup container downloads.osgeo.org (for testing first with no data) and with nginx will require LDAP ssh (requires figuring out theldap/ ssh issue on lxd) |
Revision as of 13:56, 13 February 2019
Where and When
- in IRC on Freenode, channel: osgeo-sac
- Web IRC client: https://webchat.freenode.net/ Thursday Feb 14th 2019 20 UTC
Meetings Happened
Agenda
Talk about hardware plans
- 2205 Regina completed install of Ubuntu 18.04.1 on OSGeo7 on Samsung drive and also installed zfsutils-linux and lxd.
Regina completed install of nginx lxd container, and nextcloud.osgeo.org (which proxies thru the nginx container), started setting up a debian10 lxd container for ssh access (not completed)
, docker template container completed and used to build dronie server / agent
- Discovered nginx the way currently set up can't see external ip - need to do differently than just proxying port which means we'll need a dedicated IP for nginx
* Can we ask OSUOSL for an extra ip
NEXT STEPS: For robe - setup container downloads.osgeo.org (for testing first with no data) and with nginx will require LDAP ssh (requires figuring out theldap/ ssh issue on lxd)
- Details of what's done so far on SAC_Service_Status#osgeo_7.
- FTP mirror on OSUOSL hardware, do we want an to push or pull with rsync or other method. TODO: make sure there's a ticket.
Budget
- We need to make a 2019 Budget to submit to the board. 2019 Proposal
- 2018 - How much did we actually spend?
- Only 1 contract partly used
- OSUOSL donation never happened because board wanted to add more $ but never voted on it?
System Contracts
- Regina has a draft contract would like to go over
- New contract for Vicky for supporting Wordpress www.osgeo.org, I for supporting new lxd system and setting up new apps on it
Open tickets needing attention
- 2019.foss4g.org needs oauth with github - 22228
- https://trac.osgeo.org/osgeo/ticket/2190 (Vicky has in progress, needs feedback) [DONE still need feedback? ]
- maybe we could also setup a domain like elections.osgeo.org too
- important that only CRO has access to elections stuff
- #2199 Upload FOSS4G PDF Waiting for feedback from Studio 17
- [https://trac.osgeo.org/osgeo/ticket/2195 Blog account for Astride - this should be on www.osgeo.org? Asked for clarification
- Domain Renewals (needs ticket)
Other topics
- are we feeling ok now with the cracked geotools account on osgeo6?
- We need to change the passwords, and move to key only login
- the question is how to deploy the keys
- One or all 4 keys? (4??)
- Add support for registering public user SSH keys in LDAP: https://trac.osgeo.org/osgeo/ticket/2116
- confirmed password auth is now off
- we should clean the keys and deploy new ones
- geotools should create new keys and supply the public key.