Eventually, the only statefull thing on deploy host is a folder with configuration (/etc/openstack_deploy by default), which technically can be stored in git. The most troublesome part of storing it there are actually SSL certificates, because as of today there's no way to store them in an encrypted way like with ansible-vault or with hashi vault. We're planning to add such support in the next release though. But if it's fine with your policies to store certificates (and their private keys) in plain text in git, I would suggest doing that. As it's matter of couple of minutes then to spawn a new deploy host whenever needed. And moreover, you can create a CI/CD jobs/pipelines to ensure the state of deploy host or making it "ephemeral" at all. On Wed, Jun 14, 2023, 06:42 Murilo Morais <murilo@evocorp.com.br> wrote:

Hello Maksim!

I will try, thanks!

Em qua., 14 de jun. de 2023 às 09:56, Maksim Malchuk < maksim.malchuk@gmail.com> escreveu:

...

Hi Murilo,

Sure. But you should transfer the configuration and inventory to the backup host yourself.

On Wed, Jun 14, 2023 at 2:59 PM Murilo Morais <murilo@evocorp.com.br> wrote:

...

Good morning everybody!

Is it possible to use another Host as Deployment Host? For example, if a problem occurs in the "primary" Deployment Host, use a second backup to perform some kind of intervention/change.

Thanks in advance!

-- Regards, Maksim Malchuk