Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
| Excerpt |
|---|
Currently, new New containers 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. |
Currently, new New containers 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 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 type
Required Information
General information about container
A unique name e.g. webfrontend, mobilebackend, admin
Brief description of the task of the container
Technical information about container
Resources
Can a statement about minimum vCPU/ RAM/ SSD requirements be taken?
Required Resources
For each container instance (“task”) of the container type: how much CPU and Memory reservation is required
Is it a horizontally scale-able (add additional tasks) application, or is it supported only by a vertical scale (increase the size of a single task)?
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)?
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.
| Note |
|---|
Do not provide any send secrets to through the customer service portal or through any other plain text informationcommunication channel. Please use https://share.root360.cloud 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
New Container type questionnaire
Required information | ||||
|---|---|---|---|---|
| 1 | Short, unique container name (e.g. | |||
| 2 | Short description of the container’s purpose | |||
| 3 | Resource requirements for the container instances in CPU-Units (1000 = 1vCPU), RAM in MiB. | |||
| 4 | How many container instances? Should we configure Scale-out/Autoscaling? | |||
| 5 | On which port and with which protocol (http or https) should the container be operated? | |||
| 6 | Network connectivity (accessibility of the container in the environment/from the public internet) | |||
| 7 | If accessibility from the public internet: through which domain(s) and/or URL-Paths should the container type be accessible | |||
| 8 | Name a container healthcheck path. We check this path for a http(s) return code (usually | |||
| 9 | Is a mount-point needed as a share? If yes, how big?Which environment variables are needed? What is the volume of data and the requirements for the performance of the data storage? | |||
| 10 | List required environment variables, e.g. database credentials, endpoints of other containers
| |||
| 11 | Is access to other components needed ? (eg e.g. databases or S3 buckets)? | |||
| 12 | Which kind of deployment is used? (blue/green or replacement)Is Cloudwatch used for logging? Should something else used for it? | |||
| 13 | Logging: we use Cloudwatch by default. Do you want to use another logdriver? For detailed description of logging for docker see Understanding container logging configuration |
Related tutorials
| Filter by label (Content by label) | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Related components
| Filter by label (Content by label) | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Table of Contents | ||
|---|---|---|
|
| Filter by label (Content by label) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|