Good afternoon, everyone. Thank you for joining us today for our webinar titled What you need to know about V sphere seven
Our speaker today is Ken Willard senior instructor at exit certified Ken specializes in system virtualization and consolidation for both servers and desktops.
Helping technology teams approach virtualization while considering the technical organizational and political impact.
And has worked with IT organizations from the commercial government and nonprofit verticals addressing virtualization in each of these unique environments.
In addition to delivering training to both the business partner and end user communities can also works with the tech data channel community to assist with presale consulting
All right. Before we get started with the the webinar. I want to talk about the functionalities.
So during the webinar. Everyone's microphones will be muted. So if you have a question, please enter them in the Q AMP a box at the bottom of your screen will have a dedicated question and answer session after the lecture.
Today's webinar is being recorded and will send a copy to each and every one of you. By the end of the week. I'm also going to share a promo at the end of the webinar, so stick around to learn a little bit more about that.
Alright, you can you can take it away from here.
Thank you very much. Good morning everyone, or good afternoon, I guess, at this point, we've actually tipped over the middle of the day here so appreciate everybody joining us
Had a lot of press starting actually way back at VMware last year talking about these her seven
The patent gelsinger stood on stage and talk a lot about things that maybe we hadn't heard about before.
There's an awful lot of talk. I think even more so than we had heard out of VMware previously around containers around Cooper daddy's specifically and those types of topics.
And we knew that we had, you know, the, the tanzer grid was announced. And that was a sort of a part of the overall structure of what VMware was taken to market as of August of last year.
And then, of course, about three weeks ago now, we saw the announcement of the sphere seven with a lot more native integration of Cooper daddy's container support lot of things around that area. So let's look at what we really began to see here with these first seven
Some, some structural change when we think about some of those core functionalities. We've now got some really specific support for things like
Artificial intelligence and machine learning, if there's some behaviors, now that are part of the sphere that are starting to leverage machine learning algorithms.
get even more so when we had before you think about, I would almost say things like V realized operations and the predictive DRS features and those kinds of things. We're certainly starting to leverage some of that machine learning or receiving and even more of it.
We've had some security changes we've had some things developed around
Supporting DevOps and making the V sphere platform, much more conducive to those of you have your own internal code development teams and making sure that those run well
But let's start with lifecycle management.
Some big changes here, or at least the beginning of a very different roadmap.
For most of us have been working with the product for a while and we are well accustomed to Update Manager and the idea of managing our virtualized environment with the concept of baselines building out patch infrastructure that way.
That all gets rolled over to lifecycle manager in this version. And one of the big things that lifecycle manager does for us. If you've seen in the video had a chance to read a the blog is this idea of
We have the option. It's not required. We have the option to go from this idea of baselines and baseline groups for patch management to an image based architecture.
One of the big things that could happen in environments is
Different administrators administrating at different times of day and different release cycles and those kinds of things. And you could conceivably wind up with one or two systems that wound up getting omitted from a particular patch when it was deployed.
The patch didn't apply to a particular host. For some reason, and the troubleshooting never got done those types of things. And what that meant was then within a single cluster, we had the risk of two things.
One clusters, not being consistently patched. So that creates a potential security problem.
And if clusters are consistently patched and don't reflect that I didn't cover image that can create a troubleshooting problem. So with an image based approach. That means that every host effectively gets rebuilt or reinstalled with every patch deployment.
If you need to, you have had larger environments and you worked with the auto deploy server. Some of this architecture probably starts to sound familiar, this idea of patching based on a single unified image that we will push on to the host said effectively rebuilding it
There's some other things. You got to think about it. That means the cluster has to be made up of absolutely only hardware from a single vendor.
Only hardware of a single chassis and ideally not required but ideally hardware of the same generation, right. So if you have a vendor that revs generations of a single model.
That is something you're going to want to look at
We also have the center server profiles, which is really great for those of you that have multiple environments or wind up
provisioning and tearing down and provisioning for part of your test dev or QA cycles, you now have the ability to build the center server just like you can push coach profiles on the ASX hosts. And then lastly update planner in this area.
Update planner legend build the roadmap for the center V sphere environment upgrades. So a nice graphic solution there.
That look the intrinsic security.
Well, you've got some details here that I'm not going to spend a whole bunch of time on. But the big one here I think is identity Federation.
So we're going to talk about that a little later. But this gives us the ability to have two factor authentication into our V sphere environment, which has been a little challenging to implement before
And then we got a lot of change coming off the core virtualization model changes in resource manager. I'll be showing you some changes with Drs. A little later on in the demo.
Updates in storage, right, we now have access to some new components in the storage for storage system to leverage new technologies share VM decay support over
WS FC and the big one. I think in my mind is in the envy me access over our DMA network connections. So if those of you that have large data sets, you're leveraging and Vimeo already and you have those are DMA supporting ether net cards. Lots of performance available there.
Improvements in Drs. I'm going to talk about in demo. Those we've got improvements in the motion. And we'll talk about that.
Obviously we've continued to see revisions with new hardware support so obviously support for the new CPUs both out of AMD and Intel with those massive core accounts.
As well as virtual machine hardware version seven, which gives us, among other things, the support for up to 256 virtual CPUs and six terabytes of RAM in our virtual machines.
So continual big scaling there.
And we've got some enhancements in again that machine learning behavior with fusion.
Specific emphasis on those developer servers, we're gonna talk about some of that particular on the Cooper daddy's conversation.
And then, of course, V sphere with Cooper natives itself. So one of the things to think about the change in distribution model.
Right. There's v sphere. And there's now the V sphere with Cooper daddy's for those of you that are going to leverage the native V sphere with Cooper daddy's behaviors.
You'll have to think about your licensing approach because you see these fit with Cooper Nettie is tied directly to the cloud foundation box up here can be sphere with communities is only available through the cloud foundation software architecture.
For those of you thinking about your upgrade roadmap. Want to make sure that the kind of know where you are when you're thinking about going into version seven
You can do direct upgrades. As long as you are on the sphere, six, five, and later.
Hopefully that's not an issue, right. We all know that these are five five rolled out of support quite a while ago. These are six.oh just rolled out of support, about six weeks ago.
And I say, hopefully, because I understand. I know many of you, there were
Hardware refresh cycles to consider. There were other budget implications of these upgrades. Right. It wasn't just as easy as saying, oh,
I've got support and service. So I'm just going to keep upgrading every time, and it doesn't work like that. Unfortunately, most of our environments. So just be aware if you aren't at least six dot five
You will have a two stage migration path right you'll have to get that far in whatever your upgrade cycle is and then come on up to seven Dotto whenever you're ready.
So all this talk about Cooper daddy's and containers right, what is the what is the reason for this, and I would say, frankly, for those of you that
Don't have teams that write your own code you're not doing a lot of internal code development yourselves may not be as much of an issue in the near term.
For those of you that have on staff code development teams, you know, this is a big deal.
The idea that we don't have these big monolithic applications anymore. We've got, what do the development teams call micro services.
And applications broken up to do very specific point functions that way if they need to upgrade a behavior replace a behavior, those kinds of things. It's one small code change instead of this massive code revision.
Right. So we're seeing a growth in both the number of containers being deployed and the number of organizations deploying those containers.
We are on a runway that by next year IDC says we'll see one and a half billion containers deploy deployed as the software model of choice.
And again, this primarily impacts. Those of you that have your own code development operations happening today.
But what all of the rest of us are going to see as a trickle down effect, those of us that are accustomed to running off the shelf applications from other vendors
Folks, this is in visually going to land in our data centers as well. I think we're going to see big off the shelf software vendors also move to this microservices architecture, even when we're talking about on premises deployed licensed applications.
So for all of us. I think this model is coming in, clearly, so does VMware given this release.
Right. So what's really prompting this I sort of tease this about a slide ago we think about it today and we're using, you know, this case an application gaming application Age of Empires
And that once upon a time, ran as this one huge deployed application, you think about one single EMC file executing all of the required pieces.
And that's the way applications were developed. That's the way most of us are accustomed to interacting with them so we
Build a virtual machine we install an operating system. We get it patched up and then we deploy the application and we either launch the application service when the virtual machine boots or there's some script that calls the executable and starts at whatever it is.
Today, that's not what we're seeing. And we are getting this idea of the microservices architecture.
And the big piece of this, what's driving a lot of this is obviously cloud deployments today. You see, specifically the various cloud providers intentionally reference the Peter
But again, I think we're going to see even on premises sort of traditional licensed software move to this model where even if it's deployed in our own data center.
We've licensed that from Microsoft, or Oracle or IBM or whoever the big vendor is I think we'll see this sort of software deployment model coming for everything. We're going to be doing.
And the other big thing of course is starting to impact. This is the idea of Internet of Things, and being able to deploy a smaller components of code to do very specific functions.
Collect data collect metrics from sensors in the device and then hand those up. You see education management referenced as one of the heat microservices up here.
And started aggregate data architecture. So this is going to continue to be what we look at going from that very traditional
A virtual machine runs a nap a virtual machine runs a database to we're going to look at look like a very different behavior inside of, I think, even our own on premises data centers.
Like this is going to be reserved for those folks that are making commitments to one of the cloud architectures are those kinds of things.
And I think we're seeing stages those very cloud centric folks. They're already there. They're working on that model.
The folks that I think are going to need to be on board with this and adopting this are those folks that are already doing hybrid
I've got some of my applications. So my infrastructure deployed on premises. I'm starting to leverage AWS or Google Cloud Platform or Azure as scalable options floating capacity, those kinds of things.
So they're going to need to understand and be able to support this next that their on premises data centers. And then finally I said I think will ultimately see this get there for everyone.
The thing about what we're seeing in this particular release.
For those of you that have had the opportunity to particularly live at Cooper Nettie is, in general, you understand that one of the powerful things about Cooper Nettie is the fact that
Developers can have an environment on their own. What the laptop right could do their testing. See if it behaves properly all of those kinds of things. And the interesting thing about a container.
Is that is self contained, it will have the executable code.
A very lightweight OS maybe developers are using
Many developers are using Ubuntu, there's a specific distribution of Ubuntu. That's very lightweight
There is a there's a specific distribution on VMware called photon.
Right, and so we're trying to get this balance of how do we support this idea of a container based deployment. Because then when the developers done with that code.
And they want to promote it to production. The fact that it's entirely self contained when you're promoted it runs the same. We don't have these very abilities of
Oh, it was the developer had a specific version of.net and in production. We're running a slightly older version and it doesn't support a function call, or it doesn't support a behavior.
We don't have that problem because everything containers is entirely self contained. So how do we balance this flexible adaptive development environment with
Infrastructure and being able to do things like something as simple as I got a buddy of mine that his biggest pain. He is on the networking team for a large
Insurance Company and when you see containers spin up and developers spin up a few hundred containers over a couple of hours, and they do what they need them to do. And they spend them down. Now that's what
I just spun up and consume a couple of hundred IP addresses out of ID HTTP server which haven't default 24 hour lease. I don't need that at the end of the container life cycle.
Right, so we've got to find a way to give the developers, the flexibility and the virtual infrastructure admins, a way to maintain a little sanity.
Uber's to be serious is going to do that for us right we have two very specific versions these very with Cooper daddy's and you see on this slide available through VMware cloud foundation. That is how you license. This particular model and then the more traditional the sphere seven
We're going to talk these services component is first and then these are seven and then of course we've got a bit of a live demo for you here.
So why Cooper daddy's talk about that really gives us the container structure Cooper daddy's is a project that started at Google. And then, was released as an open source project.
And it's really sort of taken hold as the orchestration model for containers right there are some alternatives out there. But when you look at the one that's got the biggest foothold today.
Cooper daddy's is certainly leveraging that right. So being able to do real time infrastructure management through Cooper 90s native API's.
development teams don't have to learn something different. They don't have to start studying the same API system to be able to do what they can already do on other platforms.
We are fully compliant with the Cooper 90s architecture. If you're using the Tansey Cooper daddy's grid that comes with the V sphere with Cooper daddy's architecture.
And of course you've got that performance and scalability, that we are accustomed to with the sphere already
Now we just got that native integrated Cooper daddy's pod service that helps give that structure that the Cooper daddy's environment needs. So we now have the ability to do virtual machines in Cooper daddy's containers in the same platform with a native management layer.
It's really support this idea of our developers working like they always have and our infrastructure team working like they always have with the same consistency of controls.
The teams that you work with are going to continue to work through the center
Your development teams are already accustomed to an environment or an access model called QB control, they are going to continue to work through that and the sphere now talks both languages right consistently consistent experience, whether you're a developer or an infrastructure.
So we think about this, right. How did this start to come together, we have this idea of Cooper daddy's pods.
Those are managed by the Cooper natives cluster, just like they would be in any open source deployment except now we're running right next to them on native V sphere are the sphere workloads of virtual machines.
So think about what the development team is doing.
Their environment through Cooper 90s when they create containers, the self contained the bubbles and then tell the Cooper daddy's cluster, how to run them that's traditionally done with gamble. By the way, if you're thinking about your own career.
What I'm currently investing in is getting better at the animal formatting better than JSON formatting for definition and configuration scripts.
And I'm starting to pick up a little bit of Python Python is pretty utilitarian and used a lot of different places and it's supported for a lot of platforms.
We think about this today, our developers are accustomed to building these GMO files to pass over to the Cooper daddy's cluster to create they're working Cooper daddy's environment.
So what if they're building one of these bigger applications and they want to deploy some databases on top of traditional the EMS
Well, today with the new support for V sphere with Cooper 90s. They can use the same Markup Language except this time instead of specifying the kind as being the Cooper daddy's cluster that they were defining traditionally now they can simply specify that's going to be a virtual machine.
And then we have a consistent definition or class configuration for these fair components, just like the developers are accustomed to on the Cooper daddy's container side.
repurchasing skills. Little different vocabulary, if you will, that they're going to have to pick up but they don't have to relearn how to work with the infrastructure components to have this ability to deploy on the fly.
Right so developers use Cooper daddy's to manage their workloads and then we as the infrastructure administrators still get to work through the center and see all of those resources that we are accustomed to all the same management tools.
So in this case, we've got an application that we're sort of running the example here, right. It's made up of a mix of Cooper daddy's clusters virtual machines and container pods.
And we can see all of that in the traditional V sphere management interface.
Much better for us as the sphere admins and now we've got a unified way to handle this, by the way, we've talked about a couple of times. This is only available if you're running V sphere cloud Foundation and the reason for that is what comes in the cloud foundation bundle.
Well its core V sphere and now these fair with Cooper daddy's the Sanford storage optional right it's in the bundle. You don't have to deploy on base fan. Most folks do
And then lastly in SS for virtual networking. And that's where we start to be able to handle this environment of somewhat wildly scaling and contracting
Container architectures, while delivering all of those virtual services.
Right, so that's why the title linkage between these are with Cooper daddy's and VMware cloud foundation is because foundation is made up of those three core services.
That we now have an entirely software defined virtualized infrastructure underneath compute, storage and networking and the lens of support the Cooper daddy's environment, the container based environment properly.
Now what I suspected the case for most of you, you're going to be looking at traditional these five, seven, at least, probably in the short term.
And so what's happening with Easter seven changes in lifecycle management, not the least of which I think is the the big idea of managing updates via SSH images.
I'm going to talk a little bit about that. We've got some changes in security one of those obviously simplified software patching, I think.
It sort of falls in both places. The idea that we're patching by an image based model instead of a baseline model. What says, make sure that we've got that consistency.
And we're going to talk it through the Federation, as I promised that idea of being able to do two factor authentication today.
And that we saw improvements in the native machine learning that's happening inside of V sphere. We've got improvements in both DRS and V motion for our debt scalability support for our larger virtual machines and better quality of service overall
Let's talk lifecycle management to start
We now have this idea of the desired state target for most of you, maybe, hopefully, you've got fairly consistent fairly similar hardware that make up your clusters.
And so we've got this idea of base si, si, si and then those servers and their motherboards and whatever riser cards came from the original vendor. The it
IBM or HP or Dell right whatever the original configuration was we might have had some additional vids V sphere installation. But those are drivers that were required for that particular vendor model to be able to have all of the hardware components, talk to the SSI.
And then let's say we went out and we put in a specific brocade card.
Now I've got a third party vendor that was beyond the scope of the original makeup of that particular cluster hardware configuration.
Previously I had to get my DSS updates build those into my baseline. I typically a lot of organizations. I saw
Then manage all of the Dell or IBM or HP specific patches together because that way if something went wrong in those
They knew exactly which patch bundle caused the issue and they could go back to the vendor on those. And I had that that third patch, but will manage my independently chosen brocade riser card that fit in that model.
So now I've got three patches to go through and again intermediate multiple cycles, you have the opportunity, something goes wrong. There's some oversight something gets missed
Now we're doing that with the desired end state. So we have patches that we vet and test and then everything from the base sex image to the required vendor.
Patches and updates of drivers and any third party components all get rolled together into a single image and then we push that image out at the cluster layer.
Same traditional rolling ASX upgrade process, but we're now doing it based on a coordinated single image less opportunities for something to get lost left out or overlooked.
And then a couple of other things. We've got the V center update plater
That's the ability to look at any compatibility problems across other things that are tied into the environment.
So you're running Site Recovery Manager. You're also running a specific release of NSF and you want to upgrade V center. Are there any internet compatibility problems, right, then that's what the B center upgrade planner is going to help you do
We can now coordinate the software updates and we've been doing some of this, but we've got some enhanced support around either JSON format and consistent reproducible updates.
So let's say you manage multiple sites and you want to push out consistent configuration updates across those sites, you can now do that with a JSON formatted template or you can do that for REST API calls from a coordinated that software automation system.
And then finally firmware updates or a firmware updates or something that Update Manager did not touch nothing at the hardware level and we now have that incorporated as part of the lifecycle manager piece.
So that's lifecycle management identity federation. And again, the big thing here is this gives us the ability to support two factor multi factor authentication into V center server and all of my V sphere infrastructure.
Today, this is initially done with the Active Directory Federation services other providers other multifactor support will come later.
But VMware looked at that and doing the integration with Active Directory Federation services gave them a lot of broad coverage that the use case for a lot of downstream customers, obviously, in the very short term.
And so for those of you that are in more security rigid organizations, we now have the ability to support to factor into the core these fear management environments.
And then a couple of big changes here. First of all, with Drs.
If you've been working with the product for a while, you know that DRS had been it's been through a couple of sort of iterations from how it looked at things.
Right, and it's an initial days its intent was to reduce resource contention. So we could actually see hosts that had very different workload utilizations
We got a four node cluster in one host is running at 80% memory utilization. Another running 20% couple running at 40% and as long as there were no contention defense on any of those hosts.
The old older versions of DRS left that model alone. Right. So we think way back to the three dot x days of the product.
And then we've seen, we've seen some revisions come in some updates made the product and we went to what we see in the bottom here, which is this very cluster centric approach.
Because what they quickly figured out was when we had workloads that weren't very dissimilar or host that were used in a very dissimilar utilization, then if there was an HOA of it made some challenges with HGA
Right. So we went to this very cluster centric model, trying to get even utilization across all four in this case of if we had a four node cluster. We want to see them sort of start to shake out somewhere in that 55 to 60% utilization all four of them everything very consistent
Now, I've been talking to you. The first few minutes of this about microservices and self packaged containers and these very small independent workloads. Well, guess what.
The current version of DRS that we're seeing with these for seven is workload specific right. It really takes a look at what's happening so far as
The throughput. The performance. The effectiveness of individual workloads and makes an individual score rating for each workload.
Today, it's very VM centric, obviously. But I fully expect that we'll see this become inclusive of containers as we get get moving forward with the container native deployment.
So the idea here is to try to get as many views as possible in that 80 to 100% optimum behavior.
Depending on what blogs, you read, there's actually a really great reference out there. They're calling it as some of the blogs, a virtual machine happiness score.
Trying to gauge how much of its need and workload is getting done in a consistent manager is consistent manner.
And I have a student in class that mentioned that will, we're going to call that the DRS happiness score.
Then hopefully we'll see the DRS affinity and anti affinity rules rebranded as playground rules, which I thought made a whole lot of sense. So we'll see if the marketing team picks up on that.
So that's DRS sort of its progression over the years.
The other big thing. When we think about what's happening with virtual machine support and this ability to continually support bigger and bigger workflows.
With V motion was originally introduced we were running a 32 bit of classes and typically seeing the workloads that probably had
Big ones had 24 to 32 gig of memory, maybe in some of those early days, the massive applications were running with 48 maybe 64 gig of RAM, but those were very few and far between.
So when you think about taking a VM and moving its active memory page from one house to another for a V motion operation to do that with a eight to 32 Meg footprint.
wasn't a big deal. Right. And at the end of that process. Hopefully if any of you've read, you know, it's sort of a two stage operation we look at what the VM has that we call
Allocated but the inactive pages, pages that have gone quiet in the memory space and we move those first we do what's called a memory bitmap pre copy
And we get the memory bitmap pre copying done, then what we're left with is a small subset of pages that have been actively changing since the emotion of it was triggered.
And then what we do is what's called studying the VM right for a moment in time, we pull it from the CPU scheduling.
Thereby freezing those pages in memory, we move the active pages and then release it in the CPU scheduler on the new host and again when you're talking about the scale of typically VM that we're only 32 gigs in size from a memory standpoint, was very easily done.
Then we started seeing VM that it started to get this colossal scale that we often have in the data center.
Things like SAP and large Hadoop environments and those types of things. Big Data Analysis processes.
We now support massive VM from a memory capacity scale. And when you go to V motion those massive VM using the traditional architecture, what was happening was we were seeing
Really negative impact. Right. It took a long time to complete the V motion action you start thinking about VMware of the one terabyte of memory scale and bigger.
And it was a different problem. It was a different way that the technology to be approached
We were seeing problems with that stun time that quiet period where we weren't letting it update pages and memory that started to creep out
And we were seeing problems with the overall performance of the VM during the pre copy cycle.
So with version seven we get some wildly different code under the covers and you see the traffic decrease in the time it takes to do a V motion migration with what they're now.
The marketing teams calling enhance the V motion and folks. All I would caution you is if you've been working with the product for a while. Don't let what the the marketing team is calling it hands the V motion get muddled in your brain with the idea of enhanced the V motion compatibility
two entirely different behaviors of a V motion environment or enhance the emotion or the Nuvi motion in version seven is all about performance and faster execution on these massively large a VM from a ram standpoint.
Alright, so, as promised, we want to jump in and show you around a little bit, do a little bit of a live demo. Michelle, I've been keeping an eye on things other than
What I would call general pleasantries. I don't think we've got any questions or anything in the chat yet. I'm not okay. I want to make sure I wasn't missing anything.
Michelle :: Webinar Producer
Yeah, no questions. Yeah, I'll keep an eye on that though.
Little that I got a host complaining about its memory or CPU utilization
So I've got just a
Few things that I want to point out and demo.
First of all, you'll notice that we are in the V sphere client. This is all HTML5 with version seven
Hopefully you've read all the press leading up to this VMware talked about this for almost the full three years no more flash like the V sphere web client is gone from the product. There isn't even such a thing. If I go File put a new browser tab.
And I opened a late to my V center server.
Sphere ash client the URL for that flash based web client.
I get told no.
It recognizes what you've asked for. But it tells you this be center is not registered with a V sphere web client doesn't exist anymore.
So you'll, you'll see that everything today in version seven. We've now gone completely to that h5 interface.
Anything on V vols.
Nothing particularly new or earth shattering Mike the Vols continues to be supported.
Honestly, when you look a lot of what's going on with with V vols. And frankly, the way VMware has kind of approach that evolves right from the start.
They need that capability available and pushed the API definitions out to the storage vendors and said, hey,
If you want to get on board with the fault the balls. We think this is a really good idea with the customer base is going to be on board with it and you might want to think about going that route.
And they really left a lot of that adoption and a lot of the driving that to the storage vendors. So yes, we've also still here. None of that behaviors changed them that support has changed, but no really massive announcements around V vols. So far as version seven
for better for worse, they've kind of continued to leave that with the storage vendors
Alright so couple things. First of all, the, the user interface. I also want to point out when you first click through to a VM and see its Summary tab.
Right. We've got what should be pretty consistent flavor here if you've been working with any of the web interfaces before it's all feel pretty normal. But you'll notice up here, there's an option to switch to the new view.
This is sort of an upgrade or enhancement to the V sphere clarity user interface the clarity, the UI is what we have had from VMware ever since they started HTML5 development.
And it keeps getting a little refinement here and there to make it easier to read more user friendly. So I'm going to switch to
The new view.
I see see just little subtle changes. But one thing that I now have the is I now have Dragonball panels, I can restructure this view to look like whatever I want to look like.
Right. One of the big things that folks are starting to leverage, especially when they've got multi cloud and hybrid cloud environments is the idea of tags being very important
ties it to a specific cloud deployment, maybe a specific project, right. So maybe I'll drag my tag view up here. The other right so as this gets assigned to a particular work group or a particular project.
Sort of regardless of my resolution I've now promoted tags to the high priority view.
So just kind of nice that we've now got the various widget displays that are part of the makeup and I can drag and drop them under the, the new view. So that's one thing I think is worth mentioning. Really nice improvement to the architecture there.
The other thing I want to certainly be able to show you here is this idea of at the cluster level.
So for this demo. We've already got DRS up and configured and whether that we've got a bit of a DRS problem here.
I've got DRS up and running in a mode that I would never frankly recommend you write in production, it's running in full manual load.
And when you're thinking production please run DRS in fully automated mode, let it do its job I purposely got it in manual mode so that he can't do its job yet. I wanted to show you a host that sort of running in such a manner that it's not delivering good support.
I got three virtual machines turned on and they're all bound to the same host. If I look at IES x five
All my power that VM are registered on that same host. And if you've been through VMware training class, you're probably familiar with a tool called the CPU busy script. Right. Interestingly enough, I haven't even launched the CPU busy script any of these VM. If I pick a VM.
And open its web console.
It's just sitting there. I've not even really got it doing any work yet and DRS has recognized that because all the load of the powered on the EMS reside on one host right now. Probably not ideal.
So I'm gonna go back over here.
Right. We've got just a little bit of CPU, a little bit of memory running based on normal utilization. If I go back to my cluster object.
Good. I've got the DRS widget look host five starting to complain about CPU usage and I really don't have a doing anything.
I can go and take a look at all of my VM.
Right, that the three that are running
And you see we've got some sort of key metrics, when I do my, look at all the M's. I've now got a DRS score column.
Obviously, everything is in not happy condition at the moment, but you can see the metrics that are being pulled active CPU used CPU and CPU ready time and then if I scroll out here. So I've got a little bit of
Slide to do it also looks at granted that swapped and balloon memory.
And so that those are sort of the six key metrics that the new DRS is using to build that overall DRS score or again what you'll hear referred to as the happiness score.
So I'm going to make up a pretty simple adjustment here, I am going to go into the configuration of my cluster under Drs. I'm going to edit the settings.
I've already created this up to aggressive mode. I wanted to respond to the most simple or the, the smallest adjustments, so that we can see something active here in the live demo. And I'm simply going to go from manual to fully automated and hit OK.
I'm going to just this a little bit.
So we see the list says update the same configuration. Right. But it's updating the V San cluster configuration details.
validating that configuration or I just changed the DRS from manual to fully automated mode and immediately, then we see some virtual machines start to get moved around the environment right working on balancing out that utilization, a little bit.
And so once that process gets done. I'm going to click over here to my VM. So I'm in the cluster, looking at the VM.
And if I go to
And let's add the host the VM is running on
And so now I can see if I look at my powered on VM. In this case, not surprisingly, I've got three hosts, although I'm about to say, or three VM is all about the same workload, nothing much in three hosts and so they are now balanced across four, five and six evenly.
And so if I go back and look at that cluster summary.
Not done a recalculate I'm going to clear this out of the way, swing. It's more real estate back in and view my VM again.
Alright, let's see if we can force DRS to step up things I'm going to rerun DRS manually. Now that we've seen all of those migrations happen.
And then once I rerun that manually.
We're starting to get some shift right it's reevaluating now the satisfaction or the capability of delivering resources to those of the ends.
So we're starting to see the cluster score go from zero to 7% and over the next few minutes, as it continues to evaluate those metrics will see the that continued to shift and the DRS score cluster wide.
As well as well as individual the ends will continue to to come up as it re evaluate the performance
So there's a couple of things that I wanted to demo and sort of set the framework we're down to about eight minutes left.
And we had promised to give everybody some time for Q AMP. A and other discussions. So anything else that any of you would like to talk about or see with regard to version seven things you need to be playing for in your upgrade cycles anything at all.
Michelle :: Webinar Producer
I'll just take this moment to echo Ken. If you have any questions, go ahead. Find that Q AMP. A icon at the bottom of your screen and enter any questions you might have. There
While we do wait for some questions to come in. I think now's a good time to talk about the promo so this spring. You can save yourself 20% on select VMware V sphere seven training using the promo code.
V sphere seven. I'm going to post this in the chat for you. No worries. I'm also going to link the various V sphere courses we have that are applicable with that promo code. So you'll find all of that in the chat.
Requested demo the integrated Cooper Nettie is features. Unfortunately, will we have access to in the least currently in what we've been given access to the relationship with with the VMware for education pieces.
Today, it's only the core these fear so we don't actually have a deployment that is on or support. So the cloud foundation. So, regrettably, I don't have the native Cooper daddy's capability in the particular demo that we've got today.
Great question. If you are at the sphere, six, five, and you are current on your support and service.
Yes, you can upgrade to version seven. Now one of the things that's going to be a little interesting
Depends on your license level, you're probably going to need to talk to your V sphere licensing person there is an upgrade path. But one of the things that has changed pretty substantially with this version is there are only two versions to software licenses of the model.
So what we've actually had different
tiers of the software before and your support and service was tied to those tears. Now there's only two tiers and they are standard and enterprise plus
So depending on where you are currently licensed and what you want to see in the new feature, you may be having a conversation about a little bit of an incremental upgrade.
And VMware from all the stuff that I've been able to see so far as sales training. These early days, there is an incremental upgrade program. If you want to move from whatever you were on
To enterprise plus right that's going to, you're either on standard or you're going to be on enterprise plus with version seven. So yes, there is an upgrade path depending on feature sets, you may have an incremental cost to get to seven at the feature set you want
Yes, absolutely. We can demo lifecycle manager, because that is part of the core lab.
So I am at the cluster level.
And if we go to updates.
We're ready to I'm going to close this prompt to start managing with a single image.
So from the those of you that are accustomed to Update Manager.
Right, we can always go through and do the same baseline.
Go in and build baselines attached baselines at the host layer, those kinds of things. But if we go up to the top and say, manage with a single image.
Washing through really very nicely, step by step, we have to be an ASX seminar later right older hosts are not going to understand how to do this.
All of the hosts must be from the same vendor again when you get ready. If you want to go to this model you read all the docs you read some of the really nicely done V sphere seven blog posts from the V sphere team, they will tell you not only
Must be from the same vendor, but shouldn't be of the same model and ideally the same generation within that model.
It's just think about that. There's going to be a lot of this how you acquire hardware to build your clusters is going to have a heavy influence on whether or not image based management is how you want to do your updates.
Right. And then from there. And the other thing is hosts may not be stateless. What does that mean, well, the idea of a stateless host means that you're using the auto deploy server.
It means you don't have least traditionally I don't know of anybody that has the auto deploy model and they have any physical device media in the hosts.
The idea behind auto deploy is you've got a really large environment and you don't want to have spindle or solid state disks in those hosts. You really want the host to be a compute node. And so we are going to live boot as x over the wire.
There is no level image. Well, if I'm actually at the idea of the new update management is to push a consistent image onto those posts.
long winded way to say I can't use this model with
Auto deploy hosts. Right, so they're sort of mutually exclusive. So we're going, let's say, set up a new image.
And it'll go out and pull the way the hosts are configured today.
And while this runs just a little bit. Is there an upgrade matrix for seven. If you have V realized ops and horizon already deployed. Yes, there is always the compatibility matrix. That's what pop open a new window here while that's running in the background VMware
So if we go into the compatibility matrix I say I am interested in the compatibility between
Okay, so this is the systems and servers. So I am interested in
Let's do V realized ops first
Nope, that's not going to do it. It's been a while since I played around in this and they changed the user interface.
Let's go back to systems and servers.
Yes, x seven Dotto
Not turning into be a very good demo and change this UI on me but
Let me just post the base URL for the compatibility matrix.
And that's where you go to and you'll have to obviously play with the basically pivot tables of what you're working with here and that way you can take a look at the compatibility between these few seven
Horizon and V realized operations. I will tell you, I teach the horizon class as well.
And as far as I know there's no incompatibilities between these four seven and horizon seven but I have also not seen the then approved list yet. So I don't think they finished the validation of horizon 710 on the script seven yet.
Oh, we were waiting on lifecycle manager Finch. Okay, so we did fine so lifecycle manager finished up. And so the way this works is
You pick your ASX version that you're currently running so if if found, you had different versions of iOS six seven already deployed maybe somebody in your team and pulled the GA release code like we've got here and then
It to three weeks later, somebody had pulled the the first incremental update and you had again an inconsistent deployment, it would actually find the two different versions and ask you which one you want to use as your new starting point. We don't have a choice. We just have the GA.
And then if we go new vendor add ons.
Right. In this case, there's a couple that have already been pre loaded into the environment, right. So let's just say we're going to do the Dell add on. When you click on that, it tells you what this is right, you're getting the base Dell configuration.
Dell I track components for their power Edge servers and so sort of just standard base Dell components to SSI.
So we could add those in. And then if we've got firmware. So we've got a controller Carter riser card of some variety and I know I've got a specific firmware update
Right again, in this case, we don't have any that were auto discovered none that are pre loaded. You also can upload those. So the vendor publishes one you can bring it into the site.
And then when you hit Save.
It'll spin for a minute, and then it will automatically start the validation to make sure that
An image based on the given ASX code level that I've specified and including that Dell EMC add on will be able to be successfully applied to all of the hosts in this cluster, right, this, this turns your cluster into the top level consistency manager basically
Other questions that I missed. While this is doing its compatibility check
The other thing that I want to mention is if you've not already seen it. And if you are trying to get your brain around Cooper Nettie and you know nothing about it.
This is a site from VMware so they're Cooper daddy's Academy
If we go take a look at the courses.
It is everything from a very introductory level basic
All the way down through if you want to. I'm
Getting prepped for the Cooper daddy's exam and these are meant to really fit really well into your day. So you'll notice the Getting Started these four lessons that total
36 minutes in total. So, about eight minutes per lesson. Right. They are broken down into really small bite sized pieces. So you can fit them in around other things.
In or what I did was I took a couple of evenings and actually burn through the most of these over just the course of a couple of evenings. They go very, very quickly. So Cooper daddy's Academy Academy from VMware and all of this training for Cooper Nettie is free.
Alright, Michelle. Anything else that we need to wrap up here.
Michelle :: Webinar Producer
It looks like questions have stabilized. So I just want to send my gratitude to you can thank you so much for
The information you shared today and thank you to everyone for signing in and listening along asking questions and just absorbing
All of this be sphere seven knowledge. I want to remind everyone that we've recorded this session today and we're going to send a copy out by the end of the week.
So you'll be able to review everything that was discussed today, check out our website and those courses linked in the chat and feel free to learn more about the promo code on our website.
All of those links are in the chat. I'm going to post them again just so there at the top of your list so you don't need to scroll too far.
And if there are any questions, feel free to ask them now or enter them now. But otherwise, I hope you all enjoy the rest of your day. Thank you so much, everyone.