Bare Metal IMS Workflow Using SSHD Agents for Scalable Upgrades
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Infrastructure Management Service (IMS) agents running on bare metal servers face challenges such as server-specific development, difficulty in large-scale upgrades, network outages during upgrades, and crashes leading to disrupted callflow and lifecycle management operations, with monitoring and corrective actions being complex and prone to bugs.
Innovation Solution
Implementing an Infrastructure Management Service (IMS) using abstract and concrete functions, where abstract functions define an order for workflows, and concrete functions execute specific business logic, leveraging a secure shell protocol daemon (SSHD) to manage bare metal servers, and utilizing a workflow manager and scheduler to orchestrate these functions, enabling zero-touch provisioning and lifecycle management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If IMS agents are designed per bare metal server to handle server-specific hardware and firmware interactions, then server compatibility and functionality are improved, but device complexity and difficulty of large-scale management increase
Solution Approach 1:
The IMS agent is segmented into a framework component and separate plugin modules. The framework provides core functionality and interfaces, while individual server-specific implementations are isolated in separate plugins. This allows the system to maintain server compatibility through specialized plugins without increasing overall management complexity, as plugins can be independently developed, deployed, and updated.
Solution Approach 2:
The IMS agent framework is designed as a universal platform that can work with multiple server types through standardized interfaces. The framework itself is server-agnostic and provides common lifecycle management capabilities, while server-specific behavior is achieved through pluggable adapters. This universal design reduces management complexity while maintaining adaptability across different hardware platforms.
2Adaptability or versatility
If IMS agents are recompiled to add new commands or configurations, then functionality is improved, but productivity and ease of operation deteriorate
Solution Approach 1:
The agent architecture separates core framework code from functional plugins. New functionality is added by developing and deploying new plugin modules rather than recompiling the entire agent. This segmentation allows rapid functional expansion without the overhead of full recompilation cycles, significantly improving productivity while maintaining enhanced functionality.
Solution Approach 2:
The agent system is designed to be dynamic, allowing plugins to be loaded, unloaded, and updated at runtime without requiring system recompilation or restart. This dynamic capability enables functional changes to be deployed quickly and efficiently, transforming the static recompilation model into a flexible plugin-based update mechanism that dramatically improves productivity.
3Reliability
If IMS agents run as systemd processes with monitoring, then reliability is improved, but device complexity increases
Solution Approach 1:
The health check and monitoring functionality is merged into the core agent framework rather than being implemented as separate external monitoring systems. The agent includes built-in health reporting capabilities that work seamlessly with systemd integration, providing reliable monitoring while reducing overall system complexity by consolidating functions within the agent itself.
Solution Approach 2:
The IMS agent implements self-monitoring and self-reporting capabilities through integrated health check functions. The agent automatically monitors its own status, detects issues, and reports problems without requiring external monitoring infrastructure. This self-service approach improves reliability while reducing device complexity by eliminating the need for separate monitoring systems.
4Manufacturing precision
If upgrades are performed during service windows with operations blocked, then manufacturing precision is improved, but loss of time increases
Solution Approach 1:
The upgrade process performs preliminary validation and preparation steps before applying changes. The system checks compatibility, validates configurations, and prepares rollback mechanisms in advance. This preliminary action ensures upgrade reliability by preventing failed installations, thereby reducing the need for repeated upgrade attempts and minimizing total service interruption time.
Solution Approach 2:
The upgrade implementation includes built-in rollback capabilities and safety mechanisms that are prepared beforehand. If an upgrade fails or encounters issues, the system can automatically revert to the previous state. This beforehand cushioning protects against upgrade failures, ensuring reliability while minimizing the duration of service interruptions by enabling quick recovery without extended manual intervention.
Data Source
AI summary
The present invention extends to methods, systems, and computer program products for implementing an Infrastructure Management Service (IMS). A selected abstract function workflow defines an order for implementing a plurality of different abstract functions for a use case. A bare metal server of a specified configuration is selected to receive the use case. A bare metal profile pack corresponding the specified configuration and use case is accessed. A plurality of different concrete functions within the bare metal profile pack and corresponding to the plurality of different abstract functions are identified. A secure shell protocol daemon acting as a an IMS agent at the bare metal server receives instructions from worker threads executing the plurality of different concrete functions to implement the use case on the bare metal server.