Synnefo

destroy action sets VM._operstate as 'DESTROYED' and does not call rapi.DeleteInstance to destroy the machine

start Machine action, for the standard view - initial commit

added switch to ajax_error, for custom messaging

minor code formatting and comment editing

less arguments for ajax_error, ajax_success

remove redundant } breaking javascript execution

initial version of notification function

Apply DRY in machines template

This includes:

• initial code for reusable ajax error and success functions

• more descriptive names for confirmation and notification overlays

• break update() in update_vms() and update_images() for less calls

added error codes for reboot action.

if the action can't happen, the user gets informed. There are three cases:

• user sends the reboot request but timeout happens. He gets informed to check his network connection
• the request can't be made. The user gets informed that the reboot action couldn't happen. We can further parse the error message to discover why this...

added TIMEOUT variable on settings.py.dist. You'll have to cp to your settings.py

initial value is 10 seconds. after this time passes, if the ui hasn't received any data, the user is informed (with js alert window at the moment) that there
are network issues (a better message might ask the user to refresh)

update status for machines according to rsapi

prepare action notifications

a few changes on the handlers/machines.html in order for the servers to appear

tables in list view are not showing when there are no machines to show

save selected view (standard/list) in cookie

use server ids in all views for reboot, shutdown and destroy calls

Same font colors in terminated and active machines

add mock post create function in last step of wizard

Merge branch 'master' of https://code.grnet.gr/git/synnefo

Conflicts:
ui/templates/list.html
ui/templates/machines.html

added create machine .post-create class on the ui

this is a static link that once pressed sends a HTTP POST request to the ganeti cluster (through api.handlers.ServerHandler.create)
and creates a virtual server. This is sort of a mockup behavior, since

• it has to be integrated with the wizard form...

send a HTTP DELETE method with the server_id once destroy is called, for a machine

api.handlers.ServerHandler.delete receives the DELETE call and id and proceeds the request through the rapi

Initial attempt to implement the ui-->RS API-->rapi architecture

main changes are:

• handlers.py: added function VirtualMachineName that returns the VirtualMachine, given it's id. added some ORM for the server list
  (commented at the moment, uncomment and add the db on settings.py to try it). added delete() on ServerHandler that calls rapi to destroy a machine...

change Hostname to Name in standard machinie view

renamed instance to machine on css etc. also added a few strings for the translation

added, but not linked, tablesorter plugin and removed sorting from selection and OS column in list view

fixed appearance of spinner in list view, transformed it to table and added sorting

removed grey delimiter between instances, instead added more spacing