All right, so now we're finally to the point where we can capture the VM to create an image. When I'm done, I'm sure you'll agree PowerVC makes this quite easy. At a high-level preparation of the VM for capture is the first step. Actually we have it here as the first two steps but those are done. We can check those off and move on to the last two steps. You want to get to the virtual machines to your PowerVC's homepage, select the VM to capture and that performance shutdown, I've mentioned this before. This is not necessary, but it is recommended at least by me anyway. All right, so when I can I shut it down, I think it's good practice. Now once the VM is shut down and with it still selected, choose the capture task. Dialogue is presented, you fill in the details and as I'll outline shortly here, and then you click capture again at the bottom of the capture dialogue. Then it's a matter wait for PowerVC to set up the metadata and the OpenStack databases interact with the storage device to start the copies and then to mark the image is active and your images then ready for you to use. Now I said that once you clicked the capture task, you'd see a dialog to complete. Well, that's not exactly true. You see this warning here first, its PowerVC reminding you that Cloud-init has to be installed prior to the capture, and you can also think of it as a reminder to shut down the VM if you want to. It used to be actually on older versions of PowerVC that captured when other VM was active would actually fail. That was changed, three releases ago or so as while back. The next step, when you get to that dialogue where you can actually fill things in, there's not a lot there you see. The next step is to name the virtual machine image. This, like the display names that I talked about before with the resources that you want this to be descriptive of the operating system, the version of the operating system, and I've even seen some situations where they put the root password and the description in PowerVC. Now you want to be careful of that. But in the cases where the root password after you login is going to be important, having that noted somewhere is important. You need to enter a name also that conforms to the naming standards that you see in the graphic, pay attention to that. Then you have to make a decision, okay. Now, do you want to capture just the boot volumes? Do you want to capture some of the data volumes as well? How variable is you're deployed VM going to be? In other words, do you have the need to deploy VMs that have the same root contents as well as some common data, data content or data volumes. PowerVC allows you to capture only the boot volume. You can capture the boot volume and all of the data volumes, or you can capture the boot volumes and only some of the data volumes, obvious set of combinations there. Keep in mind when PowerVC deploys this image that you can specify Cloud-init processing that alters the results in the deployed VM. You could say, for example, perform processing that removes data volumes when the deployment is done for just some VMs, not all of them keeping the data volumes for most of them, it's your choice. But after you've made those selections, the naming and the volume choices, then you click the capture button to continue. Now the next step is the point of no return. You see a confirmation dialog showing you the name of the VM to be captured, the name you chose for the new image and the volumes to be included. If this all looks good, click ''capture'' again, the capture's going to begin. If you want to change something could ''cancel'' backup and fix or start the process again, basically it start the process again. During the capture operation, the image makes a number of state changes. Basically, really what it does is it goes to queued and then it goes to active, and if does something different then you have some problems, we'll talk more about logs a little bit later. You'll get transitional messages that pop up on the bottom of the screen, and then you'd get a confirmation message as you see in the lower right corner of the graphic when the capture completes. You say to yourself, all right, I have an image, now what? Seriously now what do you do? Well, there are a few management operations that you can perform. We've talked a lot about using the image to deploy new VMs, and that's what you'll do with the images most of the time. There are two ways that images are used for that deployment. The first is by an administrator, and I haven't talked a lot about this in the videos that I've made about this, but, at the end of the day, PowerVC is either an administrator's tool or it's a self-service tool. It helps administrators to do their jobs more efficiently and more quickly, and it helps users get access to resources without the involvement of administrators. Administrator, self-service. All right, so administrator, simply click that deploy button and then they interact with the full set of deployment options. But let's say you want to set up the Cloud Manager for self-service deployments. The image aspect of that setup is to create a deployment template or deploy template. I'm not going to cover that in any detail here, it's fairly straight forward. Actually, it's very similar to dealing with the full set of deployment options, but setting that up as a deployed template rather than setting up for the actual deploy. That makes sense, right. But it's useful to know, it's useful to know that you have these two image management options. What you find is that, deploy template is presented to the self-service user when they attempt to deploy a new VM similar to the full set of deploy options when you're an administrator. Now the deploy template is set up by the administrator to provide a simpler view of the deployment dialogue. Importantly, many of the deployment options have been pre-selected by the administrator to put controls on what the self-service user can do. Now you can put the video on pause and have a look at this graphic. You're going to see it in the products so it's probably not that important that you really study this. But what I've done is I've put a blue box around the ones that I've described. Import and export options as well, and I've discussed those options earlier. Then of course, someday, most likely, you're going to want to delete an image. Now, I personally, I do that when I create a new updated image. I delete the old one and inform everyone that the new image is available with the new features and with the new name. Because again, remember the name is usually going to contain the operating system and the version, and almost certainly I'm updating the image to a new OS version. There might be other features get updated. You can include those features and the name. Note the option to delete or retain the volumes as well. They're noted in the graphic, that option is noted. Now it's something that I've discussed earlier, it's an option that you may or may not want to consider. You may always want to delete the volumes, but in cases where you have volumes that you want to retain, this is the way to do it. Then finally, it's unlikely, but you could encounter a problem when you're creating an image. So where do you look? What can you do to get even more information? Well, here I show you the log locations. Now these logs will be useful if you encounter problems deploying in image as well. This is more likely what you would see, but that's not going to happen very often. The first log covers the actions taken by nova processing to deploy the VM to the compute node. The second load covers PowerVC's overall scheduling actions. Here you would see potential problems handing off processing between the OpenStack components when the deployment probably is being done. Then finally, I'm going to close this lesson with an example of increasing the logging details. Let's say you were in the logs, you said it's not enough information here, but I can see where there's a switch, but I can't, and I see that the error occurs in the middle there somewhere, but I can't see what actually is happening. This is something you might do if you're not getting enough information in the logs and you're trying to solve a capture deploy problem. You run the OpenStack-config command on the two logs as shown in the graphic with the parameters as shown. Notice that you're setting nova equal debug to get that deeper level of logging. You want to remember to restart PowerVC services so that they're forced to access these new configuration file changes because this OpenStack-config command is actually changing those config files. That takes me to the end of the lesson for image and VM management. Thanks for watching.
