| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Show the partition id as a non editable label in each partition
of the Partition and Format form.
Assign sequential partition id from top to down and recalculate
every partition id when a partition is removed.
|
|
|
|
| |
Add view to modify room information such as name, gateway and netmask
|
|
|
|
| |
Add view to modify folder information such as name
|
|
|
|
|
|
|
| |
Although ogcp support for multiple server, the plan is to only support for one
server in this version.
Remove Server: context information and Repo: in list images
|
|
|
|
|
|
|
|
| |
preselect 'pxe' (if available) at adding a new client.
use a dedicated template for adding a client and remove irrelevant
partition table; client has yet to set its partition, so everytime, the
table would load empty.
|
|
|
|
|
|
|
|
| |
Make delete confirmations show information in a manner that is easier to
read. This includes delete confirmations for centers, room and folder.
Messages are now more clear. Also, content table shows the type of the
items (folder, room, etc.)
|
|
|
|
|
|
|
|
|
|
|
| |
Make list images command show only information of the images the user
has selected in the sidebar.
Improve readability of the information.
Show size and data size attributes rounded
Warn the user if no images have been selected in sidebar
|
|
|
|
|
|
|
|
|
|
| |
In delete-center, delete-room and delete-folder confirmation pages, show
the ancestors of the items about to delete. Likewise, show the items it
contains.
For example, if user is about to delete a room, confirmation page will
display in which center it is contained and the clients and folder it
has inside
|
|
|
|
|
| |
Add list images action that shows a list of all the images in each
server and their properties
|
|
|
|
|
|
|
|
| |
When setting up oglive, preselect oglive that is most used by selected
clients. If only one client is selected, preselect that of the client.
In the unusual scenario where a client is set with an oglive that is not
in the ogserver's list of available oglives, preselect default.
|
|
|
|
| |
Remove warning header and show selected clients above boot-mode tables
|
|
|
|
| |
Fix wrong navigation details in template select_client.
|
|
|
|
|
| |
Add an action to allow the user to view details (name and ip) of a
particular repo.
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix a bug that made the 'add a new partition' button unusable if all
partitions (rows) were deleted.
The reason for this bug was that the AddPartition() function would add a
new partition by cloning an already present html row element. This would
fail if no more rows were present in the table.
The solution implemented checks, previous to delete a partition, if it
is the last partition. If it is, then, instead of removing the whole
row, it just empties it.
Html button element needs to contain 'type="button"' attribute for this to
work. Otherwise, default action for the button is submit and it would
redirect after clicking.
|
|
|
|
|
|
|
| |
Add missing templates.
Fixes: 15dd4c2a8f69 ('views: add action to update repo')
Fixes: 152337b6bdb8 ('views: add action to delete repo')
|
|
|
|
|
|
|
|
|
| |
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 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
|
|
|
|
| |
All views from Commands section have this two attributes.
|
|
|
|
|
|
|
| |
In Servers section/view, users can add or delete ogServers from ogCP
configuration file.
Replaces Repositories views and recycle some of its code.
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
| |
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; }
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
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.
|
|
|
|
|
| |
Move disk selector from the bottom of the page to the first table,
nearby "Partition Table Type" and "Total Disk Size".
|
|
|
|
|
| |
Allow the user to choose a computer as reference to display the
partition scheme form.
|
|
|
|
| |
Otherwise, this strings are not translatable.
|
|
|
|
| |
Add a back button to facilitate users to return to the previous page.
|
|
|
|
|
| |
Now users can select clients only in scopes and command views, in any
other view we set the scopes tree read only.
|
| |
|
|
|
|
| |
When loading any scopes view, its nav button becomes active.
|
|
|
|
| |
When loading any command view, its nav button becomes active.
|
|
|
|
| |
Otherwise, "image details" page lose the images tree and buttons.
|
|
|
|
|
| |
Otherwise, this actions pages lose the scopes tree and the scopes
buttons.
|
|
|
|
|
|
| |
Both "Add client" and "Client details" views use client_details.html
template. With this commit, "Add client" extends scopes.html and "Client
details" extend commands.hmlt.
|
|
|
|
|
| |
Draw selected clients from confirmation pages like selected clients from
scopes and commands pages.
|
|
|
|
| |
Show the number of clients and their IPs.
|
|
|
|
|
| |
Otherwise, this actions pages lose the scopes tree and the commands
buttons.
|
|
|
|
| |
Refactor duplicated code as a jinja macro.
|
|
|
|
|
| |
Remove code to draw selected clients. Image creation template do not use
it because only operates one client.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Extend commands.html template to keep scope tree, and action buttons
state.
When in the software inventory view, there exists two options: 'update'
or 'view'. Do not print raw json response from ogserver about the software
inventory/profile.
When vieweing the software list, print a html table using the new
template: software_list.html.
Do not print blank pages with plain text html error codes when something
goes wrong. Instead, print an error message after redirecting to the
commands view.
|
| |
|
|
|
|
|
|
|
|
| |
Extending from command.html is required for action views to mantain
the scope context on the left side column.
Enables setting dropdown button and action button as active when loading
the hardware inventory view.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Group related actions in the "commands" section inside a
dropdown button.
Declutters the panel in which the buttons are displayed.
Dropdown button jinja block name is used as prefix for the block names
of inside buttons. For example, for the image dropwdown button:
<button class="...{% block nav_image %}{% endblock %}...">
{{ _('Image') }}
</button>
Actions such as restore and create will show a jinja block inside class
attr like:
<input class="... dropdown-item{% block nav_image_restore %}{% endblock %}" ...
<input class="... dropdown-item{% block nav_image_create %}{% endblock %}" ...
|