Abstract: Apparatuses, methods, systems, and program products are disclosed for file synchronization. An apparatus includes an origin tracking module that tracks data change information for each of at least one data change in an origin file stored on an origin device. The data change information includes a location of the data change in the origin file and a length of the data change. An apparatus includes a synchronization detecting module that detects a synchronization event associated with the origin file. An apparatus includes a synchronizing module that copies the data of the origin file for each of the at least one data change in the origin file at the tracked location and length to a target file stored on a target device.

Abstract: Apparatuses, methods, systems, and program products are disclosed for file synchronization. An apparatus includes an origin tracking module that tracks data change information for each of at least one data change in an origin file stored on an origin device. The data change information includes a location of the data change in the origin file and a length of the data change. An apparatus includes a synchronization detecting module that detects a synchronization event associated with the origin file. An apparatus includes a synchronizing module that copies the data of the origin file for each of the at least one data change in the origin file at the tracked location and length to a target file stored on a target device.

Abstract: Apparatuses, methods, systems, and program products are disclosed for workload management and distribution. A method includes parking a virtual instance of a workload in a repository. The workload may be executing in a first virtual environment that is configured with a first set of execution parameters prior to being parked. The method includes receiving a request to unpark the virtual instance of the workload from the repository to a second virtual environment. The method includes unparking the virtual instance of the workload at the second virtual environment. The second virtual environment may be configured with a second set of execution parameters that are different than the first set of execution parameters. The virtual instance of the workload may be unparked at the second virtual environment using the second set of execution parameters such that the unparked virtual instance of the workload retains its operating state from the first virtual environment.

Abstract: Apparatuses, methods, systems, and computer program products are disclosed for container synchronization. Host data associated with a first container on a host device is determined. Target data associated with a second container on a target device is determined. Differences between the host data associated with the first container on the host device and the target data associated with the second container on the target device are determined. Host data associated with the first container on the host device is synchronized with target data associated with the second container on the target device in response to determining differences between the host data and the target data such that the host data associated with the first container is identical to the target data associated with the second container.

Abstract: Apparatuses, methods, systems, and program products are disclosed for workload management and distribution. A method includes parking a virtual instance of a workload in a repository. The workload may be executing in a first virtual environment that is configured with a first set of execution parameters prior to being parked. The method includes receiving a request to unpark the virtual instance of the workload from the repository to a second virtual environment. The method includes unparking the virtual instance of the workload at the second virtual environment. The second virtual environment may be configured with a second set of execution parameters that are different than the first set of execution parameters. The virtual instance of the workload may be unparked at the second virtual environment using the second set of execution parameters such that the unparked virtual instance of the workload retains its operating state from the first virtual environment.

Abstract: Apparatuses, methods, systems, and computer program products are disclosed for container synchronization. Host data associated with a first container on a host device is determined. Target data associated with a second container on a target device is determined. Differences between the host data associated with the first container on the host device and the target data associated with the second container on the target device are determined. Host data associated with the first container on the host device is synchronized with target data associated with the second container on the target device in response to determining differences between the host data and the target data such that the host data associated with the first container is identical to the target data associated with the second container.

Abstract: Various methods, devices, and systems are described for cloud federation in a cloud computing network including bridging computing resources between an enterprise and a cloud or among multiple clouds. These techniques involve generating an image of the host system and decoupling it from its underlying computing resources so that it can be migrated across disparate computing resources in a seamless manner. In one embodiment, an enterprise workload can be bridged with cloud resources to receive software as a service. In other embodiments, bridging is performed across multiple public or private clouds, each potentially having disparate computing resources. In addition, users can access and use these cloud services through a web browser or other network interface anywhere in the cloud computing network as if the services were installed locally on their own computer.

Abstract: Various methods, devices, and systems are described for cloud federation in a cloud computing network including bridging computing resources between an enterprise and a cloud or among multiple clouds. These techniques involve generating an image of the host system and decoupling it from its underlying computing resources so that it can be migrated across disparate computing resources in a seamless manner. In one embodiment, an enterprise workload can be bridged with cloud resources to receive software as a service. In other embodiments, bridging is performed across multiple public or private clouds, each potentially having disparate computing resources. In addition, users can access and use these cloud services through a web browser or other network interface anywhere in the cloud computing network as if the services were installed locally on their own computer.

Abstract: A computer system that includes a plurality of servers, and a shared I/O subsystem coupled to each of the servers and to one or more I/O interfaces. The shared I/O subsystem services I/O requests made by two or more of the servers. Each I/O interface may couple to a network, appliance, or other device. The I/O requests serviced by the shared I/O subsystem may alternatively include software initiated or hardware initiated I/O requests. Different servers coupled to the shared I/O subsystem may use different operating systems, and each I/O interface may be used by two or more servers.

Abstract: A computer system that includes a plurality of servers, and a shared I/O subsystem coupled to each of the servers and to one or more I/O interfaces. The shared I/O subsystem services I/O requests made by two or more of the servers. Each I/O interface may couple to a network, appliance, or other device. The I/O requests serviced by the shared I/O subsystem may alternatively include software initiated or hardware initiated I/O requests. Different servers coupled to the shared I/O subsystem may use different operating systems, and each I/O interface may be used by two or more servers.

Abstract: A computer system that includes a plurality of servers, and a shared I/O subsystem coupled to each of the servers and to one or more I/O interfaces. The shared I/O subsystem services I/O requests made by two or more of the servers. Each I/O interface may couple to a network, appliance, or other device. The I/O requests serviced by the shared I/O subsystem may alternatively include software initiated or hardware initiated I/O requests. Different servers coupled to the shared I/O subsystem may use different operating systems, and each I/O interface may be used by two or more servers.

Abstract: A shared I/O subsystem for a plurality of computer systems. The shared I/O subsystem includes a plurality of physical I/O interfaces and a plurality of virtual I/O interfaces where each of the computer systems is communicatively coupled to one or more of the virtual I/O interfaces. The shared I/O subsystem also includes a forwarding function having a forwarding table that logically arranges the shared I/O subsystem into one or more logical LAN switches. Each of the logical LAN switches communicatively couples one or more of the virtual I/O interfaces to at least one of the physical I/O interfaces. For each of the logical LAN switches, the forwarding function receives a data packet from any one from the group of the physical I/O interfaces and the virtual I/O interfaces, and directs the data packet to at least one from the group of the physical I/O interfaces and the virtual I/O interfaces.

Abstract: A shared I/O subsystem for a plurality of computer systems where a plurality of virtual I/O interfaces are communicatively coupled to the computer systems. Each of the computer systems includes a virtual adapter that communicates with one of the virtual I/O interfaces. The shared I/O subsystem also includes a plurality of I/O interfaces and a forwarding function. The forwarding function includes a plurality of forwarding table entries that logically arrange the shared I/O subsystem into one or more logical switches. Each of the logical switches communicatively couples one or more of the virtual I/O interfaces to one of the I/O interfaces. A logical switch receives a first I/O packet from one of the virtual I/O interfaces and directs the first I/O packet to at least one of the I/O interface and one or more of other ones of the virtual I/O interfaces. A logical switch also receives a second I/O packet from the I/O interface and directs the second I/O packet to one or more of the virtual I/O interfaces.

Abstract: A shared I/O subsystem that couples a plurality of computer systems to at least one shared I/O interface. The shared I/O subsystem includes a plurality of virtual I/O interfaces that are communicatively coupled to the computer systems. Each of the computer systems includes a virtual adapter that communicates with one of the virtual I/O interfaces. The shared I/O subsystem further includes a forwarding function having a forwarding table. The forwarding table includes a plurality of entries corresponding to each of the virtual I/O interfaces. The forwarding function receives a first I/O packet from one of the virtual I/O interfaces and uses the forwarding table to direct the first I/O packet to at least one of a physical adapter associated with the at least one shared I/O interface and one or more of other ones of the virtual I/O interfaces.

Abstract: A shared I/O subsystem that includes a plurality of I/O interfaces for coupling a plurality of computer systems where each of I/O interfaces communicatively couples one of the computer systems to the shared I/O subsystem.

Abstract: A shared I/O subsystem that couples a plurality of computer systems to at least one shared I/O interface. The shared I/O subsystem includes a plurality of virtual I/O interfaces that are communicatively coupled to the computer systems. Each of the computer systems includes a virtual adapter that communicates with one of the virtual I/O interfaces. The shared I/O subsystem further includes a forwarding function having a forwarding table. The forwarding table includes a plurality of entries corresponding to each of the virtual I/O interfaces. The forwarding function receives a first I/O packet from one of the virtual I/O interfaces and uses the forwarding table to direct the first I/O packet to at least one of a physical adapter associated with the at least one shared I/O interface and one or more of other ones of the virtual I/O interfaces.

Abstract: A shared I/O subsystem for a plurality of computer systems. The shared I/O subsystem includes a plurality of physical I/O interfaces and a plurality of virtual I/O interfaces where each of the computer systems is communicatively coupled to one or more of the virtual I/O interfaces. The shared I/O subsystem also includes a forwarding function having a forwarding table that logically arranges the shared I/O subsystem into one or more logical LAN switches. Each of the logical LAN switches communicatively couples one or more of the virtual I/O interfaces to at least one of the physical I/O interfaces. For each of the logical LAN switches, the forwarding function receives a data packet from any one from the group of the physical I/O interfaces and the virtual I/O interfaces, and directs the data packet to at least one from the group of the physical I/O interfaces and the virtual I/O interfaces.

Abstract: A shared I/O subsystem that includes a plurality of I/O interfaces for coupling a plurality of computer systems where each of I/O interfaces communicatively couples one of the computer systems to the shared I/O subsystem.

Abstract: A computer system that includes a plurality of servers, and a shared I/O subsystem coupled to each of the servers and to one or more I/O interfaces. The shared I/O subsystem services I/O requests made by two or more of the servers. Each I/O interface may couple to a network, appliance, or other device. The I/O requests serviced by the shared I/O subsystem may alternatively include software initiated or hardware initiated I/O requests. Different servers coupled to the shared I/O subsystem may use different operating systems, and each I/O interface may be used by two or more servers.

Abstract: A shared I/O subsystem for a plurality of computer systems where a plurality of virtual I/O interfaces are communicatively coupled to the computer systems. Each of the computer systems includes a virtual adapter that communicates with one of the virtual I/O interfaces. The shared I/O subsystem also includes a plurality of I/O interfaces and a forwarding function. The forwarding function includes a plurality of forwarding table entries that logically arrange the shared I/O subsystem into one or more logical switches. Each of the logical switches communicatively couples one or more of the virtual I/O interfaces to one of the I/O interfaces. A logical switch receives a first I/O packet from one of the virtual I/O interfaces and directs the first I/O packet to at least one of the I/O interface and one or more of other ones of the virtual I/O interfaces. A logical switch also receives a second I/O packet from the I/O interface and directs the second I/O packet to one or more of the virtual I/O interfaces.