WinDocks 1.0 Administration Guide

Transcription

1 WinDocks 1.0 Administration Guide This document is provided to support the Administration of WinDocks hosts. Please refer to the WinDocks User Guide for details on WinDocks client support. WinDocks is a port of the Docker daemon to Windows Server 2012 and Windows Server 2012 r2, and supports.net, SQL Server, and Windows application containers. WinDocks follows Microsoft s system architecture for support of multiple instances using shared DLL s (see: us/library/aa174516(v=sql.80).aspx ). WinDocks utilizes this architecture for container support with administrative instances of.net and SQL Server installed on the WinDocks host. While WinDocks 1.0 is supported with an automated installation, a review of the configuration of SQL Server and Windows Server used by WinDocks is provided below for background. WinDocks Clients: WinDocks interoperates with the standard Docker client version 1.7.0, and are available at: Windows clients: exe exe Mac clients: Linux client: WinDocks Administration: Server Resources: a server with 8 GB of RAM can support up to 40 running instances of SQL Server 2012 (with an average memory used per instance of 140 MB, and 100 GB of disk). SQL Server 2014 has a larger memory footprint of 550 MB, and will scale similarly with adequate RAM. WinDocks Standard (no SQL Server container support) runs well on a minimal Windows Server 2012 AWS VM (1 cpu, 1 GB of RAM, and 30 GB disk). The same configuration will also support SQL Server containers but requires a minimum of 50 GB of disk.

2 WinDocks Configuration: WinDocks includes Administrative controls for the following resources set in the WinDocks directory \config\node.cfg file. Ports are used for container access, and the default configuration is 200 ports. Ports are freed whenever a container is removed, so regular maintenance should include the removal of un- used containers. The server VM must be configured to allow for inbound support of the Docker daemon at port 2375, and for the port range required for container ports. SQL Server support includes an option for exposing SA passwords in the container return string. This is enabled with SHOW_SA_PASSWORD= 1 SQL Server support requires a mapping of WinDocks SQL container names to SQ Server instance names. This mapping is accomplished in the node.cfg file (ie., MSSQL- 2014_INSTANCE_NAME= SQL2014 ). The installed Instance Name can be found by opening SQL Management Studio, and noting the name as underlined in red in the image below. Administrative privileged commands can be defined and implemented in Dockerfiles through the node.cfg file. WinDocks ships with a sample command RUN_AS_ADMIN_CLONEDB= sdcli (a NetApp program that requires Administrative privilege). The sdcli executable needs to be installed in the Windows Server system path. Refer to the WinDocks User Guide for details on defining and using similar administrative privileged commands. WinDocks supports the use of network mounts for SQL Server databases. As is the case with Volume management of Docker on Linux, these mount points need to be monitored and cleaned up after containers are stopped or removed. WinDocks SQL Server containers release their mount points whenever the container is stopped or removed. SQL Server Install and Configuration (for support of WinDocks SQL+): WinDocks supports SQL Server 2008, 2008 R2, 2012, and Developer, Standard, and Enterprise versions. WinDocks does not require SQL Server, the support of SQL Server containers is optional. During the installation select the following options: DB Engine Client Tools Connectivity Management Tools Complete Client Tools Backward Compatibility Open SQL Server Configuration Manager, and ensure that IP4 is enabled (support for for local host work), and namedpipes are enabled. Server Configuration set the SQL Server Agent and SQL Server Database Engine to NT AUTHORITY/SYSTEM, and add current user. Set SQL Server Browser to Automatic, on and Database Engine to manual, off.

3 The red underline identifies the SQL Server Instance Name..NET and IIS Setup (Required for all WinDocks configurations): Begin with the Server Manager Add roles and features Step 2: Configure Application Server role with.net 2, 3, and 4.5 enabled, along with TCP Port Sharing, and IIS Support, Windows Process Activation with HTTP Activation and TcP Activation enabled, and DNS Server enabled. Step 3: Configure Web Server and Application Development as shown below.

4 Step 4: configure IIS Hostable Web core and Management Tools as shown below: Step 5: using the Features tab, configure the.net Framework support as shown below: The server features should reflect the following:

5 The final configured server roles should be as shown: This completes the Setup of NET and IIS for the WinDocks host. Additional WinDocks Setup Notes: WinDocks has been distributed in a zipped file (WinDocks.zip). Step 1: Windows will detect files that don t originate through a NTFS file transfer, so right click on the zip file, select Properties, and click on unblock. Installation of the zip package without unblocking will result in container start failures (the installation will appear to be trouble free, but the resulting system will not start containers reliably). Once the zip package has been unblocked, unzip the WinDocks file in a file folder of your choice, on the same partition as the Windows Server instance. Step 2: Double click on the install.bat file (this installs needed redistributable Visual Studio DLLs). If the DLL s are already present you can cancel this.

6 Step 3: Open a new Command prompt Window, navigate to the \bin folder and start the WinDocks daemon (docker.exe) with: >docker H tcp:// :2375 d Step 4: Install the Docker client binary in the file folder of your choice on a client machine. Open a new command prompt window, and establish client access to the daemon with the IP address of the host (refer to WinDocks 1.0 User Guide for supported client commands). Thank You! >docker H=tcp://[WinDocks.Host.IP.Address]:2375 command argument Image The WinDocks team appreciates your interest in WinDocks. For suggestions for new features, or technical support, contact us by at support@windocks.com