[07:19:24] accraze: wow do you have a link for the feast example? [07:19:45] it may inform us very well about how the online feature store should look like [07:19:56] feast seems to be the only real candidate for us at the current stage [07:57:17] 10Lift-Wing: Workflow to upload models to Swift - https://phabricator.wikimedia.org/T294409 (10elukey) [08:20:52] 10Lift-Wing, 10Machine-Learning-Team (Active Tasks): Bootstrap the ml-serve-codfw cluster - https://phabricator.wikimedia.org/T294412 (10elukey) [08:20:59] 10Lift-Wing: Bootstrap the ml-serve-codfw cluster - https://phabricator.wikimedia.org/T294412 (10elukey) [08:26:09] 10Lift-Wing, 10Machine-Learning-Team (Active Tasks): Add an envoy proxy sidecar to Kserve inference pods - https://phabricator.wikimedia.org/T294414 (10elukey) [09:56:32] 10Lift-Wing: Factor out feature retrieve functionality to a transformer - https://phabricator.wikimedia.org/T294419 (10elukey) [10:07:22] I had a chat with Theo ealier on (many thanks!) and I got a ton of good info to work on, opening tasks :D [10:37:00] (will finish later) [10:37:02] * elukey lunch! [13:52:23] 10Lift-Wing: Implement an online feature store - https://phabricator.wikimedia.org/T294434 (10elukey) [13:52:32] opened --^ [13:52:52] IIUC adding a feature store to our infrastructure shouldn't be horribly hard [14:06:37] ok finished to open tasks :D [14:07:08] I think that we can mark what we consider mandatory for the MVP in the task title or similar [15:34:50] added request latencies to https://grafana-rw.wikimedia.org/d/c6GYmqdnz/knative-serving [15:35:03] looks nice (the datapoints are me trying some endpoints) [15:57:25] o/ [15:57:55] elukey: thanks for opening up all the tasks! this is great :) [15:58:14] also here's the feast transformer example I saw yesterday: https://github.com/kserve/kserve/tree/master/docs/samples/v1beta1/transformer/feast [15:58:45] it seems less scary than i was expecting [16:00:27] but also we may not even need feast for an online feature store -- something like redis sentinel could work too [16:03:01] accraze: o/ yes in theory we could also avoid feast, IIUC it is a very thin layer on top of redis for online, but it also gives a lot of metadata that we may need [16:03:17] the bit that I like is that is mostly client side [16:03:50] yeah that's a good point, the metadata stuff would be really nice to have