Lab Review: Infrastructure Preview
1. Lab Review: Infrastructure Preview
In this lab, you were able to launch a complete continuous integration solution in a few minutes. You demonstrated that you had user access through the Jenkins UI and that you had administrative control over Jenkins by using SSH to connect to the VM where the service is hosted and by stopping and then restarting the services. Many of the activities that occurred in that lab were nearly transparent, and they used resources and methods that you'll learn about in the rest of this course. Examples of this include the acquisition and configuration of a network IP address; the provisioning of a virtual machine instance along with the installation of software on that machine; and the passing of default state information from the environment during the setup process. You can stick around for a lab walk-through, but remember that Google Cloud's user interface can change, so your environment might look slightly different. So here I am in the GCP Console, and the first thing I want to do is navigate to the Marketplace. So up here, I've already clicked on the Navigation menu and Marketplace is pretty much on top. So I'm going click on that. Now, I want to search for Jenkins. Specifically, the one that's certified by Bitnami. So I can just directly paste that in the search address here. Here we go. This is the one I'm looking for. So I'm going to click on that. Now, I can read all about this. There's an overview. It doesn't mean that function Compute Engine, uses a single virtual machine, when it was last updated. It talks about all the packages, the operating system. If I scroll down, I can learn more about the pricing. There's obviously, pricing associate with the VM instance itself. It does not have a usage fee. If it did, that would be displayed here, and you'd be billed for all of that together. There's a standard discharge, and then there's the sustained use discount, which we'll learn more about in a later module. So once I'm happy with all that and I've read through, I can go ahead and click on "Launch on Compute Engine". Now, it's going to present me with an interface here, where I could change the name, the zone, the Machine tab, a lot of other settings that are very similar to configuring a virtual machine. I can again, see all the Software, Terms of Service, the cost one more time. Once I'm ready to go, I can click "I accept the Terms of Services", and click "Deploy". So now, I'm actually in a different interface. This is Deployment Manager, we'll learn about this later in the course series, but the interesting thing now, is I can see the setup process. So there is an actual file here that has all the configuration in a ginger file. There is a VM that's being created. There are two firewall rules that are created. TCP for port 80 and 443. So that's HTTP and HTTPS. I can wait for this machine to now come up. There's also some software configuration. I can again, learn about all the software that is installed here. I can click on the VM instance to get more information about it. We can see the VMs instance is up, the firewalls are up. So the last thing that's happening here is the software is being configured. I can even learn more about that software. Here, I already clicked on that. So these are again, all the different versions that we can get to and engage. Once this is running, this table up here will be populated, all currently pending because this is still being initialized. Here, we can see that the instance is now ready. So there are a couple different things we could do. We have an admin user, as well as a password. So we can copy that. We could click on "Visit The Site", and this is going to open that in a new tab, that's navigating us to the external IP address. It's going to load, let's see it's the starting. It's part of the service itself, it's still getting ready to work. So you can see that the software in the background on the instance is installed, but it also needs to launch. So that itself can take some time too, and now it's up and running. I can put my username in and I can put the password in. I can click "Sign In". Here, I should be asked to customize Jenkins. There'll be some suggested plug-ins that I can install. Once I've done that, I can restart the instance. Deployment Manager and the G Suite Marketplace, will also give you some time some suggests next steps. For example, this password up here, it's just temporary. So we could go change that. The other thing we could do is we could assign a static external IP address so that when you visit the site, it's always going to be the same IP address, and that really helps if you have a DNS setup for this instance. If I go back here, I can click that I want to install the suggested plug-ins. It's going to do that. It's going to tell me where that instance is. I can save and finish, and I can go start using it. They should again now restart service. So here we are. So I can explore this a little bit. I could manage Jenkins itself. There are lots of different actions that I could perform here. I could also now, further administer the service if I go back to the Console. I'm looking at this deployment here. I'm looking Jenkins-1, I could actually SSH now to this instance. So let me click that button. That's going to establish now, an SSH session to the service. I can then actually shut down all the services by copying the command that's in the lab instructions. So let me just paste that in here and run that. If we go back to the Jenkins UI and refresh that page, we'll see that it's gone. That is expected because I have gone ahead and I have restarted that service. So what I can do now, is I stop them, I can now restart it by running the Restart command in here. So let's grab that and paste that in here. Now, the service should come back up. We might have to refresh the page a couple times for that to happen. So let's just wait a couple seconds, refresh it and see if that's service comes back up. My tab name has changed to Start in Jenkins. So it looks like that service is already coming back up right now. We can see that the service is getting ready right now. So at this point, we've completed all the task. I could now go back to the SSH session and exit out of here. Here, we see that Jenkins is back up and running. That's the end of the lab.2. Let's practice!
Create Your Free Account
or
By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.