GitLab Speed Runs, 28 May 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Speed run of new ECS auto deploy feature

Description

Trying the new ECS auto-deploy feature out blind using just the docs.

https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/#auto-deploy-to-ecs

A

You were scared, I'm, the product rector for CIC. You get that I want to record a quick demo of the new feature that we have to deploy automatically to AWS. So I'm I've got a couple things set up on my screen here, which I'll share: okay, hopefully you're, seeing this and I've got so. This is the new feature. The auto deploy to ECS feature.

A

All I've done so far is privately is set up these variables in my project here, which I can show you just that they're set. Let's.

B

B

A

Variables, yeah, and so the only thing that I've done is set these three variables, which says that it's required and then my easiest deploy automatically you built so reading the instructions. It actually does. Look like there's another step. That's not mentioned there, which is this one set the auto DevOps platform target to ECS. So let's do that.

A

B

A

Need to be protected or masked, and that's fine, okay, cool. Normally, you would associate these with environments, but I'm just going to do it be doing everything in master here. So, let's see what's needed so in your project, blah blah blah specify which AWS platform or target this variable ECS.

A

Okay, so we're going to need to enable auto dev. ah So what I need is something that's just like a you know. Like hello, our observer engineer.

B

Simple web server, simple web server container doctor.

B

A

Is there a doctor.

B

A

C

Not seem to be a doctor file.

A

A

Yeah worst case, we can make our own.

A

Yeah- let's maybe just do that mmm there may be a little bit of iteration here, live which is okay but I. Don't.

C

A

Have the dockerfile syntax memorized? Maybe we've got a template here. Actually.

A

Http server, hey great, let's add this file and then we can add just like an index that HTML as well, so it's actually gonna copy. All of this stuff I think the way that that that is set up, but that's okay. Let's add.

B

A

Okay, that's about the simplest HTML that I can think of all right, so we got all of our stuff here. Let's enable our device and see what this thing does default. Our DevOps pipeline genius deployments production sure this is cool little notification here and that's relatively new I think all right. So it's doing stuff we've got a docker file, so I should be building that I. Don't know what it's going to test, but it will try to do something.

A

Well, pretty cool! Well, let's actually head over into the pipeline view where we can see more detail, I guess it figured out. All of these things are not available, but it looks like production. Gcs is so that's really cool I'm excited to see what this going to.

B

Do we can follow along.

A

With the things that are in progress, you.

B

A

Think we need this anymore.

A

B

I'll keep the docks open just just.

A

In case we run into any trouble, I've got my eighth Amazon cluster manager over here on the other screen at yet another computer. So I don't accidentally expose any credentials or anything like that. It's actually my own personal credit card, but we'll see what happens.

A

I'm monitoring over there for the new hosts to be added.

A

So far, nothing really going on all right looks like our container build is underway.

A

Test is doing something.

A

It looks like it's: no, it's running the copy, we've built it and now we're pushing it to our container registry and it succeeded great okay. So now it's running all the other cool, auto devups automatic stuff.

A

The test failed, probably because there's nothing to actually test right here. Hopefully that doesn't cause us to not be able to then deploy.

B

Yeah but we'll see soon.

A

B

A

Run some secret scan has run so far, so good.

A

Looks like we're even getting some reports out.

A

This is a feature I've been excited about for a long time, bringing Auto DevOps and all this cool stuff over to more more kinds of users, and if you can use this free, CS and the plan is to add more AWS services as well as well as other non kubernetes, GCS and Azure as well. It opens up. Is this cool feature to a whole engine? You new areas see what code quality is doing nice and skinning.

B

A

Lot of the stuff is overkill for a you know, a single static web page served by httpd, but most actual real-world projects aren't aren't that simple, and so it's not really optimized for something that tiny in and fake, but yeah.

B

Still really interesting, it's cool that you get all this for.

A

A

Hopefully, this doesn't cause us problems. I I'm, a little worried that it's not gonna proceed to deployment because of the test that found, but well we'll see in a moment.

A

My other screen I'm, going to see if I can do a little bit of research to see if I can find like a simple, a simple example where we can have our own web server. That will pass the testing feature.

A

Okay, I did find a workaround, I can set a environment variable to be test underscore disabled and it will skip this test or skip that job. So hopefully we don't run into the problem and have to do this all over again but yeah. There is an issue to fix this, always failing when there's just a simple docker file in there that's happening. Actually it's scheduled for delivery this month, but it doesn't look like it's been fixed.

A

Yet I reported it actually, seven months ago, when I last tried to do an auto devups that walkthrough, let's see what it does, I guess in the meantime, I can go ahead and just go set that variable, because it's not going to at worst it's it's just neutral.

A

Trim doesn't need to be protected all environments, okay,.

A

This is taking some time.

A

Again, this is optimized for a much more normal project than just my tiny little toy example. Here, okay, it didn't unfortunately, fail because of this test. So let's go start another pipeline.

A

And then this one should not have a test job in it and it doesn't think so adding that variable and yeah. This will just take a few minutes again in the meantime. Is there anything else we can look at?

A

We can look at some more of the documentation. I suppose see if there's anything here so.

A

Your project could have variables plus Phi, which AWS platform yep. We chose DCs, that's done my credentials. Are there. We can take a look at this dock and make sure I didn't miss anything. Yeah I had a my cluster I had in my wait now. I didn't add these get lot, prefer I added the credentials, but I didn't add these okay.

B

It's gonna go quick.

A

Yeah this link says AWS credentials, but it's actually talking about some things. They'll be different here.

A

It actually doesn't even mention the ones that the the blog said that you needed to add. So I, don't know if those are well, they must actually be needed, so I, don't maybe they're just missing from the documentation or or something.

A

All right, well, I've, set up BCS I, set up a cluster I'm, not set up an ACS service test definition or database, but I don't need a database. Well, unfortunately, I'm have to do this in the other window, but I'll create a service EC, yes or gates, or a c2 task definition.

B

A

I'll just call it my seat use the examples here: machine platform version latest cluster test, cluster service name service.

B

A

Let's go ahead and start adding these while I, while I am doing the other thing. Yeah.

A

But wait I don't have a get left see. I am oh because I'm using Auto DevOps.

A

So how would I add these things.

A

It doesn't make any sense, it says it would work if I was including, but then it said earlier that you shouldn't it's not recommended to do that.

A

C

A

It says it's not recommended you include it, but then this page says that you should include it and if you did include it, then you could enter these variables.

A

Mm-Hmm I, don't know exactly what it wants me to do. Do in this case. Let me maybe just add them here and that that should also work. So okay, cluster is going to be test. Posture is what I named it and doesn't need be protected.

A

C

Service that I made is.

A

A

Type task definition, I called my task definition I.

A

Test efficient I'm looks over on the ACS console. It's telling me my task definition does not contain any expose ports. I. Think that's! Okay! For now,.

A

That's fine, we'll just deploy it. Ask definition is required okay, running into some trouble over on the Amazon side a little bit. Let me create a task definition.

A

All right, apparently I needed to do that at first, so.

A

The EECS console sorry, this is very boring to watch task definitions, okay, create.

B

A

A

I'll use faregates test definition is my task definition roles, optional network mobile task memory, I think one half gigabyte is fine and then quarter CPU. This is just tiny.

A

Hopefully, Apache can start in half gigabyte it should it's just a tiny little webserver.

A

Okay, it's create container list cannot be empty, alright, add a container container name. It me.

A

So I need to add the image.

A

But so if I go to the convenience tree.

A

Let's just copy this.

B

A

Alright and create our task definition: okay, we have a task definition, definition now and now: let's go ahead and go back and create the.

A

The cluster I'm, sorry, the.

B

A

Within the cluster.

A

Great service, just definition: okay, now I can choose my test. Definition cluster test cluster service thing. What did I name it? My service.

B

A

Do not do auto scaling just in case I. Do something terrible I don't want to get charged for any of this.

A

So it's creating my service now, let's see actually what's going on with this pipeline.

A

Okay, it's actually on the deployment step, so I think that it's going to have beaten.

A

Well, we'll see you finish this first Amazon or or this starting up. This container I'll go ahead and start another pipeline running in the background, so that we don't have to wait for it if, just in case this one to get, doesn't work.

B

Go to pipelines.

A

A

Ecs update test official record service, not found exception, I'm assuming that is because.

A

That is because the it just quite hadn't quite been created. Yet so, let's go double-check our environment variables and.

A

Make sure that it matches what I see over here in the Amazon console, so the CIA WS ECS task definition is set to you my task that definition it has : one on Amazon, but I, don't know if that's needed or not I think that maybe it's just the version. Okay, it wasn't in the example so I think it's not needed. Cw CIA, WS e CS service I called my service, and that is what it's called there. Then e CS cluster is called test cluster and that is what I see in the ETS console.

A

So hopefully this time around the there won't be the timing issue and we'll get we'll get a deployment. The funny thing is: is that because I had to put in the container the past, the container registry.

A

Into the Amazon console in order to create the task definition it already automatically on its own, went and fetched that container and deployed it. So I actually don't know.

A

It seems like it's just going to be handling itself. So I, don't know what the deployment is going to do on top of it. Maybe the maybe I'll see maybe it'll become clear once it finishes, and maybe.

A

Maybe another way you could use this, it would be to like disable that Auto fetching and then only run the deployment when, when you want, but oh yeah, we'll see I'll see if I can find some way to actually reach this container.

B

A

So test cluster can.

B

A

Vp see some minutes.

A

Yeah I don't know that I've stopped my head. The easiest way to find like the public facing IP I'm, much more familiar with DCP stuff. These days, I'm sure it's here somewhere obvious that I'm missing, but I'll keep looking in the meantime. While our pipeline runs here.

A

C

Best I can tell everything.

A

A

B

Around this time,.

A

I'm just doing this well, let's running.

A

For lack of anything better to do, but what I'm trying to set up here with a public IP? Okay? So it's in the V PC settings but I, don't I, don't see that in.

B

Services I have.

A

My V PC service.

B

A

Okay, I have to be pcs for some reason.

A

A

Just want to find the public IP of this thing. It's not I, don't make it so easy at least we're getting close on the production to play here.

A

And again, me figuring out all this ECS stuff is not really the point of the main thing, but.

A

Maybe elastic IPS are what we want.

A

Okay, I have a public IP address. How do I associate it with anything? I, don't know, let's go see it elastic IP address with.

A

Yeah I'm just gonna, stop messing with this stuff. It's.

A

It's a little bit too much to learn to learn, live I'll, just release that IP address.

A

Yeah, it's okay, we'll just we'll monitor this! This is the main point, and hopefully now that we've added all the right information here. It's going to work.

C

A

Task definition does not support, launched hypergate.

A

Well, that would have been helpful to know in the documentation.

A

Okay, um maybe it was in the documentation, there's a specify that only works with ec2, not here.

B

You see, yeah, see, see No.

A

Okay, maybe I can.

A

Maybe I can re recreate it.

A

Great new revision.

B

Change it to ec2.

A

Okay, compatibility is easy to forget. It requires compatibility.

A

All right so I've changed it there to be ec2.

A

Let's try rerunning be running this thing and see if it works now,.

A

All right, let's see if I can change things anywhere else.

B

A

Just going to delete the cluster and remake it.

A

But I'll call everything the same. The same thing.

A

Cluster name, so we are gonna change, some more values here. So we'll come back to you.

A

B

I see the environment variables.

A

The cluster name will be something different.

A

So the cluster of ec2 clustering- we see yes close to him.

A

Okay, that's getting created.

A

We will delete my old task definition as well.

A

New task to finish in I'll choose ec2 this time.

A

I'll call it my dad passed, wait. You.

A

Will have the container again now so I need to go back over to Becky judges, dream sorry Daniel.

A

I'm reeling that we call it megabytes is not enough to our httpd, who knows we'll get a different air at least okay.

A

To be unable to add the container, for some reason, this isn't problems on the Amazon side.

B

A

Festive finishing is created so now I need to go back to the cluster and to the ECS cluster I need to add the service, an ec2 service, using my task definition to.

A

So this name is I. Think I called it my stylist, but let's go check.

A

All right so now I have a cluster ECS cluster, with my test definition on my service tube. So having updated these variables, I think I can go back here and retry this and we will not have anything that talks about foggy anymore.

A

We really should update the documentation to say the Fargate is not compatible because from the Amazon perspective for greatest part of ECS- and it seems like we're- we're not supporting that part.

A

Let's see what this does this time.

A

Well, I'm come on I, don't see this way, hey it's doing something. It worked awesome.

A

Cool so it looks like we got some J slime back with some of the details on the cluster. Hopefully no credentials in here.

A

Message was unable place tasks no container instance met all the requirements. Okay, that's yeah! That's probably just some some configuration on on my end, but it does look like this work demand so cool nice to see a fully green pipeline here and yeah a couple hiccups, but overall not too bad. We can. We can iterate and improve those things. So thanks for watching- and hopefully this helps show some of the new user experience with using this feature thanks.