When a new key is registered, it is registered on req.environ in a
dict called 'soi:public_keys'.
The snf_create_server method pulls the keys from there and handles
the way they are injected into the VM.

When launching a new docker container, the user can now set the
repo branch to be deployed. Defaults to "develop".

Rename "paste_deploy/" to "ci/" and add a Dockerfile to create an
image which runs the snf-occi service.
Write instructions in ci/README.md on how to build and run the
container.
Update the docs and fix emerging bugs and typos.

Dockerfile version is now 0.3

The request we have tested so far is a server creation with as few
parameters as possible.

"image info" and "flavor info" implementations are trivial and are
implemented by these methods:
* snf_get_flavor
* snf_get_info

"server info" is implemented by this method:
* snf_get_server
but also requires the following side implementations:
* snf_get_server_volume_links (volume attachments)
* snf_get_server_net_attachments (server nics)

Modifications in the json response template had to be applied in
in snf_get_server and snf_get_server_net_attachments to achieve
OpenStack compatibility

Introduce two new modules:
compute.py: replacement functions will be held there, as well as
    the map of replacements
utils.py: common methods that can be used out of context

Use image id for OS_TPL, flavor id for RESOURCE_TPL
Add a "server info" field in the basic testing script