Topics created by David Durr

Tom,

Thanks for your explanation. I thought the randomized TFTP password was a fogcrypt hash. I ended up doing a new install anyway. I’d done lots of learning and experimenting on the last install, so thought it was a good idea to reinstall before we rolled this out.

I can’t thank you guys enough for the work you’re doing. I’ll be making a donation, and I’m not a developer (not much of one anyway), but I’d be glad to help in any way I can.

[quote=“David Durr, post: 20805, member: 17319”]Folks,

I have set up three fog nodes on separate subnets. The master is on subnet A with storage nodes on subnets B and C. All of them work. Images are being replicated and clients on each subnet boot from the local pxe server and images get installed.

However, I am noticing that sometimes clients on subnet C are installing images from the nodes on subnets A or B. I started a client image from subnet C this morning and it pulled its image from the node on subnet C. When I started a second client image on subnet C, it was pulling an image from the node on subnet A.

Perhaps this is a load balancing mechanism, but this is causing problems because the WAN connection subnet C and the other two subnets is slow. I need clients on subnet C to install images from the node on subnet C.

I imagined that all clients on subnet B would install images from the node on subnet B, all clients on subnet A would install images from the node on subnet A and so on.

Is this not the case or do I have something else going on?

Thanks for any help.[/quote]

BryceZ answered this. His solution has fixed my problem:

Without using the location patch, you can set FOG up to do what you want, but it gets a little ugly… Using one master Storage Group you add your remote Node to it, and create your master image pointing to the master Group, this way FOGSync will replicate the image between the master Node and the remote Node. Then you set up a remote Group and a second Node definition that matches the first remote Node except it uses the remote Group instead of the master Group. Then you set up a second image definition that matches the first image except it uses the remote Group. So now when you set up a host at the remote location you assign it to the remote image and it will only pull from the remote Group, and because the remote Node is in both Groups the image is just a copy of the image you first created on the master Group. Not the easiest setup, but it works.

IPTables isn’t, to my knowledge, the firewall that’s running.

Ubuntu 12.04, to my knowledge, uses ufw for its firewall program. try:
[code]sudo ufw disable[/code] On both of the boxes and try again. I’m currently installing two Ubuntu 12.04 boxes just to give it a shot as well to help in troubleshooting.