GitLab Incubation Engineering, 4 Jan 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Incubation Engineering 5mp - Weekly Update - January 4th 2022

Description

5mp is now Cloud Seed ⛅🌱 https://hello.cloudseed.app

Cloud Seed is an open-source program lead by GitLab Incubation Engineering in collaboration with Google Cloud.

Deploying web application (and related workloads) from GitLab to major cloud providers should be trivial.

Cloud Seed makes it ridiculously simple and intuitive to consume appropriate Google Cloud services within GitLab.

00:00 Intro
00:31 Demo
00:41 Demo - Project Generation
01:39 Demo - Deployment Credentials
02:02 Demo - Deployment Pipeline
04:19 Recap
05:30 What's next

A

This is the weekly update dated january 4th 22 for the five minute production incubation engineering project.

A

After a two-week break for the holidays, the weekly updates are back.

A

Let's begin with a demo of everything that was built in the last two or three weeks and look at the current state of the project.

A

I'm a gitlab user and I'm creating a new project.

A

Let me create a project from template and I'll select. The node.js express template.

A

I give my project a name and I create the project.

A

This will initialize for me a project which is a standard node.js project which contains express js source code. Express.Js is a very simple web framework to create web applications.

A

You will see that this project comes with a docker file and the docker file exposes the web application on port.

A

I want to deploy this application so I'll, select the infrastructure, google cloud menu and I'll create my first service account. At this point. It's important to know that I'm also a gcp user.

A

I'm authorized and I create my service accounts.

A

If I switch to the deployments tab, I see cloud run and I see the option to configure cloudrin via a merge request which will deploy my container based web app on clusters managed by google. So let me just hit this button.

A

And this creates for me a new merge request, I'm looking at the form right now and if I look at the source code or the changes it has got, one commit and the commit contains a pipeline.

A

That includes the build test and something called cloud run deployment.

A

Okay, let's see what this does. Let me create the mr.

A

You can see the mr is created a pipeline is executing. Let's have a look.

A

As expected, it has got the build and test and deploy jobs. Built-In tests are standard. So let me just quickly have a look at deploy to cloud drum this job. Let's see what this does.

A

It seems to be running a script called cloudrun.sh.

A

What else can I find out? It seems to be running off a docker image that is in the incubation, engineering, five minute production repository and it's deployed my web application. Here's the url, let's have a look.

A

There you go my express web application deployed with just a couple of button clicks right from gitlab.com.

A

Now that we saw the demo- let's recap what we saw, we saw a new project being created in my gitlab instance for creating the project. I used the node.js express template that we have right now.

A

Once the project was created, I was able to fulfill the one-click auth promise by generating service accounts simply through clicking and navigating through. Once the service accounts were generated. I was able to create a deployment pipeline through the one click config promise. So I just clicked a button that said configure with an mr. It created a pipeline for me and the branch of the mr the feature branch the pipeline was executed and it deployed for me this node express application.

A

The user experience was ridiculously simple and boring press a few button do a few things and you have the simplest way to deploy a web application through gitlab.

A

All right, lovely, this seems to work. I'm able to create my service account credentials and I'm able to use them inside a merge request. So is it ready what happens next? Two things need to happen.

A

All of these changes that I demonstrated they live today in a feature branch called uh incubation, five minute production, google run configure cloud run, so it's a mouthful of a name, but all of these changes live inside a feature branch and these changes need to be split across smaller, mrs and they need to go through the merge process.

A

That means I'll have to refactor I'll, have to write tests and get them approved so that I can merge them into the main gitlab code base. Based on my past experience of service accounts, this could easily take a month, or so I would say month month and a half something like that.

A

Once that is ready, once everything needed has been merged inside the gitlab code base, we can talk about a rollout.

A

What I want to do is have a team of trusted testers, many internal, some external, that that we will invite. So there will be a google form where we invite trusted testers and in maybe next week or the week after in the video, I will elaborate more on that process to become a trusted tester.

A

But the idea is to have a bunch of contributors and trusted testers sign up so that we can release this feature for them privately to be a trusted tester, you need to be a gitlab.com user and you need to be a gcp customer uh and you can be a gcp free to your customer as well. That is not a problem. um You just need your billing account set up.

A

I will explain all of these details in the in subsequent videos, but the idea is that trusted testers will be the first to make use of this feature. They will make use of the feature on gitlab.com and once it is sufficiently ready, we will fix the bugs. We will write some documentation and we will work on a broader rollout plan. That's the rough direction for the next few weeks and months. It's going to be an exciting time have a great week.

A