Skip to content
This repository has been archived by the owner on Jun 18, 2021. It is now read-only.

Latest commit

 

History

History
87 lines (62 loc) · 3.37 KB

ci-setup.md

File metadata and controls

87 lines (62 loc) · 3.37 KB
Raw

CI OpenStack machine setup

This is split into three parts:

  • Creating an OpenStack instance
  • Setting up the instance to be managed with ansible
  • Setting up the CI configuration

Creating an instance

Firstly, add the machine configuration to management_tools.

  • Add a host inventory file to ansible/inventory/host_vars/<name>. This must contain appropriate openstack_machine and openstack_volumes sections. See other hosts for examples.

  • Add the machine name to the appropriate groups in ansible/inventory/ci-openstack-hosts. Make sure to include it in the appropriate platform and deployment groups, and in each CI role group this instance should provide.

Run the following:

ansible-playbook -e "ci_host=<host>" -i <management_tools>/ansible/inventory/ci-openstack-hosts <infrastructure>/ansible/os-ci-create-machine.yml

Substitute all names marked with <name> for the appropriate names and paths.

When complete, you will see this instance created using either the OpenStack Horizon interface or the command-line. You should be able to SSH into it with the shared "ci" key. You'll need this key for the next step. For Windows platforms, a password was generated which you'll need to use instead; see the Windows image page for more details.

Ansible setup

This part installs the necessary packages (such as Python) for running Ansible, and also creates a common user (ci-admin) for administration using authorized_keys specified in management_tools (ansible/inventory/group_vars/ci-openstack/vars). After this step, the system can be administered with ansible using the ci-admin account and your own SSH credentials.

Unix platforms:

# SSH in manually to add the host to your known_hosts
ssh <user>@<host>

ansible-playbook -l <host> -e "ansible_user=<user>" -u <user> -i <management_tools>/ansible/inventory/ci-openstack-hosts <infrastructure>/ansible/ci-initial-setup.yml

As before, substitute all names marked with <name> for the appropriate names and paths. <user> is specific to the image. It's something like centos, freebsd, ubuntu, Admin or similar.

Windows:

# See https://github.com/ansible/ansible/issues/22660
# Enable connection via credssp which is needed to avoid "double-hop"
# problems; we have to do this step by hand since there's a
# chicken-and-egg problem with connecting to do it in a playbook.
ansible <host> -e "ansible_user=Admin ansible_password=<admin_password> ansible_winrm_transport=basic" -u Admin -i <management_tools>/ansible/inventory/ci-openstack-hosts -m win_shell -a "Enable-WSManCredSSP -Role Server -Force"

ansible-playbook -l <host> -e "ansible_user=Admin ansible_password=<admin_password>" -u Admin -i <management_tools>/ansible/inventory/ci-openstack-hosts <infrastructure>/ansible/ci-initial-setup.yml

Here, <admin_password> is the password for the Admin user, obtained as detailed on the Windows image page.

Once this completes, the node is ready to be configured for its purpose. You shouldn't need to run the initial setup playbook again (but you can if you need to).

CI setup

Run:

ansible-playbook -l <host|group> -i <management_tools>/ansible/inventory/ci-openstack-hosts <infrastructure>/ansible/ci-setup.yml

Once this step completes, the node is ready to be added to jenkins. This step may be rerun as needed, and run on groups of CI nodes.