GitLab

Show in summary and details the VM that an IP is attached to.

Fix apyrgio/synnefo#254

Replace Http404 exception with AdminHttp404 exception in most of the
views. Also, write a descriptive message in each exception that will be
shown in 404 page.

Fix apyrgio/synnefo#242

The admin app has three kinds of views: detail views, table views and
charts.

* The detail views should typically be protected from XSS attacks,
  except for some edge cases which are shown here [1].
* The chart views should most probably be protected from XSS attacks,
  due to the fact that they are rendered as SVG and we don't show user
  input (except for one chart which has been sanitized)
* The list view on the other hand is easily exploitable. To fix this, we
  have created a base DataTablesView class that escapes each table row
  by default. Also, we escape each extra data that has originated from
  user input separately.

Fix apyrgio/synnefo#190

[1] https://docs.djangoproject.com/en/1.4/topics/security/#cross-site-scripting-xss-protection

Fix apyrgio/synnefo#163

Add a list view with filters for IP History.

The IPAddressLog model is associated with the following models:

* VirtualMachine
* Network
* IPAdress

Given that VMs have a 1:1 association with users, this means that the IP
log is also associated with users.

Using this information, we can show a customised IP log in the details
view of each of the above models:

* Users: we will show the IPs that they have allocated.
* VMs: we will show the IPs that have been attached to them.
* Networks: we will show the IPs that have belonged at some point to a
  network.
* IPs: We will show to which servers and networks an IP has been
  attached.

Every log entry, regardless of where it's shown, will have the
following info:

* IP address,
* VM
* Network
* User
* Active indication (if the IP is still has not been detached)
* Date of attachment to the server
* Date of release.

All log entries will be shown in chronological order and will point to
the respective associated items.

Fix apyrgio/synnefo#133.

When an associated item is shown in the summary of an item, add a link
to its details page.

Fix apyrgio/synnefo#140

Fix apyrgio/synnefo#137

The current code structure was leading to circular imports of the files
that are responsible for each entity. To solve this, we must break each
of those files to smaller pieces.

The pieces that each of the files are broken into are:

* views: The functions that implement the views for each entity.
* actions: The functions that have to do with the actions on each
  entity.
* filters: The functions that have to do with filtering.
* utils: Auxiliary functions.

With the new structure, the users' views can import the vms' actions and
the vms' views can import the users' actions without worrying about
circular imports.

According to the decision of the GRNET Board of Directors,
switch license to GPLv3.

This commit will be propagated to the release
and master branches based on git flow, and the next
release will be licensed as GPLv3.

Drop support for Django 1.2. Remove compatibility code that were used in
order to support Django 1.2 and 1.4. Finally update django documentation
link in the docs.

- Individualize userdata api by placing module under synnefo namespace and
  urs under it's own USERDATA_PREFIX

- Removed /userdata/quota view in respect of astakos quotas api delegate
  views served in the same urls used by astakos api (/astakos/api/quotas,
  /astakos/api/resources). Base url is configurable using the
  UI_ACCOUNTS_API_URL (defaults to /astakos/api).
- Refactored quotas js client to use backbone Collection/Model
  mechanisms.
- Refresh quotas using the common api update mechanism used by vms and
  networks (deprecated UI_QUOTAS_UPDATE_INTERVAL setting)
- Extended main view initialization steps to include quotas/resources
  loading before the initial layout renedring

Mimic pithos app/ui feedback handling to avoid duplicating boilerplate
code.

New settings:
CYCLADES_USER_FEEDBACK_URL

Deprecated (removed) settings:
FEEDBACK_CONTACTS
FEEDBACK_EMAIL_FROM

ui inititalization process now includes a call to the introduced
`ui.views.userquota` view which returns a json representation of available user
quota limits. Quota information is used across ui to prevent user from the
effort of trying to allocate additional resources.

to avoid conflicts with other applications named urls.

- Also removed static files serve view (now added by webproject if
  needed)

since more than one packages exist in repository root

- Moved ui/invitations app static files on their own dir
- Reorganized static directories based on asset type (css,js,images)
- Dynamic/configurable static files urls
- Version symlink added
- Other minor static files related changes

HTML/Javascript code refactoring towards an MVC-like design.

Refs #671

Refs #421

Merge branches api-current and ui-0.4:
    * Fix merge conflicts
    * Fix minor bug in reconciliation mgmt command
    * Add comments in settings.py.dist
    * minor PEP8 fixes