Browse Prior Art Database

A architecture for distributed PaaS environment

IP.com Disclosure Number: IPCOM000244471D
Publication Date: 2015-Dec-15
Document File: 6 page(s) / 624K

Publishing Venue

The IP.com Prior Art Database

Abstract

The key idea of this disclosure is to use a Hybrid Cloud Gateway as the proxy for cloud applications. A special tag (metadata) is used at deployment time as a hint for the cloud controller that the application will be deployed on-premise. Any application whose deployment policy has that special tag will be deploy on-premise via the Hybrid-Cloud Gateway. For the on-premise PaaS platform, the application runtime container set the dynamic network proxy to the address of the "Hybrid-Cloud Gateway" agent, so all traffic targeted to the PaaS service, no matter it is defined locally or on the cloud, will be routed to the subnet of Cloud infrastructure.

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

Page 01 of 6

A architecture for distributed PaaS environment A architecture for distributed PaaS environment

Nowadays, customer sometimes has the concern to running the application on public cloud and would like to run the application on their on-premises environment and access backend data in a safe/secure environment but still can access/use some services on public cloud. How can we extend the "platform as a service" (PaaS) to customer's on premises environment and allow them to run the appication on their on-premises environment transparently as if the application deployed on public cloud?

To solve this, we need to take cares the following:


1. at the deploy time. Ensure to deploy the application on the extended parts of PaaS. (i.e., the on-premises environment).

2. during run-time, all the used service binding are well defined so the application could access those services no matter the services are on public cloud or on-premises environment.

The key idea of this disclosure is to use a Hybrid Cloud Gateway as the proxy for cloud applications. A special tag (metadata) is used at deployment time as a hint for the cloud controller that the application will be deployed on-premise. Any application whose deployment policy has that special tag will be deploy on-premise via the Hybrid-Cloud Gateway. For the on-premise PaaS platform, the application runtime container set the dynamic network proxy to the address of the "Hybrid-Cloud Gateway" agent, so all traffic targeted to the PaaS service, no matter it is defined locally or on the cloud, will be routed to the subnet of Cloud infrastructure. In another word, from application developer's perspective, the actually location here the application runs doesn't matter.

1



Page 02 of 6

Hybrid-Cloud Gatewayserves as tunel between "Cloud Runtime" and "On-Premise" runtime environment. It setup a secure tunnel with the Cloud Gateway Agent deployed on-premise for further management operations and data traffic .

Cloud Controlleris a special cloud application that hosting the mechanism for registering cloud runtime application

One single cloud controller requires for both "Cloud runtime" and "on-premise" runtime environment. It communicates the components on...