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

As the core service update doesn't depend anymore on each other but only
on the inventory update, 2 can be launched almost at the same time.
As they can't run in parallel, the second one will only start when the
first one is done, meaning that it can take more than 180 seconds to
complete.

Increasing the timeout to 500 seconds should avoid the task to be
reported as failed when it just took longer to run.

JIRA INFRA-895 #action In Progress

Following exception is raised when trying to update a network from
flask-admin:
sqlalchemy.exc.InvalidRequestError: Can't attach instance <User at 0x7f6f0e39ce10>;
another instance with key (<class 'app.models.User'>, (1,), None) is already present in this session.

1. If we remove the caching of the load_user method, the problem
disappears.
2. When updating a Network, this trigger an inventory update in
before_flush which adds a task to the session. This is when the
current_user is added to the session and the error raised.

So the problem is linked to the user caching and flask-admin.

The workaround is to remove the user object added by flask-admin to the
session.

JIRA INFRA-908 #action In Progress

Windows VM creation doesn't support post install yet
- the job that creates the VM returns before the installation is done
- the post install template is Linux only right now

JIRA INFRA-877

The /status/<job_id> view was only looking in the "default" queue to
retrieve the job.
"default" is not used anymore and was replaced by "high", "normal",
"low".
The method Job.fetch doesn't look in a specific queue.

JIRA INFRA-890 #action In Progress

launch_awx_job function was updated to trigger an inventory update.

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

- vm_osversion is passed as extra variables to the create_vm job
template
- vm_cores/vm_memory/vm_disk_size are also passed as extra variables
instead of saving them as host variables. Saving the variables in the
host when submitting the form forces to update the inventory before to
trigger the job to create the VM. This can be avoided using extra
variables. Furthermore those variables don't need to be in the
inventory, they can be retrieved as facts.

JIRA INFRA-877

The domain used as key must be a string (and not a model).

Regression from JIRA INFRA-870

No need to pass interface/memory/cores to trigger_vm_creation

JIRA INFRA-870

Only vmname and domain are required for the ics-ans-deploy-on-proxmox
playbook. All other variables are taken from the inventory.

JIRA INFRA-870 #action In Progress

New resource argument can be passed to launch_job_template.
It is optional and is set to "job" by default.
Shall be set to "workflow_job" to run a workflow template.

Note that passing the workflow name didn't work during my test.
The id had to be used instead.

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

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

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

The MAC field has both a Regexp and Unique validators.
In wtforms, the validation doesn't stop on the first error (all
validators are run).
In case of invalid mac address, the Unique validator makes a request to
the database that raises a DataError. This exception has to be catched.

JIRA INFRA-777 #action In Progress

After a VM or VIOC creation, a post install job can be triggered.
The job to trigger is based on the domain and defined in the
AWX_POST_INSTALL dictionary.

Admin users have the option to skip this post job if required.

The job is enqueued in RQ with a dependency on the creation job.
So it's only triggered after successful completion of the first one.

JIRA INFRA-769

JIRA INFRA-763

- 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

JIRA INFRA-763

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

JIRA INFRA-763

JIRA INFRA-763 #action In Progress