GitLab

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!

Return [] instead of None, if the field is null.

* Create function 'ensure_network_is_active' to check if a network
 exists in backend and create it if not.
* Create function 'create_job_dependencies' to transaform a list of job
  IDs to the 'depends' attribute as expected by Ganeti.
* Replace hard coded string of job statuses with constants from rapi
  module.

Fix when network is created in the Ganeti backends. The network must be
created in the Ganeti backends only after IPv4 or/and IPv6 subnet has
been created. This commit moves the code that created the network in the
Ganet backend out of 'network.create' function to a separate function
that is called at the end of command.

Also, this commit fixes some small issues and removes unnecessary
options.

* Return subnets from public networks, in GET subnets
* Fix a bug in list ports, where only attached ports to servers were
listed

* Return 'links' attribute in subnet api response
* Return 'links' attribute in port api response

When ports are created from the API they do not have an IPv6 address.
The IPv6 address is only available after the MAC address of the
NIC(port) is known which is only available after the message from the
Ganeti backend has been received. However, dispatcher did not created
correctly the IPv6 addresses. This commit fixes this issue along with
some small code refactoring.

Create 'cyclades_network' service which is part of Cyclades, of 'network'
type and with 'network' prefix to hold all API endpoints that are
relative with networks. So, for example, the endpoint for networks will
be: /cyclades/network/v2.0/networks

Also move 'cyclades.floating_ip' and 'cyclades.network.private'
resources to 'cyclades_network' service.

* Merge snf-manage subnet-create into snf-manage network-create

Fix bug in port tests that were introduced by latest changes in IPPool
manager.

Do not allow any action, other than 'DESTROY' in servers that are in
'ERROR' state. If the server is in 'ERROR' state then the corresponding
Ganeti instance may not exist, so all actions will fail.

Before implementing the Neutron API, each network had one IP pool that
contained the whole subnet CIDR. This changed since now we have multiple
IP Pools(with base and offset attributes) per network and this IP pools
do not contain the network, broadcast and gateway addreeses. This commit
fixes an old migration to add 'base' and 'offset' attribute to all IP
pool objects, and adds an extra step to old and not-initialized pools in
order to externally reserve those addresses.

* Print info of newly created subnet after snf-manage subnet-create

display subnet cidr when available

allow custom model id resolver

additional styles for active status indicators

Fix the default behaviour for networking of servers that are being
created. There are two settings controlling this behaviour:

* CYCLADES_DEFAULT_SERVER_NETWORKS: This setting contains list of
  networks to connect a newly created server to, if the user has not
  specified them explicitly in the POST /server API call. Each member of
  the list may be a network UUID, a tuple of network UUIDs,
  "SNF:ANY_PUBLIC_IPV4" [any public network with an IPv4 subnet
  defined], "SNF:ANY_PUBLIC_IPV6 [any public network with only an IPV6 subnet
  defined],  or "SNF:ANY_PUBLIC" [any public network].

  Access control and quota policy are enforced, just as if the user had
  specified the value of CYCLADES_DEFAULT_SERVER_NETWORKS in the content
  of the POST /call, after processing of "SNF:*" directives.

  Default value: ["SNF:ANY_PUBLIC"]

* CYCLADES_FORCED_SERVER_NETWORKS: This setting contains a list of
  networks which every new server will be forced to connect to,
  regardless of the contents of the POST /servers call, or the value of
  CYCLADES_DEFAULT_SERVER_NETWORKS.  Its format is identical to that of
  CYCLADES_DEFAULT_SERVER_NETWORKS.

 No access control or quota policy are enforced.  The server will get
 all IPv4/IPv6 addresses needed to connect to the networks specified in
 CYCLADES_FORCED_SERVER_NETWORKS, regardless of the state of the
 floating IP pool of the user, and without allocating any floating IPs.

 Default value: ["SNF:ANY_PUBLIC_IPV6"]

Also this commit changes how API handles requests that specify a public
network without specifying a floating IP address: If the request does
not contain the 'fixed_ip' attribute, the server will try to
automatically use one of the free floating IP addresses of the user
that are allocated from the specified network.

Move code relative with allocating ips and floating IPs to 'logic.ips'
module.

Remove 'floating_ips' extension attribute to POST /servers API call.
Instead use the 'fixed_ip' attribute of 'networks' attribute to specify
the IPv4 address of a floating IP. So in order to create a server
connected to a private network and a public network, the 'networks'
attribute will be:
[{"uuid": "<private-network-uuid>"},
 {"uuid": "<floating-ip-network-uuid>",
  "fixed_ip": "<floating-ip-address>"}]

Do not allow creation of new ports and reservation of floating IPs on
network that are being deleted. Currently the state of the network
changes only when the network gets deleted from all backends. So we
check if a network is being deleted by checking if the action of the
network is 'DESTROY'.

Delete backend network when network is deleted (marked as deleted=True)
in DB. Backend networks are useless as history and they may be recreated
if needed. Also fix some tests.

* Do not delete the network from the DB if it has associated floating
  IPs. This should never be the case because a check is made before
  deleting the network, however this check is added for safety.
* Do not allow deleting a network if there are still ports configured on
  on that network. Until now this check was for machines, but there may
  be ports that are not connected to any machine.
* Delete subnet IP pools when network is deleted.
* Get network in locked mode in network-remove cmd.
* Log error if trying to release an IPv4 address that does not belong to
  any of the IP pools of the associated subnet.
* Excluded deleted IPv4 addresses when reconciling IP pools.
* Do not set the network action to destroy when removing network from
  some backend.

* Add a short description of new snf-manage commands
* Beautify output of snf-manage subnet-inspect