Summary - World of Cloud, Virtualization



Project Management Plan forProject Title ABC Inc Hyper-V Infrastructure Upgrade Date 16-04-2014Version V 1.0Contents TOC \o "1-3" \h \z \u Summary PAGEREF _Toc378173612 \h 3Background PAGEREF _Toc378173613 \h 3Project Description PAGEREF _Toc378173614 \h 3The Work Plan PAGEREF _Toc378173615 \h 4Resources and Budget PAGEREF _Toc378173616 \h 4Stakeholders PAGEREF _Toc378173617 \h 5Risk Assessment PAGEREF _Toc378173618 \h 5Quality Control PAGEREF _Toc378173619 \h 5Outcomes and benefits: PAGEREF _Toc378173620 \h 5SummaryThis will be a one and half months planning and execution activity to analyze and upgrade the current Hyper-V infrastructure from Hyper-V 2.0 to Hyper-V 3.0. It is also required to upgrade all the associated components of Hyper-V like, System Center Virtual Machine Manager from 2012 to 2012 R2. BackgroundABC Inc is facing the challenges of managing the current Hyper-V platform that are not consistently synchronized with the management server, issues with integration tools, not supported list of operating systems, etc. To address these problems, Microsoft Hyper-V Server, Microsoft Failover Cluster and System Center Virtual Machine Manager will be upgraded to the most recent release of Microsoft to 2012 R2. Hyper-V and VMM will be upgraded to 2012 R2 by keep running the productions virtual machines, at the end of the migration there will be 30 minutes-1hrs downtime for the VMs. Project DescriptionCreate a new Hyper-V cluster to accommodate “Generation-2” VMs and to move all the current VMs from the existing cluster to new cluster. It would be in-place upgrade process for hosts and scvmm server.Summary Scope of Work:Pre-Upgrade TasksMove/Migrate all the VMs to Node 1Upgrade Node 2 to Windows Server 2012 R2Create Cluster BLHPVCLUSGZ01 on Node 2Migrate Hyper-V Cluster 2012 to Hyper-V Cluster 2012 R2Take off all the roles and resources on Hyper-V Cluster 2012Bring online all the resources and roles on Hyper-V Cluster 2012 R2.Remove all the roles and destroy Hyper-V Cluster 2012Upgrade Node 1 to 2012 R2Join Node 1 to cluster2012 R2.Post-Upgrade Tasks.Remove the current Hyper-V Cluster from SCVMMAdd cluster to SCVMMRefresh ClusterThe Work PlanThe work plan identifies the changes we are making into the existing processes, procedures, resources and equipment. In addition, the plan identifies respective personnel will make the changes and when the changes will be completed. It is also crucial to determine how the changes will be measured and deemed successful. Detail activity plan of the initiate is attached herewith:Resources and BudgetImplementation of the solution requires educated time, staff additions or other resources to be included from Backup and Security team, Windows team.There is no direct financial impact of upgrading the infrastructure since we will be performing it by our own. StakeholdersStakeholders of this project will be IT Backup and Security Team.Risk AssessmentAccording our analysis couldn’t find any significant risk of performing this upgrade activities.Quality ControlUpgrading the infrastructure according to the project timeframe and provide educated training on the infrastructure to the other team members of Backup & Security and Windows team. Competence, such as knowledge, skills, experience and qualificationsOutcomes and benefits: The primary outcome of the project is to host the production virtual machines and/or production load to distribute virtual workload to a cost effective hypervisors. Details outcome of the initiative is given as follows:Generation 2 VMsHyper-V in Windows Server 2012 R2 supports the concept of a totally new architecture based on modern hardware with no emulated devices. This makes it possible to add a number of new features, such as secure boot for VMs and booting off of virtual SCSI or virtual network adapters.VM Direct ConnectDirect Connect feature allows a direct remote desktop connection to any running VM over the VM bus. Extend Replication to a Third SiteWindows Server 2012 R2 and Hyper-V now provide a tertiary replication capability to support just such a scenario. By the same token, enterprises can now save one replica in-house and push a second replica off-pression for faster migrationTwo new options in Windows Server 2012 Hyper-V help improve the performance of live migrations. The first is the ability to enable compression on the data to reduce the total number of bytes transmitted over the wire. The obvious caveat is that tapping CPU resources for data compression could potentially impact other operations, so you'll need to take that into consideration. The second option, SMB Direct, requires network adapters that support RDMA. Online VM Exporting and CloningNow it’s possible to export or clone a running VM from System Center Virtual Machine Manager 2012 R2. Online VHDX resizingIn Windows Server 2012 Hyper-V, it is not possible to resize a virtual hard disk attached to a running VM. Windows Server 2012 R2 removes this restriction, making it possible to not only expand but even reduce the size of the virtual disk (VHDX format only) without stopping the running VM.Storage QoSWindows Server 2012 R2 includes the ability to limit individual VMs to a specific level of I/O throughput. The IOPS are measured by monitoring the actual disk rate to and from the attached virtual hard drives. If you have applications capable of consuming large amounts of I/O, you'll want to consider this setting to ensure that a single I/O-hungry VM won't starve neighbor VMs or take down the entire host.Shared VHDXWith Windows Server R2 Hyper-V, Windows guest clusters (think traditional Windows Server failover clustering but using a pair of VMs) no longer require an iSCSI or Fibre Channel SAN, but can be configured using commodity storage: namely a shared VHDX file stored on a Cluster Shared Volume. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download