Mounting /images/dev Permission Denied
-
@vkenny said in Mounting /images/dev Permission Denied:
Attempting to work my way through the creation of a backup solution…
I just want to address this from your first post. Fog is NOT a backup solution. It is a deployment solution. I do not recommend you try to use it for backups.
-
I think i will revert to a snapshot and follow the instructions initially provided by george1421 and see where this gets me. If it doesn’t work, we will perhaps rethink the architecture. Whatever the case, i will attempt to provide details on the procedure we used once we get it up and running.
-
@Junkhacker yes. poor choice of words on my part. I should have said creation of a “Deployment Solution”.
-
What else is the windows server you’re using do?
Maybe it’s simpler to just change it to a linux server?
Then using it as a storage node is nice and supported. -
I have removed the remote Windows server from the mix. I have added a PERC into the ESXi server that houses my FOG VM’s and connected the Disk Shelf directly into the ESXi host. Have created the Data Store in ESXi.
Now I need to make this Data Store available to 5 different FOG VM’s but with access to the entire storage system across all VM’s. I need to have all VM’s able to access all images.
I know the next question is going to be why do you need 5 FOG VM’s. The reason is we have 5 independent networks that cannot be accessed by any other. Each network is on a different VLAN with different IP schema.
Does anyone know of a FOG Wiki or otherwise that will assist with making this happen?
The Windows remote server didn’t work, and ended up being more trouble than it is worth. We gave up and decided to hook the disk shelf directly into the ESXi host.
-
@vkenny said in Mounting /images/dev Permission Denied:
I know the next question is going to be why do you need 5 FOG VM’s. The reason is we have 5 independent networks that cannot be accessed by any other. Each network is on a different VLAN with different IP schema.
Does your ESXi server have the potential access to all of these vlans?
-
@george1421
Each FOG VM is setup to have access to a specific VLAN through Virtual Switch and Port Group. We have that setup already. -
@vkenny So here’s my thoughts/suggestions, take them as you will.
Setup a Single server, with 5 nics.
Install FOG on that server as you normally would.
Once installed create 4 more storage nodes.
All nodes will contain exactly the same information with the exception of the Name and IP address of the node.
This is just my suggestion. Sharing the same disc with 5 different VM’s is going to cause problems, no matter how it’s done.
-
So how are the storage Nodes synced? If I create an image in lets say “Room 1” but want to deploy that image to say “Room 2” will this be possible?
-
@vkenny Yes. From the VLAN perspective the information remains exactly the same.
The only problem, as I see it, is your /tftpboot/default.ipxe might have some problems.
So after the first install you would want to change the /opt/fog/.fogsettings file.
Edit the ‘ipaddress=’ line to read:
${next-server}where the IP address was. (Literally read${next-server}) (Though I can help you manually edit the/tftpboot/default.ipxefile as this could also cause other unknown issues.)Your DHCP for each vlan would need to point at the respective FOG Server VLAN IP in regards to Option 66/next-server
-
@Tom-Elliott
Do I break the Data store up into 5 different data stores in ESXi, or leave it a single Data store and create 5 different storage nodes from the single data store? -
@vkenny The second element. (Single data store/server, 5 different nodes pointing essentially at the exact same spot.)
