Image hosting on NFS server, process uncompleted?

[Wayne Workman]

@arnaudrigole on the FileZilla server thing, at the CLI, go to your images directory and issue the pwd command. What does it say?

[george1421]

@arnaudrigole said:

@george1421
The 2008 server is the storage node, which is defined directly with its @ip on a fog storage node/group

Ok that explains why things are not working!! I started setting up how to do this with Server 2012, but ran out of time. The root of your issue is that you need to install FTP on the Windows storage node to move the files. This guide should get you started: https://forums.fogproject.org/topic/6941/windows-server-as-fog-storage-node-reboot Understand this is for 2012 but 2008 is very similar. I used powershell for the copy and paste reasons.

[Wayne Workman]

@george1421 Yup. You’re exactly correct. It’s also worth noting here that FileZilla is un-necessary. Windows Server has all the necessary components available already.

[arnaudrigole]

@Wayne-Workman @george1421
I’m sorry, i don’t understand what you try to say me …
Wayne, what is the CLI? whats the pwd command on a 2008 server?

George, i followed this guide to setup the nfs server, but the powershell commands aren’t the same on 2008 and 2012, i adapted it by search on microsoft an equivalent.(i stopped to follow the guide on that step, because i use FILEZILLA SERVER for ftp)

I don’t understand my problem ; i need to install FTP on my Windows storage node more than filezilla server ?..

It look very complicated, it works just with filezilla + nfs role , but it just can’t create the directory on /images…

[Wayne Workman]

@arnaudrigole I thought your node was a linux node… You can disreguard. FYI the acronym for CLI is Command Line Interface.

Also - I’m a purist. I will not install third party anything if the base-OS can do it natively. This solves a lot of maintenance issues, update issues, and reduces complexity overall.

[arnaudrigole]

@Wayne-Workman
i hope this is why you ask me:
i just opened a cmd, when type the following cmds:

c:\windows\system32> ftp 10.1.11.64 <-- windows storage node
ftp> use fog
331 password required for fog
ftp> fogpassword
230 Logged on
ftp> cd /informatique/Service_info/FOG/images
250 CWD successful. “/informatique/Service_info/FOG/images” is current directory
ftp> pwd
257 “/informatique/Service_info/FOG/images” is current directory

[Wayne Workman]

@arnaudrigole said in Image hosting on NFS server, process uncompleted?:

/informatique/Service_info/FOG/images

That’s your FTP path.

FOG Trunk supports independent FTP paths, which you need.

[arnaudrigole]

@Wayne-Workman
OK so … what i’ve to do ?..
If i upgrade to trunk, I’ll need to redo all my images, and get pxe boot problems what i’ve already encountered in test environment…

[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).