From Fedora Project Wiki

(Iniital one)
 
 
Line 14: Line 14:
 
* For src.stg repo:
 
* For src.stg repo:
 
** Already have pkgs.stg.fedoraproject.org, git.stg.centos.org and repospanner01.phx2.fedoraproject.org syncing.  
 
** Already have pkgs.stg.fedoraproject.org, git.stg.centos.org and repospanner01.phx2.fedoraproject.org syncing.  
 +
** Need more monitoring on it (nagios)
 
** Need to fix bugs that are outstanding. https://pagure.io/fedora-infrastructure/issues?status=Open&tags=repoSpanner
 
** Need to fix bugs that are outstanding. https://pagure.io/fedora-infrastructure/issues?status=Open&tags=repoSpanner
 
* For src prod repo:
 
* For src prod repo:
Line 25: Line 26:
 
=== Who? ===
 
=== Who? ===
  
Patrick and Kevin and CentOS ops
+
Patrick and Kevin and Smooge CentOS ops
  
 
=== How? ===
 
=== How? ===

Latest revision as of 18:54, 18 February 2019

This is a shorthand list of items we are needing to cover for enabling Repospanner in Fedora Infrastructure for the Fiscal Year 2020.

Point of contact: Kevin Fenzi

Why?

Repospanner is a way to sync git repos in a distributed manner. Having the Fedora dist-git and the centos git synced together and available from multiple places will allow more cross collaboration between projects as well as disaster recovery by having content in multiple places. Additionally, it will allow us to expose our currently internal ansible git repo on pagure.io so we can accept PR's and run CI tasks against changes.

What?

  • For ansible repo:
    • repospanner01.phx2.fedoraproject.org, pagure.io and batcave01.phx2.fedoraproject.org already have repospanner setup and syncing.
    • Need to get https://pagure.io/pagure/pull-request/4054 tested and merged in pagure and then a pagure release.
  • For src.stg repo:
  • For src prod repo:
    • Coordinate with CentOS side of things
    • Get RH able to push changes correctly to new repos.

When?

Sooner better than later for ansible repo.

Who?

Patrick and Kevin and Smooge CentOS ops

How?

  • Get pagure PR tested and merged and a release.
  • Fix bugs in stg

Status

The migration status can be:

  1. todo: no step has been taken yet
  2. date set: a date has been decided for the pair programming session
  3. in dev: a branch has been made and the code migration is in progress
  4. PR ready: the code migration is done and under review
  5. merged: the main branch is migrated
  6. staging: the new code is deployed to staging and under test
  7. production: the migrated app is running in production
  • ansiblle repo: in dev
  • src.stg: in progress