Hyper-V VMM ile Cloud computing

6. #mshowtobulutlarda Live Migration Daha hızlı, sınırsız ve sorunsuz VM Live Migration Live Storage Migration Sanal disklerin bağlantı kaybı olmadan taşınabilmesi Shared-Nothing Live Migration Host ve Cluster olmadan VM Live Migration Hyper-V Replica Bütünleşik VM bazlı Replikasyon Scalable Cluster Cluster içinde 64 node desteği 6

7. #mshowtobulutlarda The Shift to Cloud Computing Physical Virtual Private Public

8. #mshowtobulutlarda Service Agreement Deliver IT as a Service on your terms with flexible, common management across your hybrid environments

9. System Center 2012 - Virtual Machine Manager: #mshowtobulutlarda Provisioning Your Private Cloud Infrastructure and Applications DELIVER FLEXIBLE AND COST- PROVISION AND MANAGE OPTIMIZE VIRTUALIZATION EFFECTIVE INFRASTRUCTURE STANDARDIZED APPLICATION MANAGEMENT SERVICES • Pool and allocate data center • Provision standardized • Optimize infrastructure based resources applications on application needs • Multi-hypervisor management • Simplify application management • Highly available private cloud • Flexible delegation with control • Cloud enable existing apps infrastructure • Self-service infrastructure • Industry standards support

10. #mshowtobulutlarda Deliver Flexible and Cost-Effective Infrastructure Storage Consolidate your Finance Marketing heterogeneous infrastructure into a HR standardized cloud fabric Network AllocateProvision cloud resources your cloud fabric to business units Compute

11. #mshowtobulutlarda Why SP1? Windows Server 2012 Windows Server 2008 R2 System Center 2012 SP1 Microsoft Virtual Machine Manager Manages Hyper-V Server 2012 Microsoft Windows Server SQL Server Hyper-V Server 2008 R2 2008 R2 2012 2008 R2 2012

12. #mshowtobulutlarda Configure and Deploy Fabric COMPUTE STORAGE NETWORK CLUSTER Deploy your compute Discover, classify, and allocate Abstract your complex Consolidate your fabric resources, taking them from storage for use by the private networking infrastructure into elements for use in a private bare metal to fully deployed for cloud. Provide the correct logical networks for cloud use. cloud. your physical and virtualization storage for use with appropriate Assign IP, virtual IP, and MAC hosts. access. addresses from pools and integrate with load balancers.

13. #mshowtobulutlarda Automated Bare-Metal Hyper-V Deploy in Action Download WINPE Boot from PXE 4 2 Run generic command execution scripts and configure Host Group WDS server Customize and partitions domain join Authorize PXE boot 3 8 contoso OOB reboot 5 Host Group 1 Enable Hyper-V VMM server Hyper-V server Hyper-V server 9 Download VHD Inject drivers Bare-metal Hyper-V server Hyper-V server VHD server 7 6 Drivers Library server Host profile 1 2 3 4 5 6 7 8 9

14. #mshowtobulutlarda Storage Allocation & Management Discover storage through SMI-S provider Virtual Machine Manager Host Group Industry Standard API Create storage classification pools and associate with storage SMI-S Provider Allocate storage to specific host groups Assign existing LUNs to hosts and clusters Create new LUNs from pool and assign to hosts and clusters Gold Silver

15. #mshowtobulutlarda SP1: Storage Deploy VM’s with VHDX format Disks up to 64 TB Enhanced performance with physical disks > 512 bytes sector Added Resiliency Use of SMB 3.0 file share for stand alone/clustered host Windows File Server and NAS devices supporting SMB 3.0 Compatibility with Synthetic Fiber Channel in the guest Live Storage Migration Seamless use of ODX with capable hardware

16. #mshowtobulutlarda Logical Networks in the Private Cloud Standardized Services Delegated Capacity Development Production Create Logical Networks and assign them to the appropriate networking on the hosts Cloud Abstraction DMZ Prod DMZ Prod DMZ Prod Configure and deploy Infrastructure Production Development

17. #mshowtobulutlarda Hyper-V Network Virtualization Blue VM Red VM Blue Network Red Network Virtualization Physical Physical Server Network Server Virtualization Hyper-V Network Virtualization – Run multiple virtual networks on a • Run multiple virtual servers on a physical server physical network • Each VM has illusion it is running as a – Each virtual network has illusion it is physical server running as a physical network – Realized via Windows Server and VMM

18. #mshowtobulutlarda SP1: Cluster Manage “Possible/Preferred Owner” settings Supports CSV2, 64 cluster nodes, 8000 VMs/cluster, 1024 VMs/node Availability Sets (anti-affinity) Ensures VMs are placed on different hosts for VM and Service continuity per policy Works even for stand alone hosts Leverages “AntiAffinityClassNames” property for Windows Server 2008 R2 & Windows Server 2012 failover clusters

19. #mshowtobulutlarda SP1: Cloud and User Role Enhancements • Tenant Admin Administrator –Manage tenant membership • Tenant membership ID Delegated decoupled from AD via Administrator Service Provider Foundation (SPF) Tenant Administrator • Increased scale • Self-Service User

20. #mshowtobulutlarda Tesekkurler www.Mshowto.org

Notas del editor

Please change the logo
Goal: Frame the enterprise cloud computing conversation by highlighting the evolution from traditional to cloud computing models. Define industry taxonomy around private and public clouds. A couple of data points from internal Microsoft research: 41 percent of our customers are using services across datacenters on premises and in public clouds. 80 percent of our customers over the next three to five years will use hybrid models.Talking pointsTransition from previous slide Let’s start with the definitive evolution that's happening within IT.Customers are telling us that they are increasingly considering cloud computing models (versus just deploying physical and virtual environments). <click> If you’re referring to Infrastructure as a Service (private cloud), you're thinking about your datacenter as a set of pooled resources (including compute, network and storage), not in terms of individual hosts or VMs.If you’re referring to public cloud, you're talking about building applications that will then be delivered as a service. The platform provides all the required building blocks for your app. Think Windows Azure. Between private and public cloud, we believe that the concept of delivering IT as a Service will transform how customers consume IT and will deliver a completely new cost structure at a much higher level of business responsiveness.We believe hybrid environments will become the norm over the next few years. A common toolset with integrated physical, virtual, Private, and Public cloud management will help you optimize your return on investment.
Goal of this slide. Frame the cloud computing opportunity for the enterprise and Microsoft’s cloud and data center management vision to address that opportunity.Spotlight the players in the IT as a Service conversation within the enterprise (call out the app leader and the ops leader in the room). Talk about their motivations and how they’re typically non-compatible.Key points to landIT as a Service is the mental model around which the app leader and the ops leader come together as consumer and provider respectively.Talk about how the System Center 2012 cloud and data center management vision uniquely addresses IT as a Service in the context of private and public cloud computing. Talking Points (progressive builds) So what does this cloud transformation mean to the enterprise)?Cloud computing is emerging as a major disruptive force in shaping the nature of business and IT conversations. Cloud computing enables what we call IT as a Service which represents IT delivered to the business in a manner that’s agile and cost-effective while meeting the quality of service (QoS) parameters that the business expects. A cloud service demonstrates attributes like self-service, metering by use, elasticity, and scalability. <click> Now, any service offering by definition has a service consumer and a service provider. Simplistically speaking, the service consumer represents business interests while the service provider represents IT. These constituencies are incented around different KPIs. <click> For example, a business or application owner (the service consumer) would care about time to market, costs, and ease of use…<click> …whereas a data center administrator (or service provider) optimizes for security, compliance, process controls, and availability. To align these interests, we need a mechanism to deliver the agility that the business needs while ensuring the operational efficiencies that IT cares about most. <click> Enter IT as a Service. IT as a Service provides the framework for the service level based agreement between IT and the business stakeholders. <click> Through System Center 2012, Microsoft’s cloud and data center management vision is to deliver: Common management experiences across private and public clouds.IT as a Service on your terms with flexible management across your hybrid environments.How does System Center 2012 do that?
Goal of this slideRepresent core messages that differentiate us from VMwareTalking PointsSo at it’s heart, System Center 2012 delivers three core promises for datacenter and cloud management.System Center 2012 cloud and data center management solutions empower you with a common management toolset for your private and public cloud applications and services. System Center helps you confidently deliver IT as a Service for your business.System Center 2012 helps your organization consume and deliver IT as a Service by enabling productive infrastructure, predictable applications, and cloud on your terms. System Center 2012 helps you to deliver flexible and cost-effective private-cloud infrastructure to your business units in a self-service model, while carrying forward your existing data center investments. Recognizing that applications are where core business value resides, System Center 2012 offers deep application insight, which, combined with a service-centric approach, helps you deliver predictable application-service levels. Finally, System Center 2012 empowers you to deliver and consume private and public cloud computing on your terms with common management experiences across your hybrid environments.Productive Infrastructure System Center 2012 helps you deliver flexible and cost-effective infrastructure with what you already know and own. System Center 2012 helps you integrate heterogeneous data center investments, including multi-hypervisor environments. You can pool and abstract your data center resources and deliver self-service infrastructure to your business units in a flexible, yet controlled, manner.Heterogeneous supportTo help you carry forward your existing data center investments and skillsets, System Center 2012 offers integrated management for your heterogeneous data center environments. For example, it offers multi-hypervisor management for Microsoft Hyper-V, VMware vSphere/ESX, and Citrix XenServer with Virtual Machine Manager; cross-platform monitoring of Linux/Unix/Sun Solaris guests with Operations Manager; cross-platform configuration management for Linux and Unix servers with Configuration Manager; and integrated automation across management toolsets from vendors like HP, CA, BMC, EMC, and even VMware with Orchestrator.Process automation System Center 2012 helps you simplify and standardize your data center with a flexible process automation platform. By automating repetitive tasks, you can lower your costs and improve service reliability. With Orchestrator, you can integrate and extend your existing toolsets and build flexible workflows (or runbooks) that can span across multiple organizational silos and systems. These workflows are then executed in an orchestrated manner through the automation engine built into Orchestrator. Service Manager offers industry-standard service management capabilities (based on ITIL/MOF) which automates core organizational process workflows like incident management, problem management, change management, and release management.Self-service infrastructure With the provisioning capability of Virtual Machine Manager, you can pool and abstract your data center resources (such as compute, network, and storage) into a private cloud infrastructure fabric, which can then be maintained by Virtual Machine Manager and Operations Manager. You can allocate and delegate this pooled fabric to your business unit IT organizations in a flexible, yet controlled, manner using Virtual Machine Manager. Application owners can consume capacity (and request additional capacity) in a self-service mode using the service catalog offered by Service Manager. Requests for capacity would be fulfilled using the process automation and provisioning capabilities offered by Orchestrator and Virtual Machine Manager respectively.Predictable ApplicationsApps power your business. System Center 2012 helps you deliver predictable application service levels with deep application insight, and holistically manage your application services, which is where your core business value resides.Deep application monitoring and diagnosisOperations Manager offers deep application and transaction monitoring insight for .NET applications (and J2EE application server health) to maximize application availability and performance. Operations Manager also integrates with Microsoft Visual Studio through a connector to unlock development-to-operations collaboration, thereby helping you remediate application issues faster, which results in the delivery of predictable SLAs. Easy-to-use reporting and dashboarding allows you to track and communicate your SLAs more effectively.Comprehensive application manageability Microsoft Server Application Virtualization (SAV), a feature of Virtual Machine Manager, optimizes your modern and existing applications for private cloud deployments with sequenced state separation between the application and underlying infrastructure. SAV dramatically simplifies application servicing (such as upgrades and maintenance) with image-based configuration and management techniques that reduce administrative effort and expense. By decoupling your applications from the infrastructure, SAV helps unlock application portability as appropriate to your business needs.Configuration Manager supports SAV, thereby extending the benefits of SAV to applications and workloads that may be deployed in physical/traditional environments. Through SAV support, Configuration Manager enables easier physical-to-virtual application mobility and in-place application servicing. Service-centric approachIn a cloud computing model, a service is a deployed instance of an application along with its associated configuration and virtual infrastructure. System Center 2012 offers a service-centric approach to help you manage your application components in the context of the holistic service that it represents to the business. From provisioning services (visualization, design, composition, deployment, and configuration) to operating them (monitoring, remediation, and upgrades), we help you manage the full lifecycle. For example, Virtual Machine Manager and App Controller enable service-centric provisioning and updates while Operations Manager enables monitoring at the service level. Your CloudPrivate and public cloud computing on your terms managed with a common toolset. System Center 2012 empowers you to deliver and consume private and public cloud computing on your terms, with common management experiences across your hybrid environments.Flexibility with delegation and controlConstruct and manage clouds across multiple data centers, multiple infrastructures (such as Microsoft and VMware), and service providers (Windows Azure). Provide delegated authority and tools to enable self-service flexibility across your environments. You retain control across your private and public cloud environments, which is important for enterprise security and compliance requirements while ensuring your IT pros have a key role even as your organization adopts cloud-computing models.Applications self-service across clouds System Center 2012 empowers your application and service owners with a common self-service experience across private-cloud and public-cloud computing models. With App Controller, you can experience full visibility and control of your private and public cloud applications and services, so you can confidently adopt Windows Azure as your enterprise Platform as a Service (PaaS) choice.Physical, virtual, and cloud managementSystem Center has historically been known for physical and virtual management in the data center. You can also use your familiar on-premises Operations Manager to monitor your Windows Azure applications (using the Monitoring Pack for Windows Azure Applications)—thus extending your common management experience to the cloud. App Controller provides you a single pane of glass with self-service flexibility and control for your application owners to manage their applications and services across private and public clouds, including Windows Azure. Hybrid environments will be the corporate standard for many years; a common management toolset with integrated physical, virtual, IaaS, and PaaS management will help you increase efficiency and optimize ROI.
Talking points:[Click] Deliver flexible and cost-effective infrastructure. With the provisioning capability of the System Center 2012 component Virtual Machine Manager, you can pool and abstract your compute, network, and storage resources into a private cloud fabric. To help leverage your existing datacenter investments, Virtual Machine Manager supports VMware and Citrix infrastructure as well as Hyper-V. You can allocate these pooled datacenter resources to your business units in a flexible manner using the controlled delegation capabilities offered by Virtual Machine Manager. [Click] Provision and manage standardized application services. Microsoft’s goal is to apply to your private cloud what it has learned from operating large-scale online services like Bing, Hotmail, and Windows Live efficiently and reliably using the capabilities in Virtual Machine Manager. To this end, Virtual Machine Manager enables you to easily provision and maintain standardized application services to your private cloud using capabilities like service templates and image-based management. SAV technology built into Virtual Machine Manager makes it possible to abstract (or sequence) your applications from the underlying infrastructure, so it’s easy to upgrade them, and potentially enhances their cloud readiness. [Click] Optimize virtualization management. Virtual Machine Manager delivers:Dynamic optimization of your datacenter resources based on workload demands like power management and fabric utilization. A highly available and reliable Virtual Machine Manager server infrastructure to base your private cloud on. Deeper support for industry standards like PowerShell, OVF, and SMI-S.
Talking points:Virtual Machine Manager helps you deliver a flexible and cost-effective private cloud infrastructure while leveraging your existing datacenter investments. [Click] The first step in setting up your private cloud infrastructure is to consolidate your existing datacenter resources. Virtual Machine Manager helps through its support of VMware and Citrix infrastructure as well as Hyper-V. It also supports a variety of other storage, network, and compute resources that you can take advantage of, depending on your investments. [Click] As a next step, Virtual Machine Manager helps you pool and abstract datacenter resources to provision a standardized private cloud infrastructure fabric.For compute, Virtual Machine Manager offers bare-metal to Hyper-V to cluster provisioning. For network provisioning, Virtual Machine Manager helps you define logical networks using VLANs and sub-nets, assign IP addresses, and automate load balancer provisioning. For storage provisioning, Virtual Machine Manager offers discovery of storage arrays and pools, LUN configuration and assignment to hosts and clusters, and rapid VM provisioning. [Click] Finally, to enable self-service infrastructure, Virtual Machine Manager offers flexible delegation of clouds with the right balance of control between the service provider and service consumer. Think of these as mini-clouds based on each of your organization’s requirements. While this example shows a breakout based on line of business, you could just as well think of these as being Dev, Test, and Production mini-clouds, or geography-based mini-clouds.
Talking points:Virtual Machine Manager offers service templates that help you provision standardized application services to your private cloud. This will improve the agility of your application deployments and help you benefit from cloud computing attributes like elastic scale. [Click] With Virtual Machine Manager, the application owner (or service consumer) can specify configuration requirements like application architecture, scale-out rules, health thresholds, upgrade rules, and so on, just as a developer would specify requirements for a Windows Azure application. Except in this case, we are talking about an application service that will be deployed to your private cloud. Service templates provide the blueprint for the application service, including the hardware, operating system, and application packages. Virtual Machine Manager supports multiple package types for.Net applications, including MS Deploy for the web tier (IIS), Server App-V for the application tier, and SQL DAC for the data tier. [Click] Virtual Machine Manager uses the service template specification to build out the application tiers, including the various logical instances associated with each tier. In the real world, you are likely to encounter scaled-out (or multi-instance) web front ends and application tiers, but scaled up (or single-instance–based) database tiers. [Click] Virtual Machine Manager also uses the service template specifications to help ensure that the application is deployed to the appropriate virtualized resource pools. We’ve thus seen that an application service comprises the application code, the virtual infrastructure on which it is hosted, and its configuration details. We’ve also seen how Virtual Machine Manager is bringing Microsoft’s learning from operating large-scale cloud application services to help you deploy standardized application services to your private cloud environments.
Talking points:Server Application Virtualization (SAV) dramatically simplifies maintaining standardized application services in your private cloud. SAV optimizes your applications (including a subset of existing applications) for private cloud deployments with sequenced state separation between the application and underlying virtual infrastructure. Further, it dramatically simplifies upgrades and maintenance with image-based configuration and management techniques that reduce administrative effort and expense. [Click] Let’s look at a scenario in which you can update the business logic tier of a three-tier application using image-based updates to a previously deployed application service. An image-based approach is where one or more new virtual instances (or VMs) are created, typically from an updated virtual image. Virtual Machine Manager moves the running application into these new VMs, and shuts down any VMs that the application was previously running.[Click] Let’s say we need to update the middle-tier business logic of a running application, so we must install the application’s code in the new VM. This should be pretty straightforward if the application maintains no state within its VM. But applications often make local changes within their VMs, such as modifying the Windows registry or relying on local configuration files. So moving the application successfully to a new VM might require moving this state as well. Virtual Machine Manager can accomplish this by wrapping the application code in an SAV package. Through sequencing, SAV can detect and track any local state changes the application makes. When the running application is moved into a new VM, the SAV package moves its current state as well, including registry changes and configuration files. Because image-based updates can install a new VM image beneath a running application, it allows a separation of applications and VM images. This eliminates the need to have a separate VM image for each application that uses that image. Instead, an organization might choose to use the same small set of VM images for many applications, combining them as needed with service templates. Managing fewer VM images is simpler, cheaper, and less error-prone.
Talking pointsVirtual Machine Manager includes a new feature: dynamic optimization (DO) of your datacenter resources based on workload demands. It optimizes VM performance and use of resources through cluster-level workload balancing. Virtual Machine Manager supports dynamic optimization for Hyper-V, VMware, and Citrix XenServer clusters (as shown in the screenshot in the background). Dynamic optimization:Optimizes for the following resource types: CPU, memory, and disk and network I/O. Is triggered when resource usage goes above a threshold specified by the administrator. Calls upon other features like live migration to avoid fabric downtime. Can be configured according to the level of optimization required—for example, setting more aggressive thresholds will result in a greater number of optimization actions. Virtual Machine Manager uses power management to optimize for the same resource types as DO when resource usage falls below the specified threshold (as illustrated by the screenshot in the foreground). This capability works to an administrator-defined schedule—for example, hours of the day when power should be optimized. Virtual Machine Manager helps to ensure that the host is evacuated before powering off, that the evacuation will not cause other nodes to go above the DO threshold, and that no cluster quorum requirements are violated. Virtual Machine Manager offers a highly available and reliable server infrastructure on which to base your private cloud. Virtual Machine Manager server is cluster-aware, which offers a level of resiliency against OS and VM failures. For example, you could create non–high availability VMs on clustered hosts to take advantage of this capability. Virtual Machine Manager continues to offer deep support for standards like PowerShell, OVF formats, and SMI-S.
So why Service Pack 1? Well in System Center 2012 Virtual Machine Manager we support all the current versions of the Microsoft products. Windows Server 2008 R2, Microsoft Hyper-V Server 2008 R2, but shortly after that release Windows Server iterated their new version to Windows Server 2012 and so in System Center 2012 SP1 Virtual Machine Manager we add support to the 2012 wave of Windows Server products.
So what I’m going to go through today is I’m going to talk about how in VMM 2012 we’ve enhanced our configuration and deployment mechanism which is where we assign dedicated and shared resources to our compute fabric and storage fabric and network fabric. We put all that together so that you can present a cloud abstraction to the users of your environment. We made some enhancements there as well that I’ll be talking about throughout this session. Once you have a cloud abstraction available you can delegate that capacity to the users of your system. And then finally these users are able to build standardized services that can model a multi-tier application that can be deployed into that file.
So configuration and deployment of the fabric it really starts off with the basics of compute, storage and networking, these are the physical resources that you have in your data center. We can build those together into a cluster so that you can deploy highly available workloads into your environment.
So I’m going to walk you through the bare metal hyper-V deployment process to give you a little review of how we get an operating system onto a Hyper-V host. It starts off with a bare metal server that doesn’t have an operating system but what is does have is a called a BMC or a baseboard management controller. VMM is able to tell the BMC to do what we call an out of band reboot, we tell the machine through that controller to reboot yourself. When it does that the machine is configured to boot from PXE or the pre-boot execution environment and when it does this PXE boot it talks to a WDS server to get a boot image of a Win PE image that it’s able to deploy to boot from to get the deployment image. Now, before we can actually deploy an image to it we check to make sure that this is a bare metal server that VMM has configured for deployment. So VMM authorizes this PXE boot then downloads the customized Win PE image to the bare metal server. This Win PE image is customized to contain the VMM agent that is able to talk to the VM Server and get itself orchestrated through the deployment process. So it’s part once we’re in through Win PE as part of the deployment process we’ll run GCE’s on this bare metal machine so that we can get the machine configured into a known consistent state based off of what the generic command script contains. After we’ve prepared the machine, formatted the hard disk and downloaded the VHD we configure the machine to do a native boot from VHD or to boot into the operating system that it will be running in production and so we need to download a VHD onto the bare metal server to get that VHD on there. after we’ve put the VHD on there we will also inject drivers so that the bare metal server has the necessary drivers that it needs so that when it boots into Hyper V for the first time the operating system is able to see all the hardware in the machine. We inject the drivers from the VMM library so that we know that there’s a consistent set available for every machine that we deploy to. After we’ve deployed drivers we now reboot the machine into the customization process, we use the unattend XML that is automatically inserted into the VHD and the machine is customized based on the settings from the host profile. ? Custom process machine also joins a domain in this example the Contoso domain is joined. And then finally we install the VMM agent and enable Hyper-V so that this bare metal machine then becomes a Hyper-V server and is now ready for use. You can either use it immediately as a stand alone host or you can then continue later on and add it to a cluster or as a highly available Hyper-V server. The final thing you’ll want to do though is run post deployment scripts which can be used to configure the teaming or configure additional storage options after the initial deployment.
So in VMM 2012 we’ve added the ability to allocate and manage storage arrays, we do this through an ability called SMI-S in order to talk to SMI-S you have to have an SMI-S provider installed that let’s us talk to a particular storage array. Once we can talk to the storage array we can create storage classifications and pools and associate the storage with those pools. We can then also allocate storage from these pools to specific host groups, we can then use that storage for assigning to hosts and clusters so that you can use them for creating clusters or creating VMs.
So in Service Pack one we made a number of enhancements in the area of storage for starters you can now deploy VMs using the VHDX format for the virtual hard disk. There are a number of enhancements in the VHDX format, they can be much larger than before so the skys goes up from 2 TB to 64 TB. There’s enhanced performance and more resiliency. We also now have the ability to add SMB file shares to hosts and clusters so that you can store your VMs that are running onto SMB shares and run these VMs off of these shares. These shares will be provided by Windows file server or mass devices that support SMB 3.0. We also have compatibility with synthetic fiber channel in the guest and we now support live storage migration this lets you move the VHD or VHDX that the running VM is using, you can move it from one storage location to another, this allows you to balance out your storage if one of your storage locations is becoming too full or if there is too high of an IO workload on one storage device you can migrate some of that workload to another storage device.
So in the area of networking we’ve also made a number of enhancements. So in 2012 we added the ability to model your network to logical networks. So this lets you in each part of your data center define what the network means there but give a common name that can be used to reference that data center because nobody that deploys a VM wants to connect that VM wot VLAN 5 they want to connect it to their corp network or their production network. So by doing this we let them access named entities to deploy their VM to that environment.
So Hyper-V network virtualization is a new capability in Windows Server 2012 where the network environment is virtualized in much of the same way as a server environment is virtualized in virtual machines. So with the virtual machines you can run multiple VMs on the same physical server so with network virtualization you can have multiple networks that are each independent with their own address base completely isolated from each other all on the same physical network. This is done through isolation in the Hyper-V switch and on the network the packets are encapsulated and on the network using a portal called NBGRE.
We’ve seen a big shift happen in the last year around where modeling the fabric isn’t enough there’s been a shift towards software defined networking. Software defined networking abstracts out the hardware in much the same way that a virtual machine abstracts out the hardware of your server for your compute, software defined networking abstracts out the control layers and how that network is exposed to the virtual machines so that it’s separate from the physical infrastructure. So we interact with Software Defined Networking in two ways, number one with Hyper-V network virtualization, this abstracts out the IP Address base for what the workloads of the virtual machines will be using and we also support an extensible virtual switch this is using the new capabilities in Windows Server 2012 which allows the virtual switch in Hyper-V to be extended using third party drivers. These extensions give additional capability to the switch all done through software without any enhancements required in your network environment. So in SP1 we’ve also added support for some of the other new capabilities of the Hyper-V extensible switch such as network policy and offloads these include SR-IOV, DHCP Guard, also bandwidth controls. So in order to expose these capabilities we’ve added a new concept called a VM network, a VM network is the layer that is presented to the virtual machine and the tenants of this environment. The VM network contains it’s own address space for network virtualized networks but you can also use a VM network for other isolation technologies such as VLANs or if the Hyper-V extensible switch has a reporting extension, reporting extension can also do it’s own form of isolation. So by exposing VM networks to VMs we now have a separation from what the virtual environment sees to what’s actually defined in the fabric.
Now we’ve made a number of enhancements in SP1 to clustering including managing the “possible/preferred owner” settings, these give you a preferred location to deploy your VM. In addition we’ve increased our scale to match the new capabilities in failover clustering and we’ve now added support for availability sets so these are availability sets you set up on your clusters so that when you deploy your VM we will respect those rules and ensure that the VMs are placed on the hosts that the availability sets have defined for them.
In SP1 we’ve enhanced the user roles and the clouds that we have in there to support a new role called tenant administrator. A tenant administrator is the one person or multiple people in an organization that keep track that the organization has used in a multi-tenant environment so this tenant admin is able to delegate the resources available to sub tenants or self service users. We expose this through our service provider foundation and ultimately up through to our portals. We’ve also increased the scale that’s available to these tenants as well.
Thank you again for watching this and I’ll see you next time.

Hyper-V VMM ile Cloud computing

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Similar a Hyper-V VMM ile Cloud computing

Similar a Hyper-V VMM ile Cloud computing (20)

Último

Último (20)

Hyper-V VMM ile Cloud computing

Notas del editor