 Hello, my name is Tim Cerowitz with the Linux Foundation. In this video, we're going to learn how to gain access to two cloud nodes to run the labs for the Kubernetes classes. The basic flow is, first, we're going to install Putty, then we're going to log in to the Google Cloud and deploy to instances. In a separate video, I will show you how to use Amazon instead, similar but distinct, either way, you would need Putty. Of course, this does work if you're from a Windows environment. If you're on a Linux laptop natively, which I hope you are, or a Mac, then you could just use a terminal and the SSH command. This video is definitely aimed at people using Windows as their local machine and then accessing the Linux systems online. The first step is to get Putty installed on our local Windows machine. Let me bring that up and then you can see I have a browser here and I'm going to go to Putty.org. Then where it says download Putty, we're going to download the two different packages. The first one is the Windows installer for Putty itself. This is the tool that we'll use throughout the labs to gain access to our nodes. I'm going to save that and then I'm going to scroll down and look for PuttyGen. This will help us generate the keys that we need or convert from a pen key to a PBK key, which is the type of key that we need to gain access to our nodes. I'm going to go ahead and download PuttyGen as well. Looks like it finished here, so I'm going to double click on the installer, allow it to run, go through the typical setup process. In this case, I also want to have a shortcut on my system as well for Putty just because I'll be using it, just because I'll be using it quite a bit and it's there. There's a finished page that shows you how to do stuff and more information as necessary. Now to get PuttyGen working, this is the basic PuttyGen information. Just go ahead and click on generate. Once you move your mouse, it's using random location information to generate this key. In the key component, we're going to swap that out and we're going to put the word student there. That's our username inside of our lab student. You could have a passphrase. For ease of use, I'm not going to have a passphrase in my case. Then I'm going to go ahead and say save private key. Are you sure without a passphrase? Yes, I'm sure without a passphrase. In this case, I'm going to put it on my desktop and I'm going to call this LF class and save. On my desktop, behind these windows, I can then find the new key. In fact, let's just go ahead and see if we can find it here someplace. There it is, LF class. Now that we have LF class, we can close up PuttyGen. Now it's Putty. Here's my desktop. There's Putty. This is what Putty looks like. This information, we need to get at least some of it from whatever our cloud provider is going to be. For example, the IP address. What we're going to do is let's go ahead and create something called master. I'm just going to call it master. I can click save and then by selecting it, I can load that profile layer. So master, I'm going to go down to where it has SSH and then auth, LF class, and then open and verify that indeed that PPK is showing up right there. Then go back up. There's other things you can change like how the title looks like. For example, I might put master here and appearance. You can change color. We'll probably do that on our secondary terminal. Go back up to session and let's save what we've made the changes. We will eventually need to put the IP address in here. But until then, let's go ahead to cloud console.cloud.google.com. Now the first time you log in, it will ask you a series of questions about your credit cards and paying for everything. So I won't go through that. That should be fairly straightforward. But once we've added our credit card information, the dashboard should look something like this. So the first thing we need to do is set up a new VPC. So upper left hand side, the menu area, and then scroll down to VPC network and over to VPC networks. When that comes up, you should see some default information. We're going to select the create VPC network button and give it a name like LF class, for example, for my LF class. Then name, give it a name like LF class, the region. Now I'd probably choose something close to me or perhaps something inexpensive. So US central, for example, the address range, other information. You should be able to just click on create at this point, and look, there it even stops me. So you need to put some sort of address range in here. So 10 dot, let's see here, 10 dot 2 dot 0 dot 0 slash 24. That would give me 256 nodes in that network or I could do it slash 16. It's internal, so it's not affecting the outside world and then create. And soon I should have a class show up. Now that depends on a lot of things how fast it is, but eventually this should become bold and I should be able to select it. I'm going to select it and create a firewall rule. It's taking a while, so let's go over to firewall rules. So we're going to click on create firewall rule. We're going to name like LF class for my LF class. Then the network, by now it should have popped up and there's an LF class. I just made that a second ago. Then we see ingress, we're going to allow and all ports and protocols. So in this case, you can say all instances on this network, the IP range and allow all. We have the zeros there to allow all and we have a new for class that is going to allow everything and it's over here, it should say LF class. So that's where our VPC is and we see that indeed we can also look at firewall rules here and all traffic is allowed on all IP ranges. Now that we have our VPC set up, we can go ahead and spin up a node. So we're going to go to compute engine and then VM instances will set up our master node and then a worker node. So we select create and we're going to give it a name like master. The location, that's the region that you'd like it to be running in. Of course, I just created my VPC in central. So central there, for example, then the series type, we're going to leave that as just kind of a general N1, then we're going to change this to be N1 standard two, which is two vCPUs and 7.5 gig of memory. We're going to change the disk. So click on change there and we're going to choose in Ubuntu and then in Ubuntu 18.04 and I'm going to make the disk a little bit bigger. We don't need a lot of space, but just in case, I'm going to up the disk to be 20 gig in size and select that. Then down here, it has management security, networking and sole tenancy. So under security, you select that, you'll notice it says enter the public SSH key. Well, this would be one of those places where we want to paste our SSH key. The putty gen is a way of getting that. So putty gen and let's try that. Let's try that again and load LF class open. And we can see here all the information that we need. We copy all of it and paste. So now we picked up that student that was in the comment field and then that way it will line up with what the lab exercises have. So then networking, we can see it goes to the default network, but we want the LF class network instead. And at that point, we can click on create. It should spin up an instance. The instance name will be tied to the, I should say the host name, is tied to the instance name. So we'll be able to see that when it comes up with an IP address. The IP address is right here, so I'm going to take that information and paste it into our putty information. So copy, put it under host name, paste. And again, it's the master setting. I'm going to go ahead and save it first and then open. Now it takes a little bit to start. So it may not be quite ready yet, but let's just see here. You know, I think we were faster than the node spinning up. It won't always update. So if it doesn't come up after a couple of seconds, go ahead and close the session and then start putty again. That's putty gen, putty, master, load and open. This time it says the server's key is not cached because we haven't connected to this instance before. And we're going to say yes, connect. And it says log in as, so log in as the username student. And there we are. We're logged in and we look at our prompts, student at master in this case, and we can continue with the lab exercise. Now we may need a secondary node. So we're going to come over here and select master. That's the name itself is a link. And there's a create similar option. I'm going to change the name to be worker. Just double check the end to is the size of two CPUs, 7.5 gig of memory, 1804 LTS. We see that under security, it has the same SSH key. And under the network, it is the same LF class. So we click create and that one should come up. Now we can leave this one running. You can see there's a right click on the terminal in here and there's a new session or save session, change session. I'm going to go ahead and start putty by itself. And I'll start off with master and I'm going to load it. But then I'm going to change this to be worker and then save. So now I have a master and a worker. And I'm also going to change the colors just so that I can keep them distinct from each other in a little easier way. So cursor text, we're going to modify that to be some sort of red color there. OK, and now that that's we have a color set, we're going to go back up to session and we need to swap out the IP address. The new IP address is up so I can go ahead and use that copy first. Copy, paste, and let's save it and then open and see if it works. Again, we haven't connected to it yet. So yes, I'd like to connect in there. And we see now we have a new session against student. And if you look, the prop says worker. So student worker, student at master. Now, the as you type, it should have been a different color. If it's not what you want, you can come in here and go on change settings. And you should be able to change the colors and some of the other settings. You know, the student, a worker, student, master, there's different ways of doing it. But I usually like using colors. I'm not sure why it's it's not using the color that I'd like. So modify and red, OK, apply. The product is changing, but the text isn't something I'll have to look into. But at this point, then I can use them as much as I'd like. When you're done, don't forget to come in here and select all of your nodes and then delete. So it says it will also lead to two booths. That's important. We want that. We don't want to be paying for any storage. It'll take a little bit to shut down. In the meantime, you can go to billing and see more information about how much is costing you and make sure there's not being charged for anything else. You can always come back in here to Compute Engine and then disks. And hopefully those will get shut down there shortly so that I'm no longer using them. That should get you started in accessing the labs for Google Compute Engine for the LF classes. I'm also going to have a video on how to use Amazon. Thanks very much.