GitLab

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

* Add snf-manage subnet-inspect
* Update return_end and return_start function in IPPool

handle classes which do not define element for model view to be rendered to

major refactoring on network/ip's step view is on the way

for floating ip's and public keys tabs

extract title from data-hover-title

- Use neutron API
- Display as an additional tab within the main content area of the app instead
  of using layout view.

based on introduced neutron models/collections

includes models/collection objects for Network, Port, Subnet, FloatingIP
neutron APIs.

- pre/post hide/show hooks
- set parent_view attribute if set in options