[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog

Ian Booth ian.booth at canonical.com
Tue Jul 28 12:02:23 UTC 2015


On 28/07/15 18:26, Christian Reis wrote:
> The code which sets up the role lives here:
> 
> https://github.com/juju/juju/blame/8da94246468a4da71e62894f7a8a1bbbce112697/mongo/admin.go#L136
> 
> The roles we are setting up are:
> 
>     Roles: []mgo.Role{
>         mgo.RoleDBAdminAny,
>         mgo.RoleUserAdminAny,
>         mgo.RoleClusterAdmin,
>         mgo.RoleReadWriteAny},
> 
> Why do we need RoleClusterAdmin and RoleReadWriteAny (in particular,
> because they don't seem to be defined in the database)?
> 

They are not in 2.4 but are in 2.6+. Some time back, Juju was ported to be
compatible with mongo 2.6+ as a pre-requisite to allowing upgrading to a more
recent mongo (there are bugs not fixed in 2.4). However, the effort to get Juju
on mongo 2.6 was then stalled because of the tokumx evaluation.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949

Title:
  Juju's mongodb does not need to log every command in syslog

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions



More information about the Ubuntu-server-bugs mailing list