From Fedora Project Wiki

< Infrastructure

Revision as of 15:53, 28 April 2017 by Tflink (talk | contribs) (Initial apps)

OpenShift in Fedora Infrastructure

Background

We want to stand up at least a proof of concept OpenShift instance in Fedora infrastucture. There's a number of reasons for this, inclusing (but not limited to):

  • A chance to stay on the leading edge of tech
  • Ability to deploy things that are expecting to be deployed in OpenShift
  • Allow us to change/improve our deployment workflow
  • Save resources by moving applications into pods instead of vm's.
  • Help dogfood software our primary sponsor makes and give them feedback.
  • Reduce required sysadmin/ops cycles for application deployment/updating.

Outstanding questions

Deploy questions

  • OpenShift Origin or OpenShift Container platform?
  • Install to vms or bare metal?
  • Atomic host or Normal?
  • RHEL or Fedora?
  • How many: controllers, nodes, routers?
  • Storage? NFS? gluster?
  • Databases: in or outside?
  • Setup things with ansible? what level? just the OpenShift? Any/all apps? Changing things like replicants?
  • Keep proxy network haproxy -> openshift apps?

Policy Questions

  • All rpms?
  • Trigger builds from git? Just some branches?
  • Does prod vs stg vs dev distrinction exist anymore?
  • Do freezes exist anymore?
  • whats the workflow?

git commit upstream -> build -> test -> deploy (slowly) ? git commits upstream on release branch -> build -> test -> deploy (slowly)? new rpm package -> build -> test -> deploy (slowly)?

  • CI? when and where?
  • "alive tests" ?
  • what monitoring do we do on instances/apps?

Initial apps

  • what initial apps would be good to move to it?
    • I'd be interested in looking at blockerbugs or taskotron as candidates to move to openshift (tflink)