Container Deployment Location Determination Using Operation History
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Information processing systems using container virtualization face challenges in completing data synchronization for new container deployments within a desired time, leading to prolonged configuration changes and recovery from failures due to the need for data transfer between containers on different physical machines.
Innovation Solution
An information processing device that stores operation history information and uses this data to determine the optimal physical machine for deploying a new container based on the reason for its deployment, thereby avoiding unnecessary data re-transfer and reducing synchronization time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If containers are deployed on different physical machines from their storage, then resource utilization is improved, but data synchronization time increases
Solution Approach 1:
The system performs preliminary actions by identifying the deployment reason before actual deployment occurs. When a container is deployed due to failure recovery, the system proactively determines to deploy on the same physical machine as the failed container's storage. When deployed due to configuration changes, it proactively determines to deploy on a different physical machine. This preliminary determination prevents subsequent data re-transfer operations.
Solution Approach 2:
The system enables self-service by using operation history information to automatically determine optimal deployment locations without manual intervention. The deployment reason identification and physical machine determination processes are automated based on historical data, allowing the system to make intelligent decisions about container placement that optimize both resource utilization and data synchronization efficiency.
2Adaptability or versatility
If data is transferred between containers on different physical machines, then container flexibility is improved, but deployment time increases
Solution Approach 1:
The system performs preliminary determination of the deployment physical machine based on operation history information before actual container deployment. By identifying the deployment reason (failure recovery or configuration change) in advance, the system pre-determines the optimal physical machine location, preventing the need for data re-transfer after deployment and thus reducing overall deployment time.
3Ease of operation
If containers are deployed without considering deployment reason, then deployment simplicity is improved, but system recovery efficiency decreases
Solution Approach 1:
The system implements self-service by automatically identifying deployment reasons from operation history information and determining optimal physical machines without manual intervention. This automated approach maintains deployment simplicity while significantly improving system recovery efficiency, as the system intelligently selects appropriate deployment locations based on historical data.
Data Source
AI summary
An information processing device of deploying containers on a plurality of physical machines includes: memory configured to store operation history information, the operation history information corresponding to each of the containers deployed on the plurality of physical machines; and processor circuitry coupled to the memory, the processor circuitry being configured to perform processing, the processing including: in response that a first container is to be deployed, identifying from the operation history information a reason why the first container is to be deployed; and determining a physical machine from among the plurality of physical machines by using the reason identified to use the determined physical machine as a target physical machine on which the first container is to be deployed.