+2

On Tue, Apr 18, 2023 at 4:35 PM Damian Dabrowski damian@dabrowski.cloud wrote:

+2

On Tue, Apr 18, 2023 at 9:34 PM Amy Marrich amy@demarco.com wrote:

...

+2 from me

On Tue, Apr 18, 2023 at 2:05 PM Dmitriy Rabotyagov noonedeadpunk@gmail.com wrote:

...

Hi everyone,

I'm pleased to propose Neil Hanlon as OpenStack-Ansible Core Reviewer. Neil has helped us a lot lately with maintenance of RHEL-like distros

both CentOS Stream and Rocky Linux, and basically has brought in support for the last one.

Neil is present at meetings and always is responsive in IRC. At the same time they were providing useful reviews lately [1]

If there are no objections, I will add Neil to the team on 25th of April 2023. Until then, please feel free to provide your feedback/opinions on the matter.

[1]

https://www.stackalytics.io/report/contribution?module=openstackansible-grou...

...

Hey there,

Since no objections were raised, I warmly welcome Neil to the team!

вт, 25 апр. 2023 г. в 09:21, Jonathan Rosser jonathan.rosser@rd.bbc.co.uk:

This would be great. +2 from me.

Jon.

On 18/04/2023 20:00, Dmitriy Rabotyagov wrote:

...

Hi everyone,

I'm pleased to propose Neil Hanlon as OpenStack-Ansible Core Reviewer. Neil has helped us a lot lately with maintenance of RHEL-like distros

both CentOS Stream and Rocky Linux, and basically has brought in support for the last one.

Neil is present at meetings and always is responsive in IRC. At the same time they were providing useful reviews lately [1]

If there are no objections, I will add Neil to the team on 25th of April 2023. Until then, please feel free to provide your feedback/opinions on the matter.

[1] https://www.stackalytics.io/report/contribution?module=openstackansible-grou...

Hi, Roger,

No, unfortunately we don't have any in-house way to deploy redis, as it's usage area is quite limited. Moreover there're more storage/incoming drivers that are supported by Gnocchi, including Ceph, S3 and just MySQL.

But roles should not be aware of LXC containers or anything OSA specific as you can create any arbitrary containers whenever needed with default OSA roles and then using a playbook execute any third-party roles against these LXC containers. You can find some documentation on how inventory works with OSA here: https://docs.openstack.org/openstack-ansible/latest/reference/inventory/unde...

So, basically what you should do to create extra set of containers for Redis: 1. Create /etc/openstack_deploy/env.d/redis.yml with content: component_skel: redis: belongs_to: - redis_all container_skel: redis_container: belongs_to: - redis_containers contains: - redis physical_skel: redis_containers: belongs_to: - all_containers redis_hosts: belongs_to: - hosts 2. In /etc/openstack_deploy/openstack_user_config.yml (or in a separate file under conf.d) define where containers should reside, ie: redis_hosts: infra1: ip: 172.29.236.11 infra2: ip: 172.29.236.12 infra3: ip: 172.29.236.13 3. Execute playbook: openstack-ansible playbooks/lxc-containers-create.yml --limit redis_all,lxc_hosts

Once this is done, you can simply deploy redis to these containers, by targeting the redis_all group from corresponsive playbook. Hope this helps:)

пн, 1 мая 2023 г. в 19:46, Roger Rivera roger.riverac@gmail.com:

Hello Community,

I was wondering if there is an Ansible playbook from OSA to install a Redis cluster to be configured as incoming measure for Gnocchi?

There is this deployment example that points to an external Ansible role. Unfortunately, that role does not make use of LXC containers to keep consistency with OSA deployment on the infra nodes.

We want the infra nodes to also host the Redis/Sentinel master-slave cluster, if possible.

Questions:

Can anyone steer us in the right direction to do Telemetry with Gnocchi, Ceph and Redis with an Openstack-Ansible deployment with LXC containers? Is there a better approach to use Redis as an incoming measure storage for the gnocchi installation?

Any suggestions, guidance will be appreciated.

-- Roger Rivera