#467 using cico client with Ansible on new OCP Jenkins
Closed: Fixed with Explanation 2 years ago by arrfab. Opened 2 years ago by evgeni.

Ohai,

we (foreman) are currently planning the migration of our old ci.centos.org setup to the new OCP based one, and are facing a few problems (or maybe misunderstandings) with the setup.

To give a bit of background:
We're using Duffy to run end-to-end tests for Foreman. To do so we have an Ansible playbook that will request a node using the cico module, deploy our test-suite on the node, run the tests and give the node back to the pool.

This worked quite fine in the old setup, as Ansible and all the CICO bits (and secrets) were already present.

Now moving to the new OCP setup, I see the following:

  • the controller doesn't have CICO (neither the client, not the API key) provisioned, and I think I need to run our stuff on a node with the cico-workspace label (which gets dynamically provisioned on K8s from quay.io/centosci/cico-workspace)
  • the cico-workspace container has Python2, but neither Ansible nor any reasonable means to install it (pip/virtualenv)
  • the controller would have Python3 (and venv/pip), but no API token for Duffy, and it seems less secure to run stuff on the controller directly. additionally, pip install ansible-core python-cicoclient in an virtualenv takes very long (~10 minutes), probably because of NFS.

So I think my real question is: Would it be possible to get a cico-workspace container with Ansible pre-installed? Or, failing that, at least a Python that can be used to pip install things on?

Thanks!
Evgeni

PS: the cico-workspace container seems to be based on CentOS 7.7, which sounds a bit dated? ;)


Metadata Update from @arrfab:
- Issue tagged with: centos-ci-infra, doc, high-gain, medium-trouble

2 years ago

@mobrien were you able to ask time from people who left our sub-team and who'd be able to help with this ?

Closing as it was pushed earlier today.
We also updated doc that covers how to rebuild/refresh the cico-workspace container (as infra and releng team now also got access to quay.io and github repository where Dockerfile is)

Metadata Update from @arrfab:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata
Boards 1
CentOS CI Infra Status: Backlog