Browse Prior Art Database

Configuration Management for Cloud-Based Solutions

IP.com Disclosure Number: IPCOM000248616D
Publication Date: 2016-Dec-21
Document File: 2 page(s) / 32K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a design for a packet forwarder product that enables customers to easily configure and edit configuration files for multiple systems in a single location/system.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

1

Configuration Management for Cloud -Based Solutions

Many users install packet forwarder products on many machines on the cloud and each machine has a configuration file for a particular product. Currently, users need to log into each machine to change a configuration setting that applies to all machines. This is inefficient, time consuming, and painful for a provider’s customers.

Further, customers need a method to automatically configure newly and automatically spawned machines; have machines automatically spawned on the cloud based on traffic load with a currently installed packet forwarder product. Because a packet forwarder product requires configuration and customers cannot predict when associated machines will spawn, manual configuration by an available engineer is necessary. This costs time, money, and data loss.

The novel solution addresses the first problem by keeping all the configuration files on a single machine and appropriately synchronizing the files across each machine in a secure and efficient manner. The solution auto-configures the packet forwarder product without manual intervention.

The novel contribution is a design that enables customers to easily configure and edit configuration files for multiple systems in a single location/system. Users do not have to manually login or enter a password on all other machines/systems. In addition, newer machines automatically configure and start with no customer intervention. New machines receive new configuration settings and the packet forwarding product automatically starts these settings.

Implementation of the novel design works by denoting one machine as the “master” machine. The user logs into this machine to manage and run the auto-configuration service. After configuration, the auto-configuration service listens on a port for incoming connections. New instances of the packet forwarder product connect to this port on the master machine. The service then builds an appropriate packet forwarder configuration file for each new instance, securely (encrypted) sends the product over, and restarts the product with the appropriate configuration settings.

Figure: Configuration of machines

2

While listening to incoming connections, the auto-configuration service goes through a list of built packet forwarder configuration files that are already sent to the packet forward...