Operations/Minutes/2023-05-18

From OpenStreetMap Foundation

OpenStreetMap Foundation, Operations Meeting - Draft minutes

These minutes do not go through a formal acceptance process.
This is not strictly an Operations Working Group (OWG) meeting.

Thursday 18 May 2023, 19:00 London time
Location: Video room at https://osmvideo.cloud68.co

Participants

Minutes by Dorothea Kazazi.

Absent

New action items from this meeting

  • OWG to review the draft policy by Martijn van Exel on adding editors to the editor menu [Reportage]
  • OPS to work out budget for a Pyrene replacement. [Topic: US rendering server]
  • Potentially ask the Arizona State University (ASU) if they're interested in hosting 3rd party hardware. [Topic: US rendering server]
  • Paul Norman to close the karm & eddie tickets. [Topic: Keeping karm & eddie longer]
  • Guillaume Rischard to send extra paperwork for HE.net [Topic: HE.net]
  • Paul Norman to start an open document listing goals for longer-term planning. [Topic: Longer-term planning]
  • Paul Norman to talk with Craig who offered to help with longer-term planning. [Topic: Longer-term planning]
  • Grant Slater to create ticket for removing some of the power limits. https://github.com/openstreetmap/operations/issues/884

Reportage

On a draft a policy regarding adding editors to the editor menu

On action item: 2023-04-20 Guillaume to ask people on Discourse for comments on a draft a policy regarding adding editors to the editor menu and provide context. [Topic: Reportage - Draft a policy regarding adding editors to the editor menu]

  • Martijn van Exel has written a draft policy and would like feedback from the OWG.
  • Decision: Change the action item to "OPS to review the draft that Martijn has written"

Action item: OWG to review the draft policy by Martijn van Exel on adding editors to the editor menu

On resilience plan document

On action item: 2023-04-20 Grant to write a high level document of what would happen if one of the data-centers caught fire and a sketch of what investments would be needed if we wanted to improve the different tiers. [Topic: Scheduled outage]

  • Draft being written and includes a number of scenarios.

On monitoring AMS RAID controller batteries

On action item: 2023-04-06 Grant to create a ticket for monitoring AMS RAID controller batteries. [Topic: HE.net]

  • There was a specific issue with the two machines, where the batteries were reporting as charging and not as failed.
  • Complete.

US rendering server

  • Need to replace Pyrene (Tile server, Hosted by OSUOSL in Corvallis, Oregon).
  • The plan was to go with Arizona State University (ASU), who would be paying for it. They initially offered DELL equipment which they usually buy, but were not sufficient for us.
  • OSM US was - at the time - willing to sponsor the hardware if needed.

Suggestion

  • Ask ASU if they're interested in hosting 3rd party hardware. If they're not, avoid establishing presence in an additional site by sending the hardware there.

Other points during discussion

  • ASU would probably not be opposed if hardware was shipped to them and was easy to rack.
  • We usually buy second hand US hardware from Orange computers.
    • Do not seem to have NVMe.
    • Might build us a custom system.

Action items

  • OPS to work out budget for a Pyrene replacement.
  • Potentially ask ASU if they're interested in hosting 3rd party hardware.

Keeping karm & eddie longer

karm and eddie are read only database mirrors for www.openstreetmap.org

PG upgrade + index changes saved several TB, do we still need to decommission these?

  • They're all SSDs.
  • We would stop using them as they would be running out of disk space, but no longer the case.

Action item

Paul to close the karm & eddie tickets.

HE.net

The final order has been submitted.

Dublin

  • Current status: waiting for a letter of authority (LoA), to be able to order the crossconnects to their equipment.
  • Theoretically we can keep the existing crossconnect in Dublin.
  • Plan: Get the 2nd line connected to a 1G port, and get the existing line connected to another 1G port.
    • Might end up costing more for remote hands.
    • We got the bonded link already set-up, if we add the 1G straight away to that, it's fully resilient once we got the IP address. We can talk to technical implementation people, once the paperwork gets done.

AMS

  • Need to order 2 crossconnects, once we get the approval.
  • We're using layer 2.
  • Change: Add a VLAN to the machine.

Action item

Guillaume to send extra paperwork.

Longer-term planning

Our only planning document is the budget, which only looks forward a year at a time, and only mentions projects that have expenses.

Points mentioned during discussion

  • Some OWG work does not incur expenses.
  • Grant has been asked to create a document detailing resilience/back-ups and failures scenarios, including human factors. Intended for the board.
    • Happy to share the document.
    • Does not replace a planning document.
    • The GitHub tickets are not substitutes for a plan.
  • There will probably be no great debate for the technical content that a planning document would include.

A long-term planning document could include (examples):

  • An item for maintaining hardware
  • Discourse
  • Containerisation
  • Method for building Debian packages
  • Moving to Debian
  • Removing the code that is built by Chef

Action items

  • Paul to start an open document listing goals for longer-term planning.
  • Paul to talk with Craig who offered to help with longer term planning.

Dorothea's questions

Is the current level of details in the minutes what the OWG wants? (more/less?)

  • Happy with current level of details.
  • The group hasn't reviewed them.
  • Dorothea to publish them and link them from the OWG site, to give people an insight of the OWG's work.
  • For previous ones read, the details were fine to understand them.

In case there would be a decision for a reduction of her time for the working groups, what would the OWG like her to prioritise.?

  • Reduction could be done in publishing the minutes for external people, if it takes much time.
  • The OWG has administrative assistance in its budget, so if the board decides for a reduction, they would get the work through someone else.
  • Helpful: minute taking and reminders.

Dublin

  • Grant might reorder some stuff.
  • Check if Equinix have charged us for doing nothing.
  • They cancelled the work-order on the incoming delivery.

Power upgrade

Action item

Grant to create ticket for removing some of the power limits. https://github.com/openstreetmap/operations/issues/884

Action items

  • 2023-05-04 [WordPress] Grant Slater to disable all users on not active sites. [Topic: WordPress security] Pending
  • 2023-05-04 [WordPress] Grant Slater to scale back user permissions, particularly translation users. [Topic: WordPress security]
  • 2023-05-04 [WordPress] Grant Slater to share list of WordPress users with Dorothea and their response to keeping an account. [Topic: WordPress security]
  • 2023-05-04 [WordPress] Grant Slater to try the primary 2FA WordPress plugin. [Topic: WordPress security]
  • 2023-05-04 Grant Slater to go through the HE.net prices. [Topic: HE.net go-ahead?] On 2023-05-18 agenda
  • 2023-05-04 Tom Hughes to open an issue on streets.gl GitHub repo, ask them not to use editing API for pulling relation data and point to our usage policy. [Topic: Streets.GL]
  • 2023-05-04 Grant Slater to talk to Tom about changing the AWS keys. (low priority) [Topic: Reportage - AWS]
  • 2023-04-20 Guillaume Rischard to ask people on Discourse for comments on a draft a policy regarding adding editors to the editor menu and provide context. [Topic: Reportage - Draft a policy regarding adding editors to the editor menu]
  • 2023-04-20 Grant Slater to create a Github ticket about a draft a policy regarding adding editors to the editor menu. [Topic: Reportage - Draft a policy regarding adding editors to the editor menu]
  • 2023-04-20 Grant Slater to politely email OPNVKarte and make them aware of the problem of the layer not updating. [Topic: Featured layers not updating - OPNVKarte is failing to update]
  • 2023-04-20 Guillaume Rischard to confirm with Gary regarding the technical details, plan for switches, book remote hands, make plan for IP addresses, DNS, prepare the change. [Topic: Go-Ahead for HE.net networking?]
  • 2023-04-20 Grant Slater to send an announcement for the upcoming maintenance outage. [Topic: Scheduled outage]
  • 2023-04-20 Grant Slater to write a high-level document of what would happen if one of the data-centers caught fire and a sketch of what investments would be needed if we wanted to improve the different tiers. [Topic: Scheduled outage]
  • 2023-04-06 Grant Slater to create a ticket for monitoring AMS RAID controller batteries. [Topic: HE.net]
  • 2023-04-06 Tom Hughes to ask Martijn van Exel to clarify if he meant that the link would be to an external website. [Topic: Adding Rapid to editor menu]
  • 2023-04-06 OPS Guillaume to draft a policy regarding adding editors to the editor menu. [Topic: Adding Rapid to editor menu]
  • 2023-03-09 Guillaume Rischard to try to provide options for 1G connectivity for AM6 by the next OPS meeting. [Topic: Network Upgrades]
  • 2023-01-12 Grant Slater to experiment with Netbox. [Topic: Asset management]
  • 2022-12-15 Grant Slater to produce a pull request and finish the OSQA one. [Topic: Containerisation of small services https://github.com/openstreetmap/operations/issues/807] # 2022-12-29 In progress.
  • 2022-07-14 Guillaume Rischard to ask Brian Sperlongano about OpenMapTiles and YAML, to do a test run. [Topic: Vector tile status]. # 2022-09-22: Suspended for a while. Brian is back at school and has no time to work on this. Guillaume will try to move vector tiles forward with someone else. # 2022-12-29 Still suspended.
  • 2020-12-02 [AWS] Grant Slater to develop some thoughts on what is next for us using AWS. [Topic: AWS] # 2021-05-19 & 2021-06-02 & 2021-06-16 postponed for a few weeks. # 2022-12-29 In progress.
  • 2020-07-29 [AWS] Grant Slater to enable background sync to AWS S3. [Topic: Ironbelly] #2020-08-12&26 & 2021-06-02 Manually run, automated scripting to be added. # 2021-05-19 Grant to run the script again. # 2022-04-09 Still manually run. # 2022-09-22 wants to make sure there are absolutely minimum permissions. # 2022-12-29 In progress. # 2023-01-12 Still manually run. Grant to look at the policies together with Paul.
  • 2020-07-01 Paul Norman to create a ticket about solutions to reduce incoming communications. [Topic:Revision of acceptable use policy to reduce incoming communications] # 2021-05-19 decision to leave the action item open. # 2021-06-02 discussion about priority for account deletion. # 2022-04-09 Grant can show Paul how to do that with autoresponder which Tom built. Might be better to work on an online form (action item below).
  • 2020-07-01 Grant Slater to work out some of the questions for an online form as a solution to reduce incoming communications. [Topic: Revision of acceptable use policy to reduce incoming communications] 2020-08-12 need to think about the reply # 2021-05-19 decision to leave the action item open. # 2022-04-09 Grant is thinking about examples. Suggestion to add what is considered large for tile usage.
  • 2020-04-10 Grant Slater to work out a table of different data bits, work out how they are backed up and what can be potentially improved. [Topic: High Availability / redundancy of OpenStreetMap.org (and primary services)] # 2021-05-19 decision to leave the action item open. # 2021-06-02 pending.

Meeting adjourned 66 minutes after start.

Next meeting

Thursday 01 June 2023, 19:00 London time, unless rescheduled.

Operations meetings are currently being held every two Thursdays, at 19:00 London time.
Online calendar showing the OPS meetings.

Retrieved from "https://osmfoundation.org/w/index.php?title=Operations/Minutes/2023-05-18&oldid=10994"