Docker Plugin Deployment for Third-Party HCI Extensions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing HCI platforms lack support for widely accepted methodologies in creating cloud native applications, limiting plugin development to authorized parties and restricting the creation of extended functionalities.
Innovation Solution
A method is introduced to create, register, and save Docker images for HCI platform plugins, enabling third-party developers to develop cloud-native plugins by using a base image, digital signature, and cloud-based resources, allowing extended functionalities like provisioning third-party storage devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional plugin creation process is used, then plugin functionality can be extended, but cloud native application methodologies are not embraced and third-party developers lack access
Solution Approach 1:
A cloud-based plugin repository and Docker image registry serve as intermediaries between third-party developers and the HCI platform. Developers can upload Docker images to the repository without direct platform access, while the platform retrieves and executes these images. This mediator architecture enables third-party participation while maintaining platform security and control.
Solution Approach 2:
The traditional mechanical plugin installation process (requiring direct platform access and manual configuration) is replaced with a cloud-based Docker image distribution system. Plugin images are built, signed, and distributed through cloud repositories using automated processes, eliminating the need for direct authorized access during the development and deployment phases.
2Reliability
If authorized access is required for plugin creation, then platform security is maintained, but independent developer participation is restricted
Solution Approach 1:
The cloud-based plugin repository acts as a trusted intermediary that decouples the authentication requirements. Developers authenticate with the cloud repository (not directly with the HCI platform), and the platform trusts images from the authorized repository. This mediator approach maintains security while enabling broad developer participation.
Solution Approach 2:
The system enables self-service plugin development and distribution through the cloud repository. Developers can independently build, sign, upload, and manage their plugin images without requiring ongoing authorized access to HCI platforms. The automated image signing and retrieval processes further reduce manual intervention requirements.
3Reliability
If Docker images are digitally signed by cloud-based signature server, then image authenticity is verified, but additional processing steps are introduced
Solution Approach 1:
Digital signing of Docker images is performed in advance during the build process, before deployment to the HCI platform. The cloud-based signature server authenticates images upfront, and the signed images are stored in the plugin repository. This preliminary authentication eliminates the need for complex runtime verification processes and simplifies the deployment workflow.
Solution Approach 2:
The digital signature mechanism creates a trusted copy of the image metadata that can be verified without modifying the original image. The signature server creates cryptographic copies of authentication information that travel with the image through the repository system, enabling fast verification without re-authenticating the entire image during deployment.
Data Source
AI summary
Disclosed systems and methods may retrieve a base image of a plugin for a hyperconverged infrastructure (HCI) platform and create a Docker image for an HCI platform plugin based, in part, on the base image. The HCI platform plugin enables an extended function not native to the HCI platform. Disclosed methods may include registering the Docker image within an HCI platform instance running on an HCI appliance associated with a customer, and saving the Docker image to a Docker image repository within the HCI platform instance. The extended HCI platform function may be any suitable function including, as an illustrative example, a function for provisioning a third party storage device within the HCI platform. Disclosed method steps may be performed by an independent third party developer that lacks authorized access to an HCI platform instance.