WEBVTT 00:00.660 --> 00:05.820 Anytime you make a web application you're going to have to consider the different types of deployment 00:05.820 --> 00:07.940 models that are available for it. 00:07.980 --> 00:14.290 How are you going to get that to the people who need to use this new amazing app that you've developed. 00:14.440 --> 00:15.930 Well you've got a lot of choices here. 00:15.930 --> 00:18.210 So let's start with way back in the day. 00:18.570 --> 00:23.640 Back in the old days if you developed an app you mean old days I'm talking about like you know 2005 00:24.120 --> 00:31.200 if you developed a web app you would have to then buy yourself physical servers and you have to take 00:31.200 --> 00:37.920 these physical servers and you'd install some type of server software and you install a web server on 00:37.920 --> 00:43.170 there and then you would install your web application and you'd set up your own DNA Zee's and you set 00:43.170 --> 00:46.170 up your own firewall you'd be responsible for everything. 00:46.350 --> 00:49.570 And if a lot of people liked it you'd have to start setting up more servers. 00:49.720 --> 00:52.290 SSL accelerators and low balancers. 00:52.920 --> 00:54.570 It wasn't a really pretty way to do it. 00:54.570 --> 01:03.460 It didn't take very long for third party organizations to offer new ways to host these types of applications. 01:03.480 --> 01:09.630 So one that came on fairly early was a called a hosted application in this particular situation what 01:09.630 --> 01:16.050 would happen is that some big building with really incredible Internet connectivity and extra power 01:16.050 --> 01:21.840 and generators in case the power went out and all the security and all this safety would allow you to 01:21.840 --> 01:25.900 put your computer into their facility. 01:25.920 --> 01:30.960 Now after a while that got even better and they would then say listen we've already got a computer here 01:30.960 --> 01:36.900 for you and then you just go ahead and put your application on there and then you can imagine that we 01:36.900 --> 01:42.630 got to the point where virtualization came along and now people are taking a system and they're saying 01:42.690 --> 01:48.560 well here just install it onto one of my virtual machines here and my third party location. 01:48.750 --> 01:52.520 And if you really think about it you're using the cloud. 01:52.620 --> 01:54.180 I mean what do you got. 01:54.180 --> 01:55.560 It's a remote location. 01:55.590 --> 01:57.270 It's running virtualization. 01:57.450 --> 02:03.370 You have no real direct control over the hardware just the actual software and the VM that you're renting. 02:03.690 --> 02:06.510 You have now generated the cloud. 02:06.510 --> 02:14.190 So if I'm an organization I can make my own cloud anytime I want as long as I've got some server systems 02:14.490 --> 02:20.220 and I've got some big storage is like a sand system or something like that that could store lots and 02:20.220 --> 02:21.450 lots of data. 02:21.510 --> 02:23.300 I can make my own cloud. 02:23.400 --> 02:25.180 It's actually pretty easy. 02:25.310 --> 02:27.810 Now there's a lot of different clouds out there. 02:27.810 --> 02:32.280 So depending on what your deployment is you're going to have to pick from one of these four different 02:32.280 --> 02:33.340 clouds. 02:33.390 --> 02:37.990 The first one is a private cloud in a private cloud situation. 02:37.990 --> 02:39.340 Here's my little cloud. 02:39.340 --> 02:45.730 So let's just say I've got a whole bunch of computers here and I've got this all set up now we can generate 02:45.730 --> 02:49.630 our own virtual machines anytime we want but it's private. 02:49.630 --> 02:56.340 So keep out it is just for us so it's just within my organization that we can use this private cloud 02:57.750 --> 03:03.750 the next type is a public cloud a public cloud is pretty much the exact opposite of a private cloud 03:04.080 --> 03:05.060 with a public cloud. 03:05.070 --> 03:09.630 And these are things like Amazon S3 and Microsoft as your. 03:09.720 --> 03:14.820 These places are open for business and anybody with a credit card can connect in. 03:14.820 --> 03:19.670 They can set up their own Vians they can upload their web apps they can do anything they want to do 03:19.680 --> 03:24.870 and it includes all kinds of stuff like security add ons and all kinds of fun stuff. 03:24.870 --> 03:27.870 So a public is very very popular. 03:27.870 --> 03:29.140 We see them all the time. 03:30.170 --> 03:36.480 Next is a hybrid cloud hybrid cloud is a little bit from column A and a little bit from column B. 03:37.260 --> 03:39.870 What we have is one big cloud. 03:39.990 --> 03:46.680 But some of this cloud is segregated as private and some of the cloud maybe we don't need all this capacity 03:46.890 --> 03:54.800 so we offer this up as a public so that we can make some money while we have our cloud now fourth is 03:54.800 --> 03:55.900 a community cloud. 03:56.060 --> 03:59.810 The problem with setting up your own cloud is that it's expensive. 03:59.810 --> 04:05.120 We're talking hundreds of thousands of dollars even for the most base type of robust cloud. 04:05.150 --> 04:12.180 So a lot of smaller organizations businesses government entities instead of making their own. 04:12.230 --> 04:16.910 They'll join up as a community three four five 10 different organizations. 04:16.910 --> 04:20.420 Everybody puts a little money and they build one cloud. 04:20.630 --> 04:24.560 So in this particular case it's like having your own private club. 04:24.740 --> 04:26.470 So it's just members only. 04:26.510 --> 04:31.080 And if you could be a part of that member then you can be a part of that cloud. 04:31.100 --> 04:36.350 All of these different clouds are great in the virtualization gives us some real opportunities. 04:36.380 --> 04:43.100 One of the places we're deploying that really comes into play is the idea of virtualizing our desktops 04:43.430 --> 04:48.230 now this is a little bit different than simply a web type application. 04:48.290 --> 04:52.550 In this case what we're talking about is virtualizing the OS itself. 04:52.550 --> 04:55.870 So what we're talking about that there's two different ways to do that. 04:55.910 --> 05:03.740 And the first is virtual desktop environment a virtual desktop environment is also known as Old School 05:03.770 --> 05:05.210 remote desktop. 05:05.240 --> 05:11.900 In this particular situation we have a local client that is taking control of some kind of remote system. 05:12.140 --> 05:14.430 This remote system is not virtualise. 05:14.450 --> 05:18.320 It's a real computer like my desktop in my office. 05:18.320 --> 05:26.780 If I access this system with some type of remote terminal tool if anybody walks up to my computer the 05:26.780 --> 05:30.650 computer is not going to like that because it's going to go wait a minute somebody is remotely connected 05:30.650 --> 05:32.930 in at this particular moment. 05:33.200 --> 05:36.730 These types of remote desktop tools have been around for ever. 05:36.740 --> 05:43.330 The Windows Remote Desktop Protocol has been popular since the arguably the late 1980s. 05:43.640 --> 05:47.540 One of the nice things about something like this though is that we can do some interesting stuff like 05:47.810 --> 05:52.970 here I've got my little Android right here and what I want to do is I want a remote desktop into my 05:53.240 --> 05:56.810 system in my office so it's pretty easy to do. 05:58.770 --> 06:03.720 I've already logged in and everything so he already knows I'm here and I'm actually on the Windows system 06:03.720 --> 06:05.670 yes I'm running Android on here. 06:05.790 --> 06:10.560 But if you were to take a look at the screen there's nothing Android about the screen at all is there. 06:10.620 --> 06:11.540 It's all there. 06:11.580 --> 06:12.600 All my icons on. 06:12.630 --> 06:15.370 Yes I have a messy desk top with a lot of icons. 06:15.510 --> 06:21.590 I can actually start up applications I assure you I don't have Microsoft Word on this Android. 06:21.630 --> 06:27.080 The important thing to keep in mind in this situation is he's really nothing more than a terminal. 06:27.240 --> 06:33.930 It's nothing more than keystrokes mouse movements which are manifested through my finger and an actual 06:33.930 --> 06:35.630 interface to the screen itself. 06:35.670 --> 06:41.020 So there's not a lot of work involved with this type of virtual desktop environment. 06:41.040 --> 06:44.680 Now let's take this idea and take it one step further. 06:44.820 --> 06:52.110 What if I took some type of local system and instead of connecting to a real machine what if I connected 06:52.110 --> 06:54.580 to a virtualise machine in the cloud. 06:54.600 --> 06:59.010 In that type of situation I would have some interesting controls for example. 06:59.010 --> 07:02.330 I don't really have to have any operating system on here at all. 07:02.370 --> 07:08.170 I'd have to have some type of virtualise hypervisor or something like that so I could load something. 07:08.190 --> 07:14.190 But really all I would need is a terminal tool and that's what virtual desktop integration is all about. 07:14.190 --> 07:17.340 So let's take a look at the screen that I have right here. 07:17.370 --> 07:22.080 Now if you look at this I've just got a little copy of Ubuntu running on top of Windows. 07:22.090 --> 07:24.470 Now what if I did something like this. 07:26.130 --> 07:27.850 It takes a minute but it gets there. 07:27.960 --> 07:33.810 If you look at the screen there's nothing to tell you that you're actually running Ubuntu in a virtual 07:33.810 --> 07:35.520 machine on top of Windows. 07:35.530 --> 07:39.350 Yeah OK there's a little tab here we can make that go away. 07:39.660 --> 07:45.990 And now to the common user all that they're seeing is a desktop. 07:46.160 --> 07:52.350 And this is the power of VDI in a VDI environment you can deploy complete operating systems. 07:52.370 --> 07:57.950 People don't have to have a zillion copies of something they just have a terminal tool that's on whatever 07:57.950 --> 07:58.520 they want. 07:58.520 --> 08:06.080 A tablet a phone a laptop whatever it might be or desktop and they can log in and connect to their always 08:06.080 --> 08:08.970 running always in one place virtual machine. 08:09.230 --> 08:14.010 So when it comes to deployment deployment isn't locked in only for web applications. 08:14.030 --> 08:16.070 We can also do it for operating systems. 08:16.070 --> 08:21.220 Make sure you're comfortable with the idea of VD versus VDI.