Don't expose state port for openstack provider
Do not open state port. ec2 and azure.
Do not open state port. ec2 and azure.
Remove last mention of StatePort in azure provider tests
Moved requirements to the top and added table of contents.
Alter the behavior of opening and closing ports - closing a port range that is not open will not result in an error.
state: remove unit.SetMongoPassword
Only login to "admin" mongo database

We create a user in the admin database
with read/write privileges to all databases,
so there's no need to add users to each
other database. Consequently, we can remove
the mongo.SetMongoPassword function and
change state.Machine.SetMongoPassword to
just call mongo.SetAdminMongoPassword.

Tested live:
 - juju bootstrap && juju ensure-availability
 - juju upgrade-juju
Merge pull request #414 from axw/state-remove-setmongopassword

State remove setmongopassword

We create a user in the admin database
with read/write privileges to all databases,
so there's no need to add users to each
other database. Consequently, we can remove
the mongo.SetMongoPassword function and
change state.Machine.SetMongoPassword to
just call mongo.SetAdminMongoPassword.

Also removed unit.SetMongoPassword, which
isn't required anymore.

Tested live:
 - juju bootstrap && juju ensure-availability
 - juju upgrade-juju
Merge pull request #460 from TheMue/api-design-spec-toc

Moved requirements to the top and added table of contents.

Minor changes to the API Design Specification.
Merge pull request #474 from tasdomas/port_closing_restrictions

Alter the behavior of opening and closing ports

Closing a port range that has not been opened will not result in an error.

This is an outcome of the discussions on the juju-dev mailing list. Furthermore it follows the practices adopted by charm authors, where closing a port that was not open is often expected to be a noop.
Merge pull request #449 from voidspace/database-shutoff

Switch off direct database access

No longer expose port 37017 on machines as direct mongo access is no longer required.
Only set Safe.{J,WMode} in production

As of Mongo 2.6, attempting to set Safe.J
fails if journaling is disabled in mongod.
Similarly, WMode=majority will cause problems
if a replicaset is not configured. We need
to only set these in production, where those
conditions are guaranteed to be true.