summaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
...
* rest: allow the same center name in center updateAlejandro Sirgo Rica2024-06-121-6/+8
| | | | | | | 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.
* rest: validate mac in client/updateAlejandro Sirgo Rica2024-06-121-1/+22
| | | | | Check if the requested new MAC exists in another client and refuse update request if that's the case.
* rest: fix memory leak in client/updateAlejandro Sirgo Rica2024-06-121-0/+3
| | | | Free dbi result after use in og_cmd_post_client_update().
* rest: Add /center/infoOpenGnSys Support Team2024-06-124-0/+115
| | | | | | | | | | | | 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.
* client: update cache after image/restorev1.2.5-11Alejandro Sirgo Rica2024-05-301-0/+2
| | | | | | | | | | | | | | | | | | | | Update the database with the new cache contents sent by the client after an image/restore operation. Resquest response structure: { ... 'cache': [ {'name': 'windows.img', 'size': 2432370213, checksum: '5d4dcc677bc19f40a647d0002f4ade90'}, {'name': 'linux.img', 'size': 243234534213, checksum: '3eb22f888f88a55ad954f55644e1192e'} ] ... } Parse the contents of the 'cache' field to update the data of the client's cache in the database. This is one of the required changes the make cache/list coherent and prevent cache desync between the server and clients.
* rest: add cache/deleteAlejandro Sirgo Rica2024-05-303-0/+109
| | | | | | | | | | | | | | | | | | | 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.
* rest: add cache/listAlejandro Sirgo Rica2024-05-302-0/+162
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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': [] } ...
* client: store image cache data in databaseAlejandro Sirgo Rica2024-05-303-7/+141
| | | | | | | | | | | | | | | | | | | | | | Parse the 'cache' field of the refresh payload sent by the clients. Cache field structure in the payload: { ... 'cache': [ {'name': 'windows.img', 'size': 2432370213, checksum: '5d4dcc677bc19f40a647d0002f4ade90'}, {'name': 'linux.img', 'size': 243234534213, checksum: '3eb22f888f88a55ad954f55644e1192e'}, ] ... } Store that data in the 'cache' table of the database so it can be obtained later on. The table contains the following fields: - clientid: the numeric identifier of the client. - imagename: name of the image in cache. - size: size in bytes of the image in cache. - checksum: checksum of the image in cache.
* src: replace old function to update image informationOpenGnSys Support Team2024-05-293-112/+91
| | | | replace old legacy code, no functional changes are intended.
* schema: add cache table to store image files in clientOpenGnSys Support Team2024-05-291-0/+36
| | | | | Add a new table to store the image file that are stores in the client cache. Use bigint to store file size in bytes.
* rest: extend GET /session to support for more than one clientv1.2.5-10OpenGnSys Support Team2024-05-141-39/+53
| | | | | | | | 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.
* rest: delete images that belong to deleted centersAlejandro Sirgo Rica2024-02-191-37/+72
| | | | | | | | | | 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.
* rest: remove .full.sum file when image is removedOpenGnSys Support Team2024-02-151-1/+5
| | | | Remove .full.sum file too when user requests to remove an image.
* rest: allow room update keeping the same nameAlejandro Sirgo Rica2024-02-131-2/+2
| | | | | | 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.
* rest: room in folder can't be updatedJavier Hernandez2024-02-081-1/+1
| | | | change code to make possible to update rooms that are inside folders
* rest: Add uri to update folder nameJavier Hernandez2024-02-053-2/+184
| | | | | | Add support to update computer folder name Add support to update room folder name
* rest: Add uri to update roomJavier Hernandez2024-02-012-0/+123
| | | | | | | | 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
* rest: Add uri to update centerJavier Hernandez2024-02-012-0/+108
| | | | | | | | 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.
* rest: Check no client owns provided mac addressv1.2.5-9Javier Hernandez2024-01-161-0/+29
| | | | | | | | 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
* rest: Change room field 'group' to 'folder_id'Javier Hernandez2024-01-112-4/+4
| | | | | | | | 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.
* rest: update og_uri_handle with new folder commandsOpenGnSys Support Team2024-01-112-0/+4
| | | | Add folder/add and folder/delete, otherwise logging shows "unknown"
* rest: Support adding clients inside folderJavier Hernandez2024-01-112-6/+12
| | | | | | 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.
* rest: Add support for deleting foldersJavier Hernandez2024-01-101-0/+132
| | | | | | | | | | 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.
* rest: Add support for adding foldersJavier Hernandez2024-01-092-0/+158
| | | | Add support for adding computer folders and room folders.
* rest: Use mask to differentiate folder typesJavier Hernandez2024-01-081-4/+10
| | | | | | | | | | | | | | 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)
* rest: allow to set boot mode in client/updateOpenGnSys Support Team2023-12-211-2/+16
| | | | | Allow to specify .boot field and call set_client_mode() to update the boot mode.
* rest: missing POST /image/update in syslogOpenGnSys Support Team2023-12-212-0/+2
| | | | | | 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
* rest: cannot fail with image/create if it existsv1.2.5-8OpenGnSys Support Team2023-12-191-7/+0
| | | | | | legacy web console uses this REST API to refresh an existing image. Relax check not to break things.
* rest: add POST image/updateOpenGnSys Support Team2023-12-192-1/+40
| | | | add explicit API to update an image
* rest: no assumption on description field in create/imagev1.2.5-7OpenGnSys Support Team2023-12-193-24/+42
| | | | | | | | | 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.
* rest: log failed to delete entry from tableOpenGnSys Support Team2023-12-181-0/+12
| | | | add logging to report failure to remove entry.
* rest: do not exit() if execlp() failsv1.2.5-6OpenGnSys Support Team2023-12-151-1/+1
| | | | | execlp() should not ever fail, but if it ever happens, return -1 instead of exitting this daemon.
* rest: do not report error when removing image fileOpenGnSys Support Team2023-12-151-9/+2
| | | | this file might be in a different repository, this is best effort.
* client: parse permissions and lastupdate in /image/create response from clientv1.2.5-5OpenGnSys Support Team2023-12-124-28/+54
| | | | | | Use permissions and last update from client. update src/schema.c to add a new database version.
* client: stub to parse size field in /image/create response from clientOpenGnSys Support Team2023-12-121-3/+6
| | | | | Still incomplete, src/schema.c needs to be update to add a new field to the 'imagenes' table in the database.
* rest: expose description in GET /imagesOpenGnSys Support Team2023-12-121-1/+6
| | | | add .description field to json.
* dbi: og_computer_get_info() uses netmask field in 'room' tablev1.2.5-4OpenGnSys Support Team2023-11-301-2/+2
| | | | | | | | | | | netmask field in 'computers' table is never used, but ogcli still displays it through: # ogcli list client --client-ip 1.2.3.4 and it shows '0' or incorrect netmask (ogCP hardcodes this field). Update SQL query to fetch the room.netmask instead.
* rest: add GET /room/infoOpenGnSys Support Team2023-11-304-0/+116
| | | | | | | 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 }
* rest: fix client/info maintenance fieldOpenGnSys Support Team2023-11-301-1/+1
| | | | | | Use computer.maintenance instead of computer.name. Fixes: af47a082adb1 ("#1004 Add GET /client/info HTTP REST method")
* rest: add POST repository/updatev1.2.5-3Javier Hernandez2023-11-242-0/+83
| | | | | | | | | | 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" }'
* core: remove useless log when ogClient connects to serverOpenGnSys Support Team2023-11-231-9/+1
| | | | | | | | | | The following log message is display for each ogClient that is connected to the ogServer: Sent refresh to: 192.168.2.200 this tells the ogClient to send his current partition table when the connection between ogServer <-> ogClient starts. This is not very useful, remove it.
* rest: revisit loggingOpenGnSys Support Team2023-11-232-4/+190
| | | | | | | | | | | | | | | | 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.
* rest: fix WoL handlingOpenGnSys Support Team2023-11-231-13/+22
| | | | | | | | | | 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")
* rest: set center in /repository/addOpenGnSys Support Team2023-11-231-1/+3
| | | | | Set it to 1, ogCP and ogCLI never use this, and this REST API is never used by the old web console.
* rest: remove dead code in /repository/addOpenGnSys Support Team2023-11-231-27/+3
| | | | Remove unused code in this request and do not assume center id.
* rest: add /client/updateJavier Hernandez2023-11-231-0/+127
| | | | | Add POST client/update request to update client, this is identified by its ip address, with the data provided in the payload.
* main: use etc folder instead of cfg to store .json configuration fileOpenGnSys Support Team2023-11-141-1/+1
| | | | debian packages use etc, so update source code to use this folder too.
* core: restrict rest API to 127.0.0.1OpenGnSys Support Team2023-11-143-5/+11
| | | | | Until there is TLS support for this, frontend and ogserver needs to be in the same box by now.
* rest: Check valid bootmodeJavier Hernandez2023-11-061-0/+29
| | | | | | 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.
* rest: extract og_get_boot_modes from og_cmd_get_modes()Javier Hernandez2023-11-061-22/+62
| | | | | | 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.