| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
Fix unusable image view when an image has a repo associated that no longer
exists. Display image under "unknown" if there is no repo for it.
|
|
|
|
|
| |
Display partition table in Scopes -> Client Update, this is meaningful context
information
|
|
|
|
|
|
|
|
| |
In edit client form, set boot field to read-only
Boot mode can be updated from Commands -> Set boot mode, it is more flexible to
do it from there, because you can select several clients and set the boot mode
at once.
|
|
|
|
|
|
|
|
|
|
| |
Remove netiface selectable in clientsDetails form.
eth{0,1,2} is misleading, it does not represent the real device in the client.
And users we know always boot from the first device.
Hide this feature until there is a better design for this.
|
|
|
|
|
|
|
| |
Show a more detailed description of each choice
Display an error and redirect the user if an empty list of os's was
received. Post does not work with an empty list
|
|
|
|
| |
In client details command, show read-only form
|
|
|
|
|
| |
Show the user an error if ogServer responds with an error when
retrieving oglive list
|
|
|
|
| |
Support adding a room to a folder
|
|
|
|
|
|
|
|
|
|
| |
Add support for adding computers to a folder.
It uses a js script that when selecting a folder in the html form, it
will also select the parent of the folder. For instance, if the user
were to select a folder that is contained inside a room, the room would
also get selected. This allows the view to know which parent contains
the folder.
|
|
|
|
|
|
|
| |
Add functionality to allow the user to delete a folder.
Show a confirmation page to the user listing the content of the folder
that is about to delete
|
|
|
|
|
|
| |
Add support to create a folder able to contain multiple computers.
Add support for adding a folder able to contain rooms
|
|
|
|
|
| |
Warn user if trying to access the logs of a client that don't yet exist.
This is prefered to showing the backtrace to the user.
|
|
|
|
|
| |
In set boot mode, show an error if server replies with an empty list of
boot modes
|
|
|
|
|
| |
Check that server replies with error code and display an error if it
does.
|
|
|
|
|
|
|
|
|
| |
- Remove a table with redundant info; it was displaying server's stats,
which was already in another table
- Add last update info at the top of the page
- Make page more robust by checking if ogLive images are available.
Before this patch, page shows a traceback if the ogLive list are not available.
|
|
|
|
|
|
| |
Show user, when attempting to change the bootmode of more than one
client with different boot modes, a warning and a table with said
bootmodes.
|
|
|
|
|
| |
Sort tree that contain the scope information (centers, rooms, clients)
so that they appear in sidebar in alphanumerical order.
|
|
|
|
|
|
|
|
| |
Allow user to change boot mode when editing a client.
First item selected is the client's current boot mode. This is so that
if the user edits the client's data, but doesnt touch bootmode, it stays
the same.
|
|
|
|
|
|
|
| |
In client_details template, rename 'create' button to 'submit'.
This template is used by both client-add and client-edit commands; it
would not make sense to have a 'Create' button in client-edit.
|
|
|
|
|
|
| |
Allow to update only images that are in the repo the client is assigned
to; if an image is inside a different repo, it will not appear in the
'Image' selector
|
|
|
|
|
|
|
|
| |
Fix client detail form failing in some cases. It would fail if the user
wanted to view the details of a client, that had a partition using an
image that is no longer in the list of all images stored by the servers.
This could happen if the image was deleted, but the client still was using
the image in one of its partitions
|
|
|
|
| |
use new POST image/update when updating an image.
|
|
|
|
|
|
|
|
|
|
| |
Allow only the creation of images in the repository that is currently
assigned to the selected client.
This operation is still not handled in ogserver and oglive, it needs
more work behind the scenes: it needs an update in the templates and
it also needs the new ogLive builder so ogClient has control on the
samba mount.
|
|
|
|
|
| |
Allow to restore only to images that are in the repo the client
is assigned to.
|
|
|
|
| |
Make the create-image menu preselect the repo of the selected client
|
|
|
|
|
| |
Make the sidebar from the images menu display the list of repos grouped
by repos
|
|
|
|
|
| |
Modify the add/edit users menu to make the 'allowed
scopes' field only display centers
|
|
|
|
|
|
|
|
| |
Add, in import clients menu, a selector to select the repo to be
associated with the clients about to import
modify OG_CLIENT_DEFAULT_BOOT variable to be 'oglive'; 'pxe' is not a
valid boot mode, and ogserver would return an error
|
|
|
|
| |
Add a 'description' field to the image-details form.
|
|
|
|
|
| |
Change the Image details form to display the 'Datasize' field of the
image in MiB instead of GiB
|
|
|
|
|
|
| |
Fix a bug that made the create and update images actions unusable.
The data sent to post was incomplete; partition's 'code' data was missing.
|
|
|
|
|
|
|
| |
Make the partition and format form fail if the user has not added a
cache partition.
A cache partition is required to make the restoration of images work
|
|
|
|
|
|
|
|
|
| |
combine repo_add_get and repo_add_post into one, action_repo_add. This
is to follow convention across all the views and to clarify that it is
an action.
rename repos_details template to repos_add. Now it is clear the purpose
of each action template; there is one for each: add, delete and update
|
|
|
|
|
| |
allow the user to update a repo by selecting one and pressing the update
button.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
allow the user to delete a repo by selecting one and pressing the delete
button. Previous to deletion, show the user a confirmation page (a form)
with the details of the repo to delete
the confirmation form is constructed with the fields of Repoform.
RepoForm is also used in template used to create a repo. To make both
templates work with RepoForm, RepoForm's field 'create' has been renamed to
'submit'
ogcp.js: add a function to make that, when the user selects a
repository, the server in which it is contained is automatically
checked. We need it checked so that action_repo_delete can know the
server to which it has to send the delete request. Use data-server in
repos_details.html to make this work
Validate, in action_delete_repo, that user has only selected one repo to
delete. In order to do that, action_delete_repo view needs to be able to
get a list of all selected repos. This is only possible if <input>
elements that are associated with repos info contain a different name
attribute per repo. In this case, template repos.html has been modified
to use name={repo name}-{repo_id}. After this, parse_elements() will
work and parse a set containing all selected repos.
modify html input associated to repos server in order to follow same
convention as in other templates. For example, images uses image-server;
scopes, scope-server.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The menu includes a list of the repos of each server. The user can
select a server or a repo to make changes.
As of now, the only action possible is to add a repo to selected
server.
The work contained in this commit can be structured in:
1. Add the repos menu:
- Add a 'repos' button in the menus bar (base.html).
- Add repos.html template to create the management repos menu.
- In ogcp.js, add function to store in browser's local storage which
elements of the sidebar are uncollapsed. This saves the sidebar state
after a page refresh.
- Add manage_repos() in views.py
2. Allow to add a repo:
- Add template with form to add a repo (repos_details.html)
- Create RepoForm(FlaskForm) in action_forms.py
- Add repo_add_get() and repo_add_post() in views.py
|
|
|
|
| |
This is never used by ogserver, instead the room netmask is always used.
|
|
|
|
|
|
|
|
| |
Add a placeholder that shows the user an example of what a valid mac
address looks like.
By now, mac needs to be specified as AABBCCDDEEFF without : for historical
reasons.
|
|
|
|
|
|
|
| |
- netmask is no accesible anymore, remove it.
- The form made reference to fields that do not exist anymore:
netmask and netdriver (removed in a previous commit)
- make the repository field show the repo that is in use
|
|
|
|
|
|
|
|
| |
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 '}'
|