메뉴
Synchronise Kayobe overcloud inventory templates with Kolla Ansible multinode inventory. Use when: updating for a new OpenStack/Kolla release, copying inventory group changes from kolla-ansible, and validating top-level/components/services split in Kayobe templates.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Add a new Kayobe CLI command end-to-end. Use when: adding a CLI subcommand, creating a new kayobe command, wiring up a playbook to the CLI. Touches commands.py, setup.cfg, playbook, and unit test.
Add a new Kayobe configuration variable with proper inventory defaults, operator examples, and docs. Use when: adding a config knob, introducing a new setting, creating a new component config file. Touches group_vars, etc/kayobe, and doc/source.
Synchronise Kayobe Kolla feature flags with a target kolla-ansible tree. Use when: updating for a new OpenStack/Kolla release, refreshing kolla_feature_flags, regenerating etc/kayobe kolla_enable_* examples, and checking removed services in overcloud image regex maps.
SOC 직업 분류 기준
| name | sync-kolla-inventory |
| description | Synchronise Kayobe overcloud inventory templates with Kolla Ansible multinode inventory. Use when: updating for a new OpenStack/Kolla release, copying inventory group changes from kolla-ansible, and validating top-level/components/services split in Kayobe templates. |
Last validated for 2026.1.
ansible/inventory/multinodeansible/roles/kolla-ansible/templates/overcloud-top-level.j2ansible/roles/kolla-ansible/templates/overcloud-components.j2ansible/roles/kolla-ansible/templates/overcloud-services.j2Kayobe splits multinode inventory into three parts.
Target: ansible/roles/kolla-ansible/templates/overcloud-top-level.j2
[baremetal] group.Target: ansible/roles/kolla-ansible/templates/overcloud-components.j2
[baremetal] down to this marker:# Additional control implemented here. These groups allow you to control which
# services run on which hosts at a per-service level.
Target: ansible/roles/kolla-ansible/templates/overcloud-services.j2
Prompt for the target <release> (for example 2026.1), then ensure the
kolla-ansible checkout exists under ${KAYOBE_AGENT_WORKDIR} in
kolla-ansible/.
Before cloning or reusing the checkout, source .agents/scripts/agent-environment.sh to set
KAYOBE_AGENT_WORKDIR.
If kolla-ansible/ does not exist, clone with:
source .agents/scripts/agent-environment.sh
git clone https://github.com/openstack/kolla-ansible -b stable/<release> "${KAYOBE_AGENT_WORKDIR}/kolla-ansible"
If kolla-ansible/ already exists, checkout the correct branch:
source .agents/scripts/agent-environment.sh
git -C "${KAYOBE_AGENT_WORKDIR}/kolla-ansible" status --porcelain
If this command returns any output, stop and ask the user to clean, commit, or stash changes before continuing. Abort all sync checks until the checkout is clean.
Then run:
source .agents/scripts/agent-environment.sh
git -C "${KAYOBE_AGENT_WORKDIR}/kolla-ansible" fetch origin
git -C "${KAYOBE_AGENT_WORKDIR}/kolla-ansible" checkout stable/<release>
git -C "${KAYOBE_AGENT_WORKDIR}/kolla-ansible" pull --ff-only origin stable/<release>
Review group additions/removals/renames in the source and map each change by section boundary:
[baremetal] -> overcloud-top-level.j2[baremetal] to marker -> overcloud-components.j2overcloud-services.j2Port each relevant change into the appropriate file while preserving existing Kayobe templating and comments.
When new services appear in multinode:
overcloud-components.j2 when appropriate.overcloud-services.j2.overcloud-services.j2 only.After sync, confirm intentional Kayobe differences are still present and valid,
particularly in overcloud-services.j2.
<release>kolla-ansible/ exists in repo root on stable/<release>kolla-ansible/ has no uncommitted changes before checkoutkolla-ansible/ was dirtyansible/inventory/multinode with Kayobe templates[baremetal] changes for overcloud-top-level.j2overcloud-components.j2overcloud-services.j2