# Patent

## Title
Method and apparatus for cloud resource delivery

## Abstract

A multi-cloud fabric includes an application management unit responsive to one or more applications from an application layer. The multi-cloud fabric further includes a controller that is in communication with resources of a cloud. The controller is responsive to the applications and includes a processor operable to analyze the application relative to the resources to cause delivery of the applications to the resources dynamically and automatically.

## Background
FIELD OF THE INVENTION
Various embodiments of the invention relate generally to a multi-cloud fabric and particularly to a multi-cloud fabric with distributed application delivery.
BACKGROUND
Data centers refer to facilities used to house computer systems and associated components, such as telecommunications (networking equipment) and storage systems. They generally include redundancy, such as redundant data communications connections and power supplies. These computer systems and associated components generally make up the Internet. A metaphor for the Internet is cloud.
A large number of computers connected through a real-time communication network such as the Internet generally form a cloud. Cloud computing refers to distributed computing over a network, and the ability to run a program or application on many connected computers of one or more clouds at the same time.
The cloud has become one of the, or perhaps even the, most desirable platform for storage and networking. A data center with one or more clouds may have real server hardware, and in fact served up by virtual hardware, simulated by software running on one or more real machines. Such virtual servers do not physically exist and can therefore be moved around and scaled up or down on the fly without affecting the end user, somewhat like a cloud becoming larger or smaller without being a physical object. Cloud bursting refers to a cloud becoming larger or smaller.
The cloud also focuses on maximizing the effectiveness of shared resources, resources referring to machines or hardware such as storage systems and/or networking equipment. Sometimes, these resources are referred to as instances. Cloud resources are usually not only shared by multiple users but are also dynamically reallocated per demand. This can work for allocating resources to users. For example, a cloud computer facility, or a data center, that serves Australian users during Australian business hours with a specific application (e.g., email) may reallocate the same resources to serve North American users during North America's business hours with a different application (e.g., a web server). With cloud computing, multiple users can access a single server to retrieve and update their data without purchasing licenses for different applications.
Cloud computing allows companies to avoid upfront infrastructure costs, and focus on projects that differentiate their businesses instead of infrastructure. It further allows enterprises to get their applications up and running faster, with improved manageability and less maintenance, and enables information technology (IT) to more rapidly adjust resources to meet fluctuating and unpredictable business demands.
Fabric computing or unified computing involves the creation of a computing fabric consisting of interconnected nodes that look like a ‘weave’ or a ‘fabric’ when viewed collectively from a distance. Usually this refers to a consolidated high-performance computing system consisting of loosely coupled storage, networking and parallel processing functions linked by high bandwidth interconnects.
The fundamental components of fabrics are “nodes” (processor(s), memory, and/or peripherals) and “links” (functional connection between nodes). Manufacturers of fabrics include IBM and BROCADE. The latter are examples of fabrics made of hardware. Fabrics are also made of software or a combination of hardware and software.
A traditional data center employed with a cloud may suffer from latency and crashes due to underestimated usage. Furthermore, such a data center may inefficiently use storage and networking systems of the cloud. Perhaps most importantly of all, such a data center may manually deploy applications. Application deployment services may be performed, in large part, manually with elaborate infrastructure and/or numerous teams of professionals, and potential failures due to unexpected bottlenecks. Some of the foregoing translate to high costs. Lack of automation results in delays in launching business applications. It is estimated that application delivery services currently consume approximately thirty percent of the time required for deployment operations. Additionally, scalability of applications across multiple clouds is nearly nonexistent.
There is therefore a need for a method and apparatus to decrease bottleneck, latency, infrastructure, and costs while increasing efficiency and scalability of a data center.
SUMMARY
Briefly, an embodiment of the invention includes a multi-cloud fabric that includes an application management unit responsive to one or more applications from an application layer. The multi-cloud fabric further includes a controller that is in communication with resources of a cloud. The controller is responsive to the one or more applications and includes a processor operable to analyze the same relative to the resources of the cloud to cause delivery of the one or more applications to the resources dynamically and automatically.
A further understanding of the nature and the advantages of particular embodiments disclosed herein may be realized by reference of the remaining portions of the specification and the attached drawings.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 shows a data center 100, in accordance with an embodiment of the invention.
FIG. 2 shows further details of relevant portions of the data center 100 and in particular, the multi-cloud fabric 106 of FIG. 1.
FIG. 3 shows conceptually various features of a data center 300, in accordance with an embodiment of the invention.
FIG. 4 shows, in conceptual form, a relevant portion of a multi-cloud data center 400, in accordance with another embodiment of the invention.
FIGS. 4a-c show exemplary data centers configured using embodiments and methods of the invention.



DETAILED DESCRIPTION OF EMBODIMENTS
The following description describes a multi-cloud fabric. The multi-cloud fabric has a controller and spans homogeneously and seamlessly across the same or different types of clouds, as discussed below.
Particular embodiments and methods of the invention disclose a virtual multi-cloud fabric. Still other embodiments and methods disclose automation of application delivery by use of the multi-cloud fabric.
In other embodiments, a data center includes a plug-in, application layer, multi-cloud fabric, network, and one or more the same or different types of clouds.
Referring now to FIG. 1, a data center 100 is shown, in accordance with an embodiment of the invention. The data center 100 is shown to include a private cloud 102 and a hybrid cloud 104. A hybrid cloud is a combination public and private cloud. The data center 100 is further shown to include a plug-in unit 108 and a multi-cloud fabric 106 spanning across the private cloud 102 and hybrid cloud 104. Each of private cloud 102 and hybrid cloud 104 are shown to include a respective application layer 110, a network 112, and resources 114.
The network 112 may include switches and the like and the resources 114 may include routers, servers, and other networking and/or storage equipment.
Each respective application layer 110 is shown to include applications 118 and resources 114 further include machines, such as servers, storage systems, switches, servers, routers, or any combination thereof.
The plug-in unit 108 is shown to include various plug-ins. As an example, in the embodiment of FIG. 1, plug-in unit 108 is shown to include several distinct plug-ins 116, such as one made by OPENSOURCE, another made by MICROSOFT, INC., and yet another made by VMWARE, INC. Each of the foregoing plug-ins typically have different formats. The plug-in unit 108 converts all of the various formats of the applications into one or more native formats for use by the multi-cloud fabric 106. The native-format application(s) is passed through the application layer 110 to the multi-cloud fabric 106.
The multi-cloud fabric 106 is shown to include various nodes 106a and links 106b connected together in a weave-like fashion.
In some embodiments of the invention, the plug-in unit 108 and the multi-cloud fabric 106 do not span across clouds and the data center 100 includes a single cloud. In embodiments with the plug-in unit 108 and multi-cloud fabric 106 spanning across clouds, such as that of FIG. 1, resources of the two clouds (i.e., the private cloud 102 and the hybrid cloud 104) are treated as resources of a single unit. For example, an application may be distributed across the resources of both the private cloud 102 and the hybrid cloud 104 homogeneously thereby making the clouds seamless. This allows use of analytics, searches, monitoring, reporting, displaying and otherwise data crunching thereby optimizing services and use of resources of the private cloud 102 and the hybrid cloud 104 collectively.
While two clouds are shown in the embodiment of FIG. 1, it is understood that any number of clouds, including one cloud, may be employed. Furthermore, any combination of private, public and hybrid clouds may be employed. Alternatively, one or more of the same type of cloud may be employed.
In an embodiment of the invention, the multi-cloud fabric 106 is a Layer (L) 4-7 fabric. Those skilled in the art appreciate data centers with various layers of networking. As earlier noted, multi-cloud fabric 106 is made of nodes 106a and connections (i.e., links 106b). In an embodiment of the invention, the nodes 106a are devices, such as but not limited to L4-L7 devices. In some embodiments, the multi-cloud fabric 106 is implemented in software and, in other embodiments, it is made with hardware and, in still others, it is made with hardware and software.
The multi-cloud fabric 106 sends the application to the resources 114 through the network 112.
In an SLA engine, as will be discussed relative to a subsequent figure, data is acted upon in real-time. Further, the data center 100 dynamically and automatically delivers applications, virtually or in physical reality, in a single or multi-cloud of either the same or different types of clouds.
The data center 100, in accordance with some embodiments and methods of the invention, may serve as a service (e.g., Software as a Service (SAAS)) model, a software package through existing cloud management platforms, and/or a physical appliance for high scale requirements. Further, licensing can be throughput or flow-based and can be enabled with network services only, network services with SLA and elasticity engine (as will be further evident below), network service enablement engine, and/or multi-cloud engine.
As will be further discussed below, the data center 100 may be driven by representational state transfer (REST) application programming interface (API).
The data center 100, with the use of the multi-cloud fabric 106, eliminates the need for an expensive infrastructure, manual and static configuration of resources, limitation of a single cloud, and delays in configuring the resources, among other advantages. Rather than a team of professionals configuring the resources for delivery of applications over months of time, the data center 100 automatically and dynamically does the same, in real-time. Additionally, more features and capabilities are realized with the data center 100 over that of prior art. For example, due to multi-cloud and virtual delivery capabilities, cloud bursting to existing clouds is possible and utilized only when required to save resources and therefore expenses.
Moreover, the data center 100 effectively has a feedback loop that results from monitoring traffic, performance, usage, time, resource limitations and the like (i.e., the configuration of the resources can be dynamically altered based on the monitored information). A log of information pertaining to configuration, resources, the environment, and the like allow the data center 100 to provide a user with pertinent information to enable the user to adjust and substantially optimize its usage of resources and clouds. Similarly, the data center 100 itself can optimize resources based on the foregoing information.
FIG. 2 shows further details of relevant portions of the data center 100 and in particular, the multi-cloud fabric 106 of FIG. 1. The multi-cloud fabric 106 is shown to be in communication with an applications unit 202 and a network 204, which is shown to include a number of Software Defined Networking (SDN)-enabled controllers and switches 208. The network 204 is analogous to the network 112 of FIG. 1.
The applications unit 202 is shown to include a number of applications 206, for instance, for an enterprise. These applications are analyzed, monitored, searched, and otherwise crunched just like the applications from the plug-ins of the multi-cloud fabric 106 for ultimate delivery to resources through the network 204.
In FIG. 2, the data center 100 is shown to include five units (or planes): the management unit 210, the value-added services (VAS) unit 214, the controller unit 212, the service unit 216 and the data unit (i.e., network 204). Accordingly and advantageously, control, data, VAS, network services and management are provided separately. Each of the planes is an agent and the data from each of the agents is crunched by the controller unit 212 and the VAS unit 214.
In FIG. 2, the multi-cloud fabric 106 is shown to include the management unit 210, the VAS unit 214, the controller unit 212 and the service unit 216. The management unit 210 is shown to include a user interface (UI) plug-in 222, an orchestrator compatibility framework 224, and applications 226. The management unit 210 is analogous to the plug-in unit 108 in FIG. 1. The UI plug-in 222 and the applications 226 receive applications of various formats and the orchestrator compatibility framework 224 translates the various formatted application into native-format applications. Examples of the plug-ins 116, located in the applications 226, may include VMWARE ICENTER by VMWARE, INC. and SYSTEM CENTER by MICROSOFT, INC. While two plug-ins are shown in FIG. 2, it is understood that any number may be employed.
The controller unit 212 (also referred to herein as “multi-cloud master controller”) serves as the master or brain of the data center 100 in that it controls the flow of data throughout the data center 100 and timing of various events, to name a couple of many other functions it performs as the mastermind of the data center. In FIG. 2, the controller unit 212 is shown to include a services controller 218 and an SDN controller 220. The services controller 218 is shown to include a multi-cloud master controller 232, an application delivery services stitching engine or network enablement engine 230, an SLA engine 228, and a controller compatibility abstraction 234.
Typically, one of the clouds of a multi-cloud network is the master of the clouds and includes a multi-cloud master controller that talks to local cloud controllers (or managers) to help configure the topology among other functions. The master cloud includes an SLA engine (such as the SLA engine 228) whereas other clouds need not to but all clouds include an SLA agent and an SLA aggregator with the former typically being a part of a virtual services platform, such as virtual services platform 244, and the latter being a part of a search and analytics module, such as search and analytics unit 238.
The controller compatibility abstraction 234 provides abstraction to enable handling of different types of controllers (e.g., SDN controllers 236) in a uniform manner to offload traffic in the switches and routers of the network 204. This increases response time and performance as well as allowing more efficient use of the network.
The network enablement engine 230 performs stitching where an application or network service (such as configuring load balance) is automatically enabled. This eliminates the need for the user to work on meeting, for instance, a load balance policy. Moreover, it allows scaling out automatically when violating a policy.
The multi-cloud master control 232 (e.g., a flex-cloud engine) handles multi-cloud configurations such as determining, for instance, which cloud is less costly, or whether an application must go onto more than one cloud based on a particular policy, or the number and type of cloud that is best suited for a particular scenario.
The SLA engine 228 monitors various parameters in real-time and decides if policies are met. Exemplary parameters include different types of SLAs and application parameters. Examples of different types of SLAs include network SLAs and application SLAs. The SLA engine 228, besides monitoring allows for acting on the data, such as service plane (L4-L7), application, network data and the like, in real-time.
The practice of service assurance enables Data Centers (DCs) and/or Cloud Service Providers (CSPs) to identify faults in the network and resolve these issues in a timely manner so as to minimize service downtime. The practice also includes policies and processes to proactively pinpoint, diagnose and resolve service quality degradations or device malfunctions before subscribers (users) are impacted.
In some embodiments, service assurance may encompass the following: fault and event management, performance management, probe monitoring, quality of service (QoS) management, network and service testing, customer experience management, real-time SLA monitoring and assurance, service and application availability, and trouble ticket management.
The structures shown included in the controller unit 212 are implemented using one or more processors executing software (or code) and in this sense, the controller unit 212 may be a processor. Alternatively, any other structures in FIG. 2 may be implemented as one or more processors executing software. In other embodiments, the controller unit 212 and perhaps some or all of the remaining structures of FIG. 2 may be implemented in hardware or a combination of hardware and software.
The VAS unit 214 uses its search and analytics unit 238 to search analytics (e.g., based on a distributed large data engine) and crunches data and displays analytics. The search and analytics unit 238 can filter all of the logs a distributed logging unit 240 of the VAS unit 214 logs, based on the customer's (user's) desires. Examples of analytics include events and logs. The VAS unit 214 also determines configurations such as who needs SLA, who is violating SLA, and the like.
The SDN controller 220, which includes software defined network programmability, such as those made by FLOODLIGHT, OPEN DAYLIGHT, PDX, and other manufacturers, receives all the data from the network 204 and allows for programmability of a network switch/router.
The service unit 216 is shown to include an API based, Network Function Virtualization (NFV), Application Delivery Network (ADN) 242 and a distributed virtual services platform 244. The service unit 216 activates the right components based on rules. It includes ADC, web-application firewall, DPI, VPN, DNS and other L4-L7 services and configures based on policy (it is completely distributed). It can also include any application or L4-L7 network services.
The distributed virtual services platform 244 may contain, for example, an Application Delivery Controller (ADC), Web Application Firewall (Firewall), L2-L3 Zonal Firewall (ZFW), Virtual Private Network (VPN), Deep Packet Inspection (DPI), and various other services that can be enabled as a single-pass architecture. The service unit 216 may contain, for example, a Configuration agent, a Stats/Analytics reporting agent, a Zero-copy driver to send and receive packets in a fast manner, a Memory mapping engine that maps memory via TLB to any virtualized platform/hypervisor, an SSL offload engine, etc.
FIG. 3 shows conceptually various features of a data center 300, in accordance with an embodiment of the invention. The data center 300 is analogous to the data center 100 except some of the features/structures of the data center 300 are in addition to those shown in the data center 100. The data center 300 is shown to include plug-ins 116, flow-through orchestration 302, cloud management platform 304, controller 306, public clouds 308 and private clouds 310.
The controller 306 is analogous to the controller unit 212 of FIG. 2. In FIG. 3, the controller 306 is shown to include a REST APIs-based invocations for self-discovery (i.e., REST APIs 312), platform services 318, data services 316, infrastructure services 314, profiler 320, service controller 322, and SLA manager 324.
The flow-through orchestration 302 is analogous to the orchestrator compatibility framework 224 of FIG. 2. Plug-ins 116 and flow-through orchestration 302 provide applications to the cloud management platform 304, which converts the formats of the applications to native format. The native-formatted applications are processed by the controller 306. The RESI APIs 312 drive the controller 306. The platform services 318 is for services such as licensing, Role Based Access and Control (RBAC) jobs, log, and search. The data services 316 is to store data of various components, services, applications, databases such as Search and Query Language (SQL), NoSQL, data in memory. The infrastructure services 314 is for services such as node and health.
The profiler 320 is a test engine. Service controller 322 is analogous to the SDN controller 220 and SLA manager 324 is analogous to the SLA engine 228 of FIG. 2. During testing by the profiler 320, simulated traffic is run through the data center 300 to test for proper operability as well as adjustment of parameters such as response time, resource and cloud requirements, and processing usage.
In the exemplary embodiment of FIG. 3, the controller 306 interacts with public clouds 308 and private clouds 310. Both the public clouds 308 and the private clouds 310 may include multiple clouds and may communicate not only with the controller 306 but also with each other. Benefits of the clouds communicating with one another include, without limitation, optimization of traffic path, dynamic traffic steering, and/or reduction of costs.
The plug-ins 116 and the flow-through orchestration 302 are the clients of the data center 300, the controller 306 is the infrastructure of the data center 300, and the public clouds 308 and the private clouds 310 are the virtual machines and SLA agents 305 of the data center 300.
FIG. 4 shows, in conceptual form, relevant portions of a multi-cloud data center 400, in accordance with another embodiment of the invention. A client 401 (i.e., a user) is shown to use the multi-cloud data center 400, which is shown to include plug-in unit 108, cloud providers 402(1)-(N), a distributed elastic analytics engine (i.e., including multiple instances of the VAS unit 214), a distributed elastic controller of clouds, also known herein as a “flex cloud engine” (i.e., multi-cloud master controller 232, tiers 406(1)-(N), underlying physical network 416, such as Servers, Storage, Network elements, etc., and SDN controller 220.
Each tier within tiers 406(1)-(N) is shown to include multiple distributed elastic network services (i.e., distributed elastic network service 408—distributed elastic network service 410), elastic applications 412, and storage 414. The distributed elastic network services (i.e., distributed elastic network service 408—distributed elastic network service 410) communicate bidirectionally with the underlying physical network 416 and the latter unilaterally provides information to the SDN controller 220. A part of each of the tiers within tiers 406(1)-(N) is included in the service unit 216 of FIG. 2.
The cloud providers 402(1)-(N) are providers of the clouds shown and/or discussed herein. The multi-cloud master controller 232 (as depicted in FIG. 4) includes multiple distributed elastic controllers each of which services a cloud from one of the cloud providers 402(1)-(N), as discussed previously except that in FIG. 4, there are N number of clouds, “N” being an integer value.
As previously discussed, the distributed elastic analytics engine includes multiple instances of the VAS unit 214, one for each of the clouds, and the analytics are provided to the multi-cloud master controller 232 for various reasons, one of which is the feedback feature discussed earlier. The multi-cloud master controller 232 also provides information to the distributed elastic analytics engine, as discussed above.
The distributed elastic network service 408 through the distributed elastic network service 410 (representing services 1-N, “N” being an integer value) are analogous to the services illustrated in FIG. 3 (i.e., the platform services 318, the data services 316, and the infrastructure services 314) except that in FIG. 4, the services are shown to be distributed, as are the controllers within multi-cloud master controller 232 and the instances of VAS unit 214 within the distributed elastic analytics. Such distribution allows flexibility in the use of resource allocation therefore minimizing costs to the user among other advantages.
The underlying physical network 416 is analogous to the resources 114 of FIG. 1 and that of other figures herein. The underlying network 416 includes servers for running any applications, storage, and/or network elements such as routers, switches, etc. The storage 414 is also a part of the underlying network 416 (analogous to resources 114).
The tiers 406 are deployed across multiple clouds and are subject to enablement. Enablement refers to evaluation of applications for L4 through L7. An example of enablement is stitching.
In summary, in one embodiment of the invention, the disclosed data center is multi-cloud and capable of application deployment, application orchestration, and application delivery.
In operation, client 401 interacts with the user interface 404 and through the user interface 404, client 401 interacts with the plug-in unit 108. Alternatively, the client 401 interacts directly with the plug-in unit 108. The plug-in unit 108 receives applications from the client 401 with perhaps certain specifications. As illustrated in FIG. 4, orchestration and discovery take place between the plug-in unit 108 and the controllers within the multi-cloud master controller 232 and between the cloud providers 402(1)-(N) and the controllers within the multi-cloud master controller 232. A management interface (such as the management unit 210 illustrated in FIG. 2) manages the interactions between the controllers within the multi-cloud master controller 232 and the plug-in unit 108.
The distributed elastic analytics engine (which includes multiple instances of the VAS unit 214) and the tiers 406(1)-(N) perform monitoring of various applications, application delivery services and network elements and the controllers within the multi-cloud master controller 232 effectuate service change.
In accordance with various embodiments and methods of the invention, some of which are shown and discussed herein, a multi-cloud fabric is disclosed. The multi-cloud fabric includes an application management unit responsive to one or more applications from an application layer. The multi-cloud fabric further includes a controller in communication with resources of a cloud, the controller is responsive to the received application and includes a processor operable to analyze the received application relative to the resources to cause delivery of the one or more applications to the resources dynamically and automatically.
The multi-cloud fabric, in some embodiments of the invention, is virtual. In some embodiments of the invention, the multi-cloud fabric is operable to deploy the one or more native-format applications automatically and/or dynamically. In still other embodiments of the invention, the controller is in communication with resources of more than one cloud.
The processor of the multi-cloud fabric is operable to analyze applications relative to resources of more than one cloud.
In an embodiment of the invention, a Value Added Services (VAS) unit is in communication with the controller and the application management unit and the VAS unit is operable to provide analytics to the controller. The VAS unit is operable to perform a search of data provided by the controller and filters the searched data based on the user's specifications (or desire).
In an embodiment of the invention, the multi-cloud fabric includes a service unit that is in communication with the controller and operative to configure data of a network based on rules from the user or otherwise.
In some embodiments, the controller includes a cloud engine that assesses multiple clouds relative to an application and resources. In an embodiment of the invention, the controller includes a network enablement engine.
In some embodiments of the invention, the application deployment fabric includes a plug-in unit responsive to applications with different format applications and operable to convert the different format applications to a native-format application. The application deployment fabric can report configuration and analytics related to the resources to the user. The application deployment fabric can have multiple clouds including one or more private clouds, one or more public clouds, or one or more hybrid clouds. A hybrid cloud is private and public.
The application deployment fabric configures the resources and monitors traffic of the resources, in real-time, and based at least on the monitored traffic, re-configure the resources, in real-time.
In an embodiment of the invention, the multi-cloud fabric can stitch end-to-end, i.e. an application to the cloud, automatically.
In an embodiment of the invention, the SLA engine of the multi-cloud fabric sets the parameters of different types of SLA in real-time.
In some embodiments, the multi-cloud fabric automatically scales in or scales out the resources. For example, upon an underestimation of resources or unforeseen circumstances requiring addition resources, such as during a SUPER BOWL game with subscribers exceeding an estimated and planned for number, the resources are scaled out and perhaps use existing resources, such as those offered by AMAZON, INC. Similarly, resources can be scaled down.
The following are some, but not all, various alternative embodiments. The multi-cloud fabric is operable to stitch across the cloud and at least one more cloud and to stitch network services, in real-time.
The multi-cloud fabric is operable to burst across clouds other than the cloud and access existing resources.
The controller of the multi-cloud fabric receives test traffic and configures resources based on the test traffic.
Upon violation of a policy, the multi-cloud fabric automatically scales the resources.
The SLA engine of the controller monitors parameters of different types of SLA in real-time.
The SLA includes application SLA and networking SLA, among other types of SLA contemplated by those skilled in the art.
The multi-cloud fabric may be distributed and it may be capable of receiving more than one application with different formats and to generate native-format applications from the more than one application.
The resources may include storage systems, servers, routers, switches, or any combination thereof.
The analytics of the multi-cloud fabric include but not limited to traffic, response time, connections/sec, throughput, network characteristics, disk I/O or any combination thereof.
In accordance with various alternative methods of delivering an application by the multi-cloud fabric, the multi-cloud fabric receives at least one application, determines resources of one or more clouds, and automatically and dynamically delivers the at least one application to the one or more clouds based on the determined resources. Analytics related to the resources are displayed on a dashboard or otherwise and the analytics help cause the multi-cloud fabric to substantially optimally deliver the at least one application.
FIGS. 4a-c show exemplary data centers configured using embodiments and methods of the invention. FIG. 4a shows the example of a work flow of a 3-tier application development and deployment. At development environment 422 is shown a developer's development environment including a web tier 424, an application tier 426, and a database 428, each used by a user for different purposes typically and perhaps requiring its own security measure. For example, a company like YAHOO, INC. may use the web tier 424 for its web and the application tier 426 for its applications and the database 428 for its sensitive data. Accordingly, the database 428 may be a part of a private cloud rather than a public cloud. The web tier 424, the application tier 426, and database 428 are all linked together.
At 420, a development testing and production environment is shown. At 422, an optional deployment is shown with a firewall (FW), ADC, a web tier (such as the web tier 424), another ADC, an application tier (such as the application tier 426), and a virtual database (same as the database 428). ADC is essentially a load balancer. This deployment may not be optimal and actually far from it because it is an initial pass and without the use of some of the optimizations done by various methods and embodiments of the invention. The instances of this deployment are stitched together (or orchestrated).
At 424, another optional deployment is shown with perhaps greater optimization. A FW is followed by a web-application FW (WFW), which is followed by an ADC and so on. Accordingly, the instances shown at 424 are stitched together.
Accordingly, consistent development/production environments are realized. Automated discovery, automatic stitching, test and verify, real-time SLA, automatic scaling up/down capabilities of the various methods and embodiments of the invention may be employed for the three-tier (web, application, and database) application development and deployment of FIG. 4a. Further, deployment can be done in minutes due to automation and other features. Deployment can be to a private cloud, public cloud, or a hybrid cloud or multi-clouds.
FIG. 4b shows an exemplary multi-cloud environment having a public, private, or hybrid cloud 460 and another public or private or hybrid cloud 460 in communication through a secure access 464. The cloud 460 is shown to include a multi-cloud master controller whereas the cloud 462 is shown to include a slave or local cloud controller. Accordingly, an SLA engine resides in the cloud 460.
FIG. 4c shows a virtualized multi-cloud fabric 450 spanning across multiple clouds (i.e., private cloud 102 and cloud 102′) with a single point of control and management (i.e., a master instance of the controller unit 212 that includes a multi-cloud master controller and a performance monitor/analytics engine). As illustrated in FIG. 4c, private cloud 102 is associated with the master instance of the controller unit 212, network 112, applications 226, plug-ins 116 (i.e., an OPENSTACK plug-in, a VMWARE VCENTER plug-in and a MICROSOFT SYSTEM CENTER 2012 plug-in), and optional deployments 454. As illustrated in FIG. 4c, cloud 102′ is associated with an additional network 112′, a local instance of the controller unit 212 (i.e., a local controller unit 212′) that includes a local cloud controller and a local performance monitor/analytics engine, and optional deployments 454. As illustrated in FIG. 4c, the master instance of the controller unit 212 may access the local controller unit 212′ a using secured tunnels 452.
Although the description has been described with respect to particular embodiments thereof, these particular embodiments are merely illustrative, and not restrictive.
As used in the description herein and throughout the claims that follow, “a” “an”, and “the” includes plural references unless the context clearly dictates otherwise. Also, as used in the description herein and throughout the claims that follow, the meaning of “in” includes “in” and “on” unless the context clearly dictates otherwise.
Thus, while particular embodiments have been described herein, latitudes of modification, various changes, and substitutions are intended in the foregoing disclosures, and it will be appreciated that in some instances some features of particular embodiments will be employed without a corresponding use of other features without departing from the scope and spirit as set forth. Therefore, many modifications may be made to adapt a particular situation or material to the essential scope and spirit.

## Claims

1. A networking system with networking layers and including at least one cloud fabric, the networking system comprising:
a cloud fabric comprising:
a plurality of clouds;
a master controller;
an application management unit responsive to one or more user applications from an application layer;
a first set of nodes communicatively connected with each other through a set of links, the first set of nodes comprising a combination of Layer 4 through Layer 7 networking devices, wherein:
each node within the first set of nodes represents a distinct Layer 4 through Layer 7 networking device;
the first set of nodes comprises a first plurality of load balancers and a plurality of resources; and
each resource within the plurality of resources operates as a user application and is in communication with each load balancer within the first plurality of load balancers;

a value-added services (VAS) unit located externally to the first set of nodes and communicatively coupled to the master controller and the first set of nodes; and
a second set of nodes, located externally to the VAS unit, the first set of nodes, and the master controller, the second set of nodes comprising a combination of Layer 4 through Layer 7 networking devices, wherein:
each node within the second set of nodes represents a distinct Layer 4 through Layer 7 networking device;
the second set of nodes comprises a second plurality of load balancers;
each load balancer within the second plurality of load balancers is in communication with the plurality of resources such that the first set of nodes are communicatively coupled to the second set of nodes through the plurality of resources and the second plurality of the load balancers; and
the first set of nodes and the second set of nodes are dynamically configurable by the VAS unit;


wherein the VAS unit is operable, by use of one or more policies from a user and at least one load balancer within the first plurality of load balancers, to cause the master controller to create an instance of at least one resource from within the plurality of resources in a cloud selected from within the plurality of clouds based on a balance of load on the plurality of resources through use of a local cloud controller of the selected cloud in real-time.

2. The networking system, as recited in claim 1, wherein the VAS unit is operable to provide analytics to the master controller.

3. The networking system, as recited in claim 2, wherein the VAS unit is operable to perform a search of data provided by the master controller.

4. The networking system, as recited in claim 3, wherein the VAS unit is operable to filter the searched data based on user input.

5. The networking system, as recited in claim 2, wherein the analytics include one or more of: traffic information, response time information, connections per second throughput information, network characteristics information, and disk input/output information.

6. The networking system, as recited in claim 1, wherein the master controller is in communication with resources of more than one cloud.

7. The networking system, as recited in claim 6, wherein the application management unit is operable to analyze the one or more user applications relative to the resources of more than one cloud.

8. The networking system, as recited in claim 1, wherein the cloud fabric is operable to:
configure the plurality of resources;
monitor traffic of the plurality of resources; and
based at least on the monitored traffic, re-configure the plurality of resources.

9. The networking system, as recited in claim 8, wherein the cloud fabric is operable to monitor the traffic in real-time and to re-configure the plurality of resources in real-time.

10. The networking system, as recited in claim 1, wherein the cloud fabric is operable to stitch network services.

11. The networking system, as recited in claim 10, wherein the cloud fabric is operable to stitch the network services in real-time.

12. The networking system, as recited in claim 1, wherein the master controller is responsive to test traffic and operable to generate test traffic.

13. The networking system, as recited in claim 12, wherein the cloud fabric is operable to configure the plurality of resources based on the test traffic.

14. The networking system, as recited in claim 1, wherein the master controller further includes a service level agreement (SLA) engine operable to monitor and set parameters of different types of SLAs in real-time.

15. The networking system, as recited in claim 14, wherein the SLA engine includes application SLA and networking SLA.

16. The networking system, as recited in claim 1, wherein the VAS unit includes a search and analytics unit operable to search analytics based on filter logs based on user input.

17. The networking system, as recited in claim 16, wherein the analytics includes events and logs.

18. The networking system, as recited in claim 1, wherein the cloud fabric is virtual.

19. The networking system, as recited in claim 1, wherein the cloud fabric is physical.

20. The networking system, as recited in claim 1, wherein the cloud fabric is made of hardware.

21. The networking system, as recited in claim 1, wherein the cloud fabric is made of software.

22. The networking system, as recited in claim 1, wherein the cloud fabric is made of hardware and software.

23. The networking system, as recited in claim 1, wherein the cloud fabric is operable to deploy one or more native-format applications automatically.

24. The networking system, as recited in claim 1, wherein the one or more user applications are stitched.

25. The networking system, as recited in claim 1, wherein the cloud fabric further includes at least one of Layer 4 through Layer 7 application delivery services, network, and storage.

26. The networking system, as recited in claim 1, wherein the cloud fabric is operable to automatically stitch user applications end-to-end.

27. The networking system, as recited in claim 1, further including a service unit in communication with the master controller and operable to configure data of the networking system based on rules.

28. The networking system, as recited in claim 1, wherein the master controller includes a cloud engine operable to assess multiple clouds relative to an application and resources.

29. The networking system, as recited in claim 1, wherein the master controller includes a network enablement engine.

30. The networking system, as recited in claim 1, wherein the application management unit includes a plug-in unit responsive to applications with different formats and operable to convert the applications with different formats to a native-format.

31. The networking system, as recited in claim 1, wherein the application management unit is operable to report configuration and analytics related to the plurality of resources.

32. The networking system, as recited in claim 1, wherein the selected cloud is a private cloud or a public cloud.

33. The networking system, as recited in claim 1, wherein the selected cloud is a hybrid cloud.

34. The networking system, as recited in claim 1, wherein the cloud fabric is operable to stitch across the selected cloud and at least one additional cloud.

35. The networking system, as recited in claim 1, wherein the cloud fabric is operable to burst across clouds other than the selected cloud and access existing resources.

36. The networking system, as recited in claim 1, wherein upon violation of a policy, the cloud fabric is operable to automatically scale out or scale in the plurality of resources.

37. The networking system, as recited in claim 1, wherein the application management unit is operable to receive applications with different formats and to generate native-format applications from the applications with different formats.

38. The networking system, as recited in claim 1, wherein the Layer 4 through Layer 7 networking devices of the first set of nodes further includes storage systems, servers, routers, switches, or any combination thereof.

39. The networking system, as recited in claim 1, wherein the cloud fabric further includes a service unit and a management unit that are located externally to the VAS unit and the master controller.

40. The networking system, as recited in claim 1, wherein the VAS unit is operable to determine a configuration of the plurality of resources and further operable to determine violation of a policy.

41. The networking system, as recited in claim 1, wherein the VAS unit is operable to provide analytics to the master controller.