mountainss Cloud and Datacenter Management Blog

Microsoft SystemCenter blogsite about virtualization on-premises and Cloud


1 Comment

Why is Microsoft System Center integration important ?

This Topic explains why Microsoft System Center products becomes more important then ever before.

The layers are further defined as follows:

  • Service Delivery Layer: Represents those Service Management activities that require input and interaction with the business and service owner. The components are not only responsible for that interaction, but also the translation of business requirement into technology and operational capabilities. This layer represents the business perspective on the basis of IT.
  • Software Layer: Provides the applications and software that support a business activity (for example, CRM). The Software Layer consumes Virtual Machines (VM) services from the Infrastructure Layer and may consume application services from the Platform Layer.
  • Platform Layer: Provides a set of platform-level (above operating system(OS) level) building blocks which can be consumed by the Software Layer. It consumes hypervisor services from the Infrastructure Layer and is managed by the Management Layer.
  • InfrastructureLayer: Provides resilient hypervisor services to the Platform Layer and is managed by the Management Layer. The Infrastructure, Platform, and Software Layers represent the enabling technology perspective within IT.
  • Operations Layer: Represents Service Management and operational processes carried out by IT operations and support staff.
  • Management Layer: Provides management services to the Infrastructure, Platform, and Software Layers. It is comprised of the suite of management tools necessary to support IT Service and Operations Layer and implements the operational processes. The Management Layer provides a baseline set of capabilities to the Infrastructure Layer and an incremental set to the Platform Layer and the Software Layer. The Operations and Management Layers represent the operational perspective within IT.

A key tenet of the Reference Architecture is that it helps IT strategists and solution architects to make good design decisions. The guidance will only cater to the difference between the best practices of traditional IT and dynamic IT. For example, guidance on designing the directory services or change management processes already exists, so we will not duplicate that but will instead highlight what is different or new for a Private Cloud.

Examples of the principles are as follows:

  • Use virtualization to abstract applications from hardware.
  • Focus on Mean-Time-to-Restore-Service instead of avoiding hardware failure.
  • Have a meaningful understanding of infrastructure’s health state.
  • Automate “detect and respond” processes.
  • Homogenize your hardware infrastructure to reduce complexity.
  • Encourage desired consumer behavior.

When you keep this model in mind, you can see what this means for Microsoft System Center Virtual Machine Manager for example :

 

With Microsoft Product code “Concero” you get a hybrid Cloud Managementtool wich brings privat and public Cloud togehter in one Console.
More Microsoft System Center products becomes integraded.
For example, in System Center Virtual Machine Manager 2012 you can deploy your virtual application as a Service wich is sequenced by Microsoft APP-V 4.6

With this System Center 2012 Cycle you are ready for the future with Cloud technology.


Leave a comment

Hybrid Cloud Management with Microsoft System Center Code-Named “Concero”

Here is the powerpoint presentation about Microsoft System Center “Concero” wich was presented on Tech-Ed 2011 in Atlanta.

For the video about Concero at Tech-Ed 2011 in Atlanta, just click on the picture above.

Microsoft Concero Presentation


Leave a comment

Microsoft System Center Virtual Machine Manager evolution

This topic is about the evolution of Virtual Machine Manager.

First we used the Microsoft Hyper-V release 1 manager in our datacenter with each virtualmachine his own LUN’s (fiberdisk)
This is a service roll in Windows 2008 Enterprise Server.

The first Microsoft Virtual Machine Manager 2008 wich was separated from the Operating System looks like this :

SCVMM2008

New Hyper-V architecture was released with Windows 2008 R2 Server which supports shared volume between nodes. It called as Clustered shared volume. This volume can be used by all nodes at the same time. All virtual machines located in this LUN can be started on any of the host. If one node dies virtual machine will get started in any other available nodes. And can be live migrated (like vMotion) to other available nodes. It also saved a lot of diskspace.

Cluster Shared Volumes

Microsoft System Center Virtual Machine Manager 2008 R2 Service Pack1 made the difference with Dynamic Memory and Remote FX.

Dynamic memory settings

remotefx

When you look to the history of Microsoft Virtual Machine Manager the topology looks like this today :

Microsoft System Center Virtual Machine Manager 2008 R2 SP1 can manage a mixed virtual environment like:

Vmware

VMWare ESX Servers and Cluster Support.

citrix_xenserver_architecture

Citrix Xen Servers and Cluster support.

Microsoft is making a big jump this year with great features in System Center Virtual Machine Manager 2012 with Cloud technology.
Microsoft Virtualization developer team has worked really hard and have listened to IT professionals and Customers.

Microsoft System Center Virtual Machine Manager must be High Available to manage the virtual environment on-premises and Cloud with Windows Azure, and with this we have a hybrid virtual managed environment.

This Virtual environment has been divided in areas in virtual Machine Manager 2012 :

1. Infrastructure enhancements
Highly Available VMM server. As SCVMM is core of management infrastructure for virtual environment it is really important for this infrastructure to be highly available in todays big datacenters.

2. Fabric Management
SCVMM 2012 can now manage even more hypervisors: Hyper-V, VMWare and XEN. Also it can integrate with remote management such as iLO and SMASH. One interesting thing here is also ability for bare metal provisioning meaning that with SCVMM 2012 you can provision Hyper-V even on bare metal computers withoudt much manual work. Cluster creation with storage provisioning is also one of the interesting new features. Regarding the network management enhancements, SCVMM 2012 can now integrate with load balancers. Besides that now you can also assign IP and MAC from pools. Dynamic Optimization and new Power Management features are also important updates.

And now for the two most expected features of System Center Virtual Machine Manager 2012:

3. Cloud Managementor Simple Cloud Creation.

SCVMM can now abstract server, network and storage resources into private clouds, delegate access to private clouds with control of capacity, capabilities and user quotas. Also now it is rather easy to enable self-service usage for application administrator to author, deploy, manage and decommission applications in the private cloud.

4. Service Management
With SCVMM you can now define service templates to create sets of connected virtual machines, os images and application packages. For example you can create service template for three tier application which consist of frontend, middletier and backend. During service deployment operating images and applications can be composed. And of course if you need your virtual machines in a service to scale out, no problem, SCVMM 2012 makes this possible. And final and maybe most important feature in service management is ability to leverage great and powerfull technologies like Server Application Virtualization (Server App-V). Server App-V behaves in same manner as client App-V, so they are dynamic, “decoupled from OS” and easy to manage.

There are of course much, much more enhancements in System Center Virtual Machine Manager 2012. Check them out on technet and start your yourney to the cloud.

And at last Microsoft System Center Codename “Concero” preview is more then great easy to manage Virtual Machine Manager in the Cloud.

Microsoft System Center Virtual Machine Manager evolution is better then ever before, and almost every choice of the customer is possible with Microsoft virtualization technology on-premises and/or in the Cloud with Windows Azure and of course with Office 365.

My compliments to the System Center team !Emoticon met brede lach


Leave a comment

Microsoft System Center Codename “Concero” overview

Italian YouTube movie about Microsoft System Center Codename “Concero” overview.

First look to the features of System Center Codename “Concero”

“Concero will enable customers to deploy, manage and control applications and services on private clouds built using System Center Virtual Machine Manager 2012 and in the public cloud offering of Windows Azure. This provides a consistent and simple user experience for service management across these clouds.”

The list of top-line Concero feature includes access to resources across Virtual Machine Manager (VMM) servers, the ability to register and consume capacity from multiple Windows Azure subscriptions, and the ability to copy service templates and optional resources from one VMM Server to another. Other Azure-related features enable multiple users to be authenticated through Active Directory to access a single Azure subscription, and make it possible to copy Azure configuration, package files and VHDs from on-premises and between Azure subscriptions.


Leave a comment

Windows Azure connect concept of Chung Chou

This topic explains why SCVMM2012 and Microsoft projectcode “Concero”  becomes a very important tool to manage your virtual machines and applications on-premises and Cloud platform Azure.
Make your domain inclusive with Microsoft Windows Azure.

Read more on Chung Chou his blogsite at Microsoft Technet :

http://blogs.technet.com/b/yungchou/archive/2011/05/03/cloud-computing-of-paas-with-windows-azure-connect-1-2.aspx

Great blog Chung !
Thanx.