GitLab Incubation Engineering, 18 Nov 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Incubation Engineering MLOps - Update 2022-11-18

Description

New Features, MVP is complete, priority now is kickstarting testing and early user support

- Request for testing: https://forms.gle/pALYkCFbz9jZmfXU7
- Feedback Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/381660
- This Update: https://gitlab.com/gitlab-org/incubation-engineering/mlops/meta/-/issues/63
- All Updates: https://gitlab.com/gitlab-org/incubation-engineering/mlops/meta/-/issues/16

A

Hello, everyone and welcome to another update of incubation engineer and my labs at gitlab. My name is Eduardo and today is a is November 18th and we're gonna talk about what we're currently doing again, which is uh machine, learning, experience, tracking data scientists do a lot of experiments with their machine learning models and they have to keep track of the metadata of the artifacts and everything else, uh and we believe gitlab could solve this pain point for them, because it's already there and it makes it really uh easy for them to use.

A

So uh over the last few weeks, we added a few more features. First, uh now, if we look at it, when you look at experiments, we have a better UI over here with links to the artifacts directly from the experiment page. So you can see all the artifacts that were generated for that specific uh candidate. So, for example like this, we also have the details. Now this is a new page. We are adding, so we will be able to manage everything related to the candidate on this page.

A

All the metrics parameters and additional information- and the second feature that we are adding, is experiment in candidates metadata. So these are the ammo flow tags that we're ignoring so far, but now we're adding at least the back end for this. So while there's no UI to display them. Yet, if you use the tags, they will be saved and then we can add the UI soon, so we we will not be losing that data right. So with this two features we are done with the MVP.

A

uh So if we look at um we're done with the MVP feature, so it's already usable it. It already provides value to users and we are now focusing on testing.

A

We already started internal testing with gitlab teams, so more focused on setup on setup experience and on docs, uh improving docs and consolidating the docs for this feature, and but my focus now will be to Kickstart the external uh testing private testing of this feature so reach out to customers that want to test this. um Both are self-managed and that use gitlab.com, so I'll be reaching out to some.

A

And if you are watching this- and you want to test this feature out uh ping me on the on the issue for feedback, then I will, which is this one? Zero uh I will add this to the description of this video. But the issue is this one? So if you want to get access to this feature for testing now, you can reach out on the issue 381660, but I will add a link later.

A

um So it is a feature the MVP is complete. We are focusing on internal testing, but that doesn't mean we want to stop adding features right now, uh while we will be focusing on providing customer support at the beginning, so the beta testers will be focusing providing support to them. That's our priority. We will uh I expect to be working on candidate search, filtering and deletion. Meanwhile, so whenever I have a bit of time, I'll be working on candidate search and filtering, mainly, and that's it for today, thanks for watching bye.