Separating Frontend and Storage backend
I have bunch of isos and machine images what I moved to another physical server with tftp on it.
After replacing the tftp server for the LAN to my storage server, my menu and boot images work fine but the fog deployment system itself is not.
I would like to know what protocol does FOG use to upload and download machine images what you create with the rescue? If it possible I don’t want to run webserver or nfs on my storage server just tftpd-hpa.
Is it possible to do all the transfers through that?
you’ll want to edit the default storage node info on the storage management page to change these settings.
i have never used clonezilla, but it might be more in line with what you want
Ok then maybe you could explain what modifications do I need to do on my FOG server to redirect all the NFS/FTP requests to my new storage server on another ip if it’s possible.
Would clonezilla be easier to migrate to architecture like this? I don’t relly need the web frontend at all, I do need 2 functionalities:
1, Booting dos, windows, linux floppy images through PXE (this is working)
2, Option to image windows/linux machines through PXE (this broke now)
no, nfs is used for image file transfer, ftp is used for move/delete opperations. you need both
Ok thanks for the answer, fortunately that machine has regular ftp server as well. Can I just reconfigure FOG to use that by default? Thanks!
[quote=“kek, post: 36641, member: 21879”]If it possible I don’t want to run webserver or nfs on my storage server just tftpd-hpa.
Is it possible to do all the transfers through that?[/quote]
fog uses nfs and ftp for storage servers, you can not do it though tftp exclusively, and even if you could, it would be excruciatingly slow