- 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

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

JIRA INFRA-570 #action In Progress

New get_json method on test client response.
See http://flask.pocoo.org/docs/1.0/testing/#testing-json-apis

JIRA INFRA-424

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

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/

- rename physical to physical machine
- IOC should be a tag

JIRA INFRA-302

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

JIRA INFRA-277

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

JIRA INFRA-281

cnames entered in CSEntry are just names not FQDN
See d1f500238c5798259f536bb80fa93aba2d493b97

Allow to filter by domains

Not everyone at ICS is part of the 'ICS Employees' AD group.
We have to accept 'ICS Consultants' as well.

The CSENTRY_LDAP_GROUPS settings now takes a list of groups instead of
just one.

Remove unused is_member_of_all_groups method.

Fixes INFRA-225

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

- 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

The string representation of a Network is the vlan_name.
This is what we should allow to pass as string to create an interface.

Note that if we pass network_id instead of network when creating
and interface, the validate_interfaces method from the Network class
is not called.

All endpoints are plural

Having the description field only on the Model class makes things
inconsistent.
It's nice to have a description on other attributes as well.

Required to create users when importing items from JIRA.

Renamed blueprint from "users" to "user" to be consistent with other
blueprints (inventory and network).

+ fix tests

- Several IPs (hosts) can be associated to one MAC address
- Host name shall be non nullable