r956 is out.
With this comes Timers for Scheduled tasks, Both delayed and cron-style scheduled tasks appear to work properly. The mobile site appears to work properly now. You can now remove scheduled tasks and view what’s listed. It displays all scheduled tasks, whether active or not, but it displays the active status and the Type of job it’s set for.
Hope you all enjoy.
I think I actually got it through more rigorous checking with my test system. It actually looks to create the task as active in wait for the job to start.
Scheduled tasks, I hope, work on an actual basis now.
I’ve, still, only tested the cron style as that was the most difficult to figure out for me. Maybe over the week I’ll try to fix and test single/delayed.
Well,
I’ve been spending a lot of my weekend working on the whole scheduled tasks thing you were probably already aware of. Then I started working on the mobile side. I am glad to say that it seems to be working. You can now login, create image tasks (download), and remove tasks using the mobile version of the program.
I’ve also, so far, got it where it can actually perform scheduled tasks, now I’m looking into getting it to remove the scheduled tasks properly. It does remove them, but maintains the DB records for some reason. You know that’s simple. My next feat will be to tackle getting the delayed/single deployment working from the pages themselves. Also the same with some quirkiness on the scheduled task stuff.
I think that already exists. Under, the directory mobile. Instead of going to /fog, try /fog/mobile
r949 is out. I’ve been able to test and watch tasks be created on a schedule. They never cleanup though, probably because I don’t have a real thing to test it with. The only thing I could watch be created on a schedule goes to the active tasks, and because the task doesn’t truly run the job doesn’t cleanup from active. It’s only cron jobs that I could test. I’m looking at some issues with entry so I couldn’t figure out how to do the single/delayed start.
Thank you,
I’m about to release another revision due to Scheduled tasks. Again it’s only for 0.33, but it seems to, finally, be working properly. *'s work just like crontab. There’s a couple other issues in scheduling the task that’s a little off, but that’s validation problems and not scheduling problems.
I’ve only tested using false values for everything and watching log files. Real-world I haven’t a clue, but at least I can say with some assurance it appears to be working as expected. I haven’t figure out the Single Scheduled task entry process yet and haven’t tested it because of this reason. So to be blatant, only cron style tasks seem to be working for now.
Hopefully this helps.
I am adding the caveat to this, as reading a little further, you’re stating that this bug was with 0.32 and I have been updating 0.33. I still don’t know if the jobs are working properly, but can see what’s going on in 0.32. Maybe I’ll have another aha moment when looking into this for you all.
I’m not familiar with scheduled tasks too much beyond crontab specified, so if my results aren’t working fully yet, I’m very sorry.
r948 is out. It should have everything, I imagine, needed for Scheduled Tasks to work. On the Tasks Management Page, comes the scheduled tasks list as well. It displays the type of task, and provides the needed items to delete the task.
r947 was out, please don’t try was testing something and forgot to remove those tests.
r948 is out and should have scheduled tasks back though I don’t really know for sure. Please test.
I’ve since, I think, fixed this issue and will post the updates. I’ve also added the tools to start viewing the scheduled jobs as nothing was in place for this. When I have time tomorrow, I’ll try to upload my changes. Hope all is well. First file that needed changing is the one I already uploaded once. It didn’t work through my testing, but I narrowed how to get it sort of working, I think. Again, I have nothing much I can truly test on, but at least I can see the jobs trying to run.
See,
Jaymes et al.,
While I agree with the security aspect of it, with this being open as it is and the possibility of chainloading for gpxe and ipxe, I think having an openly (internet) accessible fog server is kind of a good idea. It would allow, potentially, a cloud based site for known working images for upload/download points, and relieve the strain of some sites requiring multiple fog servers for their setups. Point thru http/ftp dns names and have them image.
Just my two cents I guess.
r946 should now have scheduled tasks back. Hopefully this helps, but please test. I don’t know what Imageable.interface.php was supposed to have so I haven’t a clue as to where to begin coding this if it was truly ever needed in the first place.
I think I found the problem.
The file in /opt/fog/service/FOGTaskScheduler/ is referencing the class files Host.class.php, Task.class.php, etc… as WEB_ROOT . /management/lib/<classfilename> Which is why it’s not finding anything. One of the files, Imageable.interface.php, doesn’t exist and never has, though the file is still referencing it. I may have just found a fix, but will test with a simple inserted job to see that it recognizes and attempts to run the job. Man, maybe this is much easier than I thought it would be.
I don’t know about that, but I might add a crontab for the root user that basically runs the php file every minute. This way the DB gets checked, assuming this worked at some point in time. That’s my guess at least.
r945, had error were it thought there was a duplicate key, it’s fixed now.
[LEFT]r944 released. Schema now inserts Windows 8 associations.[/LEFT]
You can use SVN, or download the tarball’s I’ve already created, or let sourceforge create them for you.
First,
Tarball from Sourceforge is at:
[url]http://sourceforge.net/p/freeghost/code/HEAD/tarball?path=/trunk[/url] It will download as a zip file.
Tarball from my site is at:
[url]https://mastacontrola.com/fog_0.33b.tar.bz2[/url]
To checkout through svn perform:
svn co [url]https://svn.code.sf.net/p/freeghost/code/trunk[/url] fog_0.33b
Then cd into fog_0.33b directory created and perform normal install procedures.
From what I could tell looking into this, it’s not using crontab or at to create scheduled jobs, but rather using the scheduletask service to check the database for specifics. I’ll try to look into it this weekend, but no gaurantees.
Does this mean it worked? It looks like it’s doing a DD clone.