MaaS provider should expose the bootstrap timeout options.
Update environprovider.go

Updated bootstrap-timeout to 1800 secs by default on MAAS provider.
Update environprovider.go

Just bootstrap-timeout option will be exposed, until this default value is increased
on a per-provider basis.
Enable replicasets unconditionally

Once #82 lands, we can enable replsets
unconditionally. This makes it possible
to do limited testing of HA on the local
provider currently, and gets rid of a
code burden that we don't need.
mongo: fix vet warning

The pre-push script's vet invocation, it does nothing.
If you invoke "go tool vet .", it returns rc 0 even if
there's a warning; "go tool vet *.go" returns rc 1.
Merge pull request #89 from axw/prealloc-fix-vet

mongo: fix vet warning

The pre-push script's vet invocation, it does nothing.
If you invoke "go tool vet .", it returns rc 0 even if
there's a warning; "go tool vet *.go" returns rc 1.
Merge pull request #18 from niedbalski/bootstrap-boilerplate-timeout

MaaS provider should expose the bootstrap timeout options.

Most of the MAAS deployments takes longer times, in fact a install with d-i typically takes around 20 minutes on a good day.

Would be a good thing to at least have the timeout settings exposed ( commented ) for being
noticed by all users.

Please see reference LP: #1325891
Merge pull request #83 from axw/replset-always

Enable replicasets unconditionally

Once #82 lands, we can enable replsets
unconditionally. This makes it possible
to do limited testing of HA on the local
provider currently, and gets rid of a
code burden that we don't need.
upgradeWaiterWorker: comments and edits to improve clarity
apiserver.NewServer now takes a struct for the server params

There were already too many arguments being passed to this function
and another one is about to be added.
Added login validation to the API server

This allows an option function to be supplied when the API server is
constructed which will decide whether a login request can proceed.

This will be used to prevent agent logins during upgrades (while still
allowing client logins).