setup network interfaces
Switch backup to use explicit username, password and addresss
State EnsureAvailability call returns changes structure.
Added promotion and demotion information to ensure-availability output.
Tag-Id separation in ensure-availability.
Tags instead of ids.
Minor cleanup.
Do not quote machine names.
Updates w.r.t new names package api.
Merge pull request #39 from tasdomas/ensure-availability-output

Ensure availability command output.

Add output for ensure-availability command.

The ensure-availability command will notify the user, how many state servers
were added to the environment.

$ juju ensure-availability -n 7
maintaining machines: "0"
adding machines: "1", "2", "3", "4", "5", "6"

This is a move to github of the MP started in https://codereview.appspot.com/99670044/
Test state.Info used by Backup
Merge pull request #30 from perrito666/update_HA_doc

Added basic doc for HA

I created a doc for High Availability based on code analysis and interviewing people from the team that where involved in the design and development of this.
WIP basic commit to get Action Hooks rolling
Action Hook Info parameters and tests added to worker/uniter
Update to latest juju/names
provider/ec2: match more constrained AZ errors

Horacio reports a bootstrap failure caused by
a constrained AZ, but received a different error
message from EC2:

"2014-06-17 13:35:22 ERROR juju.provider.common bootstrap.go:119 bootstrap failed:
cannot start bootstrap instance: cannot run instances: Your requested instance type
(m3.medium) is not supported in your requested Availability Zone (us-east-1a).
Please retry your request by not specifying an Availability Zone or choosing
us-east-1e, us-east-1c, us-east-1d. (Unsupported)"

The change I've made is simply to match any "Unsupported" error
that contains the string "Availability Zone".

Fixes https://bugs.launchpad.net/juju-core/+bug/1330163
Merge pull request #117 from axw/lp1330163-ec2-moar-constrained-az

provider/ec2: match more constrained AZ errors

Horacio reports a bootstrap failure caused by
a constrained AZ, but received a different error
message from EC2:

"2014-06-17 13:35:22 ERROR juju.provider.common bootstrap.go:119 bootstrap failed:
cannot start bootstrap instance: cannot run instances: Your requested instance type
(m3.medium) is not supported in your requested Availability Zone (us-east-1a).
Please retry your request by not specifying an Availability Zone or choosing
us-east-1e, us-east-1c, us-east-1d. (Unsupported)"

The change I've made is simply to match any "Unsupported" error
that contains the string "Availability Zone".

Fixes https://bugs.launchpad.net/juju-core/+bug/1330163
Updated dependencies to include Charm package with Actions Hook Kind definition
Show relation name in status when a relation hook fails

This change takes advantage of new information that's been recently
added to the FullStatus API.

Fixes LP #1194481
cmd/juju: refactor status formatting

Status formatting functions are now part of a struct. This avoids the
need to pass the relations map through many functions when it is only
used in one (deeply nested) place.
Merge pull request #109 from mjs/1194481-relation_name_in_status_when_relation_hook_fails

Better status information when a relation hook fails

The first commit makes a  bunch of changes which take advantage of new data now available in the FullStatus API response to show the remote endpoint details when a relation hook fails. This addresses LP #1194481.

The second commit refactors the status formatting code to make some of the changes made in the previous revision somewhat cleaner.