Merge pull request #1066 from wallyworld/validate-joyent-credentials

Validate creedentials are correct before attempting to bootstrap a joyent environment

Partially fixes: https://bugs.launchpad.net/bugs/1362072

In a similar vein to what was done for ec2 etc, validate joyent credentials prior to bootstrapping.

Tested live.
Merge pull request #1067 from wallyworld/validate-joyent-credentials-1.21

Merge pull request #1066 from wallyworld/validate-joyent-credentials

Validate creedentials are correct before attempting to bootstrap a joyent environment

Partially fixes: https://bugs.launchpad.net/bugs/1362072

In a similar vein to what was done for ec2 etc, validate joyent credentials prior to bootstrapping.

Tested live.
Add the .reviewboardrc file to help with backporting.
Merge pull request #1068 from wallyworld/generate-metadata-delete-option

Add --clean option to tools metadata generation

Fixes: https://bugs.launchpad.net/bugs/1390250

Add a --clean option to "juju metadata generate-tools"

This will delete any exiting metadata for the specified stream, so that new metadata replaces instead of merging. Metadata for other streams is untouched.
provider/azure: verify credentials during Prepare

Verify credentials while preparing environment configuration
for Azure, and display a helpful error message on failure.

Fixes https://bugs.launchpad.net/juju-core/+bug/1362072
Fix copy/paste
Merge pull request #1072 from wallyworld/generate-metadata-delete-option-1.21

Merge pull request #1068 from wallyworld/generate-metadata-delete-option

Add --clean option to tools metadata generation

Fixes: https://bugs.launchpad.net/bugs/1390250

Add a --clean option to "juju metadata generate-tools"

This will delete any exiting metadata for the specified stream, so that new metadata replaces instead of merging. Metadata for other streams is untouched.

Also, drive by fix for go vet error.
Merge pull request #1073 from axw/lp1362072-azure-verify-credentials-1.21

provider/azure: verify credentials during Prepare (backport)

Verify credentials while preparing environment configuration
for Azure, and display a helpful error message on failure.

Fixes https://bugs.launchpad.net/juju-core/+bug/1362072
Merge pull request #1071 from ericsnowcurrently/1.21-reviewboardrc

Add the .reviewboardrc file to help with backporting.
Merge pull request #1075 from mjs/1382751-prevent-non-subordinate-container-scoped-relations

1382751 prevent non subordinate container scoped relations

This fixes LP #1382751.

Container scoped relations are now only allowed if there's exactly one subordinate service involved. This prevents conditions that should never have been allowed. The Uniter errors and exits when it encounters relations without a subordinate service on one side.

InferEndpoints now ignores container relations unless there's exactly one subordinate service involved.
Merge pull request #1054 from anastasiamac/mongo-on-multi-socket-nodes-Bug1350337

Wrapping mongod for NUMA machines. Bug 1350337

Bug https://bugs.launchpad.net/juju-core/+bug/1350337
Merge pull request #1079 from anastasiamac/multinode-numa-fix

Merge pull request #1054 from anastasiamac/mongo-on-multi-socket-nodes-Bug

1350337

Wrapping mongod for NUMA machines. Bug 1350337

Bug https://bugs.launchpad.net/juju-core/+bug/1350337

PR 1054 from master.
Remove the new backups CLI.

While the rest of the backups implementation is complete, a key
component (restore) has not landed in time for 1.21.  The existing
restore plugin *should* work with the new backups code, but that has
not been tested at all.  Regardless, it doesn't make a lot of sense
to mix the old and new backups in that way.

Consequently we are effectively disabling the new backups capability
in 1.21.  Completely excising the new backups implementation would
introduce too much risk.  Removing just the CLI portion is sufficient
to effectively eliminate exposing the new backups implementation to
users.  The new API facade is still in place and the various packages
are still there in the code, but that is not likely to be an issue.

This code will remain in the master branch (for 1.22 and forward).
Only *unregistering* the backups CLI is necessary.
Merge pull request #1082 from ericsnowcurrently/1.21-excise-backups

Remove the new backups CLI.

While the rest of the backups implementation is complete, a key
component (restore) has not landed in time for 1.21.  The existing
restore plugin *should* work with the new backups code, but that has
not been tested at all.  Regardless, it doesn't make a lot of sense
to mix the old and new backups in that way.

Consequently we are effectively disabling the new backups capability
in 1.21.  Completely excising the new backups implementation would
introduce too much risk.  Removing just the CLI portion is sufficient
to effectively eliminate exposing the new backups implementation to
users.  The new API facade is still in place and the various packages
are still there in the code, but that is not likely to be an issue.

This code will remain in the master branch (for 1.22 and forward).
merge PR 1048
fixes to make stuff compile
fix merge error
Merge pull request #1083 from natefinch/merge-1048

Merge 1048

This merges PR #1048, which is a prerequisite for merging PR #1075 which is needed for 1.21.  The merge for 1075 will come after this one.
Merge pull request #1077 from wallyworld/backport-subordinate-relation-fix

Merge pull request #1075 from mjs/1382751-prevent-non-subordinate-contai...

...ner-scoped-relations

1382751 prevent non subordinate container scoped relations

This fixes LP #1382751.

Container scoped relations are now only allowed if there's exactly one subordinate service involved. This prevents conditions that should never have been allowed. The Uniter errors and exits when it encounters relations without a subordinate service on one side.

InferEndpoints now ignores container relations unless there's exactly one subordinate service involved.