Rancher v1.3 Released: Windows container comes!

At the beginning of December 2016, when we released Rancher v1.2, we set a plan for "more frequent iterations" in the future. Just last week, Rancher v1.3 officially released! In addition to fixing some bugs in v1.2, it has several new features: 1) user interface repair, 2) DNS engine changes, 3) Kubernetes and related tools improvements.

Most importantly, in rancher v1.3, we begin to address a frequent request received from users: support for Windows 2016!

The support for Windows in Rancher v1.3 is still experimental and limited in scope, but it is an important step for Rancher labs to serve the customer's needs. Containers are increasingly being used in enterprises, and in the world, a significant portion of the workload is running on Windows servers and client systems. And, in the foreseeable future, this situation will not change.

The goal of Rancher Labs is to enable applications to truly achieve portability between the cloud and infrastructure and to run workloads on top of Windows containers, a key part of Rancher Labs ' vision.

Windows in Rancher Tutorial

To deploy Windowsin rancher, you first need to create a new environment in which the container orchestration needs to be set to Windows in the environment template.

Currently, rancher only supports the creation of containers on specific hosts. Features such as service discovery, health checks, metadata, DNS, and load balancers that may appear in cattle in the UI are not yet supported at this stage.

Note: Rancher has provided you with a default Windows environment template available. But if you create your own Windows environment template, you need to disable all other infrastructure services because they are currently incompatible with Windows.

Create a Windows environment

In the Environment drop-down list, clickManage Environment (Manage environment). To create a new environment, click AddEnvironment (add environment), provide a name, a description (optional), and then select the Environment template to use Windows as the orchestration. If you have access control turned on, you can add members here and select their member roles. Anyone in the members list can access your environment.

After you create a Windows environment, you need to navigate to the environment, where you can select the name of the environment in the context drop-down menu in the upper-left corner, or select "Switchto this environment (switch into this environment)" in the specific environment drop-down menu.

Note: Rancher supports multiple container orchestration frameworks, but at this stage, users cannot switch environments if existing services are running in some environments.

Add a Windows Host

To add a host to Windows, you need to first install a host that is running Windows Server with Docker.

In the Infrastructure tab, you will get a custom command to start the rancher Proxy service. You can follow the instructions to start the Rancher Agent service in Windows.

On the host, the proxy binaries will be downloaded to a folder named C:/Program Files/rancher, and the agent log will be located in C:/programdata/rancher/agent.log.

Remove a Windows Host

When you add a host to rancher, the rancher agent is part of it, and it is installed and registered on the host as a service. In order to reuse the host, you must delete the existing service. You can run the following commands in PowerShell. After you delete a service, you can reuse the host in a Windows environment.

& ' C:\Program Files\rancher\agent.exe '-unregister-service

The network in Windows

By default, we support NAT and transparent networks.

Currently, the default Windows environment template supports a transparent network named Transparent, which is created by running Docker network create-d transparent transparent.

If you are creating a transparent network with a different name, you need to use Windows to create a new environment template as a container orchestration. After you select Windows, you can change the name of the transparent network by clicking Editconfig. The default name is transparent. After you create an updated environment template, you can create a new environment to support the newly named

Transparent network. The UI will continue to use transparent as the default name, so you need to update the command to Docker network create-d transparent <new_name_in_template.

More feedback and sharing

We look forward to receiving your feedback on these early efforts as rancher Labs strives to advance to the needs of our service customers. We believe that only a wider range of feedback from users can make rancher products better.

Original source: Rancher Labs

This article is from the "12452495" blog, please be sure to keep this source http://12462495.blog.51cto.com/12452495/1892193

Rancher v1.3 Released: Windows container comes!