| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Make the repository list's first element be the current repo in use.
This is needed because, otherwise, an update could inadvertently
change the repo.
Remove a print statement that is no longer needed
|
|
|
|
|
| |
Make, in add and edit clients forms, the field repository show the list
with the actual repositories, not a harcoded value.
|
|
|
|
|
|
| |
- remove field image 'id'
- change size to display MiB instead of GiB
- replace 'Modified' with 'Last update'
|
|
|
|
|
|
|
| |
Make forms containing a 'Partition' field use all the same format (ie.
<Disk id> | <Partition id> | <Partion type> <Partition format>")
Signed-off-by: OpenGnSys Support Team <soporte-og@soleta.eu>
|
|
|
|
|
| |
Remove unnecessary field 'netmask' from forms used to create and update
clients. Netmask is configured in rooms instead.
|
|
|
|
|
|
|
|
|
|
|
| |
Add a form to allow the user to update a client.
ip field is in read only mode because this is the primary key to
identify a client in db.
Fields corresponding to boot mode (ie. oglivedir and boot) are also in
read only for now; ogServer has to fix set boot mode functionality
before it can be added here.
|
|
|
|
|
|
|
|
| |
Remove netdriver field from forms used to add or update a client.
At the time of creating (or updating) a client, ogCP uses a hardcoded
value for this field of the payload.
This field is not used by oglive in any way, remove it.
|
|
|
|
| |
Add the possibility to configure a gateway in a room.
|
|
|
|
|
|
|
|
| |
User can use this boolean field to specify if an backup copy needs to be
created before updating an image.
This only applies when sending a request to a client (ogClient)
supporting this parameter.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some programs substitute regular space characters (\u0020) by en spaces
(\u2002) when displaying monospace text. Others replace it by
non-breaking spaces.
Using a character set such as [ \t\n] to match any possible "space
related" character. Use \s to match any kind of whitespace related
character in the regex.
Pasted from python's documentation:
\s
For Unicode (str) patterns:
Matches Unicode whitespace characters (which includes
[ \t\n\r\f\v], and also many other characters, for example the
non-breaking spaces mandated by typography rules in many languages). If
the ASCII flag is used, only [ \t\n\r\f\v] is matched.
[...]
Fixes: d9f8c9561823daf234e2348b5ea0db2e92d29216
('views: better dhcp conf parsing when importing clients')
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This new regex allows parsing of:
- Irrelevant options that the user may paste from its config
file, eg. 'option host-name'.
- Allows linebreaks.
Hosts still require to have 'hardware ethernet' first, and then
'fixed-address'.
For example this regex admits dhcp host declarations such as
host pir36-22_78 {
hardware ethernet d8:5e:d3:25:28:9d;
fixed-address 10.1.36.78;
option host-name "pc_78";
}
Summary of the regex:
(?: *host *) # Match host keyword and spaces
([\w.-]*) # Match any word character (alphanum and underscore)
(?:[ \n\r]*{[ \n\r]*) # Match any space or newline, then match { and any following space or newline
(?:[ \t]*hardware *ethernet *) # Match any space or tab character followed by 'hardware ethernet'
((?:[0-9A-Fa-f]{2}[:-]){5}(?:[0-9A-Fa-f]{2})) # Match the mac address using ':' or '-' as separator
(?: *;) # Match any space character before a ';'
(?:[ \t\n\r]*fixed-address *) # Match any space, tab or newline followed by 'fixed address' and any following space
(\d+\.\d+\.\d+\.\d+) # Match an ip address (no validity check)
(?: *;)(?:[ \r\n]*[^}]*}) # Match any space followed by ';', then match any character except '}'
|
|
|
|
|
|
|
|
|
| |
Help user by hinting the current expected format via a placeholder in
the textarea box.
Current regex has its limitations when parsing dhcpd host declarations.
It does not support multi line host declarations or different options
outside "hardware ethernet ..." and "fixed-address ...".
|
|
|
|
|
|
| |
If an administrator selects a client without disks and goes to
"Partition & Format", ogCP redirects it again to "Commands" and shows a
floating message indicating that the client has no disks.
|
| |
|
|
|
|
|
| |
Instead of give permissions on all centers of a server selecting each one
of them, you can select the server that contains all this centers.
|
|
|
|
|
|
| |
Otherwise, ogCP crashes on image update.
Fixes: 8726ade ("Adapt commands to work with several ogServers")
|
|
|
|
|
|
| |
Since ogCP multi ogServer support, g.server is not used anymore. The
list of available servers is stored in the global variable "servers" at
og_server.py
|
|
|
|
|
| |
When creating o editing a user, you can select in which scopes from all
servers the user has permission.
|
|
|
|
|
| |
Otherwise, users can not remove from the web a server declared in the
deprecated way.
|
|
|
|
|
| |
Otherwise, if the configuration file do not have 'SERVERS' array, ogCP
crashes trying to append a new server.
|
|
|
|
|
| |
Otherwise, get_repositories() and get_repository() functions only get
the repositories of the first ogServer of the list.
|
|
|
|
|
|
|
| |
Commit X wrongly changed the URI to retrieve the repositories of an
ogServer.
Fixes: cf02e0c ("Add Servers section")
|
|
|
|
|
|
| |
Otherwise, ogCP crashes on image restore.
Fixes: 8726ade ("Adapt commands to work with several ogServers")
|
| |
|
|
|
|
|
| |
This commit makes Delete clients view to use "get_server_from_clients()"
function to send the deletion request to the correct ogServer.
|
|
|
|
| |
Otherwise, ogCP crashes trying to connect to unreachable ogServers.
|
|
|
|
|
|
|
| |
In Servers section/view, users can add or delete ogServers from ogCP
configuration file.
Replaces Repositories views and recycle some of its code.
|
|
|
|
|
| |
Otherwise, users may change the file path on one place of the code and
forget to change the other places.
|
|
|
|
|
|
| |
Clients pills show MACs regardless of the ogServer they belong to. Flask
GET /client/mac API uses "get_server_from_clients()" function to send
the command to the correct ogServer.
|
|
|
|
|
| |
This commit makes Delete image view to use ogServer field from
imagesForm to send the deletion request to the correct ogServer.
|
|
|
|
|
|
|
|
|
|
| |
When users select an image, its ogServer is sent too. Then, the back-end
(flask) processes the form to obtain this ogServer and send it the
pertinent requests.
It also makes "Image details" view use this new parameter, and adds
javascript code to ensure that users can only work with several images
at the same time if they belong to the same ogServer.
|
|
|
|
|
|
| |
Images view fetch images from all ogServers configured and show them in
the left tree as a nested list. ogServers are represented as the parents
of their images.
|
|
|
|
|
| |
This commit makes Delete center 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 delete it.
|
|
|
|
|
|
| |
This commit adds a new select input with all available ogServers to "Add
center" view. The ogCP creates the center in the ogServer selected by
the user.
|
|
|
|
|
| |
This commit makes Delete room 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
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.
|