Fog: multicasting across subnets
-
@K.Hays if you go to Image Management and click on one of your images, and then click on “Storage Group” on the left, what do you see?
-
@Wayne-Workman It depends on the image. For the ones linked to the storage node, i.e the middle school group we have, it says Middle School. But the checkbox isn’t checked, should it be? Thats all thats in there though
-
@K.Hays what is the OS you are using on these nodes? What are the actual interface names and are they reflected properly in the db.
-
@Tom-Elliott Im using 14.04 on the nodes also. The interface names on both are eth2. One of the nodes defaulted to eth0 in the database and the other we manually changed to eth2. I believe we got the same results regardless.
-
For now we just decided to put a fog server in each building because summer is approaching quickly and we need a better alternative to ghost. Advice is still welcome if there is any to give at this point. Thanks for the help so far.
-
@K.Hays My advice, don’t multicast. fog unicasting is stupid fast. And - most multicast issues are network problems that unicast does not suffer from.
FYI - I used to use fog with multicast. Then I got over that, because unicast is just so fast. I image an entire lab with unicast in under 30 minutes. 40GB image.
-
@K-Hays Have you done any multicast tests by hand yet? https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_Downloading_-_Multicast
You might want to stick to unicast if you cannot make it work but if you want to deploy the same image to a lot of computers then multicast is one of the nicest ways of doing it I suppose.
-
@Wayne-Workman The problem is the amount of bandwidth that would take up. Unless unicast doesn’t take any more bandwidth than multicast would then that’s not an option. We would be multicasting up to 30+ computers at a time sometimes and I’m afraid unicasting would take down the network in those situations. and Sebastion i ran through that troubleshoot page already, but thank you.
-
@K-Hays Have you had a look at the process list on your FOG server after starting a multicast task? Please show us the output of
ps ax | grep udpon your FOG server while a multicast task is waiting! -
@K.Hays FOG has a queuing functionality. I set my fog server to run 2 tasks at max.
So when I image 30 computers and start them all up, 2 start, 28 wait in line. when the 2 finish, another 2 go.
This is automatic.
-
@Sebastian-Roth ill post this the next time I’m at a separate building so that i can run the test. Might be a little while.
@Wayne-Workman That’s awesome actually i didn’t know that. How many computers can fog do max in this way, do you think? -
@K.Hays said in Fog: multicasting across subnets:
That’s awesome actually i didn’t know that. How many computers can fog do max in this way, do you think?
As many as you wish. I limit mine to 2 to keep things moving along quickly - that way no computer takes hours, but each one takes about 5 minutes and they take turns. This is also easier on the server’s HDD as well.
For image deployment to many hosts at once using unicast, the server’s HDD speed is critical, along with it’s network speed. The switch’s internal throughput is also important.
