---
# System prepended metadata

title: 20220119_fcos-pipeline-next-steps

---

# 20220119_fcos-pipeline-next-steps


## Agenda:

- Moving the pipeline to the prod OpenShift cluster
    - Can we run this pipeline in the prod cluster?
        - Notes:
            - DK: some good news! we found five more servers to the prod cluster
              should be sufficiently powerful to handle the FCOS pipeline 
            - DM & JL: our pods have memory requests and limits defined. The cluster
              should behave appropriately in scheduling these pods and delay scheduling
              if resources aren't available.
            - JL: fedora-coreos uses non-local storage
            - DK: why are you spawning VMs? We need to build disk images and also test
              those disk images, it's impossible to do that without virtualization.
            - DK: we can move to the prod cluster today
- Developer pipelines in the staging cluster
    - used to develop on our pipeline in a compatible env (openshift + jenkins)
    - 99% of the time these are unused (not a resource hog)
        - Notes:
- CoreOS CI
    - PR testing for our upstream projects
    - Currently running in CentOS CI
    - Needs to run somewhere in the future
        - Notes:
            - JL: coreos-ci uses local storage
            - JL: coreos-ci can be power hungry if a lot of Pull Requests are open at the same time
                - hopefully no longer an issue because of local storage
            - DK: can also run in prod OpenShift cluster

https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/openshift-apps/fedora-coreos.yml#_2

David Kirwan: Saffronique
Lenka Segura: lenkaseg

Proposal:
- move `fedora-coreos` to prod fedora cluster in next week
- move `coreos-ci` to the prod fedora cluster when 5 new nodes get added to the prod cluster
