Deploying your Image a group of clients - Revision history

Wolfbane8653.3362: /* Unicast_vs._Multicast_vs._Torrent-Cast_images */

2014-12-05T15:12:09Z

‎Unicast_vs._Multicast_vs._Torrent-Cast_images

Wolfbane8653.3362: /* Groups */

2014-12-05T15:11:56Z

‎Groups

Wolfbane8653.3362: /* Unicast vs. Multicast vs. Torrent-Cast images */

2014-12-05T15:09:26Z

‎Unicast vs. Multicast vs. Torrent-Cast images

Wolfbane8653.3362: /* Unicast vs. Multicast vs. Torrent-Cast images */

2014-12-05T15:08:14Z

‎Unicast vs. Multicast vs. Torrent-Cast images

Wolfbane8653.3362: /* Start the Task */

2014-12-04T19:21:37Z

‎Start the Task

Wolfbane8653.3362: /* Creating a Group */

2014-12-04T19:21:08Z

‎Creating a Group

Wolfbane8653.3362: /* Start */

2014-12-04T19:21:01Z

‎Start

Wolfbane8653.3362: /* Start */

2014-12-04T19:17:34Z

‎Start

Wolfbane8653.3362: /* staring */

2014-12-04T19:11:07Z

‎staring

Wolfbane8653.3362 at 19:08, 4 December 2014

2014-12-04T19:08:17Z

← Older revision		Revision as of 15:12, 5 December 2014
Line 25:		Line 25:


−	=== ~~Unicast_vs~~.~~_Multicast_vs~~.~~_Torrent~~-Cast_images ===	+	=== Unicast vs. Multicast vs. Torrent-Cast_images ===
	{{Unicast_vs._Multicast_vs._Torrent-Cast_images}}		{{Unicast_vs._Multicast_vs._Torrent-Cast_images}}

← Older revision		Revision as of 15:11, 5 December 2014
Line 25:		Line 25:


		+	=== Unicast_vs._Multicast_vs._Torrent-Cast_images ===
	{{Unicast_vs._Multicast_vs._Torrent-Cast_images}}		{{Unicast_vs._Multicast_vs._Torrent-Cast_images}}

← Older revision		Revision as of 15:09, 5 December 2014
Line 26:		Line 26:

	{{Unicast_vs._Multicast_vs._Torrent-Cast_images}}		{{Unicast_vs._Multicast_vs._Torrent-Cast_images}}
−	~~== Unicast vs. Multicast vs. Torrent-Cast images==~~
−	~~=== Unicast ===~~
−	*Accessible from Host Management --> Select Host --> Basic Tasks
−	*Accessible from Group Management --> Select Group --> Basic Tasks
−	*Accessible from Fog iPXE Menu
−	*This occurs when scheduling a "Download" task, "Quick Image", or during "Full Registration" the user selects image after registration. The server (or storage node) will directly send packets (the image) to that Host's MAC address.(aka. TCP) This is excellent for directing network traffic. This can be performed under Groups running multiple unicasts to multiple hosts. However, all the hosts will not finish at exactly the same time.
−	*Since unicast does not rely or communicate with others in a group it is unaffected by "hung up" host
−
−	~~=== Multicast ===~~
−	*Accessible from Group Management --> Select Group --> Basic Tasks
−	*Accessible Image Management --> Multicast Image
−	*This occurs when scheduling a "Multi-Cast" task from Groups. The server (or storage node) will wait for all Host computers to be network booted. Once all hosts have registered for the task the packets will be sent out out to the entire network.(aka. UDP) Packets are sent and received exactly the same. Image may not complete exactly the same time
−	*Down side to this is if one host gets hung up then the entire process is stopped till that host catches up
−	*[[Multicasting]]
−
−
−	~~===Torrent-Cast===~~
−	* <span style="background-color:RED; color:white;">Currently not working.</span>
−	*Accessible from Host Management --> Select Host --> Basic Tasks --> Advanced
−	*Accessible from Group Management --> Select Group --> Basic Tasks --> Advanced
−	*The image is broken down into chunks and indexed to create a torrent file.
−	*The server (or storage node) beings creates the torrent and starts seeding. The hosts request the torrent and start downloading chunks for the torrent. Once a chunk is received then the hosts will seed that chunk to other hosts. Once torrent is done downloading it will start imaging. Then the partition is rewritten to accomidate the size needed to download the files originally.
−	*If one host gets "hung up" the other host are not affected, but marginal time and speed are lost.

@@ Line 24: / Line 24: @@
 #Boot the Host PCs.
 == Unicast vs. Multicast vs. Torrent-Cast images==
 === Unicast ===

@@ Line 13: / Line 13: @@
 *Now all those Hosts are now part of that group.
-== Start the Task ==
+=== Start the Task ===
 *From the host side follow all instructions from the single client [[Deploying_your_Image_a_single_client]]
 *In the Web GUI section you can change the the images and start tasks from the Groups.

@@ Line 14: / Line 14: @@
 == Start ==
-{{:Deploying_your_Image_a_single_client}}
+*From the host side follow all instructions from the single client [[Deploying_your_Image_a_single_client]]
 == Unicast vs. Multicast vs. Torrent-Cast images==

@@ Line 12: / Line 12: @@
 *#Check mark the Hosts you wish to add to this group and then click "Update Hosts" at the bottom.
 *Now all those Hosts are now part of that group.
 == Unicast vs. Multicast vs. Torrent-Cast images==
@@ Line 19: / Line 22: @@
 *Accessible from Fog iPXE Menu
 *This occurs when scheduling a "Download" task, "Quick Image", or during "Full Registration" the user selects image after registration. The server (or storage node) will directly send packets (the image) to that Host's MAC address.(aka. TCP) This is excellent for directing network traffic. This can be performed under Groups running multiple unicasts to multiple hosts. However, all the hosts will not finish at exactly the same time.
 === Multicast ===
-*Accessible ONLY from Group Management --> Select Group --> Basic Tasks
+*Accessible from Group Management --> Select Group --> Basic Tasks
-*This occurs when scheduling a "Multi-Cast" task from Groups. The server (or storage node) will wait for all Host computers to be network booted. Once all hosts have registered for the task the packets will be sent out out to the entire network.(aka. UDP) All hosts will download the image piece by piece all at exactly the same time and finish at the exact same time.
+*Accessible Image Management --> Multicast Image
 *[[Multicasting]]
 ===Torrent-Cast===
@@ Line 30: / Line 37: @@
 *Accessible from Group Management --> Select Group --> Basic Tasks --> Advanced
 *The image is broken down into chunks and indexed to create a torrent file.
-*The server (or storage node) beings sending packets directly to the "first" host (TCP) once the "first" host completes a chunk it then uploads that chunk to the next host. The next host then downloads it and uploads to the next. This continues with all the chunks and hosts until the hosts have completed downloading the entire image.
+*The server (or storage node) beings creates the torrent and starts seeding. The hosts request the torrent and start downloading chunks for the torrent. Once a chunk is received then the hosts will seed that chunk to other hosts. Once torrent is done downloading it will start imaging. Then the partition is rewritten to accomidate the size needed to download the files originally.