Latest Development FOG
-
What’s the drive?
-
SVN 2759 released.
With this comes a slight change to how the apache web server operates.
It will download the kernels and inits as needed rather than having them stored in the svn repo.
What’s bound to happen, some delay (sometimes seemingly a long time) during the Setting up and starting Apache Web Server phase. This delay is the download occurring.
What this means, for the kernel’s, it will always have the most current one on the published kernels, even if you use older SVN revisions back to 2759.
Hopefully you all understand.
-
Sounds great, always updated and only a minor delay on boot (which doesn’t happen very often).
Does it download updates/new kernels at regular intervals or only on boot.
Possibly once a week or once a month would be good to update them and put the older ones in a backup folder for roll back if needed.
-
Ummm, What?
It only installs/updates kernels/inits at install, not at boot.
If you want a “rotation” schedule I leave that on you to create the necessary scheduled tasks.
-
Tom,
Does the latest SVN work with the latest Ubuntu Server 14 ?
-
I don’t know what you mean.
-
Will Fog run/install on Ubuntu Server 14.04.1 LTS ?
-
There are examples in the Tutorials section ( [url]http://fogproject.org/forum/forums/tutorials.13/[/url] ).
-
[url]http://fogproject.org/wiki/index.php/Installation[/url]
To be clear. TFTP is a bit buggy in Ubuntu 14.xx but some have corrected this by editing a start up script.
[url]http://fogproject.org/wiki/index.php/Ubuntu_14.04[/url] (includes 14.04.1 & 14.10) -
[quote=“Ray Zuchowski, post: 39830, member: 24449”]Will Fog run/install on Ubuntu Server 14.04.1 LTS ?[/quote]
What Wolfbane Said!!!
But, Yes Fog will run on Ubuntu 14.04, 14.10 and Kubuntu 14.04, 14.10
We do not recommend using the latest version, stuff tends to get changed, or broken (such as moving the Apache root dir, and TFTP) If you find issues during installation, please document them and how you solve them so we can help the community.
I set up a 14.10 Kubuntu server this morning. The only issue I ran into is the common issue with ANY Ubuntu revision as of 12.04.4 and requiring users to specify their nameserver in resolv.conf so that you have internet connectivity.
-
[quote=“Ray Zuchowski, post: 39700, member: 24449”]Drk3,
It worked like a champ but when I go to register the PC, it comes back that the Hard Drive isn’t found. Tom… LOL you are needed here ![/quote]
Welcome to my world, that’s where I’m at with my Asus T100TA’s.
Try setting the Host Primary Disk to:
/dev/mmcblk0
I can’t pull inventory until I do this…
-
Can you try updating again?
-
SVN 2787 released.
With this release comes some sad, but hopefully better news. The sad is that We’ve decided to remove clamav from our package sources. This is two fold, we no longer build clamav as a part of the init’s, for the simple fact init’s don’t change too often, and therefor the packages tend to be outdated, especially when there’s a new release of clamav just far too frequently. We moved the clamav and made an effort to get clamav as a static binary set. This worked, but the binaries only worked with 64 bit, and inflated the size of the installer from (before inits and kernels where installed during installer) about 70MB to a whopping 200MB. It is because of the size of this and the fact that the files are far to vast in changes consistently, that keeping clamav on the installer or integrated in the init is just too much.
That all said, I am working on getting the [url]http://fogproject.org/wiki/index.php/Clamav[/url] wiki article updated with how to build and place the built binaries in the /opt/fog/clamav folder so that those of you who use clamav can still get it operational for your environments.
I know some are going to love this, and others are going to hate it. This is not to make anybody’s lives rougher or anything. It’s simply a practical (I think) decision that needed to happen probably long ago.
-
SVN 2806 released.
With this release comes FOG Snapin Replicator within the log viewer options as well as semi-realtime updating of these files. This means no more need to refresh to see the latest data. Also it adds the apache error/access logs right from the GUI.
Hopefully this helps when trying to diagnose a problem other than if the GUI breaks itself.
-
I agree with your removal of ClamAV. I think the FOG project’s focus should be towards the PXE and imaging side of things. Other tools should be up to each specific user to set up, especially since adding additional options to the boot menu has become so easy.
-
SVN 2845 Released.
With this comes Many changes to Log viewer. I’m sure there’s a few other things too, but this is the most significant.
LOG Viewer is a sort of realtime viewer (now) of your Logs. Multicast, Scheduler, Snapin Replicator, Image Replicator, Apache Error, and Apache Access logs. It updates everything every 10 seconds. The addition to this, now, is that it checks on all the master nodes, rather than the local GUI system. This means you can monitor what’s happening on remote nodes with out having to ssh or be at that node. There’s a Continue/Pause button in place which pauses the updating of the logs so you can copy and paste. Of course, any selection you make to the number of lines or which log you’re viewing, will re-enable the updating of the relevant log you’re looking at, so the pause button updates accordingly.
The Logs are separated with a simple disabled selector in the log file drop down that tells you which node in the format ------- <nodename> -------.
Also, the logs are hookable now, and you can add in your own logs as needed. To help you all out, I’ve created a log viewer hook with an example. The example I have is specific to the system log and checks for both ubuntu or redhat style messages. The file is commented at the top to help you understand what kind of permissions the file and folders will likely need.
While this doesn’t seem exciting, and to me it wasn’t that difficult of a change to add, I believe it’s uses are under-evaluated. Especially when it comes to us trying to help others on the forums.
With that all said, I wish all of you guys a Happy Holidays. I’d say the old “Merry Christmas” but seeing as I know not everybody celebrates this holiday, I’ll take the politically correct approach.
-
SVN 2866 released.
I forget all the changes but most of them stem from trial and error. There’s nothing of any major note beyond improving things and trying to ensure they all work. I know it feels like I’ve been leaving things alone, but really nobody’s reported any major issues thus far that I need to work on. I haven’t had an original new addition to add either now that log files are auto updating and can come from other nodes.
I know this is a rather boring post, but hey, HAPPY NEW YEAR!
-
SVN 2867 Released.
With this release finally comes OOP styled Schema updater. I can now, rather simply, use a single file who’s sole purpose is the check and establish the schema while using the templated page information. This means, should we finally figure out a nice method, themes would affect all pages of fog including schema, login/logout, client, and the regular management pages. No need to edit many separate files to have things operate.
With the schema updater, it will allow you to generate a backup file now from the click of a button. Obviously if this is the first install it won’t do anything and may cause failures, but it is a simpler means to getting a backup than expecting a terminal to get the file itself. I haven’t decided quite yet if I want to allow you to recover from an old database though as the intent of the schema updater is to update your database. So using an old version would still return you to the updater page to begin with.
Also, with this comes a few minor fixes to ensure things can still work with little/no interruption. If fixes the value setting values so it will only set a value if the service to adjust actually exists rather than trying to use functions that may not be present (for example when you’re first installing fog not all functions can exist because nothing really exists until the db is generated.) For the SSL stuff, it tries to use the defined value of your snapins directory (typically /opt/fog/snapins/ssl) but if the setting isn’t accessible it might try using //ssl which there aren’t permissions for and probably doesn’t exist. Rather than that, it will actually assume /opt/fog/snapins/ssl in the case that the called setting is blank or doesn’t exist.
-
SVN 2874 released.
With this release comes a minor (albeit those of you used to it now may dislike it) change to image size on server setting on the GUI. While this setting is useful, it’s also time consuming when you have many images. This changes adds an ability to enable or disable this field with a default of disabled. Also, it’s adds the starting components to maybe allow mass deletion from an elements respective management page.
This will mean I can remove the “group mass delete hosts” option we currently have.
-
SVN 2891 released.
With this release comes a minor change in the tftp files. The undionly/ipxe/snp, whatever have all been embedded to check for next server. If next server isn’t set, it checks if proxydhcp/next server is set. If that’s not true, it re-initializes the interface and attempts it’s checks again. This should work across the board for those of you with dnsmasq as a helper/main method to distribute the pxe chaining needed to operate.
Also comes a lot of work to add in Mass deletions, modified deletions, for form elements. Each of the pages: User, Host, Group, Image, Snapin, and Printer, follow a similar methodology of how Hosts can join a group from the Host search/list portion. There’s a series of checkboxes. When paired with the delete button, it will allow you to mass remove those elements after your confirmation of course. I’ve also added to the edit portions, where relevant (not fully done yet) similar methodologies to the multi-add portions to allow you to more easily remove elements as well.
Hopefully this makes FOG GUI a little bit more intuitive and easier to work with.
