Browse Prior Art Database

A method of managing infrastructure-as-code for DevOps

IP.com Disclosure Number: IPCOM000246239D
Publication Date: 2016-May-19
Document File: 7 page(s) / 256K

Publishing Venue

The IP.com Prior Art Database

Abstract

Cloud provider generally deliver their specific cloud release, and such release will be deployed and operated on global datacenters for different customers with customization required. To manage such customization is a big challenge especially on deployment and operation. This article describes a way to ease such work

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

Page 01 of 7

A method of managing infrastructure-as-code for DevOps

As a cloud provider, many different clouds(public, private, production workload, dev/test workload) could be developed, deployed and operated in different sites in parallel, and this situation brings up big challenges to deploy and operate those cloud:
1. Without standardization or clear methodology, different cloud deployment and operation in parallel could be nightmare, in some cases, for each cloud, some dedicated resources are needed for ongoing automation development and operation
2. Each time, upgrade cloud from one release to another could be new automation development from scratch since changes could be everywhere

This invention is to manage multiple types of cloud deployment and operation in a systematic way by defining and implementing clear structure and relationship of different infrastructure-as-code work product.

With such structure and relationship defined and implemented, some advantages can be acquired:


1. Rather than conception or principle, Infrastructure-as-code now is the specific work product, and it can be standardized and reused for industry or community regarding cloud DevOps
2. Relationship("extends", "implementation", "overwrite") defined among those infrastructure-as-code can help minimize effort regarding cloud upgrade and customization
3. Version cloud at whole infrastructure-as-code level to facilitate management of multiple cloud deployment at different version, workload and sites.

To achieve advantages described above, clear work product definition is required, this invention defines a structure of infrastructure-as-code and relationship among those work products.

At automation development phase, DevOps team defines infrastructure-as-code and relationships as below, abstraction infrastructure-as-code can be defined as the base for all other infrastructure-as-code definition or instances, it contains two important components, one is Topology Definition, the other is Resource Definition, resource is the entity to be installed or configured, e.g. firewall, interface. Both Topology and Resource Definition can be extended and implemented.

One example for such relationship is one cloud provider could provide both public cloud and private cloud based on similar technologies, under such scenario, it can define abst...