GitLab Distribution Team Demos, 29 Jun 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Deploy Praefect with Helm 2020-06-29

Description

https://gitlab.com/gitlab-org/charts/gitlab/-/issues/1610

A

Hello and welcome to the distribution team demo for June 29th I've been working on getting prefect working in the charts, so I will demonstrate where I am with that right now, I do have a proof of concept working. It's not actually in the charts, the hell charts, but it is in kubernetes. So currently I've got a standard install up and running using this top configuration right. There everything works.

A

It's fine I haven't created angel I'm, going to migrate to prefect, and that is going to delete the existing giddily instance and that would include any repos, so I haven't actually things to install.

B

First thing you do is being able to.

A

Connect to an external Ghibli instance.

A

That's it's everybody's watching, I'm tightening, horribly.

A

So this will disable the built-in giddily and then I just have a llamo file with everything to apply once giddily is gone from the running instance down here.

A

Someone like watching paint dry.

B

A

To talk about this I use this: uh this is a shell script. I'm gonna create the conflict map which opens we'll create the critics configuration file and then protect em all contains multiple stateful sets, independent of each other that will eat you get at least a full set of all the statements that are created itself.

A

So there you see the multiple Gilly 1, 2 & 3 being created as well. It's perfect one down below that's currently airing, probably because there's no good Leesville for it.

A

All right research done folks there we go Oh.

B

See what's down.

A

All right so pretty thick, it does require a database and I forgot to do that. Step.

A

Argentine steps in.

A

B

A

First, we create the creative role.

B

Passwords that nobody can steal.

A

And then I will create the database.

B

That should do it.

A

You just divorce. We start immediately.

B

B

A

A

Configuration says.

A

Just pray sex is the name, but the documentation says pray picked, production.

B

A

All right next step, log on to prefect, we need to run the migrations.

A

Ask you a little thing and talk.

B

To database all right.

A

There's nothing fun, I agreed now we're all set, and then the next thing to do is to check out see they can talk to all different nodes configure to talk to but success there. So that is what we want to see. So now we should have get away in prefect working.

B

So it's filling the connector like Italy.

A

Not seeing the server version or the gate version.

A

Tried bouncing the webservice.

A

I see the problem: Court is wrong. Gracyk runs on 2035.

A

A

Carry that over.

C

While we're waiting here again, could you tell us a little bit more about the rigged file that you're using? Oh, this.

A

Is a personal thing that I use where I automate everything I need to do so? I have like the Helms like a new rake helm, upgrade release to install the latest release, chart version or rake helm, upgrade repo to upgrade to the latest version of Maya. Whatever branch I'm currently working on break helm open will open the curves that configured URL and copy the root password clipboard, so I can just root I, don't think it's currently open because at one point in time, I committed a key by accident and haven't yet gone through that clean.

A

The history and I didn't revoke the key, but still want to just the extra paranoid. But I will do that sometime in the near future. If people are interested because I do I think save a lot of time, I can easily spin up a chart or install a cluster either I'm gonna bus just use my personal rake tasks in my own personal settings.

D

Be sure that at some point I'd be great yeah.

B

So I'm just waiting for the new web services to come up and the other wants to go away.

B

A

I can at least show you. This is what I have put into my rake file.

A

So it is handy if I can just delete my cluster and if I do rake em upgrade release, it will spin up the cluster and make sure I'll have all the repos out of my home configuration.

A

That does save me some time.

C

It's pretty cool. It's a little bit like an Amish fishing team. She became.

A

Yeah, probably about 75% of these actually work and the rest are kind of there and neat finishing off, or they do part of the job.

A

And that's a lot better, so there we see that it's talking to it see the two version: good version.

A

It should do the right thing from here since we're just using a default. But this is the only historic that we have configured, but you didn't have different storage paths and we haven't dealt with.

B

And now let's try creating a project again.

A

Good activity, let me see the project exists.

A

That's all well and good.

B

A

So there we go, some basic get operations are working as expected, which is great news. I haven't tested much further than this. Just some basic functionality confirmed working, so I figured well we're all watching. You can get rid of the pod and see what happens.

A

B

A

A

Don't see any way to check to see you.

A

Perfect is very chatty and I haven't done a great job. Cleaning up a great logging system, so I can find out more stuff. I.

A

Would like to know who the current primary is. If that's in the prefect docks.

A

Just trying to do.

A

That's not that I didn't notice. Not she try to do failover is to say.

A

A

A

And change this to true.

C

So we didn't get a failure in the UI, but the pod you deleted was the primary yep. Did your change just get black hole he's like basically, what happened check that out? No.

A

Shouldn't have that last flew there blue still there. That would be an interesting case to follow up when I figure out. Why that worked.

C

Yeah from the logs it looked like, maybe prefect was likely trying the transaction it's possible. The pod hadn't finished terminating. It.

A

So I guess instead of I'll leave this here but I won't. We start pray sect.

A

Instead of just deleting the pod, we set this zero.

A

You sure the pot is not running and then I'll do it.

A

One is gone.

A

And now we're getting a 500 which I think there's no I'm lying. What I would expect.

A

And now it's on okay, so this isn't so I think probably the pod was not finished terminating when I did the they really will commit. Now it's perfect, oh so she yeah.

A

See what happens it fills over on startup, rather than bring the the first, the primary back.

A

Maybe doesn't want to start in a bad state.

B

A

I'll, try that with that size meant four minutes left. So let's try this quick.

C

Yeah, it looks like it had chosen the sec. The second part already as the primary.

A

Did you see that I'll put in the.

C

A

C

Could be the Walkman.

C

It's the second last line.

B

D

A

Two's going away so we should see, fell over.

D

A

Alright, so see subscribe, the only primary inch 3, it's nice to is gone.

A

Pilot status that who will lock me out.

A

Not getting 500, that's good news, Disney, really slow.

A

Now a fun project.

A

So that is a good data point. We are out of time. I. Think I will probably end it here, because I am interested in the growth meeting that is coming up next, but I think we learned and stuff and I have some more things that I need to dig into so.

C

Yeah thanks again thanks everybody for not exactly sure what what should be happening at this point.