Allow to trigger a new core service update only if there is none
depending on the triggered inventory update.

JIRA INFRA-895

Tags were basically only used for IOCs.
Tags were linked to the interface (and not the host).
But for IOC we assume it should always be the main (first) interface.

Using a field on the host table will make it more obvious for users.

Created a IOC dynamic group type, to create a group including all IOCs

JIRA INFRA-862 #action In Progress

JIRA INFRA-860 #action In Progress

No need to use ajax to retrieve the content of simple tables.

For Ansible groups, it takes some time to retrieve the data due to the
list of hosts for each group to compute. We keep the ajax request so
that the page is displayed quickly. We might switch to server side
processing (like for hosts).

JIRA INFRA-860

Allow to specify the gateway for each network

JIRA INFRA-809

- Restrict the width of the vars column
- Make the children and hosts a list of comma separated words with space
  to allow line break

JIRA INFRA-763

- mac is now a column
- the id of the input field changed from #mac_address to #mac

JIRA INFRA-639

- Host names are unique (no 2 hosts with same name)
- A host name shall not conflict with a cname or interface (if not main
interface)
- Interface names are unique (no 2 interfaces with same name)
- An interface shall not conflict with a cname or host (if not assigned
host)
- cnames are only unique by domain (2 cnames can have the same name if
different domains)
- A cname shall not conflict with a host or interface
- An interface has to be linked to a host

Validation is implemented at the model level.
Some is also implemented at the form level as it gives nicer feedback,
but not all as it's a bit more complex when it requires check on several fields.

JIRA INFRA-245

selectize-bootstrap4-theme v2.0.2 from
https://github.com/const-se/selectize-bootstrap4-theme

To use selectize on a Select or MultiSelect field, add the
selectize-default class. It initializes selectize with the default
options.

JIRA INFRA-644 #action In Progress

JIRA INFRA-618 #action In Progress

This saves the state of hosts and items tables (search input,
ordering, paging position) so that it can be restored when the user
reloads a page.

See https://datatables.net/examples/basic_init/state_save.html

JIRA INFRA-608 #action In Progress

- switch to server side processing to retrieve network hosts
  (the table started to be bigger and takes time to load)
- add full text search using elasticsearch

Note that only the first IP is displayed in the host table (all
interfaces were displayed before). Search can be performed on any
interfaces.

JIRA INFRA-595 #action In Progress

JIRA INFRA-575 #action In Progress

The buttons should only be created if the items_table exists

JIRA INFRA-584

Retrieving all items from the database takes some time.
The task is thus handled by the RQ worker.
We use ajax to periodically monitor the status of the job
and redirect to the file when ready.
A progress bar is displayed to let the user see the progress.

The mechanism put in place could be re-used for other use cases.

JIRA INFRA-545 #action In Progress

JIRA INFRA-545

Included libraries:
- DataTables 1.10.18 (with bootstrap 4 theme)
- Buttons 1.5.2
- Column visibility 1.5.2
- Print view 1.5.2

JIRA INFRA-545

This is not directly supported by CodeMirror.
See https://github.com/codemirror/CodeMirror/issues/850

Add cm-resize library from https://github.com/Sphinxxxx/cm-resize

JIRA INFRA-543 #action In Progress

The official flask-bootstrap is still not compatible with bootstrap 4.
The application basically only uses the main template and one macro.
It's easier to include directly bootstrap in CSEntry.
It makes upgrading to the latest bootstrap much easier and removes a
dependency.

Update to bootstrap 4.1.3

Added:
- jquery-3.3.1.min.js
- bootstrap.bundle.min.js (include popper but not jquery)

Note that jquery.slim can't be used.
We need for example $.getJSON for datatables.

JIRA INFRA-412

Allow to enter Ansible variables on host in YAML format.
Use codemirror (http://codemirror.net) to make editing YAML easier.

JIRA INFRA-412

+ yaml mode

Allow to display tasks

JIRA INFRA-403

JIRA INFRA-302

This is to be used for stack of switches only

- a stack_member is linked to an host (device_type has to be "Switch")
- a stack_member is an integer between 0 and 9 (included) or can be None
- the couple (host_id, stack_member) must be unique

JIRA INFRA-267

- rename "Virtual" to "Virtual Machine"
- add "Virtual IOC"
- add several physical devices (Switch, Industrial PC IOC, MicroTCA,
  VME, PLC)

1. When we have a stack of switches, the same IP is associated to several
   switches
2. Move the items <-> host assocation to the item create/edit page

JIRA INFRA-267

The interface name doesn't need to be displayed in the form as we force
it to the hostname.

We set the interface name to the hostname when submitting the form.
This fixes the copy/paste issue with the mouse that didn't trigger the
keyup event.

JIRA INFRA-287

JIRA INFRA-281

If an error is raised when submitting the form, we should keep the IP
that was entered.

JIRA INFRA-285

The class "is-invalid" is removed on all type=text input
on keyup event.

JIRA INFRA-285

- create many-to-many relationships between the user table and
attributes tables (manufacturer / model / location / status / action)
- add a checkbox as the first column of the attributes table to add or
remove an attribute to the favorites
- add a new page to display the favorite attributes

JIRA INFRA-283