GitLab Incubation Engineering, 22 Oct 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Incubation Engineering MLOps -- Weekly Demo October 22nd 2021

Description

All demos: https://gitlab.com/gitlab-org/incubation-engineering/mlops/meta/-/issues/16

A

Good afternoon, everyone, this is another weekly knobs demo uh this week for this time for the week of october 22nd, and this week is a short uh one again, uh we are continue working with uh jupiter, notebooks, uh rich tits, so better uh dips for notebooks. We already have a mr prepared and the works mostly done at this point.

A

We are just figuring out some bureaucracy and how to include this into the code base itself, so a little bit a little bit of back and forth, but uh we also work a little bit on the improvement, so, for example, before we were not including svg's outputs like this one, uh for example over here, there's enough speeches somewhere, but this one is an svg output, and now we include it, so you can see it over here as well.

A

We do the same for latex, so latex was not being included before and now it is, and you can see the difference between a regular uh div on the notebook that you have over here and the one we are adding right now, so you can clearly see which is what it's called. What is the output data? What is new code, and so on and so forth?

A

um So, even though, we're still a little bit now slow uh on the progress fall because of of how, because we're reaching the point where it becomes it's beyond experimentation, it's more getting into the code base, uh it's a little bit slower, but it's moving uh steadily uh and we hope that soon would this be merged in already.

A

Meanwhile, uh what we are doing as a department now, the next next steps will continue on the exploration of how gitlab plays out in developed space, and one of the main components of the melodramate is the model registry. It's where we connected.

A

Where models are versions and where they are stored, they can be used to serve models as well, or at least it's kind of like the database for serving the models, and we want to explore how gitlab cicd connects better with the different vendors. We have right there out there, so we'll begin doing with this with the with an outflow. So if you have any ideas, you can just come into this issue.

A

We have worked already with some others uh with another one, but uh we want to see how area flow uh and git lab work together. Just a reminder that this is not about feature development. This is more of an experiment.

A

We intend to create a playbook where uh users can just select uh what are the components of their stack, and then we provide uh ready uh out of the box uh gamble files where they can just change the variables and connect between the different components and gitlab itself for pipelines, but this is not about future development. At this point, it's just about understanding.

A

uh Why are the different players on this area? uh What are each one's features and how can we connect to each one of them and so on so forth, um and that is actually it for this week so up next, we are wrapping up seven more, uh the integrating uh the jupiter div into the code base, and uh we want to release this very soon, but meanwhile we will be working on connecting it live and upload.

A

That's it for today see you next week.