Epic OSPRH-18266 has a child ticket: "OSPRH-18267 create 17.1 configuration with BGP at controlplane only".

But we need to investigate what else is needed to create a job that tests adotion with a "BGP at controlplane" 17.1 environment. It may mean changes in:

• ci-fmw
• https://github.com/openstack-k8s-operators/data-plane-adoption/
• architecture?
• install_yamls?
• To create new scenario files, ansible playbooks and/or zuul jobs under ci-fmw-jobs

The job should create a RHOSP/tripleo 17.1 environment configuring BGP at controlplane.

The existing 17.1 BGP jenkins jobs cannot be used because the adoption job will run on zuul.

Scripts/playbooks from the repo bgp-playbooks-templates could be used to deploy spines and leafs (this is what 17.1 BGP jenkins jobs use).

Simplifying as much as possible the topology used will help to avoid capacity issues, due to the high number of nodes that will have to run on the test server. For example, if freeipa could be removed from the 17.1 source environment, that would help. We should use as less OCP nodes as possible (no master vs workers separation).

The spines and leafs will have to connect to:

• controller nodes (only used for 17.1)
• ocp nodes (only used for rhoso)
• compute nodes (used for both 17.1 and rhoso, they are updated during adoption)
• not sure if controller-0 and undercloud will have to connect to spines&leafs too or not

ovn-bgp-agent is not needed because we are not testing BGP at dataplane, but frr is needed for BGP at controlplane. No frr dataplane adoption code was implemented. I am not sure if something will be needed for this.

The DoD for this ticket is to collect all the required information and generate the tickets (stories) needed to complete the parent epic, i.e. to create a "BGP at controlplane adoption job".