Installing a new clean fog server
-
Thanks for the information.
The reason why i’m using VMWare workstation is to test it before i put it in our VMWare pool.
Once it’s fully tested and working by me i will put it on a VMWare server and manage it from the vsphere client.
-
@predator To each their own I guess. We do guest testing all the time in our vSphere production environment. You’re the first person I’ve ever heard of who has an ESXi host, but does all their testing in VMware Workstation O_o.
-
Yep don’t mind me it’s just a infrastructural decision.
-
Having problems with entering the following command lines in centOS
echo “Open UDP port 49152 through 65532, the possible used ports for fog multicast”
firewall-cmd --permanent --add-port=49152-65532/udp
echo “Allow IGMP traffic for multicast”
firewall-cmd --permanent --direct --add-rule ipv4 filter INPUT 0 -p igmp -j ACCEPT
systemctl restart firewalld.service
echo “Done.”FYI i’m not using putty but entering the commands in terminal of centOS.
Any idea why this is not working? I get the error command not found…
This is a step of the continue pre-config step from wiki guide: https://wiki.fogproject.org/wiki/index.php?title=CentOS_7
-
Nevermind i managed to make the command lines work.
Can someone explain me which one and why i should activate the following?
Set SELinux to permissive on boot:
sed -i.bak ‘s/^.\SELINUX=enforcing\b.$/SELINUX=permissive/’ /etc/selinux/configSet SELinux to permissive on the fly (this is not persistent, the above config must be done to be persistent):
setenforce 0 -
@george1421 @lmioperations @Sebastian-Roth
Can someone chime in on this?
-
@predator Hi, SELinux must be set to permissive for now in order for certain FOG central services to work correctly (such as NFS).
There have been some attempts to create SELinux profiles instead, but given how often things can change, this is obviously a more cumbersome way of going about it.
You should use both commands. First one will make it so when you reboot, SELinux is in permissive mode, second one sets it in current session so you don’t have to reboot.
-
Simply the
setenforce 0disables selinux (think MS Windows UAC) off without having to reboot your server. Updating the selinux conf file will make the change persistent across reboots. We are recommending you set the value to permissive. This is done so that selinux will record the events but not block them. If you require selinux enabled because of your company’s security policy you can take these logged events and create a selinux profile. This fog selinux profile then can be enabled to allow FOG to run while selinux is enabled. -
@predator said in Installing a new clean fog server:
SELinux to permissive on boot
See if this info helps: https://wiki.gentoo.org/wiki/SELinux/Tutorials/Permissive_versus_enforcing
Looks like George already beat me to a reply :D, and his info ended up being more to the point of what you need with regards to FOG ;).
-
Ok looks like i’m kinda stuck here. I managed to install the fog client and have to visit the management console in my web browser 10.x.x.x/fog/management/index.php
I’m in front of the login page and can’t seem to login. Where the hell did i setup this login i don’t even know…
-
I have setup centos on IPV4 10.2.3.207
When installing the fogclient i choose IPV4 10.2.3.208
I get a response in the terminal to open the management console on http://10.2.3.208/fog/management/index.php
Yet http://10.2.3.208/fog/management/index.php is not reachable…
But when i enter http://10.2.3.207/fog/management/index.php i do get the fog login page…
-
@predator Why did you setup on 207, but then go to 208?
-
@george1421 said in Installing a new clean fog server:
And you are correct all three need different IP addresses.
-
Because George confirmed all three need different ip addresses…
@george1421
1.VM Host = leave network settings on dynamic
2.VM Guest = configure network settings on static
3.FOG Client = configure network settings on staticSo if we set it up like this all 3 would have different ip addresses correct?
-
@predator You have this incorrect.
1.VM Host = leave network settings on dynamic
2.VM Guest = configure network settings on static
3.FOG Client = configure network settings on staticThis should be,
- VM Host = Must be unique, but don’t really care. Not used by/for fog
- VM Guest = configure network settings on static
- FOG Client = dhcp
-
@predator You are adding a little bit of complexity because you are using a type-2 hypervisor.
The requirements for FOG are the same.
-
FOG server must have a unique static address that is not changed after FOG is installed.
-
The target (client) computer must have its IP address assigned by dhcp, because that is the only way it can find out about the FOG server to boot from.
-
-
@predator Well, I think you’re confusing terminologies here.
FOG Client, in my eyes, is the machine you’re attempting to image. The FOG Client, you’re basing your layout on, is actually what I would term “FOG Server”?
VM Host needs an IP address.
VM Guest = FOG Server as I’m seeing it. (This is the vm guest that’s hosting the fog server)
-
@predator How did you configure the virtual NIC to act? (bridged?)
-
I think i am. The fog client is what i call the fog server because we have to install the fog console on the server.
Debriefing:
1 VMWare Workstation (VM Host)
2 CentOS (VM Guest)
3 FOG Management Console (FOG Client)So the FOG management console needs the same IPV4 address as CentOS?
-
Let’s keep things simple here.
A FOG Client is a different computer that connects to the FOG Server.
In other words, your 2 and 3 are one and the same (and thus not a FOG Client). A FOG Client would indeed need a different IP as George said, but this is not the case for you.
Your FOG server ip is the Centos IP, since they are the same. FOG is just software that runs on it, if that makes sense.
