 Hello, we're back, all four of us. So, yeah, next up is the connecting to the cluster. I don't think I much need it here, but yeah, go ahead. Okay, let's start. You can definitely need it. So essentially up until now, we have been on, mostly on your machine, you haven't done anything yet. And you can see here this kind of image of the cluster and in this step, we are now going on to the login node, which is essentially the interface to the cluster or one of the several interfaces to the cluster that we will be presenting over the course of the next few days. We are not yet doing anything on the compute node. We are not compute nodes. We are not yet doing anything on the actual cluster. We are just accessing it now. So, I assume that everyone has gotten an account if you haven't followed that, follow that link after the course and get yourself an account set up. So, after that, we will demonstrate connecting via SH using a terminal. Terminal can be either of any Linux terminal or Windows PowerShell or even the Windows command line. All of them work similarly well. You know, if you could scroll it down a little bit. Yes, just a small announcement for you and for everyone else, I just had a collision on the VPN and internet connection. So, I'm hopefully not going to drop out for a very long period of time, but my connection is a bit unstable right now. But you do need a VPN. Oh, the VPN is very useful for connecting to the cluster. So, I will keep it on and I'll also show you how to do it without the VPN. But, okay, let's go on. So, if you could open a terminal since you are on the VPN, yes, this becomes a little bit easier. You essentially only have to type SSH. Let me just quickly clear up the screen. And now, yes. Now, we are taking the way that works when you are on the auto VPN. In this instance, we can directly say SH and depending if you are on an auto laptop or an auto desktop, you can simply say SSH tries.alto.fi. Yeah, in this case, it's all in fact not work. So, my username is actually not displayed here, but it often will be displayed in this prompt here, but I have made it simple. If you are on Linux, if you are on Windows, it's not. If you are on Linux, yes. On Windows, I assume also before my command doesn't necessarily work. I don't actually know. I am, well, that is my username, but that is not my username at Alba. So, this is my username at Alba. Well, so, if you want to be sure, you can essentially add your username with an ad and then try.alto.fi. Try.alto.fi, okay. So, SSH is a command that we're running and this is the name and the address that we are going to, the address of the server that we are connecting to. And I'll press Enter. And this will... Okay, what is this? Yeah, this is the first time connecting. All machines do have so-called fingerprints, which uniquely identify them. And if you try to connect to a machine, you want to make sure that it's actually the correct machine you're talking to because you will send some credentials over and you don't want to be kind of trapped in the wrong system. For Triton, the keys can be looked up online on the documentations. Do you know the address? Otherwise, I can just, if you can copy them over there. Yes, so I think I found the correct page. Yeah, the SSH fingerprints. And you can compare whether the one that is shown to you fits one of the keys here depending on which key it is and... Yes, so in fact, I'm seeing this one. And it's with six I and it is SHA256. So, well, this is something you will basically see only once the first time you connect. And if it's correct, you can type S. Essentially again, then for some reason, the fingerprint has changed. And one potential reason is that it's actually not the correct machine. So, more likely it's just changed for some technical reasons. But I would say if it shows up again, definitely check. Yeah, if it's the first time it is expected and I probably wouldn't care to check, but in practically speaking, but if it's not the first time you're connecting, then it's definitely worth checking, yeah. So, I'm connecting. And essentially, this is now connected to the login node. And that is kind of the most difficult thing to do, but it's a difficult step to some extent. That is the goal of this session. So, if you are not on the VPN, you can't directly connect to Triton. So if you exit this, if you're not connected to the VPN, you can't directly connect to Triton. You will need a so-called proxy jump. Essentially, there are a few machines in Auto that allow you to access from outside, and those machines then can access Triton. So, essentially, we'll have to log in twice. And the command is roughly very similar, except that you have a minus j, capital J. The first part is the same or the command is the same as this H, and then I give it a minus j. And then you use a name at, for example, kosh.alto.fi. Okay, let's go for kosh.alto.fi. So, that's another server that I can actually connect to directly without the VPN. And then, again, use a name at Triton.alto.fi. Okay. Now, again, this is... Now, this is for kosh. So, for kosh.alto.fi. And this is the fingerprint. Do you remember easily whether to check if this is correct or not? You can check it on the... If you go to the same page, there is a link at the bottom. If you're seeing the same as what I'm seeing, then it's probably correct. And that is the SHAR 2256. Yeah, that's the... Okay, that's correct. Yeah, so I will type yes. And press Enter. And, by the way, it also tells you permanently added. So, from now on, it will never ask again unless the fingerprint has somehow changed. Okay, and... Now I have a stupid question to you. Did you type your password again? Or... Oh, okay. Do you have a config on kosh? Yes, I do. Okay, don't worry. So, you can go around a lot of things by setting up configurations for Kosh also, for the SSH command. And that works the same on Windows, Linux, or Mac. Essentially, what it does is it allows you to set up certain hosts. It allows you to define... SH key files to use to connect instead of password, instead of using a password. So, essentially, you don't have to type your password again. And similar things. We are not going to go through the details of that now. There is extensive documentation on the documentation pages. We are now more looking at to if someone has problems connecting here. We will show one... Basically, if you tried SSH and you were able to connect everything is working, it would be probably a good way to spend your time to help others, or look through this SSH configuration file. And the advanced SSH information stuff. Yeah. It is linked under the SSH configuration file. Yes. But we will not be going through that. Yeah, what we will now do is there are multiple ways to connect to Triton. And one quite convenient way is to go over open on-demand. Open on-demand has a couple of tools that you can use to directly work on Triton. Can I ask, does open on-demand have a parallel to other clusters in Finland? I'm not at all sure, I think. Actually, maybe I can answer that better. So not that we know of. CSC has a similar thing on some of their clusters. But I guess the moral of the story is read your own site's information and see what they have. They might have something similar. So I guess someone could write that question into the collaborative document, into the notes and people can answer for their own sites if something similar exists. So should we or should I go? Yeah. If you just follow the link. Yeah. It will, you have to be locked into a VPN. I clicked on the link. I, yeah, I should be on the VPN. And you have the load. I might need to lock in again, but. Yeah. I was already locked in and it remembers the session. So, but this is the. The interface. If you have been using the other things, this is the same logging interface that you are using in most other places. And then you end up on this front page. On this page. The, depending on how large the screen is, the menu will look a little bit different. It can be a little wider. And you can't, yeah. So it's not a big difference. If you just want to have a terminal, there's the Triton shuttle access in the pinned apps. This, if you start, or if you click on that. Okay. It will essentially. It's asking for the fingerprint again. This is different than what we had previously, but this is one of the correct ones. Yeah, it's a different fingerprint. But the reason it's different is because it's a different protocol. True. Yeah. This is not. It's ECDSA and the other was ED25590. Okay. Okay. Don't explain to me what the difference is, please. I can't really at the moment. Okay. Well, it's again permanently added it to my known hosts. And here I am on Triton again. Yeah. And this is interesting though. This looks somewhat different. Yeah. Somehow the rest is missing. I don't ask me why. Well, don't get confused. Don't get any more confused than I am. Why I wanted to mention OD is because there's all, there are also a couple of other programs that you can run via OD, like RStudio, MATLAB, I think. Okay. Let's close this. So at least it's all available apps here where the pinned apps are. And also you can get applications listed here and all these, my interactive sessions has the terminal. So essentially what's currently available is Spyder for Python, RStudio, MATLAB, and Jupyter on Triton again. And if you go to the second page, I think there should be... Yeah. VS Code. VS Code run on a machine. The advantage of this access is that those are running on as an individual job. So all of these programs are running actually on the cluster and not on the login node. And since the login node is a shared resource, it running programs on the login node can lead to problems. And we sometimes have to kill some programs that are running there because they are making it very sluggish to login. To the course page and the image. Yeah. So basically we're all going through the login node. In fact, we're all going into the login node now. So whatever you want to do on the cluster side, you're always going through the login node. And well, that means everybody's there. So if you run something heavier on the login node, you're slowing everyone down. That's not the right way of doing things. How you submit then jobs to the cluster, to the actual cluster will be discussed later. And the thing with the OOD applications is that except for the terminal, which is again on the login node, they are all running on an actual node. So an actual compute node. There's at least one person asking or saying that it was unclear why we were using OOD. So should we maybe quickly demonstrate running some graphical thing on OOD? Okay, here it is. Otherwise I think we are done with the demonstration, right? Yeah. So I'll just run VS Code. I was kind of clicking through this relatively quickly though. So here I can ask for a single processor with four gigabytes of memory for hours. And it will run VS Code for me on the... On the queue, which essentially it submits a job to the queue. So your slur manager that we were talking about will start this as you see this going pretty quickly. It's already running. And now I can actually open it up. So since I'm using the VS Code text editor, this is actually quite nice. So this is your folder, your home folder. Yeah, this is my home folder and all of my projects and all of my files on Triton are here. And the same works with Matlab, RStudio, or Spyder. Yeah. So this is very convenient for editing files, coding, running stuff in RStudio, of course. And in Matlab you give this good run or... It's easier to run Matlab and RStudio using RStudio and the Matlab graphical system. And you can simply delete this job again. Delete this. Okay. So that's essentially the reason for showing OOD. Of course, the other reason is if for some reason running it on the terminal doesn't work, oops, that was an instance of Jupiter on Triton, but I don't think I opened it while you were looking, so I will just not show it. So yeah, but that is essentially the... If you could connect through the terminal, you're all set. If you have questions, either ask in the Zoom rooms or ask in the notes. Yeah. So if you are seeing this... Yeah. If you are at locking three, then you should be fine. You are set up for tomorrow or for the next sections. Yeah. So now we have a nice long break to let everyone get connected. And we know that this might be a little bit annoying because for some people you already have this, but some people don't and some fraction of people have big problems right now. So we can either leave a bunch of people behind or go too fast for... Or go too slow for a bunch of people. But luckily we're online. So you can have a 35-minute break. If it's working, you can start previewing the next part. Keep asking questions and come back at three o'clock or in the top of the hour. And what we'll do then. So there's two more final examples. So one example of what you can do once you're connected. So it's sort of an intro to this shell thing we see here that lets us do the inputs and outputs. And then we do some demonstrations of running stuff on the cluster, which is basically a sit back and relax. But all of this is really important because it's basically preparing for what comes tomorrow. So we want to give you... No, we... Sorry, I have a bit of an issue here. No, you don't need to eat me right now. It's okay. Use an attack mode. Okay, so basically we want to give you the introduction to the shell now. So when we talk about the cluster tomorrow, we're just talking about how to run stuff. So this will be partly homework also. So we give an introduction, you have some time to play with it and hopefully we can come back and then get to work right away. Yes, so let's... I'll put a notification of the break in the HackMD. And yeah, see you later keep asking questions. Okay, is that all? Yeah, okay, bye for now then. See you at the top of the hour.