* First part of integrating join table for machines and users

* Second part of adding manyusers to one machine

* Add ldap username to users models

* Refactor test to correspond with the new use/machine system

* Add test for ldap multi user
Add front-end part
Add refactor of fake plaza

* Last part of assigning multiple users to a machine with ldap.
Start application with the administrator login, because plaza don't
support multi users.

* Rebase on master

* Force plaza to fork itself with Administrator user.
Rewording

* Add users on machine details

* Solve test problems

* Add logs to plaza.

* Change default packer URL to download new one.

* Add backend part of adding size for images.
Creating an image set his instancesSize to the default value in config.
Creating instances will take the size specified in image.instancesSize.

* Add front-end part of adding a size per image

* Fix instances size of the different drivers,
Make test corresponding to the update of machine size per image.

* Delete configurations variable, replaced by instancesSize.

* Fixe name/indentation

* Update migration script

* Add informations for users.

* Readme update

* If machine have no flavor, it is recreated.

* Fix some bug when updating size.
Add column size on machines index page, and machine details pages.
Add the possibility to change default instances size for new images.
Update nanocloud api doc.

* Add tests to validate adding instances size per image.

* Add more visibility

* eslint, update timeout on machines service units tests.

* Update wording

* Add RDP Guacamole options

* Use a loop in guacamole-client

* Litle refactoring of units tests for running them in the same time of
api tests, in the preparation of istanbul test-coverage in comming.

* Test of coveralls woth istanbul test coverage

create travis directory

Add badge

* Add istanbul.yml to exclude assets folder scanning

* update README

* Disallow ldap's users modification by flagging them.

For the front-end side, even administrator can't edit them.
Moreover the API will response a 400 Bad request.

* Disallow reset password for LDAP users.

* Security test for ldap users.

* Ldap users have not password anymore.
It forces to authenticate them against ldap for every new connection.
Also informations such as theirs first name and last name can be updated from ldap automatically.

* Fixes eslint

* Fixes security and API tests.

* Fix tests

* Include Photon code

* Ignore Photon's client libs

* Adapt code to Nanocloud's standard

* Run photon everytime the session starts

* WIP install Photon

* Include Photon's javascript webRTC libs

* Install photon by default on AWS

* Addd optinal configuration for Photon

* Launch Photon on VDI startup

* Proxy webRTC handshake through Nanocloud's backend

* Set WebRTC video tag to fit the screen

* Open port for Photon on AWS's machine

* Open firewall for Photon in AWS

* Dynamically target correct server proxying webRTC requests

* Move photon frontend internals in a dedicated util

* Open Photon port on machines on openstack

* Remove unused client example

* Re-indent AppController

* Add wonrgly deleted space

* Remove useless canva statement

* Activate/deactivate Photon from configuration page

* Rename ls in curl

* Remove explicit reference to localhost on URL

* Remove extra space

* Fix code standard

* Reject webRTC connection on error

* Fix double inputs on Photon

Disabling keyboard handling on Photon. Rely on guacamole to treat inputs.

* Precise Photon is available on AWS only

* Include bluebirds

* Authentication againt LDAP.

- Authenticate user in LDAP (if activated) if classic authentication failed.
  A new user is created in the database and can be assigned to a default group.
- Documentation for new configuation variable.
- Front-end to configure these new variable.
- Add 2 new depencies for back-end : `ldapjs` and `activedirectory`.
- API tests authentication against Active Directory.

* Update package.json and fixes linter.

* Update auto signup api tests.

* Add the stop/start options on drivers.

Stop will not destroy the machine, she will just stop taking resources.
Start on a stopped machine will rerun her, so she can be reused.

* Add the stop/start options on drivers.

Stop will not destroy the machine, she will just stop taking resources.
Start on a stopped machine will rerun her, so she can be reused.

* Add the possibility to force the borker to always assign the same vm
to a user.

This option is available only in the config file.

* Add the possibility to stop/start machines, by requesting to update it
with the right attribute (start, stop).

* Destructuring the props directly in the argument list.

* Not the job of getMachineForUser to update the the machine endDate.
So we let the startMachine function do it.

* Refresh the tests for corresponding with change in start/stop commits.

- Example for *machines* variable in configuration
- New section *configuration* with subtitles for each parts
- Add a mention to *config/local.js* for configuration not in git files
- Add a section to explain *extra* services
- There was no reason for *licence* section to be a second level section
- Add *qemu* to *iaas* possible values

Co-authored-by: Romain Soufflet <romain.soufflet@nanocloud.com>

This relies on code modification proposed in Pkgcloud forked by Nanocloud here: https://github.com/Nanocloud/pkgcloud/pull/1

While it was possible to specify a custom AMI to use as default image, the default generating password strategy would not work.
This fixes it by adding a new `awsMachinePassword` variable to specify the default password if any.

Reference all variable in README

Download price from aws endpoint.
Add a User service function for search history of a user with a specified driver.
Add a machineType key on history model.
Add a function for calculate the user credit
Add function how calculate the credit for a user
getUserCredit use getUserHistory for know the machines used
It search for price of all machine and return a global price
Add a User service function for search history of a user with a specified driver.
Add a machineType key on history model.
Add test for aws getUserCredit function
Test if the function return a valid price, using a fake price data
Add credit to user model
Use the sessionEnded function to check the credit used byt the user
and update it in the database
Initialise price with the current Aws region
Add the front end part of limt credit
Add a 402 error code when credit is exceeded

Add the history model on backend.

Add unit test for machine service.

Change the iaas on the Config service test.

AWS price

Download price from aws endpoint.
Add a User service function for search history of a user with a specified driver.
Add a machineType key on history model.

Add getUserCredit function (not finished)

Add a function for calculate the user credit

Add function how calculate the credit for a user

getUserCredit use getUserHistory for know the machines used
It search for price of all machine and return a global price

Add machine-type, and flavor

add flavor for the machine size

Add some modification for more visibility,

using JSON.parse on the data of the fake file price for the driver test.
Use an array on machine controller, for corresponding to frontend.

Test the err variable when aws endpoint is called.
Supress duplicate key.

remove all console log

Add modification test for corresponding
to new aws api/apps/connections end point

Indent

Add more visibility

User function getUserHistory return the right time of duration of the user machines history.

Aws driver add a function getAwsPrice to parse the price receved on aws endpoint.
getUserCredit now don't need to parse or serach price, it's already do in getAwsPrice.

Test cover all possibility of histories entrie.

withing lodash

getUserHistory return the different with the current time if their is no endDate
It add 1 hour only if the history duration is not exactly equal to 1 hour

Add tests for this 2 thinks

Add comment for more visiblity

Add the front part for aws price config.
If not using aws, can't configure credit limit

Add front-end part for set credit used by a user

User how not use aws, can't see their credit.

The awsPrice is now a promise,
Front end work correctly with credit
remove comment

Disable the option for admin to set credit of a user

User credit is now only for the actual month (month start the day he sign-up)

Add test to check this.
Change start/end date on all test, to match with this too.

Price calculated can't have more than 4 decimales.

remove a log

remove a </tr>

Fix bug: if credit limit is set to 0, no vdi can be up.

Fix bug initialize taking to long

Add 5 min on tests time for getUserHistory, for be sur it take the right timer