The fake server has been commented so instance information page won't
appear anymore.

Currently do a simple ajax call over sinonJS server and display data
received.

Javascript : jQuery 1.7.2, Modernizr 2.5.3, SlapOs plugin
Test : SinonJS 1.3.2
CSS : Bootstrap

Also modified all tests to use slapos plugin new structure

statusEvent parameter added to request method. It define what's happen
when a non expected response occured from ajax request. Each API methods
can define it's own statusEvent but by default if no statusEvent is
provided then statusDefault is called. statusDefault can be overwritted
in the user interface application.

This tests are usefull to check if a browser support or not cross-domain
requests

Forgot to add modified files

We need to store persistence data (mainly host ip).
Both, local storage(html5) and cookies were implemented, but only one is
used in an instance.

Try to have only one library for pc browser and mobile browser

This first version contains:

The library (static/js/slapOs.js):
	A jQuery plugin which permit to discuss with a slapOs master.
	All methods are listed here: <http://packages.python.org/slapos.core/rest.html>
library tests (static/js/test.js):
	For slapOs tests, we used others libraries:
		Qunit for units tests
		SinonJs to simulate server responses (no need a real server)
a Flask server (server.py):
	A real server to principally test cross-domain requests with ajax methods
and some html files to test all of it

Instance can be destroyed when no cleanup delivery is related, but when order
line got cancelled.

This reverts commit 4b3c41d9.

This problem should be handled at recipe level.

Always Listen To Luke, He's Right. (tm)

As this is called in a loop, only try to find delivery lines for occupied
partitions.

Otherwise two queries lasting 0.3s each will be called in order to result with
None.

Delivery can be stopped by user without enough privileges.

And ExpandableItem does not have to be immediately expanded, there is alarm which
is responsible for simulation tree updates.

The KVM ordering interface has extremely simplified - customer is just one
click away from instance, so modify test to follow it.

Simplify test:

 * drop all server side scripts and rewrite AJAX calls to use already
   implemented SoftwareInstance_getStatus
 * where required implement client (browser) side analysis of data instead of
   relying on server side implementation (eg. fetching path of Software
   Instance)
 * avoid big pauses; pause just once (as client side logic to know when
   Software Instance is indexed would be cumbersome and complicated and anyway
   10s to index object is really long and shall be treat as failure)
 * flatten macros into main test for readability and beacuse they become
   oneliners