This disclosure relates generally to communications systems, more particularly, to providing network resources in a hybrid cloud environment.
Data centers include a complex network of hardware and software that form “clouds,” used to host applications and store data. An enterprise data center, for example, can be used to provide services for a number of customers, with each customer accessing data center resources by way of one or more private networks. Enterprise data centers can provide dynamic “virtual networks” that support server and desktop virtualization. When an enterprise data center runs out of capacity (e.g., storage or computing resources, etc.), an enterprise service provider can add additional hardware, resulting in an increase in data center hardware and/or operational costs. As another option, the enterprise service provider may contract or lease additional computing resources from another cloud, such as, a public cloud data center.
When an enterprise data center shares or leases computing resources from another data center (e.g., a public cloud data center), the resultant combination of computing resources is referred to as a “hybrid” cloud. A hybrid cloud generally includes a cloud infrastructure composed of two or more clouds that inter-operate network communication, such as a network overlay. Therefore hybrid cloud can represent an interaction between multiple clouds, such as private and public clouds, where a private cloud joins a public cloud and utilizes public cloud resources in a secure and scalable way. Despite numerous advantages offered by hybrid cloud environments, the expansion of cloud services, and/or migration of workloads between cloud environments is often onerous and complex.
The embodiments herein may be better understood by referring to the following description in conjunction with the accompanying drawings in which like reference numerals indicate similar elements. Understanding that these drawings depict only exemplary embodiments of the disclosure and are not therefore to be considered to be limiting of its scope, the principles herein are described and explained with additional specificity and detail through the use of the accompanying drawings in which:
Aspects of the disclosed technology relate to methods for facilitating intercloud resource migration. In some implementations, the method can include steps for instantiating a first intercloud fabric provider platform (ICFPP) at a first cloud datacenter, instantiating a second ICFPP at a second cloud datacenter, and receiving a migration request at the first ICFPP, for example, from an intercloud fabric director (ICFD). The migration request can include a request to migrate a virtual machine (VM) workload from the first cloud datacenter to the second cloud datacenter. In some approaches, the method can also include steps for initiating, by the first ICFPP, a migration of the VM workload via the second ICFPP in response to the migration request.
Some cloud architectures support an Intercloud Fabric (ICF) solution that facilitates the extension of enterprise infrastructures (e.g., network and/or storage, etc.) to other cloud environments, such as public clouds. Infrastructure can be used for fulfilling various hybrid cloud use cases, including workload migration, cloud bursting, and/or disaster recovery. ICF cloud extension is sometimes performed through the creation of network extensions that stretch the enterprise network into the cloud datacenter, for example, so that virtual machines (VMs) and related network and security policies are preserved when instantiated on the public datacenter.
As the use of cloud platforms in the computing industry continues to evolve, there is an increasing demand for cloud migration services. In particular, there is an increasing need to share infrastructure and services between different clouds, for example, culminating in a “multicloud.” In such multicloud environments, there are many use cases in which cloud-to-cloud migrations are desired, such as in VM migration, and/or backup disaster relief scenarios. However, conventional ICF cloud orchestration models are challenged by the cloud-to-cloud migration requirements inherent in current multicloud deployments.
In particular, existing orchestration models are typically designed to support enterprise-to-cloud and cloud-to-enterprise hybrid use cases, and therefore rely heavily core application logic residing at the enterprise cloud. Accordingly, aspects of the subject technology provide an improved distributed hybrid orchestration model, for example, in which a novel Intercloud Fabric Director (ICFD) is configured to function as a pure hybrid cloud management platform for use in conjunction with various ICF provider platforms (ICFPP). As discussed below, the novel ICFPPs provided by the subject technology can function as infrastructure gateways to their respective cloud datacenter environments, providing translation logic necessary to convert VM images and resolve infrastructure difference.
Enterprise Datacenter 102 includes applications and logic needed for user control/management over cloud extensions between Enterprise Datacenter 102, Cloud 1 Datacenter 108 and/or Cloud 2 Datacenter 112. Much of this control logic resides in Intercloud Fabric Director (ICFD) 104 that provides a management control platform for ICF system administrators. As such, ICFD 104 can serve as a customer management platform, e.g., on the enterprise side of the network. In some aspects, ICFD 104 can provide role-based end-user and IT administration portals, for example, to provide for a seamless experience in accessing and managing private and public cloud resources.
As illustrated, ICFD 104 includes a management GUI/API 105A, a hybrid cloud management module 105B, an infrastructure orchestration module 105C, an ICFPP adapter 105D, and a cloud adaptor, i.e., Cloud 1 Adapter 105E. Operationally, management GUI/API module 105A is configured to provide various interfaces (e.g., user and programming interfaces) for use by the ICF administrator and/or end user/s to configure and manage the hybrid solution. Hybrid cloud management module 105B functions to provide high level abstractions of how to build a hybrid cloud, and use it to operate various features, such as virtual cloud account abstraction, workload migration, cluster bursting, and/or application level disaster recovery, etc.
In turn, infrastructure orchestration module 105C can be used to provide low-level abstractions of infrastructure orchestrations, such as cloud resources discovery, cloud resource lifecycle management, image format transformation, image transportation, and/or template creation. The VMM/cloud platform infrastructure adapter module 105D can be used to provide a cloud adapter layer, for example, for translating infrastructural orchestration functions into VMM/cloud specific APIs (e.g., vCenter, API, AWS API, OpenStack API, etc.) and submitting API requests to target VMM/cloud API endpoints.
Another component of conventional ICF implementations is the ICF Provider Platform (ICFPP 113), which is typically deployed at the cloud data center, e.g. Cloud 2 Datacenter 112. As provided in the illustrated example of
Similar to ICFD 104, ICFPP 113 includes various software modules, including: an ICF Cloud API module 113A, Provider GUI/API module 113B, core API Translation Logic module 113C, and a VMM/Cloud Platform Infrastructure Adapter module, e.g., Cloud 2 Adapter 113D.
ICF Cloud API 113A provides support for a uniform infrastructure of API interfaces (e.g., ICF Open Cloud API), for example, to help reduce ICFD 104 resource consumption. Provider API 113B (e.g., ICFP Provider GUI/API), provides an interface (e.g., for a system administrator) through which ICFPP 113 can be configured and managed. With the assistance of a cloud specific adapter, core API translation logic module 113C provides for API translation between ICF Cloud API 113A and a given cloud environment, such as, Cloud 2 Datacenter 112. In turn, Cloud 2 Adapter 113D (e.g., a VMM/Cloud Platform Infrastructure Adapter) serves to provide a cloud adapter layer, for example, for translating infrastructure orchestration functions into VMM/cloud specific APIs (e.g., vCenter API, AWS API, OpenStack API), and submitting various API requests to targeted VMM/cloud API end-points.
In some aspects, the hub-and-spoke hybrid cloud model exemplified by
By way of example, an ICF user intending to perform a workload migration, such as migrating VM3 from Cloud 1 Datacenter 108 to Cloud 2 Datacenter 112, would first need to export (transport) a VM image for VM3 from Cloud 1 Datacenter 108 to Enterprise Datacenter 102. Subsequently, based on the image format requirements at the destination cloud (e.g., Cloud 2 Datacenter 112), ICFD 104 would need to transform the image format from the source cloud (i.e., Cloud 1 Datacenter 108) to the proper destination format, i.e., a format for Cloud 2 datacenter 112, such as Qcow2 for the OpenStack based cloud platform. After the VM image transformation is complete, it is transported to the destination cloud datacenter (e.g., Cloud 2 Datacenter), and used to build a VM template for instantiating a new VM instance on the destination datacenter, thus completing transfer of the VM workload associated with VM2 from Cloud 1 Datacenter 108 to Cloud 2 Datacenter 112.
As discussed in further detail below, integrating an ICF Open Cloud API into the new ICFPP 213 enables direct communication between different ICFPP instances instantiated at different datacenters, thereby enabling direct cloud-to-cloud migrations. Additionally, integration of Infrastructure Orchestration module into the ICFPP provides a solution in which infrastructure processing capacity can be scaled, for example, proportional to the number of ICFPP instances.
By way of example, communication between a first ICFPP instance at a first cloud location can be used to directly communicate with a second ICFPP instance at a second cloud location, e.g., via their respective ICF Open Cloud API modules. In contrast to conventional ICFPP implementations, this direct communication can be performed without the continued involvement of the ICFD. Therefore, in such implementations, the ICFPP instances are permitted to issue infrastructure level requests on behalf of the ICFD instance.
Cloud-to-cloud migrations are further facilitated by an Infrastructure Orchestration module of the ICFPP, which supports translation logic required for image conversation and the resolution of infrastructure differences, for example, between the source cloud and the destination cloud. Typical infrastructural operations of the Infrastructure Orchestration module can include, but are not limited to, image format transformation, image transportation, VM life-cycle management, and/or network/storage service management, etc. Further details relating to cloud-to-cloud transfers using ICFD 204 and ICFPP 213 are discussed in connection with
In particular,
Cloud environment 300 includes enterprise datacenter 302, a first cloud (e.g., Cloud 1 304), and a second cloud, e.g., Cloud 2 306. Enterprise datacenter 302 includes ICFD 204 that is configured to enable an ICF end user (not illustrated) to orchestrate cloud infrastructure changes, and/or VM workload migrations between Cloud 1 304 and Cloud 2 306. As illustrated, Cloud 1 304 includes ICFPP 213A and Cloud 2 includes ICFPP 213B, each of which are configured to communicate with ICFD 204 via a respective ICF Cloud Infrastructure API. Additionally, ICFPP 213A and 213B are each configured for direct communication via a respective ICF Open Cloud API.
In operation, an ICF user or administrator (not illustrated) of ICFD 204 can perform a VM workload migration, e.g., from Cloud 1 304 to Cloud 2 306, using ICFPP 213A and 213B. To perform the migration, the ICF user would login to ICFPP 213A, using the ICF Cloud Infrastructure API of ICFD 204 to submit a VM migration request to ICFPP 213A. Upon receiving the VM migration request from ICFD 204, ICFPP 213A in Cloud 1 304 would sign-on to ICFPP 213B in Cloud 2 306, for example, through communication between respective ICF Open Cloud API modules. ICFPP 213A would then transport a VM image to ICFPP 213B.
After VM image transportation is complete, using the Infrastructure Orchestration module, ICFPP 213B can transform the image into a local format (e.g., depending on the cloud platform of Cloud 2 306), and use the transformed image to build a VM template. Subsequently, the VM template is used for instantiating a VM instance on Cloud 2 306. In some aspects, once the VM workload is successfully instantiated on Cloud 2 306, ICFPP 213A in Cloud 1 304 can generate and transmit an operational status back to ICFD 204, for example, to indicate completion of the hybrid cloud operation cycle.
Although the examples described in relation to
Each ICFPP instance contains a respective Infrastructure Orchestration module, as well as an ICF Open Cloud API module, for example, to enable direct communication with other ICF Open Cloud API modules. Additionally, each ICFPP includes an ICF Cloud Infrastructure API module configured for communication with a complementary ICF Cloud Infrastructure API module, for example, located at a datacenter ICFD, such as, ICFD 204, discussed above.
In step 406, a migration request is received at the first ICFPP. The migration request can be issued by an ICF administrator, e.g., from an associated ICFD instantiated on another cloud, such as a remote enterprise datacenter. Although the foregoing example provides an illustration of a migration request for transporting a VM workload directly between clouds (e.g., from Cloud 1 304 to Cloud 2 306), it is understood that other hybrid use cases are contemplated by the present invention. For example, the ICF end user can use an ICFD at a remote datacenter to extend (or contract) infrastructure between two clouds using the ICFPP communication methods mentioned above.
Subsequently, in step 408, a migration of the VM workload is initiated by the first ICFPP. As discussed above, initiation of the VM workload migration by the first ICFPP can be performed by signing into the second ICFPP in the second cloud datacenter. Once the VM image has been transported to the second cloud datacenter, a resident Infrastructure Orchestration module can perform processing necessary to transform the image into a local format, and use the image to build a new VM template that is specific for the local cloud environment. The newly created VM template can then be used to instantiate the corresponding VM workload, and notification can be provided back to the ICFD indicating that the migration has completed.
By creating an orchestration model in which VMM/cloud platform infrastructure related processing is handled by each ICFPP (as opposed to the ICFD), processing overhead for image transportation can be greatly reduced. Additionally, moving infrastructure related processing (e.g., the Infrastructure Orchestration module) into the ICFPP, provides an effective way to scale ICF deployments, and therefore, for diagnosing infrastructure related problems. In some aspects, the orchestration model provided by the subject technology can also be used to address use cases such as enterprise-to-enterprise and region-to-region (same cloud) migrations.
The interfaces 568 are typically provided as interface cards (sometimes referred to as “line cards”). Generally, they control the sending and receiving of data packets over the network and sometimes support other peripherals used with the router 510. Among the interfaces that may be provided are Ethernet interfaces, frame relay interfaces, cable interfaces, DSL interfaces, token ring interfaces, and the like. In addition, various very high-speed interfaces may be provided such as fast token ring interfaces, wireless interfaces, Ethernet interfaces, Gigabit Ethernet interfaces, ATM interfaces, HSSI interfaces, POS interfaces, FDDI interfaces and the like. Generally, these interfaces may include ports appropriate for communication with the appropriate media. In some cases, they may also include an independent processor and, in some instances, volatile RAM. The independent processors may control such communications intensive tasks as packet switching, media control and management. By providing separate processors for the communications intensive tasks, these interfaces allow the master microprocessor 562 to efficiently perform routing computations, network diagnostics, security functions, etc.
Although the system shown in
Regardless of the network device's configuration, it may employ one or more memories or memory modules (including memory 561) configured to store program instructions for the general-purpose network operations and mechanisms for roaming, route optimization and routing functions described herein. The program instructions may control the operation of an operating system and/or one or more applications, for example. The memory or memories may also be configured to store tables such as mobility binding, registration, and association tables, etc.
To enable user interaction with the computing device 600, an input device 645 can represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech and so forth. An output device 635 can also be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems can enable a user to provide multiple types of input to communicate with the computing device 600. The communications interface 640 can generally govern and manage the user input and system output. There is no restriction on operating on any particular hardware arrangement and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.
Storage device 630 is a non-volatile memory and can be a hard disk or other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, random access memories (RAMs) 625, read only memory (ROM) 620, and hybrids thereof.
The storage device 630 can include software modules 632, 634, 636 for controlling the processor 610. Other hardware or software modules are contemplated. The storage device 630 can be connected to the system bus 605. In one aspect, a hardware module that performs a particular function can include the software component stored in a computer-readable medium in connection with the necessary hardware components, such as the processor 610, bus 605, display 635, and so forth, to carry out the function.
Chipset 660 can also interface with one or more communication interfaces 690 that can have different physical interfaces. Such communication interfaces can include interfaces for wired and wireless local area networks, for broadband wireless networks, as well as personal area networks. Some applications of the methods for generating, displaying, and using the GUI disclosed herein can include receiving ordered datasets over the physical interface or be generated by the machine itself by processor 655 analyzing data stored in storage 670 or 675. Further, the machine can receive inputs from a user via user interface components 685 and execute appropriate functions, such as browsing functions by interpreting these inputs using processor 655.
It can be appreciated that example systems 600 and 650 can have more than one processor 610 or be part of a group or cluster of computing devices networked together to provide greater processing capability.
For clarity of explanation, in some instances the present technology may be presented as including individual functional blocks including functional blocks comprising devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software.
In some embodiments the computer-readable storage devices, mediums, and memories can include a cable or wireless signal containing a bit stream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.
Methods according to the above-described examples can be implemented using computer-executable instructions that are stored or otherwise available from computer readable media. Such instructions can comprise, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that may be used to store instructions, information used, and/or information created during methods according to described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, and so on.
Devices implementing methods according to these disclosures can comprise hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include laptops, smart phones, small form factor personal computers, personal digital assistants, rackmount devices, standalone devices, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.
The instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in these disclosures.
Although a variety of examples and other information was used to explain aspects within the scope of the appended claims, no limitation of the claims should be implied based on particular features or arrangements in such examples, as one of ordinary skill would be able to use these examples to derive a wide variety of implementations. Further and although some subject matter may have been described in language specific to examples of structural features and/or method steps, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to these described features or acts. For example, such functionality can be distributed differently or performed in components other than those identified herein. Rather, the described features and steps are disclosed as examples of components of systems and methods within the scope of the appended claims. Moreover, claim language reciting “at least one of” a set indicates that one member of the set or multiple members of the set satisfy the claim.
Number | Name | Date | Kind |
---|---|---|---|
5812773 | Norin | Sep 1998 | A |
5889896 | Meshinsky et al. | Mar 1999 | A |
6108782 | Fletcher et al. | Aug 2000 | A |
6178453 | Mattaway et al. | Jan 2001 | B1 |
6298153 | Oishi | Oct 2001 | B1 |
6343290 | Cossins et al. | Jan 2002 | B1 |
6643260 | Kloth et al. | Nov 2003 | B1 |
6683873 | Kwok et al. | Jan 2004 | B1 |
6721804 | Rubin et al. | Apr 2004 | B1 |
6733449 | Krishnamurthy et al. | May 2004 | B1 |
6735631 | Oehrke et al. | May 2004 | B1 |
6885670 | Regula | Apr 2005 | B1 |
6996615 | McGuire | Feb 2006 | B1 |
7054930 | Cheriton | May 2006 | B1 |
7058706 | Lyer et al. | Jun 2006 | B1 |
7062571 | Dale et al. | Jun 2006 | B1 |
7076397 | Ding et al. | Jul 2006 | B2 |
7111177 | Chauvel et al. | Sep 2006 | B1 |
7212490 | Kao et al. | May 2007 | B1 |
7277948 | Igarashi et al. | Oct 2007 | B2 |
7313667 | Pullela et al. | Dec 2007 | B1 |
7379846 | Williams et al. | May 2008 | B1 |
7480672 | Hahn et al. | Jan 2009 | B2 |
7496043 | Leong et al. | Feb 2009 | B1 |
7536476 | Alleyne | May 2009 | B1 |
7567504 | Darling et al. | Jul 2009 | B2 |
7606147 | Luft et al. | Oct 2009 | B2 |
7647594 | Togawa | Jan 2010 | B2 |
7684322 | Sand et al. | Mar 2010 | B2 |
7773510 | Back et al. | Aug 2010 | B2 |
7808897 | Mehta et al. | Oct 2010 | B1 |
7881957 | Cohen et al. | Feb 2011 | B1 |
7917647 | Cooper et al. | Mar 2011 | B2 |
8010598 | Tanimoto | Aug 2011 | B2 |
8028071 | Mahalingam et al. | Sep 2011 | B1 |
8041714 | Aymeloglu et al. | Oct 2011 | B2 |
8121117 | Amdahl et al. | Feb 2012 | B1 |
8171415 | Appleyard et al. | May 2012 | B2 |
8234377 | Cohn | Jul 2012 | B2 |
8244559 | Horvitz et al. | Aug 2012 | B2 |
8250215 | Stienhans et al. | Aug 2012 | B2 |
8280880 | Aymeloglu et al. | Oct 2012 | B1 |
8284664 | Aybay et al. | Oct 2012 | B1 |
8284776 | Petersen | Oct 2012 | B2 |
8301746 | Head et al. | Oct 2012 | B2 |
8345692 | Smith | Jan 2013 | B2 |
8406141 | Couturier et al. | Mar 2013 | B1 |
8407413 | Yucel et al. | Mar 2013 | B1 |
8448171 | Donnellan et al. | May 2013 | B2 |
8477610 | Zuo et al. | Jul 2013 | B2 |
8478961 | Bozek | Jul 2013 | B2 |
8495252 | Lais et al. | Jul 2013 | B2 |
8495356 | Ashok et al. | Jul 2013 | B2 |
8510469 | Portolani | Aug 2013 | B2 |
8514868 | Hill | Aug 2013 | B2 |
8532108 | Li et al. | Sep 2013 | B2 |
8533687 | Greifeneder et al. | Sep 2013 | B1 |
8547974 | Guruswamy et al. | Oct 2013 | B1 |
8560639 | Murphy et al. | Oct 2013 | B2 |
8560663 | Baucke et al. | Oct 2013 | B2 |
8589543 | Dutta et al. | Nov 2013 | B2 |
8590050 | Nagpal et al. | Nov 2013 | B2 |
8611356 | Yu et al. | Dec 2013 | B2 |
8612625 | Andreis et al. | Dec 2013 | B2 |
8630291 | Shaffer et al. | Jan 2014 | B2 |
8639787 | Lagergren et al. | Jan 2014 | B2 |
8656024 | Krishnan et al. | Feb 2014 | B2 |
8660129 | Brendel et al. | Feb 2014 | B1 |
8719804 | Jain | May 2014 | B2 |
8775576 | Hebert et al. | Jul 2014 | B2 |
8797867 | Chen et al. | Aug 2014 | B1 |
8805951 | Faibish et al. | Aug 2014 | B1 |
8831000 | Mishra | Sep 2014 | B2 |
8850182 | Fritz et al. | Sep 2014 | B1 |
8856339 | Mestery | Oct 2014 | B2 |
8909780 | Dickinson et al. | Dec 2014 | B1 |
8909928 | Ahmad et al. | Dec 2014 | B2 |
8918510 | Gmach et al. | Dec 2014 | B2 |
8924720 | Raghuram et al. | Dec 2014 | B2 |
8930747 | Levijarvi et al. | Jan 2015 | B2 |
8938775 | Roth et al. | Jan 2015 | B1 |
8954544 | Edwards | Feb 2015 | B2 |
8959526 | Kansal et al. | Feb 2015 | B2 |
8977754 | Curry, Jr. et al. | Mar 2015 | B2 |
9003006 | Xia | Apr 2015 | B2 |
9009697 | Breiter et al. | Apr 2015 | B2 |
9015324 | Jackson | Apr 2015 | B2 |
9043439 | Bicket et al. | May 2015 | B2 |
9049115 | Rajendran et al. | Jun 2015 | B2 |
9063789 | Beaty et al. | Jun 2015 | B2 |
9065727 | Liu et al. | Jun 2015 | B1 |
9075649 | Bushman et al. | Jul 2015 | B1 |
9104334 | Madhusudana et al. | Aug 2015 | B2 |
9104460 | Jansen | Aug 2015 | B2 |
9164795 | Vincent | Oct 2015 | B1 |
9167050 | Durazzo et al. | Oct 2015 | B2 |
9201701 | Boldyrev et al. | Dec 2015 | B2 |
9201704 | Chang | Dec 2015 | B2 |
9203784 | Chang | Dec 2015 | B2 |
9223634 | Chang | Dec 2015 | B2 |
9244776 | Koza et al. | Jan 2016 | B2 |
9251114 | Ancin et al. | Feb 2016 | B1 |
9264478 | Hon et al. | Feb 2016 | B2 |
9276911 | Wang | Mar 2016 | B2 |
9313048 | Chang et al. | Apr 2016 | B2 |
9361192 | Smith et al. | Jun 2016 | B2 |
9380075 | He et al. | Jun 2016 | B2 |
9389773 | Koohestanian | Jul 2016 | B2 |
9411534 | Lakshman | Aug 2016 | B2 |
9411626 | Ghosh | Aug 2016 | B2 |
9424151 | Lakshman | Aug 2016 | B2 |
9432294 | Sharma et al. | Aug 2016 | B1 |
9438534 | Xia | Sep 2016 | B2 |
9444744 | Sharma et al. | Sep 2016 | B1 |
9473365 | Melander et al. | Oct 2016 | B2 |
9483205 | Lakshman | Nov 2016 | B2 |
9503530 | Niedzielski | Nov 2016 | B1 |
9525564 | Lee | Dec 2016 | B2 |
9553887 | Thakkar | Jan 2017 | B2 |
9558078 | Farlee et al. | Jan 2017 | B2 |
9558085 | Lakshman | Jan 2017 | B2 |
9560037 | Bartz | Jan 2017 | B2 |
9563480 | Messerli | Feb 2017 | B2 |
9600320 | Hamilton, II | Mar 2017 | B2 |
9606826 | Ghosh | Mar 2017 | B2 |
9606828 | Ghosh | Mar 2017 | B2 |
9613078 | Vermeulen et al. | Apr 2017 | B2 |
9626212 | Beveridge | Apr 2017 | B2 |
9628471 | Sundaram et al. | Apr 2017 | B1 |
9632858 | Sasturkar et al. | Apr 2017 | B2 |
9658876 | Chang et al. | May 2017 | B2 |
9692802 | Bicket et al. | Jun 2017 | B2 |
9727359 | Tsirkin | Aug 2017 | B2 |
9736063 | Wan et al. | Aug 2017 | B2 |
9755858 | Bagepalli | Sep 2017 | B2 |
9787582 | Zenker | Oct 2017 | B1 |
9792245 | Raghavan et al. | Oct 2017 | B2 |
9804988 | Ayoub et al. | Oct 2017 | B1 |
9851997 | Gough | Dec 2017 | B2 |
9864530 | Lakshman | Jan 2018 | B2 |
9875063 | Lakshman | Jan 2018 | B2 |
9935896 | Chang | Apr 2018 | B2 |
9954783 | Thirumurthi et al. | Apr 2018 | B1 |
10050951 | Mathaiyan | Aug 2018 | B2 |
10067722 | Lakshman | Sep 2018 | B2 |
10382426 | Falodiya | Aug 2019 | B2 |
20020004900 | Patel | Jan 2002 | A1 |
20020073337 | Ioele et al. | Jun 2002 | A1 |
20020143928 | Maltz et al. | Oct 2002 | A1 |
20020166117 | Abrams et al. | Nov 2002 | A1 |
20020174216 | Shorey et al. | Nov 2002 | A1 |
20030018591 | Komisky | Jan 2003 | A1 |
20030056001 | Mate et al. | Mar 2003 | A1 |
20030228585 | Inoko et al. | Dec 2003 | A1 |
20040004941 | Malan et al. | Jan 2004 | A1 |
20040095237 | Chen et al. | May 2004 | A1 |
20040131059 | Ayyakad et al. | Jul 2004 | A1 |
20040264481 | Darling et al. | Dec 2004 | A1 |
20050060418 | Sorokopud | Mar 2005 | A1 |
20050125424 | Herriott et al. | Jun 2005 | A1 |
20060059558 | Selep et al. | Mar 2006 | A1 |
20060104286 | Cheriton | May 2006 | A1 |
20060120575 | Ahn et al. | Jun 2006 | A1 |
20060126665 | Ward et al. | Jun 2006 | A1 |
20060146825 | Hofstaedter et al. | Jul 2006 | A1 |
20060155875 | Cheriton | Jul 2006 | A1 |
20060168338 | Bruegl et al. | Jul 2006 | A1 |
20060294207 | Barsness et al. | Dec 2006 | A1 |
20070011330 | Dinker et al. | Jan 2007 | A1 |
20070174663 | Crawford et al. | Jul 2007 | A1 |
20070223487 | Kajekar et al. | Sep 2007 | A1 |
20070242830 | Conrado et al. | Oct 2007 | A1 |
20080005293 | Bhargava et al. | Jan 2008 | A1 |
20080084880 | Dharwadkar | Apr 2008 | A1 |
20080165778 | Ertemalp | Jul 2008 | A1 |
20080198752 | Fan et al. | Aug 2008 | A1 |
20080201711 | Amir Husain | Aug 2008 | A1 |
20080235755 | Blaisdell et al. | Sep 2008 | A1 |
20090006527 | Gingell, Jr. et al. | Jan 2009 | A1 |
20090010277 | Halbraich et al. | Jan 2009 | A1 |
20090019367 | Cavagnari et al. | Jan 2009 | A1 |
20090031312 | Mausolf et al. | Jan 2009 | A1 |
20090083183 | Rao et al. | Mar 2009 | A1 |
20090138763 | Arnold | May 2009 | A1 |
20090177775 | Radia et al. | Jul 2009 | A1 |
20090178058 | Stillwell, III et al. | Jul 2009 | A1 |
20090182874 | Morford et al. | Jul 2009 | A1 |
20090265468 | Annambhotla et al. | Oct 2009 | A1 |
20090265753 | Anderson et al. | Oct 2009 | A1 |
20090293056 | Ferris | Nov 2009 | A1 |
20090300608 | Ferris et al. | Dec 2009 | A1 |
20090313562 | Appleyard et al. | Dec 2009 | A1 |
20090323706 | Germain et al. | Dec 2009 | A1 |
20090328031 | Pouyadou et al. | Dec 2009 | A1 |
20100042720 | Stienhans et al. | Feb 2010 | A1 |
20100061250 | Nugent | Mar 2010 | A1 |
20100115341 | Baker et al. | May 2010 | A1 |
20100131765 | Bromley et al. | May 2010 | A1 |
20100191783 | Mason et al. | Jul 2010 | A1 |
20100192157 | Jackson et al. | Jul 2010 | A1 |
20100205601 | Abbas et al. | Aug 2010 | A1 |
20100211782 | Auradkar et al. | Aug 2010 | A1 |
20100217886 | Seren et al. | Aug 2010 | A1 |
20100293270 | Augenstein et al. | Nov 2010 | A1 |
20100318609 | Lahiri et al. | Dec 2010 | A1 |
20100325199 | Park et al. | Dec 2010 | A1 |
20100325257 | Goel et al. | Dec 2010 | A1 |
20100325441 | Laurie et al. | Dec 2010 | A1 |
20100333116 | Prahlad et al. | Dec 2010 | A1 |
20110016214 | Jackson | Jan 2011 | A1 |
20110035754 | Srinivasan | Feb 2011 | A1 |
20110055396 | Dehaan | Mar 2011 | A1 |
20110055398 | Dehaan et al. | Mar 2011 | A1 |
20110055470 | Portolani | Mar 2011 | A1 |
20110072489 | Parann-Nissany | Mar 2011 | A1 |
20110075667 | Li et al. | Mar 2011 | A1 |
20110110382 | Jabr et al. | May 2011 | A1 |
20110116443 | Yu et al. | May 2011 | A1 |
20110126099 | Anderson et al. | May 2011 | A1 |
20110138055 | Daly et al. | Jun 2011 | A1 |
20110145413 | Dawson et al. | Jun 2011 | A1 |
20110145657 | Bishop et al. | Jun 2011 | A1 |
20110173303 | Rider | Jul 2011 | A1 |
20110185063 | Head et al. | Jul 2011 | A1 |
20110199902 | Leavy et al. | Aug 2011 | A1 |
20110213687 | Ferris et al. | Sep 2011 | A1 |
20110213966 | Fu et al. | Sep 2011 | A1 |
20110219434 | Betz et al. | Sep 2011 | A1 |
20110231715 | Kunii et al. | Sep 2011 | A1 |
20110231899 | Pulier et al. | Sep 2011 | A1 |
20110239039 | Dieffenbach et al. | Sep 2011 | A1 |
20110252327 | Awasthi et al. | Oct 2011 | A1 |
20110261811 | Battestilli et al. | Oct 2011 | A1 |
20110261828 | Smith | Oct 2011 | A1 |
20110276675 | Singh et al. | Nov 2011 | A1 |
20110276951 | Jain | Nov 2011 | A1 |
20110295998 | Ferris et al. | Dec 2011 | A1 |
20110305149 | Scott et al. | Dec 2011 | A1 |
20110307531 | Gaponenko et al. | Dec 2011 | A1 |
20110320870 | Kenigsberg et al. | Dec 2011 | A1 |
20120005724 | Lee | Jan 2012 | A1 |
20120023418 | Frields et al. | Jan 2012 | A1 |
20120054367 | Ramakrishnan et al. | Mar 2012 | A1 |
20120072318 | Akiyama et al. | Mar 2012 | A1 |
20120072578 | Alam | Mar 2012 | A1 |
20120072581 | Tung et al. | Mar 2012 | A1 |
20120072985 | Davne et al. | Mar 2012 | A1 |
20120072992 | Arasaratnam et al. | Mar 2012 | A1 |
20120084445 | Brock et al. | Apr 2012 | A1 |
20120084782 | Chou et al. | Apr 2012 | A1 |
20120096134 | Suit | Apr 2012 | A1 |
20120102193 | Rathore et al. | Apr 2012 | A1 |
20120102199 | Hopmann et al. | Apr 2012 | A1 |
20120131174 | Ferris et al. | May 2012 | A1 |
20120137215 | Kawara | May 2012 | A1 |
20120137289 | Nolterieke | May 2012 | A1 |
20120158967 | Sedayao et al. | Jun 2012 | A1 |
20120159097 | Jennas, II et al. | Jun 2012 | A1 |
20120166649 | Watanabe et al. | Jun 2012 | A1 |
20120167094 | Suit | Jun 2012 | A1 |
20120173541 | Venkatarannani | Jul 2012 | A1 |
20120173710 | Rodriguez | Jul 2012 | A1 |
20120179909 | Sagi et al. | Jul 2012 | A1 |
20120180044 | Donnellan et al. | Jul 2012 | A1 |
20120182891 | Lee et al. | Jul 2012 | A1 |
20120185632 | Lais et al. | Jul 2012 | A1 |
20120185913 | Martinez et al. | Jul 2012 | A1 |
20120192016 | Gotesdyner et al. | Jul 2012 | A1 |
20120192075 | Ebtekar et al. | Jul 2012 | A1 |
20120201135 | Ding et al. | Aug 2012 | A1 |
20120203908 | Beaty et al. | Aug 2012 | A1 |
20120204169 | Breiter et al. | Aug 2012 | A1 |
20120204187 | Breiter et al. | Aug 2012 | A1 |
20120214506 | Skaaksrud et al. | Aug 2012 | A1 |
20120222106 | Kuehl | Aug 2012 | A1 |
20120236716 | Anbazhagan et al. | Sep 2012 | A1 |
20120240113 | Hur | Sep 2012 | A1 |
20120265976 | Spiers et al. | Oct 2012 | A1 |
20120272025 | Park et al. | Oct 2012 | A1 |
20120272243 | Nolterieke | Oct 2012 | A1 |
20120281706 | Agarwal et al. | Nov 2012 | A1 |
20120281708 | Chauhan et al. | Nov 2012 | A1 |
20120290647 | Ellison et al. | Nov 2012 | A1 |
20120297238 | Watson et al. | Nov 2012 | A1 |
20120311106 | Morgan | Dec 2012 | A1 |
20120311568 | Jansen | Dec 2012 | A1 |
20120324092 | Brown et al. | Dec 2012 | A1 |
20120324114 | Dutta et al. | Dec 2012 | A1 |
20130003567 | Gallant et al. | Jan 2013 | A1 |
20130013248 | Brugler et al. | Jan 2013 | A1 |
20130036213 | Hasan et al. | Feb 2013 | A1 |
20130044636 | Koponen et al. | Feb 2013 | A1 |
20130066939 | Shao | Mar 2013 | A1 |
20130066940 | Shao | Mar 2013 | A1 |
20130069950 | Adam et al. | Mar 2013 | A1 |
20130080509 | Wang | Mar 2013 | A1 |
20130080624 | Nagai et al. | Mar 2013 | A1 |
20130091557 | Gurrapu | Apr 2013 | A1 |
20130097601 | Podvratnik et al. | Apr 2013 | A1 |
20130104140 | Meng et al. | Apr 2013 | A1 |
20130111540 | Sabin | May 2013 | A1 |
20130117337 | Dunham | May 2013 | A1 |
20130124712 | Parker | May 2013 | A1 |
20130125124 | Kempf et al. | May 2013 | A1 |
20130138816 | Kuo et al. | May 2013 | A1 |
20130144978 | Jain et al. | Jun 2013 | A1 |
20130152076 | Patel | Jun 2013 | A1 |
20130152175 | Hromoko et al. | Jun 2013 | A1 |
20130159097 | Schory et al. | Jun 2013 | A1 |
20130159496 | Hamilton et al. | Jun 2013 | A1 |
20130160008 | Cawlfield et al. | Jun 2013 | A1 |
20130162753 | Hendrickson et al. | Jun 2013 | A1 |
20130169666 | Pacheco et al. | Jul 2013 | A1 |
20130179941 | McGloin et al. | Jul 2013 | A1 |
20130182712 | Aguayo et al. | Jul 2013 | A1 |
20130185413 | Beaty et al. | Jul 2013 | A1 |
20130185433 | Zhu et al. | Jul 2013 | A1 |
20130191106 | Kephart et al. | Jul 2013 | A1 |
20130198050 | Shroff et al. | Aug 2013 | A1 |
20130198374 | Zalmanovitch et al. | Aug 2013 | A1 |
20130204849 | Chacko | Aug 2013 | A1 |
20130232491 | Radhakrishnan et al. | Sep 2013 | A1 |
20130232492 | Wang | Sep 2013 | A1 |
20130246588 | Borowicz et al. | Sep 2013 | A1 |
20130250770 | Zou et al. | Sep 2013 | A1 |
20130254415 | Fullen et al. | Sep 2013 | A1 |
20130262347 | Dodson | Oct 2013 | A1 |
20130283364 | Chang et al. | Oct 2013 | A1 |
20130291121 | Iovanov | Oct 2013 | A1 |
20130297769 | Chang et al. | Nov 2013 | A1 |
20130318240 | Hebert et al. | Nov 2013 | A1 |
20130318546 | Kothuri et al. | Nov 2013 | A1 |
20130339949 | Spiers et al. | Dec 2013 | A1 |
20140006481 | Frey et al. | Jan 2014 | A1 |
20140006535 | Reddy | Jan 2014 | A1 |
20140006585 | Dunbar et al. | Jan 2014 | A1 |
20140007092 | Barbee | Jan 2014 | A1 |
20140019639 | Ueno | Jan 2014 | A1 |
20140040473 | Ho et al. | Feb 2014 | A1 |
20140040883 | Tompkins | Feb 2014 | A1 |
20140052877 | Mao | Feb 2014 | A1 |
20140059310 | Du et al. | Feb 2014 | A1 |
20140074850 | Noel et al. | Mar 2014 | A1 |
20140075048 | Yuksel et al. | Mar 2014 | A1 |
20140075108 | Dong et al. | Mar 2014 | A1 |
20140075357 | Flores et al. | Mar 2014 | A1 |
20140075501 | Srinivasan et al. | Mar 2014 | A1 |
20140089727 | Cherkasova et al. | Mar 2014 | A1 |
20140098762 | Ghai et al. | Apr 2014 | A1 |
20140108985 | Scott et al. | Apr 2014 | A1 |
20140122560 | Ramey et al. | May 2014 | A1 |
20140136779 | Guha et al. | May 2014 | A1 |
20140140211 | Chandrasekaran et al. | May 2014 | A1 |
20140141720 | Princen et al. | May 2014 | A1 |
20140156557 | Zeng et al. | Jun 2014 | A1 |
20140160924 | Pfautz et al. | Jun 2014 | A1 |
20140164486 | Ravichandran et al. | Jun 2014 | A1 |
20140188825 | Muthukkaruppan et al. | Jul 2014 | A1 |
20140189095 | Lindberg et al. | Jul 2014 | A1 |
20140189125 | Amies et al. | Jul 2014 | A1 |
20140215471 | Cherkasova | Jul 2014 | A1 |
20140222953 | Karve et al. | Aug 2014 | A1 |
20140244851 | Lee | Aug 2014 | A1 |
20140245298 | Zhou et al. | Aug 2014 | A1 |
20140269266 | Filsfils et al. | Sep 2014 | A1 |
20140280805 | Sawalha | Sep 2014 | A1 |
20140282536 | Dave et al. | Sep 2014 | A1 |
20140282611 | Campbell et al. | Sep 2014 | A1 |
20140282669 | McMillan | Sep 2014 | A1 |
20140282889 | Ishaya et al. | Sep 2014 | A1 |
20140289200 | Kato | Sep 2014 | A1 |
20140297569 | Clark et al. | Oct 2014 | A1 |
20140297835 | Buys | Oct 2014 | A1 |
20140314078 | Jilani | Oct 2014 | A1 |
20140317261 | Shatzkamer et al. | Oct 2014 | A1 |
20140366155 | Chang et al. | Dec 2014 | A1 |
20140372567 | Ganesh et al. | Dec 2014 | A1 |
20150006470 | Mohan | Jan 2015 | A1 |
20150033086 | Sasturkar et al. | Jan 2015 | A1 |
20150043335 | Testicioglu et al. | Feb 2015 | A1 |
20150043576 | Dixon et al. | Feb 2015 | A1 |
20150052247 | Threefoot et al. | Feb 2015 | A1 |
20150052517 | Raghu et al. | Feb 2015 | A1 |
20150058382 | St. Laurent et al. | Feb 2015 | A1 |
20150058459 | Amendjian et al. | Feb 2015 | A1 |
20150058557 | Madhusudana et al. | Feb 2015 | A1 |
20150070516 | Shoemake et al. | Mar 2015 | A1 |
20150071285 | Kumar et al. | Mar 2015 | A1 |
20150089478 | Cheluvaraju et al. | Mar 2015 | A1 |
20150100471 | Curry, Jr. et al. | Apr 2015 | A1 |
20150106802 | Ivanov et al. | Apr 2015 | A1 |
20150106805 | Melander et al. | Apr 2015 | A1 |
20150109923 | Hwang | Apr 2015 | A1 |
20150117199 | Chinnaiah Sankaran et al. | Apr 2015 | A1 |
20150117458 | Gurkan et al. | Apr 2015 | A1 |
20150120914 | Wada et al. | Apr 2015 | A1 |
20150149828 | Mukerji et al. | May 2015 | A1 |
20150178133 | Phelan et al. | Jun 2015 | A1 |
20150215819 | Bosch et al. | Jul 2015 | A1 |
20150227405 | Jan et al. | Aug 2015 | A1 |
20150242204 | Hassine et al. | Aug 2015 | A1 |
20150249709 | Teng et al. | Sep 2015 | A1 |
20150271199 | Bradley et al. | Sep 2015 | A1 |
20150280980 | Bitar | Oct 2015 | A1 |
20150281067 | Wu | Oct 2015 | A1 |
20150281113 | Siciliano et al. | Oct 2015 | A1 |
20150309908 | Pearson et al. | Oct 2015 | A1 |
20150319063 | Zourzouvillys et al. | Nov 2015 | A1 |
20150326524 | Tankala et al. | Nov 2015 | A1 |
20150339210 | Kopp et al. | Nov 2015 | A1 |
20150373108 | Fleming et al. | Dec 2015 | A1 |
20150379062 | Vermeulen et al. | Dec 2015 | A1 |
20160011925 | Kulkarni et al. | Jan 2016 | A1 |
20160013990 | Kulkarni et al. | Jan 2016 | A1 |
20160062786 | Meng et al. | Mar 2016 | A1 |
20160065417 | Sapuram et al. | Mar 2016 | A1 |
20160094398 | Choudhury et al. | Mar 2016 | A1 |
20160094480 | Kulkarni et al. | Mar 2016 | A1 |
20160094643 | Jain et al. | Mar 2016 | A1 |
20160094894 | Inayatullah et al. | Mar 2016 | A1 |
20160099847 | Melander et al. | Apr 2016 | A1 |
20160099873 | Gerö et al. | Apr 2016 | A1 |
20160103699 | Thakkar | Apr 2016 | A1 |
20160103838 | Sainani et al. | Apr 2016 | A1 |
20160105321 | Thakkar | Apr 2016 | A1 |
20160105393 | Thakkar et al. | Apr 2016 | A1 |
20160127184 | Bursell | May 2016 | A1 |
20160134557 | Steinder et al. | May 2016 | A1 |
20160147676 | Cha et al. | May 2016 | A1 |
20160162436 | Raghavan et al. | Jun 2016 | A1 |
20160164914 | Madhav et al. | Jun 2016 | A1 |
20160188527 | Cherian et al. | Jun 2016 | A1 |
20160234071 | Nambiar et al. | Aug 2016 | A1 |
20160239399 | Babu et al. | Aug 2016 | A1 |
20160248669 | Natarajan | Aug 2016 | A1 |
20160253078 | Ebtekar et al. | Sep 2016 | A1 |
20160254968 | Ebtekar et al. | Sep 2016 | A1 |
20160259662 | Ghosh | Sep 2016 | A1 |
20160261564 | Foxhoven et al. | Sep 2016 | A1 |
20160277368 | Narayanaswamy et al. | Sep 2016 | A1 |
20160292611 | Boe et al. | Oct 2016 | A1 |
20160352682 | Chang | Dec 2016 | A1 |
20160378389 | Hrischuk et al. | Dec 2016 | A1 |
20170005948 | Melander et al. | Jan 2017 | A1 |
20170024260 | Chandrasekaran et al. | Jan 2017 | A1 |
20170026470 | Bhargava et al. | Jan 2017 | A1 |
20170034199 | Zaw | Feb 2017 | A1 |
20170041342 | Efremov et al. | Feb 2017 | A1 |
20170054659 | Ergin et al. | Feb 2017 | A1 |
20170060615 | Thakkar | Mar 2017 | A1 |
20170063674 | Maskalik et al. | Mar 2017 | A1 |
20170097841 | Chang et al. | Apr 2017 | A1 |
20170099188 | Chang et al. | Apr 2017 | A1 |
20170104755 | Arregoces | Apr 2017 | A1 |
20170126583 | Xia | May 2017 | A1 |
20170147297 | Krishnamurthy et al. | May 2017 | A1 |
20170163569 | Koganti | Jun 2017 | A1 |
20170171157 | Hristov | Jun 2017 | A1 |
20170171158 | Hoy et al. | Jun 2017 | A1 |
20170192823 | Karaje et al. | Jul 2017 | A1 |
20170264663 | Bicket et al. | Sep 2017 | A1 |
20170277555 | Gautam | Sep 2017 | A1 |
20170302521 | Lui et al. | Oct 2017 | A1 |
20170310556 | Knowles et al. | Oct 2017 | A1 |
20170317932 | Paramasivam | Nov 2017 | A1 |
20170339070 | Chang et al. | Nov 2017 | A1 |
20180069885 | Patterson et al. | Mar 2018 | A1 |
20180173372 | Greenspan et al. | Jun 2018 | A1 |
20180174060 | Velez-Rojas et al. | Jun 2018 | A1 |
Number | Date | Country |
---|---|---|
101719930 | Jun 2010 | CN |
101394360 | Jul 2011 | CN |
102164091 | Aug 2011 | CN |
104320342 | Jan 2015 | CN |
105740084 | Jul 2016 | CN |
2228719 | Sep 2010 | EP |
2439637 | Apr 2012 | EP |
2645253 | Nov 2014 | EP |
10-2015-0070676 | May 2015 | KR |
M394537 | Dec 2010 | TW |
WO 2009155574 | Dec 2009 | WO |
WO 2010030915 | Mar 2010 | WO |
WO 2013158707 | Oct 2013 | WO |
Entry |
---|
Al-Harbi, S.H., et al., “Adapting γ-means for supervised clustering,” Jun. 2006, Applied Intelligence, vol. 24, Issue 3, pp. 219-226. |
Bohner, Shawn A., “Extending Software Change Impact Analysis into COTS Components,” 2003, IEEE, 8 pages. |
Hood, C. S., et al., “Automated Proactive Anomaly Detection,” 1997, Springer Science and Business Media Dordrecht , pp. 688-699. |
Vilalta R., et al., “An efficient approach to external cluster assessment with an application to martian topography,” Feb. 2007, 23 pages, Data Mining and Knowledge Discovery 14.1: 1-23. New York: Springer Science & Business Media. |
Amedro, Brian, et al., “An Efficient Framework for Running Applications on Clusters, Grids and Cloud,” 2010, 17 pages. |
Author Unknown, “A Look at DeltaCloud: The Multi-Cloud API,” Feb. 17, 2012, 4 pages. |
Author Unknown, “About Deltacloud,” Apache Software Foundation, Aug. 18, 2013, 1 page. |
Author Unknown, “Architecture for Managing Clouds, A White Paper from the Open Cloud Standards Incubator,” Version 1.0.0, Document No. DSP-IS0102, Jun. 18, 2010, 57 pages. |
Author Unknown, “Cloud Infrastructure Management Interface—Common Information Model (CIMI-CIM),” Document No. DSP0264, Version 1.0.0, Dec. 14, 2012, 21 pages. |
Author Unknown, “Cloud Infrastructure Management Interface (CIMI) Primer,” Document No. DSP2027, Version 1.0.1, Sep. 12, 2012, 30 pages. |
Author Unknown, “cloudControl Documentation,” Aug. 25, 2013, 14 pages. |
Author Unknown, “Interoperable Clouds, A White Paper from the Open Cloud Standards Incubator,” Version 1.0.0, Document No. DSP-IS0101, Nov. 11, 2009, 21 pages. |
Author Unknown, “Microsoft Cloud Edge Gateway (MCE) Series Appliance,” Iron Networks, Inc., 2014, 4 pages. |
Author Unknown, “Use Cases and Interactions for Managing Clouds, A White Paper from the Open Cloud Standards Incubator,” Version 1.0.0, Document No. DSP-ISO0103, Jun. 16, 2010, 75 pages. |
Author Unknown, “Apache Ambari Meetup What's New,” Hortonworks Inc., Sep. 2013, 28 pages. |
Author Unknown, “Introduction,” Apache Ambari project, Apache Software Foundation, 2014, 1 page. |
Citrix, “Citrix StoreFront 2.0” White Paper, Proof of Concept Implementation Guide, Citrix Systems, Inc., 2013, 48 pages. |
Citrix, “Deployment Practices and Guidelines for NetScaler 10.5 on Amazon Web Services,” White Paper, citrix.com, 2014, 14 pages. |
Gedymin, Adam, “Cloud Computing with an emphasis on Google App Engine,” Sep. 2011, 146 pages. |
Good, Nathan A., “Use Apache Deltacloud to administer multiple instances with a single API,” Dec. 17, 2012, 7 pages. |
Kunz, Thomas, et al., “OmniCloud—The Secure and Flexible Use of Cloud Storage Services,” 2014, 30 pages. |
Logan, Marcus, “Hybrid Cloud Application Architecture for Elastic Java-Based Web Applications,” F5 Deployment Guide Version 1.1, 2016, 65 pages. |
Lynch, Sean, “Monitoring cache with Claspin” Facebook Engineering, Sep. 19, 2012, 5 pages. |
Meireles, Fernando Miguel Dias, “Integrated Management of Cloud Computing Resources,” 2013-2014, 286 pages. |
Mu, Shuai, et al., “uLibCloud: Providing High Available and Uniform Accessing to Multiple Cloud Storages,” 2012 IEEE, 8 pages. |
Sun, Aobing, et al., “IaaS Public Cloud Computing Platform Scheduling Model and Optimization Analysis,” Int. J. Communications, Network and System Sciences, 2011, 4, 803-811, 9 pages. |
Szymaniak, Michal, et al., “Latency-Driven Replica Placement”, vol. 47 No. 8, IPSJ Journal, Aug. 2006, 12 pages. |
Toews, Everett, “Introduction to Apache jclouds,” Apr. 7, 2014, 23 pages. |
Von Laszewski, Gregor, et al., “Design of a Dynamic Provisioning System for a Federated Cloud and Bare-metal Environment,” 2012, 8 pages. |
Ye, Xianglong, et al., “A Novel Blocks Placement Strategy for Hadoop,” 2012 IEEE/ACTS 11th International Conference on Computer and Information Science, 2012 IEEE, 5 pages. |
Author Unknown, “5 Benefits of a Storage Gateway in the Cloud,” Blog, TwinStrata, Inc., Jul. 25, 2012, XP055141645, 4 pages, https://web.archive.org/web/20120725092619/http://blog.twinstrata.com/2012/07/10//5-benefits-of-a-storage-gateway-in-the-cloud. |
Author Unknown, “Joint Cisco and VMWare Solution for Optimizing Virtual Desktop Delivery: Data Center 3.0: Solutions to Accelerate Data Center Virtualization,” Cisco Systems, Inc. and VMware, Inc., Sep. 2008, 10 pages. |
Author Unknown, “Open Data Center Alliance Usage: Virtual Machine (VM) Interoperability in a Hybrid Cloud Environment Rev. 1.2,” Open Data Center Alliance, Inc., 2013, 18 pages. |
Author Unknown, “Real-Time Performance Monitoring on Juniper Networks Devices, Tips and Tools for Assessing and Analyzing Network Efficiency,” Juniper Networks, Inc., May 2010, 35 pages. |
Beyer, Steffen, “Module “Data::Locations?!”,” YAPC::Europe, London, UK,ICA, Sep. 22-24, 2000, XP002742700, 15 pages. |
Borovick, Lucinda, et al., “Architecting the Network for the Cloud,” IDC White Paper, Jan. 2011, 8 pages. |
Bosch, Greg, “Virtualization,” last modified Apr. 2012 by B. Davison, 33 pages. |
Broadcasters Audience Research Board, “What's Next,” http://lwww.barb.co.uk/whats-next, accessed Jul. 22, 2015, 2 pages. |
Cisco Systems, Inc. “Best Practices in Deploying Cisco Nexus 1000V Series Switches on Cisco UCS B and C Series Cisco UCS Manager Servers,” Cisco White Paper, Apr. 2011, 36 pages, http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9902/white_paper_c11-558242.pdf. |
Cisco Systems, Inc., “Cisco Unified Network Services: Overcome Obstacles to Cloud-Ready Deployments,” Cisco White Paper, Jan. 2011, 6 pages. |
Cisco Systems, Inc., “Cisco Intercloud Fabric: Hybrid Cloud with Choice, Consistency, Control and Compliance,” Dec. 10, 2014, 22 pages. |
Cisco Technology, Inc., “Cisco Expands Videoscape TV Platform Into the Cloud,” Jan. 6, 2014, Las Vegas, Nevada, Press Release, 3 pages. |
CSS Corp, “Enterprise Cloud Gateway (ECG)—Policy driven framework for managing multi-cloud environments,” original published on or about Feb. 11, 2012; 1 page; http://www.css-cloud.com/platform/enterprise-cloud-gateway.php. |
Fang K., “LISP MAC-EID-TO-RLOC Mapping (LISP based L2VPN),” Network Working Group, Internet Draft, CISCO Systems, Jan. 2012, 12 pages. |
Herry, William, “Keep It Simple, Stupid: OpenStack nova-scheduler and its algorithm”, May 12, 2012, IBM, 12 pages. |
Hewlett-Packard Company, “Virtual context management on network devices”, Research Disclosure, vol. 564, No. 60, Apr. 1, 2011, Mason Publications, Hampshire, GB, Apr. 1, 2011, 524. |
Juniper Networks, Inc., “Recreating Real Application Traffic in Junosphere Lab,” Solution Brief, Dec. 2011, 3 pages. |
Kenhui, “Musings on Cloud Computing and IT-as-a-Service: [Updated for Havana] Openstack Computer for VSphere Admins, Part 2: Nova-Scheduler and DRS”, Jun. 26, 2013, Cloud Architect Musings, 12 pages. |
Kolyshkin, Kirill, “Virtualization in Linux,” Sep. 1, 2006, XP055141648, 5 pages, https://web.archive.org/web/20070120205111/http://download.openvz.org/doc/openvz-intro.pdf. |
Lerach, S.R.O., “Golem,” http://www.lerach.cz/en/products/golem, accessed Jul. 22, 2015, 2 pages. |
Linthicum, David, “VM Import could be a game changer for hybrid clouds”, InfoWorld, Dec. 23, 2010, 4 pages. |
Naik, Vijay K., et al., “Harmony: A Desktop Grid for Delivering Enterprise Computations,” Grid Computing, 2003, Fourth International Workshop on Proceedings, Nov. 17, 2003, pp. 1-11. |
Nair, Srijith K. et al., “Towards Secure Cloud Bursting, Brokerage and Aggregation,” 2012, 8 pages, www.flexiant.com. |
Nielsen, “SimMetry Audience Measurement—Technology,” http://www.nielsen-admosphere.eu/products-and-services/simmetry-audience-measurement-technology/, accessed Jul. 22, 2015, 6 pages. |
Nielsen, “Television,” http://www.nielsen.com/us/en/solutions/measurement/television.html, accessed Jul. 22, 2015, 4 pages. |
Open Stack, “Filter Scheduler,” updated Dec. 17, 2017, 5 pages, accessed on Dec. 18, 2017, https://docs.openstack.org/nova/latest/user/filter-scheduler.html. |
Rabadan, J., et al., “Operational Aspects of Proxy-ARP/ND in EVPN Networks,” BESS Worksgroup Internet Draft, draft-snr-bess-evpn-proxy-arp-nd-02, Oct. 6, 2015, 22 pages. |
Saidi, Ali, et al., “Performance Validation of Network-Intensive Workloads on a Full-System Simulator,” Interaction between Operating System and Computer Architecture Workshop, (IOSCA 2005), Austin, Texas, Oct. 2005, 10 pages. |
Shunra, “Shunra for HP Software; Enabling Confidence in Application Performance Before Deployment,” 2010, 2 pages. |
Son, Jungmin, “Automatic decision system for efficient resource selection and allocation in inter-clouds,” Jun. 2013, 35 pages. |
Wikipedia, “Filter (software)”, Wikipedia, Feb. 8, 2014, 2 pages, https://en.wikipedia.org/w/index.php?title=Filter_%28software%29&oldid=594544359. |
Wikipedia; “Pipeline (Unix)”, Wikipedia, May 4, 2014, 4 pages, https://en.wikipedia.org/w/index.php?title=Pipeline2/028Unix%29&oldid=606980114. |
Number | Date | Country | |
---|---|---|---|
20180212896 A1 | Jul 2018 | US |