- 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

This was just a typo...
It should be AnsibleGroup instead of AnsibleQuery...

JIRA INFRA-548

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

Use the before_flush hook to trigger the core services update.
It's much nicer than having to call a method in several places.

The core services update is triggered on creation/modification/deletion
of an Interface.

In the before_flush we can manipulate the session (add objects) but we
shouldn't call commit.
The db.session.commit() was removed from the launch_task method.

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

Table used to save the RQ background jobs

JIRA INFRA-403

JIRA INFRA-402

Memory shall be passed in MB and GB

a "startsWith" was inserted by commit 1a2f3786
This is the javascript syntax. In Python, it should be lowercase
"startswith"...

Passing tags as kwarg to the InterfaceForm doesn't work because
obj takes precedence (but interface.tags contain Tag instances and not id)
We need to update the default values. Calling process is required.
See https://stackoverflow.com/questions/5519729/wtforms-how-to-select-options-in-selectmultiplefield

JIRA INFRA-334

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

- rename "Virtual" to "Virtual Machine"
- add "Virtual IOC"
- add several physical devices (Switch, Industrial PC IOC, MicroTCA,
  VME, PLC)

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

We should reserve 10 addresses at the beginning and 5 at the end.
Meaning for a /24 network, we should start at 11 and end at 249.

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

Some tags (like gateway) should only be selectable by admin users.

One should be able to enter a MAC when creating/editing an interface.

- Only admin should be able to create networks
- Deleting an interface should require at least create group (should
  that be restricted to admin?)

Add delete and delete-orphan options to the cascade behavior:
- delete: delete from database associated cnames when deleting an
  interface
- delete-orphan: delete cname when removing it from the list of
  interface.cnames

Allow to create/delete cnames when creating/deleting interfaces

Move regex to validators.py

To check if the unique object is the one being edited, we need to store
the object used to create the form in the form (_obj).
This is inspired from flask-admin.