[MUSIC] All right, in this video I'll cover the course steps of installing PowerVC. In this agenda I'll cover the first three items that gets us through the installation in the review of the logs. I'll finish the agenda in next in the next video addressing, updating, and upgrading PowerVC, which upgrading related to the installation and updating as a post install task. You have to get the PowerVC software though first in order to install. So here you go. Head to the IBM entitled Software site. It's there on the screen, right? So you want to navigate there. And while it's possible to navigation can change once you're in there overtime, once you get to that site. Generally what you're going to do is you're going to sign in with your IBM ID. You're going to select your entitled software. It's usually called my entitled software. Over the years, it's that's pretty much stayed the same. You'll select software to download, right, software downloads, is generally something like that. And then you'll look for a product tab, somewhere in the in the interface and then you'll look for PowerVC. Now as of the recording of this video, that's that's product number 5765-Victor V Charlie C Charlie C. So 5765 VCC. He followed the instructions to begin the download and soon you'll have the PowerVC tar file on your system. Now to extract the contents, I like to make a directory where I keep the software and then we use the Tar command you see in the graphic to extract the contents. And by the way the process to extract the PowerVC software from shift media is very similar. You need to mount the DVD and then untar the file. It uses the same name as what you see in the graphic, and you're going to get that from the root directory of the DVD. So let's move on now to having to prepare for the installation right. You have the code now, so let's prepare a Red Hat Linux repository where PowerVC's installer can get the prerequisites. Now I've covered these steps, may not have been me, but in previous courses in this series I've covered the steps in detail on how to do this. So I'm just going to provide a quick refresher here. This is one way to create a local YUM repository. You may very well be using a satellite server, or you may use HTTP or other methods. There are other ways to do this. So we'll start off by creating a directory on which to mount the realm media, okay and then will mount up that media. Moving on, we're going to create a repository file in the etc yum.repository.directory to define the repository. Here were mounting up and defining rhel77 repository and make sure inside that file that you specify enabled equal 1. The file is going to end in a .repo.repo. I'll note here that with rhel8 the process is a little different, but we've covered that in earlier classes and it is generally available on Red Hat's website. Also note that as of the recording of this video, Red Hat version eight was not supported as a basis for PowerVC. It will be someday, but not right now. Move on, you'll then check your work using the Yum repo list command. It should show the newly added repository in the output like you see in the graphic. If not, check your mount of the media and also recheck the syntax in your repo file. And then finally it's time to actually install the code, all right? So we're finally here, a script named install drives, the installation is not very original, but very easy to remember. It performs prerequisite checks, verifies that the prerequisite Yum repository is set up. Installs and configures open stack packages and databases and then it installs PowerVC and perform some basic configuration. Now important directory's to note are OPT/IBM/PowerVC, okay? You'll find logs, you'll find all kinds of good stuff in opt, IBM Power PC. And then also in opt IBM TTV-validation. That's TTV TomTom Victor-validation. The log files are in opt IBM PowerVC log. And this can be helpful if you encounter installation problems or if you just want to go back and have a look at what happened during the installation. Similarly you'll have log file for when you do an update or an upgrade. And we'll talk about that in a later video. All right now, the install script does take flags that install script takes flags. And I want to show you the syntax because the syntax for the install command is hard to find. It's not well documented. Now if you're doing an install, you can simply use the -H flag to see the latest syntax, but I'm going to kind of guy, I want to see the syntax ahead of time before I even get the code. Okay, so you see the syntax in the graphic. Now, in addition to the -H, you want to pay attention to the -C, as you will probably want to let the installer set up the firewall on the PowerVC server as required by PowerVC. You can specify not too and then do it as a post install task if you so desire. You have to have that done our PoweVC is not going to communicate with the outside. Also it can be helpful to use the -t before you do the installation to check prerequisites. The prerequisite checker does run as part of the installation process. But again on the kind of guy likes to know these things ahead of time. And then finally you can bypass the menu, although it's a very simple menu. So I generally don't bypass it, but you can specify -s for silent mode specifying either standard or cloud as the installation. As the installation that you want done, standard and cloud being the two types of PowerVC we see that you can install with this tar file. And then finally there's the minus you uninstall flag. Use this flag when your installation has failed and you want to clean up to prepare for retry the installation. Note this is not an uninstall of PowerVC once it's been installed. This is a clean up of a failed installation. All right and note in the graphic that you have to navigate to the install script location. It's not at the root level of that are extracting that can be kind of confusing. And then you simply invoke it. You pick the addition, you read and accept the license agreements, and then you follow along with the installation. It's just that simple. If you have prepared the systems as I've described, you're going to see a successful installation now. If not, you might encounter errors during the installation. You'll see them come across the screen and you'll definitely see them in the log. One example of that would be if there's a problem accessing the rail repository, okay? Maybe you've set it up and then you went away, came back and something happened to disable it. The installer is going to report an error and you'll have to fix that. The installer also reported error if the IP address is not an ETF zero. It's going to flag that and it's going to recommend that you set the HOST_INTERFACE environment variable. That's all caps HOST_INTERFACE with the interface that has the IP address on it. And then once complete, you'll see the message in the graphic, including the path to the install log, which is nice to have. That's handy, and that's it. You've installed Power BC. Congratulations! There are not a lot, but there is more to do and I'll describe that in upcoming videos. [MUSIC]
