Currently, new containers New container types are being put into operation in cooperation with the administrators of the root360. The process is briefly explained below. It also lists what information should needs to be provided for root360 to prepare set up a new container type.

Process

• Request a new container type via a customer portal https://support.root360.cloud and provide general required information

• Provide technicel details on request

• (see questionnaire below)

• Discuss questions and technical details with root360

• When the requirements are clear, root360 will integrate a set of instances of the new container type into the existing environmentTesting your existing Elastic Container Service (ECS) cluster

• Test the instance(s)/service(s)

• Rollout / scale of Go-live and possibly scale the container type 

Required Information

General information about container

• A unique name type

New Container questionnaire

• Short, unique container name (e.g. webfrontend, mobilebackend frontend, admin):

• Brief Short description of the task of the container

Technical information about container

Resources

• Can a statement about minimum vCPU/ RAM/ SSD requirements be taken?

• Is it a horizontally scale-able application, or is it supported only by a vertical scale?

Network connectivity

• Is it possible to reach the container or container network within the environment? Are there possibly special requirements, e.g. port 5672 for RabbitMQ or 8080 for Tomcat?

• Is an accessibility of the container or container network from the Internet necessary? Are there possibly special requirements, e.g. port 5672 for RabbitMQ or 8080 for Tomcat?

• Is an external domain and/or an associated path (e.g. /service1 routes to container1) required for external accessibility?

Shared Storage

• Is a mountpoint needed to share data (with containers of the same type or others)container’s purpose:

• Resource requirements for the container instances in CPU-Units (1000 = 1 vCPU), RAM in MiB:

• How many container instances? Should we configure Scale-out/Autoscaling?

• If container autoscaling: minimum+maximum number of containers?

• On which port and with which protocol (http, https or tcp) will the container image listen on?

• If accessibility from the public internet: through which domain(s) and/or URL-Paths should the container type be accessible:

• Name a container healthcheck path. We check this path for a http(s) return code (usually 200) to continually validate the container state:

• Is a mount-point needed as a share?

• What is the volume of data and the requirements for the performance of the data storage?

Environment variables

• A collection of environment variables that must be available for the initial configuration of the container or its runtime.

• List required environment variables, e.g. database credentials, endpoints of other containers
  Do not send secrets through the customer service portal or through any other plain text

• communication channel. Please use https://

• otp.

• skaylink.

• com/to ensure a secure, encrypted one-time transmission.

Deployment

• Which kind of deployment is used?

  • Blue-Green

  • Replacement

Logging

For detailed description of logging for docker see Understanding container logging configuration

• Optional: Cloudwatch can be used as default for logging.

• Do the requirements for logging differ from the already existing agreements / containers?

Checklist

Required information

Yes ✅ / No ❌

Name and short description of the container

Technical requirements for the system (CPU, RAM, SSD-requirements)

On which port and with which protocol should the container be operated?

Network connectivity (accessibility of the container in the environment/from the internet)

Is a mount-point needed as a share? If yes, how big?

• Is access to other components needed

• (

• e.g. databases or S3 buckets)?

• Which kind of deployment is used? (blue/green or replacement)

• Logging: we use Cloudwatch by default. Do you want to use another logdriver? (Fargate: only Cloudwatch supported) (For detailed description of logging for docker see ​​​​​​​​Understanding container logging configuration.)

Related tutorials

Related components