• Hi

    I can’t install all the packages needed for FOG, because some repo are not allowed by proxy at work.

    The problem is that centos repo system use random host with different IP address and some are not allowed.

    My goal is to install Fog on a different VM (eg : at home with the same OS setup) and to get the packages out from it and install them on the orther VM at work.

    I did not find another way to make it to work.

    For the moment we have FOG on a different machine (not virtualized, and i know why now, because you can easily swap network cable on a dedicated nekwork without proxy). I really want to install Fog in a VM like the rest of our machines.

    Can someone help me to achieve this ?

    I have no clue how the Fog installer work and where it stores packages during installation ?

    A part of that, Fog is a really nice tool i like to use…


  • @fall711 said in FOG offline installation:

    The problem is that centos repo system use random host with different IP address and some are not allowed.

    You can easily specify exactly what mirror you want to use by commenting out the mirrorlist directive inside of all the /etc/yum.repos.d/*.repo files and instead using the baseurl directive. Here’s a writeup on it, there are many others online too:

    Just pick a mirror nearby you, and explicitly define that. You will need to do the same for the remi repository as well:

    There is never a problem that cannot be solved.

  • Moderator

    @fall711 If your company is restricting access to the internet, even via a proxy server AND you want to use FOG, you need to setup FOG in a development environment and then move it to your production workload.

    Since you use vmware virtualization, you can setup FOG on a vmware Workstation computer that has full access to the internet. Once FOG is installed then you can remove full internet access. FOG will run fine internally with no internet access.

    Once fog is loaded, just export the OVA from VMWare workstation and then import the OVA into your VMWare production environment.

    Now for the second bit about storage space. For your development install. You could create a small disk for your FOG server, like 25GB in size. Then once the server is in your production environment create 2 new vmdk files, partition them as standard partitions, then mount them onto your fog server over /images and /opt/fog/snapins. The standard partitions will allow you to grow the disks and partitions in the future as demand increases for storage space.

  • VMware.

    So you suggest i use the same VM technology on a different computer, configure FOG as my needs and then transfer the OS disk to my Work datacenter ?

    Is this possible when you use LVM volumes ?

    The second option is to have a local depot, but that’s too much…

  • Moderator

    What is your virtualization technology do you use at work?

    You do have an interesting issue since it is common practice for linux updater to use what ever repository source is available for updates. Probably using an external vm host and then moving that to your internal host server is the easiest. If you create 2 vmdks one of the OS and one for the images (good choice anyway) you can keep the size down while transporting.