Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

A system and method for verification of configuration files before applying to a production cloud environment

IP.com Disclosure Number: IPCOM000222877D
Publication Date: 2012-Oct-26
Document File: 2 page(s) / 64K

Publishing Venue

The IP.com Prior Art Database

Abstract

Automated verification of configuration files before applying to a production cloud environment

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

Page 01 of 2

A system and method for verification of configuration files before applying to a production cloud environment

A very common problem that is seen in cloud deployments are failures occurring due to errors introduced by developers into configuration files. For example:
Mistyped URLs like "http//xyz.com" missing the colon.

Unresolved variables like "http://${my_var}" where my_var is undefined.

Duplicate entries in the configuration; where the system picks up the last entry or makes a random choice.

Missing configuration entries.

    These common errors are not detected until a build is deployed and it fails to run. At that point it takes a lot of effort and time to diagnose the issue and determine cause.

Value:

    This tool will save a lot of anxiety in the deployment of cloud software, providing verification to the develop before the configurations are ever attempted to be deployed. While the current implementation is somewhat specific to individual needs the general idea can be applied widely.

    The invention provides a method to verify the configuration at build time, failing builds that contain errors due to poor configuration. Thus allowing a developer to fix the problem before it ever gets into a deployment.

A verification configuration file is provided to the build.

This verification file defines a set of verification patterns in the form of regular

expressions:

"prop":

{

"pat_url" : "|^http(s)?://[a-z0-9-]+(.[a-z0-9-]+)*(:[0-9]+)?(/.*)?$|i",

"pat_ldapurl" : "|^ldap://[a-z0-9-]+(.[a-z0-9-]+)*(:[0-9]+)?(/.*)?$|i",

"pat_boolean" : "/^TRUE$|^FALSE$/i",

"pat_trials" : "/^TRUE$|^FALSE$|CA_Engage,engage-notes|CA_Engage/i",

"pat_guests" : "/^TRUE$|^FALSE$|in-domain-only/i",

"pat_number" : "|^[\\+\\-]*[0-9]+$|",

"pat_numberorblank" : "/^[\\+\\-]*[0-9]+$|^$/",

"pat_email" : "|^[a-zA-Z0-9_.-]+@[a-zA-Z0-9-]+.[a-zA-Z0-9-.]+$|",

"pat_emailorblank" : "/^[a-zA-Z0-9_.-]+@[a-zA-Z0-9-]+.[a-zA-Z0-9-.]+$|^$/",

"pat_time" : "/^[0-9]+ (minutes)|(days)$/",

"pat_extension" : "|^\\.[a-z]+$|i",

"pat_label" : "|^[a-zA-Z0-9\\._\\-@]+$|",

"pat_file" : "|^[a-zA-Z0-9\\._\\/\\-:~]+$|",

"pat_string" : "|^.*$|",

"pat_orgid" : "/126|^$/", }

Example Verification Patterns


Page 02 of 2

contains a list of each configuration parameter with a reference to the pattern that is used to verify it:

Example Configuration Verif...