Platform Node Version Upgrade for Application Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cloud computing platforms, specifically PaaS, face challenges in application upgrades as they often provide fixed platform node versions, leading to compatibility issues where upgraded applications cannot run normally due to differing version requirements.
Innovation Solution
An application upgrade method that involves receiving a deployment request with version requirements, determining if the existing platform node version meets these requirements, and acquiring/upgrading the platform node to match the needed version, ensuring the application can be successfully updated.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If the PaaS CSP maintains a fixed version of the platform node for all applications, then the platform node version is stable and easy to manage, but the upgraded application cannot run normally when it requires a different platform node version
Solution Approach 1:
The patent segments the unified platform node management into individual platform node instances, each capable of running different versions. This allows the system to maintain multiple platform node versions simultaneously, enabling upgraded applications to run on compatible versions while other applications continue using the stable original version.
Solution Approach 2:
The patent introduces dynamic version management where platform node versions can be flexibly adjusted and upgraded on-demand. The system dynamically allocates appropriate platform node versions to applications based on their requirements, allowing the platform to adapt to different application version needs while maintaining overall stability.
2Reliability
If the platform node version is upgraded to meet the requirements of an upgraded application, then the application can run normally, but other applications that depend on the original platform node version may fail to run
Solution Approach 1:
The patent divides the platform node into multiple independent instances, each maintaining a specific version. This segmentation allows different applications to be assigned to platform node instances with appropriate versions, ensuring that upgraded applications can run on upgraded platform nodes while legacy applications continue running on original version platform nodes.
Solution Approach 2:
The patent applies local quality by allowing different platform node instances to have different versions tailored to specific application needs. Each application can be associated with a platform node instance that has the exact version compatibility it requires, rather than forcing a single universal version across all applications.
3Adaptability or versatility
If multiple versions of the platform node are maintained to support both old and upgraded applications, then application compatibility is improved, but the device complexity increases
Solution Approach 1:
The patent creates a universal platform node architecture that can host multiple versions through virtualization or containerization. The platform node system gains multi-functionality, capable of simultaneously supporting multiple application versions and their corresponding platform node versions through a unified management interface.
Solution Approach 2:
The patent introduces an intermediary layer (such as a virtualization layer or container orchestration system) that manages multiple platform node versions. This intermediary abstracts the complexity of version management, providing a unified interface for application deployment while handling the underlying complexity of coordinating multiple platform node versions.
Data Source
AI summary
Embodiments of the present invention provide an application upgrade method and an apparatus. The application upgrade method includes: receiving an application deployment request; determining a deployment package of a to-be-deployed application; determining that a version of a first platform node is below a version requirement of a node template of the to-be-deployment application for a first platform node template; acquiring a first platform node upgrade package that meets the version requirement of the node template of the to-be-deployed application for the first platform node template; upgrading the first platform node indicated by an identifier of the first platform node by using the first platform node upgrade package; determining an identifier of a to-be-upgraded application node; and upgrading the application node indicated by the identifier of the to-be-upgraded application node by using the deployment package of the to-be-deployed application.