GitLab Pods Group, 5 Apr 2023

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Cells: Iteration 1 demo - Sharing of Admin Area Settings

Description

This video shows results of Iteration 1. Those changes are currently merged into GitLab `master` and available when `main_clusterwide:` is configured.

A

My name is coming. I would like to tell you about iteration 1 of gitlab cells. What we've been doing for the last two Milestones when we decided to share admin area settings between different cells, you may be asking: what is cell soil is, according to our blueprint, is a set of infrastructure components that contains multiples of level 9 spaces that belong to different organizations.

A

The the main difference rating factor is like the cell is self-sufficient. You may come think about the cell, like a complete a gitlab instance running that has its own database. It has its own web server, side, key redis and every other component as part of the iteration one.

A

Our goal was like to share some settings that are currently stored in the postgres and some other data that are stored in the radius, so any other cell that was added would be able to fetch the data directly from cell 1., and this is exactly like the architecture that we end up as of now, basically cell one. You may think about the third one as a gitlab.com.

A

Basically, everything existing like a big GitHub about, and you can think about the additional cells like additional search that are provisioned, that fetch relevant data that they need from the main cell.

A

So the cell number one I'm gonna, be presenting exactly what we've been doing on preliminary Trends to GitHub compost kit, where you can provision easily managed cells and run them concurrently with a method we initially were thinking about, sharing only a very simple table application settings, but in the end we end up to sir significantly more than that, we decide we figure out to make it like a world file demo, we had to share appearances licenses, broadcast messages and application settings on today's demo.

A

I'm gonna show you how I am provisioning three different cells and setting broadcast message and some appearance that it's being shared between all of these cells per this diagram. You can see that, like we're, gonna, be fetching application settings license uh appearance and broadcast message from the third one which has like this third possible SQL database, but cell 2. We have its onset of the user and projects so we're gonna. Try to change admin area. Settings to see that they are populated, but secondly, I'm gonna.

A

Try to show you also that I can create a group answer one answer two and these groups that will not be shared between such because they do not share database containing groups.

A

Okay, let's start first with starting um a gitlab for the third one. While it is happening, I will start provisioning.

A

So two with creating new development environment with that command, I'm gonna be provisioning, a new database, everything required by this cell, but some postgres table will be fetched from the third one foreign.

A

uh Neo guitar and right now we try to connect to guitalele in order to provision a new database.

A

Great, so we did create a new account. uh It is enough for now we don't have to provision further. Let's do the same for server 3.

A

And why 33 is being provisioned I need to Force somehow to share the same root account, even though user's table is not shared today between clusters. But since we are sharing ready sessions as long as encrypted password and user ID and username are in sync, which is like the case for this gitlab setup, they can actually like session cookie, can be served between these git labs.

A

So what I'm gonna be doing now? I'm, just gonna update root with the same encrypted, password and disable password expiry, do not have to change this password folder great. So now, I can start web interface for decision number. Two why it is happening. Let's now wait for the server free to provision and let's do the same with updating root user foreign.

A

Now, let's update root user.

A

Is updated as well? Let's start web interface gitlab. Where is Puma personal number, three, why it is starting. Let's now just simply go to gitlop. This size is going to be running on different ports, but the third one is going to be running on the port 3000.

A

So 2 is going to be running on Airport, 3001 and 3002..

A

As you can see, we are right now locked in the third one.

A

Let me refresh so two since I'm, already unlocking the third one, the cookies are being shared and since Ready Set my session, the root user is also shared and I am here on the third tool. Let's see what happens with the sun free.

A

Great, we also have cell free running. Let's now go to adding area and change some messages, we're gonna, add hi. This is a message from web cell 1..

A

What we are expecting here is like that. This message is actually being present on Cell 2 and cell 3..

A

We have this message on the third one: let's now check, if we have this message on the server too,.

A

Great this message is also present on the SL2. Let's now check that this message is present on the cell free great. This message is also present on the cell free. Let's do the same for another change, which is appearance where we can add a photo message.

A

This is food, the message from server.

A

We can save this information, and this is what it's present. Let's see. Okay, this is also present on the third too I'm just gonna know go change these uh message from cell to because this is said: I'm gonna, write, footer message from serve 2, update appearance, and basically this is going to be also updated. Equal cells, as you can see, it's like the same, was updated.

A

However, there are only like these few tables that are sure that I mentioned, like appearance license versus and application settings, so any other change that I make on this cell is not really served. Let me show you that by, for example, editing my root user I'm, just gonna rename myself to become your shinsuke.

A

um So, as you can see, even though I am I have my full username here, if I go to try to edit my profile on the cell tool, uh this information is not shared. Yet this is something that we are planning to do as part of the iteration too. This is the same case for the iteration for the third three, that each of these databases.

A

Sorry, each of these search. They have a separate user table and only those mentioned tables are actually third. Now, if I simply go to create a group, this is exactly the same case.

A

The groups are not shared, it's amazing. So basically, it also means that, like group IDs, since they are not shared as well, they can produce a conflict group created from soil. One create group great, our group was created, and now, let's do the same on the third tool.

A

Group was created as well. You can, of course, do it from the cell free.

A

And basically, even though these groups are created separately, they are not really short across key clubs. I can only see groups that are local to this particular cell.

A

So this is really like what we've been doing as part of the iteration one. It's pretty much complete. We can read uh desert settings from cell one iteration 2 will simply try to implement user, can create a group on Cell tool where actual user exactly the same. The thing that I sound with the root account where I edit my profile would also be reflected the same way as I've been showing you with changing my profile, like sorry, with changing appearance or broadcast messages on on cell one.

A

Thank you very much for your attention. That's it.