Blog Archives

Yeni Baslayanlar Icin Windows Server 2016 Uzerinde Docker

Windows 10 ve Windows 2016 Server ile beraber Docker artik dogal olarak destekleniyor farkli bir sanallastirma yazilimina (virtualbox gibi) ihtiyac duyulmadan. Hatta Microsoft Docker On Windows degil, Docker artik Windows’un dogal bir parcasi olarak adlandiriyor.

Windows 10 development , Windows Server 2016’da production icin oneriliyor. Windows 10 kullanicilarinin Professional veya Enterprise (Anniversary Edition) kullanmalari gerekiyor.

Microsoft 2016 Server ile beraber iki tip Container desteklemeye basladi bunlardan biri Windows Server Container diger ise Hyper-V Container.

Hyper-V Container dedigimiz sey aslinda bir Hyper-V uzerinde yaratilmis sanal bir sunucu ve icersinde calisan Container. Soyle bir gecmise donersek Containerlar ciktiginda hep daha guvenli olsun diye bir sanal makiner icersinde calisirsa iyi olur, tam izolasyon olur durumlari vardi , halen bu yaklasim guncelligini koruyor.  Hyper-V Container kullanabilmek icinde haliyle Hyper-V role’unun kurulu olmasi gerekiyor. Keza Microsoft’da musterilerinin development icin Windows Container , production icin Hyper-V kullandigini soyluyor.

Windows Server Container‘da bizim host uzerinde kosacak, yine izole processler olacak, resimlersek Windows Server Container gordugunuz gibi Container Host uzerindeki Windows Kernal’i kullanirken , Hyper-V Containerlarin her biri tekil Windows Kernel uzerinde kosacaklar.

Read the rest of this entry

Advertisements

WAP, NVGRE and Hair pinning

Hello All ,

Today we faces connectivity issue between tenant networks behind same NVGRE GW.

Think that you have two tenants , Company A and Company B and two virtual networks and also NAT rule configured for remote access 3389 (RDP) to Company A VM can connect Company B VM but problem is two virtual networks are behind the same NVGRE GW.

Problem is single interface and To and From is behind a single interface , means source vm network coming from NVGRE outside interface and want to get in same interface to access other vm network .

This image could explain , BRIDGE is describing NVGRE , squares are vm networks and VM s behind

vepa

Pls check related settings on NVGRE GW node , active or passive , i guess its not important

 

PS C:\Users\Administrator.DORUKCOSN> Get-NetNatGlobal
InterRoutingDomainHairpinningMode : External

 

Then set it Local

PS C:\Users\Administrator.DORUKCOSN> Set-NetNatGlobal -InterRoutingDomainHairpinningMode Local
PS C:\Users\Administrator.DORUKCOSN>

Then go go go , try it now

External comes default , be care about it

Regards
VM