[zaphod-v0.4][issue-0.4-002]: Make test_copy_file more robust.

FEATURE
issue-0.4-002-scp-support

SYNOPSIS
[modified]m42/test/test_zaphod.py: Make test_copy_file more robust.

DETAILS
Use with closing to close an open ssh connection.
[zaphod-v0.4][issue-0.4-024]: Initial specification and demo walk though.

FEATURE
issue-0.4-024-spec-and-design-docs

SYNOPSIS
[new]doc/.gitignore: Gitignore file for the doc directory.
[new]doc/demo.txt: This is the initial demo walkthough.
[new]doc/spec.txt: This is the initial specification document.

DETAILS
The doc directory will contain all documentation about using and
implementing zaphod.

Going forward, zaphod will follow a practice of documenting the design
of a feature before it is implemented. The overall architecture and
design roadmap will be documented here. For every new feature
implemented. The specification and design documents will be updated.
As it currently stands this specification and design does not match the
actual implementation. The goal of further updates to these documents
will be to bring the spec and design documents eventually. This branch
will exist as long as the actual design and implementation do not match
the design documented here. After that further changes to the design of
zaphod will be update on a new issue branch.
[zaphod-v0.4][issue-0.4-024]: HTML design specification inital checkin.

FEATURE
issue-0.4-024-spec-and-design-docs

SYNOPSIS
[new]doc/design-specification.html: Table of contents for the design spec.
[new]doc/zaphod.css: The spec style sheet.

DETAILS
This check in creates the design-specification document. The document
will be updated incrementally in feature sprints.
[zaphod-v0.4][merge]: Branch issue-0.4-024-spec-and-design-docs into develop.

FEATURE
issue-0.4-024-spec-and-design-docs

SYNOPSIS
[new]doc/.gitignore: gitignore file for doc directory.
[new]doc/demo.txt: Demo walkthrough instructions.
[new]doc/design-specification.html: Initial checkin with table of contents.
[new]doc/spec.txt: Text spec. (Temporary. To be replaced by design-specification.html)
[new]doc/zaphod.css: CSS file for styling the design specification document.

DETAILS
This merges the template for the design specification from the
issue-0.4-024-spec-and-design-docs branch into the develop. Feature
branches must update the design document as part of the implementation
process for features. (Preferably before implementing a feature!)
[zaphod-v0.4][issue-0.4-024]: Initial specification and demo walk though.

FEATURE
issue-0.4-024-spec-and-design-docs

SYNOPSIS
[new]doc/.gitignore: Gitignore file for the doc directory.
[new]doc/demo.txt: This is the initial demo walkthough.
[new]doc/spec.txt: This is the initial specification document.

DETAILS
The doc directory will contain all documentation about using and
implementing zaphod.

Going forward, zaphod will follow a practice of documenting the design
of a feature before it is implemented. The overall architecture and
design roadmap will be documented here. For every new feature
implemented. The specification and design documents will be updated.
As it currently stands this specification and design does not match the
actual implementation. The goal of further updates to these documents
will be to bring the spec and design documents eventually. This branch
will exist as long as the actual design and implementation do not match
the design documented here. After that further changes to the design of
zaphod will be update on a new issue branch.
[zaphod-v0.4][issue-0.4-024]: HTML design specification inital checkin.

FEATURE
issue-0.4-024-spec-and-design-docs

SYNOPSIS
[new]doc/design-specification.html: Table of contents for the design spec.
[new]doc/zaphod.css: The spec style sheet.

DETAILS
This check in creates the design-specification document. The document
will be updated incrementally in feature sprints.
[zaphod-v0.4][issue-0.4-002]: Refactor content checking code in test_copy_file.

FEATURE
issue-0.4-002-scp-support

SYNOPSIS
[modified]m42/test/test_zaphod.py: check_contents_match to check correct copy.
[modified]m42/test/zaphodtestutil.py: Implement check_contents_match.

DETAILS
Refactored code in test_copy_file to check if contents match into a
separate file. This makes the content matching code reusable for
other tests.
[zaphod-v0.4][issue-0.4-002]: Detailed design documentation.

FEATURE
issue-0.4-002-scp-support

SYNOPSIS
[modified]doc/design-specification.html: Define copy_file + use syntaxhighlighter.
[modified]doc/zaphod.css: Styling for parameter tables and code signatures..

DETAILS
Definition and expected behavior of copy_file. Note that the actual
functionality may be refactord into a better design at a later stage.
[zaphod-v0.4][merge]: issue-0.4-002-scp-support into develop.

FEATURE
issue-0.4-002-scp-support

SYNOPSIS
[modified] doc/design-specification.html: Resolved merge conflict.
[modified] doc/zaphod.css: Resolved merge conflict.
[modified] m42/test/test_zaphod.py: Implemented test_copy_file.
[modified] m42/test/zaphodtestutil.py: Implemented check_content_match.

DETAILS
This is a full implementation and test, and documentation of the copy_file
method. Previous checkins did not have roubust, reusable unit test. This
checkin resolves this.
[zaphod-v0.4][issue-027]: Increase ssh connection timeout.

FEATURE
issue-0.4-027-increase-ssh-connection-timeout

SYNOPSIS
[modified]m42/zaphod.py: Increased ssh connection timeout in Zaphod._login.

DETAILS
On initial testing on a cold slow machine (i.e. one where VM and OS code
has not been paged into memory by previous useage.), there SSH errors
out reading protocol banners when connecting to a VM. This can be avoided
by increasing the connection timeout. The timeout has been arbitrarily
increased to 30 seconds.
[zaphod-v0.4][issue-028]: Mid-level provisioning spec.

FEATURE
issue-028-design-provisioningissue-028-design-provisioning

SYNOPSIS
[modified]doc/design-specification.html: Mid-level provisioning spec.
[modified]doc/zaphod.css: Various improvements to support the spec.

DETAILS
This checkin contains the mid-level provisioning spec. It describes
the featues of the provisioning sytem at the level of provisioning
stages. The details of each provisioning state are NOT explored
in this spec.
[zaphod-v0.4][merge]: issue-028-design-provisioning into develop

FEATURE
issue-028-design-provisioning

SYNOPSIS
[modified]doc/design-specification.html: Mid-level provisioning spec.
[modified]doc/zaphod.css: Various improvements to support the spec.

DETAILS
This merge pulls in the current design of the provisioning system,
from the issue-028-design-provisioning topic branch into develop.
This will allow implementation branches for separate stages
of the provisioning system to edit the design spec for the design
specific to a given stage. Further high level design document
changes will continue to be made on the issue-028-design-provisioning
branch.