00:00:03.120 --> 00:00:14.370
Michelle Coppens :: Webinar Producer: Hello everyone and welcome to today's webinar titled explore new tactics is hyper converged infrastructure features and tools. Our speaker today is Ken Willard
00:00:14.910 --> 00:00:29.790
Michelle Coppens :: Webinar Producer: Ken specializes in system virtualization and consolidation at both the server and desktop level helping technology teams approach virtualization while considering the technical organizational and political impact.
00:00:30.330 --> 00:00:40.740
Michelle Coppens :: Webinar Producer: Ken has worked with IT organizations from the commercial government and nonprofit verticals addressing the virtualization in each of these unique environments.
00:00:41.430 --> 00:01:01.320
Michelle Coppens :: Webinar Producer: In addition to delivering training to both the business partner and end user communities. Ken has also worked with the tech data channel community to assist with pre sale consulting very impressively since 2016 Ken has delivered over 50 new tactics training events to nearly 500 students
00:01:02.340 --> 00:01:08.100
Michelle Coppens :: Webinar Producer: Now before we get started with today's webinar. I want to talk about the functionalities of this platform.
00:01:08.820 --> 00:01:20.910
Michelle Coppens :: Webinar Producer: As mentioned during the webinar. Everyone's microphones will be muted. So if you have any questions, I want to encourage you to post them in the question and answer box at the bottom of your screen.
00:01:21.270 --> 00:01:33.750
Michelle Coppens :: Webinar Producer: You should see a small q AMP. A icon at the bottom toolbar of your screen will have a dedicated question answer session at the end of the presentation, but don't hesitate to post your questions as soon as they come up.
00:01:34.980 --> 00:01:42.720
Michelle Coppens :: Webinar Producer: Today's webinar is being recorded and we're going to send a copy out to everyone there by the end of this week or early next week.
00:01:43.410 --> 00:01:54.330
Michelle Coppens :: Webinar Producer: And stick around till the end of the session where I will share a special promo which can save you some money on your new tannic straining. Alright, so you can take it away can
00:01:55.020 --> 00:01:56.250
Ken Willard: Michelle, thank you very much.
00:01:57.480 --> 00:02:06.360
Ken Willard: Fantastic introduction there and you actually pulled out some stats that I wasn't aware of so far as the the training events. So that was kind of a cool number for me to hear
00:02:07.350 --> 00:02:12.510
Ken Willard: Well welcome everybody. We're going to talk about just a little tiny bit on the front end here.
00:02:13.320 --> 00:02:23.070
Ken Willard: About hyper converged in general sort of where that's starting to fit into the data center today and obviously primary emphasis on this conversation is around
00:02:23.490 --> 00:02:35.580
Ken Willard: The new Chantix hyper converged offering overall. So let's talk specifically what they have in what we think about as their prison or their ALS environment.
00:02:36.570 --> 00:02:47.100
Ken Willard: And then we get into some of the other products that sort of wrap around that what makes up the entire family of the new tannic is offering. And then finally, a bit of a live demo at the end.
00:02:47.940 --> 00:02:57.450
Ken Willard: Just in case you've not already had a chance to look at, or work with the new tonics user interfaces. We want to show you a little bit of prison element which is their
00:02:57.930 --> 00:03:13.470
Ken Willard: Management interface that has the scope of a single cluster from the hyper converged standpoint and then there's single pane of glass management tool that is called prism central and that is intended to be a multi cluster management architecture.
00:03:17.340 --> 00:03:20.790
Ken Willard: So if we look at really how things have sort of evolved.
00:03:22.080 --> 00:03:30.180
Ken Willard: Right, as I see in the data center has changed, you go back to the 90s. It was a very client server focused model.
00:03:31.380 --> 00:03:42.600
Ken Willard: And that had some particular drawbacks. Most notably, often in efficiency in utilization and return on investment from it dollars spent
00:03:43.320 --> 00:03:54.030
Ken Willard: We have this idea of one server one less than one application due to potential interaction between applications if we tried to run multiples on the single host
00:03:54.750 --> 00:04:02.010
Ken Willard: If one of them had an issue and crashed. It was likely to take down the entire underlying OS. So that meant we lost multiple applications.
00:04:02.550 --> 00:04:11.520
Ken Willard: And so it's a pretty inefficient model from when we started looking at virtualization, we were doing virtualization to consolidation assessments and impact assessments.
00:04:12.300 --> 00:04:23.040
Ken Willard: We were finding pretty consistently that folks were using on an average something between four and 8% of the CPU in an individual server.
00:04:23.940 --> 00:04:35.880
Ken Willard: And from a ram perspective generally somewhere between 60 and 70% of the memory installed in a particular server. See, but if you just take the high watermark from the memory perspective.
00:04:37.020 --> 00:04:38.700
Ken Willard: 70% utilization
00:04:39.720 --> 00:04:43.440
Ken Willard: If you want to sort of compare that to something that you live in work with every day.
00:04:44.220 --> 00:04:53.280
Ken Willard: Would be about like buying a gallon of milk drinking 70% of it taking that 30% of the remains port down the drain and go get another gallon of milk.
00:04:53.880 --> 00:05:04.230
Ken Willard: And that's kind of what we were doing from the physical server perspective of the 90s course we started seeing the, the late 90s, early 2000s, the introduction of virtualization.
00:05:05.460 --> 00:05:16.050
Ken Willard: VMware really starts to make a presence in the data center for themselves. And we see those utilization rates go up on our server infrastructure.
00:05:16.590 --> 00:05:29.010
Ken Willard: We now have a secure way to run multiple workloads on a single piece of hardware and that gives us much better financial ROI. When we think about the server component of what's going on in the data center.
00:05:30.450 --> 00:05:34.470
Ken Willard: But the back end of that is often very complex.
00:05:35.520 --> 00:05:42.600
Ken Willard: We've got multi tier storage architectures. Right. Well, we consider that traditional three tier storage architecture.
00:05:43.200 --> 00:05:49.200
Ken Willard: It means different skill sets we have different teams operating and managing within the data center.
00:05:49.680 --> 00:06:04.770
Ken Willard: With different capabilities different workflows different ways to evaluate their success. And we all know, frankly, when it comes to the data center, the human capital is more often the most expensive part of the data center equation.
00:06:06.750 --> 00:06:11.310
Ken Willard: And so while we got some good economic improvements with virtualization.
00:06:12.330 --> 00:06:20.010
Ken Willard: We're really starting to capitalize and make things as efficient as possible until we started looking at some shifts that were happening.
00:06:20.940 --> 00:06:34.950
Ken Willard: When we think about the cloud generation. And that was really sort of founded with the likes of Amazon and Google frankly to start with and then we saw organizations like Facebook start to come into
00:06:35.370 --> 00:06:46.770
Ken Willard: The environment and they needed to run their back end infrastructures in a way that was completely different from what we thought about as traditional IT data centers.
00:06:47.430 --> 00:06:58.440
Ken Willard: The concept of something called web scale architecture came into being. But it was a different way to consider resiliency and availability and scalability decisions.
00:06:58.890 --> 00:07:08.970
Ken Willard: And how do you make that work in these massive architectures and so out of that came obviously cloud deployments from
00:07:09.420 --> 00:07:14.550
Ken Willard: Google Cloud Platform to Amazon Web Services, we see there's your reference the pier.
00:07:15.180 --> 00:07:25.050
Ken Willard: If you're running global operations today, you're probably thinking about the Alibaba cloud in the Asia Pacific region, right, we now have these global architectures.
00:07:26.010 --> 00:07:39.600
Ken Willard: And because of that, we've now got a different way that we're starting to think about not only what we do from public facing cloud deployed applications to our own on premises operations.
00:07:41.520 --> 00:08:02.100
Ken Willard: When we think about what happened with the web scale approach, it meant that we had very, very small slices of compute. We had extremely resilient software and physical architectures. No single point of failure.
00:08:03.480 --> 00:08:05.460
Ken Willard: Always on environments.
00:08:07.140 --> 00:08:12.030
Ken Willard: And the idea was to build that scale and that resiliency.
00:08:13.140 --> 00:08:23.580
Ken Willard: needed a little bit of a different way to look at that maybe sometimes from the hardware perspective, instead of partnering with some of the traditional hardware vendors, we all know that.
00:08:24.390 --> 00:08:32.160
Ken Willard: Facebook and Google started with off the shelf sort of generic x86 hardware.
00:08:32.850 --> 00:08:44.250
Ken Willard: Amazon's take them out of step further. They've got their natural system which is unbranded by any of the big hardware vendors, but built a very specific specifications.
00:08:44.820 --> 00:08:53.940
Ken Willard: But no special purpose environments. All of the intelligence, all of the management all the capabilities built into the software.
00:08:54.480 --> 00:09:06.480
Ken Willard: So if I want to upgrade a component or I want to upgrade a process or a behavior in my data center infrastructure. I don't have to worry about. Do I have to swap out a piece of hardware to make that work.
00:09:07.710 --> 00:09:10.890
Ken Willard: I rewrite the software and the capabilities there.
00:09:11.940 --> 00:09:23.670
Ken Willard: Right, so it gives us a whole new way to look at operations. And this was originally reserved just for those big cloud vendors. They were the folks that were thinking about this.
00:09:24.660 --> 00:09:39.780
Ken Willard: But then that idea started to trickle down. What if we can run traditional corporate or company owned it operations. The same way that we saw these big cloud providers delivering web scale infrastructure.
00:09:40.980 --> 00:09:52.590
Ken Willard: And that's where a lot of us are today. A lot of organizations are on the road to that completely software defined sort of approach where, to be blunt
00:09:53.040 --> 00:10:10.770
Ken Willard: The hardware is a commodity and I don't really care what it is and the power, the controls and the intelligence all lie in the software and if I want to change a function changes security policy implement a new approach to something to software level change.
00:10:12.450 --> 00:10:17.280
Ken Willard: So we think about that specifically as it relates to new tonics
00:10:19.020 --> 00:10:38.190
Ken Willard: We start to think about how we get the environment, capable of supporting that in most cases our traditional three tier architecture is are not going to lend themselves well to that sort of a software driven approach. So we want to modernize with a hyper converged platform.
00:10:40.020 --> 00:10:45.090
Ken Willard: That gives us the underpinnings to be able to start to build an Enterprise Cloud.
00:10:46.440 --> 00:10:52.830
Ken Willard: And we're thinking about that now from an on premises perspective, right, why don't we call it a cloud. It's all about the management.
00:10:53.340 --> 00:10:57.060
Ken Willard: And how do we deploy resources. How do we manage them through their life cycle.
00:10:57.840 --> 00:11:07.890
Ken Willard: And then for some of you that may mean we're going to bridge that into a multi cloud architecture where part of the application. The architecture runs on premises.
00:11:08.280 --> 00:11:25.440
Ken Willard: And part of it runs in one of the public cloud providers, but that's not a requirement. Right. What we're really thinking about is making sure that we can help you get to this stage, so that you've got that responsiveness flexibility and no single point of failure.
00:11:28.080 --> 00:11:34.470
Ken Willard: I especially with, think about what most of us have our environments today traditional three tier architecture.
00:11:35.700 --> 00:11:46.410
Ken Willard: Lots of vendors to integrate lots of vendor specific configurations and models that we need to implement
00:11:47.760 --> 00:11:50.400
Ken Willard: Right. It's time consuming on the front.
00:11:51.570 --> 00:12:03.810
Ken Willard: Most of you probably have project teams or if you don't have project teams at a minimum, you've got a an Excel spreadsheet that lays out everything you got to do when you start thinking about a new deployment.
00:12:04.860 --> 00:12:20.160
Ken Willard: Right. It is a big process to get new hardware and new architecture deployed in the data center today. As a general rule, and when we think about, especially those traditional three tier architectures, they're challenging to maintain over their life cycle.
00:12:21.210 --> 00:12:31.290
Ken Willard: Especially because we're talking about now multi vendor deployments with interdependencies it's really tough sometimes to do the troubleshooting.
00:12:32.670 --> 00:12:41.880
Ken Willard: Lots of planning has to go into upgrade operations to make sure that upgrading one part one component of the system does it break something else.
00:12:43.260 --> 00:12:55.800
Ken Willard: And we talked about. I mentioned earlier, in most cases, the most expensive asset in the data center is the human capital I us, the people that make the data center do what it needs to do.
00:12:56.580 --> 00:13:06.270
Ken Willard: And when we're in heavy multi vendor integrated environments folks we wind up spending most of our time on
00:13:06.990 --> 00:13:26.190
Ken Willard: care and feeding of that environment, instead of figuring out new ways to deliver a service better make an appt perform faster make things better integrated right no time for innovation and creativity because we're spending all of our time and care and feeding operations.
00:13:28.500 --> 00:13:48.480
Ken Willard: So the idea behind what we're thinking about today, particularly with hyper converged in the new technics vision for how that rolls out he's really this idea of bringing the cloud operationally management design principles and bringing those on premises inside the corporate data center.
00:13:49.500 --> 00:13:56.190
Ken Willard: So all of the things that we think about that Google, Facebook and Amazon really pioneered
00:13:57.330 --> 00:14:11.070
Ken Willard: How do we bring that into our on premises operations faster deployments grow as we need simplified management, by the way, you notice I skipped actually saying the phrase one click operation.
00:14:12.150 --> 00:14:23.100
Ken Willard: I don't know about you, but I've never used the single software product that one click actually did anything for me but simplified operations cleaner workflows unified workflows.
00:14:26.010 --> 00:14:30.090
Ken Willard: So that's what we get with the new tannic environment.
00:14:31.500 --> 00:14:44.760
Ken Willard: And the foundation of this is. And you've probably seen the the branding, the Acropolis OS. Well, honestly, folks, the Acropolis OS is just a set of services.
00:14:45.330 --> 00:14:56.730
Ken Willard: That run on every node of a new tannic cluster and give us things like data services and the hardware integration and the administrative controls.
00:14:58.170 --> 00:15:00.990
Ken Willard: All in one user interface.
00:15:02.820 --> 00:15:04.740
Ken Willard: So let's look at how this starts to come together.
00:15:05.940 --> 00:15:23.970
Ken Willard: We think about traditional three tier architecture, you've got some makeup of disk in the back end. And that's generally presented out for redundancy through a tube controller model.
00:15:25.650 --> 00:15:32.520
Ken Willard: Will and it says a bit on scalability. Those two controllers. That's generally all we're ever going to get out of a chassis.
00:15:33.180 --> 00:15:50.310
Ken Willard: And so if those two controllers together can generate hundred thousand I ops, that's great. But then as we started to add more and more servers, more and more nodes that connect and communicate to those two controllers, we started to carve up that resource.
00:15:51.900 --> 00:15:54.900
Ken Willard: When you look at hyper converged.
00:15:56.250 --> 00:16:03.960
Ken Willard: We take away the three tier part of the storage architecture and we fold that into local storage.
00:16:04.980 --> 00:16:11.940
Ken Willard: Right, let's be clear, this is not a new tannic specific concept. This is the idea that we get when we talk hyper converged in general.
00:16:13.260 --> 00:16:19.230
Ken Willard: And so I now have local disk very good performance.
00:16:20.310 --> 00:16:28.830
Ken Willard: And then this is where the new tannic specific piece starts to come into play with new tonics, we have what we call a controller VM.
00:16:30.390 --> 00:16:41.190
Ken Willard: And those controllers. The two that we used to see on the external storage arrays. Right. I now get one of those controllers for every node in the cluster.
00:16:42.600 --> 00:16:56.010
Ken Willard: Now my limited hundred thousand I ops that I had an external storage enclosure. Well now, guess what, every time I add a new node. I'm adding a new storage process or a new storage controller.
00:16:56.610 --> 00:17:05.130
Ken Willard: I'm getting the ability to scale. My disk throughput performance as I scale, the number of nodes that need to talk to that disk.
00:17:07.470 --> 00:17:17.100
Ken Willard: And so this lets me be able to start small, build as I need right not pay for a lot of additional resource in advance.
00:17:19.320 --> 00:17:27.270
Ken Willard: And if you've read much about the tactics. You know that we have the idea of data locality which optimizes the communications.
00:17:27.960 --> 00:17:43.410
Ken Willard: These VM that are running on a particular node we optimize the storage to keep their data local to that node with resiliency redundant copies distributed throughout other nodes in the cluster. So we don't have a single point of failure.
00:17:45.060 --> 00:17:50.610
Ken Willard: And this gives us the ability that as we need to grow over time, we can mix.
00:17:51.120 --> 00:18:09.450
Ken Willard: Different sizes, different types of nodes nodes that have different storage capacities nodes that are storage only or compute only depending on the kind of workloads. We need to run in our environment gives us an extremely flexible, scalable redundant architecture.
00:18:14.280 --> 00:18:32.310
Ken Willard: So when we think about this. We've now got a great way to glue everything together that acropolis OS and that gives us all of those operational flexibility pieces. But how do we start to pull this together from an administrative perspective.
00:18:33.360 --> 00:18:35.100
Ken Willard: And that's where prism comes in.
00:18:36.990 --> 00:18:41.160
Ken Willard: Prison really simplifies our operations.
00:18:42.360 --> 00:18:57.150
Ken Willard: We've got a full stack of management analytics built right in. All HTML5 driven. So really fast clean highly compatible in how we access that
00:18:59.880 --> 00:19:13.020
Ken Willard: We get great analysis on a per entity basis. So here we're looking at specifics around a particular virtual machine. And we've selected the VM and the top
00:19:13.740 --> 00:19:27.300
Ken Willard: And then in the bottom we get all of the details and what is it doing from a CPU standpoint. What are they doing from a memory standpoint. What kind of IO, is it driving through the infrastructure.
00:19:29.130 --> 00:19:31.230
Ken Willard: Really good analytics.
00:19:33.210 --> 00:19:52.710
Ken Willard: The ability to graphically look at what's going on cluster wide. So in this case, we're looking at the diagram view of the hardware that makes up our cluster, we see each node represented in the top and then that cluster wide metric view at the bottom.
00:19:56.190 --> 00:20:04.020
Ken Willard: So what kind of view from storage. The other thing is if you've done any looking at new tactics, you know, this is our main pull down
00:20:04.410 --> 00:20:23.520
Ken Willard: And under that we have things like this storage administration, the virtual machine administration and each one of those categories has its own dashboard, which gives you a very quick summary view of what's going on in relationship to that component or that aspect of your infrastructure.
00:20:24.690 --> 00:20:45.630
Ken Willard: And then we can start to drill down, looking at the specifics of alerts and events going on in the environment. How healthy is the cluster how healthy are my VM. Do I have configuration concerns that I need to be drilling into right all presented in a very clean format.
00:20:47.370 --> 00:20:52.440
Ken Willard: And then, of course, a couple of the other things that you've probably seen in other new tannic conversations
00:20:53.520 --> 00:20:56.580
Ken Willard: Is the ability to do some forward looking
00:20:57.840 --> 00:21:09.900
Ken Willard: Right, I know I've got a certain amount of projects that have been deployed. We've had a busy season this quarter so far as new VM and new resources being consumed.
00:21:10.410 --> 00:21:23.970
Ken Willard: Given what's been going on. Where am I on a runway perspective. Am I about to have a problem with CPU capacity or disk capacity right lets me have those forward looking, analytics, as well.
00:21:26.760 --> 00:21:41.910
Ken Willard: From a troubleshooting perspective, some great graphics tools to start to map details, particularly as it relates to network in one of the most critical parts of your data center infrastructure.
00:21:42.660 --> 00:21:56.700
Ken Willard: And so we can see VM running as they connect through the virtual that we're getting the structure of the host of they're running out to the physical switch infrastructure in your top of rack environment.
00:21:58.170 --> 00:22:05.130
Ken Willard: And depending on the team that manages your physical switch infrastructure how frankly flexible. They are what they'll give you
00:22:06.090 --> 00:22:20.610
Ken Willard: If we can get CDP or LLP turned on, we can get some great metrics back with either of those protocols and then if I want to even look at some specific performance throughput on individual ports.
00:22:21.390 --> 00:22:31.620
Ken Willard: If we can get SNP data, I can pull all of that back and presented in these graphic elements, right in the cluster management tools.
00:22:34.680 --> 00:22:39.150
Ken Willard: It's so great resources from the overall management.
00:22:42.210 --> 00:22:51.510
Ken Willard: So one of the value propositions what we were just talking about is this idea of not having traditional external storage cabinets and a three tiered storage architecture.
00:22:52.320 --> 00:23:01.380
Ken Willard: And you're scratching your head and going, Well, yeah, but I've got some fantastic tools in that extra cabinet right it will do the duplication.
00:23:01.800 --> 00:23:14.700
Ken Willard: It'll do compression, I can replicate that cabinet from my Cleveland data center to my Omaha data center for disaster recovery and I don't really want to give up all of those enterprise class data services.
00:23:16.740 --> 00:23:28.260
Ken Willard: Right. That is part of the core behavior of that acropolis LS those things that we think about from core data services.
00:23:29.400 --> 00:23:32.130
Ken Willard: In storage snapshot and cloning.
00:23:33.360 --> 00:23:46.110
Ken Willard: Intelligent data tearing I mentioned compression DD right all of those types of things, as well as the ability to replicate to other locations, if we need to.
00:23:47.460 --> 00:23:54.480
Ken Willard: All native behaviors of that acropolis OS what's running your new tannic clusters.
00:23:56.460 --> 00:24:01.830
Ken Willard: In addition to that, we also all know how critical security is in the data center today.
00:24:03.360 --> 00:24:24.960
Ken Willard: I'm doing threats new day zero events are a constant part of our lives. So the new tax environment is very resilient. We've got some great configurable options around data security but I folks. I think the biggest one is
00:24:26.220 --> 00:24:28.230
Ken Willard: The self healing aspect of this
00:24:29.370 --> 00:24:36.210
Ken Willard: Right there is a security management and automation tool set that is part of a new tannic cluster deployment.
00:24:36.930 --> 00:24:44.700
Ken Willard: And you can enable that. And it will then at regular intervals hourly, daily, weekly, depending on
00:24:45.240 --> 00:25:05.400
Ken Willard: Your industry what your response profiles need to be those kinds of things. It will scan your cluster and ensure standard configurations proper security policies down to the ability to verify proper file level permissions on key system files in the new technics architecture.
00:25:06.420 --> 00:25:22.320
Ken Willard: We can do that at that controller VM layer. And if you're running the Acropolis hypervisor. The new tonics native hypervisor. We can do that at the underlying hypervisor as well so extremely powerful storage and security management.
00:25:27.120 --> 00:25:28.560
Ken Willard: So we think about this.
00:25:30.390 --> 00:25:35.010
Ken Willard: Primarily today. We're seeing folks that talk about the choice of hypervisor.
00:25:36.180 --> 00:25:45.450
Ken Willard: Right, that's one of the great things about this new tannic hyper converged at its core is a storage platform. It is a hyper converged platform.
00:25:45.930 --> 00:25:53.310
Ken Willard: And with that, you could be running traditional Hyper V, if you've got an investment in Hyper V in your data center already
00:25:53.850 --> 00:26:08.430
Ken Willard: Traditional the SSI. If that's your hypervisor of choice. You don't have to replace the virtualization layer, but we are seeing many organizations, choose the new tonics native acropolis hypervisor.
00:26:11.070 --> 00:26:28.260
Ken Willard: With the Acropolis hypervisor and some variant of JVM. They started with K VM and build some of their own services and operations into it, it natively obviously ties into both the prism element and prism central administrative panels.
00:26:29.430 --> 00:26:45.930
Ken Willard: And folks, one of the biggest things is when you select the Acropolis hypervisor your virtual networking becomes open virtual switch and that lets you then start to implement things like micro segmentation and service chaining.
00:26:47.730 --> 00:26:57.300
Ken Willard: And I think from a security standpoint today micro segmentation is one of the most critical things that should be implemented in every data center.
00:26:57.810 --> 00:27:15.060
Ken Willard: You'll hear it referred to as micro segmentation. You'll hear referred to as a zero trust data center model. It is the idea that just because something exists behind our perimeter firewall doesn't mean that it should be talking to everything in the data center.
00:27:16.380 --> 00:27:26.790
Ken Willard: There's no reason for my public web facing servers to have full unrestricted access to my financial accounting package running in the same data center.
00:27:27.690 --> 00:27:37.020
Ken Willard: Where there might be some very specific API calls that it's allowed to make for account look ups and billing charges and those kinds of things.
00:27:37.380 --> 00:27:42.300
Ken Willard: But it shouldn't have full unrestricted access and with micro segmentation. We can do that.
00:27:43.140 --> 00:28:02.250
Ken Willard: The other big thing is service chaining leveraging our vendor partner relationship. So if you're using Palo Alto, or four to net for some of your data center networking security we can leverage those products and tie them in using the service chain model under network function virtualization.
00:28:05.880 --> 00:28:11.820
Ken Willard: The other great thing about this sort of management perspective is this idea of full lifecycle management.
00:28:12.930 --> 00:28:24.420
Ken Willard: Talked about several these right scaling as we need very easy to deploy great management infrastructure, about to get into the live demo here in just a minute.
00:28:24.840 --> 00:28:36.840
Ken Willard: So we'll get to see some of those. But folks, I think the biggest thing and then I do. I always poke fun. Every time I see a one click upgrade because nothing. You don't execute a process in one click, but
00:28:37.500 --> 00:28:57.510
Ken Willard: Their resources are very good for management and we've got a single management infrastructure to do everything from upgrading the firmware on hardware components through our hypervisor up into that acropolis operating system itself.
00:28:58.560 --> 00:29:16.770
Ken Willard: And if you're running any of the other resources that new tannic needs things are that you want to deploy Entertainment's things like new tactics files objects carbon, right, I have one lifecycle manager that can see and administer all of those upgrade tracks.
00:29:24.570 --> 00:29:28.410
Ken Willard: So very quickly want to touch on some of the other things, actually, I was just mentioning
00:29:30.390 --> 00:29:46.350
Ken Willard: This conversation around hyper converged is really about the core new technics cluster architecture acropolis LS for operations and prison for management. But folks, there's an awful lot more to the new tannic family.
00:29:47.370 --> 00:30:02.670
Ken Willard: We have new tactics volumes. If you have a use case for I scuzzy communication you have external systems that could leverage I scuzzy endpoints. And so you could have an extra bare metal system.
00:30:03.660 --> 00:30:21.840
Ken Willard: To run and connect two data sets on your distributed storage fabric new tannic volumes will do that if you were looking to have a redundant easy to manage file server infrastructure that deploys on top of that distributed file system from new tonics files.
00:30:23.250 --> 00:30:24.030
Ken Willard: Buckets
00:30:25.080 --> 00:30:36.210
Ken Willard: Buckets give us an Amazon S3 API compliant object store. And what do you do with an object store folks anytime, you've got
00:30:36.870 --> 00:30:50.280
Ken Willard: Digital think of objects doors for large data sets that need to be archived for a long time. It's a very efficient methodology for storing those things so security video is a big topic, they're
00:30:50.850 --> 00:31:01.230
Ken Willard: Large graphics and video rendering operations. If you've got a marketing team that produces those kinds of images great use case for buckets.
00:31:02.430 --> 00:31:18.090
Ken Willard: We can also with buckets impose lifecycle management. So if you have to retain documents images, video files for a certain number of years for audit compliance buckets gets you to that type of type of capability.
00:31:19.830 --> 00:31:28.350
Ken Willard: Common flow. I want to talk about sort of side by side here, calm is the new tactics application lifecycle manager.
00:31:29.010 --> 00:31:39.750
Ken Willard: It lets us configure and when we say application. This is we don't mean a VM, we're thinking about those rich multi party applications where you've got
00:31:40.110 --> 00:31:48.480
Ken Willard: A database server probably talking to some kind of an application server, maybe a couple of application servers that are front end and via load balancer.
00:31:50.040 --> 00:31:58.350
Ken Willard: Building those deployments setting up the communication rules, making sure they are patched and secured properly. Lot of work.
00:31:59.070 --> 00:32:08.280
Ken Willard: We can manage all of that through a single workflow and call and make sure that we have consistent deployment of those types of applications.
00:32:08.850 --> 00:32:20.610
Ken Willard: And the reason I said we'll talk about common flow together flow is the new tonics micro segmentation. Actually, it's their new technics network virtualization management.
00:32:21.270 --> 00:32:33.060
Ken Willard: Which gives us micro segmentation and it lets us set up those security rules of these systems should be talking to each other, the system should not talk to the rest of the world.
00:32:33.510 --> 00:32:42.390
Ken Willard: Right, this is my HR resources and I want them isolated from everything else in production, I can do that from a networking perspective with flow.
00:32:43.650 --> 00:32:49.410
Ken Willard: And then the last one carbon up here. For those of you that you have development teams.
00:32:50.280 --> 00:32:59.910
Ken Willard: You're probably having conversations. Things are moving from what we would think about traditional monolithic applications using a waterfall development methodology.
00:33:00.720 --> 00:33:14.880
Ken Willard: Folks, we know that's all moving to a microservices approach for most software development today fast turnaround fast changes independent isolated code pieces that just make calls to each other.
00:33:15.990 --> 00:33:26.910
Ken Willard: Carbon is the new techniques distribution of a cooper daddy's container management environment completely Cabernets Cooper daddy's certified
00:33:28.560 --> 00:33:34.350
Ken Willard: So just a few things that make up sort of that overall product family from new tonics
00:33:39.030 --> 00:33:41.490
Ken Willard: Alright. We promised you want to get jumped over here.
00:33:42.990 --> 00:33:50.490
Ken Willard: Do a little bit of a live demo with everybody just show you some of the features and functionalities here.
00:33:53.040 --> 00:33:58.950
Ken Willard: Since I've got some multiple tabs open, let me kind of walk you through what we've got set up for the demo today.
00:34:00.600 --> 00:34:04.800
Ken Willard: I have a prison central deployment.
00:34:05.940 --> 00:34:14.820
Ken Willard: Can prism central is that centralized single pane of glass intended to manage multiple clusters.
00:34:18.960 --> 00:34:30.420
Ken Willard: And then that is currently managing and talking to a couple of individual clusters or prison element deployments. I've got a lab cluster A in a lab Cluster B.
00:34:31.650 --> 00:34:32.940
Ken Willard: And so in this example.
00:34:34.110 --> 00:34:41.250
Ken Willard: Lab cluster A is our production work cluster this kind of how we've got this setup for the demo.
00:34:43.590 --> 00:34:53.400
Ken Willard: And we'll let that load. You can see I've got some VM is deployed out here, frankly, three of those are just our controller VM that are showing up in inventory
00:34:54.810 --> 00:34:59.970
Ken Willard: But I've got some other example vs out here already up and running, doing some work for us.
00:35:03.090 --> 00:35:14.220
Ken Willard: And then I've got lab Cluster B, and he may not necessarily have this exact kind of architecture in your environment. But for us, for this demo lap Cluster B is our management cluster.
00:35:15.090 --> 00:35:29.100
Ken Willard: I smaller resourcing just basically at this point it's running our prison central VM for us and it's acting as our backup target for our Dr example, and we do the demo here.
00:35:29.850 --> 00:35:38.160
Ken Willard: But other than that, you may not have that architecture, you may not have a dedicated management cluster, we just happened to set that up for the purpose of the demo.
00:35:39.840 --> 00:35:42.180
Ken Willard: You'll notice that on the prison element.
00:35:43.230 --> 00:35:48.150
Ken Willard: Main dashboard of each of the independent clusters, they
00:35:49.200 --> 00:36:03.900
Ken Willard: Acknowledge that they are connected directly to the prism central management platform. If I go to the main dashboard here we get that same prism central communication verification
00:36:07.410 --> 00:36:21.300
Ken Willard: The first things I want to do is start to generate some workload for us in one of our VM, so that we can take a look at what happens in some of the charting and those types of things. So I'm going to in prison central
00:36:22.440 --> 00:36:27.600
Ken Willard: Pull down and you'll hear a couple of references to that. Let me close that out for a second.
00:36:29.010 --> 00:36:36.810
Ken Willard: You see, see the, the three parallel lines there, the sort of official name for that is the entities menu.
00:36:38.310 --> 00:36:42.750
Ken Willard: The unofficial team, but far more in common is called the hamburger maybe
00:36:44.280 --> 00:36:50.880
Ken Willard: I've also heard tell that there are other vendors that have similar looking menus that call them the pancake stack menu.
00:36:51.330 --> 00:37:00.840
Ken Willard: However you want to think about it or if you want to call it entities are you want it to be food related. Absolutely. I'm going to go under virtual infrastructure pick my VM.
00:37:03.000 --> 00:37:14.730
Ken Willard: And at this point, since I've got two clusters that are associated with my prison central management environment. I'm going to see all of the VM from both clusters.
00:37:15.450 --> 00:37:23.100
Ken Willard: So I want to clean this up. This is a little busy for me. So one of the things I want to do is just go up here to the grouping options and let's just group these by cluster.
00:37:23.490 --> 00:37:30.450
Ken Willard: So I can get a sense of what's running where it that makes a little more sense to me. That's a little easier to get my brain around
00:37:31.380 --> 00:37:48.960
Ken Willard: Now, the other thing that we want to make sure that we're doing. Let's go ahead down here to this finance database and let's get that powered up, obviously we want to power up the database. Before I start to power up the finance app here in a minute.
00:37:51.030 --> 00:37:59.760
Ken Willard: The other thing I want to work on is this CentOS seven VM. I've got a little batch job over there. I wanted to run to start generating some disk access for us.
00:38:00.120 --> 00:38:10.950
Ken Willard: So a couple ways I could do this, and I can simply selected and then under actions I could launch the console for that. But in this case, I'm actually going to click through on its name.
00:38:12.990 --> 00:38:23.010
Ken Willard: Just get a little more look at what kind of metrics, I get back in the prism central view. And you can see sort of how it's running from an operational standpoint.
00:38:24.870 --> 00:38:33.840
Ken Willard: This happens to be on a network where I'm not doing IP address assignment. So when it tried to do HTTP request that didn't get one Friday and give it an IP address.
00:38:34.530 --> 00:38:42.780
Ken Willard: I can see it's not doing a whole lot of work over here running absolutely no disk utilization at the moment we're about to fix that.
00:38:43.800 --> 00:38:46.020
Ken Willard: So I'm going to launch the console for this VM.
00:38:50.550 --> 00:38:51.840
Ken Willard: Get logged in here.
00:38:54.840 --> 00:38:57.900
Ken Willard: It's going to work better if I type the password correctly.
00:39:02.940 --> 00:39:09.360
Ken Willard: And so, all I've done is I've just started a little script that's going to sit here in the background for us and write some
00:39:09.870 --> 00:39:26.130
Ken Willard: Miscellaneous data to the desk. I just really want to do some work so that we can see the I O performance and the I O mapping right somewhat close that let that go ahead and sit and run in the background. Start to spin up some resources.
00:39:27.150 --> 00:39:29.430
Ken Willard: Go back to my VM view.
00:39:30.960 --> 00:39:41.610
Ken Willard: I don't want to trust that my finance database is online and running. And so now I'm going to go ahead and power up that finance app VM as well.
00:39:46.560 --> 00:39:53.700
Ken Willard: And since the finance audit VM really kind of stands on its own. We're going to power that one on
00:39:58.020 --> 00:40:02.220
Ken Willard: So that we've got it running when we get down to the next part of the demo.
00:40:05.880 --> 00:40:13.380
Ken Willard: So for that next part. What I want to look at is one of the data integrity data protection tools.
00:40:14.820 --> 00:40:16.830
Ken Willard: So under data protection.
00:40:19.680 --> 00:40:36.870
Ken Willard: I've already set up today. We've got a finance apps Data Protection Group logical structure. Let's be pulled interrelated VM together. And in this case, we're doing two things with them. We're taking what's called local snapshots.
00:40:38.520 --> 00:40:49.170
Ken Willard: That means that I have near line storage traditional storage layer snapshots. For those of you coming at this from a VMware perspective, be very clear.
00:40:49.770 --> 00:41:03.780
Ken Willard: New technics native snapshots have absolutely nothing to do with these fear based snapshots. They are two different management functions, but we take snapshots in new tactics that is a storage tier snapshot of it.
00:41:05.790 --> 00:41:20.730
Ken Willard: Right. So if I take a look. If I click on my finance apps and I go in and say, I want to update it. I can see how I've got this configured right now. It houses. My finance app database and application server.
00:41:23.070 --> 00:41:27.240
Ken Willard: And that's taking a snapshot every hour.
00:41:28.650 --> 00:41:38.970
Ken Willard: Locally I'm keeping the last six right very near line so that if something happened that I need to recover that it's nearly instantaneous
00:41:40.200 --> 00:41:46.080
Ken Willard: But the other thing I want to do is, what happens if something catastrophic happens at my primary data center.
00:41:47.190 --> 00:42:07.290
Ken Willard: I lose power. Somebody cuts through the fiber link with a backhoe those kinds of things. I'm also replicating to the remote site lab Cluster B and I keep in the last 48 hours worth just to make sure that if something goes wrong. I've got a little layer of protection.
00:42:08.580 --> 00:42:11.910
Ken Willard: I can either then fail that over at the remote site.
00:42:13.020 --> 00:42:24.300
Ken Willard: Or if I needed to. I could just recover. One of those instances from the remote site and maybe do some manual data recovery and a couple of ways that that could happen.
00:42:25.680 --> 00:42:28.770
Ken Willard: If I looked at the remote site and they go under data protection.
00:42:31.740 --> 00:42:40.770
Ken Willard: Go to the table view, in this case, I can see I've got that same finance apps Data Protection Group.
00:42:41.850 --> 00:42:43.020
Ken Willard: And if I scroll down
00:42:44.550 --> 00:42:47.280
Ken Willard: I see the mode for this is inactive.
00:42:48.300 --> 00:42:59.460
Ken Willard: Right. Well, what does that mean that means that the VM is are inactive on the fail over site there in the condition to have inbound replication jobs update their disk state.
00:43:01.710 --> 00:43:10.020
Ken Willard: And if I keep scrolling down here, right, I can see that I've had the last incoming replication happened just a little bit ago
00:43:12.270 --> 00:43:18.690
Ken Willard: And if I go look at the local snapshots. Right. What do I have on my remote site.
00:43:20.490 --> 00:43:28.230
Ken Willard: Well we fired off three different intervals. This morning right at that one hour interval window.
00:43:33.930 --> 00:43:53.040
Ken Willard: So the other thing I want to demo we powered up but we added the audit VM to my finance group of resources, but that audit VM, the application for that was purchased and brought in after we already had our data protection setup.
00:43:54.180 --> 00:44:03.180
Ken Willard: Easy enough. Ready to go back on lab cluster A. My primary site. I'm going to update my protection domain.
00:44:04.230 --> 00:44:10.410
Ken Willard: And it now shows me a list of all the VM on the primary site that are not already protected.
00:44:12.120 --> 00:44:14.940
Ken Willard: And so now I can simply pick that audit VM.
00:44:16.830 --> 00:44:20.250
Ken Willard: Scroll down here to the bottom and move that over
00:44:21.420 --> 00:44:23.550
Ken Willard: To the protected entities inventory
00:44:25.500 --> 00:44:34.950
Ken Willard: And so now the next time this job runs it will not only backup the finance database and application server, but my audit server as well.
00:44:37.680 --> 00:44:40.410
Ken Willard: Right. Really nice clean management there.
00:44:41.700 --> 00:44:50.370
Ken Willard: Folks, we've been looking at this. The other thing that you know is new tonics has a fantastic channel partner relationship around Dr. Specifically, so
00:44:51.090 --> 00:45:11.400
Ken Willard: VM haiku rubric, or if you're already using one of those other third party products to do your backups and your disaster planning and fail over activities, all of those integrate natively into new tactics. If you don't already have one of those. You have this tool set ready to go.
00:45:13.710 --> 00:45:23.580
Ken Willard: The one thing I want to demo because we're sort of pushing up on the title of it here, but I want to talk about one of the things I think is a really powerful feature when you're using the Acropolis hypervisor.
00:45:25.320 --> 00:45:39.210
Ken Willard: We often have a scenario where we might need to share discs between virtual machines or between, say, a virtual machine at an outside bare metal, metal system.
00:45:39.900 --> 00:45:51.480
Ken Willard: Think about this. Anytime there's an cluster environment going on right database cluster some application that you're running that is natively clustered or can do native clustering at the application tier
00:45:52.440 --> 00:46:00.660
Ken Willard: And in that case, I probably need some kind of a shared corn disk probably need to share David is maybe a shared logs drive
00:46:01.980 --> 00:46:12.210
Ken Willard: And I want to be able to present that maybe to VM on the cluster or maybe to have VM on the cluster and a bare metal system outside
00:46:13.770 --> 00:46:20.580
Ken Willard: The way we can do that very clearly through new tactics is to use the volume group architecture.
00:46:21.780 --> 00:46:26.160
Ken Willard: This is native to every entertainers cluster, regardless of your license level.
00:46:27.330 --> 00:46:34.350
Ken Willard: Right. So I add a new volume group, and I'm going to call this my finance.
00:46:37.530 --> 00:46:39.210
Ken Willard: Here discs.
00:46:43.350 --> 00:47:03.630
Ken Willard: Then I go in and add a new disc. I can pick which container. This is going to live on really important tool there because your containers are where you define your data services. So as a container running compression is it running duplication, those types of things.
00:47:05.340 --> 00:47:22.770
Ken Willard: Think about a modern database application all the modern databases run their own compression algorithms. So I would certainly not want to build a disk for a database engine on a compressed volume and now paying that compression tax twice.
00:47:23.790 --> 00:47:33.420
Ken Willard: But my love volume for that database what our logs flat text those compress really really well.
00:47:34.200 --> 00:47:48.630
Ken Willard: Right. So even within a single volume group. If I had multiple containers with different policies, I could build my different discs on different containers and thereby deliver the right storage policies.
00:47:52.050 --> 00:48:00.600
Ken Willard: Right, so I just added a single disc of 20 game. Let's add another one. Let's say this is going to be the database volume will make it 50 gig.
00:48:01.740 --> 00:48:03.900
Ken Willard: Again, I'm going to put that on the default container.
00:48:05.730 --> 00:48:10.440
Ken Willard: And then let's just say I need a little tiny corn disk out here.
00:48:11.820 --> 00:48:15.390
Ken Willard: So we'll just make a little one. That's five gig for my corn disk.
00:48:17.130 --> 00:48:22.440
Ken Willard: So I don't have a single volume group managing three logical disk entities.
00:48:24.600 --> 00:48:25.830
Ken Willard: And I can save that.
00:48:29.580 --> 00:48:33.510
Ken Willard: And then I can shift over to my virtual machines view.
00:48:35.550 --> 00:48:44.520
Ken Willard: And with the new tonics hypervisor. This is a new tannic hypervisor specific feature, but I can go into my finance app virtual machine now.
00:48:47.640 --> 00:48:48.810
Ken Willard: Update that VM.
00:48:50.820 --> 00:48:52.050
Ken Willard: I can scroll down
00:48:54.480 --> 00:48:57.870
Ken Willard: Well, that has not been very cooperative. Come on now.
00:48:59.880 --> 00:49:05.640
Ken Willard: There we go and add the volume group. I just created financial discs.
00:49:09.750 --> 00:49:22.230
Ken Willard: And so now, without configuring I scuzzy in the virtual machine. I have just delivered it access to those three share discs in the volume group.
00:49:24.060 --> 00:49:44.280
Ken Willard: And then if the other half the other half of that cluster companion pair was a bare metal server. I could enable the I scuzzy support services and share those same three discs to an external system via I scuzzy and through the new techniques acropolis hypervisor natively to that VM.
00:49:45.510 --> 00:49:47.250
Ken Willard: On the same service.
00:49:49.380 --> 00:50:00.450
Ken Willard: Since I don't have an external bare metal system to demo. I'll show that with just going into the finance VM. Another VM on the same host. I'm going to update that VM.
00:50:02.580 --> 00:50:05.460
Ken Willard: Good out of my volume groups again say out of volume group.
00:50:06.630 --> 00:50:07.650
Ken Willard: Pick the same one.
00:50:17.040 --> 00:50:22.410
Ken Willard: And just that easily. I've now mapped, those three shared disks to two volumes in my environment.
00:50:23.910 --> 00:50:32.040
Ken Willard: Very simple, very powerful folks. The other thing to think about, though with that and I can't stress this enough. We hear this pretty hard in the class that is
00:50:32.910 --> 00:50:55.860
Ken Willard: An open disk share right we're not doing any on disk locking know Eric checking if you do this architecture, it means that something at the application tier has cluster services built in, and it has to understand how to properly share those discs across the two cluster members.
00:51:00.870 --> 00:51:08.220
Ken Willard: Alright so that runs us up to just a few minutes before the top of the hour.
00:51:10.500 --> 00:51:26.940
Ken Willard: Fonts comments things that you want to get into the discussion here. I know we had a quick question about the recorded options which we've already gotten answered anything from the new tennis family questions about acropolis operations, anything like that.
00:51:31.830 --> 00:51:40.560
Michelle Coppens :: Webinar Producer: While we wait for some questions to come in, I would like to use this time to talk about that promo that 80s, early on.
00:51:41.610 --> 00:51:52.350
Michelle Coppens :: Webinar Producer: But before I do that, thank you so much. Ken very informative session another reminder that we are sending a copy of the recording out to everyone. There'll be sent out by email.
00:51:52.770 --> 00:52:02.340
Michelle Coppens :: Webinar Producer: All right, let's talk about promos, I am so excited to share that we are offering a 10% discount on our new technics Enterprise Cloud administration class.
00:52:02.670 --> 00:52:08.220
Michelle Coppens :: Webinar Producer: As well as the new tactics advanced administration and performance management class.
00:52:08.700 --> 00:52:19.440
Michelle Coppens :: Webinar Producer: So this promo will run from now through December 31 there is a unique promo code which can is sharing on a screen and I will also post in the chat for everyone.
00:52:19.920 --> 00:52:39.630
Michelle Coppens :: Webinar Producer: I would also like to invite you over to our website. Exit certified.com to see the current schedule of those new tannic classes, some more details about the promo and just to learn more about us. So let me post the promo details in the chat window for everyone.
00:52:43.890 --> 00:52:46.680
Ken Willard: Show. What you're posting those let me do a little bit of
00:52:48.210 --> 00:52:50.700
Ken Willard: Expectation certainly I think maybe around the two courses.
00:52:51.810 --> 00:52:54.810
Ken Willard: Folks, if you've been in the it
00:52:54.810 --> 00:52:56.130
Ken Willard: industry for a while.
00:52:56.880 --> 00:53:10.860
Ken Willard: But you have not necessarily been working with new tonics, I would maybe caution you against jumping right into the advanced management and performance class, we've had that happen with some folks the past
00:53:11.400 --> 00:53:22.110
Ken Willard: I get it. You're seasoned you've been in the data center for a while, you know, want to start with an intro course. But what happens is with that advanced administration class.
00:53:23.190 --> 00:53:39.270
Ken Willard: The curriculum is written, and it says very clearly in the course description you come into this with either the ECA course already under your belt or about six months of experience with new tonics folks that class is a very interesting and very good structure.
00:53:40.740 --> 00:53:51.990
Ken Willard: It's four days eight modules for each module, we have an hour of discussion and topic presentation and three hours of lab.
00:53:53.190 --> 00:54:07.740
Ken Willard: And then we take a lunch break and we come back and we do an hour of the next topic and put you back into three hours of lab, it is extremely hands on and is extremely intense and if you don't have a little bit of background with the new tactics platform overall
00:54:08.940 --> 00:54:12.270
Ken Willard: You're going to have a kind of rough four days personal opinion.
00:54:13.800 --> 00:54:15.750
Ken Willard: I teach that one a lot.
00:54:20.880 --> 00:54:34.980
Michelle Coppens :: Webinar Producer: So we don't have a question, but I think this is a nice kudos to you can Michael found this session, very informative great overview of newt annex and so that will be watching the recording more than once. So I think that's, that's fantastic.
00:54:35.700 --> 00:54:36.150
Ken Willard: Thank you.
00:54:46.440 --> 00:54:56.730
Michelle Coppens :: Webinar Producer: Our session may have been just so thorough that there are no follow up questions I but we do have some time. So we'll continue to stay here i. So, do you feel free to post any questions.
00:54:57.060 --> 00:55:04.740
Michelle Coppens :: Webinar Producer: In the meantime, I am just going to stop the recording now. So once again, thank you so much again for your time and for everyone for joining us today.