| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
skip including client in the listing if command never run or it did not finished
yet.
|
|
|
|
| |
Provide a timestamp that tells when the command output from client was received.
|
|
|
|
|
| |
Add "cmd" field to json that provides the original command string, so it is
provided with the output and the return code.
|
|
|
|
| |
Add retcode field to specify return code of shell invocation.
|
|
|
|
| |
Free dbi result after use in og_delete_computer_folder().
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add URI to allow a POST request to move clients to a new room/folder.
Request POST /client/move:
{
"clients": [
"192.168.56.11"
],
"room": 10,
"folder_id": 0,
}
If folder_id is zero then that means computer is not stored in a folder.
|
|
|
|
|
|
|
| |
Exclude centerid of the center we update from the search of
centers with the same name.
Report when other center have the same name as the one in the
payload of the update request.
|
|
|
|
|
| |
Check if the requested new MAC exists in another client and refuse
update request if that's the case.
|
|
|
|
| |
Free dbi result after use in og_cmd_post_client_update().
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add URI to allow a GET request to obtain info about a center (name, id
and comment of the center as of now).
To use this uri, simply send a GET request with a json containing the id
of the center whose info needs to be consulted:
curl -X GET -H "Authorization: $API_KEY" http://127.0.0.1:8888/center/info -d '{"id":1}'
based on work from Javier Hernandez.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add POST cache/delete request to request deletion of images in
the client's cache.
Resquest payload structure:
{
'clients': ['10.141.10.21', '10.141.10.22']
'images': ['windows.img', 'linux.img']
}
The clients listed in the 'clients' field will receive a
cache/delete POST request with the 'clients' field removed and
only containing 'images' from the payload received by the server.
Each client will try to delete as many images as available in
their cache from the list of files in 'images'.
The clients will give response with the contents of the cache so
the server can update the database.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add GET cache/list request to obtain information about the client's
cache.
Resquest payload structure:
{
'clients': ['10.141.10.21', '10.141.10.22']
}
Response's structure:
{
'clients': [
{
'ip': '10.141.10.21',
'cache_size': 2894572304857,
'images': [
{name:'img1', size: 87283902343, checksum: '5d4dcc677bc19f40a647d0002f4ade90'},
{name:'img2', size: 894572304857, checksum: '3eb22f888f88a55ad954f55644e1192e'}
]
},
{
'ip': '10.141.10.22',
'cache_size': 49872839023434,
'images': [
{name:'img2', size: 894572304857, checksum: '3eb22f888f88a55ad954f55644e1192e'}
]
}
]
}
Both 'cache_size' and the values in 'image_sizes' are provided
as bytes.
If a client has no cache partition the payload will include it as:
...
{
'ip': '10.141.10.22',
'cache_size': 0,
'images': []
}
...
|
|
|
|
|
|
|
|
| |
GET /session only supports for one single client IP address, extend
it to remove this artificial limit.
Add "clients" json attribute which is an alias of the existing "client"
for consistency with other existing endpoints.
|
|
|
|
|
|
|
|
|
|
| |
When og_cmd_post_center_delete is invoked by the REST API the
images that contain the same id as the center being deleted are
also deleted.
Move the image deletion functionality into its own function called
og_delete_image to prevent code duplication as it is now required
in og_cmd_post_center_delete and og_cmd_delete_image.
|
|
|
|
| |
Remove .full.sum file too when user requests to remove an image.
|
|
|
|
|
|
| |
Fix the code tha checked the existence of other rooms with the same
name in the center but only check the rooms other than the one being
updated.
|
|
|
|
|
|
| |
Add support to update computer folder name
Add support to update room folder name
|
|
|
|
|
|
|
|
| |
Add uri to allow the change of a room's properties, such as 'name',
'gateway' or 'netmask'
Reject update if new name is already being used by any room of the
center where the room is located
|
|
|
|
|
|
|
|
| |
Add uri to allow the change of a center's properties such as 'name' or
'comment'
Refuse to update center's name if that name is already in use by another
center. This is because a center should not share name with another one.
|
|
|
|
|
|
|
|
| |
Reply with an error if user tries to create a client with a mac that is
already owned by another client
Write to syslog info about the client that owns the mac: client's name,
ip, mac address and room
|
|
|
|
|
|
|
|
| |
Change the name of variable 'group', in og_group struct, to 'folder_id'.
Change payload field to 'folder_id'
These changes are to make code easier to understand.
|
|
|
|
| |
Add folder/add and folder/delete, otherwise logging shows "unknown"
|
|
|
|
|
|
| |
Add support for adding clients that are inside a folder.
Add new folder_id field, if zero it means computer is not in a folder.
|
|
|
|
|
|
|
|
|
|
| |
Add support for deleting folders containing rooms. Delete rooms that are
in folder.
Computers inside rooms are automatically deleted in cascade when room is
deleted (implemented in sql)
Add support for deleting folders containing clients. Delete clients that are
in folder.
|
|
|
|
| |
Add support for adding computer folders and room folders.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
marker tells us if this folder to group rooms or computers.
this is a woraround because the database has two tables to store room and
computer folders, there is no unique id.
the tables cannot be merged yet because of the legacy web console, to overcome
this limitation, add a marker that provides a unique id to differentiate room
and computer folder.
this assumes only 65535 room folders are possible because the marker is
0x000010000 (65536)
|
|
|
|
|
| |
Allow to specify .boot field and call set_client_mode() to update
the boot mode.
|
|
|
|
|
|
| |
Update it so it shows in syslog, instead of unknown:
Dec 19 18:31:18 ogserver ogserver[1133]: 127.0.0.1:36538 POST /unknown clients=150.128.34.25
|
|
|
|
|
|
| |
legacy web console uses this REST API to refresh an existing image.
Relax check not to break things.
|
|
|
|
| |
add explicit API to update an image
|
|
|
|
|
|
|
|
|
| |
do not use description field to decide if this is a new image or an update.
add og_dbi_get_image() to check if the image exists. If it is not found, then
add new image entry to database.
update og_dbi_add_image() to update the image.id field.
|
|
|
|
| |
add logging to report failure to remove entry.
|
|
|
|
|
| |
execlp() should not ever fail, but if it ever happens, return -1 instead of
exitting this daemon.
|
|
|
|
| |
this file might be in a different repository, this is best effort.
|
|
|
|
|
|
| |
Use permissions and last update from client.
update src/schema.c to add a new database version.
|
|
|
|
| |
add .description field to json.
|
|
|
|
|
|
|
| |
Add GET /room/info to obtain room information, this includes the name,
gateway and netmask.
curl -X GET -H "Authorization: $API_KEY" http://127.0.0.1:8888/room/info -d '{ "id" : 1 }
|
|
|
|
|
|
| |
Use computer.maintenance instead of computer.name.
Fixes: af47a082adb1 ("#1004 Add GET /client/info HTTP REST method")
|
|
|
|
|
|
|
|
|
|
| |
Add POST repository/update request to update repository. Repository is
identified by its id, that is provided in the payload.
This can be tested with curl like:
curl -X POST -H "Authorization: $API_KEY"
http://127.0.0.1:8888/repository/update -d '{ "repo_id" : 16, "center" :
3, "name": "newName", "ip":"127.0.0.1" }'
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Skip logging for the following REST API invocations:
- GET /scopes
- GET /clients
- POST /clients (for legacy web console only)
The web front-end generated very frequent requests for this.
Update logging format to:
127.0.0.1:54637 POST /wol clients=192.168.2.130
to include client IP address.
|
|
|
|
|
|
|
|
|
|
| |
Valgrind reports a memleak because og_cmd_wol() overrides params->ips_array,
then it releases params->ips_array but og_cmd_free() already does this.
Use a new_params structure to store the IPs that has been filtered through the
database query and check that buffer overrun does not happen.
Fixes: e4cb91b5f660 ("#990 wol: migrate mac and netmask query to ogServer")
|
|
|
|
|
| |
Set it to 1, ogCP and ogCLI never use this, and this REST API is never
used by the old web console.
|
|
|
|
| |
Remove unused code in this request and do not assume center id.
|
|
|
|
|
| |
Add POST client/update request to update client, this is identified by its ip
address, with the data provided in the payload.
|
|
|
|
|
|
| |
ogserver will check that the user provided a valid bootmode. It will go
through the list of all available boot modes and check that the bootmode
provided by the user is in said list; otherwise, it will not set it.
|
|
|
|
|
|
| |
og_cmd_get_modes() now uses a helper function that returns a list of all boot
modes, this is for a new API REST validate that boot mode is set to something
that exists in a follow up patch.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Every time a delete operation is performed it needs to be checked that a row
has been deleted. If no rows are deleted, then ogserver reports an error.
Previous to this change, it only checks that the connection to db
was succesful. For example, previously, if a user deletes a client that did
not exist, ogserver responds with no errors.
After this change, it responds with an error.
This error check has been implemented when deleting:
- A client
- An image
- A center
- A repo
- A room
- A server
|
|
|
|
|
| |
/clients says bad request for unsupported method, use correct error
report.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
POST /repository/add checks validity of the repository ip address
specified in the request payload.
/repository/add can optionally receive a center id parameter inside its
request payload. For backward compatibility, the default center id (1)
is used if no center is received inside the request payload.
POST /repository/add returns a JSON response payload containing relevant
fields from the inserted repository.
$ curl -D-
\ -X POST
\ -H "Authorization: a0e9ab768cbe93dab5b1998e952bcdb7"
\ --json '{"name": "helloworld", "ip": "192.168.21.21a", "center": 2}'
\ localhost:8888/repository/add
HTTP/1.1 400 Bad Request
Content-Length: 0
$ curl -D-
\ -X POST
\ -H "Authorization: a0e9ab768cbe93dab5b1998e952bcdb7"
\ --json '{"name": "helloworld", "ip": "192.168.21.21a", "center": 2}'
\ localhost:8888/repository/add
HTTP/1.1 200 OK
Content-Length: 54
{"id": 7, "ip": "192.168.21.21", "name": "helloworld"}
|
|
|
|
|
|
|
|
|
|
| |
Move struct og_repository to dbi.h and use field max length for name and
ip.
Use og_json_parse_string_copy instead of og_json_parse_string to check
maximum length against the request payload.
Fixes: 86ccc3c2e8377623 ("#915 Add POST /repository/add")
|