Olaf, I can't show you a concrete example, but can tell you what you should do. For example, if you want to combine ansible control host with seed you should add a host into the [seed] group the same way as described ansible control host: [seed] seed1234 ansible_connection=local The seed1234 is a seed host where now you should run ansible. For example, if you want to combine seed-hypervisor with seed you should add seed host to the [seed-hypervisor] group or create [seed-hypervisor:children] group with seed group/host inside. [seed-hypervisor] seed1234 Before doing changes you need to read: 1. https://docs.ansible.com/ansible/latest/inventory_guide/intro_inventory.html 2. https://github.com/openstack/kayobe/blob/master/etc/kayobe/inventory/groups 3. https://github.com/openstack/kayobe/blob/master/etc/kayobe/inventory/hosts.e... On Thu, Nov 28, 2024 at 8:00 PM Olaf Trygve Berglihn < olaf.berglihn@sigma2.no> wrote:

Thanks, Maxim. I think I understand the concepts, but I’m lacking a concrete workable example.

-Olaf

-- Regards, Maksim Malchuk

Olaf, This was the working example, in my case 'seed1234' is a VM somewhere, with networks connected to the 'cloud' later deployed by Kayobe. After 'ssh seed1234' the commands like 'kayobe seed host configure' then 'kayobe seed service deploy' executed on this host prepares and deploys the 'bifrost' service on it. On Mon, Dec 2, 2024 at 12:03 PM Olaf Trygve Berglihn < olaf.berglihn@sigma2.no> wrote:

I appreciate that you take the time to answer, Maxim. The docs you point to are there to read, yes. But I find they do not give much clue as how to enable the quite basic case of running the seed on the ansible control node.

In the past I have set up Bifrost/Ironic manually. Now I want to roll it automagically by Kayobe config. This is the case, and I would assume it to be a very basic one. There is no need to consume a full physical node for the seed in most cases. Thus I would think having a working example of this would be to the benefit of many prospect users of Kayobe - and not just generic description of the variables without the context and the specifics.

Doing what you suggest

# kayobe-config/etc/kayobe/inventory/hosts localhost ansible_connection=local

[seed] seed1234 ansible_connection=local

does not do the trick.

If someone could provide a working example of how to roll the seed on the ansible control node based on a working example of kayobe-config, I would much appreciate it.

-Olaf

-- Regards, Maksim Malchuk