On 07/26/2017 07:48 AM, Markus Zoeller wrote:
> To close the loop, I've added a bug report to track this effort:
> https://bugs.launchpad.net/openstack-ansible/+bug/1706595
>
> TBH, I'm not sure when/if I can work on that. I also don't know how the
> effort prioritization works within the openstac
On 25.07.2017 16:20, Major Hayden wrote:
> On 07/25/2017 08:36 AM, Markus Zoeller wrote:
>> A short grep in 'openstack-ansible' shows that the file permissions are
>> often not set. I used these commands:
>>
>> $ grep -n -R "template:" --include \*.yml -A 5
>> $ grep -n -R "copy:" --include \*.yml
On 07/25/2017 08:36 AM, Markus Zoeller wrote:
> A short grep in 'openstack-ansible' shows that the file permissions are
> often not set. I used these commands:
>
> $ grep -n -R "template:" --include \*.yml -A 5
> $ grep -n -R "copy:" --include \*.yml -A 5
>
> IIUC, we're using 'ansible-lint' for
On 17.07.2017 23:13, Major Hayden wrote:
> On 07/04/2017 03:54 AM, Markus Zoeller wrote:
>> How do you deal with hosts which have a restrictive umask of 077
>> *before* openstack-ansible starts the setup? Do you start with the
>> default umask of 022 and opt-in later to that security hardening[1]?
On 07/04/2017 03:54 AM, Markus Zoeller wrote:
> How do you deal with hosts which have a restrictive umask of 077
> *before* openstack-ansible starts the setup? Do you start with the
> default umask of 022 and opt-in later to that security hardening[1]?
We don't test for that in the OpenStack-Ansib
How do you deal with hosts which have a restrictive umask of 077
*before* openstack-ansible starts the setup? Do you start with the
default umask of 022 and opt-in later to that security hardening[1]?
What's the development policy of openstack-ansible regarding setting
file or directory permission
