System and method for process migration in a content centric network

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 15/339,116, entitled “SYSTEM AND METHOD FOR PROCESS MIGRATION IN A CONTENT CENTRIC NETWORK,” filed Oct. 31, 2016, the disclosure of which is hereby incorporated herein by reference in its entirety. <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0002">The subject matter of this application is related to the subject matter in the following applications:</li><li id="ul0002-0002" num="0003">U.S. patent application Ser. No. 13/847,814, entitled “ORDERED=ELEMENT NAMING FOR NAME-BASED PACKET FORWARDING,” by inventor Ignacio Solis, filed 20 Mar. 2013 (hereinafter “U.S. patent application Ser. No. 13/847,814”);</li><li id="ul0002-0003" num="0004">U.S. patent application Ser. No. 13/857,814, entitled “ORDERED-ELEMENT NAMING FOR NAME-BASED PACKET FORWARDING,” by inventor Ignacio Solis, filed Mar. 20, 2013 (hereinafter “U.S. patent application Ser. No. 13/847,814”);</li><li id="ul0002-0004" num="0005">U.S. patent application Ser. No. 12/338,175, entitled “CONTROLLING THE SPREAD OF INTERESTS AND CONTENT IN A CONTENT CENTRIC NETWORK,” by inventors Van L. Jacobson and Diana K. Smetters, filed Dec. 18, 2008 (hereinafter “U.S. patent application Ser. No. 12/338,175”); and</li><li id="ul0002-0005" num="0006">U.S. patent application Ser. No. 14/337,026, entitled “SYSTEM FOR DISTRIBUTING NAMELESS OBJECTS USING SELF-CERTIFYING NAMES,” by inventor Marc E. Mosko, filed Jul. 21, 2014 (hereinafter “U.S. patent application Ser. No. 14/337,026”); <br /> the disclosures of which are herein incorporated by reference in their entireties. </li></ul></li></ul>

BACKGROUND

Field

This disclosure is generally related to distribution of digital content. More specifically, this disclosure is related to a method and system for process migration in a content centric network based on a naming ontology and creation of checkpoint versions.

Related Art

The proliferation of the Internet and e-commerce continues to create a vast amount of digital content. Content centric network (CCN) architectures have been designed to facilitate accessing and processing such digital content. A CCN includes entities, or nodes, such as network clients, forwarders (e.g., routers), and content producers, which communicate with each other by sending interest packets for various content items and receiving content object packets in return. CCN interests and content objects are identified by their unique names, which are typically hierarchically structured variable length identifiers (HSVLI). An HSVLI can include contiguous name components ordered from a most general level to a most specific level.

A CCN data packet (such as an interest or content object) is routed based on its name. An interest can leave state in a pending interest table (PIT) as it travels through the network. A responsive content object can be cached by any intermediate node in its content store (CS). This caching creates efficient access to frequently requested data, because a subsequent interest for the same content can be satisfied by an intermediate node, rather than by an end host such as a content producer.

Process migration involves moving the running state of a process from one physical system to another, such as moving the state of a virtual machine from one system to another. While a CCN brings many desired features to a network, some issues remain unsolved in providing a system that facilitates process migration over a content centric network.

One embodiment provide s a system that facilitates a migration of a data model from a source de vice to a target device in a CCN. The system generates, by a target device, a first interest for a first manifest which represents a version of the data model, wherein a manifest indicates a phase of the migration and a plurality of machine resources with corresponding names. In response to receiving the first manifest the system transmits a first plurality of interests for the resources indicated in the first manifest based on a name for a respective resource indicated in the first manifest The system receives a second manifest, wherein the migration phase indicated in the second manifest is a stop-and-copy phase. The system transmits a second plurality of interests for the resources indicated in the second manifest based on a name for a respective resource indicated in the second manifest. The system starts the data model on the system based on content objects retrieved in response to the first and second plurality of interests, thereby facilitating the migration of the data model over a content centric network from a source device to the system. The system can be a target device.

In some embodiments, generating the first interest, receiving the first manifest, and transmitting the first plurality of interests are in response to determining a pre-copy method for the migration of the data model. Receiving the second manifest is in response to retrieving content indicated in the first manifest and one or more checkpoint manifests.

In some embodiments, a respective checkpoint manifest indicates a unique version identifier for the data model, the migration phase indicated in the first manifest and a respective checkpoint manifest is a push phase, and the second manifest represents a hot version of the data model.

In some embodiments, the data model comprises an architecture for a virtual machine, and the resources are resources of the virtual machine.

In some embodiments, a name is a hierarchically structured variable length identifier that includes contiguous name components ordered from a most general level to a most specific level. The name for a respective resource indicated in a manifest is a hash-based name which includes a hash value for data representing the respective resource. The hash-based name for the respective resource allows the system to obtain the respective resource from any device that stores a content object with a hash value that matches the hash value included in the hash-based name, thereby facilitating de-duplication of data in the data model.

In some embodiments, receiving the second manifest is further in response to the source device determining that a predetermined marginal threshold is reached and freezing the data model on the source device.

In some embodiments, the system receives a third manifest which represents a final version of the data model, wherein the migration phase indicated in the third manifest is a pull phase. The system transmits a third plurality of interests for the resources indicated in the third manifest based on a name for a respective resource indicated in the third manifest, wherein transmitting the third plurality of interests is based on a policy of the system.

In some embodiments, the system transmits a first interest which is a close checkpoint message with a name that indicates a respective manifest, in response to receiving an acknowledgment of the first interest, the system transmits a second interest which is a confirm checkpoint close message with a name that indicates the respective manifest. The system receives an acknowledgment of the second interest, wherein the source device releases the resources indicated in the respective manifest.

Another embodiment provides a system for facilitating a migration of a data model indicating resources. The system generates a first manifest which represents a version of the data model, wherein a manifest indicates a phase of the migration and a plurality of resources with corresponding names. In response to receiving a first plurality of interests for the resources indicated in the first manifest based on a name for a respective resource indicated in the first manifest, the system transmits a first plurality of corresponding content objects. In response to reaching a predetermined threshold, the system: freezes the data model on the system; and generates a second manifest, wherein the migration phase indicated in the second manifest is a stop-and-copy phase. In response to receiving a second plurality of interests for the resources indicated in the second manifest based on a name for a respective resource indicated in the second manifest, the system transmits a second plurality of corresponding content objects, thereby facilitating the migration of the data model over a content centric network from the system to a target device. The system can be a source device.

In some embodiments, generating the first manifest, receiving the first plurality of interests, and transmitting the first plurality of content objects are in response to determining a pre-copy method for the migration of the data model, wherein the migration phase indicated in the first manifest is a push phase.

In some embodiments, the system generates one or more checkpoint manifests. A respective checkpoint manifest indicates a unique version identifier for the data model, the migration phase indicated in the respective checkpoint manifest is a push phase, and the second manifest represents a hot version of the data model.

In some embodiments, the system generates a third manifest which represents a final version of the data model, wherein the migration phase of the third manifest indicates a pull phase. In response to receiving a third plurality of interests for the resources indicated in the third manifest based on a name for a respective resource indicated in the third manifest, the systems transmits a third plurality of corresponding content objects.

In some embodiments, in response to receiving a first interest which is a close checkpoint message with a name that indicates a respective manifest, the system transmits an acknowledgment of the first interest. In response to receiving a second interest which is a confirm checkpoint close message with a name that indicates the respective manifest, the system: transmits an acknowledgement of the second interest; and releases the resources indicated in the respective manifest.

BRIEF DESCRIPTION OF THE FIGURES

<figref idref="DRAWINGS">FIG. 1</figref> illustrates an exemplary network which facilitates process migration in a content centric network, in accordance with an embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 2A</figref> illustrates an exemplary format for a checkpoint manifest, in accordance with an embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 2B</figref> illustrates an exemplary push phase checkpoint manifest, in accordance with an embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 2C</figref> illustrates an exemplary stop-and-copy phase checkpoint manifest, in accordance with an embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 2D</figref> illustrates an exemplary pull phases checkpoint manifest, in accordance with an embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 3A</figref> illustrates an exemplary communication which facilitates process migration in a content centric network, in accordance with an embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 3B</figref> illustrates an exemplary communication which facilitates process migration in a content centric network, in accordance with an embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 4A</figref> presents a flow chart illustrating a method by a target device for facilitating process migration in a content centric network, in accordance with an embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 4B</figref> presents a flow chart illustrating a method by a target device for facilitating process migration in a content centric network, in accordance with an embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 5</figref> presents a flow chart illustrating a method by a target device for closing a checkpoint during process migration in a content centric network, in accordance with an embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 6A</figref> presents a flow chart illustrating a method by a source device for facilitating process migration in a content centric network, in accordance with an embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 6B</figref> presents a flow chart illustrating a method by a source device for facilitating process migration in a content centric network, in accordance with an embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 7</figref> illustrates an exemplary computer system that facilitates process migration in a content centric network, in accordance with an embodiment of the present invention.

In the figures, like reference numerals refer to the same figure elements.

DETAILED DESCRIPTION

The following description is presented to enable any person skilled in the rut to make and use the embodiments, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present disclosure. Thus, the present invention is not limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.

Overview

Embodiments of the present invention provide a system which facilitates process migration in a content centric network based on a naming ontology and named checkpoint versions. A CCN data packet (such as an interest or content object) is routed based on its name. An interest can leave state in a pending interest table (PIT) as it travels through the network. A responsive content object can be cached by any intermediate node in its content store (CS). This caching creates efficient access to frequently requested data, because a subsequent interest for the same content can be satisfied by an intermediate node, rather than by an end host such as a content producer.

Process migration can include moving the state of a virtual machine from one physical system (i.e., a source device) to another physical system (i.e., a target device). One technique for progress migration is the pre-copy method, which involves three phases: the push phase; the stop-and-copy phase; and the pull phase, as described in Clark, et al., “Live migration of virtual machines,” Proceedings of the 2^ndConference on Symposium on Networked Systems Designs &amp; Implementation, Vol. 2, pages 273-286, USENIX Association, 2005. In the push phase, slowly changing state is moved over the network, possibly in several rounds. In the stop-and-copy phase, the source virtual machine freezes, and the hot state is moved over the network. In the pull phase, any remaining data not copied over is moved over the network (e.g., the target can “lazily” pull the data on-demand or at its desired pace).

Another technique for process migration is the post-copy method, whereby the source first freezes the virtual machine and transfers the CPU state (similar to the stop-and-copy phase of the pre-copy method), and then transfers the memory (similar to both the push and pull phases of the pre-copy method), as described in Hines, et al., “Post-copy based live virtual machine migration using adaptive pre-paging and dynamic self-ballooning,” Proceedings of the 2009 ACM SIGPLAN/SIGOPS International Conference on Virtual Execution Environments, pages 51-60, ACM, 2009. Other process migration techniques are possible, including the Remus hot migration, which uses consistent and frequent checkpoints for hot-spare virtual machine migration, as described in Cully, et al., “Remus: High availability via asynchronous virtual machine replication,” Proceedings of the 5th USENIX Symposium on Networked Systems Design and Implementation, pages 161-174, San Francisco, 2008.

Embodiments of the present invention provide a system based on the pre-copy process migration technique which facilitates process migration over a CCN by mapping machine elements to CCN names. The system uses hash-based formatted names and manifests via CCN interests and content objects to identify, represent, and move the machine resources. Hash-based names (i.e., nameless content objects) are described in U.S. patent application Ser. No. 14/337,026. The system includes strong checkpointing and data de-duplication. The system creates named checkpoint manifests in the three phases of the pre-copy technique, where a named checkpoint corresponds to a specific version of a machine model. Exemplary checkpoint manifests are described below in relation to <figref idref="DRAWINGS">FIGS. 2A-2D</figref>, and an exemplary communication that facilitates process migration in a CCN based on formatted names is described below in relation to <figref idref="DRAWINGS">FIGS. 3A and 3B</figref>.

Thus, the present system provides improvements to the distribution of digital content, where the improvements are fundamentally technological. Embodiments of the present invention provide a technological solution (e.g., facilitating process migration over a CCN based on a pre-copy method using interest/content object exchanges and manifests) to the technological problem of efficiently migrating a process, such as a data model or a virtual machine, over a CCN.

In CCN, each piece of content is individually named, and each piece of data is bound to a unique name that distinguishes the data from any other piece of data, such as other versions of the same data or data from other sources. This unique name allows a network device to request the data by disseminating a request or an interest that indicates the unique name, and can obtain the data independent from the data's storage location, network location, application, and means of transportation. The following terms are used to describe the CCN architecture.

Content Object (or “Content Object”):

A single piece of named data, which is bound to a unique name. Content Objects are “persistent,” which means that a Content Object can move around within a computing device, or across different computing devices, but does not change. If any component of the Content Object changes the entity that made the change creates a new Content Object that includes the updated content and binds the new Content Object to a new unique name.

Unique Names:

A name in a CCN is typically location independent and uniquely identifies a Content Object. A data-forwarding device can use the name or name prefix to forward a packet toward a network node that generates or stores the Content Object, regardless of a network address or physical location for the Content Object. In some embodiments, the name may be a hierarchically structured variable-length identifier (HSVLI). The HSVLI can be divided into several hierarchical components, which can be structured in various ways. For example, the individual name components pare, home, ccn, and test.txt can be structured in a left-oriented prefix-major fashion to form the name “/pare/home/ccn/test.txt.” Thus, the name “/pare/home/ccn” can be a “parent” or “prefix” of “/pare/home/ccn/test.txt.” Additional components can be used to distinguish between different versions of the content item, such as a collaborative document. The HSVLI can also include contiguous name components ordered from a most general level to a most specific level.

In some embodiments, the name can include an identifier, such as a hash value that is derived from the Content Object's data (e.g., a checksum value) and/or from elements of the Content Object's name. A description of a hash-based name is described in U.S. patent application Ser. No. 13/847,814, which is herein incorporated by reference. A name can also be a flat label. Hereinafter, “name” is used to refer to any name for a piece of data in a name-data network, such as a hierarchical name or name prefix, a flat name, a fixed-length name, an arbitrary-length name, or a label (e.g., a Multiprotocol Label Switching (MPS) label).

Interest (or “Interest”):

A packet that indicates a request for a piece of data, and includes a name (or a name prefix) for the piece of data. A data consumer can disseminate a request or Interest across an information-centric network, which CCN/NDN routers can propagate toward a storage device (e.g., a cache server) or a data producer that can provide the requested data to satisfy the request or Interest.

The methods disclosed herein are not limited to CCN networks and are applicable to other architectures as well. A description of a CCN architecture is described in U.S. patent application Ser. No. 12/338,175, which is herein incorporated by reference.

A Classic Machine Model and Exemplary Formatted Names

A classic machine model includes a central processing unit (CPU) with a register file, random access memory (RAM), permanent storage (e.g., hard disks), and accessories (e.g., network interface cards or a graphics system), as well as a configuration file describing the system architecture. The machine model (or any data model) and its constituent resources can be mapped to names and corresponding content objects. The configuration file can specify the hardware parameters, including the number of CPUs (including identifiers, e.g., where “cpu_n,” is the nth CPU) the amount of RAM and the page size (e.g., 1 GB with 4 KB pages), the number of hard disks (including identifiers, e.g., “hdA” and “hdB”), and network interfaces (e.g., “en( )”). A hard disk may be represented in the Virtual Hard Disk (“vhd”) format and includes its own configuration file in addition to data blocks (e.g., 512 bytes or 4 KB, per the configuration file). A standard disk model, such as vhd, uses three control structures in addition to the data blocks: a dynamic disk header a block allocation table (BAT); and a disk footer. The CCN naming ontology maps each machine element or resource to a CCN name. Below are exemplary names for resources of a virtual machine with a routable prefix or identifier of “/vm-name,” n CPUs, x pages of RAM, two hard disks (hdA and hdB, where at least hdA is of the vhd format) each with y blocks, and a network interface of en( ): <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0054">/vm-name/config Format (1)</li><li id="ul0003-0002" num="0055">/vm-name/cpu/\{0 . . . cpu_n\}/regfile Format (2)</li><li id="ul0003-0003" num="0056">/vm-name/cpu/\{0 . . . cpu_n\}/tlb Format (3)</li><li id="ul0003-0004" num="0057">/vm-name/ram/page/{O . . . ram_x} Format (4)</li><li id="ul0003-0005" num="0058">/vm-name/disk/hda/config Format (5)</li><li id="ul0003-0006" num="0059">/vm-name/disk/hda/vhd/header Format (6)</li><li id="ul0003-0007" num="0060">/vm-name/disk/hda/vhd/bat Format (7)</li><li id="ul0003-0008" num="0061">/vm-name/disk/hda/vhd/footer Format (8)</li><li id="ul0003-0009" num="0062">/vm-name/disk/hda/block/{0 . . . hda_y} Format (9)</li><li id="ul0003-0010" num="0063">/vm-name/disk/hdb/config Format (10)</li><li id="ul0003-0011" num="0064">/vm-name/disk/hdb/block/{0 . . . hdb_y} Format (11)</li><li id="ul0003-0012" num="0065">/vm-name/net/enO Format (12) <br /> Process Migration Using Pre-Copy Technique and Hash-Based Names </li></ul>

The following assumptions may be made: A supervisory process determines the need to begin a migration process, i.e., to move a process from a source or source device to a target or target device. The supervisory process can instantiate a process duplicator agent on each of the source and the target, such as in the virtual machine hypervisor. Furthermore, the agents have a reliable transfer method, and the source and the target can agree on a window size or acknowledgment mechanism so that the source can release resources which have been correctly transferred to the target. Finally, the source and the target have a reliable close mechanism such as the four-way handshake described below in relation to <figref idref="DRAWINGS">FIG. 5</figref>.

The system can facilitate process migration over a CCN based on the three phases of the pre-copy technique and the specific naming ontology. In the push phase, the source creates versioned checkpoint manifests, which are pulled by the target. The target then retrieves the data represented in the checkpoint manifest via the naming ontology. The source and the target iterate through the push phase until the source determines a marginal benefit. In the stop-and-copy phase, the source freezes the data model (e.g., the virtual machine), creates a next checkpoint manifest of critical resources, and transfers the next checkpoint manifest to the target. Finally, in the pull phase, the source creates a final checkpoint manifest, which the target can lazily pull as needed. This three-phase process, along with hash-based formatted names following the naming ontology, is described below in the exemplary communications of <figref idref="DRAWINGS">FIGS. 3A and 3B</figref>.

The naming ontology follows the formatted names described above for the exemplary machine model. For example in the push phase, a checkpoint manifest can have a name such as “/vm-name/checkpoint/ver=j/manifest” while a resource represented in the checkpoint manifest can be retrieving using a hash-based name. For example, an interest for the resource can have a name of “/vm-name/checkpoint/ver=j/resource=ram/feature=page_1/hash=hash_p1” or “/vm-name/chkpt/ver=0/ram/page_1/hash_p1.” Exemplary checkpoint manifests are described below in relation to <figref idref="DRAWINGS">FIGS. 2A-2D</figref>.

Exemplary Network

<figref idref="DRAWINGS">FIG. 1</figref> illustrates an exemplary network <b>100</b> which facilitates process migration in a content centric network, in accordance with an embodiment of the present invention. Network <b>100</b> can include a consumer or content requesting device <b>116</b>, producers or content producing devices <b>118</b> and <b>120</b>, and a router or other forwarding device at nodes <b>102</b>, <b>104</b>, <b>106</b>, <b>108</b>, <b>110</b>, <b>112</b> and <b>114</b>. A node can be a computer system, an end-point representing users, and/or a device that can generate interests or originate content. A node can also be an edge router (e.g., CCN nodes <b>102</b>, <b>104</b>, <b>110</b>, and <b>114</b>) or a core router (e.g., intermediate CCN routers <b>106</b>, <b>108</b>, and <b>112</b>). Network <b>100</b> can be a content centric network. Device <b>118</b> can be a source device, and device <b>158</b> can be a target device. Source device <b>118</b> can run a virtual machine <b>120</b>, which can include the following components or resources: a configuration file <b>122</b>; a CPU <b>124</b>; a RAM <b>126</b>; a hard disk A <b>128</b>; a hard disk B <b>130</b>; and a network interface <b>132</b>. Hard disk A <b>128</b> can be of a vhd format, and can include a configuration file <b>140</b>, a vhd <b>142</b>, and a block <b>144</b>. While only one block <b>144</b> is depicted in <figref idref="DRAWINGS">FIG. 1</figref>, hard disk A <b>128</b> can include multiple blocks. Vhd <b>144</b> can include a header <b>150</b>, a BAT <b>152</b>, and a footer <b>154</b>. Target device <b>158</b> can run a virtual machine <b>160</b> with similar resources (not shown) as virtual machine <b>120</b> running on source device <b>118</b>. Source device <b>118</b> and target device <b>158</b> can participate in a migration process, which involves moving the state of virtual machine <b>120</b> from source device <b>118</b> to (virtual machine <b>160</b>) on target device <b>158</b>.

During operation, target device <b>158</b> can communicate with source device <b>118</b> by sending an interest <b>170</b> which travels through network <b>100</b> via nodes <b>114</b>, <b>112</b>, and <b>110</b> before reaching source device <b>118</b>. Source device <b>118</b> can satisfy interest <b>170</b> and return a responsive content object <b>172</b>. For example, interest <b>170</b> can be an interest for a checkpoint manifest which represents a version of the data model for virtual machine <b>120</b>, and content object <b>172</b> can be the responsive checkpoint manifest. A name for interest <b>170</b> (and responsive content object <b>172</b> can be “/vm-name/checkpoint/ver=O/manifest.” The manifest can indicate the phase of the process migration (e.g., push, stop-and-copy, or pull) as well as the resources with corresponding names, including hash-based names.

Upon receiving the manifest target device <b>158</b> can generate interests for the indicated resources using the corresponding hash-based names. Target device <b>158</b> can retrieve the corresponding content objects from source device <b>118</b> or from any intermediate node that may have a cached copy of the corresponding content objects. For example, node <b>112</b> may store a cached copy of a content object with a name of “/vm-name/checkpoint/ver=0/ram/page_1/hash_p1,” that is, a content object whose hash is equal to “hash_p1” as included in the name of the respective interest. Thus, intermediate node <b>112</b> can return a responsive content object <b>172</b> to target device <b>158</b>. The caching features of a CCN also result in de-duplication, which is described in detail below. A detailed description of the push, stop-and-copy, and pull phases in a process migration over a CCN is described below in relation to <figref idref="DRAWINGS">FIGS. 3A and 3B</figref>.

Exemplary Versioned Checkpoint Manifests

<figref idref="DRAWINGS">FIG. 2A</figref> illustrates an exemplary format for a checkpoint manifest <b>200</b>, in accordance with an embodiment of the present invention Checkpoint manifest <b>200</b> can indicate a phase <b>202</b>, a configuration <b>204</b>, and a list of resources <b>206</b>, where a resource can include one or more tuples comprised of a feature <b>208</b> and a hash <b>210</b>.

<figref idref="DRAWINGS">FIG. 2B</figref> illustrates an exemplary push phase checkpoint manifest <b>210</b>, in accordance with an embodiment of the present invention. Manifest <b>210</b> can indicate a phase <b>212</b> with a value of “push,” a configuration file <b>214</b> with a value of “&lt;data, hash, or link&gt;,” a CPU <b>216</b> resource with a value of “cpu_1,” a RAM <b>218</b> resource with a value of “ram,” a hard disk <b>220</b> resource with a value of “hdA,” and a hard disk <b>222</b> resource with a value of “hdB.” CPU <b>212</b> can include the following {feature, hash} tuples: {regfile, hash_regfile}; and {tlb, hash_tlb}. RAM <b>218</b> can indicate the following {feature, hash} tuples: {page_0, hash_p0}; (page_1, hash_p1); and (page_2, hash_p2}. Hard disk <b>220</b> can indicate the following {feature, hash} tuples: {config_A, hash_configA}; {vhd/header, hash_vhdr), {vhd/bat, hash_vbat); {vhd/footer, hash_vftr); {block_0, hash_ab0}; {block_1, hash_ab1}; and {block_2, hash_ab2}. Hard disk <b>222</b> can indicate the following {feature, hash} tuples: {config_B, hash_configB}; {block_0, hash_bb0}; {block_1, hash_bb1}; and {block_2, hash_bb2}.

<figref idref="DRAWINGS">FIG. 2C</figref> illustrates an exemplary stop-and-copy phase checkpoint manifest <b>230</b>, in accordance with an embodiment of the present invention. Manifest <b>230</b> can indicate a phase <b>232</b> with a value of “stop-and-copy,” a configuration file <b>234</b> with a value of “&lt;data, hash, or link&gt;,” a CPU <b>236</b> resource with a value of “cpu_1,” and a RAM <b>238</b> resource with a value of “ram.” CPU <b>236</b> can indicate the following {feature, hash} tuples: {reg file, hash_regfile}; and {tlb, hash_tlb}. CPU <b>236</b> can also indicate other essential CPU state in stop-and-copy checkpoint manifest <b>230</b>. RAM <b>238</b> can indicate the following {feature, hash} tuples: {page_20, hash_p20}; {page_21, hash_p21}; {page_22, hash_p22}; {page_54, hash_p54}; {page_55, hash_p55}; and {page_56, hash_p56}. RAM <b>238</b> can also indicate other high turnover pages in stop-and-copy manifest <b>230</b>.

<figref idref="DRAWINGS">FIG. 2D</figref> illustrate s an exemplary pull phase checkpoint manifest <b>250</b>, in accordance with an embodiment of the present invention. Manifest <b>250</b> can indicate a phase <b>252</b> with a value of “pull,” a RAM <b>254</b> resource with a value of “ram,” a hard disk <b>256</b> resource with a value of “bdA,” and a hard disk <b>258</b> resource with a value of “hdB.” RAM <b>254</b> can indicate the following {feature, hash} tuples: {page_4, hash_p4); and {page_8, hash_p8). Hard disk <b>256</b> can indicate the following {feature, hash} tuples: {block_88, hash_ab88}; {block_98, hash_ab98}; and {block_99, hash_ab99}. Hard disk <b>258</b> can indicate the following {feature, hash} tuples: {block_49, hash_bb49}; and {block_54, hash_bb54}.

Each of checkpoint manifest <b>200</b>, push phase checkpoint manifest <b>210</b>, stop-and-copy phase manifest <b>230</b>, and pull phase checkpoint manifest <b>250</b> can also include a name and a version field (not shown). Each resource indicated in a manifest can be retrieved by generating an interest with a name in the format of, e.g., Formats (1)-(12), where a last name component is the corresponding hash value for the resource or the specific feature of the resource. A responsive content object with the same name as the interest is thus retrieved by (and transferred to) the target device. For example, an interest with a name of “/vm-name/checkpoint/ver=15/ram/page_1/hash_p1” will return a content object with the same name. Chunk numbers may also be used when a content object representing a resource is larger in sire than a single content object. In this case, the interest name can be, e.g., “/vm-name/checkpoint/ver=15/chunk=k/ram/page_1/hash_p1”

Exemplary Communication Facilitating Process Migration Over a CCN

<figref idref="DRAWINGS">FIG. 3A</figref> illustrates an exemplary communication <b>300</b> which facilitates process migration in a content centric network, in accordance with an embodiment of the present invention. Communication <b>300</b> includes a source or source device <b>302</b> and a target or target device <b>304</b>, which can communicate over a network such as a CCN. A supervisory process can determine the need to migrate a data model (such as a process like a virtual machine model) from source <b>302</b> to target <b>304</b>. Target <b>304</b> and source <b>302</b> can participate in a push phase <b>306</b>, a stop-and-copy phase <b>308</b>, and a pull phase <b>310</b> (in <figref idref="DRAWINGS">FIG. 3B</figref>).

Target <b>304</b> can generate an interest <b>312</b> with a name of “/vm-name/chkpt/ver=0/manifest,” which represents a version of the data model. In some embodiments, version 0 indicates an initial image of the data model. Source <b>302</b> can generate and return a responsive content object <b>314</b> with the same name as the interest name. Content object <b>314</b> can be, e.g., push phase checkpoint manifest <b>210</b> of <figref idref="DRAWINGS">FIG. 2B</figref>.

Target <b>304</b> can retrieve the checkpoint manifest (function <b>316</b>), which involves transmitting a plurality of interests for the resources indicated in the checkpoint manifest. Each interest has a name which indicates the resource and can include a specific feature and corresponding hash value. For example, target <b>304</b> can generate an interest <b>318</b>.<b>1</b> with a name of “/vm-name/chkpt/ver=0/disk/hdA/block_0/hash_ab0” and receive a responsive content object <b>320</b>.<b>1</b> with the same name and which includes as its payload the data corresponding to the specific resource.

Upon retrieving all the content objects indicated in manifest <b>314</b>, target <b>304</b> can close the checkpoint (function <b>322</b>), which involves a four-way handshake. Target <b>304</b> can send an interest <b>324</b> with a name of “/vm-name/checkpt/ver=0/close” and receive from source <b>302</b> a responsive ACK content object <b>326</b> with the same name. The ACK can be indicated in a payload of content object <b>326</b> or in another field. Target <b>304</b> can then send an interest <b>328</b> with a name of “/vm-nan1e/chkpt/ver=0/confirm_close” and receive from source <b>302</b> a responsive ACK content object <b>330</b> with the same name. Interest <b>324</b> can be a close checkpoint message, and interest <b>328</b> can be a confirm checkpoint close message. Source <b>302</b> can release the resources (function <b>332</b>) associated with the respective manifest (i.e., version 0 of the checkpoint manifest). Target <b>304</b> and source <b>302</b> can iterate through push phase <b>306</b> until source <b>302</b> determines that a predetermined marginal threshold is reached (function <b>333</b>) (i.e., transferring a push checkpoint manifest only results in a marginal benefit).

Upon making this determination, source <b>302</b> can freeze the data model on source <b>302</b> (function <b>334</b>) and create a stop-and-copy (“stp”) checkpoint manifest (function <b>336</b>). Source <b>302</b> can send a content object <b>338</b> which is an stp checkpoint manifest with a name of, e.g., “/vm-name/chkpt/ver=15/manifest.” In some embodiments, source <b>302</b> sends content object <b>338</b> in response to an interest (from target <b>304</b>) with the same name as the content object name. Content object <b>314</b> can be, e.g., stop-and-copy phase check point manifest <b>230</b> of <figref idref="DRAWINGS">FIG. 2C</figref>.

Target <b>304</b> can retrieve the stp checkpoint manifest (function <b>340</b>), which involves transmitting a plurality of interests for the resources indicated in the stp checkpoint manifest. Each interest has a name which indicates the resource and can include a specific feature and corresponding hash value. For example, target <b>304</b> can generate an interest <b>342</b>.<b>1</b> with a name of “/vm-name/chkpt/ver=15/ram/page_20/hash_p20” and receive a responsive content object <b>344</b>.<b>1</b> with the same name and which includes as its payload the data corresponding to the specific resource.

Upon retrieving all the content objects indicated in manifest <b>338</b>, target <b>304</b> can start the data model on target <b>304</b> (function <b>346</b>) and close the checkpoint (function <b>348</b>), which involves the four-way handshake described above and applied to interest <b>350</b>, content object <b>352</b>, interest <b>354</b>, and content object <b>356</b>. Source <b>302</b> can release the resources (function <b>338</b>) associated with the respective manifest (i.e., version 15 of the checkpoint manifest, or the stp checkpoint manifest).

<figref idref="DRAWINGS">FIG. 3B</figref> illustrates an exemplary communication <b>360</b> which facilitates process migration in a content centric network, in accordance with an embodiment of the present invention. Subsequent to the communications described in <figref idref="DRAWINGS">FIG. 3A</figref>, source <b>302</b> can create a final checkpoint manifest <b>362</b>. Source <b>302</b> can send a content object <b>364</b> which is a final checkpoint manifest with a name of, e.g., “/vm-name/chkpt/ver=F/manifest.” In some embodiments, source <b>302</b> sends content object <b>364</b> in response to an interest (from target <b>304</b>) with the same name as the content object name. The version “F” refers to a final version, and can also be a version number or identifier greater than the version number or identifier for the previously transferred manifest. Content object <b>364</b> can be, e.g., pull phase checkpoint manifest <b>250</b> of <figref idref="DRAWINGS">FIG. 2D</figref>.

Target <b>304</b> can retrieve the final checkpoint manifest (function <b>366</b>), which involves transmitting a plurality of interests for the resources indicated in the final manifest. Each interest has a name which indicates the resource and can include a specific feature and corresponding hash value. For example, target <b>304</b> can generate an interest <b>368</b>.<b>1</b> with a name of “/vm-name/chkpt/ver=F/disk/hdB/block_54/hash_bb54” and receive a responsive content object <b>370</b>.<b>1</b> with the same name and which includes as its payload the data corresponding to the specific resource. Because the most crucial information has already been transferred to target <b>304</b> (in stop-and-copy phase <b>308</b>), and because the data model is already running on target <b>304</b> target <b>304</b> can perform function <b>355</b> on demand (i.e., a “lazy” pull at a pace of its choosing).

Upon retrieving all the content objects indicated in manifest <b>364</b>, target <b>304</b> can close the checkpoint (function <b>372</b>), which involves the four-way handshake described above and applied to interest <b>374</b>, content object <b>376</b>, interest <b>378</b>, and content object <b>380</b>. Source <b>302</b> can release the resources (function <b>382</b>) associated with the respective manifest (i.e., version F of the checkpoint manifest, or the final checkpoint manifest).

Thus, communications <b>300</b> and <b>360</b> illustrate how the system facilitates process migration over a CCN, based on the three phases of the pre-copy technique, and further based on standard CCN interest and content object packets with hash-based formatted names. Other process migration techniques are possible, including the post-copy technique and the Remus hot migration technique.

How Nameless Content Objects Facilitate De-Duplication

De-duplication is a technique where only one copy of data exists and the one copy is shared between multiple instances. In CCN, resources can be de-duplicated and shared both within and between virtual machine instances. For example, two disk blocks that have the same hash value refer to the same content object. In this case, only the block index in the manifest is different.

A virtual machine hypervisor may also share blocks between virtual machines. When generating the names used to retrieve content indicated in a checkpoint manifest, the source migration agent running in the source hypervisor can use a name such as “/nyc/host/hash=0x6333” so that any instance or any component can share the same data. If the size of a memory page and the size of a disk block are the same, the data or content object with this name can be both a disk block and a RAM page of the same data (e.g., a shared library code section). The checkpoint manifest can point to different names prefixes for each hash value, and can indicate the virtual resource corresponding to the hash value. Thus, the same physical bytes may be used for many purposes.

As an example, a migration agent may know that some disk blocks are common. The hard disk hdA can mount a read-only root file system that only contains common operating system and application binary resources. These may be associated with a name prefix such a “/nyc/objectstore” and may be shared over many different physical hosts. The checkpoint manifest allows these resources to come from the specific name prefix and also allow other resources to come from a host-specific or virtual machine-specific location. Thus, the system allows for de-duplication of data based on the CCN naming ontology and further based on retrieval of content from both cached copies and varying prefix-based locations.

Routing and Control Channel

The system can manage routing in several ways. We assume that all systems have a unique name (e.g., “/nyc/host7/vm-name”) possibly in addition to a generic name (e.g., “/vm-name”). Three routing models are possible. The first routing model is the external model, where an external agency or agencies manage the routing namespace. One example is a typical CCN interest. In the external model, the source and target migration agents can have different names. The source may have the name prefix “/nyc/host7/vm-name” and the target may have the name prefix “/sfo/host2/vm-name.” A migration orchestrator (e.g., a supervisory process) can understand these names and appropriately instruct the migration agents of the correct names.

The second routing model is the software-defined model, where a central but programmable agency manages the routing namespace, such as a software-defined network environment. In the software-defined model, generic names such as “/vm-name” may be used. Prior to and during the stop-and-copy phase, the name points to the source agent. After the stop-and-copy phase, when the target is ready to strut the data model or virtual machine, the target notifies the network controller to point “vm-name” to the target. This leaves the source with only its location-dependent name, “/nyc/host7/vm-name,” which is used in the pull phase to transfer any remaining data.

The third routing model is the distributed model, where the endpoints manage the routing namespace, e.g., by running a secure routing process. In the distributed model, the source agent advertises “/vm-name” until the completion of the stop-and-copy phase. After this point, the source agent stops advertising the name, and the destination agent begins advertising the name. The destination may then finish transferring data in the pull phase using the location-dependent name of the source agent, e.g., “/nyc/host7/vm-name.”

CCNx routing can be set up such that “/vm-name” points to the correct location of the source system. The target agent can poll the source agent until the source agent is running, and the target agent can then request the first checkpoint (e.g., by issuing interest <b>312</b> in <figref idref="DRAWINGS">FIG. 3A</figref>). After a specific checkpoint is transferred, the target agent can pull the next checkpoint version (e.g., by iterating through push phase <b>306</b> of <figref idref="DRAWINGS">FIG. 3A</figref>).

Recall that each checkpoint manifest indicates the phase (or purpose) of the manifest (i.e., push, stop-and-copy, or pull). The target thus knows to keep its data model (or virtual machine) frozen while receiving a push phase manifest and retrieving the indicated content. The target also knows to start the data model after receiving the stop-and-copy phase manifest and retrieving the indicated content. Upon starting, the data model, the target also knows to retrieve the final manifest for the next checkpoint version, which is the remaining uncopied data which the target agent can subsequently pull or retrieve at its leisure.

Target Device Facilitates Process Migration Over a CCN

<figref idref="DRAWINGS">FIG. 4A</figref> presents a flow chart <b>400</b> illustrating a method by a target device for facilitating process migration in a content centric network, in accordance with an embodiment of the present invention. During operation, a target device determines whether a pre-copy method is used for a migration of a data model (decision <b>402</b>). If the pre-copy method is not being used, and another method such as a post-copy method is being used, the operation continues at operation <b>412</b>. If the pre-copy method is being used, the target device generates a first interest for a first manifest which represents a checkpoint version of the data model, wherein a manifest indicates a phase of the migration and a plurality of resources with corresponding names, wherein the migration phase indicated in the first manifest is a push phase (operation <b>404</b>). In response to receiving the first manifest, the target device transmits a first plurality of interests for the resources indicated in the first manifest based on a name for a respective resource indicated in the first manifest (operation <b>406</b>). The target device retrieves content objects in response to the first plurality of interests (operation <b>408</b>). The target device closes the checkpoint corresponding to the first manifest (operation <b>410</b>, and as described below in relation to <figref idref="DRAWINGS">FIG. 5</figref>).

The target device receives a second manifest which represents a hot version of the data model, wherein the migration phase indicated in the second manifest is a stop-and-copy phase (operation <b>412</b>). Receiving the second manifest is in response to the source device reaching a predetermined threshold (i.e., determining that marginal benefits result from transferring a checkpoint manifest, as in function <b>333</b> of <figref idref="DRAWINGS">FIG. 3A</figref>). Receiving the second manifest is further in response to the source device freezing the data model on the source device (as in function <b>334</b> of <figref idref="DRAWINGS">FIG. 3A</figref>). In response to receiving the second manifest, the target device transmits a second plurality of interests for the resources indicated in the second manifest based on a name for a respective resource indicated in the second manifest (operation <b>414</b>). The target device retrieves content objects in response to the second plurality of interests (operation <b>416</b>), and the operation continues at Label A of <figref idref="DRAWINGS">FIG. 4A</figref>.

<figref idref="DRAWINGS">FIG. 4B</figref> presents a flow chart illustrating a method by a target device for facilitating process migration in a content centric network, in accordance with an embodiment of the present invention. During operation, the target device closes the checkpoint corresponding to the second manifest (operation <b>422</b>, and as described below in relation to <figref idref="DRAWINGS">FIG. 5</figref>). The target device starts the data model on the target device based on the retrieved content objects (operation <b>424</b>).

The target device receives a third manifest which represents a final version of the data model, wherein the migration phase indicated in the third manifest is a pull phase (operation <b>426</b>). In some embodiments, such as a process migration based on a post-copy method, there may be more than one single “final” pull checkpoint manifest The target device transmits a third plurality of interests for the resources indicated in the third manifest based on a name for a respective resource indicated in the third manifest, wherein transmitting the third plurality of interests is based on a policy of the target device (operation <b>428</b>). The target device retrieves content in response to the third plurality of interests (operation <b>430</b>). The target device closes the checkpoint corresponding to the third manifest (operation <b>432</b>, and as described below in relation to <figref idref="DRAWINGS">FIG. 5</figref>).

Closing a Checkpoint

<figref idref="DRAWINGS">FIG. 5</figref> presents a flow chart <b>500</b> illustrating a method by a target device for closing a checkpoint during process migration in a content centric network, in accordance with an embodiment of the present invention. Closing a checkpoint may be initiated by a target device, and can occur after the target device finishes retrieving all data associated with a respective checkpoint manifest. During operation, a target device transmits a first interest which is a close checkpoint message with a name that indicates a respective manifest (operation <b>502</b>). In response to receiving an acknowledgment of the first interest, the target device transmits a second interest which is a confirm checkpoint close message with a name that indicates the respective manifest (operation <b>504</b>). The target device receives an acknowledgement of the second interest, wherein the source device releases the resources indicated in the respective manifest (operation <b>506</b>).

Source Device Facilitates Process Migration Over a CCN

<figref idref="DRAWINGS">FIG. 6A</figref> presents a flow chart <b>600</b> illustrating a method by a source device for facilitating process migration in a content centric network, in accordance with an embodiment of the present invention. During operation, a source device determines whether a pre-copy method is used for a migration of a data model (decision <b>602</b>). If the pre-copy method is not being used, and another method such as a post-copy method is being used, the operation continues at operation <b>612</b>. If the pre-copy method is being used, the source device generates a first manifest which represents a checkpoint version of the data model, wherein a manifest indicates a phase of the migration and a plurality of resources with corresponding names, wherein the migration phase indicated in the first manifest is a push phase (operation <b>604</b>). The first manifest can be a checkpoint manifest which indicates a unique version identifier for the data model. In response to receiving a first plurality of interests for the resources indicated in the first manifest based on a name for a respective resource indicated in the first manifest, the source device transmits a first plurality of corresponding content objects (operation <b>606</b>). The source device closes the checkpoint corresponding to the first manifest and releases the resources indicated in the first manifest (operation <b>608</b>, and as described below in relation to <figref idref="DRAWINGS">FIG. 5</figref>).

The source device determines whether a pre-determined threshold has been reached (decision <b>610</b>) (i.e., marginal benefits result from transferring a checkpoint manifest, as in function <b>333</b> of <figref idref="DRAWINGS">FIG. 3A</figref>). If the threshold is not reached, the operation returns to operation <b>604</b>, i.e., generating and transferring another checkpoint manifest to the target device. If the threshold is reached, the source device freezes the data model on the source device (as in function <b>334</b> of <figref idref="DRAWINGS">FIG. 3A</figref>), and the operation continues at Label B of <figref idref="DRAWINGS">FIG. 6B</figref>.

<figref idref="DRAWINGS">FIG. 6B</figref> presents a flow chart <b>620</b> illustrating a method by a source device for facilitating process migration in a content centric network, in accordance with an embodiment of the present invention. During operation, the source device generates a second manifest which represents a hot version of the data model, wherein the migration phase indicated in the second manifest is a stop-and-copy phase (operation <b>622</b>). In response to receiving a second plurality of interests for the resources indicated in the second manifest based on a name for a respective resource indicated in the second manifest, the source device transmits a second plurality of corresponding content objects (operation <b>624</b>). When the target receives the second plurality of corresponding content objects, the target device starts the data model on the target device (as in operation <b>424</b> of <figref idref="DRAWINGS">FIG. 4B</figref>). The source device closes the checkpoint corresponding to the second manifest and releases the resources indicated in the second manifest (operation <b>626</b>, and as described below in relation to <figref idref="DRAWINGS">FIG. 5</figref>).

The source device generates a third manifest which represents a final version of the data model, wherein the migration phase indicated in the third manifest is a pull phase (operation <b>628</b>). In some embodiments, including process migration based on a post-copy method, there may be more than one single “final” pull checkpoint manifest. In response to receiving a third plurality of interests for the resources indicated in the third manifest based on a name for a respective resource indicated in the third manifest, the source device transmits a third plurality of corresponding content objects (operation <b>630</b>). The source device closes the checkpoint corresponding to the third manifest and releases the resources indicated in the third manifest (operation <b>632</b>, and as described below in relation to <figref idref="DRAWINGS">FIG. 5</figref>).

Exemplary Computer System

<figref idref="DRAWINGS">FIG. 7</figref> illustrates an exemplary computer system that facilitates process migration in a content centric network, in accordance with an embodiment of the present invention. Computer system <b>702</b> includes a processor <b>704</b>, a memory <b>706</b>, and a storage device <b>708</b>. Computer system <b>702</b> can be a source device or a target device for a migration of a data model. Memory <b>706</b> can include a volatile memory (e.g., RAM) that serves as a managed memory, and can be used to store one or more memory pools. Furthermore, computer system <b>702</b> can be coupled to a display device <b>710</b>, a keyboard <b>712</b>, and a pointing device <b>714</b>. Storage device <b>708</b> can store an operating system <b>716</b>, a content-processing system <b>718</b>, and data <b>730</b>.

Content-processing system <b>718</b> can include instructions, which when executed by computer system <b>702</b>, can cause computer system <b>702</b> to perform methods and/or processes described in this disclosure. Specifically, content-processing system <b>718</b> may include instructions for sending and/or receiving data packets to/from other network nodes across a computer network, such as a content centric network (communication module <b>720</b>). A data packet can include an interest packet or a content object packet with a name which is an HSVLI that includes contiguous name components ordered from a most general level to a most specific level. The name can be a hash-based name, where the last name component is the hash value of the respective content object. A data packet can also include a manifest or an acknowledgment.

Further, content-processing system <b>718</b> can include instructions for generating a first interest for a first manifest which represents a version of the data model (interest-generating module <b>724</b>). Content-processing system <b>718</b> can include instructions for, in response to receiving the first manifest, transmitting a first plurality of interests for the resources indicated in the first manifest based on a name for a respective resource indicated in the first manifest (communication module <b>720</b> and interest-generating module <b>724</b>). Content-processing system <b>718</b> can include instructions for starting the data model on the system based on content objects retrieved in response to the first plurality of interests and other interests for other resources indicated in other manifests (data model-managing module <b>728</b>).

Content-processing system <b>718</b> can include instructions for transmitting a first interest which is a close checkpoint message with a name that indicates a respective manifest (communication module <b>720</b> and interest-generating module <b>724</b>). Content-processing system <b>7</b><b>18</b> can include instructions for, in response to receiving an acknowledgment of the first interest, transmitting a second interest which is a confirm checkpoint dose message with a name that indicates the respective manifest (communication module <b>720</b> and interest-generating module <b>724</b>). Content-processing system <b>718</b> can include instructions for receiving an acknowledgment of the second interest (communication module <b>720</b>).

Content-processing system <b>718</b> can include instructions for generating a first manifest which represents a version of the data model (manifest-generating module <b>722</b>). Content-processing system <b>718</b> can include instructions for, in response to receiving a first plurality of interests for the resources indicated in the first manifest based on a name for respective resource indicated in the first manifest, transmitting a first plurality of corresponding content objects (communication module <b>720</b> and content-generating module <b>726</b>). Content-processing system <b>718</b> can include instructions for, in response to reaching a predetermined threshold (threshold-determining module <b>730</b>): freezing the data model on the system (data model-managing module <b>728</b>); and generating a second manifest (manifest-generating module <b>722</b>).

Data <b>732</b> can include any data that is required as input or that is generated as output by the methods and/or processes described in this disclosure. Specifically, data <b>732</b> can store at least: an interest; a content object; a name; a name that is an HSVLI that includes contiguous name components ordered from a most general level to a most specific level; a routable prefix or a name prefix that indicates one or more contiguous name components beginning from the most general level; a manifest; a data model; a version number or identifier of a data model; a phase of a migration; resources and corresponding names; a hash-based name; a hash value of data representing a resource; an indicator of a pre-copy technique, a post-copy technique, or any other migration technique; an indicator of a push, stop-and-copy, or pull phase; an instruction to freeze or start a data model; a virtual machine architecture; a manifest which represents a collection of data including resources, features, and hash values; a configuration file or link; a predetermined marginal threshold; a checkpoint version of a data model; a message; an acknowledgment of a message; a close checkpoint message; a confirm checkpoint close message; and an indicator of a manifest.

The data structures and code described in this detailed description are typically stored on a computer-readable storage medium, which may be any device or medium that can store code and/or data for use by a computer system. The computer-readable storage medium includes, but is not limited to, volatile memory, non-volatile memory, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs), DVDs (digital versatile discs or digital video discs), or other media capable of storing computer-readable media now known or later developed.

The methods and processes described in the detailed description section can be embodied as code and/or data, which can be stored in a computer-readable storage medium as described above. When a computer system reads and executes the code and/or data stored on the computer-readable storage medium, the computer system performs the methods and processes embodied as data structures and code and stored within the computer-readable storage medium.

Furthermore, the methods and processes described above can be included in hardware module. For example, the hardware modules can include, but are not limited to, application-specific integrated circuit (ASIC) chips, field-programmable gate arrays (FPGAs), and other programmable-logic devices now known or late developed. When the hardware modules are activated, the hardware modules perform the methods and processes included within the hardware modules.

The foregoing descriptions of embodiments of the present invention have been presented for purposes of illustration and description only. They are not intended to be exhaustive or to limit the present invention to the forms disclosed. Accordingly, many modifications and variations will be apparent to practitioners skilled in the art. Additionally, the above disclosure is not intended to limit the present invention. The scope of the present invention is defined by the appended claims.