00:00:11.429 --> 00:00:26.790
Michelle Coppens :: Webinar Support: Hello everyone and welcome to today's webinar titled discover new tonics with vmware yes si hybrid hypervisor my name is Michelle and I will be your MC for the hour, thank you for joining the conversation.
00:00:27.810 --> 00:00:35.460
Michelle Coppens :: Webinar Support: Before we get started let's cover the webinar functionalities during the session everyone's microphones will be muted.
00:00:36.240 --> 00:00:46.890
Michelle Coppens :: Webinar Support: But we want this to be an open discussion so if you have any questions or comments, please enter them in the Q amp a box or the chat window at the bottom of your screen.
00:00:47.610 --> 00:00:54.930
Michelle Coppens :: Webinar Support: There will be a dedicated question answer session after the presentation, but we encourage you to drop those comments in along the way.
00:00:56.160 --> 00:01:05.130
Michelle Coppens :: Webinar Support: today's webinar is being recorded and a copy will be sent out to everyone, near the end of the week, our speaker today is can willard.
00:01:05.670 --> 00:01:12.240
Michelle Coppens :: Webinar Support: Ken specializes in system virtualization and consolidation at the server and desktop level.
00:01:13.050 --> 00:01:21.240
Michelle Coppens :: Webinar Support: Happy helping technology teams approach virtualization well, considering the technical organizational and political impact.
00:01:21.930 --> 00:01:32.670
Michelle Coppens :: Webinar Support: tennis worked with it organizations from the commercial government and nonprofit verticals addressing virtualization and each of these unique environments.
00:01:33.390 --> 00:01:45.270
Michelle Coppens :: Webinar Support: In addition to delivering training to both the business partner and and user communities can also works with the tech data channel community to assist with pre sale consulting.
00:01:46.440 --> 00:01:53.040
Michelle Coppens :: Webinar Support: we're in for an informative discussion and a real time DEMO today so let's get started, can you can take it from here.
00:01:53.880 --> 00:01:55.920
Ken Willard: Thanks for show welcome everyone.
00:01:57.690 --> 00:01:58.680
Ken Willard: So a little bit of a.
00:01:59.880 --> 00:02:11.940
Ken Willard: hot topic these days right as folks are looking at hyper converged environments and what that means for them in choices of infrastructure and frankly today a lot of.
00:02:12.510 --> 00:02:21.060
Ken Willard: Emphasis on automation and looking at how the data Center is going to change and evolve over the next probably three to five years.
00:02:22.290 --> 00:02:34.530
Ken Willard: So as Michelle talked about we're going to open up we've got a general presentation we're going to talk a little bit about some of the new news out of new tactics recently little update from late in the last month.
00:02:35.160 --> 00:02:41.700
Ken Willard: we're going to talk about just some of the trends that have been going on in general, over the last few years.
00:02:42.150 --> 00:02:52.860
Ken Willard: Honestly, nothing that many of you don't probably already know, but just do a little bit of review kind of set the framework for how we got to the hyper converged conversation that many of us are having today.
00:02:53.580 --> 00:03:02.340
Ken Willard: And then finally start drilling into some of those specifics about what's going on with the new tannic distributed storage fabric platform.
00:03:03.270 --> 00:03:14.070
Ken Willard: And how that interacts specifically with the vmware hypervisor and then, as discussed we'll have a little bit of a live DEMO we got a DEMO environment setup.
00:03:14.700 --> 00:03:27.930
Ken Willard: will be talking about the management platforms and we'll be doing a little bit of work with some virtual machines just very quickly to show you some of the capabilities, with the different ones of the management platforms.
00:03:31.740 --> 00:03:41.700
Ken Willard: So, as we look at what's kind of the big news last month, about the third week of September, we got the announcement of new tonics releasing.
00:03:42.090 --> 00:03:55.680
Ken Willard: The Acropolis os version six release and, by the way, just so that everybody's coming clear right there's a lot of vocabulary, I found any it product or solution.
00:03:56.850 --> 00:04:09.540
Ken Willard: When we think about that Acropolis os when new tonics makes that recommendation right what they're talking about is the software that's running inside of your CV EMS.
00:04:10.140 --> 00:04:19.290
Ken Willard: And it doesn't matter which hypervisor you're working with there's always a CVs one CVs per node with the new tannic architecture.
00:04:20.430 --> 00:04:31.020
Ken Willard: So it's that Acropolis os it's the the makeup and the code base that's running inside of your controller vm on each node in the cluster.
00:04:32.400 --> 00:04:44.130
Ken Willard: And that's what's delivering our data services that's what's delivering the cluster storage architecture for us right so obviously a critical part of the architecture.
00:04:45.090 --> 00:04:54.630
Ken Willard: The other thing that may be a little different for some of you particularly thinking about how other vendors handle their release schedules and what's going on.
00:04:55.320 --> 00:05:06.300
Ken Willard: The ios release six, so the whole number incremental release is a short term support release from new tactics.
00:05:07.200 --> 00:05:17.640
Ken Willard: New tannic does their support model in two different configurations there's the long term support release, which is intended to.
00:05:18.330 --> 00:05:30.690
Ken Willard: Just kind of like its name implies be the long term, stable release of the platform that just to be candid we generally think about that in organizations that are.
00:05:31.200 --> 00:05:48.960
Ken Willard: A little more conservative in their it operations, they tend to want to have a single cluster upgrade done and have that cluster upgrade be able to be viable a run long term for many months or a year.
00:05:50.220 --> 00:05:59.880
Ken Willard: Right and so with the long term support model that's what you get and then inside of the long term support release says, you get.
00:06:00.570 --> 00:06:09.900
Ken Willard: patches or security updates and those kinds of things so it's not that with the long term, release you you don't have any more patching at noon, but.
00:06:10.800 --> 00:06:22.980
Ken Willard: you've got a stable code base that is intended to be run long term and the current long term support released from new tonics is the five dot 20 release.
00:06:24.510 --> 00:06:32.550
Ken Willard: So what do we get with the short term releases right, the whole thing from the new tax perspective is the short term support release as.
00:06:33.120 --> 00:06:46.950
Ken Willard: Our feature set releases, you will get new capabilities new things that get released, and if you want the right away, you can roll out that short term support release.
00:06:47.970 --> 00:06:57.360
Ken Willard: doesn't commit you to one path or another right, this is another conversation that I have with customers that they say, well, so if I go to the short term support release.
00:06:57.750 --> 00:07:07.680
Ken Willard: Then I have to stay there, well, you stay there until such time as the next long term support release comes out and then you can shift the model back.
00:07:08.220 --> 00:07:27.180
Ken Willard: Right interesting that we're talking about sex here this actually happened with several customers that i've worked with back when V sphere, six, seven was released so obviously a few years ago, but the then long term support release didn't support the sphere version, six, seven.
00:07:28.230 --> 00:07:36.180
Ken Willard: So then those customers moved on to a short term support release to get the V sphere, six, seven hypervisor support.
00:07:37.050 --> 00:07:48.450
Ken Willard: And then, when the next long term support bundle came out they rolled right back to the lts model, so you have your choices right, you can manage that, so that it stays in line with your own it practices.
00:07:49.830 --> 00:07:58.110
Ken Willard: So sort of some of the big hitters right, and this is a very short list of what we got in the six.oh release.
00:07:59.340 --> 00:08:02.580
Ken Willard: But some things like replication factor one.
00:08:04.080 --> 00:08:21.420
Ken Willard: Right and if you're kind of thinking about you know why would I want less replication factor capability right, why would I want less redundancy of my data, the thought here is, we often have things that are doing some kind of application level clustering.
00:08:22.530 --> 00:08:30.540
Ken Willard: Active directory is a great example of that you're not going to deploy a single active directory controller vm into an environment you're going to deploy.
00:08:31.410 --> 00:08:45.270
Ken Willard: In generally receive it in small shops, a minimum of three oftentimes more well if i'm already deploying multiple copies of a service or an application within my environment.
00:08:45.990 --> 00:08:59.790
Ken Willard: I don't maybe I don't necessarily need multiple copies of that data on disk as well, so we now have the ability to store virtual machines in a replication factor one, in other words.
00:09:00.390 --> 00:09:12.690
Ken Willard: No on disk redundancy of that virtual machine data but it's intended to support those environments where you're running multiple copies of a particular vm or a particular application bill anyway.
00:09:13.350 --> 00:09:21.990
Ken Willard: So you're not double investing in that on disk storage right those kinds of things Meta data rewarding, this is an interesting one.
00:09:22.980 --> 00:09:32.190
Ken Willard: Right we've always had the idea of the metadata behavior, but when we look at events like virtual machine migrations or.
00:09:32.970 --> 00:09:42.480
Ken Willard: The sphere ha events where a virtual machine is restarted on another host we could actually see a little slow down in the performance of that vm for a little bit.
00:09:43.230 --> 00:09:55.620
Ken Willard: Because the metadata about that vm might not be readily available on the node where that vm was running right we think about the metadata again those Cassandra database services.
00:09:56.220 --> 00:10:04.380
Ken Willard: And that's a distributed model, it runs across multiple nodes of the cluster architecture for that redundancy and resiliency purpose.
00:10:05.100 --> 00:10:22.770
Ken Willard: So now, when we have something like an H a restart of it or even just a simple the motion migration of a vm for maybe drs load balancing rules, the metadata for that vm will get rewarded on the new note as well and we'll see bump in performance.
00:10:25.500 --> 00:10:27.240
Ken Willard: The autonomous extent store.
00:10:28.470 --> 00:10:37.110
Ken Willard: there's quite actually a big conversation around that when we get into if anybody was interested maybe during the Q amp a but the idea behind me a total of 16 store.
00:10:37.980 --> 00:10:53.040
Ken Willard: We have talked about data locality, from the beginning of the new tannic architecture, but again kind of following on that Meta data reward and conversation the Cassandra metadata for your virtual machines was a distributed model.
00:10:54.360 --> 00:11:02.100
Ken Willard: And so we could sometimes see some performance his, particularly when we were ingesting a large sets of data.
00:11:02.850 --> 00:11:09.930
Ken Willard: you're thinking about something like a dupe big data analysis, environment and you're building it out, for the first time and populating the data sets.
00:11:10.260 --> 00:11:17.070
Ken Willard: or you're building out one of the on premises data lake architectures and so you're bringing in large data set ingestion.
00:11:18.060 --> 00:11:23.010
Ken Willard: The fact that the Cassandra metadata database architecture was distributed.
00:11:24.000 --> 00:11:42.600
Ken Willard: There was no concept previously of that metadata or existing just on one note, to start with, and then being able to be made redundant after the fact, it was always distributed right from the start, which meant we paid a little bit of a right latency performance hit around those events.
00:11:44.130 --> 00:11:47.580
Ken Willard: Then, with 510 we got what was called the autonomous extend store.
00:11:48.660 --> 00:12:00.570
Ken Willard: And if your cluster had at least eight solid state devices or any one in via me device per node the autonomous extended store could keep.
00:12:01.110 --> 00:12:06.060
Ken Willard: A primary copy of the metadata locally, as we were ingesting the large sets of data.
00:12:06.840 --> 00:12:14.640
Ken Willard: And then worry about the redundancy after the fact that it permission a massive performance increase in bringing in those large data sets.
00:12:15.390 --> 00:12:22.200
Ken Willard: But the trick to the autonomous extent store I guess the catch is maybe the better way to say that it originally only worked in brand new clusters.
00:12:22.950 --> 00:12:27.540
Ken Willard: We now have what they're calling the autonomous extent store brownfield implementation.
00:12:27.990 --> 00:12:37.260
Ken Willard: That is if you're going to a progressive hardware upgrade maybe just upgrading the number of disks in your nose or the envy and the architecture of your nodes.
00:12:38.250 --> 00:12:51.690
Ken Willard: The autonomous extent store can now be activated in those clusters that previously did not meet the hardware configuration when they were created right and that was previously, not an option, Italy could be done when you build the cluster.
00:12:53.700 --> 00:12:59.940
Ken Willard: A little bit on the Acropolis hypervisor metro availability conversation I mentioned that simply because.
00:13:00.990 --> 00:13:10.710
Ken Willard: there's two things at play here when we think about metro support the metro behavior that metro function gives us zero.
00:13:11.820 --> 00:13:12.840
Ken Willard: recovery.
00:13:14.610 --> 00:13:35.700
Ken Willard: Point Objective I want to make sure I was using the right accurate in there it's real time replication of the data between two clusters we've always had metro architecture, because on the asx I hypervisor because it tied into the native ios six I high availability services.
00:13:37.470 --> 00:13:46.470
Ken Willard: The reason I brought this up in this particular presentation is because a lot of you are looking at running both SSI and Acropolis hypervisor today.
00:13:47.220 --> 00:13:52.770
Ken Willard: You may have some sites where you're picking one hypervisor or the other, because of cost and functionality decisions.
00:13:53.730 --> 00:14:00.030
Ken Willard: And so we had historically been able to do synchronous replication with the Acropolis hypervisor.
00:14:00.660 --> 00:14:11.820
Ken Willard: But not the metro management and thinking about the metro availability distinction is it leverages high availability services of the hypervisor to automatically do fail overs.
00:14:12.420 --> 00:14:32.070
Ken Willard: If we have a failure of one of the two sites that's replicating so For those of you that are looking at those zero downtime events from a data set and a near zero downtime recovery window for your recovery time objective, you can do that with both SSI and the Acropolis hypervisor.
00:14:33.180 --> 00:14:40.500
Ken Willard: And then, finally, the last bullet up, there is the fact that near sink has been expanded to support multiple sites.
00:14:41.550 --> 00:14:58.230
Ken Willard: gives you a much better fail over model and folks, this is a tiny snippet of the Acropolis os version six announcement, so I just posted the link to the full announcement in the chat window.
00:15:04.020 --> 00:15:14.730
Ken Willard: we've got a few slides that kind of do some background work and honestly we're going to move through these really quickly because I don't think there's anything that's new or revolutionary here, this is stuff that we all know.
00:15:15.600 --> 00:15:28.920
Ken Willard: we've kind of seen this evolution of the data Center from client server to virtualized and, frankly, a lot of the impact was there was on storage and networking infrastructure changing from.
00:15:29.970 --> 00:15:38.340
Ken Willard: Frankly, a little slower transaction rate things to workloads that are much higher transaction rate on the disk architecture.
00:15:38.940 --> 00:15:49.200
Ken Willard: And workloads that instead of being what we traditionally think of as north, south traffic for communication lot of east, west right a lot of density of communication between vm.
00:15:49.680 --> 00:15:59.190
Ken Willard: Sometimes, on the same hypervisor sometimes hopping hypervisor the hypervisor adjacent Lee and so that is all kind of snowballed then of course we're finally into this cloud.
00:15:59.940 --> 00:16:05.910
Ken Willard: concept architecture, where folks are using cloud is this really broad really generic umbrella.
00:16:06.840 --> 00:16:12.300
Ken Willard: But it sort of helps us started to find, especially the more we think about automation in the data Center.
00:16:12.780 --> 00:16:32.520
Ken Willard: and putting management systems in front of our environment that can do rest API calls or even scripted automation calls and making that much cleaner and being able to support density of data and density of network communication that's kind of where we've seen this come from.
00:16:35.040 --> 00:16:42.030
Ken Willard: web scale i'm going to spend nearly no time on this right, we know what this means the number of vm.
00:16:42.660 --> 00:16:56.040
Ken Willard: And the responsiveness of either recovery or the ability to deploy new workloads continues to grow, and when you think about the the cloud providers or those very cloud centric applications like Facebook.
00:16:56.850 --> 00:17:14.160
Ken Willard: they've driven a lot of innovation in that and and so it's based on frankly cheap commodity x86 hardware and yet being able to ensure very high performance and very high reliability with ideally inexpensive hardware.
00:17:16.380 --> 00:17:23.460
Ken Willard: And we want to get into a space where we are being able to leverage more automation because, as we think about.
00:17:24.360 --> 00:17:38.460
Ken Willard: Some parts of the application may run on premises some parts of the application may run out in the cloud the firewall the network, even the backend storage performance configuration can get more and more complex.
00:17:40.500 --> 00:17:49.680
Ken Willard: Right, and this also sort of moved us into this idea of trying to simplify complexity, not just in operations.
00:17:50.340 --> 00:17:56.820
Ken Willard: But when we think about hyper converged right, this is really talking about simplifying that complexity.
00:17:57.690 --> 00:18:07.290
Ken Willard: Specific to storage, we think about the traditional what most folks consider the three tier model right you had your.
00:18:07.860 --> 00:18:21.390
Ken Willard: compute layer where the execution of the Code was being run, we often had some kind of a dedicated storage infrastructure or storage fabric, if you come from that industry.
00:18:21.810 --> 00:18:35.130
Ken Willard: And that was letting those compute resources talk to them some back in traditional storage area network or network attached storage appliance that delivered your storage network.
00:18:36.960 --> 00:18:47.460
Ken Willard: and obviously today we're looking at a lot of converged architectures where we're bringing the disk right into the same chassis that's delivering compute networking.
00:18:48.660 --> 00:19:06.390
Ken Willard: It gives us more flexibility, it gives us the ability to scale capacity, at the same time, when we think about hyper converged architectures and how they deliver specifically disk resource the performance is handled and measured wildly differently.
00:19:09.420 --> 00:19:25.860
Ken Willard: New tactics specifically not only helps us address what we think about as the storage concerns, but a lot of things like business continuity concerns right frankly everything over here in this second column.
00:19:27.060 --> 00:19:31.200
Ken Willard: is primarily talking about business continuity concerns.
00:19:32.520 --> 00:19:39.390
Ken Willard: Everything kind of on the right side of the the enterprise storage section of this slide.
00:19:40.200 --> 00:19:50.430
Ken Willard: is talking about the data, efficiency and the data performance capabilities right and I just mentioned, actually now not listed on the slide the ability to do.
00:19:51.030 --> 00:20:10.350
Ken Willard: The rf one configuration, so if you're running effectively multiple copies of the same application vm because they're doing some kind of application level clustering it doesn't always make sense to keep multiple copies of those multiple vm on disk we can be more efficient about that.
00:20:13.380 --> 00:20:24.690
Ken Willard: big part of any conversation today what we think about the growing virus threats and things that are particularly damaging to operations like crypto locker viruses.
00:20:25.560 --> 00:20:33.720
Ken Willard: The new tactics approach security first they actually have, if you read much of their documentation, you know what they have they call the.
00:20:34.410 --> 00:20:45.330
Ken Willard: Security development lifecycle right it's not software development it is security, development, because as their Dev OPS team creates new functions.
00:20:45.780 --> 00:20:58.440
Ken Willard: makes changes upgrades and additions to the Acropolis os environment that gets tested at every phase it's not just a post compile How does this work now that it's all built.
00:20:58.950 --> 00:21:12.960
Ken Willard: So a lot of emphasis on security, all the way through, not only the stack itself so far as the pieces that you would be managing as the infrastructure team, but right from the development standpoint as well.
00:21:14.280 --> 00:21:39.090
Ken Willard: Right so as promised to try to move those very quickly to get into the real vmware and new tactics conversation right, so what parts of the vmware software environment software stack are supported on new tactics and if you go out and pull the documentation right, these are the components.
00:21:43.170 --> 00:21:48.000
Ken Willard: So Courtney sphere, the V cloud suite and horizon view.
00:21:49.410 --> 00:21:57.540
Ken Willard: And in my mind it often becomes some of the folks think about as a separate product but it's kind of implied in the cloud suite.
00:21:57.990 --> 00:22:12.540
Ken Willard: Right intersects is on that support in the list as well, but it's actually interested in kind of not listed as an independent thing or an independent supported product when you look at the documentation.
00:22:13.740 --> 00:22:22.110
Ken Willard: So, for most organizations today it's sort of the first and the third right they care about core server virtualization.
00:22:22.620 --> 00:22:33.960
Ken Willard: And then obviously if they're working on virtual desktops which has been more of an emphasis over the last 18 months right horizon view fully supportive there.
00:22:34.890 --> 00:22:50.160
Ken Willard: So those are the software components of the software stacks that are supported on the new tannic distributed storage fabric, when we look at V sphere, specifically and break down what functions of the sphere are supported.
00:22:51.240 --> 00:23:08.280
Ken Willard: folks it's all the stuff that we would want to do right anything that we would do it in any other storage backed V sphere architecture we're going to get with the new tannic distributed storage fabric solution running the SSI hypervisor.
00:23:09.810 --> 00:23:21.660
Ken Willard: And I think the big one, where this really comes into play in my mind what the value proposition is is here in the support for the V sphere api's for array integration.
00:23:22.560 --> 00:23:34.860
Ken Willard: Or the wallet is that right if you've not dug into the V sphere, environment, a lot, it is simply a mouthful to say V sphere can hand off a particular storage task.
00:23:35.430 --> 00:23:45.600
Ken Willard: To the distributed storage fabric, to the storage array let it do the storage work and then simply reply when the rest API request is completed.
00:23:46.800 --> 00:24:00.060
Ken Willard: There are functions that we think about the SSI hypervisor is have to historically spare cpu time so that the vm Colonel can do this actual storage work itself.
00:24:01.320 --> 00:24:10.710
Ken Willard: When we look at environments where the api's for array integration are supported that work gets handed off to the storage engine.
00:24:11.820 --> 00:24:12.960
Ken Willard: Now you make the case.
00:24:14.370 --> 00:24:34.440
Ken Willard: In the perspective of new techniques technically that still means we're spinning some cpu cycles, because that workload is getting handed off to the cpm but we get them access to those additional behaviors and the big one, is really in cloning operations.
00:24:36.000 --> 00:24:48.600
Ken Willard: I don't have time in this short window to date and time, but there are substantial differences in the way the distributed storage fabric handles cloning and snap shouting.
00:24:49.260 --> 00:25:01.500
Ken Willard: versus the way that a native SSI clone or snapshot would be invoked simply based on the fact that he had sex, I had to be built to work with multiple storage vendors.
00:25:02.070 --> 00:25:10.440
Ken Willard: I they had to have sort of a gnostic way to implement those two features that would work across third party storage vendors.
00:25:11.280 --> 00:25:28.410
Ken Willard: But when we leverage the api's for array integration we can leverage those really specific new tannic behaviors and if you've not seen this in short the way this works is I have my base vm.
00:25:29.460 --> 00:25:36.660
Ken Willard: And it has out on disks what new tactics refers to as expense.
00:25:38.520 --> 00:25:47.850
Ken Willard: I would think about traditional storage, a lot of times, the thing about the smallest unit that we're managing is called a block when we're talking about the distributed storage fabric that's called an extent.
00:25:50.880 --> 00:26:14.310
Ken Willard: We didn't have the Meta data architecture that Cassandra metadata architecture that's so critical to the distributed storage fabric it's what points us to those extends on disk right we build what's called a disk map that tells us what extends on disk are owned by a particular vm.
00:26:15.330 --> 00:26:30.030
Ken Willard: When I go to do a cloning or snapshot operation through the distributed storage fabric architecture and let's just talk cloning for the sake of this conversation, what I can do is I can mark.
00:26:31.080 --> 00:26:35.820
Ken Willard: All of the current extents on disk as read, only.
00:26:38.340 --> 00:26:41.910
Ken Willard: I can create a new virtual machine.
00:26:45.510 --> 00:26:48.600
Ken Willard: And initially for a short period of time.
00:26:49.650 --> 00:27:00.270
Ken Willard: It can share all of the exact same extents on disk when it first starts up if this map is identical.
00:27:01.650 --> 00:27:21.390
Ken Willard: And then obviously if those two beams are powered on and continuing to run their on disk condition will diverged over the course of normal operation, but we can just leave those extents that are still common and shared between the two, we can keep a single copy.
00:27:22.530 --> 00:27:28.380
Ken Willard: And we can report their disk map to different extents when they need to create updates.
00:27:29.520 --> 00:27:39.510
Ken Willard: Right, and that is a really quick really over simplified version of how the new tannic distributed storage fabric handles that real efficiency on disk.
00:27:41.160 --> 00:27:50.070
Ken Willard: And you can get to that behavior through the Center right you don't need to be using prism or prison element prism central to do that.
00:27:51.540 --> 00:28:05.070
Ken Willard: When you clone right from within the Center you can get access to that really efficient model on disk but the catch is the vm must be powered off.
00:28:06.810 --> 00:28:10.140
Ken Willard: Maybe sounds like something I want to use a template for Sam right.
00:28:11.460 --> 00:28:24.870
Ken Willard: And it may not have snapshots, that is, the sphere based snapshots in place if I want to leverage these api's for array integration and that behavior.
00:28:25.830 --> 00:28:42.150
Ken Willard: it's a bit the vm is outside of those two requirements so if it's powered on or if it has these fear based snapshots in place the system automatically shifts over and goes back to the traditional asx will manage the on disk operation for us.
00:28:45.180 --> 00:28:58.530
Ken Willard: A little bit on that, so far as exactly when you get the benefit of using the api's for array integration is detailed really well in the new tannic Bible.
00:29:00.030 --> 00:29:04.770
Ken Willard: And so I just posted into chat the specifically.
00:29:06.390 --> 00:29:12.780
Ken Willard: The talks about how new techniques and when the new tactics API for array integration gets invoked.
00:29:16.500 --> 00:29:24.690
Ken Willard: So lets you kind of the conversations around the products and features from the vmware side that are supported on top of the distributed storage fabric.
00:29:25.590 --> 00:29:41.370
Ken Willard: Whatever, that is from the other perspective right a lot of organizations are starting to look at the other things that are available from new tactics, so what other new tannic services or functions, can we support on top of the SSI hypervisor.
00:29:42.420 --> 00:29:55.650
Ken Willard: When we look at the three what new taylor's calls their data services right, these are the three data services that can be delivered from your distributed storage fabric based cluster.
00:29:56.880 --> 00:30:02.640
Ken Willard: If you're not familiar with these new tannic volumes, these are I scuzzy targets.
00:30:04.350 --> 00:30:17.250
Ken Willard: New tannic files is just exactly what you would think hey i've really messed myself up let's try this differently, you might have a little more room to word, where they are right, I scuzzy targets files.
00:30:18.300 --> 00:30:27.210
Ken Willard: In fs and six chairs let's just say SMB shares it's faster right and then buckets are object stores.
00:30:29.280 --> 00:30:48.030
Ken Willard: We can run all of those types of data services and, obviously, each one of them have very different use cases around when you might want to use one or the other but they are all free from a data services standpoint supported with vmware.
00:30:50.580 --> 00:30:55.710
Ken Willard: And then, lastly, of course, calm anybody started looking at this.
00:30:57.570 --> 00:30:59.190
Ken Willard: The cloud.
00:31:00.360 --> 00:31:01.650
Ken Willard: application.
00:31:03.210 --> 00:31:13.410
Ken Willard: lifecycle manager tool, this is a function of prism centrally and to be really specific, you have to be.
00:31:15.270 --> 00:31:28.290
Ken Willard: No, you don't have to be ready prism central pro you can get this with some central as an add on, if I remember right, this is licensed on a per vm basis that you want to manage.
00:31:30.210 --> 00:31:42.660
Ken Willard: So when it's called well, to put it sort of in vmware language calm is a direct competitor to V realize automation.
00:31:43.530 --> 00:32:01.470
Ken Willard: Right, so if you're looking back and forth you're looking to bring more automation into your environment you're looking to be able to deploy maintain and support applications that may be part of US deployed on premises in your V sphere clusters running on new tonics.
00:32:02.550 --> 00:32:17.100
Ken Willard: Maybe you're in those mixed environments for you also running some Acropolis hypervisor and you're starting to tie into a couple of things that are public facing so you've got some azure deploy a vm or some aws deployed EC two instances.
00:32:18.150 --> 00:32:25.200
Ken Willard: Calm can manage those deployments and lifecycle operations across all of those environments for you.
00:32:27.450 --> 00:32:29.040
Ken Willard: So those are all supportive.
00:32:34.020 --> 00:32:42.480
Ken Willard: So the next thing to think about is leveraging that distributed storage fabric if you're not familiar with the language around the distributed storage fabric.
00:32:43.770 --> 00:32:51.480
Ken Willard: If you come from a more traditional storage environment you're probably used to lunch and managing storage in the construct of loans.
00:32:52.770 --> 00:33:00.870
Ken Willard: We don't have that with a software defined architecture, the distributed storage fabric is defined by storage containers.
00:33:02.130 --> 00:33:19.320
Ken Willard: And a lot of times, based on frankly when organizations stood up there, retain its environment depending on who came out to do the install there may or may not have been a lot of time with the installation engineer and see you got one container.
00:33:20.460 --> 00:33:28.650
Ken Willard: And they turned on compression and duplication and they shook your head and they said fantastic you're all set up have a great day and out the door they went.
00:33:30.480 --> 00:33:34.590
Ken Willard: Is one container with compression and the duplication, really.
00:33:35.640 --> 00:33:37.050
Ken Willard: What you want to do.
00:33:38.670 --> 00:33:43.290
Ken Willard: Probably not right, you probably want to do a little bit of data analysis.
00:33:44.850 --> 00:33:54.480
Ken Willard: It takes some time, you got to look through what's going on with the different types of applications that you run probably going to have to do some research.
00:33:55.410 --> 00:34:16.230
Ken Willard: But this is a really high level slide of different types of data set that you might be running in a new tannic environment and the various different data storage policies that new tannic recommends that data will perform best under.
00:34:23.580 --> 00:34:31.470
Ken Willard: Alright, so we are coming up about 25 minutes before the hour here so let's dig into.
00:34:32.910 --> 00:34:35.730
Ken Willard: The live DEMO was looking at a few things.
00:34:36.840 --> 00:34:42.930
Ken Willard: back and forth, with the new tactics and SSI environment.
00:34:47.100 --> 00:34:49.530
Ken Willard: me make some adjustments here.
00:35:08.070 --> 00:35:08.910
Ken Willard: alright.
00:35:13.890 --> 00:35:19.110
Ken Willard: Apologies I should have made one other adjustment before we got started here.
00:35:26.040 --> 00:35:27.840
Ken Willard: Nothing like a live DEMO right.
00:35:28.860 --> 00:35:29.910
Ken Willard: let's see if I can.
00:35:41.940 --> 00:35:45.570
Ken Willard: Try to maximize our screen real estate here real quick.
00:36:03.810 --> 00:36:07.050
Ken Willard: Okay, so this should be a little better for us.
00:36:10.590 --> 00:36:22.920
Ken Willard: So what we're looking at here is i've got a DEMO environment setup we've got the desktop and, as you can see i've got some management tabs already open here.
00:36:24.120 --> 00:36:27.330
Ken Willard: i've got my the sphere client running.
00:36:28.350 --> 00:36:31.050
Ken Willard: i've got a tab open.
00:36:32.130 --> 00:36:32.760
Ken Willard: To.
00:36:34.080 --> 00:36:42.780
Ken Willard: Prison element right the local cluster administration interface for new tactics.
00:36:44.130 --> 00:36:48.570
Ken Willard: And I also have a prism central architecture deploy.
00:36:50.580 --> 00:37:01.710
Ken Willard: One of those points of conversation and, frankly, sometimes a point of consternation around which management interface do I use.
00:37:02.880 --> 00:37:05.430
Ken Willard: The reality is, if you're working with.
00:37:06.900 --> 00:37:18.870
Ken Willard: Is exercise your hypervisor you are likely going to spend most of your time still in the Center it just makes sense, and it is the most likely operational space.
00:37:20.040 --> 00:37:23.970
Ken Willard: So let's look at a few things that we need to think about when we roll this out.
00:37:25.080 --> 00:37:41.970
Ken Willard: folks first of all it's a really basic instruction, but time coordination, I would be not doing a good service here if I didn't mention the idea that my V Center.
00:37:45.120 --> 00:37:48.120
Ken Willard: Now yeah wrong window willard try again.
00:37:49.590 --> 00:37:51.390
Ken Willard: gotta go to the management interface.
00:38:08.940 --> 00:38:09.270
Ken Willard: Okay.
00:38:11.220 --> 00:38:30.750
Ken Willard: Trust me visa shirt is set to use the same time source, the same time provider, as my individual SSI hosts right so type configuration is set up, to use the NTP time services.
00:38:33.750 --> 00:38:46.680
Ken Willard: The distributed storage fabric services are set up to use the same timekeepers so when we look at the time configuration.
00:38:48.360 --> 00:38:58.110
Ken Willard: Within prison element you'll notice the same NTP pools set up and I have that same configuration and prism central.
00:38:58.980 --> 00:39:05.280
Ken Willard: I know that's not a very exciting part of the DEMO, but it is critical to understand the time coordination.
00:39:06.120 --> 00:39:22.830
Ken Willard: and hopefully y'all pretty faithful about this, but it's really critical, especially if you're going to look at some most advanced services like new tannic files or new tannic objects, on top of your hypervisor the type coordination becomes even more important.
00:39:27.330 --> 00:39:34.620
Ken Willard: The one place where you have got to start making a mental shift is the idea of.
00:39:35.820 --> 00:39:45.000
Ken Willard: Doing update and patch management from within the sphere update manager, or if you're already on version seven the new lifecycle manager tool.
00:39:46.380 --> 00:39:50.970
Ken Willard: that's a no no right we either want to be doing that, through prism element.
00:39:52.470 --> 00:40:01.590
Ken Willard: Right so look at in prison element, you have the upgrade software capability and you can specify that you want to do a rolling hypervisor upgrade.
00:40:03.060 --> 00:40:12.450
Ken Willard: And then I can up date if I wanted to get to something newer obviously we're well past seven dot O just happens to be what this cluster is built with.
00:40:13.950 --> 00:40:25.140
Ken Willard: or we're going to the point where we can start to do some of that through prism central and under the administration service is lifecycle manager.
00:40:27.450 --> 00:40:30.420
Ken Willard: So we could do our hypervisor upgrades here.
00:40:31.620 --> 00:40:43.290
Ken Willard: Why do I care that I need to not do this in the Center because we Center has no appreciation and no knowledge of what the CBS do for us.
00:40:44.820 --> 00:40:53.940
Ken Willard: And folks, especially if you've got a smaller cluster configured with an rf have to what does that really mean that means we're planning on any one single failure.
00:40:54.840 --> 00:40:58.710
Ken Willard: And when you do your patching and you're updating of your via sex host through update manager.
00:40:59.580 --> 00:41:16.170
Ken Willard: It doesn't know or care about that cdn and once it sees that the base SSI hypervisor is online it's going to start dropping the next year sex host and putting it into maintenance mode and expecting you to power down the CVs on that next system.
00:41:17.610 --> 00:41:34.710
Ken Willard: Please be doing your passion through either prison element or prison central so that the hypervisor and the CV and get managed appropriately and you're not unintentionally, creating a multi node outage in the window.
00:41:37.800 --> 00:41:46.980
Ken Willard: The other thing we could take a look at here, as you can see i'm actually running prism central inside my environment I don't have any thing else particularly exciting running.
00:41:49.230 --> 00:41:51.660
Ken Willard: But we do have a windows server.
00:41:52.920 --> 00:41:53.340
Ken Willard: template.
00:41:54.960 --> 00:41:59.550
Ken Willard: So i'm going to do a new vm from this template here pretty quickly.
00:42:03.060 --> 00:42:04.680
Ken Willard: Oh boy, this is going to be a challenge.
00:42:11.790 --> 00:42:16.530
Ken Willard: zoom and his screen resolution are not being very kind to me.
00:42:20.610 --> 00:42:23.790
Ken Willard: Alright, well, let me do this from prison central then actually.
00:42:25.800 --> 00:42:29.190
Ken Willard: So for prison central avenue to virtual infrastructure and say vm.
00:42:31.830 --> 00:42:36.180
Ken Willard: Now the challenge here is prison central in prison element.
00:42:37.530 --> 00:42:48.810
Ken Willard: are not particularly aware, or have any connection into the cloning practices right, so this would be a create new vm environment.
00:42:51.540 --> 00:42:53.520
Ken Willard: But I could create a windows DEMO.
00:42:58.950 --> 00:43:14.430
Ken Willard: you'll notice that prism central understands that i'm running on an SSI hypervisor so I need to get that windows os specified so let's just say.
00:43:16.020 --> 00:43:18.120
Ken Willard: we're going to do server 2016.
00:43:20.430 --> 00:43:22.260
Ken Willard: or cpus.
00:43:24.210 --> 00:43:26.340
Ken Willard: or gig of memory in the short term.
00:43:29.760 --> 00:43:31.170
Ken Willard: build out disks.
00:43:33.630 --> 00:43:46.890
Ken Willard: And then, if I had multiple containers with different storage process or different storage services on them right, I could pick them we haven't done that here we've just done so far, the wonderful container.
00:43:48.540 --> 00:43:49.860
Ken Willard: build that hard drive.
00:43:51.210 --> 00:43:56.460
Ken Willard: folks bear with me i'm gonna have to steal this screen back to my other monitor to finish out this wizard.
00:44:09.360 --> 00:44:10.740
Ken Willard: Live demos are never boring.
00:44:11.910 --> 00:44:15.150
Ken Willard: And then it's time to add a network card again I.
00:44:16.710 --> 00:44:31.470
Ken Willard: have just the vm network we haven't created any others, yet and prism central is aware that there are different types of virtual next that can be provided, so we can pick the vm X net three.
00:44:32.880 --> 00:44:35.970
Ken Willard: and say add but i'm going to pull out an important distinction here.
00:44:37.650 --> 00:44:42.810
Ken Willard: When I pull this step, I know here, the only network i'm seeing is the vm network.
00:44:44.310 --> 00:44:45.720
Ken Willard: We go back to the Center.
00:44:50.040 --> 00:44:52.350
Ken Willard: If I just pick.
00:44:53.760 --> 00:44:57.840
Ken Willard: let's say one of my other running vmware and say edit that vm.
00:45:02.400 --> 00:45:05.760
Ken Willard: What I got to look at the network options here.
00:45:10.530 --> 00:45:15.270
Ken Willard: This is one of those things that you want to kind of plan for and think about.
00:45:16.800 --> 00:45:22.230
Ken Willard: The Center is going to give you all the networks that it sees in the environment, just like it always has.
00:45:22.800 --> 00:45:37.890
Ken Willard: And what you get what you saw with prison central is that back playing network and the I scuzzy port group that back in network between the hypervisor and ESF side those get filtered out.
00:45:38.970 --> 00:45:51.240
Ken Willard: Right so prism central frankly put some guard rails around and especially if you have maybe newer admins that aren't really familiar with the distributed storage fabric architecture.
00:45:52.230 --> 00:46:04.590
Ken Willard: You might want to start them in prison element of prison central because some of those new tannic specific guardrails are already going to be there they're going to be built into the user interface for you in that regard.
00:46:10.380 --> 00:46:16.260
Ken Willard: And then the last thing I want to do is, I want to take a look at storage and then we'll open for open Q amp a.
00:46:18.150 --> 00:46:31.590
Ken Willard: folks also hopefully your installation engineer had time and walk you through what you're seeing here you'll notice we've got a series of in 10 X local data stores.
00:46:33.270 --> 00:46:39.690
Ken Willard: These are the data stores, that are the local boot image for each SSI node.
00:46:41.370 --> 00:46:44.070
Ken Willard: And house the cpm.
00:46:45.570 --> 00:46:55.170
Ken Willard: Right So these are off limits for general deployment, you should not be using those for any storage, you have the default container.
00:46:56.610 --> 00:47:08.910
Ken Willard: Which is built, when the cluster gets installed and you can see, this arrived build that windows server vm I have built an ISIS directory and put my windows server ISO out there.
00:47:12.420 --> 00:47:15.540
Ken Willard: But how do I, create a new data store.
00:47:16.770 --> 00:47:27.570
Ken Willard: That is done through your choice, one of the two prism interfaces i'm going to go to the prism element interface, because a lot of you may have not deployed present central.
00:47:30.450 --> 00:47:39.510
Ken Willard: And so the here's The other thing right you see there's the default container we've got a management share we've got a self service container but those don't appear in vmware.
00:47:40.920 --> 00:47:48.690
Ken Willard: It those are reserved for new tannic functionality, so we don't mount them to the sx host by default.
00:47:50.400 --> 00:47:52.500
Ken Willard: But if I want to create a new storage container.
00:47:53.640 --> 00:47:54.990
Ken Willard: let's call this.
00:47:59.100 --> 00:48:00.360
Ken Willard: Without compression.
00:48:03.960 --> 00:48:09.390
Ken Willard: And then i've got my choice of how do I want this to be handled on my sex host.
00:48:10.950 --> 00:48:23.370
Ken Willard: Your new tactics distributed storage fabric is presented to your sex host as in fs shares so we're going to say mounts all I want to take a look at my advanced settings.
00:48:25.890 --> 00:48:31.050
Ken Willard: And I am going to turn off compression on this particular container.
00:48:33.660 --> 00:48:34.770
Ken Willard: And when I hit save.
00:48:40.140 --> 00:48:50.190
Ken Willard: It runs through it creates the new container and then confirms that it was able to mount that on all three of my hosts so now, if I go back over.
00:48:50.760 --> 00:49:02.850
Ken Willard: i'm now back in the Center and my container without compression is already there, so if I had a particular workload that should be built in a data environment.
00:49:03.300 --> 00:49:18.630
Ken Willard: Where the back end system is not already running compression right what's a good example of that how about any sequel Oracle database volume right today most modern databases run in in application compression model.
00:49:19.770 --> 00:49:24.720
Ken Willard: So I don't want to be trying to do compression that data twice I won't get any extra efficiency out of that.
00:49:26.190 --> 00:49:41.880
Ken Willard: So it lets me build the right data services around those specific types of workloads and then by simply creating the storage environment in prison element it automatically gets created well how does it automatically get created.
00:49:43.290 --> 00:49:47.370
Ken Willard: If we go to the settings for prison itself.
00:49:51.630 --> 00:50:08.700
Ken Willard: I have the ability to register to prison central and I have the ability to register to the Center so i've already put administrative credentials in the new tactics management platform that lets it talk to the sphere.
00:50:10.080 --> 00:50:15.870
Ken Willard: If I go back over to my V sphere, environment, if I can get the mouse to cooperate.
00:50:20.160 --> 00:50:30.570
Ken Willard: it's already rolled out, we could have potentially better, faster we would have seen the initiator, would have been calm that new tactics.
00:50:31.710 --> 00:50:37.140
Ken Willard: And it would have executed that mount on all three of those asx hosts.
00:50:41.160 --> 00:50:48.240
Ken Willard: So just a little bit on how you've got three different management interfaces.
00:50:50.040 --> 00:51:00.900
Ken Willard: By and large, like I said, I suspect, most of you are going to stay with the V sphere client but prism central is very V sphere century.
00:51:01.920 --> 00:51:07.740
Ken Willard: and has the ability to have those sort of new tannic specific guardrails.
00:51:10.080 --> 00:51:24.990
Ken Willard: And so i'll finish up this workflow creating my new vm right it's not configured as that windows DEMO vm i've added the network i'm gonna have to slide this back over to the other monitor just for a minute to get my resolution back.
00:51:26.010 --> 00:51:29.490
Ken Willard: Because I want to finish this workflow I just hit save.
00:51:35.610 --> 00:51:41.640
Ken Willard: And so I created a new vm called windows DEMO and I did that from prison central.
00:51:43.770 --> 00:51:51.510
Ken Willard: And now, if I go look at my virtual machine inventory there, it appears right because i've set up the credential relationships.
00:51:52.800 --> 00:51:56.820
Ken Willard: I can do my management from any of the three platforms.
00:52:07.080 --> 00:52:24.870
Ken Willard: So folks other things that you have follow up questions that have come to mind as we've been talking about the new tonics in vmware interconnection with that SSI hypervisor and the distributed storage fabric services or the management planes.
00:52:28.980 --> 00:52:43.260
Michelle Coppens :: Webinar Support: 10, I would like to second I inviting everyone in the room to post their questions or comments in the Q amp a or the chat window both found at the bottom of your screen.
00:52:43.800 --> 00:52:56.100
Michelle Coppens :: Webinar Support: with one eye on our time as those questions are coming in i'd also like to talk about why you should shoes exit certified, for your new Technics training.
00:52:57.480 --> 00:53:10.860
Michelle Coppens :: Webinar Support: So professionals like you have been training with us since 2001, and today I just certified is the only new tactics premier authorized training partner in North America.
00:53:11.700 --> 00:53:18.240
Michelle Coppens :: Webinar Support: we're proud to commit to the largest do tactics guarantee to run training schedule in North America.
00:53:18.660 --> 00:53:30.060
Michelle Coppens :: Webinar Support: And you will be able to distinguish which classes are guaranteed to run when you see the GT our staff on our schedule another great and.
00:53:30.720 --> 00:53:44.160
Michelle Coppens :: Webinar Support: A great asset of why you should train as a certified is that we offer a one to one ratio of student live infrastructure, that means no shared clusters or team labs you get your own environment to work in.
00:53:45.060 --> 00:53:52.950
Michelle Coppens :: Webinar Support: I spoke about a public training schedule and i'm going to leave a link in the chat window for everyone here.
00:53:53.700 --> 00:54:00.840
Michelle Coppens :: Webinar Support: Not only you're going to see our new tannic schedule, but you will also see the option to contact us if you do have any questions.
00:54:01.200 --> 00:54:16.230
Michelle Coppens :: Webinar Support: And if you need any more convincing about why you should train with ISIS certified we are offering a webinar exclusive savings this opportunity will give you 15% off virtual or classroom training.
00:54:16.530 --> 00:54:38.340
Michelle Coppens :: Webinar Support: or 10% off on demand subscriptions and self paced courses, you need to register by November 30 and to find all of the details about this promotion check the leg, which I just left in the chat window awesome we have a question in the Q amp a.
00:54:39.330 --> 00:54:41.010
Ken Willard: We do good question actually.
00:54:42.030 --> 00:54:43.080
Ken Willard: So the question is, I.
00:54:43.320 --> 00:54:45.270
Ken Willard: don't know who's got the the Q amp a window open.
00:54:45.330 --> 00:54:58.770
Ken Willard: But the question says, if we have V disk latency alerts for a vm that's running on top of vs XI with new tonics where do you start troubleshooting that right, are you looking at the SSI or you're looking at new tactics.
00:55:00.150 --> 00:55:01.710
Ken Willard: I would tend if it's.
00:55:03.360 --> 00:55:13.620
Ken Willard: disk latency i'm going to start with new tonics here's why, when you think about what those CVs those controller vm do for you in your environment.
00:55:14.400 --> 00:55:29.520
Ken Willard: Trying to draw some parallels again to maybe a traditional three tier architecture, we think about those external storage area networks or network attached storage platforms as having communication in points called storage providers.
00:55:30.870 --> 00:55:48.540
Ken Willard: When we think about what's happening in the new Technics hyper converged architecture, the CV is our storage provider right, it is that communication important for us and you shouldn't be having any kind of latency.
00:55:49.560 --> 00:55:58.290
Ken Willard: Between the SSI your cdn and The reason I say that is because, if we go back and take a look at the configuration.
00:55:59.550 --> 00:56:00.960
Ken Willard: i'm going to go to my hosts.
00:56:02.760 --> 00:56:06.150
Ken Willard: And I am going to look at their virtual switches.
00:56:07.350 --> 00:56:21.450
Ken Willard: And I get I get this is a little bit of an eye chart but if I scroll down, you will all have in your environments this V switch new tactics configuration.
00:56:23.490 --> 00:56:35.820
Ken Willard: you'll notice it has no physical uplinks associated with it right, it is a private communication internal to that host only that the.
00:56:36.900 --> 00:56:54.840
Ken Willard: hypervisor So if you look at this you've got the cpm and you've got a vm Colonel port defined and, by the way, folks and don't let this through, I know they labeled these I scuzzy.
00:56:56.190 --> 00:57:03.870
Ken Willard: sx does use in fs to communicate with its storage from new tactics.
00:57:04.890 --> 00:57:21.120
Ken Willard: So when we think about that communication, there should be no network latency between the host and the cdn because they're local to each other, right that see vm is running on that host, and that is internal traffic, so if you're having some disk latency issues.
00:57:22.290 --> 00:57:33.090
Ken Willard: you're going to want to start looking at the cpm and find out is that CBS overworked is it may be undersized right, these are things like there it's read latency.
00:57:33.930 --> 00:57:43.050
Ken Willard: You might want to allocate a little warm memory to that cpm so it can build a little more read io cash right but assuming that there's.
00:57:43.770 --> 00:57:52.500
Ken Willard: Nothing that's been modified that's one of the other things, you should never ever modify that V switch new tactics and the architecture.
00:57:53.130 --> 00:58:04.470
Ken Willard: So, assuming that that's true and nothing's been modified or miss configured with that switch i'd love to see if maybe i'll can be a little more resource to the cpm would help that.
00:58:05.100 --> 00:58:16.410
Ken Willard: They haven't always tell you, hopefully, you have the experience, but if you've got a question open a support ticket right new tanning support is fantastic at working through these things with you.
00:58:17.610 --> 00:58:25.740
Ken Willard: Great question all right second budget where would you do software and firmware updates for the hosts.
00:58:26.850 --> 00:58:49.650
Ken Willard: Again I would be doing that, through either if you're not going to deploy prism central I would be doing it through prism element, simply because of the reboot cycles on those scenarios and the fact that vmware update manager, you know, even if you're doing something like.
00:58:51.750 --> 00:59:01.020
Ken Willard: Other vendors software patch in your ear sex host or firmware updates it's not going to necessarily wait for the CVs to completely come back online.
00:59:01.770 --> 00:59:09.390
Ken Willard: and start all that services before it tries to move on and get the next toast to go into maintenance mode, so you could.
00:59:09.900 --> 00:59:21.150
Ken Willard: Either put yourself at a situation where you've got too many hosts down from a resiliency standpoint and certainly you could create some congestion on those hosts that are still up and running.
00:59:21.570 --> 00:59:27.570
Ken Willard: Depending on how big your cluster so yeah platform for more updates for hosts also through personally.
00:59:29.760 --> 00:59:30.330
Ken Willard: Good question.
00:59:33.870 --> 00:59:47.730
Michelle Coppens :: Webinar Support: Thank you, Ken and Thank you everyone for attending today, we have reached the end of our webinar as mentioned, we will be following up with an email in the next few days, where you will also.
00:59:48.780 --> 01:00:08.400
Michelle Coppens :: Webinar Support: receive a copy of the recording if there are any questions, we want to encourage you to contact us i'll leave our site once again in the chat window do reach out with any questions, and thank you, Ken excellent job as always enjoy your day everyone.