Reading ports from an existing deployment is broken
Bug 1092903 - Restart shouldn't check current state as "stopped"

Stop guarding restart as closely
Add package comments, fix formatting, and cleanup references
Make the client use a "transport" abstraction to talk to server

Decouple client -> server from knowing about the particular details
of how data flows back and forth from the server.  Use a consistent
Locator interface for referring to hosts that is generic across
possible transports.
WIP gearD - Remove failed containers from runtime

* "Failed" is determined as non-zero exit code and a gearD managed container
WIP gearD - test for cleanup_failure.go
WIP gearD - Refactor from reviews

* Added retentionAge
* Removed DryRun special messaging
* Removed container prefix check
* Updated tests
Review fixes
WIP gearD - Refactor from reviews

* Skip containers with name ending in '-data'
WIP gearD - test for cleanup_failure.go

* Bad error message
Only use IPv4 address for network links for now
Add instructions for using SSH.
Update the demo JSON
Merge pull request #83 from jwhonce/wip/gear_repair

Remove failed containers from runtime
Merge pull request #82 from mrunalp/docs/ssh

Add instructions for using SSH.
Merge pull request #86 from smarterclayton/use_ipv4_only

Only use IPv4 address for network links for now
Merge pull request #80 from smarterclayton/add_transport

Add transport abstraction to geard
Separate out job implementations 1/3

Move container jobs to their own package
Separate out job implementations 2/3

Update package references to container/jobs
Separate out job implementations 3/3

Rename jobs classes to remove redundancy (jobs.JobResponse -> jobs.Response)