Latest FOG 0.33b
-
Tom this sounds great, appreciate what you are achieving and doing for us FOG folk!!
-
Thanks Nathan for the support.
Also,
I wanted to try something as a test with this, but I am stuck testing within VM modes at work. Maybe I can get the community to test this part.
I’ve added, I think, recognition within the ClientServiceManager to look for additional MAC’s. Theoretically this should allow you to use the FOG Client even on wireless clients. I have NOT…I repeat…have NOT added wireless device recognition/adding for wireless MACs into the init.gz file. My worry with doing such a thing is make a kernel that’s just too large for a simple imaging solution. If I were to add Wireless adding of mac’s it could, potentially, add about 30-50 mb to the size of the kernel, not to mention the wireless tools needing to be built into the init.gz itself.
That said, however, I think I might be able to get the FOG Service hostregister utility to do this work for me. It isn’t added yet, but I with the addition of the hostname checking, I think I can have it, now, pull the information from the system and add it to the correct areas.
-
r988 out.
I doubt it’s fully complete, but it looks like I can finally view snapin jobs. I can’t tell if they’re actually working yet, but I’m almost certain I’m getting close.
-
Tom Elliot, i think i love you. :rolleyes:
Good to see the progress
-
While I appreciate the the sentiment there @tuxmania, I think my wife would say otherwise
r991 is out.
Just add’s a few fixes to things I noticed where problems.
-
r992 is out. Finally working towards refining methods. All service files now use, seemingly proper as well, the base.inc.php.
-
Finally going to get time to give 0.33b a try. Big thanks for ALL the hard work Tom.
[SIZE=6][B][FONT=Helvetica Neue][COLOR=#000000][SIZE=24px]“A Giant among men”[/SIZE][/COLOR][/FONT][/B][/SIZE] -
First of all, Tom it is great to see that they finally have someone like you working on the next version of fog, YOU ARE A MACHINE!!!
Anyway a quick question for you,
Is there any timeline of any kind that you may have on getting 0.33b to work on uefi bios devices?
This is the most crucial part of Fog that i need to work, as I am in the same boat as you with working at a school district and am looking at getting 100’s of new tablets (Dell Latitude 10) by the end of the school year. Getting Fog to work with these new devices would be a great plus as I ABSOLUTELY HATE USING WDS. So no pressure of any kind ;). -
Though I know there’s plenty more work to get the GUI at 100%, however I think I’ll start playing with partclone and see if I can get any status on this for everybody.
-
Awesome, I would like to seem some alternatives!
I would even like to see using the cloning portion as a “add-on” so that other can choose the derivative they want to go with. I’ve seen some people talking about using the Bittorrent to transfer, this would be a BAD idea for my environment, we have HEAVY restrictions against the torrents, but It would be nice to have an alternative for those that aren’t locked down as heavily as I.
Keep up the good work Tom, so far my 0.33b server is working beautifully, I should probably update it though, I’m still on 98something
! -
Torrent is one method I was suggesting… If the replication has an option to turn off so you can implement your own then those of us willing to build what works best will have an advantage.
What method would be best in your environment?
-
Hi Tom, I’ve been following your progress with 0.33b and finally decided to implement your revision onto a fresh ubuntu install. I have hit a snag with the auto register. Despite changing FOG_QUICKREG_AUTOPOP to 1, the client machine wont image after quick registration. Is there a config file somewhere that I can manipulate?
-
When changing the FOG_QUICKREG_AUTOPROP to 1, are you doing it from the <fogwebdir>/commons/config.php or are you doing it from the FOG GUI.
-
This post is deleted! -
I added a define for FOG_QUICKREG_AUTOPOP in the config file and set the default value to 1. Still no dice. It registers the host no problem, I can also add a task to deploy the image, which works fine, but I was hoping to bypass the use of the webui to set tasks, and utilise the quick reg/image feature.
-
Your first method, adjusting through the web GUI is correct.
Can you provide a bit of your httpd/apache2 error log. Maybe it’s telling you what the issue is.
I only ask because, I know this works for 0.33, but am nearly certain it does for 0.32 as well. It sounds like some other issue is occuring. Maybe the IMAGE_ID Field needs to be set to the proper ID you want the quick register systems to image with?
-
Tom, Could you point me in the right direction on what I need to change in [b]hosts.upload.include.php[/b] to allow it to import a secondary MAC address. I’ve got nearly 900 laptops to import and don’t want to be adding these manually.
Thanks
Mike
-
Michael,
I don’t think there’s an easy way to go about it, besides manually, though that doesn’t mean it couldn’t happen.
I think you would want to do the INNER JOIN Fields. Are you comfortable performing CSV Exports using SQL Code?
I think the two tables you’re looking at here would be: hosts and hostMAC tables.
The way you’d perform the query would be:
[code]SELECT * FROM hosts INNER JOIN hostMAC ON (hostID=hmHostID)[/code]Getting it into the format you need should be similar. All, I’d imagine, you should need would be:
hostName, hostMAC, hmMAC, imageID, and possibly Description, though you may also want to get he hostID so hostMAC (Primary) and hmMAC (additional) line up properly.
-
[quote=“Tom Elliott, post: 19503, member: 7271”]Your first method, adjusting through the web GUI is correct.
Can you provide a bit of your httpd/apache2 error log. Maybe it’s telling you what the issue is.
I only ask because, I know this works for 0.33, but am nearly certain it does for 0.32 as well. It sounds like some other issue is occuring. Maybe the IMAGE_ID Field needs to be set to the proper ID you want the quick register systems to image with?[/quote]
Hi tom, thanks for sending me to the apache logs, I found the following errors:
[CODE][Thu Oct 31 13:08:54 2013] [notice] Apache/2.2.22 (Ubuntu) PHP/5.3.10-1ubuntu3.8 with Suhosin-Patch configured – resuming normal operations
[Thu Oct 31 13:17:56 2013] [error] [client 192.168.1.20] PHP Fatal error: Call to a member function createImagePackage() on a non-object in /var/www/fog/service/auto.register.php on line 236
[Thu Oct 31 14:20:11 2013] [error] [client 192.168.1.1] File does not exist: /var/www/favicon.ico
[Thu Oct 31 14:39:32 2013] [error] [client 192.168.1.20] PHP Fatal error: Call to undefined function checkIn() in /var/www/fog/service/mc_checkin.php on line 43
[/CODE]I have removed and re-installed fog 0.32 and 0.33b multiple times now with no success on repairing the issue, where should I go form here? I looked at the code on those lines and it is all mumbo jumbo to me.
-
My best guess is that you still need to set your OS_IMAGE_ID needs to be set still, though I’m not 100% sure.
In 0.33, the line should be:
[php]if( $Host->createImagePackage(1,“AutoRegTask”,true,true,true) )[/php]Basically this references the class file function createImagePackage
This doesn’t need huge explaining, but this is where the image task gets created.
The 1 means deploy task, the “AutoRegTask” just sets the name, and the true, true, true, means, set shutdown after, set debug, and set deploy snapins.
In 0.32 the line should be:
[php]if( createImagePackage($conn, $imageMember, “”, $tmp, false ) )[/php]
This, again, means it’s creating the image package.
The $conn just sends the database information, $imageMember is sending the host information, “” is just setting the task name (as nothing), the $tmp is sending the reason, and the false is just setting the debug information.
I have the sneaky, albeit blind, suspision you still haven’t set the IMAGE_ID that you want this associated with. In 0.33b, you’ll get the non-object error thrown because it can’t send back the class information, so the object doesn’t exist yet. I don’t know which error’s you’re getting with 0.32 as it seems to be the error you provided is from a 0.33b install.
