Yaybu

----------------

- Your ``Yaybufile`` is now executed in parallel. Constraints are implied by
your metadata. If a ``Provision`` configuration needs to know the IP of a
``Compute`` node then the ``Compute`` node will be started first.

- You can use a ``GitChangeSource`` to trigger deployments. (Use ``yaybu run``
to have yaybu stay running and monitoring your repository).

- When establishing an SSH connection to deploy configuration various self-test
steps are performed. The motivation here is that after 123 we know Amazon
have AMI's that don't respect the SSH protocol. They accept an SSH connection
and allow commands to appear to execute successfully, but secretly they are
dropped. By testing that the ``false`` binary works and that ``whoami``
matches the ``user`` config option we can be more confident we are connected
to a functioning SSH server.

- Use libcloud 0.14.x. This has a bunch of bug fixes that improve how libcloud
interacts with Yaybu, including better support for using custom SSH keys with
AWS.

- Implement 'yaybu ssh' without needing ssh binary - this means we don't need
to let encrypted stuff touch the disk!

- There is now a ``renderer`` attribute on ``File``. Set it to ``json`` and it
will encode ``args`` as JSON and write to ``name``.

- Add a new ``yaybu selftest`` command. Right now this runs the yaybu test
suite. It's purpose is to ensure any py2exe/py2app/dh_virtualenv builds of
yaybu are functional and contain all required assets.

- Deprecate the ``template``, ``static`` and ``template_args`` arguments of
``File`` in favour of ``source`` and ``args``.

------------------

- Add validation for ``image`` paramter of ``Compute``. Validation is only
available for libcloud ``NodeDriver`` classes that implemented the
``list_images`` API.

- Add validation for ``size`` parameter of ``Compute``. Validation is only
available for libcloud ``NodeDriver`` clasess that implemented the
``list_sizes`` API. Where possible Yaybu will suggest alternative sizes. For
example, for the typo ``m1.micro`` it is able to suggest ``t1.micro``.

----------------

- If ``shared`` is ``True`` (the default) then Yaybu won't delete records in
DNS zone's that it didn't create. If it is ``False`` then it will remove any
records that arent declared in your configuration.

- Add support for ``MINIDNS`` (a simple local DNS server for developing
against).

- ``LoadBalancer`` part has better validation - and more useful errors if you
provide an incorrect value for an enum.

- Validate ``driver.id`` for all libcloud based parts, and use difflib to
suggest the closest driver id where possible. E.g. for ``ROUTE52`` suggest
``ROUTE53``.

- You can now pass a driver id directly as the driver parameter if no
additional arguments are required. E.g. for vmware::

new Compute as myinstance:
name: test1234
driver: VMWARE
<snip>

- Many bugfixes to the parsing of YAML-like multiline blocks

- If you install a package and your index is out of date Yaybu will implicitly
``apt-get update`` and retry the install before giving up.

----------------

- New line of development based upon the latest iteration of yay (yay3).

- Refactor provisioner backend to use "transports" (rather than starting a
remote copy of yaybu that communicates with the local yaybu)

- Refactor the libcloud code to integrate with the yay3 "graph" - so that nodes
are started on demand and ordering is implicit.

------------------

- Add a subclass of ``yay.config.Config`` that helps adapt yay for use in
Yaybu..

- Depend on at least 0.11.4 of libcloud to avoid hanging on S3 access.

- Drop dependency on boto.

------------------

- Update workaround to avoid conflicts with boto (which has a HTTPResponse
subclass).

- Remove some of the more pointless logging.