Re-attach previously attached elastic IP on starting an EC2 instance which was in stopped state. Fixes #66.
Retry creation of snapshot, as it might run into a RequestLimitExceeded.
New AMIs.
When attaching an EBS volume, first wait until EBS API has the volume
in 'attached' state.  This will ensure that we catch situation where
volumes are in weird states (e.g. attaching). Use log functions for
'wait' functions to have nicer logs output.
Extended 'nixops check' to take into account the attachment status of EBS volumes.

+---------+--------+-----+-----------+----------+----------------+--------------+-------------------------------------------------------------------------------+
| Name    | Exists | Up  | Reachable | Disks OK | Load avg.      | Failed units | Notes                                                                         |
+---------+--------+-----+-----------+----------+----------------+--------------+-------------------------------------------------------------------------------+
| machine | Yes    | Yes | Yes       | No       | 0.00 0.01 0.05 |              | volume ‘vol-34baca6f’ on device ‘/dev/xvdf’ has unexpected state: ‘attaching’ |
+---------+--------+-----+-----------+----------+----------------+--------------+-------------------------------------------------------------------------------+
Allow restoring to an EC2/EBS backup for a subset of devices (e.g. just data disk on /dev/xvdf). Also added --backup-id argument as the previous positional argument was incompatible with usage of --exclude/--include.
Minor doc fix: backupid -> backup-id.
Fixes to deal with backups of previous versions of network that might have had less machines.
Added possibility to resize EBS root disk on initial deployment. This will
allow instances to be created that need a bigger root disk than the default
20GB, e.g. for a bigger nix store (buildfarm or deployment servers).

Example usage:

  deployment.ec2.ebsInitialRootDiskSize = 100;
Perform remote builds on a single machine

Fixes issue #103.
Remove import of pre-SQLite state files
nixops list: Ignore deployments with unknown resource types

This provides some forward compatibility (e.g. if the state file
contains resources from the "next" branch such as EBS volumes).
Fix weird "cannot compare values of different types" error
Refactoring: Move state file handling into a class
Move StateFile into a separate file
Add a method to get all deployments (as objects)
Sort deployments by name
nixops list: Make column alignment more sensible
nixops dump-state: New command to dump a JSON serialisation of deployments

Issue #99.
Generalize handling of --all