janhorstmann

> Although the [API documentation states](https://docs.opsgenie.com/docs/alert-and-notification-policy-api#create-policy) that only user and team are possible values to the responders field, the web interface definitely allows setting an escalation. I have just tested...

I went ahead and tested this locally and realised that responder type is also validated in [opsgenie-go-sdk-v2](https://github.com/opsgenie/opsgenie-go-sdk-v2). I have also [created an issue](https://github.com/opsgenie/opsgenie-go-sdk-v2/issues/118) and [a simple PR](https://github.com/opsgenie/opsgenie-go-sdk-v2/pull/119) there. With those...

Part of https://github.com/osism/issues/issues/1009

Depends on https://github.com/osism/kolla-operations/pull/52 and https://github.com/osism/defaults/pull/239 for successful run

Closes: https://github.com/osism/issues/issues/1012

> We should also add this to the osism/cfg-cookiecutter repository as default. Done in https://github.com/osism/cfg-cookiecutter/pull/610 But it still needs testing

This still needs to be tested @berendt Fo now I have used the third supplied block device as local storage. From my understanding it is only used for ceph when...

> This still needs to be tested > > @berendt Fo now I have used the third supplied block device as local storage. From my understanding it is only used...

> > This still needs to be tested > > @berendt Fo now I have used the third supplied block device as local storage. From my understanding it is only...

On my last testbed deployment the volume group for the local storage was not created. The playbook itself worked fine, but it was not created automatically. I will draft this...