Package installation fails if user 'openstack' does not exists

[rsjethani]

This is quite obvious and may not be considered a bug as such. But I would like to point out here that requiring a specific 'user name' to be present for package installation to be successful doesn't seem like a good idea.

IMO following two approaches look better:

1. Create the required user a part of the installation process. This is done by many softwares. For e.g. postgresql, mysql etc.
2. Let the software be runnable/usable by any user who has required privilages/permissions.

In our case 2nd approach seems more appropriate. For e.g. I am running OpenStack as a user named 'ubuntu'. So naturally I should be able to run masakari as the user 'ubuntu'.

EDIT: I think what we want here is to have the same user running openstack and masakari. Hence while installing masakari we should be able to 'configure' the user. As a result of this someone running openstack as 'abc' user will be able to configure/install/use masakari via the user 'abc'.

[johnavp1989]

I second this. I think it makes sense for the package to create it's own user but in this case I believe the user should be masakari not openstack.