Image hosting on NFS server, process uncompleted?

[Junkhacker]

you won’t lose your images on an upgrade, and what pxe problems did you have? i’m sure we can fix them

[arnaudrigole]

@Junkhacker

Ok i’ll try to snapshot my fog vm before upgrade, then try to upgrade.

Seeing that the early uses it generated more problems than I already was in , I preferred board on version 1.2 . I do not remember exactly , but it was impossible to automatically inventory a machine, it had to be done manually , and after it was impossible to launch any task.

[arnaudrigole]

@Junkhacker
Is it possible to copy/paste all .img files which are actually on fog local storage, on fog external storage and make em readable for fog webui?
Is it a procedure to transfer an image?

[Junkhacker]

i don’t know if there is a procedure, per se, but you can move images to a new storage node. just copy the image (including the directory and all files in it) and update the image profile with the new location

[Wayne Workman]

@arnaudrigole I have some methods documented.

using lftp:
lftp -c 'open x.x.x.x; user UserGoesHere PasswordHere; mirror -e /images/TheImagePath /images/TheImagePath; quit'

using NFS:
mount x.x.x.x:/<remote directory> <local directory>
cp -R /mbimages/Optiplex9020UEFI /images/Optiplex9020UEFI
umount <local directory>

Using Samba:
mkdir /tempMount
mount -t cifs //x.x.x.x/ShareNameGoesHere /tempMount -o username=YourUsernameGoesHere -o password=YourPasswordGoesHere,noexec
cp -r /tempMount/ImageNameHere /images/ImageNameHere
umount /tempMount

using SCP:
scp -r /images/ImageNameHere root@x.x.x.x:/images/ImageNameHere

using rsync:
rsync -a /images/ImageNameHere root@x.x.x.x:/images/ImageNameHere

wiki worthy

[arnaudrigole]

@Wayne-Workman @Junkhacker
Thank you very much.

I let you informed about my issue after upgrading to trunk.

Have a good night

[arnaudrigole]

@Wayne-Workman
Hello Wayne,
After i’ve transfered all img files on the new location (nfs server), how to index it on fog webgui? (make the image recognized by fog server)

[Sebastian Roth]

@arnaudrigole When you put the files in the correct directory FOG will see them. No need to index or anything!

[arnaudrigole]

@Sebastian-Roth
Ok i’ll try :). Thank you.

[Wayne Workman]

@Sebastian-Roth I think he’s talking about the image definitions, in the web gui.

If the image definitions are not already there, and the old server was the same version as the new one, you can try to export the images and import them. Otherwise you must create the definitions manually.

[Sebastian Roth]

Ohhhh, didn’t read properly. If this is a complete new server (and DB) then you need to create the image definition or import those from a DB dump… sorry for that!

[george1421]

Or depending on the source FOG server version, export the Image definitions into a csv file and then import them into the new fog server. The image files are already on the target server, what is missing is the db definitions.

We have to do something similar in our multi-master/storage node setup (unique configuration for our application. But only when we add new images in our environment).

[arnaudrigole]

@george1421 @Sebastian-Roth @Wayne-Workman

Thanks for your help. I haven’t new fog server, i just setup a new storage node on Windows Server 2008R2.

Currently, my images are stored on /images on the fog local server, i wanna know if it’s possible to move em on my windows nfs server, like Wayne described : copy all the .img files in fogserver:/images in a directory named exactly as the local fog server directory.

I’m currently copying an image (18gb) on nfs server, then i’ll create the correspondant entry on fog webui and will see if it see the image : )

[Wayne Workman]

@arnaudrigole Oh. I guess I missed the part about the windows storage node somewhere? Sorry.

Guess Sebastian was right to begin with (he doesn’t make mistakes too often).

So, if the windows server is configured as a storage node, you’re good to go. Don’t worry about the image definitions.

However - You’ll need more than NFS on the windows server, you’ll need FTP too. Windows Server comes with both of these things native, and I would recommend using the windows native tools to set it up.

@george1421 has a writeup explaining how to do it all via PowerShell - and I would recommend his instructions. In the past, I’ve tried setting it up via GUI in windows and things just weren’t working.

However… I do now have a windows server setup at home, it could be an opportune time to maybe document the process…

[arnaudrigole]

@Wayne-Workman
I just transfered .img files in a directory named “P7510Win7prox64CAO” , exactly like defined in the “image path” on the image i created on fog webgui.

Created a storage group for my windows server, and setup this image on that storage group.

Fog don’t see the image size, i think it dont recognize it…

[Wayne Workman]

@arnaudrigole You need to setup FTP on the windows node, create an FTP account called fog, and then give that account full access to the images directory.

Also: https://forums.fogproject.org/topic/6941/windows-server-as-fog-storage-node-reboot

[george1421]

@arnaudrigole Sorry I’ve been involved with too many threads in the last few days.

For the image size bit, you need to have an ftp server setup on that windows storage node since if the storage node doesn’t respond to the http calls as with a normal linux storage node, Tom set it up to default back to the FTP query to get the image size.

[edit]
Well if Wayne can post a link, so can I: https://forums.fogproject.org/topic/6941/windows-server-as-fog-storage-node-reboot The first post there gives the powershell commands to use the windows built in ftp server for FOG.

[arnaudrigole]

@george1421 @Wayne-Workman
Wayne, remember , i’ve already set the complete environment NFS / FTP on my windows server using filezilla & windows nfs . Fog user is already created, with full rw rights on root E: E:/images E:/images/dev

@george1421 I don’t understand what you say ? my ftp server is set up and work ?

[george1421]

@arnaudrigole The fog server talks to the storage nodes (windows or linux).

IF the storage node is a linux server with the fog storage node install this communication is via http calls.

If the storage node doesn’t respond with the proper response to the http calls it will revert back to the old way and use FTP to communicate with the storage node. You need to ensure the ftp user ID and password defined in the storage node configuration matches the ftp user account on the remote storage node. Getting the image size IS a function of the FTP communications. The home server for the FOG FTP account must be the images root on the remote storage node. If this is wrong then the FTP communications won’t work.

[arnaudrigole]

@george1421
Thanks for that precisions. The credentials used are both the same on webgui & filezilla.

I don’t use built-in ftp server because the procedure described is for 2012, and i don’t master 2008 powershell anymore to find equivalent cmds … FileZilla looks more simply, and seems working because i can connect on it from any client, write any file or directory on it with no problem. But FOG can’t…