SOLVED Need some clarity on how 'Image Export/Import' is supposed to work please.

  • Server
    • FOG Version: 1.3.0-RC-14
    • OS: CentOS 7.2
    Client (none)
    • Service Version:
    • OS:

    This isn’t really a problem (unless it is) but I need some clarity on what is supposed to happen when I click ‘export images’.

    What I expected is a ‘Save As’ type box to pop up asking me where to save an image. Instead, I get a CSV. What I’m trying to do is independently extract an image, save it to a DropBox-like service from the San Francisco office and have an employee in Dublin pull the image down and import it into his storage node. We have a VPLS link which is only 20mb wide to Dublin (of which we get maybe 3-5mb for IT stuff). However they have 100mb down from the internet and we have over 100mb up. The goal is significantly faster image transfer.

    Regardless of whether this or something like it is possible, I want to say great job and thanks for RC14. The last time I visited Trunk was about 6+ months ago but it didn’t feel ready for prime time. I notice a massive improvement in RC14. Keep it up guys!

  • It exports the definitions (the pointers) as a image_export.csv (Comma Separated Value) text file.

    This file can be edited!

    If after exporting your complete list of images from one server, you want to then import just one of those images to another server you edit the original exported .csv . I use Microsoft Excel.

    Delete the lines for the images you are not interested in, then save that new .csv .

    On the destination server you then import the updated .csv. The contents of which are then merged into that server’s database.

    One of the nicer bits about the exported .csv is that the creation date and image size are saved and imported along with all the other pertinent fields. Do not worry about the image ID #, that is not saved or imported.

    Of course you will still need to copy the actual image files referenced by the image definition onto the destination server.

  • The image definitions are not the images themselves, the image definitions are metadata about the actual image - this data is tedious to manually recreate, thus the import/export feature was created for Image Management. The import/export feature only deals with the image definitions.

    Moving the actual image files is best done manually, please see the links I posted.

  • Understood. So it is supposed to be exporting the entire image and not just a CSV?

  • This article may interest you:

    If you have a Windows server share somewhere local, you can use the Samba instructions to move an image to that share.

    Of course I think the simplest is just plugging in a flash drive into the server, and copying the image. A simple Google search on mounting a flash drive gave me this, I’m sure there about a thousand other articles on the Internet about it though:

  • Also, import/export only deals with definitions, not the data itself.

  • Save as or just download is typically a setting in the browser, not something fog can control.