Posts made by Gilou

Hi there,

Congratulations Tom on releasing Fog 1.2.0, now is the time for me to test it, and to upgrade our french training for it as well. As I was testing, I came across something annoying: changing the IP of FOG (having all on one serv).
a) In the configuration settings, there is no “expand all” possibility, so unless you browse the source, it’s quite painful to actually look for a given value, and to use any search/replace functionnality. Expand all would fix that, but there are other ways…

That’s a lot of changes, I’ve referenced so far:
FOG_WOL_HOST
FOG_TFTP_HOST
FOG_WEB_HOST
Storage Node IP

But that’s OK, that’s how it’s intended to be. However, when booting on iPXE, my hosts couldn’t go through… which leads to :
b) default.ipxe is hard coded at install ?
Because the IP is written in default.ipxe… So I said to myself (tuduum.), well, that might have been done in the “Boot PXE Menu”, but updating it from there didn’t regenerate default.ipxe.
Bug ? Feature ? Missed option? You tell me

Be prepared for more feedback.
Btw: I love the grub exit… It fixes most of the f*cked up Dell BIOSes that refuse to boot on disk once PXE boots… I love the resizable partitions, and I love partclone being used (I know, I’m late for the party, but well ;))

Cheers

Gilou

I really need to get testing… The exit issue is a problem on almost all the new Dell boxes… Hopefully soon!
Way to go Tom, it’s great to see things moving.

Does it work when you reboot and force it to boot on the hard drive from the bios/boot menu?

I have a lot of new Dell machines that won’t boot off the disk if they started using PXE, and PXE tells them to use the disk… There’s some doc about it, but it’s annoying as hell

Something like this ?
[CODE]mkdir /backup ; mount -o username=login //2008R2SERVER/bakcupshare /backup ; rsync -a /images/ /backup/images [/CODE]

that’s possible… but please let’s focus on 0.33 working before adding stuff
It could be done by using syslinux to boot the init.gz + kernel of FOG, and modifying a bit its code to tell it to look for a file on the disk rather than on a server… interesting…

definately, that’s the easy setup if you can tell dhcp to just point to a different TFTP server for the PXE part.

And for those looking to avoid compiling it, and need a 32 bits init.gz , I made one: [url]https://gilouweb.com/bordel/init_fog_i686.xz[/url] based on buildroot of r1284.

Is the 64 bits init/buildroot & kernel compatible with fog 0.32 (that is without iPXE, and with the “old” task informations) ?

Also, could you provide some details about how you get from buildroot to the init.gz ? It’s not trivial to get buildroot by itself, but I’ve seen that using your tarball, there are FOG patches that were already applied in partimage… And well, a single error in the buildroot compilation can get quite frustrating

well, without LVM, no, if you have a separate dir… it’s gonna get annoying for NFS… and using a storage node is probably not a good idea.
But copying data over to the LV, then umounting /images, remounting the LV on /images, then lvextending, that’s less than a minute of downtime if done properly…

Use LVM then… set up LVM on the new disk, add a LV called images, move everything from /images in there, and then mount it in /images… If you don’t have a specific partition for /images you won’t be able to extend it over that, but you’ll have some room to make it happen (like reclaim the space, create a partition on the first hdd, and lvextend on it).

The registry hack works fine for 7, as far as I know. But it won’t help for sid/AD integration obviously

It could also be based on the info on the date of the file/directory itself, rather than stored in the db!

partimage does not support ext4, thus fog 0.32 can’t image an ext4 partition. Full disk, or nothing. Or roll back to ext3 !
Or try out fog 0.33

Debian 7, Ubuntu Server 12.04, and soon, CentOS 6.5. But all my production is Debian-based.

If you’re router is already doing the DHCP part, you need to be able to tell it where to find the TFTP server, so that will depend on the brand and OS on the router.

NFS doesn’t do any auth by itself, it can use kerberos, but doesn’t have a concept of “logging in”. Hence the use of FTP in the first place to “move” the image. NFS can restrict the IPs connecting to/accessing it though, but that’s all you get. And I wouldn’t use kerberos just for FOG

updog: I agree, but that approach would be Linux centric… Though it’s a not so ugly way to think of snap-ins for linux hosts

If the server doesn’t boot anymore, that won’t be easy

Ah, I read a little bit fast, the router provides DHCP… It boils down to knowing if the router has an option to set the TFTP/PXE settings in it (option 66/67). If not, just use the linux as dhcp instead of the router, it will work fine.

Why do you want to have a 2008 server? FOG / Linux can do DHCP just fine, and that’s the easiest way to set it up when you install FOG