GitLab

* Fix the way we handle input of get_subnet()

New name is snf-manage floating-ip-history <floating-ip-address>
Get info about which servers this ip is or was connected to.

* Fix a bug if the user specified no allocation pools
* Fix a wrong error message in logic/subnets.py

* Add a function in logic/subnets.py that parses allocation pools
* Add a new option in snf-manage network-create for allocation pools
* Update subnet-create to use the new function

Update the way allocation-pools work in subnet-create. Now,
--allocation-pool can be used multiple times, each time for a different
pool. Eg.,
snf-manage subnet-create --network-id 1 --cidr 192.168.42.0/24
--allocation-pool 192.168.42.10,192.168.42.30
--allocation-pool 192.168.42.100,192.168.42.200

Add decorator convert_api_faults

snf-manage floating-ip-state <floating_ip_state>
Find if a floating-ip is attached to a server or not.
IPAddressLog now can contain multiple entries for the same ip.

Use --port multiple times to configure server connections.
Possible forms are:
* --port network:<network_id>(,address=<ip_address>)
* --port id:<port_id>
* --port floatingip:<floatingip_id>.

List only ports connected to public networks
List only ports connected to a specific server

Change default value of 'dhcp' option in snf-manage network-create command.

Do not print IP pool of Ganeti network in case the network is an IPv6
only network. The Ganeti network has a dummy IPv5 subnet, just because
it is needed. Only change this dummy subnet to /30 to reduce space in
Ganeti config file.

* Export 'SNF:DRAINED' status for drained networks.
* Do not allow creation of new ports in drained networks.
* Do not allow allocation of new IPs in drained networks.

If at the end of reconciliation the state of the network is not ACTIVE,
try to recompute the state of the network based on the state of the
networks in each backend. This step is mostly needed in case that the
network does not exist in any backend.

Use 'models.PROTECT' for 'on_delete' attribute for some ForeignKey
relationship between networking models. This will create a more "strict"
database and protect for unexpected data loss.

Allow registering a resource for a different service, if it originates
from the same component.

Remove special handling of floating IP pools in reconciliation
mechanism since floating IP pools are treated the same way with other
networks.

Pass 'nfdhcp' tag even if network is IPv6 only.

Use prefetch_related and select-related to importive the DB queries that
are generated by *-list snf-manage commands.

Add options to use 'prefetch_related' and 'select_related' options of
Django queries to optimize the DB queries.

Fix which networks are going to be initialized in the new backend and
how the are printed in the output!