SAC Meeting 2018-03-02

From OSGeo
Revision as of 13:18, 19 February 2018 by Strk (talk | contribs) (→‎Agenda: add Dropbox replacement solution)
Jump to navigation Jump to search


Where and When

Agenda

Go over status of SSLs - FOSS4G2018

January 4th 2018 Meeting

<Fill report here>

New Website status report

Report:

  • [robe] Status of staging.www.osgeo.org now setup on web18a.osgeo.osuosl.org (plans to migrate production to there as well)
 Eventual shutoff of cloudvps.com hosting

Sys Admin Contract

  • [martin]:

<Fill report here>

Martin to report on what he's been working on.

Migration off old hard-ware AND Virtualization, Containerization, or None

  • Discussion pending on list (moderator: could not find the mail thread)
  • Needs:
    • trac is painfully slow (now seems better with Chris Giorgi's recent changes to apache config)
    • osgeo6 is running an ancient Debian, needs to be updated

Leaning to libvrt since it can be done with one server (less resource intensive than ganeti), with possibility of moving to ganeti next year when we get more hardware.

DONE: Alex sent quote to mailing list, Updated Feb 15 ~$6300-7000. Chris Gorgi has some ideas, may provide enhancements

  • DONE: provide clarification of new hardware purchase options suitability for hosting type. (wildintellect)
    • LXD was suggested as a drop-in alternative to full Virtualization with KVM for most service; this more similar to the feel of a virtual machine than say Docker.
    • We can mix, nest, and layer both containers and virtualization interchangeably.
    • Easy candidates for containers include Downloads and Webextra (FOSS4G) which are static files.
  • Suggestions:
    • Optane card for extra disk caching beyond memory - Question how do we configure this:
      • 25% is reserved as unallocated to reduce write-wearing and maintain speed over the expected life of the server.
      • A portion (~25-50%) would be allocated to the ZFS L2ARC (or equivalent) to keep warm FS blocks instantly accessible.
      • The remainder is available to be used essentially as a large persistent ramdisk.
    • Fill RAM, mostly caches requests, in particular file downloads
      • This will happen automatically as files are accessed and added to the filesystem's cache.
      • Data can be pre-cached simply by accessing the files and directories -- a simple script can run periodically to ensure they are kept marked as hot.
    • Larger DWPD rating for SSDs to better handle writes - Question, we didn't do this for OSGeo6, anything we should look out for? Should we estimate life of OSGeo6 drives and replace pre-failure next couple of years.
      • Total write volume can be checked with smart-tools and drives approaching the stated limit should be replaced or move to storage-only applications.
      • Write endurance and long-term speed can be improved by leaving 20-50% of each drive unallocated.
    • Mirrored pair of SATA SSDs for write-caching and high io loads.
      • Reserve 25-33% unallocated.
      • Provide ZFS ZIL SLOG with 32-64GB to minimize write latency for data stored on HDDs.
      • The remainder can be used for loads with high mixed read/write transactional loads, such as active databases, mail, etc.
    • 4 TB Spinning disks, still plenty of space (7+ usable), takes less time to rebuild on failure, cost diverted to other features.
      • (Please note - an active storage pool should never be filled to more than 2/3 of capacity to avoid serious performance degradation and fragmentation - C.G.)


Any other feedback from others to be discussed

Dropbox replacement for board

Board wants a Dropbox replacement, wrote requirements on the wiki. See https://trac.osgeo.org/osgeo/ticket/2110

We should provide a solution

Others

Trac SVN status

  • Seems good been upgrade to Debian 7

Ticket Triage

GeoForAll DNS

Jeff to report on status of GeoForALL and other DNS issues he's been fixing TODO: Keep nudging GeoForAll folks

Weblate instance ?

Some projects requested a translate.osgeo.org, we could pay Weblate core developers for the initial setup of a multi-user instance.

Minutes

Attendance

Full transcript

Details

Next Meeting

Proposed Time: UTC: Thursday, March 15th, 2018 at 8:00 pm

SAC main page

Retrieved from "http://wiki.osgeo.org/w/index.php?title=SAC_Meeting_2018-03-02&oldid=113767"