[hma] Test production deployment - Nice-to-haves and Need-to-haves

[Dcallies]

If you would consider deploying OMM to your production environment to evaluate it, please add to this issue a comment with the following.

If you would rather remain anonymous, contact me by some other method, and send me the list and indicate that it's okay to add to this issue.

Need-to-haves

1. You won't attempt deployment without these things
2. Use numbered lists

Nice-to-haves

1. These are items you would be willing to wait longer on or try without them
2. Also helps if you use numbered lists!

[benoit-yubo]

Need-to-haves

1. A solution for rebuilding / refreshing the index in background or without service interruption. With the current demo, any existing index is loaded at start up and replaced when a manual index rebuild is done. In production, we could have curator instances rebuilding the index but we need a way to either:
   • have the matchers reload newly built indices asynchronously while still serving requests
   • have the matchers restart in a rolling fashion (easy in k8s, just need a trigger)

Nice-to-haves

1. Have the loading from exchanges implemented and schedulable (NCMEC, IWF, GIFCT)
2. Using FastAPI instead of Flask to obtain better performance would be appreciated, but it's my understanding that SQLAlchemy is not built with asyncio so that would probably mean using workarounds (or rewriting most of the Postgres queries) to really leverage the power of FastAPI.

[sbruens]

Must-Haves

1. Load exchanges (e.g. GIFCT) and configure them at runtime (i.e. provide credentials).
2. Image -> GIFCT matches, original source, metadata.

Nice-to-haves

1. Provide feedback on match.
2. Distance of matches (might be too hard)
3. Create new bank and add hashes to it.
4. Add ability to configure other classifiers

Will add more as we come across them.

[Dcallies]

Progress report 2/20/2024

@benoit-yubo

Need-to-haves

1. [Solution ready, needs validation] The option TASK_INDEX_CACHE=True which spawns local threads which pre-load and keep a live copy of the index in memory should solve this, let me know if this got it

Nice-to-haves

1. [Solution ready, needs validation] Support for this is now pretty robust, all exchanges in py-tx should be supported
2. No progress.

@sbruens

Need-to-haves

1. [Solution ready, needs validation] This should be ready, with CRUD for setting credentials at runtime
2. Not started

Nice-to-haves

1. Not started
2. Not started
3. [Solution ready, needs validation] banking CRUD should handle this
4. [Solution ready, needs validation] SignalExchangeAPI is supported, which APIs are available just needs to be set at install time

[juanmrad]

Need-to-haves

• Know which hash was it that it got matched against
• Distance between hash in bank and image hash
• Ability to configure distance per bank.

Nice-to-haves

• API to enable/disable signal types
• API to enable/disable hashbanks
• ability to contribute back hashes to exchanges