Виртуализация от Майкрософт для специалистов VMware

Виртуализация от Майкрософт для специалистов VMware
9/16/2018 2:47 PM Быстрый старт — занятие 2: управление Виртуализация от Майкрософт для специалистов VMware Модуль 7: диспетчер виртуальных машин Virtual Machine Manager 2012 Corey: Fantastic. All right, so I think we’re about ready to move on and dive into I think what probably a lot of folks have been waiting for for awhile now, which is VMM 2012. Symon: Let’s do it. Corey: So without further ado, let’s go forth and conquer the wonderful world of Virtual Machine Manager. Symon: So I guess, you know, first thing to know, VMM 2012, where is it in its development cycle. So just last week at MMS the 2012 beta was released, it was announced, all of the features were announced to the first time publicly, so unless you were at MMS or watched any of the recordings or webcasts, this is going to be brand new. Corey: Yeah. Symon: But setting that expectation as well, this is a beta product but we think it’s awesome. We had the choice when we were designing this course, did we want to show only 2008 or did we want to go and show the beta, and you were strongly opinionated that we wanted to show 2012. Corey: I was, I – Symon: Why is that? Corey: I think that, you know the buzzword today is private cloud. And I think this particular product is a very solid offering into the private cloud space and I think really defines what it means to deliver private cloud, and the terminology that’s often used is infrastructure as a service. Now we’re going to dive into private cloud conceptually and how it’s implemented and all that towards the end of the day, but this really gives I think a very clear picture into what’s actually happening and what Microsoft’s direction is and is an extremely compelling product. The other thing is I’ve never been one to play it safe, so I think we dive in, I think we see what happens. I mean let’s – again, let’s set up some expectations, it is beta. I’ve only had my hands on this build for two weeks. I’m one of the privileged ones in that I was actually able to use the technology preview for about two months prior to the beta, so I’ve had a chance to kind of dive in and really learn what it does, but that being said I don’t know it all. I’m still figuring out what some of these buttons do. Symon: And there’s a lot in there as well. I’ve seen just massive improvements from 2008 R2, you know, big feature set changes. I guess really one of the biggest things I’ve seen is it’s not just about managing the VMs anymore, it’s about managing all the resources, the fabric as well, the storage, kind of giving you that whole end to end private cloud management and those resources. Corey: Take the simple notion of going from 120 PowerShell commandlets to over 600. Gives you a sense of how many features have been added. So a couple things, number one, the UI in beta is a little bit slow at times. The VMM server has 16 cores, 72 gigs of RAM and when I click a button it still takes a few seconds for stuff to open. It’s not the hardware, folks, it’s beta, there’s debug code, it will do that. Secondly, the UI from time to time just arbitrarily crashes. It’s beta. It just does that. It’s a lot better than going to CTP which just kind of mostly crash when you try to do stuff. But if I’m randomly doing something, it goes oh, I’m not responding, go away, you know, I’ll restart it, we’ll move on. It’s not the end of the world. And then some of these features we’ve kind of – I’ve – I was up really, really late last night, till I think it was one in the morning or two in the morning just filling up this VMM deployment with stuff that looks cool. And kind of making sure we can actually do some pretty compelling things that are not just look at the property page, cancel, we can actually do a few things. The most risky thing I’m going to do is I am going to patch the cluster. Symon: Have you tried this out before? Corey: Not on the – not with this set of patches on this cluster because you don’t get to trial patch it. Symon: You patch it and then it’s patched. Corey: Yeah, you know, if it’s a VM you can snapshot it and roll it back, but it’s physical hardware, it’s not the easiest thing in the world to patch it and go, cool, that worked, let me uninstall it and hope it works again. So we’ll see. Symon: Let’s give it a shot. Corey: So while we’re doing the – doing all the demos and using all the products they’re going to be moving between nodes while the nodes are rebooting and being patched underneath them. And I’m also going to power off a bunch of nodes. Now the data center is the other side of campus because we can’t get there, so they don’t come back out again. Symon might be taking a walk. So we’re living on the edge here, guys, so bear with us. Kicking back here, look, this guy’s chugging along quite – actually you can see that from the – let me just flick back to my demo desktop for a second. Symon: Yep, we’re up. Corey: And here we go, so that guy’s actually, you can see there, chugging along quite nicely with the deployment. It’s now in the customization phase, which is doing the sysprep stuff. So we’re going to – we’ll come back to that one and just kind of keep an eye on it as we’re going through. I misplaced my Live Meeting toolbar. There it is – Докладчики: Саймон Перриман и Кори Хайнс © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Учебное расписание Занятие 1: платформа Занятие 2: управление
Модуль 1: обзор виртуализации Модуль 2: отличия решений от Майкрософт и VMware Модуль 3: способы развертывания и архитектура технологии Hyper-V Модуль 4: высокая доступность и кластеризация Занятие 2: управление Модуль 5: обзор пакета System Center с акцентом на DPM Модуль 6: автоматизация с помощью System Center Opalis и PowerShell Модуль 7: диспетчер виртуальных машин VMM 2012 Модуль 8: частные облачные решения, архитектура и VMM SSP 2.0 Занятие 3: VDI Модуль 9: архитектура инфраструктуры виртуальных рабочих столов (VDI) | Часть 1 Модуль 10: архитектура инфраструктуры виртуальных рабочих столов (VDI) | Часть 2 Модуль 11: обзор решения v-Alliance Модуль 12: организация доступа к приложениям в среде VDI © 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Virtual Machine Manager 2012 | Часть 1
План обучения Введение в VMM 2012 Структура Библиотека Службы и шаблоны обслуживания Цели обучения Понять основные возможности и задачи системы VMM 2012 Познакомиться с концепцией структуры Научиться выполнять простейшие задачи в области настройки и управления Symon: So let’s walk through the agenda. So first we’re just going to give an introduction to VMM Cover the fabric, which is kind of the, all the core pieces from our compu pull(?) that we pulled together. We’re going to talk about the library a little bit. And then move into the services and service templates. Corey: Exactly, now the thing that we’re not talking about in this particular segment is the cloud components, because those are a big piece of it. Those will come later on when we do the private cloud section, because they’re more conceptual than physical. This particular segment and the way I put it together is all about the physical, tangible stuff you can touch. So the hardware management, the VM template management, the library, the objects, you know, what I call the tangible items. So let’s kind of jump in.

Обзор VMM 2012 Corey: First slide, Overview of VMM 2012, investment areas, right?

Области применения SCVMM 2012
Улучшения инфраструк-туры Сервер HA VMM Server Обновление Настраи-ваемые свойства Powershell Развертывание Структура Подготовка исходного состояния с помощью Hyper-V Hyper-V, VMware, Citrix XenServer Управление сетью Управление хранилищем Управление обновлениями Динамическая оптимизация Управление энергопотреб-лением Управление кластерами Управление структурой Управление облаком Использо-вание приложения владельцами Ресурсная емкость и возможности Делегиро-вание и квота Облако Управление службами Шаблоны обслуживания Развертывание приложений Выполнение настраиваемых команд Обслуживание с использованием образов Службы What did Microsoft decide to invest in with VMM 2012? What are the areas that they considered to be most important? Now you did some consulting from the standpoint of clustering on 2012 and what they were doing there, what can you tell us about some of those priorities? Symon: So really the thing was it’s not just about managing the VM, it’s about managing the infrastructure. So what you’re going to see is a lot more cluster management, cluster integration as well. Instead of just being able to deploy VM into a cluster like you could in 2008, you can now create a cluster. So you actually have the full cluster creation. So it’s really abstract in the admin and having them not go to the failover cluster manager console, hyper-v manager console, it’s saying go to the single interface, take care of everything from a single location. So really it’s a combination of the integration as well as the management, you know, the integration’s pulling all the pieces together and yet you can manage it from now a single location. Corey: So some key areas here, number one, in the area of deployment, some enhancements in the infrastructure, the VMM server itself is now highly available. So you can have multiple VMM servers and it will use the one that’s available, right. This is such a critical component, in the past folks would run VMM 2008 as a VM on the cluster to gain high availability. The model now would be VMM wouldn’t – you could, but you would not necessarily run it on a cluster as a node, you would have it as a separate cluster highly available because it’s role is so critical now. Symon: Absolutely. Corey: If it goes down there’s a lot of things that won’t work. Upgrade capability from 2008 R2 from the release candidate up to the full production version, custom property tagging, so it’s no longer just custom property 1, 2, 3, 4, you’re going to name value pairs and match those as you’re doing deployments. So for example you only want – you’ve got a node that has a mix of Dell and HP servers, but you only want this VM to be on a Dell server. You can actually do custom property matching so the VM goes only on a server that, where brand equals Dell and it’s tag is brand equals Dell. So you can do that level of property matching and then massive enhancements that we’ve seen – Symon: Your favorite. Corey: …around PowerShell. Symon: PowerShell. Corey: Yeah, you know, I’ m a PowerShell advocate now, but it took till version 2 for me to get there. The fabric, this is a new concept in VMM The fabric did not exist within VMM There were elements of it, for example agents, agents are part of the fabric. But the fabric represents the hardware layer. I use the – I use the analogy, and I think – I might have been talking to you at the time. We were talking about cloud and VMs and fabric and all that kind of stuff of, you know, picture a pond with candles floating on it. Was that you, yeah? Symon: Yeah, that was. Corey: It was very soothing and it was almost romantic, which was disturbing. So we had this pond and all these candles are floating and they represent VMs and they’re just there. They’re floating. You don’t know where they are or care where they are, they’re just there. They’re floating around and going to the, you know, wherever the currents of activity take them to the best place. The fabric is what you define to make that happen. The fabric is the physical layer, it’s the hosts, the clusters, the connectivity, the network and all the logic that goes into keeping that healthy. So if you look on the left hand side of that slide, bare metal provisioning, hyper-v Vmware and Citrix Xen Server management, network management, storage management, which is a new capability. Now we’re not going to be spending a lot of time on storage management simply because I don’t have connectivity to the right kinds of storage, it’s beta, the storage providers you can talk to are somewhat limited. We just didn’t have access to that equipment for this particular delivery. Then kind of on the logical side, managing updates and patches that you might say, well, config manager, that does updates and patches. Config manager can, but one of the big wins for Opalis I think early on was it could orchestrate cluster patching. Symon: That’s right. One of the big scenarios they always show. Corey: Yeah, exactly. Exactly. Cluster patching. Because that was a much more difficult thing to do because you’ve got to take into consideration the relationships between the nodes and the load, and there were a lot of people with config manager that they would just push out a patch and say mandatory and the whole cluster would go down. Symon: Every renode would reboot at the same time. Corey: Yeah, and so within config manager there isn’t that inherent logic of it’s a VM cluster, how do I orchestrate this properly. Symon: It was kind of a single server thing. No logic on this distributed architecture. Corey: Right, exactly, so this is what’s been included now on VMM. Dynamic optimization which balances hosts. Yesterday if you were here when we were talking about hyper-v and I showed my first hyper-v demo, I brought up a VM as my little test VM and I said if this vanishes that’s ok. And you kind of looked at me, what do you mean it’s going to vanish. What, it’s a – it’s a demo, it shouldn’t vanish. It was on a set of nodes that had dynamic optimization. And what dynamic optimization does is live migrates things on demand to wherever the best place for them is. Symon: So how is this different from intelligent placement? Because intelligent placement, that kind of picks the best location for dynamic optimization, how does that enhance – Corey: Intelligent placement, when you go to deploy a VM says hey, Symon, I think you should put it here. But you can put it wherever you want. Dynamic optimization goes, uh, that guy’s way busier than these three, let’s move some stuff over here, and it just does it. Symon: And it will still use kind of that intelligent placement in order to pick the best host, but it’s more kind of that automatic triggering, that automatic analysis. Corey: Exactly, stuff just live migrates on its own when the best time is – Symon: Like the candles on the lily pads floating in the pond. Corey: Exactly, I know. Wow, we’re getting way too deep. Worth mentioning, it’s controllable, it’s not just going to do it unless you tell it to and then you get to control it, how aggressive it is, how often it does it, whether you care more about CP network disk, what your thresholds are, so there’s a tremendous degree of customization. Symon: And it does it using the live migration as well, right, so when you’re actually moving the VMs from one node to another no perceived downtime, VMs stay up and running. Corey: In fact you can be blissfully oblivious. I could have been working that Opalis server while it was live migrating. Symon: We would have never known. Corey: You know I’ve done this so often that it just – all the stuff that we’ve been working on, and I know it’s – I can’t really show you right now per se, but all the stuff that we’ve been working on over the last day and a half or so are VMs that are running on this cluster that’s got dynamic optimization applied. So those VMs, my domain controllers, my ops manager servers, my VMM servers, my DPM servers, have been in flight the whole time whenever VMM decided it was – the load was too big and wanted to move things around. And the beauty of it is I don’t know or care. Symon: Right. Corey: And that kind of really gets back to what the definition of the cloud is, right? I don’t know or care. It’s just there, it just works, it has the capacity, it has the response time. I don’t care where it is or where it’s going or how often it goes there. Symon: Absolutely. Just maintains itself. Corey: I hit the wrong direction there by mistake. So next one, cloud, kind of addressed this, the cloud in terms of VMM involves taking the resources you have and slicing them up into pieces that you can give to people. Now we’ll do more of this towards the end of the day, but it involves defining what are called cloud objects, and cloud objects have places they’re allowed to live and resources they’re allowed to consume. The beauty of it is like well you’ve seen intelligence placement, so you go hey, new VM and it goes, all right, node four, that’s your best node. When you define a cloud you no longer see node four. You no longer see cluster. You simply see this cloud is the best cloud for you. And you have no insight into the physical implementation under the scenes, you don’t know if it’s one node, two nodes, ten nodes. You don’t know what the storage is, you don’t know what the network is, you simply say that cloud plugged into my corporate network and VMM figures it out. Symon: I think the key is that you shouldn’t need to know, right. It’s not like it’s going to abstract it from you and you’re blind to it. You have that level of granularity if you want it, but the idea is we – you shouldn’t care about it. Corey: It’s a case of who’s the user, who’s the consumer. You as the virtualization layer admin, you would care. The resource administrator for the app dev division who’s provisioning a server they can test against, we don’t want them to know or care. It should be hidden from them, they should be blind to it. They’re just going to pick the cloud and go. And then finally in this area right here is services. So we’ve worked with the notion of a VM as a template, what about a service as a template. Now what is a service? A service is one or more VMs connected to one or more networks running applications that have parameters around elasticity and scalability. So I’m not going to define, you know, give me a Web server, I’m going to say give me four Web servers connected to these networks with two back end SQL servers, go. And it will deploy all four or in that case all six as a service and let you manage them as a unit. Symon: And it deploys the networks as well and it can even deploy load balancers. Corey: Load balancers, provision the storage, attach the storage, do everything, and then if you decide later on down the road that wow, that service needs more CPU, I’m going to update the service definition to four CPUs. It’ll update the deployed VMs. Symon: Very cool. Corey: So it’ll actually go out and do that, that live update to all of them. Corey: There’s process around that about how it will roll in an update on a maintenance cycle and whatnot, you’d obviously have to recycle the VM to add additional CPU, so it would orchestrate all of that for you. Symon: Sounds good, so let’s cover the architecture a little bit now. [text was already here] QUESTION: should this highlight reference VMM Server HA, planning, upgrade, etc? Do we want this structured to mirror our sessions?

VMM 2012: архитектура Интерфейсы управления
9/16/2018 2:47 PM VMM 2012: архитектура Консоль Веб-портал самообслужи-вания Сервер управления Operations Manager Windows PowerShell Соединитель SCVMM Сервер управления Virtual Machine Manager Интерфейсы управления Сервер служб разверты-вания Windows (WDS) Сервер служб обнов-ления ПО Windows (WSUS) Сервер биб-лиотеки VMM Уровень абстракции виртуализации Узлы и кластеры Hyper-V Узлы и кластеры Citrix XenServer VMware vCenter Corey: Architecture for those familiar with VMM 2008 hasn’t fundamentally changed. You look at this it kind of looks the same, right, you’ve got a PowerShell provider, a self service portal, a console, the management server which talks to a SQL database, a connector that goes back to the Ops Manager and then your management interfaces. The new piece there is the virtualization abstraction layer. That’s the layer that makes all the hyper visors kind of look the same to VMM. So that’s the bit that allows you to go start VM and if the VM’s named VM1 it’s going to find VM1 and start it regardless of the hyper visor it’s running on. Now any time you abstract something you’re not replicating 100% of the functionality so for example you don’t get 100% of the functionality of V center in VMM. You only get that in V center. But you get enough and in talking to the customers that do this there’s enough there that you can cover the vast majority of day to day operational tasks. The same thing with Citrix Xen Server, right, so you don’t get 100%, you never do. But you get a very very large very big subset of all the functionality. And then over here on the side we have integration of what are called services components, so we’ve got Windows Deployment Services, we’ve got Update Services and we’ve got the VMM Library. And so there’s very big and very broad integration pool because of all these components. Узлы и кластеры VMware ESX Узлы и кластеры VMware ESX Хранилище и сетевая структура Microsoft Management Summit 2007, March 26-30, 2007, San Diego, California© 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Развертывание и обновление
Высокодоступный сервер VMM Выполняет основные запросы клиентов Сервер VMM теперь поддерживает кластеры, поэтому единственной точки сбоя больше нет Обновление С VMM 2008 R2 до VMM 2012 RC С VMM 2012 RC до VMM 2012 RTM Настраиваемые свойства Пары имен и значений Больше не нужно использовать названия типа Настраиваемое1… Настраиваемое 10 Powershell Полная поддержка скриптов Powershell Powershell 2.0 — стандартные команды, схема именования объектов Обратная совместимость с интерфейсами скриптов VMM 2008 R2 Corey: Talking about deployment and upgrade briefly, how do you get to this point? Number one you have a highly available VMM server, so you can have more than one VMM server and it will work essentially as a cluster to make sure that if one goes down the other will just pick up the workload and things will continue to function. In terms of upgrade paths you have a couple of options, we can go from VMM to 2008 R2 to VMM RC and from RC to RTM. So pretty basic upgrade paths, and again, this is as it sits at beta, anything and everything I say here may be completely wrong by the time it releases. I mean that’s the nature of beta and we just need to make that up. Custom properties as well, PowerShell, PowerShell, PowerShell, PowerShell. Symon: Lots of PowerShell. Corey: I’m willing to be I will say PowerShell 45 more times in the next two hours. Symon: Let’s hope not. Corey: All right. So that’s your real high level. Let’s kind of dive in now and talk about what is the fabric and then jump into the UI and start looking at the ways that we would configure some of these things.

Структура TechReady12 9/16/2018
Corey: All right. So that’s your real high level. Let’s kind of dive in now and talk about what is the fabric and then jump into the UI and start looking at the ways that we would configure some of these things. © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Управление структурой
Физический сервер Управление несколькими низкоуровневыми оболочками — Hyper-V, VMware, Xen Интеграция со средствами удаленного управления — IPMI, DCMI, iLO, SMASH, пользовательскими инструментами Подготовка узлов: от системы в исходном состоянии до среды Hyper-V и кластера Сеть Создание логических сетей на базе виртуальных ЛС и подсетей в каждом центре обработки данных Управление статическими IP-адресами, виртуальными IP подсистем балансировки нагрузки и MAC-адресами Автоматическая подготовка подсистем балансировки нагрузки Хранилище Обнаружение массивов и пулов хранилищ Классификация хранилищ по пропускной способности и возможностям Обнаружение или настройка логических номеров устройств и их назначение узлам и кластерам Hyper-V Подготовка новых хранилищ с развертыванием ВМ Corey: So the fabric is that new and exciting term that represents physical servers, network and storage. In terms of physical servers, three major hyper visors supported, hyper-v, Vmware and Xen. Supports hardware management protocols, IPMI, DCMI and SMASH as well as you can write custom hardware providers. Now you may be wondering what is this, this is your iLO and Idrac(?) type interfaces, right, so the hardware interfaces that are on the back of your server that let you go in and do things like power on and power off remotely, remote console access. These are particularly important for VMM for power management because what it allows us to do is tell VMM, hey, if we’re quiet you’ve got four nodes, live migrate to one or two nodes, power off the other two. Symon: Very nice. Corey: And when the load comes up so the thresholds are being exceeded, power them on, move them over, power it on and move them over. Symon: So really just this dynamic management, right, you don’t really have to think about it, you save power, save – Corey: Exactly and you can control it and be aggressive, you can say, you know what, that’s cool to do middle of the night, but middle of the day no, that’s no cool to do and you can control that within VMM, and I’ll show you where that is. It’s pretty slick. I’ve been trying to actually make it work but I haven’t been able to. So I’ve been trying to actually get it to dynamically power down one of my servers, it hasn’t actually done it for me yet, I think just because I’m using them too much. I haven’t done the magic trigger that would just make it go, oh, you don’t need that guy and shut it down. Without me forcibly shutting it down.

Управление обновлениями структурных серверов Управление операциями обновления (сканирование и исправление по запросу) Обновление кластера Hyper-V полностью автоматизировано Интеграция с сервером обновлений Windows Server Динамическая оптимизация Оптимизация работы СМ с помощью схемы балансировки нагрузки на уровне кластера Перенос нагрузки с использованием динамической миграции Оптимизация энергопотребления Увеличение количества ВМ на узел за счет динамической миграции Оптимизация энергопотребления путем отключения серверов Улучшенная схема размещения Более 100 проверок размещения Поддержка настраиваемых правил размещения Службы на базе систем из множества ВМ

Сеть Создание логических сетей на базе виртуальных ЛС и подсетей в каждом центре обработки данных Управление статическими IP-адресами, виртуальными IP подсистем балансировки нагрузки и MAC- адресами Автоматическая подготовка подсистем балансировки нагрузки [This audio actually addresses more than one slide in the “networking” set – he didn’t show each slide, he just kept talking but this can probably be broken down to relate to the next four slides in the networking section.] Corey: So the network. You now within VMM draw a picture of your physical network. Networking in VMM 2008 was somewhat limited, you would simply define all your network connections across all your hyper-v boxes, and then VMM would detect what they were and would actually let you – and would kind of import those networks into hyper-v. With – it’s kind of a reverse model with VMM You define in VMM 2012 what you want the networks to be and it will go ahead and make them all for you and ensure they’re all the same and configured properly. Symon: Nice. Corey: In addition, it will manage static IP addresses. One of the challenges we often run into in VMs, when we get into private cloud scenarios where you may be provisioning, decommissioning, provisioning, decommissioning, DHCP is fine but sometimes you need static. Maybe you just want it, maybe you need it. Maybe you’ve got firewall rules. It will actually allocate static addresses, so you create almost a pool of static addresses and kind of like DHCP it’ll actually assign those a static address and manage all that for you. It defines logical networks, you no longer need to know, and if you’ve already done this, gone into hyper-v and said hey, I’ve got three interfaces, I want to connect, make this network on this card, you’re sitting there in IP config going that’s interface number two, this is, ok, that’s that one – you don’t do it anymore. It – you simply put in the IP ranges of logical networks, it figures it out for you. Symon: So really there’s no IP address management you need to do, you simply just give it a pool of IP addresses and say go run with it. Corey: Yeah, you say you know what, , that’s my internal network and every single card that’s in every single hyper-v server that has an IP address in that range will associate itself with internal network. Corey: You can then say I want a network connection named Corpnet on my internal network logical network. Every single hyper-v server gets a new hyper-v network named corp on internal network. Symon: Very nice. Corey: You never think about the card. You never think about the IP on the card, it just figures it out. [the following text was here before transcription of presentation] Logical network is abstraction of the physical network infra which allows you to model network based on business needs. You can use them to describe networks with different purposes Traffic isolation, provision network for different SLA’s.

Логическая сеть Абстракция для администраторов серверов при моделировании служб Моделирование сетей для различных сценариев использования Расположение Логическая сеть Виртуальная локальная сеть Подсеть Нью-Йорк ИНТЕРФЕЙС 5 /24 ВНУТРЕННЯЯ 7 /20 Бостон 10 /24 12 /24

Логическая сеть и пулы IP-адресов
Группа узлов Подсети IP-адресов и виртуальные ЛС (VLAN) Пулы IP-адресов Пул 01 ИНТЕРФЕЙС БОСТОН /24 VLAN 5 Пул 02 VLAN 7 DHCP [text was already here] Pools could be IPv4 or IPv6 but not both. НЬЮ-ЙОРК /24 VLAN 10 Пул 03 Пул 04 VLAN 12 DHCP

Управление пулом IP-адресов
Создание ВМ Выдача IP-адресов Удаление, миграция ВМ Возврат IP-адресов

Управление пулом MAC-адресов
Диапазон MAC-адресов: 00:1D:D8:B7:1C: :1D:D8:F4:1F:FF ( адресов) Статические MAC-адреса Создание диапазона MAC-адресов Опреде-ление пула Связы-вание с группой узлов Выделе-ние пула Создание ВМ Выдача MAC-адресов Удаление ВМ Возврат MAC-адресов

Хранилище Сквозная идентификация устройств для хранения данных
Сквозная идентификация устройств для хранения данных Выделение и назначение хранилища Подготовка новых ВМ с использованием SAN Миграция ВМ на базе SAN [This audio transcript addresses more than one slide on the subject of storage but the presentation didn’t break it down slide by slide.] Corey: And then finally, storage, for storage providers SMIS, which is the storage management interface specification I think, I looked it up on wikipedia, there’s a couple versions of it, of what that actually stands for. But it’s a generic specification that storage providers are going to adhere to. So if you look at your different SAN vendors, your different storage vendors, they will expose their storage and their capabilities using this standard so that different companies can write different management tools. And so this allows a VMM to go into HPMSA or a Dell array or a left hand network array or one of the other ones, I’m blanking on the name, to go into one of those arrays and say hey, make a LUN and be able to tell the array in the generic language make a LUN. To be able to interrogate the array and say hey, what do you have, what are your storage pools, what are your disks, what are your virtual disks, how does it all work together. And when you piece all that together, what that means the VMM can do is it can go hey, bare metal machine, storage array, deploy hyper-v, bring it online, deploy a LUN, unmask the LUN for that piece of connectivity. The only thing I can’t do is plug in the cable. Symon: Now that’s pretty cool. Corey: So it will manage and deploy the storage, it will map the LUNs back to hosts, it’ll map the LUNs to VMs. Symon: So I guess that’s why we said that, you know, VMMs no longer about just managing the VMs, right, it’s about managing the whole fabric, the storage, the networks as well as the VMs. Corey: Might as well just call it Virtual Data Center Manager, that’s my vote. So you get – and it will also then take advantage of things like snapshots within LUNs. LUN cloning capabilities. There’s a lot of things that it can do and right now there’s a fairly limited set of arrays it’ll talk to, but that’s going to get more and more the closer we get to RTM as well as a provider model so you can write additional providers. So if your ven – if there isn’t one there you can make one or get someone to make one. Symon: Wow. So let’s move on and talk about some of the update stuff, right, that’s one of the big features, I love it, I’m a cluster guy so I just love what they’re doing with the update.

Автоматизация хранилища — VMM 2012
WS-MAN СЕРВЕР WMI Служба хранилища (поставщик WMI) Модуль SMI-S Клиент CIM-XML CIM-XML Поставщики SMI-S Массив Средство админис-трирования SAN Пул LUN LUN LUN

Автоматизация хранилища — обнаружение
VMM Служба управления хранилищем Поставщик хранилища Массив Пул Нераспре-деленный Распре-деленный Логическое устройство …

Автоматизация хранилища — обнаружение
VMM Агент VMM Ресурсы компьютера FCHBA Порт Виртуальные порты Инициатор iSCSI IQN Диспетчер дисков Диск Том

Автоматизация хранилища — скзовная идентификация
Экземпляр службы Виртуальный уровень Компьютеры В гостевой системе Логический диск МояСлужба МойVM01 (вирт.) Диск 1 (VHD-файл)

Автоматизация хранилища — сквозная идентификация
Виртуальный уровень В гостевой системе Логический диск Физический уровень В ОС узла Том Уровень массива Логическое устройство Диск 1 (VHD-файл) Том 1 (R:) Том 1 (C:) Логический диск 1 (CSV) Логический диск 2 (проходной) Логический диск 1 Логическое устройство 1 Логическое устройство 2 Логическое устройство 3

Автоматизация хранилища — скзозная идентификация
Уровень массива Логическое устройство Пул Массив Поставщик Логическое устройство 1 Логическое устройство 2 Логическое устройство 3 Пул хранилища Массив хранилища You can access all these objects through the Powershell layer. Поставщик хранилища

Управление обновлениями структурных серверов Управление операциями обновления (сканирование и исправление по запросу) Обновление кластера Hyper-V полностью автоматизировано Интеграция с сервером обновлений Windows Server Динамическая оптимизация Оптимизация работы СМ с помощью схемы балансировки нагрузки на уровне кластера Перенос нагрузки с использованием динамической миграции Оптимизация энергопотребления Увеличение количества ВМ на узел за счет динамической миграции Оптимизация энергопотребления путем отключения серверов Улучшенная схема размещения Более 100 проверок размещения Поддержка настраиваемых правил размещения Службы на базе систем из множества ВМ [Corey put this slide back up on the screen after the audio from the first storage slide, so I copied and pasted it in here for the sake of coherence] Corey: So moving into sort of the, out of the hardware and into the software management component, update management. This is – this will leverage Windows Server Update Services as a binary distribution point so you configure an update server, you sync it with Windows Update, it’ll pull all the updates down, you then tell your VMM server go here to get all your updates, it will scan the servers in your fabric, tell you if they’re compliant and give you the option to remediate. And it does this using a custom set of what are called baselines. So you can define baselines that represent configurations and – by the way you will see all of this in gory detail -- and then simply click a button and it’ll patch it for you. And with a cluster it’ll evacuate the VM’s patch, the node, reboot it, bring it up, move the VMs back, evacuate the VM’s patch, the node, reboot it, bring it up, completely reorchestrate the cluster and you never need to know what’s happening, so we’re going to do that and cross our fingers that it – when I did try it the last time I did try it it actually worked great. Symon: I’m sure it will. Come on. Microsoft technology, it’s going to work. Corey: Will you stop it. If it crashes and burns it’s his fault. I’m telling you right now, there’s a bunch of people behind the cameras that are cringing right now. Dynamic optimization kind of alluded to the idea that it will monitor the performance, move the VMs if needed. Power optimization is a component of dynamic optimization, it does the power management, and then enhanced placement which is intelligent placement multiplied by Because there’s way more characteristics that are actually brought in there. One of my favorite elements of enhanced placement, they mention this thing called, support for custom placement rules. There’s something called a – I forget if it’s a capability or a compatibility profile, I think it’s a – or a capacity profile, it’s something starting with c and ending in profile. And when we get in the UI I’ll point out what it is. It’s like a capacity or capability profile. And so what it lets you do is decide that, you know, for this particular type of host it requires dynamic memory, it requires high availability, it will not accept remote FX. And before you can place a VM on that host, regardless of the physical characteristics, it’s also got to match these logical characteristics. Symon: I mean that makes a lot of sense for a data center admin, right. They don’t want to go deploy a VM somewhere and then have it not be able to do what it’s supposed to do. Corey: Right, exactly, so let’s say there’s – you don’t want a VM with more than 8 gigs of RAM on these hosts, for whatever reason. You can create that profile to make that restriction and then intelligent placement will take that into consideration. Symon: Very cool.

Физический сервер Управление несколькими низкоуровневыми оболочками — Hyper-V, VMware, Xen Интеграция со средствами удаленного управления — IPMI, DCMI, iLO, SMASH, пользовательскими инструментами Подготовка узлов: от системы в исходном состоянии до среды Hyper-V и кластера Сеть Создание логических сетей на базе виртуальных ЛС и подсетей в каждом центре обработки данных Управление статическими IP-адресами, виртуальными IP подсистем балансировки нагрузки и MAC-адресами Автоматическая подготовка подсистем балансировки нагрузки Хранилище Обнаружение массивов и пулов хранилищ Классификация хранилищ по пропускной способности и возможностям Обнаружение или настройка логических номеров устройств и их назначение узлам и кластерам Hyper-V Подготовка новых хранилищ с развертыванием ВМ [Corey brought this slide up again, too, so I’ve pasted it in where it follows the other one in the audio] Corey: Physical server management, three hyper-visors, we’ll talk about how these actually all relate. Hyper-v, VMware and Xen.

Сеть Создание логических сетей на базе виртуальных ЛС и подсетей в каждом центре обработки данных Управление статическими IP-адресами, виртуальными IP подсистем балансировки нагрузки и MAC- адресами Автоматическая подготовка подсистем балансировки нагрузки Corey: So networking. Defining logical networks. Let’s kind of look at sort of our first view of VMM 2012 and we’ll talk through how you would go about building and defining logical networks and what those would wind up looking like. So let’s go to kick out to the demo and spend a few minutes there and then we’ll probably take a brief break. Symon: Sounds good.

Создание и определение логических сетей — демонстрация
Corey: So kicking back over to my desktop. And the first thing we’ll take a look at on the desktop is that you’ll notice my new VM from the previous Opalis section, it’s now deployed. It’s not started though. Symon: That’s great, why doesn’t it start automatically? Corey: Well because I’m still in debug mode on Opalis. So I kick back to Opalis and this step is done we’ll go next which will get the VM settings and we’ll go next and that should conceivably start the VM. Those failed probably because I made a typo in there somewhere. So I’m not going to worry about it, but you can see the VM deployed this, it was the least risky part, so who knows. But there’s the VM and I can probably just manually start it and it’ll be just fine. So you get the idea of what this did. Symon: Absolutely. Corey: All right, so VMM Let’s begin kind of right here with it first being open. Now you’ll notice that you first open this there’s a lot here in the UI. There’s a lot to look at, there’s a lot to see, it’s got that new look and feel, those really cool power on power off buttons. There’s also a bunch of buttons that are big blue things they haven’t drawn an icon for yet, and you’ll see some of those kicking around. So this is the VM and services node and this is where you can see all your VMs and all your services. I’ve got the correct level of rights, so I can see all the hosts, I can see individual hosts, there’s my DPM servers running as VMs. There’s all the contents of my cluster. Symon: So it can manage at a cluster level, you can manage in the VM level and I see this cloud, are we going to get into the cloud? Corey: We’re going to get into the cloud part towards the end of the day, so we’ll definitely be coming back to this. Symon: Sounds good. Corey: There’s nothing running in that cloud at present. It’s a very empty cloud. We’ve then got the fabric. We’re going to come back to this in just a second, but this is where I go physical level management. We’re going to kick down and talk about settings for a few minutes. And in doing so I’m actually going to – why I’m skipping a few slides later, because I’m going to show you some things in here that we’ll just kind of briefly touch on. So we click settings and there’s a lot of things in here. You’ve got your typical general VMM sort of settings. One in particular I want to point out under network settings right here. Automatic creation of logical networks, automatic creation of virtual networks. Symon: Very nice. Corey: Check by default what that means is if you bring up a hyper-v server and it’s on a subnet or has an IP address that VMM doesn’t recognize, it will create a definition for that subnet. And it will then create a network within hyper-v host so the VMs can talk to that logical network. So it’s fully automated management of the networks and you can see it like how it detects this based on the DNS suffix label, so in my case it would find something like Contoso.com, which is the DNS suffix name. We have as well these idea of profiles. Now the profiles are a particularly important concept. We’ll address more about profiles when we deal with the cloud section, but think of these as credentials you want to allow someone to use without telling them the credential. So for example I’ve got one in here which is a run as account which is my Dell iDrac Admin. So I don’t want to give the guy provisioning something maybe the admin password for my bare metal configuration for whatever reason. Maybe there’s segmentation I don’t want to have that, I can create this run as account, I’m going to just double click on it, and embed the password. Now this is all secure and encrypted in the VMM database obviously. So now what he’s going to do is whereas in VMM 2008 you would enter the credentials, now you pick the run as account. And I can create complete libraries of accounts, known as run as accounts. I can also do what are called run as profiles. And a profile is a collection of accounts. So let’s say I’m deploying a service and the service involves using four different accounts, one for SQL, one for a Web server, one for a database, one for something else. I can create a run as profile that contains all those unique accounts as a run as account and it’s going to try all of them until it gets one that works. So it’s a group of accounts that can be tried as a unit. So you don’t need to know the specific account, you can have multiple accounts and it will just cycle through them until it finds one that works. We have this notion of something called a servicing window within the settings, now the servicing window is a pretty neat idea actually. It’s not used for anything specifically, but what it allows you to do is create a window of time such as monthly. Symon: Ok. Corey: And within this if I go, I can give it a category, updates, you just make this stuff up as you go along, and we’re going to do this every month on the first day of the month. And there’s a servicing window. What I actually get to do now is I can assign that servicing window to hosts. I originally saw this, I asked the question, oh cool, does this mean that during that period of time it’s going to automatically flick it to a maintenance mode? It doesn’t. But it’s a query able property now. So if you’re doing things like orchestration Opalis you can query for the maintenance window and then programmatically flick it over to maintenance mode as soon as the maintenance window starts. This is not going to – VMM it doesn’t forcibly do this yet. It – there are no plans to my knowledge to do that, but I can’t speak for the future, but as of right now it allows you to create these maintenance windows, associate them with objects so you can actually query for them. Hey, what’s the next maintenance window for this host where I’m allowed to do something. I need to patch it, what’s its next maintenance window? And you can build all of this as data and associate it with those different objects. Symon: Pretty cool. Corey: Configuration providers, so we talked about the idea of being able to talk to storage providers, to load balancers, this is where these configuration providers would actually be loaded. So it’s – it’s like a driver library of these third party libraries that let you configure Citrix Netscalers, BIG-IP F5, HP Sans, Dell sans, whatever happens to be supported. And so you would load this with the providers for all the hardware that you have. And then your connections back to Ops Manager. Symon: And you haven’t left the settings area, those are just – so many settings, so many options. Corey: No, no, I could sit here for five hours. Back up to the fabric – Symon: Managing the fabric – Corey: Managing the fabric, addressing networking, logical networks in particular. So let’s kind of spend a few minutes there and sort of talk about that. A logical network is an object that represents essentially a collection of subnets that represents a location within the company. Now the example I give you, and I don’t have this particular setup within the demo environment itself, but what I do have here is a little diagram that I’ll show you. Here’s an example of what – of the exercise you might go through with VMM 2012 in planning your network implementation. So this is, may be what a company’s network might look like if you distill it down to a couple core pieces. I’ve got an external facing network, got a perimeter network, I’ve got a hyper- v host in the external network, we’re going to have VMs that are connecting externally to the perimeter, I’ve got a cluster that’s got connectivity on both sides, I’ve got an internal network, a storage network and I’ve got a management network where all the Ilo and idrac stuff happens. And so one of the things you would do is you would want to represent this architecture in VMM. For networking purposes. So how do I do that? On the fabric I’ve got this area called logical networks. And I’ve created one already, let’s go ahead and create another one. Symon: Now a quick question, I see this is an IPv4 network, does VMM support IPv6 as well? Corey: Absolutely. Absolutely. Everything is 4 or 6 does – Symon: I mean I think you can pretty much assume all Microsoft products – Corey: Exactly. Symon: are going to be supported. Corey: Exactly. So let’s do a perimeter. Perimeter network and hit ok, and that’s all there is to define a logical network, right there’s – it doesn’t – it’s just a named object that you can use to associate adapters between VMs and between hosts. If you wanted to be kind of automatically or logically associated then you’ve got to start adding some definition to it, so to do that I’ll go up there and go create definition and where is this network valid? This is only valid on the cluster. It’s only valid on the cluster. And I’m going to add subnets to it. So this is going to be the subnet, let’s do and it’s going to have a subnet of 16 bits. So that’s the way I define it and then I’m not implementing VLAN tagging so I’m going to put VLAN 0. So you can actually define VLANs at this level as well. Hit next and that’s it, so I’ve now got a definition defined. If I’m going to being adding VMs to this network the VMs are going to have the choice, you know, when I want to deploy the operating system of being either DHCP or static. If they’re going to be DHCP that’s fine, they’ll just pick up an address, but if I want to deploy them as static and I don’t want to have to worry about going into a VM and inputting a static address, VMM will actually do that for me. So it’ll actually put the static address in the machine and it does that by creating an IP pool. So let’s say I’m doing a range here, this is my LAN range or my perimeter range, perimeter range, and begin address is 16, let’s do 16.1, to let’s just do that, that whole third subnet, the whole fourth octave. VIPs and reserved IPs, VIPs are virtual IPs using loads balancers or IPs that you know are in use in the middle of the range. You don’t want to create two ranges, so you just exclude, it’s like a DHCP – Symon: Oh that’s right, that’s nice. It makes sense. Corey: Gateway, – say 1.100, I’m just making this up. Metric associated value, DNS, and someone has asked explicitly about being able to do DNS search word as one of the questions and this is actually where it is. DNS will be , that’s my DNS server, Contoso.com is my suffix and I can add additional DNS search suffixes in that order. Win Server, and that’s it, so I’ve now got an IP pool associated with that virtual network. Symon: Great. Corey: Now what do you do with that from here, right? Well, what you would do now is back in your fabric you’ll notice I’ve got a host up here, and let’s say that this DPM host had a couple of adapters and one of them was associated with that perimeter network. Or maybe my nodes in my cluster here is associated with that perimeter network. I can go into my hardware settings and we’ll kind of talk a little bit about what’s in here in just a second, and then come down to the networks and you’ll notice that I’ve got individual networks and it’s actually detecting the IP address of the adapter. So this is my management network. So I can choose to associate this adapter with perimeter network. Symon: Confirm? Yep. Corey: Hit ok, and I would repeat this process across all my hosts. Now, you might say well that’s a lot of clicking. A, if this were all – if I had this all set up in advance it would simply detect them and do the association automatically and b, you can do it in PowerShell. Right? So this allows me now to go in and associate these logical networks. So that when I begin to create a VM I only pick the logical network I want the VM to talk to, I don’t pick the physical adapter or the physical IP, I simply say this VM, this logical network, VMM makes sure it’s connected to the right virtual switch on the right hyper-v host and gets the right static IP from the address pool. Symon: So again, this is just simplifying the deployment, simplifying management. Symon: And so for an IT pro I don’t have to really worry about my IP addresses now. Corey: Right, if I’m deploying a service I shouldn’t have to choose the subnet and the switch. I should only choose the fact that that’s on my company’s network, it’s my internal corpnet. That’s where I want the service to be and the fabric should figure it out, and this sort of functionality’s what enables that step to happen. The other piece that we’ll look at in here is MAC address pools. So in addition to IP address pools, we’ve got MAC address pools. Now we’ve got two MAC address pools that we can address quite briefly the default and VMware MAC address pool and the default MAC address pool for hyper-v. Xen center, or Xen server, Xen center as well, uses the same MAC address pool. But you can define additional MAC address pool, and you may be doing this if you’ve got load balancing clusters in place, you’ve got ranges of MACs assigned for particular things, you can define those different address pools and kind of use them at will. Symon: Ok, that sounds good. So are you going to show us how to configure them, or – Corey: The configuration is not really all that difficult. You simply come into the wizard, choose the scope, choose the MAC address pool and you’re done. Symon: Pretty straightforward. Corey: Yeah. One of the things that – and I can’t thoroughly demo this, so I apologize, but I’ll just point out the entrance, the location here. You can configure load balancers and VIP templates. A VIP template is a virtual IP template that represents a generic configuration that can be applied to a load balancer from a certain manufacturer here. So the load balancers represent the physical hardware entities. So if you deployed five or six or seven or a dozen load balancers you can register those load balancers as pieces of hardware that operating systems and tools and applications can utilize within VMM right here. The configuration for those load balancers are the VIP templates. And so we’ll quickly step through one of those. Symon: And there’s going to be some kind of inbox default load balancers? Corey: There’s support initially, and I’m trying to remember this off the top of my head for, I believe it’s big IP F5 and Citrix Net scaler. Symon: That’s right. Corey: There may be others, but those are the ones I remember. Symon: I know NLB will actually be coming out with one as well, the network load balancing product, but it’s not yet available in the Beta Corey: Right, so the one for the – the built in Windows one. Symon: That’s the built in Windows one. Corey: So this is your basic load balancing template, how do you want to do the load balancing, do you want to enable persistence, what’s the method that you’re choosing, it’s not going to do persistence, the method you’re choosing, round robin response time will be response time, how do you want to test that it’s healthy, we’re not going to put any in there, and that’s now an object that you can choose when you’re deploying configurations. So like I say, here’s my service, it has two Web servers, here’s the load balancer, here’s the configuration of the load balancer, which is what the VIP template does. Symon: Ties everything together, that’s’ really nice. Corey: Absolutely. For storage, again, I don’t have the providers available, so I can’t directly configure the storage, but in here is where you would actually configure things like your provider. So if you want to configure the connection through to, for example, your HP SAN and your Dell SAN or you know your left hand SAN, whatever, this is where you’re actually going to configure that connection. And from there it would be able to enumerate all the arrays that you have. Now what you can do is create classifications, and this is the really interesting bit. When you choose a classification, we’ll just call this one gold storage, and let’s say this is HP UI Bug, EVA 15k drives, super fast. All right, so this is – this is my gold storage. I can then begin to associate with that gold storage pools. So list all my providers, it’ll then enumerate all my storage pools across all my providers. And I can go hey, you know what, those four storage pools, they’re on the big SAN, they’re super fast, they’re super expensive, they’re classified gold. So when you deploy a new service you can simply choose the storage class. Symon: And so why would you want to separate them, just based on the speed, the quality – Corey: You can do whatever way you want. Like a lot of companies implement chargeback, right, if you’re going to be on the gold storage pool, well then you’re charged back for using, that’s more than if you’re on the iSCSI San versus the 8 gig fiber SAN. And then depending on if those pools are available, so when you go to do placement you’ve defined that, you know, your service template’s going to use gold storage, you’ve picked the host it’s going to go on, assuming that host has access to one of the storage pools classified gold it’ll just figure it out and do the connectivity for you. It’ll deploy to the right, for example, CSV volume, it’ll deploy to the right disk array. You don’t have to worry about it. All you want to do is say, you know, this is important, it goes on the expensive storage and VMM figures out what storage is expensive, what it’s connected to, what host it can go to and puts it in the right place. Symon: Very cool. Corey: So completely abstracted. It is very cool to see in action and I know there’s going to be some demos on the way in the near future, so certainly take a look at those, but that’s the basis behind what this actually does. All right, so I’m kind of continuing forward for a second. Where are we to, moving up through the library, sorry, through the fabric. We have this notion of – I’m getting out of breath. We’re having this notion of a library server. Library Server hasn’t change, it’s still what it was in the VMM 2008. Symon: Holds the templates, stores the VMs – Corey: Yep. Exactly right. So this is just the object that represents the library server. So there’s nothing we’ll do in here. We’ll look at the library and those related objects here shortly in the near future. PXE Server, that’s a new one. What does a PXE Server do? Well a PXE server is a WDS server. And so when we look at our different scenarios for deployment, one of the scenarios that we’ve alluded to and talked about is this notion of bare metal deployment. So you can roll in a rack of servers, give me that rack of servers. As long as they’ve got their bare metal configuration protocols done, things like iDrac, Ilo, whatever, I can now tell hyper-v hey, or tell VMM, go find that server, put an OS on it, connect into storage. And it’s the PXE server component that allows that to happen. We’ve got the update server. The update server is your connection to a – a Windows Server Update Services machine. So when we talk about compliance, which is the next thing that we’ll address here, we talk about compliance, this is where the list of patches and updates would actually come from. So if we look at its properties – and I’ll talk briefly about how – what it takes to set this up because it’s not immediately straightforward, if I click properties where am I getting my Internet connectivity from? Update classifications, products, languages, so you might be sitting here thinking, say wait a minute, that looks just like update service, and it kind of is. This is meant to be a subset of that larger update services deployment. It will pull down to VMM whichever updates are approved in update services that match this category. Symon: And I notice that if you go back to the products, right, it doesn’t just have the Microsoft stuff. Corey: No. It’s – again, it’s everything that update services supports. Symon: Very cool, notice Windows Update. Corey: Now, if you’re deploying Windows Live toolbar updates to your hyper-v host I’m going to find you and you’re going to get a visit from my cousin Vinny. With a big stick. But it is pulling it straight down from the update services machine. Symon: A lot of granularity that’s – Corey: Yeah, and so what happens here is the updates are actually stored locally. The binaries, so you’re not pulling the binaries down twice, come out of update services. So this represents a subset of the approved updates in update services that are controlled by the fabric administrator. So that’s what the update server as a component does, connections to vCenter Servers, we’ll talk a little more about this in a little while. But this is where we can establish our connections to vCenter Servers. And then finally other VMM Servers that may be in this pool that we mentioned it’s highly available, this is one of the places that you would have. One of the questions I noticed over break was hey, if this is now highly available, does this mean it has to run on physical hardware? Absolutely not, right, it’s a Microsoft product, they don’t care. Physical, virtual, it doesn’t matter. A lot of people probably will choose to put this on physical hardware because they want to separate the management of the cloud and the fabric from the fabric. Should the fabric fail and take down the VMM it’s kind of hard to fix it with VMM. So there’s certainly, I think, going to be a notion of it’s why you don’t run a DC on the cluster. You may not – you may choose not to run VMM on a cluster, that being said you may choose to run VMM on a separate hyper-v cluster than the one you’re primarily managing. So you might wind up with a primary and a secondary. Symon: So really a lot of flexibility, and you can put it anywhere is the bottom line. Corey: Absolutely.

Продолжение демонстрации (часть 2)
Corey: So what else can we do in here that would be interesting? Let’s look at the properties of an actual hosted self. I’m going to actually start with host 4 here. And let’s do a couple of kind of interesting and slightly risky things. So first of view networking brings up a visible diagram of what the network framework looks like. This is – it was a similar piece of functionality in VMM 2008 R2, if you haven’t looked at it, a lot of people kind of overlooked or omitted this, it actually brings up, shows you the adapters and then shows you kind of the logical networks that they’re connected to. Symon: Nice graphical interface. Corey: Absolutely. And you can see, you notice if I click Corp Lan it lights up the pads back to the VMs. Symon: Very cool. Corey: So I know which logical networks the different VMs are actually connected to. Let’s do this to node 1 real quick. So we’ll click view networking and it’s got perimeter network – Symon: A little different yeah – Corey: Yeah, it’s a little different there and we’ve got corp lan up top. Perimeter network is connected to an adapter, but no VMs are connected to it. This is the virtual switch inside hyper-v. So it gives you a very good graphical look at how things are actually pieced together. So properties of a host. Under hardware, CPU settings, memory settings, all standard, graphic processing, if you have a remote FX capable of GPU, this is where you’ll see it. Network adapters, relevant information, logical networks their associated with, and then finally, this is my favorite, the bare metal configuration settings. Symon: BMC. Corey: All right, so this is – I’ve configured – these are Dell and so I’m using the SMASH protocol, here’s the IP address, here’s the BMC port and I’ve chosen my run as account, which is my Dell IDrac admin. And so what that lets me do is essentially using base port configuration tools to remotely control this Dell server. So watch what we’re going to do here. Let’s go ahead and take a – and let’s go back to our cluster view, let’s take 4 and let’s take this in maintenance mode. Default behavior is running virtual machine in saved state, you support live migration, do you want to live migration, heck yes, so we’ll click live migrate. Symon: Absolutely. Corey: So we just did Host 1, that’s fine. I tested with host 4, so fingers crossed. So we’re going to go ahead and actually let’s – because I want to be safe let’s go, and so host 1 is there, let’s come up and have a look at our VMs, look at the cluster, sort by node name and you can see here that the VMs for host 1, which there are four of them, are actually currently under migration. So one of them is stopped, one of them is under migration. So that’s actually going to take a couple of minutes to do all the live migration. Once that’s done what we’ll actually do is go in and that machine’s in maintenance mode, it’s not available for placement, we’ll go in and we’ll shut it down, pretend we’ve done some hardware management and then boot it back up again using VMM. So that full life cycle of management. So that one’s chugging along quite good, Exchange Server’s migrating, let’s see what we got for RAM on that guy. Move this over here, let’s get rid of some of this data, CPU average I don’t want, operating system I don’t want, and so I’m moving on to the next one which is Service Manager. I want to see what my actual RAM usage is here, 2.5 gig, so they’re chugging along just fine. We do have any questions that are coming in on the – while we’re waiting for this to happen that we can address here real quick? Symon: We do. So let’s see, find a good one, do you know about Vlans here, so what can you do with the Vlans in VMM 2012? Corey: Well you can do the same sort of things that you can do within hyper-v, it doesn’t – it hasn’t changed the functionality of hyper-v. You can still Vlan tag individual switches. This just makes it more automated. Because you can Vlan tag logical networks. For example you can have a logical network that is connected to the same switch, two IP subnets, two different Vlans. They’re all part of the same logical network and it just kind of figures that out for you. So it fully supports all the Vlan tagging and ensuring it’s consistent across multiple hosts or multiple nodes. Symon: Well, the next question I have I’m going to take. Can you live migrate multiple VMs simultaneously or are they migrated serially? So, live migration, the way it works, it copies memory from one server to another. With hyper-v clustering we do live migration of one VM at a time between any pair of nodes. So in a 16 node cluster you can do eight live migrations at the same time between eight different pairs of nodes. Now a lot of people think that hey, that’s not good, Vmware they can do four or eight live migrations at the same time but that’s actually not a good thing to do. You know the pipe is only so thick, right? So if you’re trying to live migrate one at a time, one, one, one, or four at the same time the overall time is going to be the same. But in fact if you’re trying to do four simultaneously you’re actually putting them in a worst state because there’s more processing overhead that happens while you’re actually doing a live migration. You know they’re going to be in this live migration state for longer, so there’s more pages getting dirtied and more memory that’s being changed, and so it’s actually worse to live migrate multiple VMs at the same time between any pair of nodes than just live migrate them serially. And if you are use SCVMM you put a node into maintenance mode, it’s going to have that same functionality where it will live migrate all of the VMs for you, but serially. So you just do that single operation, put the host into maintenance mode, if it has eight VMs it’ll do one, one, one, one, all the way through rather than trying to push all eight at the same time, which may probably take longer because there’s more memory transactions happening. Corey: Exactly. Eight at the same time doesn’t mean that those eight run faster than eight one after the other. Anyone that’s copied files over the network should be able to attest to that. Sorry, my host one is now in maintenance mode, let’s go ahead and power it off. And that’s going to go out within hyper-v itself and this is done at the OS level, it was shut down on the node. And if we go back here and just in my little Dell idrac control center it’s going to do a refresh and within a couple of minutes that’s now a powered off system, right, so we can tell that by actually doing the baseboard management. Go back into VMM, let’s draw some hardware down on the network card, I’m good with hardware, see how quick I did that. Go back to VMM, which is right here, and let’s go ahead and power that system on. So we’re just waiting for it to update, it’s still reporting it running, let’s do a refresh on it real quick. Click refresh, one thing you will typically notice with VMM is that because it’s an agent-based model it’s got to wait for the agent to report back. So it’s not going to be instantaneous. So we’ll click this one, it now identifies the machine’s powered off, click power on, it’s now going to go out and send that power on command back through the iDrac platform. And that’ll take a couple seconds to go back, talk to it, it’s SMASH’ed, there’s a number of protocols, SMASH is a Web services-based implementation. It takes a little bit longer for the initial negotiation. So we’ll click back to iDrac console here, do a refresh, and with a little bit of luck here within about 30 seconds or 40 seconds we’re going to see that machine as powered on. Symon: Now by chance do you know the default polling time between these agents? Corey: You know, I don’t. I did at one stage but I just – I’ve forgotten. I don’t know what the polling cycle is. Symon: No worries. You didn’t design it, so I wouldn’t expect you to. Corey: No, exactly. I know it’s – it’s relatively fast. It is relatively quick. You’re dealing with latencies and maybe 20, 30, 40 seconds maybe a minute at times, which is fine unless you are waiting for something to happen. Then it can seem a bit longer, but you can always force that poll by just doing the refresh. And that’s kind of what I recommend to people, you’re doing it interactively and it’s not displaying the state that you think it should, just do the refresh and it’ll typically be ok. So hit refresh on that there, it’s delaying right now, which usually means it’s going to come back. There we go, so our system’s now powered on. So VMM actually did that. Went out over the IDrac interface, brought the machine back online. And what you’re seeing here is the basis for power optimization as well, where it would live migrate the nodes, power down the system, when load dictated power the system back up, when it was ready live migrate the nodes back on. One of the things that folks were asking about earlier is all this dynamic optimization. Symon: Are you going to show any of that? Corey: I am, because one of the things I’ve noticed with maintenance mode, I don’t know if this is as beta or if this is just the design point on it, but when I take this out of maintenance mode it doesn’t back fill again. And so I suspect it’s because there’s no preferred owner set on the DMs within the cluster. Symon: Right. Corey: So it won’t back fill until the next dynamic optimization cycle. So let’s just kind of briefly take a look at that. The properties of dynamic optimization are on the host group. So in my case cloud cluster, it’s got one cluster, it could have lots of clusters. So if I go into the properties there and I look at this, there’s a lot of things I can do in here. Here’s my placement requirements. When I’m looking at this host group, what are the characteristics that I want to look for in terms of placement? So as I’m choosing the node to put a VM on, do I want to put more weight on networking , drive, load balancing, disks, CPU, what do I want to – what are the most important characteristics? And that’s dictated by the workload of the BMs that you’re actually going to put on these hosts. Resource usage, these are the thresholds that govern when a host is considered to be under pressure. So how much free memory do I have? How much RAM do I have? What’s the CPU utilization? Symon: So how does this tie in with Pro Tips, does System Center Operations Manager, Pro Tips – it does some of, you know, the same kind of analysis. Corey: It kind of – it replaces some of the functionality of Pro. Like the inbox functionality of Pro is more or less replaced by this. It doesn’t replace things like hardware monitoring through Ops Manager, things like application specific load monitoring, where you’re looking at the queue in the Web server. It can’t do that. so the queue in the Web server could trigger a Pro Tip to move the VM. It cannot monitor or manage to that point. Symon: But at a high level it kind of covers the basics, right, CPU, network, disk, memory. Corey: Right, and it’s looking at the host as an entity and then the characteristics of the individual VMs to decide what to move where. This is dynamic optimization. So by default you say, you know, use the host from the parent group. I unchecked it so I could customize it here. And what I’m doing is tell it, you know what, every ten minutes on a very aggressive basis, balance all of this. Now that’s insanely aggressive, I would never do that in a production environment. Symon: Because what you do in these balances, it’s a live migration. Corey: It is, it is, you know, which is – Symon: Network traffic. Corey: You’re moving a VM from one host to another, I’m sorry, I don’t care what you tell me, it’s not without risk. So it’s not something that I choose to do for fun. But certainly in balancing this I may choose to do it once every 6 hours. And then the level of aggression is, you know, ok, how balanced do you want it, like how full does this guy need to be before you try and balance. So in my case I just want this to happen all the time, just for fun right now. So I’ve got these set very, very aggressive. And then optimize power will turn hosts on and off. So as dynamic optimization is able to consolidate it’ll power hosts up. Symon: And this is the power setting that you’ve shown us, so – Corey: Right, for this to work you’ve got to have those bare metal configurations settings in all the nodes. And you’ve got to verify they work. Otherwise it’ll shut it down and go I don’t have to turn it back on again. Symon: A good thing to check. Corey: Yeah, there’s no ability in VMM yet to phone you and tell you. Although you could do something – Symon: We could Opalis that, right? Corey: In fact while we’re – the guys behind the cameras told me yesterday maybe I should tell a joke. So this isn’t a joke but it’s a funny story. Similar sort of thing, right, way back many, many years ago in the days of liquid cool servers. We still have liquid cool servers, but this was back when they were kind of a new thing back in the sort of the mid nineties, SNMP, if you’re familiar with it, sends track alert messages and so a bunch of friends of mine, the three stooges of networking I called them that ran IT for the shop and so they set up these alerts against all these servers to track the consumption, the heat. And being three guys in networking in the mid eighties in their early twenties they named all their servers after their ex-girlfriends. So there were, you know, Sally – Symon: Not Star Wars characters? Corey: No, no, no, no, no, Sally, Mary, Baba, I don’t know. And so they did this and it would page them whenever the server was needing attention. And so one of the guys was having dinner with his current girlfriend, went to the bathroom, pager went off, she picks it up, Sally needs attention. You can guess that dinner didn’t last too long. So yeah, and not relevant to any of this, but it popped into my head. And the power schedule dictates when you would actually do the – would or would not do power consumption, so if you don’t want to do power consumption during business hours you’d simply come in here and go hey, you know, from 9 to 5 Monday to Friday we’re just going to not do any of this stuff and you drag your mouse around a bunch of times and draw little eight bit pictures if you wanted to and just kind of fill up the times you don’t want to do power management. Corey: Network settings, we can see which networks are actually in here, what storage is available and then what run as profiles are available. And so that’s all based on the scope of those objects when they’re created. So by now our host should be up, we can take it out of maintenance mode, so let’s go stop maintenance mode and we’ll update that value and it should actually tell us here pretty briefly that that host is ok. At which point we can kind of take a look at what dynamic optimization is going to do. Symon: All right. Corey: Now rather than wait ten minutes, let’s go optimize hosts. So you can actually force this to happen. And this will take all the load into consideration, all those dynamic optimization settings and go ahead and run the task for you, so we’ll click that, it’s going to go ahead and think, so this may or may not – all right, so it found one and said hey, ops manager 2003 it’s on node 2, node 1 just came up, it’s looking pretty empty let’s go ahead and optimize. And what that’s going to do is if I come down here and if I find that Ops Manager server you’ll notice it’s now under migration. Symon: There we go. And so it’s being live migrated from the busiest server to that brand new server that’s fully evacuated that’s waiting for a workload. Corey: Exactly. Had I waited long enough, something like this, maybe not this exactly, but something like this would have happened. Because that’s the notion of what dynamic optimization does for you. Let’s move along into – you do realize I’m not going to get back to the slide deck, right? Symon: I think so. Corey: All right, I think that’s ok. Symon: I think that’s fine. You’re showing some cool demos, people have been asking for demos for the last two days, so – Corey: Now you have to be careful what you ask for, you just might get it. So if we click on compliance, that’s actually – let’s click on compliance. Here’s my cluster, and oh dear Lord, look, it’s just a little unhappy thing. So my cluster is non compliant, what does that mean, what does non compliant mean? Well non compliant means that it doesn’t have the patches and updates its required to have. Well how do I know what’s missing? If I start drilling down in here, and let’s just kind of go down to node 3, demo baseline, it’s going to show me that, hey, you’re missing an update. And look, it gives me the details on the update that I’m missing. Symon: So it actually pulls down the KB, number, everything like that. Corey: Right. And if you look at this particular baseline, hey I’m missing – missing a whole bunch of these security updates right here and it clicks on the – because it gives me the data back on what that update actually is. So that’s all fine and good, but what are these things, I’ve got just a simple baseline for security updates and demo baseline, what are these baseline entities that we’re talking about? If we go down under library and we go down to the bottom of the library, we’ve got this thing called update catalog and baseline. And so this is the area that I work in to define these compliance nodes. So I click update baselines, and we can see that there are three baselines I’ve created. What I a baseline? Double click demo here, it’s a collection of updates that are required. You get as many of these as you want. So they’ve got a demo security and a demo update and it would be your job as the admin to update these baselines. Symon: And if you click add, that gives you the ability to add – Corey: If you click add I can now search – you know, here’s all the updates that are recognized by VMM, pick the update that I want – Symon: Add that to your baseline and then my baseline will acknowledge it -- Corey: Add that to your baseline, right. And the thing you’ve just got to be aware of is that because you approve an update on update services doesn’t add it to a baseline. So it’s approved, the binary’s downloaded, it’s available but you’ve got to go in and actually update the baseline before you can actually begin to take advantage of that update. And so I’ll come in here and let’s go ahead and look at the assignment bit, so we’ll take that baseline, look at the properties of it, assignment scope and here are the machines that baseline applies to. So, you know, if I only want it in my cluster. Symon: And right now you just have the cluster, so – Corey: Yeah, maybe it’s the hot fix for DPM. Right, what a great way to deploy it. It’s going to require a reboot so it’s a great way to orchestrate that. Let’s go ahead and get this cluster into compliance, shall we? Back to the fabric, compliance view, JS cluster 1, remediate. Symon: So remediate, this is our keyword for deploy the patch in a cycle – Corey: Now you were involved in a little bit of the logic behind some of this stuff, weren’t you? Symon: Yes I was. Corey: So why don’t you tell us about the theory behind how this was – you know, what we’re doing here. Symon: So basically what we’re doing here is we’re going to look in at all of the cluster nodes, you know, were detected, hey, these patches are missing and we’ve got to get them compliant. So there’s really two options that you can do to actually move or handle the VMs that are on each node. The default is a live migration, so that’s going to move a running VM from one node to another with no downtime. You can also choose to save the state of the VM. So if you’re not too worried about keeping that VM up and running, you don’t want to wait for that overall time for the live migration, if you just want to get it patched as quick as possible, you know, maybe there’s a worm out there. Maybe there’s a virus and you’ve just got to get it patched, no problem, you can choose to actually shut down the VMs instead of having them live migrate. Now what it’s going to do, it’s going to move all of those VMs off, it’s going to go ahead and look at the host, deploy the patches and we’re just going to look at the applicability of the patch and say is a reboot required or not? If a reboot is required then it’s going to go ahead and reboot. Once the server comes back online it’s going to do a few checks, it’s going to say first of all was the patch successful. Assuming it was, great. Did the OS come back online, assuming it did, great. And then did the cluster service come back online? You know you don’t want to go and deploy a patch that actually kills the cluster and then go and deploy that same patch on every node in the cluster and ultimately wipe out your whole cluster. Corey: So I’ll let you continue, but this is either going to be the coolest thing ever or the end of the day. Symon: Let’s say it. Corey: So we’ll click remediate and at that point just turn off my mic, start heading for the door and just see what happens. So I want you to continue that train of thought on what’s going on there but I click remediate, but I just want to go back and look at this job that it kicked off here. And this is a doozy right here. So if you kind of look at some of the tasks that are going on – Symon: Wow, there’s a lot going on, huh? Corey: All right, evacuate highly available VMs, they’re starting to migrate some machines, it’s moving virtual machines off of the cluster, and this is going to come on, and you’ll notice there’s a bunch of install updates, you, reboot computer, install updates, start compliance scans, stop maintenance mode, and this is just going to go like gangbusters for as long as it takes to remediate. Symon: That’s right. Corey: The one caveat to this remediation process is it’s not a caveat to remediation, but you’ve deployed patches before, have you ever gotten every single patch in one update cycle? No. Symon: That often depends on the patches, right. Corey: Exactly, exactly right. Symon: You’ve got to install some binaries, they have dependent binaries – Corey: Yeah. So you may find that you want a remediation and it comes back and says I’m still not compliant, I just remediated. Do another remediation, I’m still not compliant. What’s happening is it’s going ok, I’ve now applied all those patches, I’m now able to accept these patches – Symon: Let me check for some more, pull them down, keep it going. Corey: And the reality is you know the first time you remediate your cluster after you install it you’ll probably go through that, subsequent you’re only pulling down the updates for the new cycle so you shouldn’t really have that issue. But I recall the first couple times I did it there I was like why do I got to remediate four times and finally it clicked and I went ok, it’s – it’s patch dependencies. Symon: And you know this is going to download service packs as well as regular patches, anything that you want to put in your baseline. One thing to note, it does patch one node at a time. And this is really just to simplify the core and logic and not over commit any node. You know if you had, if you were trying to patch five nodes at a time, for example, you’d be trying to push all the VMs onto fewer remaining nodes, that could be a concern and then you have to worry about quorum which is our way of maintaining kind of a single consistent view of the cluster. So if do it one node at a time not a problem, you have to plan that you can lose a node at any time in your cluster and still having enough spare capacity. So this has the assumption that, yeah, this node will probably be rebooted, it’s probably going to be unavailable for some time, so we make sure that you still have enough capacity remaining around the rest of your cluster. Corey: Right, and if you start to look at kind of what’s going on here, VMs and services, all my VMs are still here, all my VMs are still running, at least those that I’ve had running. This RDS1 is not one I’ve been using, the server core has been stopped the whole time, but the rest of these guys are all running and happy, they’re just not on node 4 it looks like. Let’s go quickly check and yeah, so four is the guy in maintenance mode right now. So they’re not on node 4, so 4 is the guy that’s now going through patching and rebooting, it comes back up, another one goes to maintenance mode, the VMs move around and this just continues to cycle through all four nodes. I have no idea how long this is going to take, so we’re just going to leave it, we’re going to come back and check it from time to time and just kind of see where it ends up.

Продолжение демонстрации (часть 3)
Symon: Now of course, maintenance mode, this presents – this prevents other VMs from moving to the node, right? Corey: Exactly. Symon: Locking into maintenance mode the equivalent fail over cluster to them is pausing a node, because you don’t want dynamic optimization to kick in while you’re trying to evacuate this node and have more things come to it. So the maintenance mode is just going to make sure that nothing else moves to it. But of course when it’s done with the patching cycle, it’ll be released from maintenance mode and when it puts another node into maintenance mode using dynamic optimization, using all this other movement, it’s going to start moving things to that node that was just patched. Or to other nodes. Corey: So while that’s happening let’s do something else incredibly risky. My goal is to push and push and push until – Symon: Hey, so far so good. Corey: I want to find the break point. Symon: You’re brave. Corey: You know what, I’m not brave, I’m just silly. So into the library. Into the library. The library’s got a lot of new stuff in here. And let’s start, we looked at the baselines, let’s look at profiles and what sort of profiles we have. Now we’ve got – we’ve got, one second, ok, train of thought back on track, we’ve got our – Symon, say something funny – our update libraries, that’s it, ok. All right, I’m with you, I’m with you. We’ve got our updates done so we’ll kind of look at that component of the library. So now let’s look at profiles and in the past there was only really a VM profile, a hardware profile and an OS profile. Now we’ve got a lot more. So let’s kind of dig into what these things are. And let’s start with a SQL profile. It seems like a really bizarre thing to have in a VMM server. But if you begin to change your thought process from deploying a VM to deploying a service in – on a fabric, a service is typically an operating system and a piece of application logic, an application of some sort and storage for that application in the form of the database. So the majority of applications that are going to come in are going to have some element of SQL database involved. You can’t sysprep SQL. You’ve got to install it, right? So I can’t build a VM that has a SQL database in it, I’ve got to add SQL after the VM has been deployed. So that’s why this is here. So I can deploy a VM that is a data layer. And it will deploy the VM, it will actually do an auto unattended install of SQL server once the VM is deployed. So this is very simple, SQL 1, I was going to call it my SQL server, but that probably wouldn’t be a good idea. SQL 1, SQL server configuration, and I’m not going to do all this, but you can see it’s got a name, instance ID product key, run as profile and then within the configuration where the source files are coming from and then essentially an answer file for SQL server. So that after you install Windows it’ll take this and install SQL into it. So that’s as far as we’re going to go with the SQL profile. Host profile, one of my favorites. We talked about bare metal deployment, how does that work? Well, it requires two things, number one, you need a sysprep copy of Windows in the library. So if I go into my library, library servers, VM 2012, here’s my library, here’s my VHDs, I have in here somewhere, I know I do, there you go, so I’ve got a VHD in here which is a sysprep, basically Windows Server 2008 R2 instance, so sitting in a library I’ve got a VHD that I can use. I take that and I combine it with a host profile. Host profile is an answer file for bare metal deployment. Let’s have a look at this hardware configuration. How do I want to do network management? It’s going to be a management NIC that’s going to be DHCP or static IP from the logical network corp Lan. Now if I do static network – static IP from logical corp lan it uses the IP pools that are part of the logical network definition. Disk, master boot record, fully utilized, operating system location, size, what the partitioning scheme is, and then drivers. Right? If you have a driver pool for this hardware sitting on a file share it will actually go out there in the library and grab all the drivers installed. Symon: Nice. Corey: So it’s a full bare metal deployment, OS configuration, typical stuff, host settings, which is where the virtual machines are going to be deployed. So what that allows me to do is this, back to my fabric, add resources, hyper-v hosts and clusters, physical computer provision into hyper-v hosts. Click next, run as account, idrac admin, protocol, I’m going to choose SMASH, where will I find my bare metal machines that have had their bare metal network cards configured, to are my four cluster nodes. And it’s now doing a scan. So what this is actually going out and doing is taking that IP range and then attempting to contact the baseboard configuration on that server. And so we’ll see here that briefly, in a moment or two, it’s actually going to find it, come back and let us deploy an operating system down onto that. Now unfortunately I can’t do anything else while, so we’ve just kind of got to wait for this. Symon: Well in the meantime that was a question, you know, you mentioned one time earlier that application profile, what exactly is that? Corey: An application profile is a couple of different things. It can be a Web deploy package, an MSI package, a server and v package or a dat package, which represents a packaged application that gets added into the operating system after the fact. So if you think of a typical three tier application you might have – and I’ll try and conceptually explain this. Servers sitting on the perimeter and external network that represent Web servers. Servers sitting on the perimeter network that represent middle tier servers and servers on the internal network containing data. So that’s three templates with an MSI package of the Web site, a – maybe an app server and v package of the application layer and a SQL install for the data layer and it will build that entire infrastructure for you. And drop the VMs, install the OS, install the application, bring it online, plug it into the right network, add the right IP addresses in, connect it to the right switches and you’re ready to go. Now, sounds like a piece of cake, it’s not – you know, it’s not the sort of thing you’re going to click twice and have done. There’s a bit of design work involved and planning work involved, but it’s all there. So here’s an example, it’s found two of those nodes already, click next, host profile, which is the one I just showed you, which is bare metal hyper-v. Give the machine a name. Bare server and that’s as far as I’m going because I don’t want to redeploy my node. Symon: Makes sense. Corey: I’m crazy but I’m not that crazy. But this is what you would essentially do, you know, you get a new rack rolled in, your manufacturer’s preconfigured this data, you know the IP address range that all these machines are configured on, you know the admin password, you can tell it, hey, go find everything, drop an OS on it, and I’m not kidding you that when I first got the beta I said yeah, this won’t do it. This sounds great, let’s try it, 24 servers in about two hours and I literally sat here for 10 minutes and went go, came back a couple of hours later and I had a UI full of agents. I just about fell over. It was just – Symon: Isn’t it nice when software works like it should? Corey: It is. It realy is. It’s an interesting concept, people should start embracing that a whole lot more I think. Let’s go back and check our compliance here and see how we’re doing, let’s go back to that job and we’re kind of – we’re still moving along here. Let’s see if we’ve moved to – moved to another node yet. Let’s go back to the fabric, fabric resources, all right, so around to host 2. So one is completed, three is completed, two is in maintenance, four failed, that’s interesting. To job status fail, four is ok, completed. Let’s come back and check and see what’s going on here over the break. So we’re just going to let that continue and see what happens. There’s no – there’s been no failures yet in the job, so this might be just a timeout that’s happening. Because everything here is looking healthy and happy. Oh I see what’s going on, because of the maintenance mode some of the refresh jobs are failing, that’s what the fail status actually comes from. Symon: Ah, ok. Corey: So we go back to compliance, so we’re still – two is in maintenance mode, I think one might be done. We’ll just have to wait and see what happens. All right, so we’re getting to the point where we need to take a break. I’m going to one other topic before we take a break, and this is one I know that’s going to be of interest to a lot of people. So we’re going to actually flick back to the slide deck of this and actually advance quite a bit through the slides and talk about, specifically, interoperability between Xen server and ESX. Symon: So you’re going to want to get into the 30s. Corey: Into the 30s, all right, so just bear with me for one sec while I skip all this stuff that I explained to you. Symon: Yeah, it’s way better showing it in person than in a PowerPoint. Corey: It is, and if you guys want to flick through the slides, certainly fire the questions off, by all means go ahead. So we’re almost there. Here we go.

CSV, доступные диски Доступные диски Доступные диски хранилища
Кластер1 CSV, доступные диски Выде-ление хранилища Назна-чение хранилища Выделенное хранилище Доступные пулы хранилища Общее хранилище Узел1 Группы узлов Доступные диски

ВМ Диск храни-лища VHD Узел VHD Узел SAN SAN SAN
Профиль ОС Шаблон VM SCC Диск храни-лища VHD Профиль оборудования Мастер создания шаблонов Мастер создания ВМ VHD поддер-живает копирование SAN (SCC) Узел VHD Узел Массив поддерживает моментальные снимки и клонирование Массив создает копию с помощью функции моментальных снимков или клонирования SAN SAN SAN

Автоматизация хранилища — миграция ВМ на базе SAN
Миграция на базе технологий iSCSI и FC Миграция iSCSI Маскировка и демаскировка Вход и выход инициатора Миграция FC Удаление и создание виртуальных портов NPIV

Управление узлами в VMM 2012
Любой узел ВМ, не только Hyper-V Добавление узлов ВМ в VMM Управление свойствами узлов ВМ Мониторинг состояния агентов ВМ Развертывание узлов на системах в исходном состоянии

Поддержка нескольких низкоуровневых оболочек
SCVMM 2007 Virtual Server 2005 R2 SCVMM 2008 RTM Hyper-V RTM ESX 3.x SCVMM 2008 R2 SP1 Hyper-V R2 Hyper-V R2 SP1 ESX 4.0 (с ог-раничениями) SCVMM 2012 Hyper-V RTM Hyper-V R2 Hyper-V R2 SP1 ESX 3.x ESX 4.1 Citrix XenServer

Управление ESX

Управление ESX — интеграция с vCenter 4.1
TechReady12 9/16/2018 Управление ESX — интеграция с vCenter 4.1 Древовидная структура центра обработки данных vCenter не импортируется Добавление узлов и кластеров в любую группу узлов Поддержка учетных записей с пониженным уровнем прав в vCenter SCVMM vNext vCenter SCVMM 2008 R2 Corey: So a few things that we’re doing in here around ESX and Xen Management. So a couple things, first of all the vCenter data center tree structure is not imported. You can actually take all those VM – those ESX servers in 2008 R2, you can preserve the tree structure in VMM 2012, you can organize them however you want. So you organize them, they’re in vCenter organized, but you can actually reposition them – Symon: Reorganize them, and then that’s set back to – Corey: Well it’s not going to change what’s in vCenter. But it’s going to – you just get to view them the way that you’re interested in viewing them. So it doesn’t force you to have the same structure in both locations, you can actually have a different structure in both locations. Add host and clusters to any host group and support for using less privileged accounts in vCenter. [this text was already here, not part of presentation audio transcript] Integration with vCenter 4.1 vCenter 2.5 support removed vCenter API interface is not backwards compatible Support for ESX 3.x and ESX 4.1 Support for distributed vSwitch and port groups Integration with on-board management controller © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Управление ESX — шаблоны VMware
Шаблон в библиотеке Обнаружение и использование VMDK в библиотеке для создания шаблонов Импорт шаблонов Импорт метаданных объекта шаблона vCenter в библиотеку VMM VMDK не копируется в библиотеку VMM Шаблон не удаляется в vCenter В новом рабочем процессе ВМ для копирования VMDK используется vCenter (ускоренное развертывание) Corey: For templates you can actually scan discover VMDK disks in the vCenter library. And you can import those templates over into hyper-v as well, into VMM. It’s not going to take the disks with it, it’s not going to remove the template, but it allows you to migrate that work and template design into VMM quickly and easily. It’s not going to destroy anything, it’s not going to bring the disks with it. Symon: And that’s great, keep that consistency or keep those templates that you’ve got up(?).

Управление VMware — управление ВМ
TechReady12 9/16/2018 Управление VMware — управление ВМ Виртуальный диск после тонкой подготовки в шаблоне и ВМ Отказоустойчивость Обнаружение и использование основных ВМ Миграция в библиотеку отключена Отсутствует поддержка создания ВМ FT Обновление аппаратных характеристик ВМ в соответствии с используемой платформой Corey: So you can actually use thinly provisioned V disks when you’re dealing with Vmware. It will discover and utilize the fault tolerance, it will actually integrate with the fault tolerant features in Vmware and it will update any relevant hardware properties that match the platform the VM is defined at. [following text was here already, not part of video presentation] FT: Secondary VM is ignored until it becomes primary VM configuration version 4 and 7 Memory 255GB maximum No support for setting reservation, maximum, or shares CPU 8 vCPU maximum SCSI BusLogic, LSILogic Parallel, LSILogic Serial, PVSCSI VMXNET Flexible, E1000, VMXNET2, VMXNET3 © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Управление ESX — миграция ВМ
TechReady12 9/16/2018 Управление ESX — миграция ВМ Поддерживаемые типы переноса VMware Динамическая миграция Миграция динамического хранилища Поддерживаемые типы переноса VMM Миграция по сети в библиотеку и из нее Примечание: диски с тонкой подготовкой становятся ТОЛСТЫМИ Миграция по сети между узлами Поддерживаемые механизмы копирования Собственный протокол HTTPS VMware Отсутствует поддержка SFTP (не требуется включать корневой SSH) Требуются учетные данные корневого уровня Corey: In terms of transfer types, live migration, live storage migration are all supported. You can do network migration to and from the library and supports two copy mechanisms, native https and also – sorry, doesn’t support SFTP. So those are all supported. You still require the root credential for some of those key copy operations. [text was already here] Datastores Discover and use datastores for VM deployment No datastore management (add, update, remove) ESX host/cluster Discover, import, and use ESX host/cluster for VM deployment No host agent management (add, remove) © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Преимущества поддержки XenServer в VMM
Управление всеми низкоуровневыми оболочками в центрах обработки данных Более широкий выбор для гостевых систем Linux в дополнение к возможностям, поддерживаемым технологией Hyper-V Возможности VMM применяются в среде XenServer Corey: Xen server, one thing, this is obviously new so it’s sort of been exciting for a lot of people. Citrix worked with Microsoft to develop the agent that goes in Xen server, so it’s a very rich aid and you’ll find there’s a lot of support here. Because it was a kind of cooperative development to that agent, and it also supports the para virtualization features that are in Xen. So if you have pair virtualized guests, VMM can actually see those in there. It can’t deploy them, but if they’re there you can actually work with them and interact with them.

Серверы Citrix XenServer
У VMM отсутствуют зависимости с Citrix XenCenter Пакет интеграции Hyper-V Установка Сервер SCVMM 2012 Серверы Citrix XenServer Citrix XenCenter Corey: So the way this works you have the Xen server, you install something called the integration pack. Sorry. You install something called the Xen Server Integration Pack, which is basically a WMI provider for the Xen server that SCVMM can then talk to. Xen Center is not required. In the beta the only kind of hard requirement that you have is that the host name that’s on the certificate, the self-signed certificate that Xen Server creates for itself that SSL cert, has to exactly match what you added in VMM. So if it’s just a host name all lower case that’s what you use in VMM. And that’s meant to be, that’s going to be further refined towards the release, but for now there’s that requirement that if you try to add it it’s going to fail saying the certificate was invalid, you’ve got to make sure those host names that you’re adding in VMM and the value of the certificate in Xen Server match perfectly. From there it can actually do a lot of work with Xen Server. Symon: Sounds great, so I think we’re covering we manage hyper-v, we manage Vmware, we manage Xen, pretty much everything. Библиотеки SCVMM 2012 Репозитории хранилища

Управление XenServer Управление узлами
TechReady12 9/16/2018 Управление XenServer Управление узлами Настройка узлов выполняется за пределами VMM Автономные узлы и узлы в пуле Управление энергопотреблением Отключение и включение (если оборудование поддерживает OOB), перезапуск Режим обслуживания Corey: Yeah, so in terms of Xen, here’s a few of the things you can do. Well stand alone and pooled hosts are manageable so essentially they’re implementation of clustering. Power control through the – those same out of box capable hardware, so you can do a restart, you can do a shutdown then reboot, power on with those OOB providers, supports maintenance mode for the Xen servers. [text already here] Not Supported Cluster Creation, OS Deployment © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Управление XenServer Узлы: хранилище
Поддержка всех репозиториев виртуальных дисков iSCSI, NFS, HBA, StorageLink Общие и локальные Все хранилища должны добавляться на сервер XenServer за пределами VMM ISO-репозитории NFS или CIFS ISO-репозиторий должен поддерживать доступ на чтение и запись Поддерживается только подключение ISO- файлов из библиотеки VMM Corey: All the disk repositories that Xen has are fully supported and recognized as well as ISO file repositories.

Управление XenServer Узлы: сеть
Различия между виртуальными коммутаторами Hyper-V и XenServer Маркировка VLAN выполняется на физическом уровне сетевых псевдоадаптеров Отдельный коммутатор для каждой VLAN VMM помещает все коммутаторы XenServer на одном физическом адаптере в единый виртуальный коммутатор Corey: In terms of networking, the only thing that’s a little bit different in here is within Xen Server they will create a lot of switches representing different network configurations, within SCVMM they will create one switch that represents the entire configuration. So there’s a little more granularity that Xen server does in its implementation and the way that they decided was the best way to do this was it’ll be one switch within VMM that’s represented within – in VMM, it doesn’t change the implementation of Xen, but the way it’s represented, you’ll see one switch where in Xen there will be multiple. It will all be logically plugged into that one logical switch within VMM. Again, it’s not going to go change the switching structure in Xen, it just represents it kind of as an aggregate as opposed to individual units. Физический коммутатор Физический адаптер Псевдоадаптер (VLAN) Виртуальный коммутатор Виртуальный адаптер ВМ Виртуальный коммутатор VMM Сеть 0 (без марк.) xenbr0 Магистраль-ный порт 1, 2, U ВМ1 VLAN1 NIC eth0 Магист-ральный режим VLAN1 VLAN2 Сеть 1 (VLAN1) xapi6 ВМ2 VLAN2 Сеть 2 (VLAN2) xapi7

Управление XenServer Управление ВМ
Поддерживаются ВМ в режимах виртуализации PV и HVM Windows работает только на ВМ в режиме HVM VMM создает ВМ в режиме HVM только с нуля Доступны стандартные параметры ВМ Используются VHD-диски Без дисководов для дискет, без COM-портов Действия Запуск, остановка, сохранение состояния, пауза, отключение Контрольные точки Новые возможности для работы с контрольными точками в XenServer Гостевой доступ к консоли Интеллектуальное размещение и динамическая оптимизация Динамическая память не поддерживается Corey: Some VMM management, para virtualized and hyper visor virtualized VMs are supported, checkpoints, which are essentially snapshots, which were kind of redone in the latest releases of Xen to be more comparable to what’s on VMM and hyper-v. Guest console access, intelligent placement optimization, dynamic memory for Xen is not supported, all your basic VM actions are supported.

Управление XenServer Шаблоны ВМ
XenServer поддерживает шаблоны VMM Обобщение и настройка только ВМ на платформе Windows Citrix Tools для работы с ВМ устанавливаются вручную Шаблоны XenServer Не используются VMM Для импорта в VMM: создайте ВМ с помощью XenCenter создайте шаблон VMM на базе этой ВМ Свойства PV сохраняются Corey: VM templates are supported. I’m not going to get into all the gory details, but you can use the same templating structure within VMM as you can use with Xen Center and it’ll honor that and use it.

Развертывание исходной версии системы
TechReady12 9/16/2018 Жизненный цикл узла ВМ Обнаружение Развертывание исходной версии системы Добавление узлов Создание кластера Мониторинг ресурсов Удаление ресурсов Corey: So yeah, so that’s right here, by the way, is the slide that talks about how we do bare metal deployment. So we’re not going to get there, so at this point I think what we’re going to do is take a break, we’ve I feel pretty much covered a lot of VMM We’ve got 2 now that’s being updated, so we’ve done a lot with VMM 2012, we’ve gone through a lot of the different elements that are in the UI. If you feel like there’s a lot we haven’t touched on, there is. There is a lot more there – Symon: There’s a ton, yeah. Corey: We’re going to do more of this in the next section, specifically around these areas right here, so clouds and services is kind of the next bit we’ll do on VMM when we come back from the break, so let’s take a break here. Symon: And we’ll see you in ten minutes. [text was already here] Refer to 2008 R2 at beginning © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Жизненный цикл узла ВМ Основные задачи, решаемые системой VMM 2012
Управление по вспомогательным каналам Управление компьютером без ОС с помощью BMC-контроллера Развертывание ОС Подготовка ОС с использованием технологии на компьютере без ОС Создание кластера (BD07) Полностью автоматизированная процедура создания кластера Hyper-V

Управление по вспомогательным каналам (OOB)
Обнаружение и составление перечня оборудования SMBIOS GUID Основные параметры устройств (изготовитель, модель, идентификатор ресурса, серийный номер и т. д.) Управление состоянием электропитания: запрос, включение отключение Сбор журналов системного оборудования Доступны следующие сценарии: Развертывание на компьютере без ОС Динамическая оптимизация и оптимизация энергопотребления

Интерфейсы OOB-управления
Стандартные (встроенные) SMASH через WS-MAN (не CLP) Архитектура управления системами для серверного оборудования (SMASH) IPMI/DCMI Интерфейс интеллектуального управления платформой (IPMI) Интерфейс управления центром обработки данных (DCMI) Расширяемые Интерфейс поставщик конфигурации

Поставщик конфигурации OOB Пример интерфейса: Powershell
function PowerOff-MyBMC { [System.Management.Instrumentation.ManagedNameAttribute("DataCenterManager. OOB.PowerOff")] PARAM ( [CmdletBinding()] [parameter(mandatory=$true, ParameterSetName="DataCenterManager.OOB.PowerOff")] [System.Management.Automation.PSCredential]$Credential, [string]$Address, [parameter(mandatory=$false, ParameterSetName="DataCenterManager.OOB.PowerOff")] [string]$Port ) # Здесь находятся команды для отключения питания }

Развертывание на компьютерах без ОС Задача
Обнаружение компьютеров без ОС и их полная подготовка с поддержкой Hyper-V

5. Запуск GCE и настройка разделов 3. Авторизация загрузки PXE
1. Перезагрузка OOB 5. Запуск GCE и настройка разделов Сервер VMM 3. Авторизация загрузки PXE Сервер WDS 2. Загрузка с PXE contoso Сервер без ОС 8. Настройка и ввод в домен 4. Загрузка WINPE 6. Загрузка VHD Сервер Hyper-V 9. Активация Сервер библиотеки 7. Установка драйверов Профиль узла Драйверы VHD

Развертывание Hyper-V на компьютере без ОС Сервер PXE
Сервер развертывания Windows (WDS) на платформе Windows Server 2008 R2 Установка поставщика и агента OSD-файлов VMM Параллельное существование с другими поставщиками Ответ на PXE-запросы от VMM Развертывание WinPE

Развертывание Hyper-V на компьютере без ОС Профиль узла
VHD в библиотеке Драйверы устройств в библиотеке Логическая сеть для статических IP (Необяза-тельно) GCE Схема разделов диска Параметры ОС Профиль узла

Развертывание Hyper-V на компьютере без ОС Мастер добавления ресурсов
Обнаружение Подсеть Диапазон IP-адресов Выбор Профиль узла Группа узлов Настройка развертывания Имя компьютера Для статического IP Выбор NIC канала управления Назначение IP — из логической сети

Высокая доступность Функция доступна с версии VMM 2008
Обеспечивает высокую доступность ВМ и упрощает их миграцию VMM 2007 Без поддержки кластеров Виртуальный сервер VMM 2008 Добавление и удаление кластеров Создание и удаление высокодоступных ВМ Миграция: быстрая, ЛС Повышенные обязательства Hyper-V и VMware VMM 2008 R2 Общие тома кластера Миграция: динамическая, SAN Миграция внутри кластера CFS и хранилище от независимых поставщиков Hyper-V R2 VMM 2012 Создание и удаление кластеров Кластеры недоверенных доменов Кластер с невысодоступными ВМ Высокая доступность для сервера VMM Citrix XenServer

Новые возможности Высокодоступный сервер VMM Виртуальные машины
TechReady12 9/16/2018 Новые возможности Высокодоступный сервер VMM Сервер VMM с поддержкой кластеров Можно реализовать защиту от сбоев ОС и VMM Консоль администратора с алгоритмом повторного подключения Виртуальные машины Создание невысокодоступных ВМ на кластеризованных узлах Создание и удаление высокодоступных ВМ в кластерах Citrix XenServer XenMotion Кластеры узлов Добавление и удаление кластеров Citrix XenServer Добавление и удаление кластеров Hyper-V в недоверенных доменах Создание кластеров Hyper-V © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Кластеры узлов Создание Управление Удаление Создание с помощью мастера
TechReady12 9/16/2018 Кластеры узлов Создание Создание с помощью мастера Автоматическая проверка кластера Выделение дисков для кластера, если VMM управляет хранилищем Создание виртуальной сети в кластере Только для узлов WS08 R2 Hyper-V в доверенном домене Управление Добавление и удаление узлов, дисков кластера и виртуальных сетей Удаление Некластеризованные узлы управляются как автономные Демаскировка диска кластера, если VMM управляет хранилищем © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Мастер создания кластеров

Управление обновлениями
Новая функция VMM 2012 Обновление серверов структуры Windows Включение функции Настройка базовых показателей Сканирование серверов Исправление серверов Управление исключениями

Активация функции управления обновлениями
Настройка сервера обновлений на сервере VMM Требует существования выделенного корневого 64-разрядного сервера WSUS 3.0 SP2 Требует наличия консоли WSUS на сервере VMM (для удаленного сервера WSUS) Поддерживает WSUS в режиме SSL VMM загружает каталог обновлений с сервера обновлений Синхронизация каталога по требованию VMM направляет серверы структуры на правильный сервер обновлений Настройка агента WUA на каждом сервере структуры

Настройка базовых показателей
TechReady12 9/16/2018 Настройка базовых показателей Создание базовых показателей Логическая группировка обновлений для оценки степени соответствия Для образца наборов показателей для обновлений системы безопасности и критических обновлений Назначение базовых показателей Выбор серверов для оценки соответствия Можно назначать: Узлам, группам узлов и кластерам узлов Ролям сервера VMM: сервер библиотеки, сервер PXE, сервер обновлений, сервер VMM НЕЛЬЗЯ назначать: Виртуальным машинам (запущенным или сохраненным), VHD-дискам в библиотеке 1. VMM automatically approves the update in WSUS when any baseline containing that update gets assigned to a server © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Сканирование и исправление
TechReady12 9/16/2018 Сканирование и исправление Сканирование Проверка соответствия сервера назначенным базовым показателям Соответствие на уровне обновлений, а также на уровне базовых показателей VMM использует WUA для оценки применимости и соответствия Сканирование выполняется по требованию и автоматизируется средствами PowerShell Исправление Обеспечение соответствия сервера путем установки отсутствующих обновлений Ход установки обновления отслеживается в консоли VMM Исправление выполняется по требованию и автоматизируется средствами PowerShell © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Представление соответствия

Исправление кластера Hyper-V
Координируемый рабочий процесс Перевод узла в режим обслуживания Эвакуация узла с помощью динамической миграции Пользователь может переопределить эту настройку и сохранять состояние ВМ на узле Установка отсутствующих обновлений на основании назначенных базовых показателей Вывод узла из режима обслуживания Переход к следующему узлу и повтор Поддержка WS08, а также кластеров WS08 R2 Автоматизация средствами PowerShell

Управление исключениями
TechReady12 9/16/2018 Управление исключениями Исключения Исключение сервера из одного или нескольких обновлений Устранения неполадок без ущерба для соответствия Исправление разрешено только для серверов, не относящихся к исключениям Устранение фактора человеческой ошибки Исключения добавляются и удаляются по требованию © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Динамическая оптимизация
Новая функция VMM 2012 Балансировка использования ресурсов в кластере Динамическая миграция позволяет избежать простоя ВМ Operations Manager не требуется Поддержка кластеров Hyper-V, VMware и Citrix XenServer

Ресурсы Оптимизация использования процессорных ресурсов, памяти, дисковой подсистемы и сети Оптимизация запускается при превышении уровнем использования ресурсов порога динамической оптимизации Ручной и автоматический режим По умолчанию используется ручной режим Задаваемая польователем частота По умолчанию частота составляет 10 минут Настраиваемая интенсивность Больше интенсивность = больше миграций = лучше баланс По умолчанию интенсивность невелика

Оптимизация энергопотребления
Расширение возможностей динамической оптимизации Включается только для динамической оптимизации в автоматическом режиме Ресурсы Объектом являются те же ресурсы, что и при динамической оптимизации Оптимизация запускается при падении уровня использования ресурсов ниже порога оптимизации энергопотребления Задаваемое пользователем расписание Время дня для оптимизации энергопотребления Выключение и включение Эвакуация узла перед отключением Гарантия того, что эвакуация не приведет к превышению другими узлами порога оптимизации энергопотребления Гарантия того, что отключение не приведет к нарушению требования к кворуму кластера Отключение и включение с использованием средств управления по вспомогательному каналу

Оптимизация энергопотребления

Моделирование и обеспечение виртуализированных служб в VMM 2012
Microsoft Management Summit 2011 9/16/2018 2:47 PM Моделирование и обеспечение виртуализированных служб в VMM 2012 Good Afternoon. My name is Nitin Bhat and I am a Program Manager in System Center Virtual Machine Manager team. There is quite a bit of content and demos. So please hold on to your questions until we get to QnA, towards the end of the session © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

TechReady12 9/16/2018 Преимущества служб Управление многоуровневыми приложениями на разных серверах как единым узлом Масштабирование по требованию Возможность совмещать ОС и приложения, что позволяет пользователям управлять меньшим числом образов ОС Services help you to model and manage multi-tier applications across a group of machines as a single unit. Services help you to handle peak load for your application, by enabling automatic or manual scale out. Services give you the ability to compose OS images and applications dynamically at deployment time. This allows you to manage fewer OS images and this can lead to significant savings. © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Службы в VMM 2012 Шаблон Экземлпяр
Отправная точка для создания служб и источник данных Определяет требования к компьютерам и подключениям Развернутые службы всегда связываются с соответствующими шаблонами Обслуживание экземпляров Шаблон Группы компьютеров, работающих вместе Включает определения компьютеров, а также приложения Собственные типы приложений: Веб-приложения (веб-развертывание) Виртуальные приложения (серверный пакет App-V) Приложения для работы с БД (SQL DAC) Экземлпяр Service is a deployed instance of collection of VMs with applications, OS roles, features that provide a service to end customers. Ex- 3 tier app (Web based app with a database with different parts of app in different VMs) How do we define what is included in a service? enter Service template Today in VMM, creating a VM from a VM template is a fire-and-forget operation, once the VM is created it has no relation whatsoever with the VM template it was created from. Service is always linked to its template. This way you have a central location holding the intent or the truth and less chance of different instances drifting from the desired configuration. Enable servicing- If you need to update a deployed instance of the Service, you need to first create a new version of the service template, associate it with an already running instance and then just update the instance to match the new version of the template

Управление жизненным циклом служб
Создание шаблона Настройка развертывания Развертывание службы Обновление шаблона и его применение к службе Here is the typical Service Management Lifecycle in VMM 2012. You always start by creating a service template. Then you can use this template to deploy a service. During the deployment process you will be able to preview and customize the deployment. Once you are ok with the preview, you can go ahead and deploy the service. And on an ongoing basis you can keep updating the deployed service until the end of life. We will go into more details on each of these steps over next set of slides.

Создание шаблона обслуживания
Настройка разверты-вания Развер-тывание службы Обнов-ление службы Шаблон является отправной точкой Шаблон создается в новом конструкторе служб Определение компьютеров и возможностей их подключения Уровни, оборудование, логические сети, ОС, приложения, шаблоны подсистемы балансировки нагрузки и т. д. Развернутые службы всегда связываются с соответствующими шаблонами Как правило, информация (например, об узлах или подсистемах балансировки нагрузки) недоступна на этапе создания шаблона Typically when you are creating a service template, deployment specific information like hosts and load balancers is not available – you just know you need a host for the VM or a load balancer for the service but don’t know or care if it is Microsoft Hyper-V host vs. VMware ESX host or F5 Big IP load balancer vs. Citrix Netscaler load balancer.

Новинка! Конструктор служб
Лента Окно конструктора This is a screenshot of the new VMM Service Designer. It gives you a simple drag and drop interface for defining and deploying new Services. Ribbon at the top provides the list of actions that can be performed in the designer In the canvas here, you are looking at the Service template for a Petshop service that has 3 tiers – Web Tier, Middle Tier and SQL Tier. All the tiers are connected to a logical network called Redmond. Details pane at the bottom provides the property settings for the selected object in the canvas. Свойства

Шаблон обслуживания и экземлпяр службы Одноуровневая служба
Экземпляр службы Экземпляр службы VM Template OS Hardware Configuration Приложение Роли и функции ОС ОС Аппаратная конфигурация Шаблон ВМ WS08 R2 Machine01 WS08 R2 Серверный пакет App-V Компьютер02 .NET 3.51 Серверный пакет App-V .NET 3.51 WS08 R2 Компьютер01 Развертывание Let’s take a quick look at simple single tier service template and an instance created from it. If you have a VM template that has the OS/hardware information, you can create a Service Template with this VM template to deploy a Service with one or more instances of the machine. As a next step, you can imagine adding roles/features and applications to the Service definition and deploying a Service that can have one or more instances by default, and can choose to mark it as scalable. This gives a high level idea of how you can build on your existing knowledge of VM templates to author and deploy services.

Компоненты шаблона обслуживания
Шаблон обслуживания Параметры Шаблон подсистемы балансировки нагрузки Уровень компьютеров (1..n) Профиль узла приложений (1…n) VHD-диски Шаблон ВМ Профиль приложения Профиль оборудования Профиль гостевой ОС Профиль SQL Разверты-вание SQL DAC GCE до и после установки Профиль приложения Before we dive deeper into service deployment, let us look at all the components that make up a Service template. As most of you know VM templates, let us start there. VM templates contain the Hardware definitions, OS definitions and VHDs. Computer Tiers consists of exactly one VM template. There can be one or more Computer Tiers. Service Template consists of one or more computer Tiers. VM Templates has one application profile which in turn has one or more application deployments – MsDeploy, SQL DAC or Server App-V packages. Application deployments always have references to the application bits in the library. You can have your custom EXEs run during application deployment. This might be for installing your MSI packages, or maybe to enable a firewall rule. In the Guest OS profile, you can define what Roles/Features need to be installed VM template can also contain a SQL profile, for installing a SQL server instance in a sysprepp’ed VM. This consists of one or SQL deployments that can have SQL scripts and library resources for the SQL scripts. Load Balancer Templates can be setup for each computer tier that needs to be scaled out. In an Enterprise environment it is very typical that SQL databases are deployed to existing physical SQL servers. In order to support this scenario, Service template can contain one or more host profiles for deploying SQL DAC packages to existing physical servers. Any settings that need to be overridden as a part of Service deployment are available at the Service template level as Service settings. Разверты-вание приложений (1..n) Роли и функции Разверты-вание SQL GCE до и после установки

Настройка развертывания
Создание шаблона Настройка разверты-вания Разверты-вание службы Обнов-ление службы Настройка развертывания Подготовка шаблона к развертыванию Настройка параметров ОС Имя компьютера, пароль администратора и т. д. Настройка параметров приложения Например, строка подключения SQL Использование одних и тех же шаблонов в разных средах Разработка, подготовка, эксплуатация и т. д. Let’s say that you have created a service template using the service designer and you are ready to deploy the service. You need to select which Cloud or Host group, you want the service to be deployed to. VMM will run the intelligent placement algorithm for placing multiple VMs in the service on the most appropriate hosts in the host group or cloud in the environment - this will be based on VM requirements and available host resources. When the target is a host group, you will be given a preview of each VM in the service and the suitable host it be deployed to. And as part of customizing the deployment, you can choose a different host if you need to. When the target is a Cloud, hosts are hidden from the preview and you can customize any of the settings for the deployment or change some of the VM properties. Ability to provide overrides as a part of Service deployment enables you to author a Service Template once and deploy it to multiple environments – test, dev, production etc, without having to change the Service Template for each environment.

Предварительный просмотр развертывания
Создание шаблона Настройка разверты-вания Разверты-вание службы Обнов-ление службы Предварительный просмотр развертывания Развертывание службы Развертывание в облаке Переопределяемые параметры This is the Service deployment preview in VMM. You can see that this Service has been deployed to the Seattle Test Cloud and none of the host information is shown. Setting values, like database name, connection string etc that need to be provided as a part of deployment can be provided here as shown.

TechReady12 9/16/2018 Создание шаблона Настройка разверты-вания Развер-тывание службы Обнов-ление службы Для служб Для компьютеров Для гостевых ОС Для приложений Выбор уровня исходя из порядка развертывания Создание новой ВМ из шаблона Включение и ожидание ВМ Установка гостевого агента VMM GCE уровня профиля приложения до установки GCE приложения до установки Установка приложения Once you have customized and you are happy with the preview, you can go ahead and deploy the service. Tier is selected based on the deployment order of the tier. For each machine in the tier, VMM will copy all the VHDs, apps, scripts etc. to the destination host. It will create VMs, customize the OS and install a guest agent that will be used for app deployment, OS Roles and Features Once the guest agent install is complete, OS roles, features are installed and any custom EXEs provided will be run before app installs followed by the installation of the application. VMM will then run the post install EXEs for the machine and once that is complete, the machine will be added to the Load Balancer. This process is repeated for each of the tiers Встроенный этап GCE уровня профиля приложения после установки GCE приложения после установки Готово Добавление в подсистему балансировки нагрузки Выполнение стандартной команды в гостевой ОС © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Новинка! Развернутая служба (схема OpsMgr)
Служба Уровни компьютеров Экземпляр ВМ Once a service is deployed, here is a typical layout of what a deployed Service diagram looks like in OpsMgr. This layout is for a Petshop service that I will be covering in my demos. Petshop service has 3 tiers Web Tier, Mid Tier and a SQL Tier. This Service Diagram is generated as the Service is being deployed in VMM. Параметры ВМ

Процесс обновления TechReady12 9/16/2018
Связанные шаблоны компьютеров Обновление шаблонов компьютеров Тестирование нового экземпляра службы 4 Обнов-ленный экземпляр службы 2 Исходный шаблон обслужи-вания Обновленный (новая версия) шаблон обслуживания Ожидающий шаблон обслуживания So let’s walk through how updating a service works. Once the application has been deployed, either the application has to be updated or the OS has to be updated or the machine characteristics have to be updated. Remember, a deployed service is always linked to the service template it was created from. Service templates contain all the VM template definitions. Updated app or the OS image has been updated outside of VMM, is added to the library You need to make a clone of the service template and the VM template to point to the new application or VHD Then you associate this new template with the deployed service that you want to update Test this configuration in the a test environment During the service (or maintenance) window you can update the service to match the new version of the template. 3 Установка обновленного шаблона Исходный экземпляр службы 5 Развертывание обновления в окне обслуживания Исходный экземпляр службы © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Типы обновления Обычные обновления Обновления образов
Создание шаблона Настройка разверты-вания Разверты-вание службы Обнов-ление службы Типы обновления Обычные обновления Изменения в параметрах шаблона применяются без замены образа ОС Пример: изменение параметров памяти и обновление приложений Обновления образов Замена старого образа ОС новым Переустановка приложений и восстановление состояния (например, переход с WS08 на WS08 R2) VMM will support two types for updating a service – regular updates and image based updates. In regular updates, changes in the service template are applied to the service instance without replacing the OS image e.g. if you update memory of the VM there is no need to change the OS. Similarly if the new version of the template contains next version of an app, we can go ahead and replace the existing version of the app without losing the app state and this can be done without replacing the OS image. In image based updates, we will go ahead and replace the old OS image with new image composed of OS and app – again without losing app state. A typical example of this can be moving from existing OS image to an OS image with new patches.

TechReady12 9/16/2018 Обычное обновление
Для служб Для компьютеров Для гостевых ОС Для приложений Выбор уровня исходя из порядка обслуживания Удаление из подсистемы балансировки нагрузки GCE приложения до обслуживания GCE приложения до удаления GCE приложения до установки Выбор компьютера по признаку домена обновления Применение изменений на уровне приложения Удаление приложения Установка приложения Добавление в подсистему балансировки нагрузки GCE приложения после обслуживания GCE приложения после удаления GCE приложения после установки Готово So let’s walk through how Regular updating works. Begin the update on tier by tier basis based on the servicing order of the tier. Within each tier groups of machines are updated in parallel VMs are removed from Load Balancer Application level changes are applied VMs are added to the Load Balancer This process is repeated for each of the tiers. Встроенный этап Выполнение стандартной команды в гостевой ОС © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

TechReady12 9/16/2018 Обновление образов
Для служб Для компьютеров Для гостевых ОС Для приложений Выбор уровня исходя из порядка обслуживания Удаление из подсистемы балансировки нагрузки Выбор компьютера по признаку домена обновления Добавление диска данных в компьютер GCE состояния сохранения уровня приложения Замена диска с ОС Состояние резервного копирования серверного APP-V GCE уровня профиля приложения до установки GCE уровня приложения до установки Настройка новой ОС Установка приложения GCE уровня приложения после установки So let’s walk through how Image updating works. Begin the update on tier by tier basis based on the servicing order of the tier. Within each tier groups of machines are updated in parallel VMs are removed from Load Balancer Application state is saved to a data disk Slide in the new patched OS image Recustomize the OS Install the application(s) and put their state back Add the machine back to the Load balancer This process is repeated for each of tiers This shows you how we are able to compose OS, roles/features, applications and the state and manage the lifetime of a service. the tiers. Состояние восстановления серверного APP-V Встроенный этап Добавление в подсистему балансировки нагрузки GCE уровня профиля приложения после установки Выполнение стандартной команды в гостевой ОС Готово GCE состояния применения уровня приложения © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Обновитель уровня службы
TechReady12 9/16/2018 Обновитель уровня службы Обновитель уровня службы обновляет всю информацию о службе Определение виртуальных машин, пропавших из службы Обновитель службы поддерживает два состояния «ОК»: все ВМ в нормальном состоянии «Требуется внимание»: а) по меньшей мере с одной ВМ связана неполадка какого-то типа; б) состояние обновителя ВМ указывает на фактическую неполадку © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Действия в службе или на уровне
Простые действия на уровне службы применяются по всем виртуальным машинам Запуск, пауза, возобновление, остановка, отключение, удаление Действия на уровне Расширение (увеличение масштаба) Эта функция доступна в новом мастере Действия уровня ВМ Миграция ВМ Сохранение виртуальных машин в библиотеке Развертывание виртуальных машин из библиотеки Клонирование виртуальных машин Создание контрольных точек Сужение (уменьшение масштаба) Powershell scripts can be used to automate the actions that are performed at the machine level today.

Импорт и экспорт шаблонов обслуживания
TechReady12 9/16/2018 Импорт и экспорт шаблонов обслуживания Преимущества Использование одних шаблонов в нескольких разных средах Резервное копирование шаблонов обслуживания и ВМ Синхронизация серверов VMM в системах с несколькими VMM Экспорт метаданных шаблона в XML-файл Защищенные параметры шифруются и сохраняются Сопоставление ресурсов во время импорта Экспорт физических ресурсов, таких как VHD- диски, пакеты приложений и т. д., по вспомогательным каналам Benefits: Sharing templates between different environments Backing up Service templates/VM templates VMM server synchronization © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Заключение Мы познакомились с архитектурой и основными возможностями VMM 2012 Мы рассмотрели планирование и настройку структуры Мы научились определять службы с использованием объектов библиотеки

9/16/2018 2:47 PM © Корпорация Майкрософт (Microsoft Corporation), Все права защищены. Microsoft, Windows, Windows Vista, Windows Azure, Hyper-V и другие наименования изделий являются охраняемыми товарными знаками корпорации Майкрософт в США и других странах. Сведения в этом документе представлены исключительно в информационных целях и отражают текущую позицию корпорации Майкрософт на дату выпуска этой презентации. Поскольку корпртация Майкрософт обязана реагировать на изменения рыночных условий, эти сведения не должны трактоваться как какая-либо гарантия с ее стороны, и корпорация Майкрософт не может гарантировать их точность после даты выпуска этой презентации. КОРПОРАЦИЯ МАЙКРОСОФТ НЕ ДАЕТ НИКАКИХ ГАРАНТИЙ, ЯВНЫХ, ПОДРАЗУМЕВАЕМЫХ ИЛИ УСТАНОВЛЕННЫХ ЗАКОНОМ, ОТНОСИТЕЛЬНО СВЕДЕНИЙ В ЭТОЙ ПРЕЗЕНТАЦИИ. © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Виртуализация от Майкрософт для специалистов VMware

Similar presentations

Presentation on theme: "Виртуализация от Майкрософт для специалистов VMware"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Виртуализация от Майкрософт для специалистов VMware

Similar presentations

Presentation on theme: "Виртуализация от Майкрософт для специалистов VMware"— Presentation transcript:

Similar presentations

About project

Feedback