Murano has hardcoded keystone user 'admin'

[Dmitry Ilyin]

Murano uses 'admin' as their user to access keystone.
If this user changes password Murano will stop to function because they will not be able to authorize.

We should create personal users with random passwords for both services and give these uses sufficent access.

[Igor Marnat (imarnat)]

This bug doesn't block QA process/release process. I'd decrease importance from Critical to High.

[Dmitry Ilyin (idv1985)]

This should be done in Puppet manifests and Heat can be used as example. It creates its own user 'heat' and uses it for keystone access.

[Dmitry Ilyin (idv1985)]

There are also plans to implement getting Murano's api and metadata URLs from Keystone endpoints.
Adding required records and creating special users could be done together.

[Dmitry Ilyin (idv1985)]

There is also a lot of refactoring in Murano's Puppet module, some fuctions have been moved to package post-install scripts and we have added syslog support to Murano services.

Perhaps it would be better to postpone all these changes untill 4.1 release.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/62704

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/62704
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=ebdf51405a73f982c9449806671fdab2e8d9f4c6
Submitter: Jenkins
Branch: master

commit ebdf51405a73f982c9449806671fdab2e8d9f4c6
Author: Dmitry Teselkin <email address hidden>
Date: Tue Dec 17 20:24:13 2013 +0400

    Custom OpenStack credentials for murano servies.

    Closes-bug: 1261457

    Change-Id: I8218ead7c6280b4a5808ab3d33463f857038ea16