Conflicts:
	slapos/tests/slapformat.py

Conflicts:
	slapos/format.py

Fix parameters order to use request()

/cc @rafael @alain.takoudjou 

/reviewed-on nexedi/slapos.core!13

When creating a TAP interface we try to add it to a bridge no mater what kind of the external interface is. Check whether it is a bridge first.

/reviewed-on nexedi/slapos.core!12

slapos/cli/entry.py, slapos/cli/format.py, slapos/format.py: Do not double the log output when "slapos node boot" failed.

Pre-check if the instance is allocated before check if it was allocated on the right place. This problem seems unreproducible on a running instance.

This is a follow up on the API change from the upgrade of facebook-sdk egg from version 0.4.0 to version 2.0.0.

On the version 0.4.0, the GraphAPI was implemented on v2.2 which is not supported anymore by facebook. With this commit we move to use GraphAPI on version v2.7.

This should reduce (significantly) the number of activities launched while searching for documents to process.

If the software installation is not deployed in 12 hours, this alarm will generate a ticket to the computer owner take action.

Initial release of the code of frontend selector demo available at http://demoapp.node.grandenet.cn

Missing form from commit d7db216a

Since the vifib_hosting was added into view skin, certain forms required the field library on vifib_web. This commit moved the forms which depends on fields which only exists on Base_viewWebFieldLibrary into vifib_web.

This commit may fix testSlapOSXHTML.test_deadProxyFields.

This message was old and it was removed.

The library was updated so the expected message changed.
Update the assertion to verbose more clearly what is wrong.

When creating a TAP interface we try to add it to a bridge no mater what kind of the external interface is. Check whether it is a bridge first.

/reviewed-on !12

slapos/cli/entry.py, slapos/cli/format.py, slapos/format.py: Do not double the log output when "slapos node boot" failed.

Pre-check if the instance is allocated before check if it was allocated on the right place. This problem seems unreproducible on a running instance.