(Archived) How can I add a new container type to an existing environment

Owned by Moritz Rötter (Unlicensed)
Last updated: Jan 30, 2021 by Steffen Drya
2 min read

You have tried to access an archived page. Please go to the new https://root360.atlassian.net/wiki/spaces/KB to find more documents.











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 Freshdesk ticket and provide general information

  • Obtain a root360 cost estimate and accept it

  • Technical information in  Freshdesk ticket  provide

  •  Use the administrators of the root360 to integrate a set of instances of the new container type into the existing environment

  • Testing the instance (s)

  • Rollout / scale of the container type 

General information about Docker Container



  • Name

  • Brief description of the task of the container

Technical Information Docker Container

General



  • A unique name eg webfrontend, mobilebackend, admin

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

  • Is it a horizontally scalable 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, eg 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, eg 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.

  • B itte note: 

  •  

    • Final naming of the variables may change during the course of the vote. 

    • No secrets about the Freshdesk or in stored documents exchange!



Deployment



  • Which kind of deployment is used?

    • Blue-Green

    • Replacement



Logging



  • Optional

  • Cloudwatch can be used as default for logging.

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

For detailed description of logging for docker see: (Archived) How logs are aggregated for Docker setups



Checklist



Required information

Yes  / No 

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?







root360 Knowledge Base - This portal is hosted by Atlassian (atlassian.com | Privacy Policy)