WARNING - WIP - NOT FOR GENERAL USE - How to reproduce a job result using the Zuul-based reproducer playbooks and script

Prior to running the Zuul-based reproducer, the following setup steps are needed - ( only need to be done once per local system):

• Create a clouds.yaml - for example:

  mkdir -p ~/.config/openstack
  vi ~/.config/openstack/clouds.yaml
  clouds:
    rdo-cloud:
      identity_api_version: 3
      region_name: regionOne
      auth:
        auth_url: https://phx2.cloud.rdoproject.org:13000/v3
        password: xxxxxxx
        project_name: user_name
        username:  user_name
        user_domain_name: Default
        project_domain_name: Default
      regions:
        - name: regionOne
          values:
            networks:
              - name: 38.145.32.0/22
                routes_externally: true
              - name: private
  
  
  

• Test your cloud.yaml by running:

  
   openstack --os-cloud rdo-cloud image list
  
  

• Note that you will need a network named 'private' in the tenant connected to an router that is connected to the external network.
• Create an ssh key pair without a pass phrase:
• The ssh key pair is configurable - see variables ssh_path
• user_pri_key. The default key is:~/.ssh/id_rsa[.pub]
• Note: Reference FAQ below when creating ssh keys, some keys fail when used w/ gerrit
• Check that you have access to the publicly shared nodepool images: There should be one image for CentOS 7, and one for Fedora 28.

Import the nodepool images to your tenant:

openstack --os-cloud rdo-cloud image set --accept 6a6d23d7-65e7-43ea-9307-71b2e17d2ead
openstack --os-cloud rdo-cloud image set --accept 88006cd1-d089-4bd3-b70a-8cbc7eb32f63

• wget the reproducer-zuul-based-quickstart.tar file.
• Note that the launcher-env-setup-playbook.yaml will set up clone repos and set up 'roles', 'playbooks', and 'library' directories from which the tasks will be executed.
• Once the files are extracted from the archive, you can run the Bash script with the various options. Run the script with --help option to output a list of available run options.

The Bash script is not required although it is the supported path. The playbooks can be run directly using ansible-playbook. The Bash script contains some package installation and Docker user/group setup that you will need to cover prior to running the playbooks directly. Please see the Bash scripts for details, especially if you are running the reproducer for the first time on teh local environment. The playbooks can be run as follows:

• ansible-playbook ./launcher-env-setup-playbook.yaml
• ansible-playbook ./launcher-playbook.yaml $OPTIONS

The launcher-playbook.yaml includes comments on how to run the playbook with the same options listed in the Bash script section above.

• The Bash scripts runs with --tags all passed to the launcher-playbook.yaml.
• After the initial docker setup has run, it is not necessary to run through those setup steps for every reproducer. The launcher-playbook.yaml can be run with --skip-tags start after the initial run.

The launcher-playbook.yaml will create and push a job to a test1 testproject repo in a temp directory. This job will start and the related Zuul infrastructure logs can be viewed in:

cd ~/tripleo-ci-reproducer
docker-compose logs --tail=10 -f
# Just view the scheduler and executor logs:
docker-compose logs --tail=10 -f scheduler executor

To see the job progress, you can access the web consoles of:

• Gerrit: http://localhost:8080
• Zuul: http://localhost:9000
• Logs: http://localhost:8000

If you are accessing a remote machine, replace localhost with the ip address.

• Gerrit keys
  If your ssh keys have being created with a new version of OpenSSH, Zuul will fail when running with these keys as there is a Paramiko bug [1]. It is recommended that keys be generated as follows: ssh-keygen -m PEM -t rsa - accepting the passwordless option. Then update the public keys used with Gerrit upstream and RDO Gerrit.
  [1] https://storyboard.openstack.org/#!/story/2004842