Latest FOG 0.33b
Updated TomElliott.config for 3.13.3.
Quick Image from iPXE is truely “Quick” as it no longer boots the init.gz or bzImage. It requires username and password as it “almost” always has, but it’s done solely with iPXE and php.
Installer create’s the relevant links to the init.gz, bzImage, and memtest rather than enlarging the download of the tar/svn code.
Updated init.gz so Inventory actually gets performed now. Sorry I had a typo and needed to correct for it.
r1212 and r1213 released.
r1212 simply verifies that the init.gz is the latest and greatest, should also fix inventory issue I was seeing, though no guarantee’s yet.
r1213 just updates the Default file for Redhat to have a valid Timeout value.
The Page itself should still work, but I have not converted it yet to ipxe, so I wouldn’t use it for now. I’d recommend just make the edits you may need, for now, directly in the boot.php if you can follow the flow of logic in there.
If you need help let me know. That’s going to be my project later today, and tomorrow after my biopsy (if I feel well enough to work on it)
If you want, I can maybe get some help on the PXE Settings, to convert it to the new formats, part of the FOGConfigurationPage.class.php?
is the FOG PXE Boot menu configuration page working yet? and if so, do advanced configuration options now need to be in ipxe format instead of the old pxelinux format?
This post is deleted!
YOU WOULD do that after I already updated my 0.33b once toady, I’ve been dying to test this! I wil have to wait until tomorrow when I am on site with my server again :)
This post is deleted!
iPXE is now implemented. Please test and see how much I broke.
Should auto-generate for your particular setup.
That is the new method.
I may create function to pull the information after user verification, but I’ve changed the FOG Settings to display the “Passwords” as Passwords, so prying eye’s don’t get your information.
what you can do - on the server (from terminal) log into mysql (mysql -u root fog (-pYOUR-PASSWORD-IF-YOU-SET-ONE)) and then run…
Select * FROM globalSettings WHERE settingKey = “FOG_STORAGENODE_MYSQLPASS”;
lepretre last edited by
To start I apologize for my English.
Fog is a very good job and thank you for this.
is it normal not to see the password FOG_STORAGENODE_MYSQLPASS in fog setting?
When i add a storage node is asking me for this paswword?
And just for the report:
When i go to the service management and I selected any service the graphics of the page disappears
sounds easy will let you know
The instruction set is much simpler now.
Just enable the plugins on the fog server.
Go to activate plugins.
Click on Location.
Go to installed plugins.
Click on Location.
Click install plugin.
Then click home. You’ll see the location Icon appear.
Click on the location icon and setup your location as you normally would.
Go to your hosts and set up your location.
I also added the element (which may have been there already) to Add all hosts within a group to a location as well.
It looks like a lot when you read it, but really it’s only seconds of work.
Tom you and lee rock I will give a go gotta get my server back up today now as you know I just moved. But I will let you know how I do with it. will there be updated instructions for any one new who may need this?
Just a little update on the Location Plugin.
I’m told it works properly. One of the largest, and I think influential changes, of Lee’s original Location Patch is that it doesn’t have to be tied to a specific node. In the original patch, you had to tie the location with a node. That node would then be the goto place for that particular system.
Under the new logic method, it’s a plugin. This means there’s two new tables created.
The first table within the schema change is the location table. This table is what holds the information on a specific location. The methodology of this is you name the location and, at the very least, assign a storage group to that location. You may also assign a specific node to the location. It will update the Storage Group to whichever group the node belongs in. I’m sure there’s a few kinks to iron out, but it seems to work from what I’ve been able to test.
The second table is locationAssoc. This is how (change from the patch method) it associates the location to a host. You will, most likely, need to assign the location to the host if you’ve enabled this plugin for all new registration’s after the location has been enabled.
What this allows?
The biggest difference is that this allows you to use Groupings AS WELL AS specific nodes for where you want the client to get it’s images. If this person moves around a lot between locations, you just make the change to that host and all will work fine. This makes for a centralized place to manage all of the hosts under your control.
I hope all will enjoy this being tied in as a “plugin” to the FOG system.
Many many thanks to Lee Rowlett who developed this originally and the assistance with getting many of the kinks ironed out and the details of how to go about getting this implemented. I admit I added new features that were unexpected initially, but I think it allows for more dynamics and adaptability within any organization.
r1208, r1209, and r1210 released.
r1208 just made correction to storage node identification. If there isn’t one set on location, it tells you not set.
r1209 fixed an issue in the host management page with location not being able to be adjusted.
r1210 Adds updating of inventory on all download tasks. This way, if you manually added a host, it will update the inventory with the systems information. Yay, better inventory management.
I will look into this I think it would be a great addition to be able to do this. it would avoid having to take an image before sysprepring or what not and it would just allow us to add to the image.
Not easily, though I’ve heard of people doing this kind of thing with partclone images, I’ve never done this myself. Theoretically it is possible with partclone, but I don’t know how to do it myself.
hey question for you tom is there any way to inject items into the image a addon-image if you will?