Cloud Native Artifact Registration via Object Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing application deployment and management systems face challenges in accessing and managing applications originating from outside their orchestrator environment, as they often require retrieving and extracting entire bundles due to limited selection of individual related applications, leading to inefficient resource usage and access complexities.
Innovation Solution
An orchestrator system that registers and manages application bundles by transferring them to an object storage within its environment, creating service specifications, and providing access through an API, allowing modules to access specific artifacts directly without needing the original storage location, thereby optimizing access and reducing computational and network resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the entire bundle is retrieved and extracted to access individual applications, then complete access to all related applications is achieved, but resource usage and processing time increase significantly
Solution Approach 1:
The patent extracts and stores metadata information about individual applications within the bundle separately in the service catalog. This allows the orchestrator to access only the specific application metadata needed without retrieving the entire bundle, thereby reducing resource usage while maintaining ease of access to individual applications.
Solution Approach 2:
The patent segments the bundle information by extracting and storing metadata for each individual application separately in the service catalog. This segmentation enables selective access to individual application metadata without requiring retrieval of the complete bundle, improving resource efficiency while maintaining operational ease.
2Loss of information
If the entire bundle is retrieved to access specific artifacts, then complete bundle information is obtained, but network and computational resources are wasted
Solution Approach 1:
The patent performs preliminary extraction and storage of application metadata in the service catalog before the orchestrator needs to access it. This preliminary action ensures that when an application needs to be accessed, only the specific metadata is retrieved from the catalog rather than retrieving the entire bundle, thus preventing waste of network and computational resources while ensuring information availability.
Solution Approach 2:
The patent creates a copy of the essential application metadata and stores it separately in the service catalog. This copy contains sufficient information for the orchestrator to access and manage applications without needing to retrieve the original bundle, thereby reducing network and computational resource consumption while maintaining complete access to necessary artifact information.
3Reliability
If modules access applications from external storage, then original application sources are maintained, but access complexity and security constraints increase
Solution Approach 1:
The patent introduces a service catalog as an intermediary between the external bundle storage and the orchestrator modules. The service catalog stores metadata information about applications and acts as a mediator that provides the orchestrator with necessary access information without requiring direct access to external storage locations, thereby reducing access complexity and managing security constraints while maintaining reliable access to application sources.
Data Source
AI summary
Application artifact registration is performed by receiving a bundle service specification configured for deployment of a software service in a cloud native environment, transferring a bundle from an original address indicated in the bundle service specification to an object storage at a principal address, attaching, to the bundle service specification, a bundle identifier and the principal address, extracting a plurality of artifacts from the bundle, each of the plurality of artifacts being stored in the object storage at a subordinate address, and creating one or more artifact service specifications, each artifact service specification representing one or more of the plurality of artifacts, each service specification representing the corresponding subordinate address, an artifact identifier, and an artifact type of each represented artifact.