Adding NAS Synology like a node

[george1421]

@ch3i Thank you for the link, but it doesn’t appear to be my specific issue.

Watching the vm boot, it appears that if I use the synology NAS as a normal storage node, during the booting process the target computer is trying to load something from the synology NAS via http. Possibly the bzImage and inits, because that is the part where its getting hung.

Am I missing the point of the OP? To me I would just nfs mount the nas to a mount point on the FOG server. This would allow me to use the nas for storage but the fog server would have the full environment.

[ch3i]

@george1421 How is configured your storage Node, slave/master ?

[george1421]

@ch3i Slave.

It was my understanding that the OP wanted to use a synology nas as a storage node while still having a master node FOG server.

[Tom Elliott]

@george1421 this is possible, but if the storage node to use doesn’t have the image available on it it will not be able to find the storage node in use by the group the image is associated with.

[george1421]

@Tom-Elliott Hmmmm…

I setup NFS (and ftp) on the NAS. Then I configured the NAS as a storage node as normal. The master node then replicated the images to the storage node. When I look in the filestation on the nas I can see all of the image files in that location. So the images are there.

I’m using the location plugin, so in the main storage group I added this synology nas but in the location of “nothere”. Then I created a vm and registered it in the location “nothere”. When I pxe boot it, the target computer loads boot.php and then many dots and then throws the error. What I’m speculating is that the target computer is trying to load the FOS kernel from the storage node (synology nas). Since of course those files are not on the nas it is failing.

I did a little research and I can enable the apache web server on the NAS, but I can only create a virtual server using a dns name, not an IP address. So I’m stopped right here for now. The though was to setup the web server then copy the fog/service/ipxe files over to the synology nas in the right location to make the client boot. (Understand this is more of a fun project to help the OP than something I want)

[Wayne Workman]

@george1421 said:

What I’m speculating is that the target computer is trying to load the FOS kernel from the storage node (synology nas). Since of course those files are not on the nas it is failing.

I’d probably recommend setting up TFTP on the NAS - and copy all the boot files into it. The file default.ipxe is the file that the boot file will look to for instructions. At the bottom in there, you can just specify the primary FOG server’s IP - and I think that would work.

Also - you know, tell DHCP to use the NAS’ IP address for 066.

I don’t worry too much about you, George.

[mtrento]

@Miguel-Palacios
I think fog 1.2 is not totally compatible with synology nas because synology use two different path to access data over NFS & FTP (/volume1/images & /images)
and on fog storage node interface you can only set one path.
(Fog does the rename job with the ftp account.)
you need to go with a newer fog version to have the “ftp path” option.