VMM Network Serisi – Logical Networks

SCVMM icerisindeki Software Defined Networking detaylarini inceleyen serinin bu bolumunde en onemli bilesenlerden birisi olan Logical Network leri inceleyecegiz. Logical Networklerden baslamamizin sebebi aslinda bir cok yapilandirmayi gerceklestirmeden once oncelikle Logical Network dizayninizi gerceklestirmenizin gerekiyor olmasidir.

Alt basliklar ile Logical Network’u inceleyemeye baslayalim.

Logical Network Nedir?

Logical Network en basit tanimi ile “Fiziksel Hyper-V hostlariniz, bu hostlar uzerinde bulunan sanal makineleriniz ve hizmetleriniz icin network bilesenlerini tanimlama ve organize etmenizi kolaylastiran bir kavramdir. SCVMM ile temelde yapmaya calistigimiz sey fiziksel network altyapisinin bir sanal kopyasini olusturmaktir, Logical Network bu noktada en buyuk rolu oynar ve fiziksel network uzerindeki bilesenlerin bircogunu tanimlamamiza olanak saglar.

Iste bu sebeple VMM icerisinde network yapilandirmasina Logical Network tanimi ile baslamamiz ve de ayni zamanda fiziksel network yapisini goz onune alarak Logical Network dizaynini gerceklestirmemiz gerekmektedir.

Logical Network tasarimi nasil gerceklestirilir?

Yukaridak bahsettigimiz gibi logical network tasarimi, VMM icerisinde tum networking bilesenlerini etkileyecegi icin tasarimi oldukca onemlidir. Logical Network tasarimi yaparken asagidaki hususlara dikkat edilmesi gerekiyor:

  • Oncelikle fiziksel network detaylari incelenir. Mumkun oldugunda fiziksel networkler Logical Network seklinde olusturulur.

Logical Network fiziksel networkun VMM icerisindeki sanal bir yansimasidir diyebiliriz. Bu sebeple fiziksel network detaylari detaylica incelenmelidir. Ornegin 3 ana lokasyona dagitilmis network altyapiniz varsa, bu 3 network icerisinde fiziksel Hyper-V sunuculariniz, farkli subnetleriniz ve IP araliklariniz varsa bu detaylar Logical Network tasarimi icin oldukca onemlidir.

Ancak bu her fiziksel network icin birer Logical Network olusturulacak anlamina gelmiyor. Ayni zamanda sadece 3 adet Logical Network olusturulmasi yeterlidir anlamina da gelmiyor.

Tek bir logical network icerisinde birden fazla network site, vlan ve IP subnet belirlenebilmektedir. Bu sebeple aslinda tek bir Logical Network olusturmak 3 farkli fiziksel network ihtiyaclarini karsilayabilir.

Ayrica herhangi bir lokasyonda farkli ihtiyaclar icin kullanilan networkler olabilir. Ornegin production sunuculari, test sunuculari ve development sunuculari birinci lokasyonda bulunuyor olabilir. Bu noktada bu birinci lokasyon icin ek 3 adet Logical Network daha olusturulabilir.

Goruldugu gibi fiziksel network yapisinin birebir kopyasi olarak Logical Network olusturmak her zaman dogru sonucu vermeyebilir.

Bu noktada yalnizca asagidaki senaryo icin kesin konusabiliriz.

Eger tek bir lokasyonunuz varsa ve herhangi bir izolasyon dusunmuyorsaniz tek bir Logical Network olusturabilir ve tum sanal makinelerinizi bu Logical Network uzerinden gecirebilirsiniz.

Bunun disindaki senaryolar icin detayli bir tasarim yapilmasi sarttir. Ancak her zaman basit sekilde baslamak ve ardindan eklemeler yapmak mantikli bir secim olur. Bu yuzden VMM icerisinde tek bir Logical Network ile baslayip ardindan ek Logical Network eklemelerini gerceklestirebilirsiniz.

Aslinda neden tek bir Logical Network olusturup farkli subnetleri destekleyebileceksen neden birden fazla Logical Network olusturmam lazim sorusunun iki cevabi var:

  • Ileriki serilerde gorecegimiz Port Profile lar yalnizca Logical Network uzerinde uygulanabilir. Port Profile ile bir network uzerindeki bandwidth yada ek guvenlik aksiyonlari alinabilir. Bu sebeple bu tarz gereksinimler var ise tek bir Logical Network ile ilerleyemezsiniz.
  • Ikincisi de tabi ki yonetim anlaminda kolaylik. Tek bir Logical Network icerisinde onlarca subnet, vlan olusturmak VMM icerisinde yonetimi oldukca zorlastiracaktir. Bunun yerine ayrilmis sekilde farkli networkleri ayri logical Networkler icerisinde yonetmek daha kolay olacaktir.

Ancak bu konustugumuz senaryolar gercekten dagitilmis ve farkli izolasyon gereksinimleri olan networkler icin gecerlidir. Eger tek bir lokasyona sahip yada ek izolasyon talepleriniz yok ise basit sekilde tek bir Logical Network ile baslamak sizin icin daha mantikli bir secim olacaktir.

Logical Network icerisinde hangi bilesenler tanimlanabilir?

Bir Logical Network icinde asagida goruldugu gibi farkli Network Site lar (ilerleyen bolumlerde inceleyecegiz) ve her bir network site icerisinde de VLAN ve subnet tanimlari girilebilir.

image

Diger bolumlerde Logical Switch, Port Profile, IP Pool, VNic, Network Site gibi ek bilesenleri inceleyecegiz.

 

 

SCOM SDK – PowerShell – Creating monitor

 

icon_sdkOne of my customers wanted to monitor a 3rd party solution by monitoring events and asked if it`s possible with SCOM. As you probably know it`s one of the easiest tasks in SCOM to create monitors to monitor events on event viewer for specific or bunch of servers.

I was told to send them instructions to create a monitor based on Windows events. I started to get screenshots from create management pack and create monitor wizards, and then creating a group for the servers need to be monitored and finally overriding my monitor to enable monitoring for this specific computer group. At the end I realized it was about 30 page screenshots. Instead of sending these screenshots I though it would be much easier and sexy to send them a single PowerShell script to create a monitor. I thought SCOM Shell would have these cmdlets.

I was wrong.

Unfortunately, SCOM Shell doesn`t have any supported shell to create a unit monitor for Windows events. Then I decided to check SCOM SDK.

https://msdn.microsoft.com/en-us/library/hh329086.aspx

That was the first time for me to deal with SDK with PowerShell. SDK is much more powerful than PowerShell but you need to figure out how to deal with objects and methods.

There is an example to create a unit monitor by using SCOM SDK but as you may realize it`s written in C#. That was a good starting point for me.

https://msdn.microsoft.com/en-us/library/hh329015.aspx

So I started my journey, spent couple of hours to create my PowerShell script that uses SCOM SDK binaries. You can find the script below.

Please note that this is really an ugly script, no error handling, structure or sexy functions. This is just a sample to deal with SDK. If you are interested in to learn how to deal with SDK using PowerShell, it`s a good chance to open my script and C# example and see the integration between them.

Also SCOM MVP Tao Yang has done great job with Automating OpsMgr series on his blog http://blog.tyang.org/ .

He also shared with me an article yet to be written regarding monitor creation using SDK. It`s much more better than my ugly script 🙂 So if you need more details, follow Tao`s automation series.

My ugly script:

https://onedrive.live.com/redir?resid=3CAAB02B9CC620D5!57641&authkey=!AKbaImed7116Ig8&ithint=file%2cps1

 

We will be at System Center Universe 2015 in Basel!

Hitachi_SCU_Logo
This is my first time to attend System Center Universe in Basel. SCU is an annual conference and brings together the best of Microsoft community speakers and MSFTs to present topics around Microsoft System Center, Azure, Windows Server, Hyper-V and much more.

I`m also very excited as I will be there on behalf of the Hitachi Data Systems. We are traveling to Basel with my four colleagues dedicated for Microsoft virtualization and management solutions in Hitachi.

We will be at our Hitachi booth and will tell the community about why we believe our Hitachi Unified Compute Platform and it`s software management/orchestration layer UCP Director is the perfect solution out there for customers looking for flexibility and seamless integration with Microsoft System Center 2012 R2.

Hitachi`s Unified Compute Platform is a converged solution. All fabric components such as Hitachi servers, Hitachi storage, IP and SAN network are pre-configured and shipped by HDS. When you look at above description you may think it`s just an another converged platform. But it`s not only hardware. UCP Director is the management solution for Unified Compute Platform and offers end-to-end visibility to the entire fabric. It`s a software orchestration layer which is seamlessly integrated with Microsoft System Center Virtual Machine Manager and also vCenter.

UCP Director simply takes responsibility of all vendor specific infrastructure workflows below the hypervisor and provides end to end visibility.

eee

As a gold partner we will also have a 60 minutes break-out session on second day of the event at 09:15. My colleagues and myself will talk about Unified Compute Platform and Hitachi`s strategy regarding the management and orchestration layer. Here are the 3 demos we are planning to show to community in our session:

  • Software Defined Infrastructure with Hitachi UCP – General Overview
  • Provisioning fabric resources of your datacenter with UCP Director
  • Extending Microsoft System Center capabilities with UCP Director

Last demo will show how UCP and its management software UCP Director provides a seamless integration with Microsoft`s System Center suite. I`m planning to demo our SCOM Management Pack, SCO integration and consistent API that can be called easily through PowerShell allows you to orchestrate all your fabric components.

Come and chat with us at our Hitachi booth!

The Power of Automation

 

IT automation has always been one of the most important goal of IT managers to make their organization run efficiently. Automation simply ensures that all resources will be allocated according to business needs dynamically.

Hu wrote a post on HDS community where he talked about typical break down of IT budgets.

https://community.hds.com/community/innovation-center/hus-place/blog/2015/04/23/software-defined-infrastructure-enables-greater-innovation-in-it

 

ITSpending

I also found another diagram on Gartner`s IT metrics report that shows us organizations are spending %66 of their time and budget to just “run the business”

Gartner IT Metric Report

These two diagrams simply show us that in order to grow and transform our business we should focus on innovation and reduce time/money spending on operating. That’s obviously not an easy task to achieve and can only be possible if your infrastructure is flexible and adaptable for these changes.

Couple of years ago, it was a straightforward task for IT administrators to manage/operate less data, servers, and applications. But now, every single minute hundreds of terabytes of data are flowing from “things” to our systems. Since IoT concept will be an enabler to different domains including logistic, transportation, automotive, healthcare and smart cities, in the near future every single “thing” will be sensor attached and connected to the internet/cloud. Analysts expect that 50 to 100 billion devices will be connected to the Internet by 2020.

IT administrators should handle not only this huge amount of data but also underlying components such as storage, network, servers, applications, hypervisors so on.

Unfortunately without having a true software-defined infrastructure approach, managing, maintaining or innovating could be impossible.

As my colleagues Paul Meehan and Paula Phipps mention, to design a software-defined infrastructure approach, we can use three A`s

Automation: 29% of IT time is spent on tedious tasks. 39% of IT outages are due to human error. Hitachi midrange VSP family eliminates tedious manual tasks, reduces errors and lets administrators focus on revenue-generating activities.

Access: Access more data and solve real-world problems

Abstraction: Provide more services faster with more flexibility to support a diverse set of applications.

Couple of years ago I was involved in a project. Customer was working for government and had very sensitive public IIS web sites. Development team was developing updates every two weeks and sending MSI update package to Operations team. This team was responsible to achieve following actions:

  • RDP to different DMZ servers. All servers were belong to different forests therefore they need to use different credential for each server.
  • Copy MSI package to servers, unzip it (No check if MSI damaged/working or not)
  • Call network team and ask them to disable pool member on Load Balancer
  • For each web site, stop IIS service, change webconfig file, install MSI (no check if its installed or not, no check on event viewer or log files)
  • Start IIS service
  • Call network team to revert back configuration
  • Connect another IIS web site….

Operation team was spending around one or two days to update all web servers in production.

But I think time was not the main problem. The main problem was human errors. According the researches, most of the storage, server or service outages are caused by human errors. For the above scenario, if operation guy changes wrong line in webconfig or network guy removes wrong pool member, production environment will have service outage.

However, as using a correct automation method, organizations can easily reduce these statistics and save more money/time.   Remember the first “A” – Automation.

Microsoft is investing in automating, enabling the use of different automation solutions such as PowerShell, System Center Orchestrator and Service Management Automation. These automation solutions can be used to automate not only Microsoft workloads but also cross-platform Linux workloads, Network and Storage solutions.

I believe PowerShell is one of the most important initiatives by Microsoft in recent years. It`s a scripting language with an easy syntax and developed for System administrators. Almost all of the new Microsoft products, on-premise or Azure based, have native Windows PowerShell support.

Orchestrator is the new version of Opalis, acquired by Microsoft in 2009. It`s a process automation solution and comes with System Center suite. If you are using Virtual Machine Manager or Operations Manager you already have an IT Process Automation solution as well. Simple dashboard, drag&drop workflow design. You can also use .NET Script activity to run PowerShell scripts in workflows.

And Service Management Automation built-on PowerShell workflows. It`s a web based process automation tool designed to work with Windows Azure Pack, local version of Microsoft Azure in your datacenter. It allows you to build SMA workflows to create, monitor, deploy and manage resources in your private cloud environment.

When it comes to Software-Defined Infrastructure and Automation, Hitachi offers a wide range of solutions.  The Hitachi midrange VSP family provides the foundation for software-defined infrastructures by making automation and abstraction easy with an integrated portfolio of infrastructure automation and virtualization software.

If you are using Hitachi`s converged solution, you already know that how it simplifies management of private cloud and data center environments. You can also combine Microsoft System Center / Windows Azure Pack suite with UCP and it enables an end-to-end Private Cloud platform with self-service / orchestration / automation capabilities.

http://www.hds.com/solutions/virtualization/microsoft-hyper-v/hitachi-ucp-for-microsoft/

This solution automates the management of servers, networking components and storage using UCP Director, System Center and Microsoft adaptors.

Hitachi integrates with Microsoft applications to create a unified automation/management solution for Microsoft environments.

These are the available adaptors provided by Hitachi:

  • Hitachi Infrastructure Adapter for Microsoft System Center Operations Manager
  • Hitachi Adapter for Microsoft System Center Virtual Machine Manager
  • Hitachi Storage Adapter for Microsoft System Center Orchestrator
  • Hitachi Storage Adapter for Microsoft® SQL Server Remote BLOB Storage
  • Hitachi Storage Adapter for Microsoft Windows PowerShell
  • Hitachi Storage Adapter for Microsoft Volume ShadowCopy Service

Especially adapters for PowerShell and Orchestrator enables you to automate and orchestrate processes using together Hitachi and Microsoft solutions.

Hitachi Storage Adapter for Microsoft Windows PowerShell allows Hitachi storage administrators to use PowerShell cmdlets on Hitachi storage systems. Using cmdlets, administrators can create scripts to automate complex tasks.

Hitachi Storage Adapter for Microsoft Windows PowerShell

Using Hitachi Storage Adapter for Microsoft System Center Orchestrator you can easily extend the capabilities of System Center Orchestrator.

Hitachi Storage Adapter for Microsoft System Center Orchestrator

This plug-in provides:

  • Storage management and Hitachi NAS (HNSA) support
  • Virtualized storage management
  • Hitachi Content Platform (HCP) management

Each activity uses built-in PowerShell processes to run on remote server and allows you to create workflows/Runbooks to automate complex tasks in your datacenter.

It`s really good to see how two different vendor come together and built a complete management and automation solution. One more time hats-off to Hitachi engineers. They created really valuable plugins and integrations with Microsoft/System Center suite. These adaptors combines the power of Hitachi performance, reliability and agility with the productivity of Microsoft solutions.

SCCM 2012 – Failed to create SQL Server Certificate

During SCCM 2012 installation you may get “Failed to create SQL Server Certificate” error message in ConfigMgrSetup.log. This is a fatal error and will kill your setup process.

For me, it was a legacy failed SCCM installation that causes the problem. Just navigate to following directory C:ProgramDataMicrosoftCryptoRSAMachineKeys and delete related keys for your legacy installation.

Update Rollup 2 for System Center 2012 Service Pack 1

To manually download the update packages from Microsoft Update Catalog, go to the following Microsoft websites:

App Controller (KB2815569)

Download: http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2815569

· Issue 1: You cannot change the virtual machine network of deployed virtual machines.

· Issue 2: The network connection is set to None after you view the network properties of a deployed virtual.

· Issue 3: You cannot view the virtual networks for a virtual machine.

· Issue 4: When you change the virtual network in App Controller, you receive the following error message:

· Issue 5: You cannot copy VMs that have multiple processors or large amounts of memory from VMM to a Windows Azure.

· Issue 6: App Controller requires Microsoft Silverlight 5 but links to the download page for Silverlight 4.

· Issue 7: An argument null exception may occur if network connectivity is interrupted.

App Controller Setup (KB2823452)

Download: http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2823452

· Issue 1: App Controller cannot be installed if the Microsoft SQL Server database server name starts with a number.

· Issue 2: Setup incorrectly reports that the SQL Server database has insufficient disk space.

· Issue 3: Setup is unsuccessful when it tries to enable Internet Information Services (IIS).

Operations Manager (KB2826664)

Download: http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2826664

· Issue 1: The Web Console performance is very poor when a view is opened for the first time.

· Issue 2: The alert links do not open in the Web Console after Service Pack 1 is applied for Operations Manager.

· Issue 3: The Distributed Applications (DA) health state is incorrect in Diagram View.

· Issue 4: The Details Widget does not display data when it is viewed by using the SharePoint webpart.

· Issue 5: The renaming of the SCOM group in Group View will not work if the user language setting is not “English (United States).”

· Issue 6: An alert description that includes multibyte UTF-8 characters is not displayed correctly in the Alert Properties view.

· Issue 7: The Chinese (Taiwan) Web Console displays a wrong message.

· Issue 8: The APM to IntelliTrace conversion is broken when alerts are generated from dynamic module events

· Issue 9: Connectivity issues to System Center services are fixed.

· Issue 10: High CPU problems are experienced in Operations Manager UI.

· Issue 11: Query processor runs out of internal resources and cannot produce a query plan when you open Dashboard views.

· Issue 12: Path details are missing for “Objects by Performance.”

Operations Manager – UNIX and Linux Monitoring (Management Pack Update) (KB2828653)

Download: http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2828653

· Issue 1: The Solaris agent could run out of file descriptors when many multi-version file systems (MVFS) are mounted.

· Issue 2: Logical and physical disks are not discoverable on AIX-based computers when a disk device file is contained in a subdirectory.

· Issue 3: Rules and monitors that were created by using the UNIX/Linux Shell Command templates do not contain some parameters.

· Issue 4: Process monitors that were created by the UNIX/Linux Process Monitoring template cannot save in an existing management.

· Issue 5: The Linux agent cannot install on a CentOS or Oracle Linux host by using FIPS version of OpenSSL 0.9.8.

Service Manager (KB2828618)

Download: http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2828618

· Issue 1: If the number of “Manual Activities” displayed in the Service Manager Portal exceeds a certain limit, page loads may time out.

· Issue 2: Incorrect cleanup of a custom related type causes grooming on the EntityChangeLog table to stall.

· Issue 3: Service requests complete unexpectedly because of a race condition between workflows.

· Issue 4: The console crashes when you double-click a parent incident link on an extended incident class.

· Issue 5: PowerShell tasks that were created by using the authoring tool do not run because of an incorrect reference.

· Issue 6: The Exchange management pack is stuck in a Pending state after management pack synchronization.

Orchestrator (KB2828616)

Download: http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2828616

· Issue 1: The Monitor SNMP Trap activity publishes incorrect values for strings when a Microsoft SNMP Trap Service connection is used.

· Issue 2: Inconsistent results when you use Orchestrator to query an Oracle database.

Data Protection Manager (KB2822782)

Download: http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2822782

· Issue 1: An express full backup job in SC 2012 SP1 may stop responding on a Hyper-V cluster that has 600 or more VMs.

· Issue 2: When a SC 2012 SP1 item level restore operation is performed on a SharePoint the restore is unsuccessful.

· Issue 3: When you open DPM on a computer that is running SC 2012 SP1, the Welcome screen does not indicate the correct version of SP1.

· Issue 4: When you perform a disconnected installation of the DPM 2012 SP1 agent, you receive an error message.

· Issue 5: When you use DPM 2012 SP1 for tape backup, a checksum error may occur when the WriteMBC workflow is run.

· Issue 6: Backups of CSV volumes may be unsuccessful with metadata file corruption in DPM 2012 SP1.

· Issue 7: The DPM console may require more time to open than expected when many client systems are being protected.

WS-Management / WinRM Standards

In 2005, Microsoft submitted WS-Management for DMTF standardization along with 12 other companies.  It simply provides a standard for building XML messages using web service standards. It can be used to manage PCs, devices, Web services and other manageble entities. The messages that are provided by WS-Management are the conventions of Simple Object Access Protocol aka SOAP.

SOAP is a protocol specification relies on XML for its message format. It allows for the use of different transport protocols and uses HTTP as a transport protocol.

As for WinRM, it is the implementation of WS-Management protocol by Microsoft. It provides a firewall-friendly, HTTP based way to manage hardware and operating systems across different vendors. Moreover Windows PowerShell remote feature works on WinRM technology. You can manage not only Windows systems but also non-windows systems such as Unix computers. Windows systems are managed over WMI and non-windows systems are managed over DCOM.

All data that is captured using WinRM are formatted in XML as follow:

image

As of January 30, 2013, WS-Management was adopted as an international ISO/IEC standard.

http://webstore.ansi.org/RecordDetail.aspx?sku=ISO%2fIEC+17963%3a2013#.UU-C1Rwqw6s

That is really really important since that means using WS-Management protocol to manage complex systems will be much more simplified. All new System Center components and Windows Server 2012 aka Cloud OS are using WS-Management and Win-RM.

That is exactly means that, if you decide to manage your cloud environment with System Center and Windows Server 2012, you will also have ISO/IEC standard while managing remote systems.

In addition to this, Microsoft has designed Open Managed Infrastructure (OMI) as an open source project. It helps you to implement a standards-based management service into any device from a free open source package using WS-Management ISO/IEC standard.

Microsoft Özel Bulut (Private Cloud) Bileşenleri

Sanallaştırma teknolojileri ile birlikte, IT servislerinin konumlandırılması ve yönetiminde kullanılan ve IT harcamalarının büyük bir kısmını oluşturan fiziksel kaynaklar önemli ölçüde konsolide olmuştu. Sanallaştırma teknolojisinin bizi getirdiği son nokta ise Bulut teknolojileri.

Bulut teknolojisi adaptasyonu ile birlikte var olan veri merkezinizi uçtan uca yönetebilir, kaynak tüketen altyapı ve servisleri bulut ortamına taşıyabilir yada siz, veri merkezinizi kullanarak bulut üzerinden hosting hizmeti verebilirsiniz.

Bu noktada karşımıza Hybrid, Private ve Public Cloud kavramları çıkıyor.

Public Cloud servislerine aylık/yıllık üyelik gerçekleştirerek kaynaklarınızı bulut hizmet sağlayıcı üzerinden kullanabilir, ek kaynak ihtiyacı durumunda satın aldığınız pricing-model’e göre ek ücretler ödeyerek yapınıza kaynak ekleyebilirsiniz.

Private Cloud ise hali hazırda var olan altyapınızı, sanallaştırma teknolojileri ile donatmak ve tüm bu sanal altyapıyı uçtan uca yönetebilmek anlamına geliyor. Yönetmek kavramını biraz daha açmak gerekirse, tüm altyapıyı ve servisleri proaktif ve canlı olarak izlemeli, izlenen verileri analiz ederek gerekli aksiyonları alabilmeli, belirli aksiyonları kriterlere bağlayarak otomatize hale getirebilmelisiniz.

Bu iki teknolojinin bir arada kullanılmasını gerektiren yapılarda ise Hybrid Cloud tasarımı kullanılabilir.

Microsoft Private Cloud çözümü için güncel 2012 ürün ailesi ile birlikte çok önemli geliştirmeleri duyurdu. Private Cloud ile önceden manuel işlem gerçekleştirilmesini zorunlu kılan aksiyonlar otomatize edilmeli ve böylece operasyonel maliyetlerin azaltılması sağlanmalıdır. Tüm bu automation ise önceden oluşturulan servis katalogları ile birlikte self-service yani kendi kendine hizmet verebilecek şekilde tasarlanmalıdır. Kendi kendini yöneten IT altyapısı aynı zamanda organizasyon içerisinde bulunan diğer farklı departmanlara da SLA’ lere bağımlı kalarak hizmet verebilir olmalıdır.

Bu yazımızda yukarıdaki gereksinimleri karşılamak için Microsoft’un sunduğu bileşenleri inceleyelim.

Windows Server / Hyper-V

Windows Server 2012 Microsoft tarafından sunulan en güncel ve güvenli işletim sistemi olarak karşımıza çıkıyor. Sahip olduğu yenilenmiş ve geliştirilmiş Hyper-V rolü ile birlikte tüm Private Cloud altyapısı için Hypervisor yani sanallaştırma katmanı görevi görmektedir. 2012 versiyonu ile birlikte sunulan basitleştirilmiş merkezi yönetim ile birlikte tek bir konsol içerisinden ortamda bulunan tüm Windows Server 2012 sunucular kolaylıkla yönetilebilir. Bu aynı zamanda sanallaştırma altyapısı için de esnek, güvenli ve basit bir arayüz deneyimi sunmaktadır.

Microsoft System Center Virtual Machine Manager

System Center 2012 içerisinde yer alan Virtual Machine Manager ile varolan sanallaştırma sunucuları, sanal makineler yönetilebilir ve bulut mimarisi için hizmet dağıtımı yapılabilir. Sağladığı çoklu sanallaştırma ortam desteği ile kompleks ve karmaşık sanallaştırma ortamlarını dahi kolaylıkla yönetebilen SCVMM aynı zamanda oluşturulan servis şablonları ile sanal makine provision işlemlerini de rahatlıkla sağlayabilir.

Microsoft System Center App Controller

App Controller sayesinde, sunulan web konsolu kullanılarak hizmetler oluşturulabilir ve Private/Public Cloud ortamlarına dağıtılabilir. App Controller sayesinde farklı cloud ortamlarında bulunan Hybrid uygulamalar merkezi bir konsol içerisinden yönetilebilir.

Microsoft System Center Operations Manager

SCOM 2012 versiyonu veri merkezlerini uçtan uca izleyebilecek şekilde tasarlandı. Geliştirilen network monitoring özelliği ve hizmet seviyesi izleme yapabilmesi sayesinde Private Cloud ortamlarının performans ve availability durumlarını uçtan uca izleyebilirsiniz.

Microsoft System Center Orchestrator

Private Cloud ortamların iskeletini oluşturan, manuel işlemlerin otomatize edilmesi görevini gerçekleştiren ürün System Center Orchestrator’dır. Oluşturulan workflow/runbook lar ile private cloud ortamlarındaki kaynaklar talep edilen ihtiyaçlara, açılan çağrılara, monitoring tool’dan gelen alertlere göre oluşturulabilir. Orchestrator aynı zamanda Private Cloud ortamlarında bulunan Microsoft olmayan sistemlere de Integration Packler sayesinde erişebilir, bu sistemleri akışlar içerisine yerleştirebilir.

Microsoft System Center Service Manager

Service Manager, ITIL içerisinde yer alan IT Hizmet yönetimi yöntemlerini organizasyonunuzda uygulamanızı sağlar. Service Manager sayesinde cloud mimarisi içerisinde self-service yönetim tam anlamıyla sağlanmış olur. Varolan Private Cloud ortamınızda değişiklik kontrolü, olay yönetimi ve problem çözümünü tümleşik gelen processler ile sağlayabilirsiniz.

Microsoft System Center Data Protection Manager

Data Protection Manager ile birlikte disk bazlı yada tape bazlı veri koruması sağlayabilirsiniz. Private Cloud ortamınızda bulunan kritik sunuucların ve sanal makinelerin canlı yedeklerini alabilir, Bare Metal Recovery yapabilirsiniz.

Diğer yazılarımızda Cloud mimarisi fiyatlandırma modellerine ve değişen IT rollerine göz gezdireceğiz.

zp8497586rq