The set event is triggered too early and no interface is yet associated
to the host. The fqdn is thus set to the name.

JIRA INFRA-1015 #action In Progress

The boot profile is used to perform a network installation on a physical
machine.

JIRA INFRA-943 #action In Progress

This is temporary. The repository should be created by IOCFactory.

JIRA INFRA-932 #action In Progress

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

JIRA INFRA-895

A job running in AWX prevents an inventory sync (of the same
inventory). This restricts AWX to run only one job at a time as
the inventory is always updated on launch.
To prevent this issue, the inventory is updated from AWX when needed.

- The update is triggered on any model modification that is used in the
inventory (AnsibleGroup, Cname, Domain, Host, Network, NetworkScope)
- For Interface, the inventory sync is triggered by the
trigger_core_services function as it depends on it
- The inventory update job is put on the "high" queue so that it takes
precedence over all other jobs.

JIRA INFRA-887 #action In Progress

Ensure that the trigger_core_services_update job is always processed
before the other jobs (low queue).

JIRA INFRA-887

- users with access to the network can create VIOC
- VM can be created only in the ALLOWED_VM_CREATION_DOMAINS

JIRA INFRA-775

Add awx_resource field to the task table.
The field is None for local tasks (like excel file creation).
It's the awx resource used to launch the job otherwise.
Currently job or workflow_job.

JIRA INFRA-886 #action In Progress

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

Allow to specify the gateway for each network

JIRA INFRA-809

Host interfaces are always returned sorted by name

JIRA INFRA-785 #action In Progress

For Network and Network scope dynamic groups, only the interface with
the same name as the host (the main interface) is taken into account.

If only another interface is part of the network or network scope, the
host is not part of the group.

JIRA INFRA-784 #action In Progress

Search on keyword can be made case insensitive by using a normalizer.
But some fields with type keyword include several words.
They are only returned by entering all words. This is not what
most users expect.

It's better to use the "text" type by default (for text fields) and add
an extra "keyword" field of type "keyword" for sorting.

JIRA INFRA-770

Dynamic mapping set to "strict" so that we don't forget to update the
mapping when adding new fields to a model.

JIRA INFRA-723 #action In Progress

- 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-578 #action In Progress

JIRA INFRA-673 #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

- 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 #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

- 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

JIRA INFRA-575 #action In Progress

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

- 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

JIRA INFRA-500 #action In Progress

JIRA INFRA-459 #action In Progress

Using flask-login request_loader, we can validate jwt tokens.
This allows to use the same decorators for the web UI (using cookies)
and the API (using JWT) as well as the current_user local proxy.

JIRA INFRA-414

This is not super clean. The model and device_type belong to the host.
This is for easy access from the API.
But it would be better to have a "expand=true" query parameter and return the
host as a dict.

JIRA INFRA-414

JIRA INFRA-414

- add ansible_groups_hosts_table for many-to-many relationship between
groups and hosts
- add new api endpoint /network/groups

JIRA INFRA-412