| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
With this commit users can select a room from the scopes tree, and then
delete it.
|
|
|
|
|
| |
This commit makes Add room view to use ogServer field from
scopesForm to send the command to the correct ogServer.
|
|
|
|
|
| |
With this commit users can select a center from the scopes tree, and then
add a room to that center.
|
|
|
|
|
| |
This commit makes Import Clients view to use ogServer field from
scopesForm to send the command to the correct ogServer.
|
|
|
|
|
| |
With this commit users can select a room from the scopes tree, and then
import clients to that room.
|
|
|
|
|
| |
This commit prevents ogcp from always mark as selected/checked scopes
that have an empty IP list.
|
|
|
|
|
|
|
|
|
| |
With this commit when users select a scope, the ogServer to
which it belongs is also sent. Then when processing the form we obtain
this ogServer and we can send it the pertinent requests.
This commit also makes action "Add client" to use the ogServer sent in
the form.
|
|
|
|
|
| |
With this commit users can select a room from the scopes tree, and then
add a client to that room.
|
|
|
|
|
| |
This commit makes commands views to use "get_server_from_clients()"
function to send the command to the correct ogServer.
|
|
|
|
|
|
|
| |
This commit adapt how "get_scopes()" accesses the name of the ogServer
because commit eae64dd changes how "multi_request()" returns it.
Fixes: eae64dd ("Initial support of ogServer requests routing")
|
|
|
|
|
|
|
| |
This commit adds a helper function ("get_server_from_clients()") to get
the adequate ogServer according to the targeted clients.
It also makes "Client details" command use this function.
|
|
|
|
| |
Fetch clients status using 'get_clients()'.
|
|
|
|
| |
With this commit, ogcp fetch all clients lists an join them.
|
|
|
|
|
|
|
| |
'multi_request()' function make requests to ogServers defined in the
configuration and aggregates it responses.
This commit also makes 'get_scopes()' use it.
|
|
|
|
|
|
|
| |
Update the configuration file format to support several ogServers and
retrieve scopes from those ogServers.
The old config file format is still supported.
|
| |
|
| |
|
|
|
|
|
| |
In "Repositories" view, users select a repository from the list on the
left and press "Delete repository".
|
|
|
|
| |
Creates "Add repository" form with the required inputs: name and IP.
|
|
|
|
|
| |
In Repositories section/view, users can manage task related to
repositories. For example: list, add, delete and edit them.
|
|
|
|
|
|
|
| |
On image creation use the id to identify repositories instead of the IP.
ogServer related commit:
* 52a38d3 ("#915 Use the repository id on image creation")
|
|
|
|
|
|
|
|
|
|
|
| |
This patch moves login password hashing from the frontend/javascript to
the backend/flask.
This patch moves password hashing of login and user management forms.
Related commits:
* c7b0024 ("Add password hashing")
* 661254b ("Add 'Add user' to Users section")
|
|
|
|
|
| |
Improve usability increasing the textarea used to copy the DHCPd
configuration.
|
|
|
|
|
|
| |
Rename "OS" to "Partition" to improve clarity.
This field represent which partition is used to create the image.
|
|
|
|
|
| |
If link speed is greater than 1000 Mb/s, show it in Gb/s to improve
readability.
|
|
|
|
|
| |
Otherwise, update/restore fails on images not saved in the same machine
which runs ogServer.
|
|
|
|
| |
Let users choose which repository want to use to save the image.
|
|
|
|
|
| |
Add ":" separator between each byte in hexadecimal and transform chars
to uppercase.
|
|
|
|
|
| |
Add an explanatory list of the colors used to represent the different
client states.
|
|
|
|
|
| |
If the last command sent to a client/s finishes with errors, their icons
in the scopes tree change to a yellow circle with an times sign inside.
|
|
|
|
|
| |
If the clients API response include link speed information, show it in
clients' pills.
|
|
|
|
| |
Retrieve and cache MACs one by one as users select clients.
|
|
|
|
|
| |
Creates "Delete user" form. The user to be deleted is selected from the
sidebar in Users section.
|
|
|
|
|
|
| |
Creates "Edit user" form with the following inputs: password, password
confirmation, role (administrator or regular), allowed scopes. It does
no allow to change/edit the username.
|
|
|
|
|
| |
Creates "Add user" form with the following inputs: username, password,
password confirmation, role (administrator or regular), allowed scopes.
|
|
|
|
|
| |
In Users section/view, administrator accounts can manage all task
related to users. For example: add, delete and edit users.
|
|
|
|
|
|
|
| |
ogCP now have to types of users, regular and administrator users.
ogCP configuration file defines users roles with the boolean field
"ADMIN".
|
|
|
|
|
|
|
|
|
|
|
| |
The front-end now hashes passwords before sending them to the back-end.
It uses SHA-512.
This commit adds a hidden input which sends the password hash to not
interfere with browsers' save password functionality.
Also change passwords of the template configuration file for their
hashed/digested versions.
|
|
|
|
|
| |
Otherwise, wtforms use "submit" as id of the <input> tag, shadowing
javascript function ".submit()".
|
|
|
|
|
|
|
|
|
|
|
| |
Add import clients form with required inputs: room and dhcpd.conf.
This permits users to rapidly add large amounts of clients to a room
using dhcpd.conf's syntax. Users can copy full dhcpd.conf files to the
text area and the parser only matches lines with the following format as
clients:
host dummy {hardware ethernet 12:34:56:78:90:ab; fixed-address 192.168.1.55; }
|
| |
|
|
|
|
|
| |
On connection error show a (toast) message warning the user. Otherwise,
users see Werkzeug debug page.
|
| |
|
|
|
|
|
|
|
|
| |
Allows updating the image file for an existing image.
This action is related to /image/create in ogServer API. If ogServer
receives an POST /image/create without the parameter "description", it
does not create a new image and only updates.
|
| |
|
|
|
|
|
|
|
| |
Each checkbox may have child checkboxes. If all those children are
checked, it be checked. If none are checked, it is unchecked. If some of
them are checked, then it’s in an indeterminate state (in this case
symbolically meaning “partially” checked).
|
|
|
|
|
|
|
|
|
|
|
| |
Old id format example: id_1-1_2-4_3-2
New id format example: scope-1-4-2
It represents the node and its ancestors' position with respect to
theirs siblings. The rightmost value is the current node position.
Commit f70d90ba32a6 introduces the old format.
|
|
|
|
| |
Also, increase its duration from 5 to 10 seconds.
|
|
|
|
| |
Also remove send button as it not necessary anymore.
|
|
|
|
|
|
|
|
|
|
| |
Disk selection uses "scopesForm" to submit the change, but setup/show
view receives new parameters not provided by this form.
Commit 17757baa4727 adds those parameters.
This commit gives disk selection its own form with all the required
parameters.
|