Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
| Excerpt |
|---|
Currently, new containers 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 be provided to prepare a new container type. |
Currently, new containers 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 be provided to prepare a new container type.
Process
Request new container type via a customer portal https://support@root360support.root360.decloud and provide general information
Provide technicel details on request
root360 will integrate a set of instances of the new container type into the existing environment
Testing the instance (s)/service(s)
Rollout / scale of the container 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?
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)?
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 secrets to the customer service portal or any other plain text information. 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 | |
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? | |
Which environment variables are needed? | |
Is access to other components needed? (eg databases or S3 buckets) | |
Which kind of deployment is used? (blue/green or replacement) | |
Is Cloudwatch used for logging? Should something else used for it? |
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) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|