RDO Cloud jobs move to zuulv3 native is blocked by legacy dependencies

[Ronelle Landy]

https://trello.com/c/TVsZ3Ut6/877-clean-up-rdo-sf-legacy-code-after-zuulv3-migration describes much of the work done so far to move RDO Cloud job to run on zuul v3 in a more native workflow.

The aim is to reparent the RDO Clould job to tripleo-ci-base https://github.com/openstack-infra/tripleo-ci/blob/master/zuul.d/base.yaml#L7 (or some child job thereof).
The process requires changes to infa-related repos, rdo-jobs, config, etc. and well as openstack-infra/tripleo-ci, openstack/tripleo-quickstart and openstack/tripleo-quickstart-extras.

The process has been somewhat slow going as the changes to the above repos have to be merged and then a request has to be made to the rdo infra team to reconfigure rdo zuul to see what issues shake out.
The errors often appear one after the other as the former issue gets fixed. The RDO-CI has little visibility into the reconfigure process.

We are waiting on the reviews below, for as of now, to test a reconfigure:

https://review.openstack.org/#/c/596422/ Remove inclusion of legacy playbook in tripleo-ci-base

(and tangentially ... https://review.openstack.org/#/c/581488 to fix the reproducer issues).

Getting rid of any legacy code is required before we can continue with other refactoring work on the CI functionality like toci-gate-test. As such, this is a blocker.

[wes hayutin (weshayutin)]

Setting as promotion blocker as a FYI to production chain council and members. If we don't get RDO-CI jobs migrated to native zuulv3 in the near term this will become a blocker when we need jobs for the next release

[Ronelle Landy (rlandy)]

This is blocking - we would to write or configure this file to not use /etc/nodepool/* files:

https://github.com/openstack/tripleo-heat-templates/blob/master/ci/common/net-config-multinode-os-net-config.yaml#L136

[Ronelle Landy (rlandy)]

Copying IRC conversation for tracking

<EvilienM> rlandy: maybe we could read from the ENV directly

<mwhahaha> rlandy, EvilienM: we'll probably need to do is rewrite the network config and pass that information in elsewhere

<rlandy> EvilienM: mwhahaha: ok - whatever we can do here would be helpful. The reliance on /etc/nodepool is blocking rdocloud jobs transition away from legacy

<panda|rover> EvilienM: that value is now provided with a zuul variable. We have that variable, we just have to pass it to you in some way, we can decide its format

[Ronelle Landy (rlandy)]

Adding reviews to remove /etc/nodepool references in THT
(starting with master - will backport if master works):

https://review.openstack.org/#/c/599739/ DNM - WIP - Remove usage of /etc/nodepool

https://review.openstack.org/#/c/599076/ WIP - Add params for network_config_hook

^^ per marios suggestion

[Ronelle Landy (rlandy)]

Decision was to leave THT updates until later - too involved.
https://review.openstack.org/#/c/596422/38/playbooks/mock-etc-nodepool/pre.yaml will create the /etc/nodepool/* files in the mean time.
the CI-related respo have been updated (with reviews outstanding) to remove references to /etc/nodepool

[Ronelle Landy (rlandy)]

Making progress - we have some passing jobs on test project. Looking to move some to rdo-jobs next week

[Ronelle Landy (rlandy)]

legacy jobs have been mobved to zuulv3 base - with teh exception of rdoinfo job - for discussion later