Synnefo

Also, both the command-line and the web tool should produce an initial, overall, dashboard-like view with vital system stats.

For the command-line tool, explore the addition of a "stats" category.
For the web-based tool, explore the addition of an initial dashboard-like display.

The stats could include total number of VMs, number of users, backend Disk (free/used/total), backend Memory (free/used/total), distribution of VMs per Image, number of users, number of total invitations, perhaps a top-10 of invitation senders, and other links to custom infrastructure. The backend numbers can be retrieved over RAPI.

A first implementation has been submitted to the admin branch (visible at /admin). However we need a way to restrict access to everything under /admin in order to be able to go into production.

A few more things:

• VERY IMPORTANT: Make sure to verify every deletion, since this can be disastrous with Django's cascading deletes. I accidentally a flavor, and all the VMs went away with it too.
• This also applies to the snf-admin command line tool, the warning for deleting a user should apply almost everywhere [--force, etc].
• it would be great if whenever a foreign key value is needed a combobox or some form of autocompletion was used, so the user may only input valid values.

Also:

• there should be a way to see all Servers, deleted=True or not.
• there should be a way to filter Servers [later, when we have custom Images, on Images too], initially based on the owner.
• How many Servers may be displayed? Support for pagination?

Also:

• image register operations should have a mandatory type argument, "dump", "ntfsclone" or otherwise. When the administrator registers a new image, he/she needs to specify its type. This applies both to the command-line and web admin tool.

For future reference, Django 1.3 allows finer control of what happens when you delete rows that have foreign keys:

https://docs.djangoproject.com/en/1.3/ref/models/fields/#django.db.models.ForeignKey.on_delete