Rancher(Docker Container Management)

(Note)This service has been terminated. Currently Container Service is being offered as individual integrated service. For details, please contact sales representatives.

Service Menu Overview

Service Menu Overview

This menu offers the Container-type Virtualization Technology using Docker (hereafter, Dock Container Execution Infrastructure).
In addition to the features such as high-speed start up, system storage/reproduction and portability, that are advantages of the Docker Container, this menu has adopted Rancher provided by Rancher Labs to realize simple operation by graphical Web interface and storage/reproduction in units of systems by Rancher Catalog.
After subscription request of this menu, customers can use the Docker Container immediately. Also, as NTT Com performs operation management of the Docker Container Execution Infrastructure, its operational workload by customers will be reduced.
In addition to Docker Container and Rancher, technical supports for orchestration tools such as Cattle and Kubernetes are available, so that customers can use Docker Container with peace of mind.
_images/rancher_overview.png

Company names and product names described here are registered trademarks or trademarks of each company.

Service Menu Features

Operational management of Docker Container Execution Infrastructure and offer of technical supports
  • The Dock Container Execution Infrastructure that can be used immediately is available. Building works by customers such as installation and setting of the Docker Host are not required.

  • Maintenance and management work of Dock Container Execution Infrastructure is covered by NTT Com. It reduces customers’ operational workload.

  • In addition to Docker and Rancher, technical support will be provided on orchestration tools such as Cattle of Rancher Labs, and on Kubernetes being developed by Google and others.

Provides Docker Container Management Tool, Rancher
  • Rancher offers Web UI and REST API for Docker Container environment management. By using Rancher, you can easily manage Docker Container and Docker Host.

  • The Orchestration Tool realizes failover, scaling, scheduling, load balancer, service discovery, security and so on in the Docker Container environment.
    Rancher can manage the Orchestration Tool. Cattle or Kubernetes is available as an Orchestration Tool.
  • Using various catalogs provided from Rancher communities, you can easily build a system comprised of multiple containers. With this function, the customer’s system can be copied or restored with ease.

  • You can connect a NFS storage to Rancher, and mount the Rancher to Docker Container. This function allows you to save data existing in Docker Container.

Cooperation with Enterprise Cloud menus and Network Services
  • By using Enterprise Cloud Virtual Server as the Docker Container Execution Infrastructure, seamless cooperation with other Enterprise Cloud menus becomes possible.

  • Use of Arcstar Universal One realized a secure Docker Container environment.

Description of Respective Menus

System configuration

Image of this menu is shown below.
The Docker Container Execution Infrastructure provided by this menu is constructed on a Tenant for Docker Container service (hereafter, Docker Container Tenant), which is one of the Enterprise Cloud Virtual Server Environments.
The Docker Container Execution Infrastructure provided by this menu is constructed on a Tenant for Docker Container service (hereafter, Docker Container Tenant), which is one of the Enterprise Cloud Virtual Server Environments.
_images/rancher_tenant.png

Explanation of the components

Explanation of the standard components of this menu

Docker Host
A virtual server that provides resources to the Dock Container.
Docker Container operates on the Docker Host.
The Docker Host has cluster configuration and can be added up to the specified value as customers require. Also, a Flavor (to be described later) can be applied to the Docker Host.

Docker Container
Application execution environment that works on the Docker Host.
Environment in the Docker Container is isolated to each other and a change of settings in a Docker Container will not affect settings of other Docker Containers.

Rancher server and Rancher Database server
Application server and database server for unified management of Docker Container Execution Infrastructure and Docker Container Environment.
Docker Host, Docker Container and Orchestration Tool can be controlled by accessing Rancher server by Web UI or REST API.

Customer Tenant
Customer Tenant is a tenant where resources that the customer has the management authority are deployed. (For tenant, refer to the Service Document “Management Functions”.)
The customer can freely create and delete resources such as a virtual server.
To use the Docker Container Service, a Customer Tenant is required.

Docker Container Tenant
A tenant where resources of Docker Container Execution Infrastructure are deployed.
It is comprised of the components of the Docker Container Execution Environment such as Docker Host, Firewall and Logical Network. The Customer can create and delete a Docker Host (virtual server) and a Docker Container via Web UI and REST API.
The ownership of the tenant, however, belongs to NTT Com and NTT Com will fix troubles and monitor the infrastructure.
Multiple Docker Container Tenants can be created. And multiple Docker Container Tenants can be connected to 1 Customer Tenant.

Management Tenant
A tenant where servers to operate and monitor Docker Tenant Execution Infrastructures are deployed.
Resources of this tenant are used by NTT Com and customers cannot use them.

Monitoring Server
A server to monitor Rancher servers, Rancher Database servers and Docker Hosts belonging to Docker Container Tenant.

Maintenance Server
A server to perform maintenance of Rancher servers, Rancher Database servers and Docker Hosts belonging to Docker Container Tenant.

Firewall
Customer Tenant and Docker Container Tenant are connected via a firewall.
This firewall prevents illegal accesses to the Docker Container Execution Infrastructure.

Logical Network
Connects between each component in each tenant.

Components to be prepared by the Customer (option)

Docker Container Storage
A storage to save data on Docker Container.
Data on Docker Container will be deleted at the timing of Docker Container deletion. NFS storage is available to eternalize data on Docker Container.
As a NFS storage, a virtual server that has launched NFS service, file storage (standard) menu provided by Enterprise Cloud, and so on are available.

Docker Hub / Docker Store
Registries where Docker images created by individuals, communities and enterprises and provided by Docker are stored.
Various application environments can be reproduced by using Docker Images stored in Docker Hub or Docker Store. And a connection to Docker Hub is required to update Docker Host and Rancher server.
Internet connectivity is required for the connectivity to Docker Hub or Docker Store.

Functions

Provided platform

Platform

Linux

Provided functions

Provision of Docker Container Execution Infrastructure
Provides Docker Host and Logical Network environment where Docker Container can be executed.
Initial, minimum and maximum No. of units of Docker Host are as follows. Deletion or addition of Docker Hosts to below the minimum or to above the maximum No. of units is not allowed.

No. of units used

No. of minimum units

No. of maximum units

3 3 20

Also, a Flavor that will be described later can be assigned to the Docker Host.

Provides Docker Container Management (Rancher) function
Rancher is offered as a tool to manage and to provide Docker Container Execution Infrastructure.
Functions of Rancher are realized by Rancher server. Typical functions of Rancher are as follows.

Name of Functions

Details

Notes

Docker Container Management

Offers Rancher Web UI and REST API for Docker Container management.
・Create and delete Docker Container
・Monitor Docker Container
 

Docker Host Management

Offers Rancher Web UI and REST API for Docker Container management.
・Create and delete Docker Host
・Monitor Docker Host

Orchestration Tool Management

Provides orchestration Tool Management function
•Realize functions of Docker Container Failover, scaling, scheduling, Load balancer, Service discovery, security and so on by using Orchestration Tool.
•As an Orchestration Tool, either Cattle which is Rancher standard, or Kubernetes can be selected.

Docker Imaging and Restoration

•Offers Docker Imaging function to save and restore Docker Container environment.
•Restores Docker Container from Docker image onto Docker Container Execution Infrastructure.

Rancher Cataloging and Restoration

Offers Rancher Cataloging function to save and restore Docker Container environment.
•Saves the system configuration as a Rancher Catalog.
•Restores the system from a Rancher Catalog.

NFS Storage connection
Offers NFS storage function mountable to Docker Container.
•Can connect NFS storage to Docker Host.
•NFS storage area connected to Docker Host can be mounted to Docker Container and can read/write data from/to the Docker Container. This function allows you to eternalize data in Docker Container if the Docker Container stops.

Menu

Compute(Docker Host)

Available Flavors(Plans) for Docker Host are as below.

Note

A Flavor assigned to a Docker Host cannot be changed after the creation of the Docker Host. If the change is required, you need to delete the Docker Host once, specify the flavor again, and create the Docker Host.

Docker Host Flavor

vCPU

GB
2CPU-8GB 2 8
4CPU-16GB 4 16
8CPU-32GB 8 32
16CPU-64GB 16 64
32CPU-128GB 32 128
Volume type, partition structure and size of Docker Host are fixed. The contents are as follows.
As the volume of Docker Host is a root disk, when Docker Host is deleted, Docker Image and data in Docker Container will be deleted.

Volume Type of Docker Host

Pertition

Capacity

Root Disk

OS space

100GB
 

Docker image space

200GB
 

Docker Container space

200GB
    500GB

Orchestration Tool

Available orchestration tools are as below.

Orchestration Tool

Overvie

Rancher Cattle
Orchestration tool provided by Rancher Labs.
As Rancher Web UI and REST API provided as means of access to Docker Container environment are implemented with an assumption that Cattle will be used, selection of Cattle is recommended to make the best use of the functions of Rancher.
Kubernetes
The Orchestration tool being developed by Google and others.
Many groups participate to the development and Kubernetes is one of the tools that aim the defact standard position as a Docker Container Orchestration Tool.
It is recommended to users well versed in, or already using, Kubernetes.
When Kubernetes is used, most of the Rancher Web UI functions are replaced by Web UI provided by Kubernetes.

Depending on the selection of the orchestration tool, differences will occur in usable user interfaces. The main contents are as follows.

Subscription

Subscription

Customers can subscribe from ECL2.0 portal.

Flow until Start of Service

Flow until start of service of this menu is as follows.

  1. The Customer requests subscription of this menu from ECL2.0 portal. Specify the initial parameters (to be described later) such as the Flavor of the Docker Host deployed initially at the subscription request.

  2. We will build a Docker container tenant at our company. The construction period is up to 10 business days.

  3. After building a Docker Container Tenant, the Docker Container Tenant and the Customer Tenant are connected.

  4. URL to the Rancher server is informed. The operation in the Docker Container environment becomes possible by accessing the URL with a Web browser or REST client from a virtual server on the Customer’s Tenant or from a terminal on a network connected to the Customer Tenant.

Initial parameter

The items (initial parameters) that you need to specify at the time of menu subscription are as follows.

No.

Initial parameter

 

Required Item

Input format

Description

1

Logical Network(SubnetA)

Logical Network name

Y

Select via pull down from logical netowork on customer’s tenant.

Specify the logical network on the Customer Tenant to be connected to the logical network of a Docker Container Tenant.
Customer is required to create logical network on customer’s tenant in advance.
Only logical network for data plan can be selected.
2  

Subnet name

Y

Select via pull down from subnet on customer’s tenant.

Specify the logical network on the Customer Tenant to be connected to the logical network of a Docker Container Tenant.
Customer is required to create logical network on customer’s tenant in advance.
Only the subnet with DHCP enabled can be selected.
3  

Default Gateway

Y

aaa.bbb.ccc.ddd format

 
4

Tenant name

  Y

Half-width alphanumeric

Specify the name of Docker Container Tenant.

5

Docker Host Flavor

  Y

Flavor of Docker Host(Appendix reference)

Specify the Flavor of the Docker Host at the initial build. The same Flavor will be set to all the initial units of the Docker Host.

6

Logical Network(Subnet B)

Network Address

Y

aaa.bbb.ccc.ddd format

Specify the logical network information (network address, subnet mask) of the Docker Container Tenant. A subnet mask with 7 bit or more is assigned to host part of the IP address (CIDR notation: /25) is required.

7  

Subnetmask

Y

Fixed

Subnetmask is fixed as /24.

8

Firewall

Firewall1 IP address

Y

aaa.bbb.ccc.ddd format

Specify customer Tenant side IP address of Firewall1.

9  

Firewall2 Ipaddress

Y

aaa.bbb.ccc.ddd format

Specify customer Tenant side IP address of Firewall1.

10  

Virtual IP Address

Y

aaa.bbb.ccc.ddd format

Specify customer Tenant side IP address of Firewall1 and 2.

11   VRID(Virtual Router ID) Y

Half-width characters for numbers(1-255)

Specify Identifier(ID)of VRRP(Virtual Router Redundancy Protocol)group.
If multiple Docker Container Tenants are connected to the same logical network of the Customer, VRID should not overlap.
12

External Server

Primary DNS IP address

Y

aaa.bbb.ccc.ddd format

Specify the IP address of the primary DNS server referenced by the Docker Container Tenant server.

13  

Secondary DNS IP address

N

aaa.bbb.ccc.ddd format

Specify the IP address of the secondary DNS server referenced by the Docker Container Tenant server.

14  

NTP IP address

Y

aaa.bbb.ccc.ddd format

Specify the NTP server address referenced by the Docker Container Tenant server.

15

Admin User

User Name

Y

Half-width alphanumeric, Symbolic characters(@, +, -, .(Period,、_(underscore))

Specify the name of admin user and password of Rancher control panel.
You can assign one Admin User for one Rancher server.
16  

Password

Y

Half-width alphanumeric, Symbolic characters(! #@=^[]{}+-?._)

 
17

Orchestration Tool

  Y

Either Cattle or Kubernetes

Specify the Orchestration Tool to use in the Docker Container environment.

_images/rancher_orderparams.png

Terms And Conditions

Combination with other menus

This menu does not set the conditions for combination with other menus.

Minimum Usage Period

There is no minimum use period in this menu.

Pricing

Initial Fee

There is no initial fee required in this menu.

Monthly Fees

Billing Structures

The monthly fee will be charged according to the following formula.

“Basic charge” + “Charge for Docker Host 1” + … + “Charge for Docker Host n”
Here, from “Basic charge” to “Charge for Docker Host n” are “Charge per use (per minute) with monthly cap”.

Billed Items

Resources in Docker Container Tenant are items to charge.
The charge will vary in accordance with the number of Docker Hosts and assigned Flavors.

Quality of Service

Support content and coverage

  • Investigation of and recovery from troubles occurred in the Docker Container Execution Infrastructure such as Docker Host, Firewall and Logical Network. However, investigation of and recovery from troubles occurred in the Docker Container that the Customer has created are outside of the scope.

  • Technical support of the applications provided in this menu, and investigation of and recovery from troubles The target applications are as follows.

    • Docker
    • Rancher
    • Orchestration Tool(Cattle or Kubernetes)

  • Trouble prevention to Docker Container environment and update work of Docker Host application, Rancher server application and Orchestration Tool (Cattle or Kubernetes) for addition of functions. Update work is conducted without notification to customers.

SLA

The SLA of this menu is based on the standardized SLA for Enterprise Cloud 2.0; for the details please refer to the Service Description of SLA.

Restrictions

  • The initial parameters specified at the time of subscription request of this menu cannot be changed after the start of the service excluding Docker Container Tenant name and the Admin User password of the Rancher server. To change the initial parameters, you need to terminate the Docker Container Tenant once and to request the subscription again.

  • Multiple Docker Container Tenants can be connected to 1 Customer Tenant. But multiple Customer Tenants can not be connected to a single Docker Container Tenant.

  • The Rancher server is managed only by the Docker host in the Docker container tenant to which the Rancher server belongs. Therefore, the Rancher server can not manage Docker hosts across tenants or regions.

  • If Rancher server or Rancher Database server has stopped, Docker Container will not stop but operation from the Customer Tenant to the Docker Container and to the Host will become impossible.

  • A Flavor assigned to a Docker Host cannot be changed after the creation of the Docker Host. If the change is required, you need to create a Docker Host with the new flavor, then to delete the unnecessary Docker Host with the old flavor.

  • Volume of Docker Host is root disk. When a Docker Host is deleted, the stored data will be deleted.

  • Size and partition structure of a volume of Docker Host (root disk) cannot be changed.

  • When Docker image area of a Docker Host is full, new download of a Docker image to the Docker Host will fail.

  • When Docker Container area of a Docker Host is full, deployment of a Docker Container to the Docker Host will fail.

  • Image acquisition (snapshot acquisition) of the Docker Host itself is not possible.

  • To save data existing in Docker Container, an NFS storage connected to the Docker Host is required separately.

  • A Docker image cannot be saved to an NFS storage connected to a Docker Host. To save a Docker image created by the Customer, either use Docker Host or prepare Docker registry separately.

  • Internet connectivity is required to use Docker Hub / Docker Store.

  • For name resolution of a Host name allocated to a Docker Container, a DNS server is required separately.

  • For new deployment of a Docker Container and a Docker Host, the DNS server should be in a condition where name resolution is possible.

  • You cannot login directly to the OS of a server (Rancher server, Rancher Database server and Docker Host) deployed in Docker Container Tenant.

  • The default setting of the access protocol to Rancher server is HTTP (Hypertext Transfer Protocol).

  • The Customer cannot specify the IP addresses of servers connected to the Logical Network of Docker Container Tenant (Rancher server, Rancher Database server and Docker Host) and those of Docker Container Tenant side of the Firewall 1 and 2.

  • The Customer cannot specify the versions of Docker Host application, Rancher server application and Orchestration Tool (Cattle or Kubernetes). Versions of these at the time of provision may be changed without advanced notice.

  • Docker Host application, Rancher server application and Orchestration Tool (Cattle or Kubernetes) may be updated without advanced notice.

  • For the update of Docker Host application, Rancher server application and Orchestration Tool (Cattle or Kubernetes), Internet connectivity is required.

  • If update of Docker Host application, Rancher server application and Orchestration Tool (Cattle or Kubernetes) is not applied, NTT Com may decline support on those products.

  • The number of Admin Users of a Rancher server is one. You cannot create multiple users.

  • Performances of the services offered in this menu are best-effort type and are not guaranteed.

  • Responses in technical support, trouble investigation and recovery support are best-effort type and response deadline is not defined.

  • NTT Com will not assume any responsibility for operation and license of applications in distributed Docker images, and of applications that the Customer installed in Docker Container. Applications in Docker Container are outside of the support coverage.