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

Coexisted with production but transparent development setup with multi-tenancy support from software stack in Cloud

IP.com Disclosure Number: IPCOM000244395D
Publication Date: 2015-Dec-09
Document File: 4 page(s) / 131K

Publishing Venue

The IP.com Prior Art Database

Abstract

Presently Cloud, especially IaaS Cloud, environments are universally very huge to support large scope of customer requirements and it need several environments ( Dev , Test , Stage , Production ) for SDLC. For now , many products support multi-tenancy , so our disclosure is derived from this . this disclosure is trying to setup environment with Multi-tenancy support from software stack in Cloud , for example Dev and Test coexist in one environment , Stage and Production coexist in another environment . This disclosure can dynamically create environments to reduce the cost of testing and development, and also help to maintain environmental parity between the different environments as you known lots of problems are caused by environment difference . Meanwhile , it can switch customer request backend among environments and implement Zero Downtime when deploying .

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

Page 01 of 4

Coexisted with production but transparent development setup with multi-tenancy support from software stack in Cloud

Presently Cloud, especially IaaS(Infrastructure As A Service) Cloud, environments are universally huge to support large scope of customer requirements including storage and network and VMs(Virtual Machine) and related services. And they are expensive more and more even per development perspective, not only from production point of view. It need to decrease expense on Cloud environments for development to make great ROI(Return On Investment), and actually this disclosure is doing that with figuring out a way to make it.

Cloud environment is extremely complex to maintain and update. So all Cloud people always expect an environment similar even same with production the most, then maintain and update can be rehearsed in advance to ensure correctness replicated in production. But as mentioned above Cloud environments are expensive and meanwhile this disclosure require a production-like environment. So it need to work out an approach to realize it.

The current solution is under a Cloud project besides production several environments are setup, i.e. one for development and another for testing and the 3rd one for Staging deployment. And a life cycle for deployment cross these environments have to be defined, i.e. daily or weekly or bi-weekly. But usually these environments are simplified by the limited resource. So 2 critical issues happened, the deployment success in Staging environment failed on production environment because of environments difference and the simplified Staging environment is still occupying resource. Meanwhile usually Cloud system include many components bringing much complexity to deployment.

This disclosure will raise an approach to alter the current solution to a brand new model. This model will setup multiple sets of isomorphic Cloud infrastructure in one Cloud environment by leveraging multi-tenancy capacity from software and configuration management automation.

1


Page 02 of 4

Presently Cloud, especially IaaS Cloud, environments are universally consist of database , middleware , applications , network , storage and so on.

For now , so many production could support multi-tenancy . so our disclosure is base on it . it shares one production for multi-environment and split environment by each instance .such as DB(Database) , all the environment use one database software , but dev(development) environment use db2inst1 and test environment use db2inst2 .But still there have some production not support multi-tenancy , this disclosure would separate usage scenario for different tenancy. Eg . File Repository . it uses different location to identify our environment . After identify which instance...