#6675 Deploy orchestrated OSBS cluster
Closed: Fixed 5 years ago Opened 6 years ago by cverna.

In order to support building mutli arch container and flatpak we need an orchestrated OSBS cluster.

The current cluster is composed of :

  • osbs-control01 - Host the ansible playbook used to deploy the cluster
  • osbs-master01 - Origin master
  • osbs-node01 - Origin node
  • osbs-node02 - Origin node

The orchestrated mode will be composed of at least :

  • osbs-control01 - Host the ansible playbook used to deploy the cluster
  • osbs-orchestrator-master01 -Origin master (Orchestrator)
  • osbs-worker-master-01 - Origin master worker (x86_64)
  • osbs-worker-node01 - Origin node worker (x86_64)
  • osbs-worker-node02 - Origin node worker (x86_64)

A new Origin cluster will be needed for each arch that need to be supported


For single arch support, it is possible to use the same Openshift Origin cluster. So in a first step it will not be required to have a second Openshift Origin cluster

Metadata Update from @kevin:
- Issue priority set to: Waiting on Asignee

6 years ago

Orchestrated cluster is now working in staging, however there are still few things to cleanup before moving to production.

  • I manually patched atomic-reactor to support Fedora auth using certs. (We are considering moving to basic auth, so that should not be needed anymore)

  • I have disabled the import_image post build plugins because it was failing. (That should be fixed in newer version of atomic-reactor)

Is this now done in production?

yes let's close this :)

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

5 years ago

Login to comment on this ticket.

Metadata