amb1ent/swarmmskit

Provisioning a Full MS NanoServer Cluster Swarm on Hyper-V with Consul + Vault + Private Registry ... all VMs (running on the last version Windows Server 2016 OS) integrated in an Active Directory Domain.

SwarmMSKit

1. Overview

2. SwarmMSKit Description - What the tool does and why it is useful

3. [Setup - The basics of getting started with SwarmMSKit]

   • Setup requirements
   • Beginning with SwarmMSKit

4. Usage - SwarmMSKit

5. [Video Tutorial](#SwarmMSKit-Youtube channel)

SwarmMSKit-Overview

Provisioning a Full MS NanoServer Cluster Swarm on Hyper-V + Consul + Vault + Private Registry ... all integrated in an Active Directory Domain and all the VM NanoServer on Hyper-V

SwarmMSKit-Description

Provisioning a Full MS NanoServer Cluster Swarm on Hyper-V with Consul Hashicorp software as Discovery Service, Vault Hashicorp software as a Secret Management Store and a Private Docker Registry host on Nexus OSS software. All VMs are integrated in an Active Directory Domain and all the VM NanoServer will running on Hyper-V.

We use the latest Docker Daemon Engine(1.14.0), Swarm (1.2.6), Vault(0.6.4), Consul(0.7.2) and Nexus OSS (3.2.0-01) versions.

Notice that I've built locally the swarm.exe binary with the latest version of docker/swarm : https://github.com/docker/swarm/archive/v1.2.6-rc1.zip

######docker -H tcp://10.1.0.24:2375 version : Client: Version: 1.14.0-dev API version: 1.26 Go version: go1.7.4 Git commit: 841968d Built: Wed Dec 28 22:39:42 2016 OS/Arch: windows/amd64

Server:
Version:      1.14.0-dev
API version:  1.26 (minimum version 1.24)
Go version:   go1.7.4
Git commit:   841968d
Built:        Wed Dec 28 22:39:42 2016
OS/Arch:      windows/amd64
Experimental: false

######docker -H tcp://10.1.0.24:2017 info Containers: 1 Running: 0 Paused: 0 Stopped: 1 Images: 2 Server Version: swarm/1.2.6 Role: primary Strategy: spread Filters: health, port, containerslots, dependency, affinity, constraint, whitelist Nodes: 2 Nano-Worker-1: 10.1.0.25:2375 └ ID: WTTJ:O36X:BCVK:UF3I:ZPG7:H6KH:HRXE:E52E:IZU3:VY6W:3KHV:YYAT └ Status: Healthy └ Containers: 1 (0 Running, 0 Paused, 1 Stopped) └ Reserved CPUs: 0 / 2 └ Reserved Memory: 0 B / 2.1 GiB └ Labels: kernelversion=10.0 14393 (14393.206.amd64fre.rs1_release.160915-0644), operatingsystem=Windows Server 2016 Datacenter, storagedriver=windowsfilter └ UpdatedAt: 2017-01-03T16:22:12Z └ ServerVersion: 1.14.0-dev Nano-Worker-2: 10.1.0.26:2375 └ ID: W4LK:ODLT:XYBL:DF7J:LOBJ:CU6G:CT2U:EAN6:UTGF:2VKM:JS52:7BNB └ Status: Healthy └ Containers: 0 (0 Running, 0 Paused, 0 Stopped) └ Reserved CPUs: 0 / 2 └ Reserved Memory: 0 B / 2.1 GiB └ Labels: kernelversion=10.0 14393 (14393.206.amd64fre.rs1_release.160915-0644), operatingsystem=Windows Server 2016 Datacenter, storagedriver=windowsfilter └ UpdatedAt: 2017-01-03T16:21:35Z └ ServerVersion: 1.14.0-dev

######vault status -address=http://10.1.0.24:8200 Sealed: true Key Shares: 5 Key Threshold: 3 Unseal Progress: 0 Version: 0.6.4

High-Availability Enabled: true
Mode: sealed

######consul members --rpc-addr=10.1.0.24:8400 Node Address Status Type Build Protocol DC Nano-Manager-1 10.1.0.24:8301 alive server 0.7.2 2 nano-swarm Nano-Worker-1 10.1.0.25:8301 alive client 0.7.2 2 nano-swarm Nano-Worker-2 10.1.0.26:8301 alive client 0.7.2 2 nano-swarm

The Windows Server 2016 has to be updated with the latest KB/Hotfixs.

For the NanoServer VHD, we will install these KB/Hotfixes too.

SwarmMSKit-Setup requirements

Windows 10 Pro or Entreprise Version (need Hyper-V) Windows Server 2016 Standard or Datacenter

Downlaod the folder SwarmMSKit which contain all the necessary binaries (latest KB/Hotfix, consul, vault, docker engine, nexus oss, swarm, nanoserver OSImage, etc ...) :

https://drive.google.com/drive/folders/0BzqZR1dT_FQgRlcxRG9PSEVmUVk?usp=sharing

SwarmMSKit - Beginning

######Set constants/variables in the SwarmMSKitProvisioning.ps1 file : WorkDir = "C:\SwarmMSKit" VMPath = "$global:WorkDir\VHD_Files" MediaPath = "$global:WorkDir\W2K16" ToolsSource = "$global:WorkDir\ToolsSource" ServicingPackages = "$global:WorkDir\ServicingPackages"

######IP Configuration of your first VM NanoServer and VM Switch Hyper-V configuration :

IPAddress      = "10.1.0.24"
GatewayAddress = "10.1.0.1"
SubnetMask     = "255.255.255.0"
DNSAddresses   = "10.1.0.1"
Subnet         = "10.1.0."
VMSwitch       = "InternalNetwork"

######System Configuration for our NanoServer VM, 2 vCPU and 2 Go Ram VMProcessor = 2 VMRam = 2048MB

######AD Credential which will be the admin NanoServer account Username = "FBOUKEZZOULA\Administrateur" clearadminPassword = "YourPassWord" DomainName = "FBOUKEZZOULA"

######Name prefix (Netbios/Hostname of the NanoServer and AD computer Names & Name in Hyper-V : Nano-Manager-1, Nano-Worker-1, Nano-Worker-2, etc...) ContainerHostName = "Nano-"

######Number of your Cluster Swarm members ServersInCluster = 3

######Our dedicated TCP Port for our Cluster Swarm Service SwarmClusterPort = "2017"

SwarmMSKit-Usage

######ExecutionPolicy Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope CurrentUser -Force or Set-ExecutionPolicy Unrestricted

######Connect to the new NanoServer VM with WinRM protocol : Set-Item WSMan:\localhost\Client\TrustedHosts -Value "*" -Force Restart-Service winrm

Then run the SwarmMSKitProvisioning.ps1 file ...

When it's finish ...

• set DOCKER_HOST=tcp://@YourFirstIP:@YourClusterSwarmPort

######Examples : set DOCKER_HOST=tcp://10.1.0.24:2017 docker images docker run -it nanoserver powershell docker run -it nanoserver cmd docker login -u admin -p admin123 @YourFirstIP:8123 docker push nanoserver

SwarmMSKit-Youtube channel

Stay tunned, very soon ...

Meanwhile, have a look on the screenshots (folder pics)