Normal users can only view networks they have access to

JIRA INFRA-1809 #action In Progress

JIRA INFRA-1790 #action In Progress

JIRA INFRA-1724

Sensitive hosts shall not be returned in search and get queries (both
web and API) for non admin users

JIRA INFRA-1671

JIRA INFRA-1671 #action In Progress

JIRA INFRA-1627

JIRA INFRA-1627 #action In Progress

Check that a group child is not:
- the group itself
- the "all" group
- in one of the parent groups (recursively)

JIRA INFRA-1622 #action In Progress

JIRA INFRA-1604 #action In Progress

Non admin users can't add an interface on a different network scope than
the main one.
No change for admin users.

Note that this is more to avoid confusion.
This is not restricted via the API.

JIRA INFRA-1297

Functionality is deprecated and not used anymore.
New playbook written to use the variables in csentry inventory.

JIRA INFRA-1299 #action In Progress

JIRA INFRA-1292 #action In Progress

JIRA INFRA-1049 #action In Progress

- admin can delete any hosts
- normal users can delete hosts they created

Note that still only admin users can delete hosts via the API (more dangerous
operation as a script could delete many hosts).

JIRA INFRA-1018 #action In Progress

Regression from b9c1b838

Calling utils.trigger_ioc_repository_creation runs launch_task
which does a db.session.add(task). This raises:

SAWarning: Usage of the 'Session.add()' operation is not currently
supported within the execution stage of the flush process. Results may
not be consistent.  Consider using alternative event listeners or
connection-level operations instead.

SAWarning: Attribute history events accumulated on 1 previously clean
instances within inner-flush event handlers have been reset, and will
not result in database updates.

The result is that the host is not added to the elasticsearch index.

We can't trigger the task in after_update/after_insert events.
Perform the call in the view instead. It's temporary anyway. This should
be handled by IOC Factory.

JIRA INFRA-1015

The csentry_autoinstall_boot_profile variable shall be saved to setup the
DHCP option.
The DHCP shall be updated when a change occurs.

JIRA INFRA-1016 #action In Progress

Allow to select by default the last chosen device_type when creating a
new host.

JIRA INFRA-987 #action In Progress

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

JIRA INFRA-943 #action In Progress

Move trigger_ztp_generation and trigger_vm_creation from tasks.py to
utils.py.
The tasks.py module should only include functions used by the worker.

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

JIRA INFRA-775

- 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

No need to pass interface/memory/cores to trigger_vm_creation

JIRA INFRA-870

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

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

- Disk size added to the create VM form
- Disk size saved to proxmox_disk_space variable in host inventory

The proxmox_disk_space variable is used by the Ansible job when creating
the machine.

JIRA INFRA-759 #action In Progress

Not sure why a tuple instead of network was returned...
There must have been a comma at the end of the line due to copy/pasting
and black converted that to a tuple.

Added a test for the create_interface function.

JIRA INFRA-697 #action In Progress

JIRA INFRA-640

JIRA INFRA-678 #action In Progress

JIRA INFRA-578 #action In Progress

JIRA INFRA-578

- 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

- 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

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

JIRA INFRA-575

JIRA INFRA-569 #action In Progress