New Fog Server - /images location

[george1421]

@Technolust said in New Fog Server - /images location:

however, when there is an upgrade will the upgrade know the location?

Yes your answers to the questions are stored in a hidden file in /opt/fog/.fogsettings That file is referenced each time the installer is run, even between version upgrades.

Also what is the difference in the installer between Normal/Storage?

A “Normal” install is a traditional FOG server with webui. A Storage [node] is a deploy only server that has no web gui, a storage node must connect to a Normal mode FOG server to be functional. You would use storage nodes, maybe at remote locations so you can deploy images locally to target computers at the same site as the storage node.

[Technolust]

Awesome, Thanks George. Running through the installer now and just saw the installer explain the difference… Haha, Reading is fundamental…

[Technolust]

@george1421

Hey George,

The installer doesn’t ask you for a location it automatically chooses the install location.

What version of Linux would you like to run the installation for?

      1) Redhat Based Linux (Redhat, CentOS, Mageia)
      2) Debian Based Linux (Debian, Ubuntu, Kubuntu, Edubuntu)
      3) Arch Linux

Choice: [1]

Starting Redhat based Installation

FOG Server installation modes:
* Normal Server: (Choice N)
This is the typical installation type and
will install all FOG components for you on this
machine. Pick this option if you are unsure what to pick.

  * Storage Node: (Choice S)
      This install mode will only install the software required
      to make this server act as a node in a storage group

More information:
http://www.fogproject.org/wiki/index.php?title=InstallationModes

What type of installation would you like to do? [N/s (Normal/Storage)] Normal

What is the IP address to be used by this FOG Server? [10.141.0.20]

Would you like to change the default network interface from ens160?
If you are not sure, select No. [y/N] n

Would you like to setup a router address for the DHCP server? [Y/n] y
What is the IP address to be used for the router on
the DHCP server? [10.141.0.1]10.141.0.27

Would you like DHCP to handle DNS? [Y/n] n

Would you like to use the FOG server for DHCP service? [y/N] n

This version of FOG has internationalization support, would
you like to install the additional language packs? [y/N] n

######################################################################

FOG now has everything it needs for this setup, but please

understand that this script will overwrite any setting you may

have setup for services like DHCP, apache, pxe, tftp, and NFS.

######################################################################

It is not recommended that you install this on a production system

as this script modifies many of your system settings.

######################################################################

This script should be run by the root user.

It will prepend the running with sudo if root is not set

######################################################################

** Notice ** FOG is difficult to setup securely

SELinux and IPTables are usually asked to be disabled

There have been strides in adding capabilities

The recommendations would now be more appropriate

to set SELinux to permissive and to disable firewall for now.

You can find some methods to enable SELinux and maintain firewall

settings and ports. If you feel comfortable doing so please do

######################################################################

Please see our wiki for more information at:

######################################################################

https://wiki.fogproject.org/wiki/index.php

######################################################################

• Here are the settings FOG will use:

• Base Linux: Redhat

• Detected Linux Distribution: CentOS Linux

• Server IP Address: 10.141.0.20

• Server Subnet Mask: 255.255.255.0

• Interface: ens160

• Installation Type: Normal Server

• Internationalization: 0

• Image Storage Location: /images

• Using FOG DHCP: No

• DHCP will NOT be setup but you must setup your
  | current DHCP server to use FOG for PXE services.

• On a Linux DHCP server you must set: next-server and filename

• On a Windows DHCP server you must set options 066 and 067

• Option 066/next-server is the IP of the FOG Server: (e.g. 10.141.0.20)

• Option 067/filename is the bootfile: (e.g. undionly.kpxe)

• Are you sure you wish to continue (Y/N)

[george1421]

@Technolust Well color me wrong. I’m pretty sure it use to…

If you look in the /opt/fog/.fogsettings file does it contain a field for /images?

We can manually fix it, but it would be swell if it retained the settings for the next install.

[Technolust]

@george1421 No worries man, should I just go ahead and go through with the install afterwords and see if we can change it? I will take an image of the server and revert back to it if I need revert back. I’m asking because I don’t have the /opt/fog directory configure yet because I canceled the install.

Thoughts?

[george1421]

@Technolust Well confirm that the… let me remote into my office and see if the field is there. Lets not do a bunch until we know. We can make it work like you need it. Give me a few minutes to double check things.

[george1421]

@Technolust OK I just looked and there IS the field in question. Its called storagelocation. Go ahead and do a normal install, let it default to /images

[george1421]

@george1421 Just open thoughts on changing storage location.

1. Update .fogsettings storagelocation field.
2. Update /etc/exports to from /images and /images/dev to new locations /fogserver/images and /fogserver/images/dev
3. Copy everything from /images to /fogserver/images
   cp -r -f /images/* /fogserver/images
4. Make sure directory permissions match between /images and /fogserver/images
5. In the web ui update Fog Settings->Fog Configuration Expand all settings and then search for /images and replace with proper path
6. Go to default storage node settings and update /images to /fogserver/images
7. Then back to the linux command prompt and rerun the fog installer script.
8. Double check /etc/exports to ensure that /fogserver/images is still shared.
9. Reboot the fog server
10. At the linux command prompt key in showmount -e 127.0.0.1. It should show /fogserver/images being exported after a reboot.

That should do it.

[Technolust]

@george1421 Ok George, so going ahead with the default install and then will try the settings below. Sound right?

[Technolust]

@george1421 Is it common to leave the mysql password blank?

[Sebastian Roth]

@Technolust said:

Is it common to leave the mysql password blank?

No you better set a proper mysql root password before installing FOG. We are working on the installer to pilot people to set passwords.

[Technolust]

@Sebastian-Roth That’s what I figured. Thank you!!!

[Technolust]

@george1421 Hey George, in step 5, the Web GUI -> Fog Configuration -> Fog Settings -> Expand all -> there is no /images location. Should there be any specific settings? In step 6 do I also change the FTP path to /fogserver/images from /images? If so I did that as well. Finally step 10 - Looks good.
Export list for 127.0.0.1:
/fogserver/images/dev *
/fogserver/images *

Can you tell me if this will need to be performed for every update or will fog server updates keep these settings?

[Technolust]

Should the Storage Node show online?

When I go to storage nodes it is up and running.

Thoughts?

Thanks,

Technolust

[george1421]

@Technolust said in New Fog Server - /images location:

Web GUI -> Fog Configuration -> Fog Settings -> Expand all -> there is no /images location

Sorry I wrote that post from memory since I didn’t have immediate access to a fog console to verify.

also change the FTP path to /fogserver/images from /images?

Right you need to change everywhere you would see /images to the new images path.

It looks good for the export list.

If you updated the .fogsettings file in step 1 then no, it should be automatic moving forward.

[george1421]

@Technolust What does the content of the default storage node look like?

Also did you reboot the fog server after you made all of those changes? Some values are only loaded at boot time.

[Technolust]

@george1421 Thanks, I did make the change for the ftp path and I did update the .fogsettings in step 1 as well as rebooted the server. Only thing now is the Storage Node not coming online.

/fogserver/images/

[root@fogserver images]# ls -lrt
total 12
drwxrwxrwx. 3 fog root 4096 Jan 22 09:21 dev
drwxrwxrwx. 2 fog root 4096 Jan 22 09:21 postdownloadscripts
drwxrwxrwx. 2 fog root 4096 Jan 22 10:03 T470-Win10

[george1421]

@Technolust I don’t have a clue about the storage node on the home screen. But from your ls command you are missing 2 check files. If you run ls -la on the old /images directory you will see a file called .mntcheck and the second one of the same name needs to be in /images/dev. Those will need to be recreated in your new location paths. You can simply do:
touch /fogserver/images/.mntcheck
and
touch /fogserver/dev/images/.mntcheck

its ok if they are already there, that touch command will just update the last time the file was access, or create it if it wasn’t there.

[Technolust]

@george1421 said in New Fog Server - /images location:

touch /fogserver/dev/images/.mntcheck

Ok looks like /fogserver/dev/images doesn’t exist. Is this supposed to be /fogserver/images/dev?
If so I ran touch touch /

[root@fogserver images]# ls -la /fogserver/images/
total 20
drwxrwxrwx. 5 fog root 4096 Jan 22 10:03 .
drwxr-xr-x. 3 root root 4096 Jan 22 09:16 …
-rwxrwxrwx. 1 fog root 0 Jan 22 10:25 .mntcheck
drwxrwxrwx. 2 fog root 4096 Jan 22 10:03 T470-Win10
drwxrwxrwx. 3 fog root 4096 Jan 22 09:21 dev
drwxrwxrwx. 2 fog root 4096 Jan 22 09:21 postdownloadscripts
[root@fogserver images]# ls -la /fogserver/dev/images/
ls: cannot access /fogserver/dev/images/: No such file or directory
[root@fogserver images]# ls -la /images/
total 16
drwxrwxrwx. 4 fog root 4096 Jan 22 09:10 .
dr-xr-xr-x. 22 root root 4096 Jan 22 09:36 …
-rwxrwxrwx. 1 fog root 0 Jan 22 09:10 .mntcheck
drwxrwxrwx. 3 fog root 4096 Jan 22 09:10 dev
drwxrwxrwx. 2 fog root 4096 Jan 22 09:10 postdownloadscripts
[root@fogserver images]#

[root@fogserver images]# touch /fogserver/images/dev/
[root@fogserver images]# ls -la /fogserver/images/dev/
total 12
drwxrwxrwx. 3 fog root 4096 Jan 22 10:28 .
drwxrwxrwx. 5 fog root 4096 Jan 22 10:03 …
-rwxrwxrwx. 1 fog root 0 Jan 22 09:21 .mntcheck
drwxrwxrwx. 2 fog root 4096 Jan 22 09:21 postinitscripts
[root@fogserver images]#

[george1421]

@Technolust said in New Fog Server - /images location:

touch /fogserver/dev/images/.mntcheck

Ok looks like /fogserver/dev/images doesn’t exist. Is this supposed to be /fogserver/images/dev?

OK its time for either another cup of coffee or for me to just go back to bed. The path /fogserver/dev/images is of course wrong. I should have typed /fogserver/images/dev

It looks like you have the check file in the proper paths from your ls command. But after a reboot your storage node is still showing off-line?