Asynchronous Service Provisioning via Repository-Based Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for provisioning services require manual configuration, which is inefficient and error-prone, especially when serving multiple users.
Innovation Solution
An asynchronous method using file distribution technology, where a provisioning manager obtains data from a database, prepares configuration files, commits them to repositories, and sends notifications to service instances, allowing for efficient and accurate provisioning without manual intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual configuration methods are used for service provisioning, then service instances can be provisioned with configuration settings, but the process becomes inefficient and error-prone especially when serving multiple users
Solution Approach 1:
The patent uses template-based configuration files that can be copied and reused across multiple service instances. Instead of manually configuring each service instance individually, administrators can create a master configuration template and replicate it across numerous service instances, ensuring consistency and reducing manual errors while improving provisioning efficiency
Solution Approach 2:
The configuration is segmented into separate configuration files for different service instances, stored in a version control repository. This allows independent management, tracking, and updating of each service instance's configuration without affecting others, improving both efficiency through automated deployment and reliability through version control
2Productivity
If asynchronous notification method is implemented, then processing efficiency is improved and overhead messaging is reduced, but system complexity increases due to repository and notification mechanisms
Solution Approach 1:
A version control repository acts as an intermediary between configuration management and service instances. Configuration files are committed to the repository, which automatically triggers notifications to relevant service instances. This intermediary approach streamlines the provisioning process by automating the notification and retrieval mechanism, improving provisioning speed while managing complexity through a centralized intermediary system
3Manufacturing precision
If configuration files are committed to repositories for each service instance, then provisioning accuracy is improved, but messaging overhead increases
Solution Approach 1:
Service instances periodically check the version control repository for updated configuration files rather than receiving continuous notifications. This periodic polling approach ensures accurate configuration deployment while reducing messaging overhead compared to push-based notification systems, as instances only communicate when configuration changes are detected
Data Source
AI summary
According to certain embodiments, a provisioning manager comprises an interface and processing circuitry. The interface is configured to obtain provisioning data from a provisioning database. The processing circuitry is configured to prepare one or more configuration files based on the provisioning data. The configuration file(s) indicate how to provision one or more service instances. The processing circuitry is further configured to commit the configuration file(s) to one or more repositories in order to make the configuration file(s) available to at least one of the service instances. The processing circuitry is further configured to send one or more notifications indicating to one or more of the service instances that the configuration file(s) have been committed to the one or more repositories.