WEBVTT 1 00:00.000 --> 00:05.130 So friends, as you know, throughout this course so far, we have had a dedicated 2 00:05.130 --> 00:06.000 control mode 3 00:06.000 --> 00:10.240 running Ansible. Pretty much this is just a Red Hat Enterprise Linux machine 4 00:10.240 --> 00:10.960 and we went 5 00:10.960 --> 00:15.360 installed Ansible directly onto it. Now, would it surprise you to learn that 6 00:15.360 --> 00:16.480 actually is another 7 00:16.480 --> 00:21.000 way to run Ansible and this is via the use of something known as Ansible Nav 8 00:21.000 --> 00:22.080 igator. And the cool 9 00:22.080 --> 00:25.890 thing about Ansible Navigator is that it's actually going to leverage the 10 00:25.890 --> 00:27.760 containerization technology. 11 00:27.760 --> 00:32.590 So you may recall in the prerequisite exam, the Red Hat Certified System Admin, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 11 00:27.760 --> 00:32.590 So you may recall in the prerequisite exam, the Red Hat Certified System Admin, 12 00:32.590 --> 00:33.120 we actually 13 00:33.120 --> 00:37.620 explicitly dealt with a subject of containerization. More specifically, we 14 00:37.620 --> 00:39.360 utilized a tool known as 15 00:39.360 --> 00:44.000 Podman. And if you recall, Podman allowed us to pull down container images. And 16 00:44.000 --> 00:44.560 from those 17 00:44.560 --> 00:48.970 base images, we could create container instances. Now realistically, this is a 18 00:48.970 --> 00:50.000 type of technology 19 00:50.000 --> 00:53.490 that we're going to be leveraging when we use Ansible Navigator. What it's 20 00:53.490 --> 00:54.480 going to do, 21 00:54.480 --> 00:58.950 it's going to provide us what is known as an execution environment. And as such 22 00:58.950 --> 00:59.360 , it's going 23 00:59.360 --> 01:03.110 to give us all the benefits of containerization that we learned about before. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 23 00:59.360 --> 01:03.110 to give us all the benefits of containerization that we learned about before. 24 01:03.110 --> 01:04.480 That said, of course, 25 01:04.480 --> 01:09.130 when we happen to run Ansible within this execution environment, things are a 26 01:09.130 --> 01:10.720 little bit different. 27 01:10.720 --> 01:13.520 So what we're going to do in this particular video is to walk through some of 28 01:13.520 --> 01:14.000 the basics of 29 01:14.000 --> 01:18.480 Ansible Navigator and set it up before running some playbooks within the 30 01:18.480 --> 01:20.240 execution environment. 31 01:20.240 --> 01:24.560 So what we're waiting for, let's just get to it by first going to the Ansible 32 01:24.560 --> 01:25.680 documentation. 33 01:25.680 --> 01:29.790 So all I've done is search for Ansible Navigator Red Hat and all I'm going to 34 01:29.790 --> 01:30.720 do to click this WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 34 01:29.790 --> 01:30.720 do to click this 35 01:30.720 --> 01:35.100 link right here, Introduction to Ansible Content Navigator. So let's just zoom 36 01:35.100 --> 01:35.760 in a little bit 37 01:35.760 --> 01:40.010 here. So directly from the Red Hat documentation here, it says that the Autom 38 01:40.010 --> 01:41.760 ation Content Navigator 39 01:41.760 --> 01:46.130 is going to allow you to develop things like playbooks, collections and roles. 40 01:46.130 --> 01:46.400 And these are 41 01:46.400 --> 01:50.270 going to be compatible with something known as Red Hat Ansible Automation 42 01:50.270 --> 01:51.360 Platform. Now, we've 43 01:51.360 --> 01:55.870 actually not seen the Red Hat Ansible Automation Platform. Pretty much, this is 44 01:55.870 --> 01:56.800 just a graphical 45 01:56.800 --> 02:00.480 user interface that we can use to effectively manage our automation system. We WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 45 01:56.800 --> 02:00.480 user interface that we can use to effectively manage our automation system. We 46 02:00.480 --> 02:01.200 will actually 47 02:01.200 --> 02:05.040 look at this later on within this very course. Now, with respect to the actual 48 02:05.040 --> 02:06.240 content navigator, 49 02:06.240 --> 02:10.550 we can have this run on local development machines, as well as our automation 50 02:10.550 --> 02:11.120 execution 51 02:11.120 --> 02:14.570 environments. Now, the automation content navigator is also going to produce 52 02:14.570 --> 02:15.840 things such as artifact 53 02:15.840 --> 02:20.070 files. This is when you run a playbook, it will actually return or rather 54 02:20.070 --> 02:21.840 create a JSON file that 55 02:21.840 --> 02:24.980 is basically going to give you some diagnostic information about what happened 56 02:24.980 --> 02:26.160 within your play. 57 02:26.160 --> 02:29.960 This can be good when you want to troubleshoot issues. Just be aware though 58 02:29.960 --> 02:30.640 that if you happen WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 58 02:29.960 --> 02:30.640 that if you happen 59 02:30.640 --> 02:34.650 to have these files generated every time you're in a playbook, then of course 60 02:34.650 --> 02:35.600 that is going to 61 02:35.600 --> 02:39.820 use up some space. So we do want to be aware of that and perhaps even disable 62 02:39.820 --> 02:40.560 it if we so wish. 63 02:40.560 --> 02:44.750 Now, one thing you'll notice about the content navigator is that it's a text 64 02:44.750 --> 02:45.680 user interface 65 02:45.680 --> 02:50.520 a TUI. Pretty much it's going to give us this menu-like feel directly from a 66 02:50.520 --> 02:51.600 thinner command line. 67 02:51.600 --> 02:55.040 So the cool thing is we'll be able to look at their playbooks, watch particular 68 02:55.040 --> 02:56.320 jobs, we'll be able to 69 02:56.320 --> 03:00.130 check out our inventory and have our inventory be read in different formats WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 69 02:56.320 --> 03:00.130 check out our inventory and have our inventory be read in different formats 70 03:00.130 --> 03:00.960 such as JSON or 71 03:00.960 --> 03:05.790 YAML or just INI, whatever it may be, as well as a whole bunch of other options 72 03:05.790 --> 03:06.880 . Now, you'll notice 73 03:06.880 --> 03:12.080 here is that we have two different modes of operation. The STD out mode, this 74 03:12.080 --> 03:13.280 mode here is pretty 75 03:13.280 --> 03:17.680 much going to present the output just like a regular Ansible Playbook would, 76 03:17.680 --> 03:19.040 whereas when we happen to 77 03:19.040 --> 03:23.290 run it in text, basic user interface modes, this is going to give us much more 78 03:23.290 --> 03:24.800 of a menu-like feel 79 03:24.800 --> 03:28.330 whereby we can explicitly navigate through that menu and select the exact 80 03:28.330 --> 03:29.920 things that we want to see. 81 03:29.920 --> 03:33.300 Now, some people may find this a little bit confusing the first time you happen WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 81 03:29.920 --> 03:33.300 Now, some people may find this a little bit confusing the first time you happen 82 03:33.300 --> 03:34.320 to use it. If you do 83 03:34.320 --> 03:39.600 prefer, you can just get that more regular outlook by using dash M to specify 84 03:39.600 --> 03:41.040 the STD out formats. 85 03:41.040 --> 03:44.560 Just something to keep in mind. So with that said, now we have a rough idea 86 03:44.560 --> 03:46.080 about what Ansible Navigator 87 03:46.080 --> 03:49.640 is. The best thing to do is to get it installed and then see it in action 88 03:49.640 --> 03:50.640 because that is going to 89 03:50.640 --> 03:55.490 make things much much cleaner for us. Okay, so I am back on my Ansible control 90 03:55.490 --> 03:56.720 node here. What I 91 03:56.720 --> 04:00.120 want to do is I want to check out my repo list right now. So if I say pseudo WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 91 03:56.720 --> 04:00.120 want to do is I want to check out my repo list right now. So if I say pseudo 92 04:00.120 --> 04:01.440 DNA for a repo list 93 04:01.440 --> 04:05.800 and to enter, we can see here the activated repositories that have my AppStream 94 04:05.800 --> 04:07.120 repository as well as my 95 04:07.120 --> 04:12.400 base OS. What I actually need to do though is to enable a specific repository 96 04:12.400 --> 04:13.440 in order to install 97 04:13.440 --> 04:17.250 Ansible Navigator because if I just say pseudo DNA install and I say Ansible 98 04:17.250 --> 04:18.480 hyphen navigator right 99 04:18.480 --> 04:21.870 now, it's going to check for this particular package and then it's just going 100 04:21.870 --> 04:22.880 to say we do not 101 04:22.880 --> 04:26.950 find a match. We are going to have to enable a very particular repository that 102 04:26.950 --> 04:28.320 actually houses 103 04:28.320 --> 04:32.770 this particular package. So recall we happen to register our system with red WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 103 04:28.320 --> 04:32.770 this particular package. So recall we happen to register our system with red 104 04:32.770 --> 04:33.680 hats. This allowed 105 04:33.680 --> 04:37.980 us to enable our repositories and download packages from dnf and the similar 106 04:37.980 --> 04:38.640 way we're going to be 107 04:38.640 --> 04:42.520 using the same type of commands, the subscription manager command to check this 108 04:42.520 --> 04:43.280 out. If I say 109 04:43.280 --> 04:48.590 pseudo subscription manager repos and I say dash dash list and to enter, we're 110 04:48.590 --> 04:49.520 going to connect to 111 04:49.520 --> 04:53.090 red hat and we're going to get a list of all the available repositories. So the 112 04:53.090 --> 04:53.840 very first thing 113 04:53.840 --> 04:58.300 that you will notice is that we happen to have a ton of options right here. You 114 04:58.300 --> 04:59.360 can easily drown 115 04:59.360 --> 05:03.690 in this. So what I would suggest you do is you actually use a grip filter. So WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 115 04:59.360 --> 05:03.690 in this. So what I would suggest you do is you actually use a grip filter. So 116 05:03.690 --> 05:04.400 all I will do is 117 05:04.400 --> 05:07.650 run the same command again, but I'll pipe the output into the grip command and 118 05:07.650 --> 05:08.320 I will just set 119 05:08.320 --> 05:14.140 for Ansible hyphen automation hyphen platform. Now if I hit enter, now we have 120 05:14.140 --> 05:15.440 a much shortened 121 05:15.440 --> 05:19.710 output here. Now what I want to point out is that your output may look a little 122 05:19.710 --> 05:20.320 bit different. 123 05:20.320 --> 05:24.240 Remember I happened to be using the arm architecture. So in my case here, the 124 05:24.240 --> 05:25.200 extensions are a little 125 05:25.200 --> 05:30.690 bit different here. I say arches 64. You might happen to see x86 64 that type WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 125 05:25.200 --> 05:30.690 bit different here. I say arches 64. You might happen to see x86 64 that type 126 05:30.690 --> 05:31.200 of thing. 127 05:31.200 --> 05:35.680 Do not stress if your output is a little bit different. So regardless of this 128 05:35.680 --> 05:36.160 part here 129 05:36.160 --> 05:39.920 looks a little bit different. In my case here, I happen to have version 2.4. 130 05:39.920 --> 05:40.480 Maybe when you 131 05:40.480 --> 05:45.730 watch this, it might be 2.6 2.7. Who knows the point is not to get hung up. You 132 05:45.730 --> 05:46.320 should expect 133 05:46.320 --> 05:52.450 to see different options available to us. Notice I have a source RPMs as well 134 05:52.450 --> 05:53.680 as a debug RPMs. 135 05:54.240 --> 05:59.040 And then I just have the regular RPMs. It's this particular repository here 136 05:59.040 --> 05:59.920 that I want to get. 137 05:59.920 --> 06:03.570 The one that is just a regular. So don't install the debug. Don't install the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 137 05:59.920 --> 06:03.570 The one that is just a regular. So don't install the debug. Don't install the 138 06:03.570 --> 06:04.160 source. 139 06:04.160 --> 06:08.910 So all I'm going to do here is I'm actually going to copy this repository ID. 140 06:08.910 --> 06:09.840 So right click 141 06:09.840 --> 06:13.840 and copy you. And now what I want to do is I actually want to enable this 142 06:13.840 --> 06:15.120 particular repository 143 06:15.120 --> 06:18.980 using subscription manager. So the way I do this is by saying so don't 144 06:18.980 --> 06:20.320 subscription manager. 145 06:20.320 --> 06:24.880 Repose and then I'll say dash dash enable. Now at this point here, all I want 146 06:24.880 --> 06:25.680 to do is I want to 147 06:25.680 --> 06:29.520 paste in that particular option that I saw. Okay, so in this case here, it's an 148 06:29.520 --> 06:30.240 cable automation WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 148 06:29.520 --> 06:30.240 cable automation 149 06:30.240 --> 06:35.520 platform 2.4 for rail nine. So if I just hit enter, it's going to fetch the 150 06:35.520 --> 06:36.880 contents and just give 151 06:36.880 --> 06:40.780 it a moment to connect. Now we can see here it says repository, ancable 152 06:40.780 --> 06:42.560 automation platform 2.4 153 06:42.560 --> 06:46.960 for rail nine is enabled for this system. Therefore, if we rerun the command 154 06:46.960 --> 06:48.960 pseudo dnf repo list 155 06:48.960 --> 06:54.000 and to enter, we don't just have base OS and app stream. Now we have the animal 156 06:54.000 --> 06:54.880 automation platform 157 06:54.880 --> 07:00.370 repository. That means therefore, if I say pseudo dnf install, ancable hyphen WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 157 06:54.880 --> 07:00.370 repository. That means therefore, if I say pseudo dnf install, ancable hyphen 158 07:00.370 --> 07:01.200 navigator, 159 07:01.200 --> 07:05.330 and I hit enter, check this out. We're now actually finding this particular 160 07:05.330 --> 07:05.840 package. 161 07:05.840 --> 07:09.560 If I say why and to enter, now it's going to run to the installation. And as we 162 07:09.560 --> 07:10.080 can see, 163 07:10.080 --> 07:15.280 the install has completed. Now what I can do is say, ancable hyphen navigator 164 07:15.280 --> 07:16.320 and say dash dash 165 07:16.320 --> 07:21.270 version. And if I hit enter, what I can see is I have version 3.4.1 again, your 166 07:21.270 --> 07:21.680 version, 167 07:21.680 --> 07:24.720 depending on when you watch this video, maybe a little bit different. Don't 168 07:24.720 --> 07:25.760 worry about that. 169 07:25.760 --> 07:29.920 Now recall with respect to Ansible content navigator, we want to make use of 170 07:29.920 --> 07:31.040 this execution WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 170 07:29.920 --> 07:31.040 this execution 171 07:31.040 --> 07:36.250 environment simply meaning we want to be making use of containers. And as such, 172 07:36.250 --> 07:36.800 if you recall, 173 07:36.800 --> 07:40.810 what we need to have in order to spin up our container is to have the correct 174 07:40.810 --> 07:42.080 container image. 175 07:42.080 --> 07:46.300 So we're going to be utilizing the tool Podman to actually log in to the red 176 07:46.300 --> 07:47.280 hat registry whereby 177 07:47.280 --> 07:51.670 we can get access to those container images. Now this is going to require the 178 07:51.670 --> 07:52.560 use of your 179 07:52.560 --> 07:56.460 red hat accounts. So the same way we happen to utilize a username and a 180 07:56.460 --> 07:57.680 password to register 181 07:57.680 --> 08:01.280 or system. The same thing is true here. So what I'm going to do here is say, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 181 07:57.680 --> 08:01.280 or system. The same thing is true here. So what I'm going to do here is say, 182 08:01.280 --> 08:03.280 pseudo Podman login, 183 08:03.280 --> 08:09.010 and I will say registry dot red hats dot IO. And if I hit enter, it's going to 184 08:09.010 --> 08:09.600 prompt me from my 185 08:09.600 --> 08:13.610 username. Now my red hat username is IPV zero. And now I'm going to have to 186 08:13.610 --> 08:14.640 type in my password, 187 08:14.640 --> 08:18.910 which I'm not going to tell you. So give them a moment. And if I hit enter, now 188 08:18.910 --> 08:19.520 we can see the 189 08:19.520 --> 08:24.350 login has succeeded with that now done. What I should be able to do is to pull 190 08:24.350 --> 08:25.280 down Ansible 191 08:25.280 --> 08:29.610 container images. So now with that done, all I'm going to do is run the command 192 08:29.610 --> 08:30.960 Ansible navigator WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 192 08:29.610 --> 08:30.960 Ansible navigator 193 08:30.960 --> 08:35.040 and to enter. Now the images begin to pull down. And once we have our images, 194 08:35.040 --> 08:36.000 we now have access 195 08:36.000 --> 08:40.890 to this text user interface. So if I want to go in to a particular option, say 196 08:40.890 --> 08:42.240 for example, images, 197 08:42.240 --> 08:46.160 it's pretty much like them. If I press colon, look at the bottom left hand 198 08:46.160 --> 08:47.120 corner, and I just 199 08:47.120 --> 08:50.970 take the words images and to enter, look at what we actually see here, we get 200 08:50.970 --> 08:51.840 to see the images 201 08:51.840 --> 08:55.530 that we have available. We have the execution environment supported for rail 202 08:55.530 --> 08:56.320 eight. Now we 203 08:56.320 --> 09:00.580 happen to be on rail nine, but the execution environment available right now is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 203 08:56.320 --> 09:00.580 happen to be on rail nine, but the execution environment available right now is 204 09:00.580 --> 09:01.280 only for rail 205 09:01.280 --> 09:04.530 eight, but this still is working for us. We can see when the environment was 206 09:04.530 --> 09:05.520 created, it was 11 207 09:05.520 --> 09:10.260 days ago, we can see the size, it's 1.76 gig. Now if I want to get out, I can 208 09:10.260 --> 09:11.280 just press escape. 209 09:11.280 --> 09:15.900 If I want to go into another option, say for example, settings, I can just say 210 09:15.900 --> 09:16.960 colon settings. 211 09:16.960 --> 09:20.320 This is pretty much how things are going to operate. So we can see all of these 212 09:20.320 --> 09:20.640 different 213 09:20.640 --> 09:24.000 settings, where if we want to display color, do we want to enable prompts that 214 09:24.000 --> 09:24.720 type of thing, 215 09:24.720 --> 09:28.500 we can scroll on down, you have the ability to go through all these options, 216 09:28.500 --> 09:29.280 explore them at 217 09:29.280 --> 09:33.430 your own leisure. But for now, I will press escape and escape again. So now we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 217 09:29.280 --> 09:33.430 your own leisure. But for now, I will press escape and escape again. So now we 218 09:33.430 --> 09:34.720 're back to a regular 219 09:34.720 --> 09:38.560 interface. What you'll notice is that every time I happen to run the command 220 09:38.560 --> 09:40.000 answerable navigator, 221 09:40.000 --> 09:44.750 what it seeks to do, it seeks to pull in a new container image. This can 222 09:44.750 --> 09:45.920 sometimes be a little 223 09:45.920 --> 09:49.530 bit annoying, a little bit time consuming. So what we can do is override that 224 09:49.530 --> 09:50.880 behavior by virtue of 225 09:50.880 --> 09:54.760 setting an answerable navigator configuration file. So what I'm actually going 226 09:54.760 --> 09:56.240 to do here is press escape, 227 09:56.240 --> 10:00.590 and I'm going to generate a sample configuration file and then modify that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 227 09:56.240 --> 10:00.590 and I'm going to generate a sample configuration file and then modify that 228 10:00.590 --> 10:01.760 sample. So the way I 229 10:01.760 --> 10:05.600 can do this, if I just clear the screen, and I just say answerable navigator, 230 10:05.600 --> 10:06.880 and I say settings. 231 10:06.880 --> 10:11.670 And what I'm going to do is to say dash dash G s to generate a sample, and then 232 10:11.670 --> 10:12.240 I'll say dash 233 10:12.240 --> 10:15.880 dash PP for pole policy, I'm going to set that to never. And then I'm going to 234 10:15.880 --> 10:17.600 have my right arrow 235 10:17.600 --> 10:21.320 to pipe the output into a file just called sample. Okay, call this anything you 236 10:21.320 --> 10:22.160 so wish right now. 237 10:22.160 --> 10:25.420 And if I hit enter, what we've actually done here is created this new 238 10:25.420 --> 10:27.200 configuration file known as 239 10:27.200 --> 10:31.690 sample. Now what I want to do with it now created, I want to rename it to be WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 239 10:27.200 --> 10:31.690 sample. Now what I want to do with it now created, I want to rename it to be 240 10:31.690 --> 10:33.760 answerable hyphen navigator 241 10:33.760 --> 10:37.840 dot YML. Now the reason why I didn't just name it directly off the bad as 242 10:37.840 --> 10:39.200 answerable navigator 243 10:39.200 --> 10:42.880 is that with that convention, answerable navigator is going to seek to parse 244 10:42.880 --> 10:44.000 that configuration file 245 10:44.000 --> 10:47.640 directly. I don't want to do that first. I want to make my modifications. So I 246 10:47.640 --> 10:49.120 'll just move this here. 247 10:49.120 --> 10:53.710 It is now renamed as we can see right here. And all I'm going to do is go in 248 10:53.710 --> 10:54.880 and modify this. So 249 10:54.880 --> 10:59.680 if I just save them answerable navigator dot YML, this is the configuration 250 10:59.680 --> 11:00.480 file that has been WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 250 10:59.680 --> 11:00.480 file that has been 251 11:00.480 --> 11:04.560 generated. So you can modify these configs if you so wish. Notice they happen 252 11:04.560 --> 11:05.440 to be commented out 253 11:05.440 --> 11:08.820 with the pound sign. So you're going to have to uncomment them for them to 254 11:08.820 --> 11:10.320 actually take effects. 255 11:10.320 --> 11:13.420 So say for example, you wanted to change the path of where your answerable 256 11:13.420 --> 11:14.160 configuration 257 11:14.160 --> 11:18.500 file is you could uncomment answerable as well as config as well as path and 258 11:18.500 --> 11:19.440 then change the actual 259 11:19.440 --> 11:22.820 value here that is a type of thing we're doing here. Similar if you want to 260 11:22.820 --> 11:23.600 change plugins 261 11:23.600 --> 11:27.310 or scrolling on down, perhaps where your inventory happens to be that type of 262 11:27.310 --> 11:27.840 thing. 263 11:27.840 --> 11:31.650 So what I'm going to do here is I'm going to scroll all the way down and I'm WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 263 11:27.840 --> 11:31.650 So what I'm going to do here is I'm going to scroll all the way down and I'm 264 11:31.650 --> 11:32.720 going to find my 265 11:32.720 --> 11:36.080 execution environment right here. So what I'm going to do here is I'm going to 266 11:36.080 --> 11:37.440 go into insert modes. 267 11:37.440 --> 11:41.250 And one thing I want to be aware of here, I want to actually maintain the 268 11:41.250 --> 11:42.560 correct indentation. So 269 11:42.560 --> 11:47.030 notice I actually have two spaces here. I will say backspace and then backspace 270 11:47.030 --> 11:48.080 again. Basically, 271 11:48.080 --> 11:51.730 I'm doing two backspaces. That is going to allow me to maintain the correct 272 11:51.730 --> 11:52.480 indentation. 273 11:52.480 --> 11:56.410 With that now done, if I scroll on down, what I want to go to is this option 274 11:56.410 --> 11:56.640 here, 275 11:56.640 --> 12:01.360 pull. So again, I'm going to go two spaces out and just say back back that will WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 275 11:56.640 --> 12:01.360 pull. So again, I'm going to go two spaces out and just say back back that will 276 12:01.360 --> 12:02.080 now uncomment 277 12:02.080 --> 12:06.100 it and leave it in the correct indentation. And then scrolling on down, if I go 278 12:06.100 --> 12:07.600 to policy right here, 279 12:07.600 --> 12:11.920 once again, two spaces out and just do back back that is now uncommented. So 280 12:11.920 --> 12:12.400 like I say, 281 12:12.400 --> 12:15.730 when we happen to run answerable navigator right now, it's going to seek to 282 12:15.730 --> 12:17.120 pull in a new image 283 12:17.120 --> 12:20.670 every single run. If you want to modify the behavior, I can just set the pull 284 12:20.670 --> 12:21.680 policy to be 285 12:21.680 --> 12:25.750 missing. That means it's going to disuse the container image that is on the box 286 12:25.750 --> 12:26.560 right now. 287 12:26.560 --> 12:31.030 So with that now done, if I press escape, colon wq to writing quits, if I now WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 287 12:26.560 --> 12:31.030 So with that now done, if I press escape, colon wq to writing quits, if I now 288 12:31.030 --> 12:31.840 say answerable 289 12:31.840 --> 12:35.720 navigator and to enter, it's going to immediately snap me into my option right 290 12:35.720 --> 12:36.720 here without any 291 12:36.720 --> 12:40.510 delay, we're not trying to pull down any new images. So that's just an example 292 12:40.510 --> 12:41.040 of one of the 293 12:41.040 --> 12:44.900 many things that you can change within your configurations, like I say, change 294 12:44.900 --> 12:45.360 the answerable 295 12:45.360 --> 12:48.930 configuration for your location, whatever it is you want to do. So now that we 296 12:48.930 --> 12:49.680 have the basics 297 12:49.680 --> 12:53.760 of answerable navigator up and running, let's now begin looking at how we can 298 12:53.760 --> 12:54.160 actually 299 12:54.160 --> 12:58.400 explore our inventory using navigator as well as running playbooks. And well, 300 12:58.400 --> 12:58.880 that's what we're 301 12:58.880 --> 13:00.480 doing in the very next video. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 301 12:58.880 --> 13:00.480 doing in the very next video.