WEBVTT 1 00:00.000 --> 00:03.770 So friends, as I happened to mention, the graphical user interface of the Ans 2 00:03.770 --> 00:05.280 ible Automation Controller 3 00:05.280 --> 00:08.560 is very very popular, and let me get my little drone pen up here. 4 00:08.560 --> 00:13.360 There we go, it's a little bit better. It's very very popular in the enterprise 5 00:13.360 --> 00:14.080 environment. 6 00:14.080 --> 00:18.480 That's because in the enterprise world, we have many different teams performing 7 00:18.480 --> 00:19.040 many different 8 00:19.040 --> 00:23.920 jobs. Maybe some particular teams are managing purely the networking devices, 9 00:23.920 --> 00:24.560 the routers and 10 00:24.560 --> 00:29.470 switches, other teams maybe organizing resources within the cloud. It may be 11 00:29.470 --> 00:30.960 AWS, it may be Microsoft WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 11 00:29.470 --> 00:30.960 AWS, it may be Microsoft 12 00:30.960 --> 00:35.980 Azure, and perhaps other teams are managing on-prem servers. The point being is 13 00:35.980 --> 00:36.480 that in these 14 00:36.480 --> 00:40.310 complex environments, you're not just going to be a single user on your own 15 00:40.310 --> 00:41.200 little machine, 16 00:41.200 --> 00:45.360 automating out absolutely everything in a massive enterprise environment. 17 00:45.360 --> 00:49.840 Ultimately, we want to have our environment organized any very particular way. 18 00:49.840 --> 00:53.610 So certain users can access certain resources, they're going to be running 19 00:53.610 --> 00:54.640 certain playbooks, 20 00:54.640 --> 00:58.960 they will be targeting very particular managed devices, that type of thing. Now 21 00:58.960 --> 00:58.960 , 22 00:58.960 --> 01:04.450 this here, this concept of being organized is one of the advantages of this WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 22 00:58.960 --> 01:04.450 this here, this concept of being organized is one of the advantages of this 23 01:04.450 --> 01:05.360 particular platform 24 01:05.360 --> 01:09.260 right here. In fact, one of the things that I want to talk to you about is the 25 01:09.260 --> 01:10.320 creation of an 26 01:10.320 --> 01:14.830 organization. Now really, an organization is just a collection of different 27 01:14.830 --> 01:16.160 teams, projects, 28 01:16.160 --> 01:19.600 inventories, that type of thing. So let's maybe say I happen to have an 29 01:19.600 --> 01:21.680 organization called CBTN 30 01:21.680 --> 01:27.230 for CBTNogus, okay? And in this environment, CBTN have different teams to 31 01:27.230 --> 01:28.080 ultimately manage 32 01:28.080 --> 01:32.370 different resources. So maybe we have our AWS cloud resource, and maybe we'll WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 32 01:28.080 --> 01:32.370 different resources. So maybe we have our AWS cloud resource, and maybe we'll 33 01:32.370 --> 01:33.680 get 10 engineers 34 01:33.680 --> 01:37.730 managing that particular environment. We could ultimately have a team of 35 01:37.730 --> 01:38.880 engineers, 36 01:38.880 --> 01:43.010 which are ultimately comprised of different users, i.e. different individual 37 01:43.010 --> 01:43.600 engineers 38 01:43.600 --> 01:48.960 managing the system, but all operating under the same banner of CBTN. And then 39 01:48.960 --> 01:49.280 of course, 40 01:49.280 --> 01:53.280 we could have another team managing another resource, maybe just say some 41 01:53.280 --> 01:54.240 regular servers 42 01:54.240 --> 01:58.860 within our own environment on premises. That could be an entirely different 43 01:58.860 --> 01:59.200 team, 44 01:59.200 --> 02:04.720 again, under the same banner of CBTN as an organization, but again, comprised WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 44 01:59.200 --> 02:04.720 again, under the same banner of CBTN as an organization, but again, comprised 45 02:04.720 --> 02:05.920 of different users 46 02:05.920 --> 02:08.840 managing different resources. Let me show you what I mean here. If I happen to 47 02:08.840 --> 02:10.000 go to the documentation 48 02:10.000 --> 02:14.720 here, if you happen to search for Ansible Automation Platform Organization, and 49 02:14.720 --> 02:15.360 let's just collect 50 02:15.360 --> 02:19.270 this top line right here for organizations. Now, what we actually see here is a 51 02:19.270 --> 02:20.320 pretty helpful 52 02:20.320 --> 02:23.670 graphic. And this is ultimately what I'm talking about here. We can see an 53 02:23.670 --> 02:24.400 organization 54 02:24.400 --> 02:29.820 as a logical collection of users, teams, projects, and inventories. And this is 55 02:29.820 --> 02:31.120 the highest level in WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 55 02:29.820 --> 02:31.120 the highest level in 56 02:31.120 --> 02:34.700 the automation controller hierarchy. So we can see here we define an 57 02:34.700 --> 02:35.920 organization such as, 58 02:35.920 --> 02:40.980 let's maybe say CBTN, as I said before, and inside of here, we're going to have 59 02:40.980 --> 02:41.760 inventories within 60 02:41.760 --> 02:45.800 the organization, which is going to have different groups and hosts. This is 61 02:45.800 --> 02:46.800 pretty much the same 62 02:46.800 --> 02:50.680 concept we see in regular Ansible. The key point here is that we can have 63 02:50.680 --> 02:51.600 multiple different 64 02:51.600 --> 02:55.300 inventories with different groups and hosts. Again, within the same 65 02:55.300 --> 02:56.720 organization, we can have 66 02:56.720 --> 03:00.470 teams now what the teams actually comprise of, but the team itself can have its WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 66 02:56.720 --> 03:00.470 teams now what the teams actually comprise of, but the team itself can have its 67 03:00.470 --> 03:01.360 own permissions 68 03:01.360 --> 03:04.950 and credentials. So we can have a group credential that allows the users or 69 03:04.950 --> 03:06.080 rather the members of 70 03:06.080 --> 03:10.120 that group to do particular tasks. But more specifically within that team, we 71 03:10.120 --> 03:11.600 can also have users 72 03:11.600 --> 03:16.090 with their own credentials, with varying permissions for more granularity. So 73 03:16.090 --> 03:16.720 maybe 74 03:16.720 --> 03:21.230 some senior users can have greater access and the more junior engineers can 75 03:21.230 --> 03:22.800 have restricted access. 76 03:22.800 --> 03:27.280 Then again, within the organization, we can have this concept of projects, and 77 03:27.280 --> 03:28.080 our projects are 78 03:28.080 --> 03:31.890 really going to be what are our playbooks. And as we'll see here, something WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 78 03:28.080 --> 03:31.890 really going to be what are our playbooks. And as we'll see here, something 79 03:31.890 --> 03:33.040 known as jobs and 80 03:33.040 --> 03:35.910 templates, we'll talk about this very, very shortly. But ultimately, what I'm 81 03:35.910 --> 03:36.800 trying to point out 82 03:36.800 --> 03:40.680 here is that the organization is the highest level and it basically ties 83 03:40.680 --> 03:41.920 everything together 84 03:41.920 --> 03:45.520 within the enterprise. So briefly, let me just show you how we can create these 85 03:45.520 --> 03:46.320 organizations, 86 03:46.320 --> 03:50.480 as well as how we can create a team and comprise of different users, if we so 87 03:50.480 --> 03:51.040 wish. 88 03:51.040 --> 03:54.960 So let's go and do that then. So down the left hand side, on the dashboard, we 89 03:54.960 --> 03:55.600 can see all of these 90 03:55.600 --> 03:59.200 different options. Let me just scroll on down and we can see here under access, 91 03:59.200 --> 04:00.080 we have our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 91 03:59.200 --> 04:00.080 we have our 92 04:00.080 --> 04:04.630 organization. If I click this here, by default, we're going to have a default 93 04:04.630 --> 04:05.680 organization. Now, 94 04:05.680 --> 04:08.940 you can just use this if you so wish, but again, I'm trying to demonstrate 95 04:08.940 --> 04:10.160 things. So let's go and 96 04:10.160 --> 04:14.330 create our own brand new organization. So let me just add this one here. So let 97 04:14.330 --> 04:14.720 's just call 98 04:14.720 --> 04:19.080 that organization nugget tick. Okay. And we'll just the description as 99 04:19.080 --> 04:20.960 organization for all 100 04:20.960 --> 04:25.080 nugget tick resources. Now, we can see here we have other options such as the 101 04:25.080 --> 04:26.000 maximum amount of 102 04:26.000 --> 04:29.650 host within the organization or perhaps things such as the default execution 103 04:29.650 --> 04:30.800 environments. But WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 103 04:29.650 --> 04:30.800 environments. But 104 04:30.800 --> 04:35.800 for now, all I'll do is I'll just choose save. Perfect. So here we have our 105 04:35.800 --> 04:36.800 organization. 106 04:36.800 --> 04:40.440 Network like on teams right here, notice we don't actually have any teams 107 04:40.440 --> 04:42.320 within this organization. 108 04:42.320 --> 04:45.830 That is what we want to create. So imagine you wanted to create a team, let's 109 04:45.830 --> 04:46.800 just say ads, 110 04:46.800 --> 04:50.740 and we'll just call this a cloud team. Okay. And we just say team to manage 111 04:50.740 --> 04:51.840 cloud resources. 112 04:51.840 --> 04:55.680 Now we specify what is the organization should this team be a member of? Well, 113 04:55.680 --> 04:56.720 in this case here, 114 04:56.720 --> 05:00.960 if I just collect the search, the only two that we have created so far is the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 114 04:56.720 --> 05:00.960 if I just collect the search, the only two that we have created so far is the 115 05:00.960 --> 05:01.360 default, 116 05:01.360 --> 05:06.000 which was automatically created and the new nugget tick organization. Let's 117 05:06.000 --> 05:06.720 make the team 118 05:06.720 --> 05:10.640 a member of nugget tick. So let's select this. And if I just save this right 119 05:10.640 --> 05:11.120 here, 120 05:11.120 --> 05:15.420 so again, going back to organization right here now, if I click on nugget tick, 121 05:15.420 --> 05:15.840 now we can see 122 05:15.840 --> 05:20.160 here in teams, we actually have cloud team a member or rather a part of the 123 05:20.160 --> 05:21.120 organization. 124 05:21.120 --> 05:25.630 And again, what are with thin teams where we have individual users? So if I 125 05:25.630 --> 05:26.720 want to have a user 126 05:26.720 --> 05:31.140 here, right now we have only a default user if I want to add one, let's maybe WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 126 05:26.720 --> 05:31.140 here, right now we have only a default user if I want to add one, let's maybe 127 05:31.140 --> 05:33.360 just say John McGovern, 128 05:33.360 --> 05:39.200 and just give an email of John McGovern. That's cloud nuggets tick.com. Let's 129 05:39.200 --> 05:39.840 have a username, 130 05:39.840 --> 05:43.680 like I said, john Mcg and then we can add in a secure password. I'll just say 131 05:43.680 --> 05:44.240 blah one, 132 05:44.240 --> 05:48.720 which is a terrible password, obviously. But this is a demo. It's all confirmed 133 05:48.720 --> 05:49.200 this. 134 05:49.200 --> 05:53.610 And now we specify the user type. Now we have three different types of users 135 05:53.610 --> 05:54.400 that we can add. 136 05:54.400 --> 05:58.080 Let me tell you what each of them are. So a normal user is going to have both 137 05:58.080 --> 06:00.000 read and write access, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 138 06:00.000 --> 06:04.240 but the user here is going to be limited within the scope of their organization 139 06:04.240 --> 06:04.240 , 140 06:04.240 --> 06:07.440 so they can perhaps read and write information relating to inventories and 141 06:07.440 --> 06:08.400 projects and jobs, 142 06:08.400 --> 06:11.680 that type of thing, but again, only within the organization that they happen to 143 06:11.680 --> 06:12.560 be a member of. 144 06:12.560 --> 06:16.560 So that's the normal user. The next user, if we look at the drop down here, 145 06:16.560 --> 06:21.790 this would be a system auditor accounts. So really, the system auditor account 146 06:21.790 --> 06:22.720 is not going to be 147 06:22.720 --> 06:26.590 limited to a single organization. We can have multiple different orgs within 148 06:26.590 --> 06:27.920 here, but the system 149 06:27.920 --> 06:31.690 auditor is only going to have read access, which kind of makes sense when you WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 149 06:27.920 --> 06:31.690 auditor is only going to have read access, which kind of makes sense when you 150 06:31.690 --> 06:32.720 actually think about 151 06:32.720 --> 06:37.480 it. The auditor is really just auditing and reading the data that exists within 152 06:37.480 --> 06:38.240 the controller 153 06:38.240 --> 06:42.820 here. And then the last account we can see here is the system admin account. 154 06:42.820 --> 06:43.760 This is going to have 155 06:43.760 --> 06:48.800 a read and write access to pretty much everything, multiple organizations, all 156 06:48.800 --> 06:49.600 the users, all the 157 06:49.600 --> 06:53.060 teams, all the projects, that type of thing. So in this case here, if I just 158 06:53.060 --> 06:54.480 want to have a user 159 06:54.480 --> 06:59.090 within a particular organization, then what I can do is just specify a normal 160 06:59.090 --> 06:59.440 user, 161 06:59.440 --> 07:02.800 and then specify that the organization, the scope it should be within, is going WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 161 06:59.440 --> 07:02.800 and then specify that the organization, the scope it should be within, is going 162 07:02.800 --> 07:03.600 to be within 163 07:03.600 --> 07:08.620 nugget tick. So if I click select here, and then save, here we have the actual 164 07:08.620 --> 07:09.440 users here. 165 07:09.440 --> 07:14.940 So if I go and click on users now, and I select John Mcgee, and I now go to 166 07:14.940 --> 07:15.680 teams, 167 07:15.680 --> 07:21.200 and I select associate, I can associate John Mcgee with the cloud team, and 168 07:21.200 --> 07:22.000 then select 169 07:22.000 --> 07:26.290 save. So now we can see here, John Mcgee is a member of the cloud team, which 170 07:26.290 --> 07:27.040 is a member of 171 07:27.040 --> 07:31.310 the nugget tech organization. And this is a team to manage cloud resources. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 171 07:27.040 --> 07:31.310 the nugget tech organization. And this is a team to manage cloud resources. 172 07:31.310 --> 07:31.920 This is what John has 173 07:31.920 --> 07:35.290 been assigned to do. So what would happen in this case here would be when John 174 07:35.290 --> 07:35.760 logs in, 175 07:35.760 --> 07:40.030 let me just log out right here. If I log in with John Mcgee, and I think the 176 07:40.030 --> 07:40.640 password was 177 07:40.640 --> 07:43.900 blah one, which was a terrible password, but nevertheless, let's try and log in 178 07:43.900 --> 07:44.560 . What we can 179 07:44.560 --> 07:49.530 see here now is John Mcgee's actual dashboard. Now John Mcgee could actually 180 07:49.530 --> 07:50.400 have particular 181 07:50.400 --> 07:54.740 inventories, particular projects that John could work with that are designed to 182 07:54.740 --> 07:55.200 manage 183 07:55.200 --> 08:00.850 the cloud resources within, as we can see here, the organization nugget tick. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 183 07:55.200 --> 08:00.850 the cloud resources within, as we can see here, the organization nugget tick. 184 08:00.850 --> 08:01.760 So as you can imagine, 185 08:01.760 --> 08:05.760 with respect to a very, very large environment, if you want to subdivide that 186 08:05.760 --> 08:06.720 environment into 187 08:06.720 --> 08:11.220 much more logical and much more manageable chunks, you can easily do so on the 188 08:11.220 --> 08:11.760 Ansible 189 08:11.760 --> 08:17.040 Automation Platform, Automation Controller, with organizations, with teams and 190 08:17.040 --> 08:17.920 with users.