It sometimes happend that buildout unistall/install the section with this recipe,
which remore storage_path file and recreate it. In most of cases this is not wanted
because the recipe is used to generate password, so that password will change when this
happend.
To prevent buildout to remove storage_path, I introduced a new option 'create-once'
which, when set to True (the default value) will not let buildout play with storage_path file
by returning None in install recipe. Also install won't remove the file if the size is not 0.

/reviewed-on !129

Also allow to change promise timeout by editing check_url_PROMISE_TIMEOUT file

No need to parse. This fixes several issues:
- key comments were messing up everything
- sometimes keys were repeated
- no way to remove key

The 'pidfile' parameter is passed to 'createWrapper' method in order to
avoid concurrent calls.

Instead, of that, the notifier wrappers will run the scripts several more times in case of failures
This is better than silent failures.

Instead, of that, the notifier wrappers will run the scripts several more times in case of failures
This is better than silent failures.

*  Includes a new recipe to get a random time
*  Moves generatepassword and generatemac into random.py
*  Fixes up some recipe, as the creation of a "random.py" file may collide
   with the import of the standard library random

This reverts commit 2b0c61d9.

Reading the .installed.cfg file is not the correct way of storing values. The publish_early
recipe should be used instead

This reverts commit 8787716d.

Same issue of avoiding publishing private code, this time with nothing published by default.

Ivan, can you quickly try this apache config and give your opinion if it acceptable that you add .htaccess in the code to be tested ?

/cc @jm @Tyagov @rafael

/reviewed-on !113

It uses Appium, which provides a Selenium WebDriver compatible API
to remotely control an iOS (or Android) simulator. This way we can
run tests in both mobile OSes without big changes to the current
test code and infrastructure.

This allows user to customize in the test suite module on which
system they want to run the tests (Firefox or iOS) through the
slapos parameters. In iOS, for example, it's possible to change
the iOS version and it's required that the user give the SauceLabs
credentials in form of user:apikey using the `appium_server_auth` parameter.

An example of parameters to use in a test suite:

```
{
  "mariadb": {
    "relaxed-writes": true,
    "mariadb-relaxed-writes": true,
    "test-database-amount": 30
  },
  "target": "iOS",
  "target-version": "9.3",
  "target-device": "iPhone Simulator",
  "target-browser": "Safari",
  "appium-server-auth": "username:auth_token",
  "test-suite" : "jio" ,
  "test-url": "jio-repository.git/test/tests.html"
}
```

  If pidfile is empty, the pgrep will fail forever until the pidfile
  is removed, so check if it exist and it is not empty.

In the case of hellorina SR, the following section generated invalid command:

[proxy]
command-line = {{ python_location }}/bin/python2.7 {{ rina_proxy }} ${server:instance-guid} ${:ipv6} ${:port}
...

This value can be used as a unique identifier within the cloud.
It was already available for the requesting partition ('request' recipe).

/reviewed-on !101

Add a class SlapConfigParser which overrite ConfigParser.write method to fix parse problem when
configuration like:
[section]
foo += bar

is included in buildout file. softwaretype recipe will generate
buildout file with foo + = bar because ConfigParser doesn't reconize +=
delimiter and read key as "foo +", value as "bar".
Then ConfigParser.write method generate

[section]
foo + = bar
...

This is invalid with buildout version 2

/reviewed-on !100

Buildout expects all needed sections to have been accessed during the
sectoin initialisation pass. It does not like having them accessed during
the "install" pass, and emits a very cryptic error:
  While:
    Installing publish.
  Error: Missing option: publish-early:__buildout_signature__