@AndrewG78 We need volunteers to write some documentation. For the multicasting problem, it may not be implemented into the API yet - I’m not sure.

Here are my example commands I promised:

FOG Server IP in these examples is 10.0.0.28 and the keys you see in here are my test keys on my test server at home. I left them in there so everyone can have a valid example. 1 is the FOG ID of the host in FOG, testhost1 is the hostname.

I think I want to push the bootstrap branch into the working branch and start getting that tested as well. I know the “GUI” side is totally different from the API side, but I’ve been improving and including new things that to the API side of things as well. As I progress I will likely add in container elements to help refine searches and what not, but I need documentation and I simply cannot do it alone unfortunately.

I’ve tried very hard to make the API as basic as possible to ensure it can get maximum exposure with relative simplicity.

EDIT:
Hmmm. I think that it would be nice to have some multicast deployment examples.
DOcs are missing this information.
I’m getting
{
“error”: “Invalid tasking type passed”
}
whilst I use proper ID=8 for multicast

It is my second post with workaround today ;)
Here is my working solution to execute deploy task for host with ID=2 from commandline.
So, Jenkins support is not a problem from now on.
I used curl with cookies file to achieve that.

This is possible if we directly interact with the database and certain specific fog web files.

We can query the DB to get the ID of the host using it’s name, and create a job in the DB. Then, we call the below link to do a WOL.http://x.x.x.x/fog/management/index.php?sub=wakeEmUp&mac=aa:bb:cc:dd:ee:ff

I’ve been planning on doing something like this at my house for automated testing purposes - and I’d be glad to work out the details with you here.