Creating new repo for CI's but still using os-ext-testing.

[AbhiS1892]

Hi Ramy,

I found out in your repo that we had to create our own repo using [1]. But the fact is while installing master we are using your repo only [2]. So, don't we have to put all the files required in our repo only.

[1] https://github.com/rasselin/os-ext-testing#new-712015-this-repo-is-being-migrated-to-use-project-config-and-puppet-openstackci
[2] https://github.com/rasselin/os-ext-testing#set-up-your-data-repository

[rasselin]

Hi Abhi,

Currently the jenkins jobs and zuul files need to be in a new project-config repo. These get pulled in automatically via [1].

Since nodepool has not yet been migrated, you'll need to keep the nodepool.yaml file in the os-ext-testing-data repo. So in the current state, you'll need both. Long term wise, you'll only need the project-config repo, which is in line with what openstack-infra is doing.

[1] https://github.com/rasselin/os-ext-testing/blob/master/puppet/install_master.sh#L138

[rasselin]

FYI, nodepool is now supported to be part of project-config. Let me know if you have any issues.