Hosting Total Cost of Ownership Squad

Product Squad Projects
1

Intro

Medic is pursuing reducing the total cost of ownership (TCO) of the CHT by trying to reduce disk space. This wiki is an experiment in using Discourse to greatly increase visibility and participation outside of Medic in this effort, and future efforts we’re calling “squads”.

Goal

As research has already been concluded, the current goal of the TCO Squad is now to ship a disk reduction feature in the form of CouchDB Nouveau.

Meetings

There’s a weekly meeting on Tuesday 7.00AM Pacific/6.00pm East Africa/8.45pm Nepal - anyone interested in attending is free to join the video call -

NB 1: the first meeting on Jan 21st will start at 7.30AM Pacific/6.30pm East Africa/9.15pm Nepal - This note will be deleted after this date passes to avoid confusion

NB 2: This time is currently pinned to 7AM Pacific which in the US changes with daylight savings time - please check here for updates on when the call is! (and maybe it shouldn’t be pinned to Pacific?!)

Meeting notes and recordings of the call will be added as comments below.

Related

For more information, see:

4 Likes
2

@antony @jkuester @sugat - feel free to add any info that’s missing above!

2 Likes
3

21 Jan 2025 Call

Attending

Notes

  • review parent ticket and sub ticket status
  • delegate outstanding tickets to the two engineers
  • there’s some concern that master keeps moving and the TCO effort is taking a while to get merged - need to keep master merged back to multiple branches as we develop. Development is branch of branch off master

Follow up

  • @mrjones - move this wiki to new forum section
  • @jkuester - log new issue to update CHT Core to use new library for free-text search instead directly using Couch as it is currently
  • @mrjones reach out to stewardship about helping out tickets to speed up delivery (too late for community membership support )

Call recording

4

28 Jan 2025 Call

Attending

Notes

  • review parent ticket and sub ticket status
  • mrjones - confirmed 1 Nouveau instance will work N instances of couch nodes - in the case of CHT Multi-node couch
  • Josh not concerned about seeing a new Couch release to test Nouveau upgrade to ensure it works
  • Possibly test a CouchDB upgrade as CouchDB master now has #5336 and #5335 - thinking is that we could test upgrading from Nouveau 3.4.2 → Nouveau Master to test upgrade in CHT
  • possible happy path for k8s would be using CHT Deploy Script? then others can extrapolate from there
  • Discuss on going PR

Follow up

Call recording

5

4 Feb 2025 Call

Attending

Notes

  • review parent ticket and sub ticket status
  • discussing this comment: I was reviewing the view query code and realized that the keyed freetext values are actually emitted whole and un-split
  • how to get current branch running in Docker? (eg npm run local-images...)

Follow up

Call recording

6

11 Feb 2025 Call

Attending

Notes

  • review parent ticket and sub ticket status
  • @sugat starting on Refactor medic code
    • this will remove a couchdb endpoint that User Man. Tool and cht-conf is using - the freetext view
  • still need to figure out how run mokhtar’s code in central branch to start it in docker compose
  • let’s release CHT Datasource ASAP (eg 4.18) with the backing of existing CouchDB pre-nouveau Views
  • discuss calling REST APIs or call CHT Datasource?

Follow up

  • @mrjones - Move Meeting time to 15 min later so it’s not as close to earlier meetings
  • @jkuester - figure out how run mokhtar’s code in central branch to start it in docker compose

Call recording

1 Like
7

18 Feb 2025 Call

Attending

Notes

Follow up

  • @mrjones - Move Meeting time to 15 min later so it’s not as close to earlier meetings
  • @jkuester - figure out how run mokhtar’s code in central branch to start it in docker compose

Call recording

1 Like
8

25 Feb 2025 Call

Attending

Notes

Follow up

Call recording

9

04 March 2025 Call

Attending

Notes

Follow up

  • NA

Call recording

  • Calls are no longer being recorded - please ask questions in this forum or show up on the call! We’ll strive to take good notes. Next call will not have a “call recording” section
10

11 March 2025 Call

Attending

Notes

  • Progress updates:
    • Sugat - cht-conf PR ready for review - cannot merge PR until the cht-core release.
    • Sugat - started on refactoring shared-libs/search. Ticket.
    • Josh - couchdb-nouveau

Follow up

  • NA
13

18 March 2025 Call

Attending

Notes

  • Progress updates:
    • New Couch version dropped
    • jkuester - couchdb-nouveau PR
      • Building, unit tests passing. Integration tests passing.
      • k3s integration tests still failing - will spin off new ticket for this
      • e2e tests failing - looking into it

Follow up

  • NA
1 Like
14

25 March 2025 Call

Attending

Notes

Follow up

  • NA
15

1 Apr 2025 Call

Attending

Notes

  • Review main ticket
  • “implement CouchDB Nouveau” PR ready for review \o/
  • noting that Nouveau communication is not authenticated or encrypted (TLS)
    • we’re not going to fix this per MVP effort
    • all containers don’t use TLS right now, so this is no worse
    • if this encryption/authentication feature is important, partners can highlight this
  • discuss authentication in “refactor shared libssearch to call cht datasource freetext search APIs”
    • solution: hack the types and force TS to work as we want
    • be great to have small suite of integration tests for search library workflow

Follow up

  • NA
1 Like
16

8 Apr 2025 Call

Attending

Notes

17

15 Apr 2025 Call

Attending

Notes

  • Review main ticket
  • Josh is very busy on all the things, but Tom’s PR and Sugat’s PR are high priorities
  • Sugat updates - making slow progress with the search lib e2e tests with WDIO
  • Tom updates - frustrated with sonar - move from 5 to 7?
  • Tom take on more issues as he rolls of prior ticket.
  • What extra docs should we add if any? Release docs will cover extra container and such, but what else?
    • architecture diagram - ticket
    • docker helper (eg list of containers) and other docker docs which list containers
    • other?