Latest FOG 0.33b

[Tom Elliott]

r1300 released.

Just fixes the login page language selection parts so they work appropriately again.

[Tom Elliott]

r1301 released.

Adds a lot of hooking elements to the GroupManagementPage. This is my latest project is to add hooking to all the of the pages. I’ve completed, where possible, the DashBoardPage, and added some to the HostManagementPage, but will work on one page at a time as it is rather time consuming. So GroupManagementPage isn’t 100% but I needed a break for a little bit. But basically all area’s down to alo on the service settings element of the group page are now hooking enabled. I’m sure it’s not a perfect system, but it gets the job done for now.

Updated the TomElliott.config.32/64 files to remove MTRR support. Updates the bzImage, bzImage32 files to reflect as well.

[BigMan99211]

So… What is hooking?

I’ve seen all these updates about it…

[Lee Rowlett]

this is obviously old and outdated but give you the idea:
[url]http://www.fogproject.org/wiki/index.php/Hook_System[/url]

you could potentially get fog to “look” how you want it to (within reason) without hard coding your changes and making changes to the core code of fog and for example when it’s time for a fog upgrade, it would be easier to implement your “hooks” back in and in “theory” wouldn’t have to do anything to do that.

[Junkhacker]

not just “look” how you want it to. act how you want it to as well. with a proper hooking system, plugins will be able to modify core functionality without being hard-coded into the files.

[Tom Elliott]

r1302 released.

Completes hooking elements, as I thought best to add, to GroupManagementPage. Starts hooking elements in ImageManagementPage. On the image add, it should also fix the double path display if you have multiple storage groups.

[lepretre]

hello

I have updated with the 1302 revision:
When I want to upload an image I get this error on the client and in the apache log:
[Wed March 12 10:46:46 2014] [error] [client 10.10.10.10] File does not exist: / var / www / fog / service / ipxe / fog

I had to copy the directory /tftpboot/fog to /var/www/fog/service/ipxe/
and the jobs start
Maybe my update

[BPSTravis]

Lepretre, did you update from .32 to .33?

We are advising to do a fresh install to make that jump. A lot of file locations changed between .32 and .33, actually, almost the entire file structure changed.

[Tom Elliott]

Some of the “upgrades” have slight issues if not a fresh install simply due to the FOG Configuration->FOG Settings area

Make sure the Kernel and Image file areas are set properly. They should just be set to bzImage and init.xz respectively. They used to be located in /tftpboot/fog/kernel/bzImage and /tftpboot/fog/images/init.xz

[lepretre]

I update from a revision of 0.33
Thank tom

my settings was not right after the update.
Now it’s ok

[Jaymes Driver]

My fresh ubuntu install of 0.33b has errors On revision 1302.

First, on the FOG Configuration page, Under TFTP Server settings the FOG_TFTP_PXE_KERNEL_DIR is pointed to the wrong folder.

it is pointing to /var/www/fog//fog/service/ipxe

it needs the extra “/fog” removed.

After doing so and pointing my ipxe stuff to the 32 bit version it still complains about not being able to find the correct file.

Should I be entering anything into the FOG_TFTP_PXE_CONFIG_DIR ? because it is currently pointed at “FOG_TFTP_PXE_CONFIG_DIR” which isn’t actually a directory

[Tom Elliott]

r1303 released.

Should fix the above issue.

Thanks for reporting.

[Jaymes Driver]

GOLDEN!!! now I have to figure out how to get DNSMasq working with the iPXE stuff!

[Tom Elliott]

There shouldn’t be any change.

Just the pointing from pxelinux.0 to undionly.kpxe

[warp]

Hi,
r1302 does not work :
Use of undefined constant WEB_ROOT - assumed ‘WEB_ROOT’ in /var/www/html/fog/commons/config.php on line 76

Could you stabilize something, we were there almost since r1200 and nothing works !
Eric

[warp]

I’m on CentOS 6.5 (64bits) with NAS Synology

[Jaymes Driver]

[quote=“Tom Elliott, post: 24058, member: 7271”]There shouldn’t be any change.

Just the pointing from pxelinux.0 to undionly.kpxe[/quote]

you know… I thought that too, but it just yells that it can’t find the boot file

either way… YOUR stuff [B]works[/B], let me play with the dnsmasq stuff to get it working.

[Jenks]

I’m currently on 31. How would I import my current images if I did a fresh install?

Thanks

[Tom Elliott]

r1304 and 1305 released.

Both are just more hooking elements. Part of the frequent releases is due to the weather in my area. I don’t want to lose my work while in the middle of changes. Hopefully you all understand.

HostManagementPage is the one receiving the Hooking elements. Currently all way through Inventory is now hooked. I still need to add the data to the hooking class, but that’s easy. First I need to make sure all is in place, like I did with the GroupManagementPage. Hopefully you all understand once again.

Thank you,

[warp]

The all this is to stabilize something overcharged as changing constantly as the PXE boot, which worked very well, for having changed?
You still need to know that the 0.33 version is expected for almost 2 years!