mountainss Cloud and Datacenter Management Blog

Microsoft SystemCenter blogsite about virtualization on-premises and Cloud


Leave a comment

#RedShirtAMS Wednesday 24th of May 2017 with @scottgu in Amsterdam #DevOps #Developers #Azure #AzureStack

 

Experience the newest technologies in Microsoft Azure by joining Scott Guthrie for sessions on how you can do more on the intelligent cloud. Scott will present a deep dive into Microsoft’s cloud services, advanced workloads and capabilities. He’ll do several demonstrations first-hand to show how these solutions can enable you to achieve more using the best of the Linux ecosystem and the best of the Windows ecosystem, together. Demos will include the latest in infrastructure – VM scale sets, managed disks, Hybridcloud, Azure Stack, enterprise mobility + security, Xamarin/mobile development, SQL, Data Lake, Cognitive Services, Machine Learning, AI, R, open source capabilities, Logic Apps, Power BI, Flow, developer tools and services, containers and more.

JOIN US

Wednesday 24th of May 2017, 09:15 AM – 16:00 PM, doors open at 08.45

Amsterdam RAI, Europaplein 2, 1078 GZ, Amsterdam

#RedShirtAMS
#MVPBuzz


Leave a comment

RUN you Own #Azure DevTest Labs in the Cloud #DevOps #Science #Linux #Containers

James TestLAB

Azure DevTest Labs is a service that helps developers and testers quickly create environments in Azure while minimizing waste and controlling cost. You can test the latest version of your application by quickly provisioning Windows and Linux environments using reusable templates and artifacts. Easily integrate your deployment pipeline with DevTest Labs to provision on-demand environments. Scale up your load testing by provisioning multiple test agents, and create pre-provisioned environments for training and demos.

Get started with Microsoft Azure DevTest Labs here

It’s really easy to setup your first Azure DevTest LAB.

Just click Create.

If you click on Automation options, you can create your own json file for Automation.

JSON Script for Automation to Create a Azure DevTest LAB

Getting Started information in your Azure TestLAB

I have Created a Windows Server 2016 VM with Containers

There are a lot of Azure DevTest Artifacts

You can copy the ARM Template for Automation

Container01 VM is running in my Azure DevTest LAB 😉

Container Images Ready to use in Azure DevTest LAB

For more Microsoft Azure Devtest Labs Documentation you can find here


Leave a comment

#WindowsContainer Host Deployment on #NanoServer #HyperV nested Virtualization

Hyper-V-Containers-Nested-Virtualization

Windows Containers on Hyper-V NanoServer nested Virtualization

Deployment Steps

Install Container Feature

The container feature can be installed on Windows Server 2016, or Windows Server 2016 Core, using Windows Server Manager or PowerShell.

To install the role using PowerShell, run the following command in an elevated PowerShell session.

Install Containers

PS C:\> Install-WindowsFeature containers

The system needs to be rebooted when the container role installation has completed.

PS C:\> shutdown /r

After the system has rebooted, use the Get-ContainerHost command to verify that the container role has successfully been installed:

Get-Containerhost

PS C:\> Get-ContainerHost

Prepare Nano Server

Deploying Nano Server involves creating a prepared virtual hard drive, which includes the Nano Server operating system, and additional feature packages. This guide quickly details preparing a Nano Server virtual hard drive, which can be used for Windows Containers.

For more information on Nano Server, and to explore different Nano Server deployment options, see the Nano Server Documentation.

Create a folder named nano.

PS C:\> New-Item -ItemType Directory c:\nano

Locate the NanoServerImageGenerator.psm1 and Convert-WindowsImage.ps1 files from the Nano Server folder, on the Windows Server Media. Copy these to c:\nano.

#Set path to Windows Server 2016 Media
PS C:\> $WindowsMedia = "C:\Users\Administrator\Downloads\WindowsServerTP4"

PS C:\> Copy-Item $WindowsMedia\NanoServer\Convert-WindowsImage.ps1 c:\nano
PS C:\> Copy-Item $WindowsMedia\NanoServer\NanoServerImageGenerator.psm1 c:\nano

Run the following to create a Nano Server virtual hard drive. The –Containers parameter indicates that the container package will be installed, and the –Compute parameter takes care of the Hyper-V package. Hyper-V is only required if Hyper-V containers will be created.

Import-Module

PS C:\> Import-Module C:\nano\NanoServerImageGenerator.psm1
PS C:\> New-NanoServerImage -MediaPath $WindowsMedia -BasePath c:\nano -TargetPath C:\nano\NanoContainer.vhdx -MaxSize 10GB -GuestDrivers -ReverseForwarders -Compute -Containers

When completed, create a virtual machine from the NanoContainer.vhdx file. This virtual machine will be running the Nano Server OS, with optional packages.

Configure Nested Virtualization

If the container host itself will be running on a Hyper-V virtual machine, and will also be hosting Hyper-V Containers, nested virtualization needs to be enabled. This can be completed with the following PowerShell command.

The virtual machines must be turned off when running this command.

PS C:\> Set-VMProcessor -VMName <container host vm> -ExposeVirtualizationExtensions $true

Configure Virtual Processors

If the container host itself will be running on a Hyper-V virtual machine, and will also be hosting Hyper-V Containers, the virtual machine will require at least two processors. This can be configured through the settings of the virtual machine, or with the following PowerShell script.

PS C:\> Set-VMProcessor –VMName <VM Name> -Count 2

Enable Hyper-V Role

If Hyper-V Containers will be deployed, the Hyper-V role needs to be enabled on the container host. If the container host is a virtual machine, ensure that nested virtualization has been enabled. The Hyper-V role can be installed on Windows Server 2016 or Windows Server 2016 Core using the following PowerShell command.

PS C:\> Install-WindowsFeature hyper-v

Create Virtual Switch

Each container needs to be attached to a virtual switch in order to communicate over a network. A virtual switch is created with the New-VMSwitch command. Containers support a virtual switch with type External or NAT.

This example creates a virtual switch with the name “Virtual Switch”, a type of NAT, and Nat Subnet of 172.16.0.0/12.

PS C:\> New-VMSwitch -Name "Virtual Switch" -SwitchType NAT -NATSubnetAddress 172.16.0.0/12

Configure NAT

In addition to creating a virtual switch, if the switch type is NAT, a NAT object needs to be created. This is completed using the New-NetNat command. This example creates a NAT object, with the name ContainerNat, and an address prefix that matches the NAT subnet assigned to the container switch.

Finally, if the container host is running inside of a Hyper-V virtual machine, MAC spoofing must be enable. This allows each container to receive an IP Address. To enable MAC address spoofing, run the following command on the Hyper-V host. The VMName property will be the name of the container host.

PS C:\> Get-VMNetworkAdapter -VMName <contianer host vm> | Set-VMNetworkAdapter -MacAddressSpoofing On

Install OS Images

An OS image is used as the base to any Windows Server or Hyper-V container. The image is used to deploy a container, which can then be modified, and captured into a new container image. OS images have been created with both Windows Server Core and Nano Server as the underlying operating system.

Container OS images can be found and installed using the ContainerProvider PowerShell module. Before using this module, it needs to be installed. The following commands can be used to install the module.

PS C:\> Install-PackageProvider ContainerProvider -Force

Return a list of images from PowerShell OneGet package manager:

PS C:\> Find-ContainerImage

Name                 Version                 Description
----                 -------                 -----------
NanoServer           10.0.10586.0            Container OS Image of Windows Server 2016 Techn...
WindowsServerCore    10.0.10586.0            Container OS Image of Windows Server 2016 Techn...

To download and install the Nano Server base OS image, run the following.

PS C:\> Install-ContainerImage -Name NanoServer -Version 10.0.10586.0
Downloaded in 0 hours, 0 minutes, 10 seconds.

Likewise, this command downloads and installs the Windows Server Core base OS image.

Issue: Save-ContainerImage and Install-ContainerImage cmdlets fail to work with a WindowsServerCore container image, from a remote PowerShell session.
Workaround: Logon to the machine using Remote Desktop and use Save-ContainerImage cmdlet directly.

PS C:\> Install-ContainerImage -Name WindowsServerCore -Version 10.0.10586.0
Downloaded in 0 hours, 2 minutes, 28 seconds.

Verify that the images have been installed using the Get-ContainerImage command.

PS C:\> Get-ContainerImage

Name              Publisher    Version      IsOSImage
----              ---------    -------      ---------
NanoServer        CN=Microsoft 10.0.10586.0 True
WindowsServerCore CN=Microsoft 10.0.10586.0 True

For more information on Container management See Windows Containers Documentation

MSFT Containers


Leave a comment

Microsoft Windows #Containers a New Ecosystem for #Developers and #ITpro

Container Channel9

Applications fuel innovation in the cloud and mobile era. Containers, and the ecosystem that is developing around them, will empower software developers to create the next generation of applications experiences, while IT Pros can use containers to provide standardized environments for their development, QA, and production teams, creating an infrastructure that is simpler to update and maintain.

The Containers Video Channel

DockerAndAzureEcosystem

Microsoft Windows Containers Documentation Site


Leave a comment

#Microsoft @shanselman Keynote: The Microsoft #Cloud Platform for Developers #Azure #Code #VisualStudio #DevOps

Just a command line or a click away – you now have the power to tap into dozens of global data centers and enact your will. Publish a website in seconds on Azure App Service, add Machine Learning intelligence with a couple of API calls, connect your internet of things or roll your own web stack from scratch in a VM – the choice is yours. In this demo-packed talk, Scott Hanselman will show you just how easy it for any developer to deliver mind blowing next-generation web applications and services powered by the cloud.

VisualStudio Online

Visual Studio Online Website { Connect();//2015 }


Leave a comment

#Microsoft Debug Diagnostic Tool v2 Update 2 for #ITPro #DevOps #MVPbuzz #Developers

Diag06

Microsoft Debug DiagTool

The Debug Diagnostic Tool (DebugDiag) is designed to assist in troubleshooting issues such as hangs, slow performance, memory leaks or memory fragmentation, and crashes in any user-mode process. The tool includes built-in analysis rules focused on Internet Information Services (IIS) applications, web data access components, COM+, SharePoint and related Microsoft technologies. Debugdiag 2.0 introduces a new analysis engine host with built-in reporting framework that can be accessed from .NET. This new analysis engine simplifies analysis rule development in .NET. Starting with Debugdiag 2.0, the analysis engine relies on Microsoft.Diagnostics.Runtime for .NET analysis.

Diag07

Add your Data files to Analyse

Diag09

Use ? for Help to get the job done

Diag10

Collect your Information for Trouble shooting

Diag11

Make your Own Debug Diag Rules

Diag12

The Help Function in the Tool can Help you understand the DiagTool

Here you can download the Microsoft Debug Diagnostic Tool v2 Update 2