- add fqdn to host
- add gateway to network
- add netmask to interface
- allow to pass recursive via the API (to expand interfaces in host)
- add is_main property to interface (True if the interface is the main
  interface of the host)

JIRA INFRA-640

JIRA INFRA-640

JIRA INFRA-640

JIRA INFRA-678 #action In Progress

Mac table removed from Network part (mac is saved as a column in the
Interface table).

JIRA INFRA-674 #action In Progress

JIRA INFRA-578 #action In Progress

JIRA INFRA-578

JIRA INFRA-673 #action In Progress

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

JIRA INFRA-639

dns parameter removed (retrieved dynamically by the playbook)

JIRA INFRA-651 #action In Progress

- 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

- mac is now a column in the interface table (no link to the mac table)
- mac column is unique (can't have 2 interfaces with the same mac)
- the mac table is kept for the items

JIRA INFRA-639

JIRA INFRA-618

JIRA INFRA-618 #action In Progress

Allow to send metrics to a zabbix server

JIRA INFRA-614 #action In Progress

session._changes can be None in after_commit
See https://sentry.esss.lu.se/sentry/csentry/issues/63

JIRA INFRA-613 #action In Progress

IndexError raised due to:
{'cn': 'Alessio Curri (new)', 'sAMAccountName': 'alessiocurri2', 'mail': []}

JIRA INFRA-610 #action In Progress

LDAPInvalidFilterError: malformed filter raised due to the search filter
'(&(member=CN=Alessio Curri (new),OU=Contractors,OU=ESS
Users,DC=esss,DC=lu,DC=se))'

The brackets must be encoded using escape_filter_chars() to follow
RFC4515.
See https://github.com/cannatag/ldap3/issues/153

JIRA INFRA-550 #action In Progress

JIRA INFRA-576 #action In Progress

JIRA INFRA-576

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

1. If there is a rollback, some objects could be updated in the
elasticsearch index but not in the database.
Updating the index after commit ensures this can't happen.

2. In after_flush, not all relationships are updated properly. We need
to retrieve the objects in the after_flush_postexec event.
It can't be done in the after_commit event because we can't emit SQL at
that point.

See https://groups.google.com/forum/#!topic/sqlalchemy/GdB5J8h7YEU

JIRA INFRA-595

Decrease the number of SELECT calls by loading relationships that are
almost always used.

See https://docs.sqlalchemy.org/en/latest/orm/loading_relationships.html

JIRA INFRA-595

This is to ensure that when editing an object it is properly
re-indexed.

JIRA INFRA-575

JIRA INFRA-575

JIRA INFRA-575

Version shall be identical to the one used in production: 6.4.2

JIRA INFRA-575 #action In Progress

JIRA INFRA-575

The buttons should only be created if the items_table exists

JIRA INFRA-584

A deferred task will remain deferred forever if the task it depends on
fails. When checking for waiting tasks, we should ignore deferred tasks
that are too old.
"Too old" is currently set to 30 minutes. We shouldn't have tasks that
take that long. We might want to shorten that even a bit (to not block
new identical tasks to be run) but if a task failed there is probably
something to be done.

JIRA INFRA-559 #action In Progress

JIRA INFRA-569 #action In Progress

Add endpoints:
DELETE /network/hosts/<host_id>
DELETE /network/interfaces/<interface_id>

JIRA INFRA-570 #action In Progress

- set cascade to all and delete-orphan to delete interfaces when
  deleting a host
- button added on the view host page to delete host (admin only)

JIRA INFRA-557 #action In Progress

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