Browse Prior Art Database

A MECHANISM TO SEAMLESSLY AND EASILY INTEGRATE VARIOUS THIRD PARTY ADVANCED SERVICE DEVICES INTO NETWORK FABRIC OF A CLOUD

IP.com Disclosure Number: IPCOM000243707D
Publication Date: 2015-Oct-14
Document File: 4 page(s) / 177K

Publishing Venue

The IP.com Prior Art Database

Related People

Milton Xu: AUTHOR

Abstract

A mechanism is provided to seamlessly and easily integrate third party advanced service devices such as load balancers or firewalls as a physical or virtual device into the network fabric for a cloud orchestrator This mechanism creates the software initiated service in the appliance and attaches it to the network automatically at the moment the service device is created by the orchestrator Both the network fabric and the service device need to work together automatically and seamlessly requiring that a user only need provision the service device from the orchestrator truly treating the network fabric and service appliances as pools of resources for the orchestrator

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

Page 01 of 4

A MECHANISM TO SEAMLESSLY AND EASILY INTEGRATE VARIOUS THIRD PARTY ADVANCED SERVICE DEVICES INTO

NETWORK FABRIC OF A CLOUD

AUTHORS:

Milton Xu

CISCO SYSTEMS, INC.

ABSTRACT

    A mechanism is provided to seamlessly and easily integrate third party advanced service devices (such as load balancers or firewalls as a physical or virtual device) into the network fabric for a cloud orchestrator. This mechanism creates the software initiated service in the appliance and attaches it to the network automatically at the moment the service device is created by the orchestrator. Both the network fabric and the service device need to work together automatically and seamlessly, requiring that a user only need provision the service device from the orchestrator, truly treating the network fabric and service appliances as pools of resources for the orchestrator.

DETAILED DESCRIPTION

     As open source cloud orchestrator solutions, such as OpenStack, become increasingly important in the cloud space, third party vendors are racing to add their advanced L4-L7 network services products (e.g., load balancers and firewalls) into the open source code base. This is very challenging as it requires reaching a consensus among the competitors in order to make all these various pieces of the cloud software work seamlessly and allow for integration into the open source code base. This is a slow and sometimes daunting process.

    Additionally, integrating L4-L7 physical or virtual service appliances into a network fabric offered by a particular networking vendor also has been proven to be difficult because of different system architectures due to different business interests among the vendors. As such, it is extremely difficult to build a cloud with an open source cloud orchestrator that can seamlessly and easily integrate the networking devices

Copyright 2015 Cisco Systems, Inc.

1


Page 02 of 4

(switches and routers) with L4-L7 advanced services from various and competing vendors in a timely fashion to meet customer requirements.

    Presented herein is a simple mechanism to seamlessly and easily integrate third party advanced service devices into a cloud orchestrator. It is not required that these advanced service devices be currently part of the cloud orchestrator software, whether either open source or proprietary. A diagram showing various system level components for an example of an implementation is shown in FIG. 1.

FIG. 1

    FIG. 1 shows an example of an implementation with OpenStack as the cloud orchestrator and Advanced Services Extender used to integrate Firewall-as-a-Service (FWaaS) and Loadbalancer-as-a-Service (LBaaS) into the network fabric under the orchestrator framework. The Extender gets the OpenStack AMQP based notifications for the FWaaS or LBaaS creation and configuration information and translates it into the Representational State Transfer (REST) Application Programming Interface (API) calls provided by the service appliances to automatically program and ins...