Comment 37 for bug 1466982

I'd say we shouldn't do that - I think it makes sense to have a separate "maas" user for this in anycase, and if the openstack services don't require administrator any deployments that arent using "rax" specific maas plugins won't require this admin user.

The overhead is pretty small, just create an additional user, and I think this separates concerns so is a good idea in anycase. (My 2c at least). The new user is created with a random password as the openstack user is, so from that perspective it is the same.