JIRA INFRA-4308

JIRA INFRA-2808 #action In Progress

JIRA INFRA-2112 #action In Progress

JIRA INFRA-1724

JIRA INFRA-1671

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

Endpoints required to update host and interface via the API

JIRA INFRA-1406 #action In Progress

The interface name shall start by the host name. Its length must thus be
longer than the host.

JIRA INFRA-1324 #action In Progress

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

1. It's possible to erase the network when creating a host.
The exception raised was due to the ip_in_range validator
where a select using the network_id is performed.
This is now catched to raise a ValidationError.
2. Add some javascript to remove the is-invalid class on the network and
IP fields when changing them

JIRA INFRA-810 #action In Progress

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

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

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

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

JIRA INFRA-640

JIRA INFRA-578 #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-414

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

https://black.readthedocs.io/en/stable/

Allow to create a VM or Virtual IOC

"gateway" tag removed. It could be re-added if needed to overwrite the
default computed gateway for example.

JIRA INFRA-339

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

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

JIRA INFRA-281

"type" field on host replaced with foreign key "machine_type_id"

JIRA INFRA-281

This reverts commit 920b9bc5.

Allowing cnames with different domains makes things too complex.
The domain shall be the same as the host.

See INFRA-242

Fix INFRA-242

The network range defines the IP to be allocated.
This is to reserve some specific addresses (for gateway for example).

An admin user should be able to define an interface outside the network
range.

The IP address select field was replaced with a string field
(initialized to the first available IP).

Fixes INFRA-200

Fixes INFRA-197

The interface name shall start with the hostname of the host it is
associated to.

Note that this is only enforced via the UI (from which most users will interact),
not from the API.

Fixes INFRA-195

- add domain_id on NetworkScope table to define a default domain
- add domain_id on Network (default to the Network Scope one)

Fixes INFRA-194