Posts made by theWizard

@Tom-Elliott
I’m using powershell with Invoke-WebRequest which is alias for curl

@Tom-Elliott said in API:

curl -H ‘fog-api-token: abcde’ -H ‘fog-user-token: fghij’ -X GET http://fogserver/fog/task/current

Thankyou perhaps i will have to wait as anything i try results in
The requested URL /fog/task/current was not found on this server.

@Tom-Elliott said in API:

fog-api-token

Hi Tom
Thanks you for the detailed response much appreciated, i feel rather stupid asking but i don’t suppose you have a couple of examples to follow do you ?
Say for instance if i wanted to list all active tasks or even add a snapin task.

Hi guys,

I’ve noticed in recent RC’s that an API is being implemented and wondered if there is any basic info on how to use it ?
I’ve searched google and the forums but can’t seem to find any info.

@Tom-Elliott
Hi Tom, just wanted to make you aware whatever changes were made recently in regards to additional mac addresses have fixed this issue now in 1.3.4-RC-2 thank you.

@Tom-Elliott Yep just checked again and no snapin tasks at all

@Tom-Elliott I updated to RC36 but same result, if i check the host the snapins are assigned to it and the image is deploying but there is no task for the snapins at all.

@george1421 Exactly yes no task to install the snapin is created.

@george1421
It’s not the fog client, when the imaging task fires after doing the auto reg the snapins don’t get launched at all. If i launched it as a standard deploy there would be an imaging task and snapins task in the queue but using auto reg even with group set to host template group the snapins task does not get created only the imaging task BUT the snapins are assigned to the host if you check in the gui.

@george1421
Yep you can select a group in quick reg ( drop down list ) which i set to the defaulttemplate group so expected the trigger to fire and launch the snapins too but unfortunately while everything else works and the image starts deploying the snapins don’t get launched, if i check the host the snapins are assigned to it but they never got launched
@Tom-Elliott I wonder if it would be simpler if possible at all just to add a drop down for snapins to the quick reg section ?

Is there any way of getting the snapins associated with the defaulttemplate host to launch when machines are deployed using quick reg auto pop ?
I set the group to defaulttemplate but the snapins never get launched, or @Developers is it possible to add a snapins selection to the auto pop section this would make imaging machines for us 100% automated at least on a per room basis.

@Wayne-Workman
I think i cracked it, after you mentioned DB connection issues i checked everything using workbench and found fogstorage user had no schema privaleges at all ! Not sure how they would dissapear but after adding back in fog seems to be picking other storagenodes correctly.
Thank you for the help and guidance.
This can be marked as no bug but maybe helpful for others to check if they encounter issues.

@Wayne-Workman

Completed on each one no errors at all each one returning RC-25 including server
Attached management page image

@Wayne-Workman
Yea i checked all nodes and the images are there as they should be, like i say if i set the queue on main server to 0 it will then use a single storagenode and not any others i.e queue of 5 on node A and fire a group of 20 to deploy only 5 will start and the other 15 will sit in the queue even tho Nodes B C D have 5 slots each too.

Yea i removed it from installed plugins.

@Wayne-Workman
Ok disabled location plugin and set main server queue to 1, meaning there is 1 slot on main server and 5 on each of the nodes ( 26 total )
Launched two machines to image and only one started, the other sits in the queue i assume because the result of
http://fogserver/fog/service/ipxe/boot.php?mac=28:f1:0e:15:34:e8

Is trying to use the server instead of any of the storage nodes.

@Wayne-Workman
There is because the machines that are used to build images on are set to the main server then when uploading/downloading those machines 1 slot is opened up and there is then no need to wait for replication ( we can be updating and uploading images at the same time as deploying machines with the image it will be replacing so our replication only runs once a day).
Location plugin aside if i open 1 slot on server then deploy 5 machines only 1 will start and others will be queued.

I can disable location plugin for testing purposes though no problem.

@Wayne-Workman
I do have it enabled but i dont set a location on any of the hosts and all the storagenodes are in the same group/location.

Server

• FOG Version: rc25
• OS: ubuntu 14

Client

• Service Version: 11.5
• OS: win7

Description

Hi guys, i have four storagenodes each with 5 slots available, main server slots set to 0 so gui/machine is always responsive.
Now i launched an imaging task for 16 machines earlier and while 5 went in and started the rest just sat in the queue as if no slots available but there is 15 more! Checking the machines using
http://fogserver/fog/service/ipxe/boot.php?mac=e0:69:95:dd:03:af

I can see that the ones i looked at that are in the queue are all waiting for the same storagenode instead of spreading out over all of them, is this normal ? I would not of thought so but not sure how to resolve.

@Tom-Elliott Attempted svn but have both available if needed.

@Wayne-Workman Ok followed your steps and checked again, same result for both logs and snapins. If i try re running the installer it fails on installing php-fpm ( i assume the old one ? ).