Hi all I wanted to start a thread about the current privileges model for TripleO quickstart. Currently there is the assumption that quickstart does not need root privileges after the environment and provision roles. However, this assumption cannot be valid for several use cases. In particular, I have the need of creating working directories outside the home directory of the user running quickstart. This can be useful on environments where /home partition is small and cannot be modified (so there is not enough disk space to host TripleO quickstart artifacts there). This is the change i'm working on for that use case: https://review.openstack.org/#/c/384892
As you can see, to be able to create working directories outside home directories, it will need root privileges to properly create the initial working dir and give proper permissions. This break current model but I think it could provide advantages and flexibility to the deployment. So what are your thoughts about it, shall we continue with that and change privileges model? The alternative I can see is to just limit the working directory to home directory, but then do not offer the ability to customize it, and document that restriction on TripleO quickstart properly. Best Yolanda Robla yrobl...@redhat.com Principal Software Engineer - NFV Partner Engineer __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
