Containers are a hot topic in the software industry at the moment. The technology promises rapid development and deployment of Web-scale applications. Although much is focused by the interest in Linux Containers, has the concept of other operating systems, with Windows Server 2016, the latest of the party is believed to join.
Earlier this year, Microsoft launched container support in its Windows Server 2016 Technical Preview. Moreover, the company with Docker worked on Windows-container in the core Docker container development, deployment, management, and integrated stack time.
XenServer already with the Docker Docker Linux Container embraced by integrating Stack administrators available to provide visibility, reporting and control of Docker container hosting environments. This capability will be extended to Windows Container in XenServer 7.0, released this week.
Before we look at how Windows container set up and use, the XenServer Docker integration let us take a brief look at some of the benefits of integration
monitoring and visibility - to know which VMs are in use for Docker hosting and what is actually executed on them containers. Today's interface is more of a "domestic" as "cattle", but it's fine for small to medium deployments and evaluations
Diagnosis -. Easy access to basic container information such as routed network ports originating Docker image name. This can research problems accelerate help where both or one may be involved the infrastructure and application layers
Runtime Management -. XenCenter using start, stop and interrupt application container. This function has a number of applications, in both evaluation and deployment scenarios including fast problematic applications
Demo
Let us, by a XenServer 7.0 environment ended to start - we need nothing special here, so I will use my favorite demo platform, an Intel NUC NUC5i5RYH with XenServer 7.0 is installed using a local SSD. XenServer of Docker integration is delivered as an additive package (XenServer add-on format). We can XenCenter the update wizard ( "Tools" menu, "Installing update ...") used to apply the pack. Browse to find the additional package (it is an ISO file) and follow the wizard through.
Once the installation is complete, we will pack listed in "Updates" Features "General" properties see Tab.
We now go ahead and Windows Server 2016 Technical Preview VM to install. I'm going to use Technical Preview 5 (SP5) for this demo. I have already set up an ISO storage repository and it contains the ISO TP5. We can install the VM in the usual manner; times using 4 GB of memory and 2 vCPUs for this demo. The installer has the ability to install with or without "Desktop Experience" - it will be easier to play with this with a proper UI that so can choose. If the Windows Installer type to select an installation asks we must choose. "Custom: Install Windows only", because we have not in our VM an existing Windows installation already
After the Windows installation is complete we can to the XenServer Tools (Agent and device drivers) in the normal manner install - you will notice that this way a quick and easy process compared to previous versions of XenServer
, now we in 2016 VM TP5 all have set a Windows server. and ready to go. We will now set up this VM Container Docker for operation. Microsoft have documentation and tools provided this easy to do (if you have previously tried on the previous Server 2016 Tech Previews then you may be pleasantly surprised by the improvements of TP5 Tooling). We are the instructions on the MSDN Web Container Micro follow - especially the "Scripted - Existing System". Instructions
PowerShell we use fetch install the script, and then run that omitted "-HyperV" option because we are going to use Windows Server Containers not Hyper-V Container .
wget -uri https://aka.ms/tp5/ Install container host -outfile C: Install ContainerHost.ps1
powershell.exe -noprofile -ExecutionPolicy bypass C: install ContainerHost.ps1
the installation script starts the VM and run again once we have registered in back to the desktop. The installation takes a few minutes because it has to be processed and the Windows Server Core Container base image to download.
Once this installation we have a functioning Windows Container has finished stack environment and Docker. The next step is to enable the VM for XenServer of the container management. This is similar in concept to the mechanism for Linux VMs Docker However for Windows, we used TLS connections to the Docker daemon instead of tunneling over SSH as in Linux case. To set this up, we can use the host console to retrieve the UUID of the VM and run prepare the script. We have the opportunity, our own TLS certificates but in this case we have the script its own self-signed certificates will have to generate.
The script is a CD image (ISO), which to be create the certificates automatically added to the Windows Server 2016 VM and a script to install it; it will then be prompted to re-run the VM this script.
We turn now to the VM go back and run the script.
to be switched on again after the host console and let it run the setup script complete a configured VM ready for use, we now have. We can test the integration, by working for the "Docker information" on the "General" tab VM search.
A good way container windows try over Docker is to follow the example IIS on MSDN container microsite. This example shows how to create containers and to change, includes initially by creating an image of the IIS Web server, and then create containers on this image based. We can improve on different TCP ports this example by running multiple IIS container on the same host. For this we need the port allocation in the "Docker run" modify commands, for example:
Docker run --name iisdemo81 -i -t -p 81:80 windowsservercoreiis cmd
docker run --name iisdemo82 -i -t -p 82:80 windowsservercoreiis cmd
in the video Take a look to see among those in action.
Once we have a few containers we run the effect of XenServer Docker can see integration. The most important elements to consider:
| The container in the infrastructure tree view showing the relationship between the containers and VMs |  | ,
| Lifecycle operations buttons administrator has control of each container is made possible. |  |
| Per Container detailed information, including port mappings to help with diagnosis. |  |
This includes our demo of Windows Server Container on XenServer 7.0. I encourage you to try it yourself. You can https://www.citrix.com/products/xenserver/overview.html and Windows Server 2016 at TP5 Downloads from XenServer 7.0 and the Container Management Pack, see https://www.microsoft.com/en- us / evalcenter / evaluate-windows-server-technical preview
resources
- https://msdn.microsoft.com/virtualization/windowscontainers/containers_welcome
- https://github.com/Microsoft/Virtualization-Documentation/blob/master/virtualization/windowscontainers/about/work_in_progress.md
- https://social.msdn.microsoft.com/forums/en-us/home?forum=windowscontainers
0 Komentar