Posts made by jjcjr

@george1421 This worked well.

I had to make one change to the importimages.sql file. I added LOCAL

LOAD DATA LOCAL INFILE “/tmp/imageimport.csv”

@wayne-workman That could work. But I still think that if the specific image folder contained a file that was the image definition, then it could easily be imported, scripted or automated.

Having a file that contains the equivalent of the one line of the images csv file would eliminate the need to have to export, edit and import.

@george1421 Right now I have two remote locations, with up to 6 in the future.

@george1421 We have already tried this approach. You still have to deal with the import and export. Hence the request to have image sql record (exported as a csv file) is contained in the image directory. Then I would just have to do an import images.

In my case the master and remote nodes do not have all the same images on them.

For our use case, we want to have a set of master base images, created on the master server distributed to the remote nodes. From there the remote nodes could use those masters, modify them and save them as a customized image for their remote location.

I need the ability to create images on one system and move them to another system. Both systems are a normal install. Would it be possible to have the FOG system create and update a csv file for each image and store that in the image folder for that image. This way all you need to do to move images from one server to another is copy the /images/ImageNameToBeCopied folder, then do an import image on the new server. The import image would point to the /images folder of the newly copied image and import the CSV file.

Right now, we do an export on one server, then edit the exported csv file. Copy the folder to the new server, then import the edited csv file on the new server.

This feature request would eliminate the need to edit the CSV file each time.

@george1421 The problem is that the remote site needs to connect to the master. Even though you say it’s a small download, if for some reason the remote site is cutoff from the master, it can no longer do ANY imaging.

I really am trying to setup a remote location that has no technical people (classroom) and be able to perform imaging of the classroom desktops.

If for some reason the master node is not accessible, then there is no way to restore an image that is saved in the storage node. Thus the need to have both set as normal and their own masters.

If the storage node could have the local clients restore an image that is local without needing to contact the master node (like when you first boot to the pxe menu an unregistered machine and then you deploy an image)

Or, if the image replication between two masters could work like the Master to storage node. Or if there was a way to just export the image definition as part of the replication, the have the remote import or scan and import the image automatically.

If I use a storage node a the remote location, can I get the remote machines to pxe from the storage node and not from the main server. The link between the two locations is not that fast.

I have setup two FOG servers setup as normal. Site A is my MAIN office and Site B is the REMOTE.

At site B remote, all we do is deploy images, no captures. Site A MAIN does all the image capture.

I have been successful in marking an image for replication and that is copying, but I wanted to see if there is a way to have the image become available in the Remote location without having to do an import of the image.

Is there any way to scan for new images in the /images folder or have the image replicated and automatically become available.

Is this an issue due to having two different databases?