- 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

- refactor Network class

- network name should be unique and not nullable
- force all name fields to StringField

Don't ovveride SQLAlchemy __init__ method on db.Model classes.

See http://flask-sqlalchemy.pocoo.org/2.3/quickstart/:
SQLAlchemy adds an implicit constructor to all model classes which
accepts keyword arguments for all its columns and relationships. If you
decide to override the constructor for any reason, make sure to keep
accepting **kwargs and call the super constructor with those **kwargs to
preserve this behavior

Use full exception error as message (error messages from psycopg2 can
be quite long but that makes it much more explicit)

TODO: we should maybe raise ValidationError in models
and catch that to raise CSEntryError in the API

The database constraints will catch the same error
(and raise an IntegrityError).

Having some validation at the model level allows to display nicer error
messages.
We use CSEntryError exception and not ValidationError so that it can be
used both by the API and views.

- Allow to pass several mandatory fields in create_generic_model
- Add tests

- catch IntegrityError on patch
- disable autoflush (IntegrityError was raised before commit due to
autoflush)