Move Tendrl builds from Copr to CentOS repos (Storage SIG)

[r0h4n]

Based on comments from @mykaul https://github.com/Tendrl/tendrl-ansible/issues/107

To better align with Gluster and Ceph in Centos storage SIG. The first step would be to have Tendrl builds saved in centos infra (we already use centos ci to make builds).

@mbukatov @mykau, once this is done we should discuss testing these Tendrl builds with gluster on centos7, currently we dont do that thoroughly, we mainly focus on gluster on rhel7.

[mbukatov]

Moving to CentOS Storage SIG would require:

• maintain rpm spec files in dist git repositories and build rpm packages in koji
• maintain set of yum repositories
• update our current checks in CentOS CI to use different repositories

In general, this is a good idea, as it would force us to:

• be more disciplined
• do proper release engineering (which we lack now)
• easier reuse of build plumbing code downstream

That said, it seems to be long term effort.

[TimothyAsirJeyasing]

We are currently using copr for building of packages and the repo. It creates the repo automatically. It also support multiple distribution for which it uses its own build servers for epel7 and fedora and other distribution.

However moving to CentOS repo could be an interesting option. It needs lot of effort. So initially till the time we moved completely to CentOS, I would suggest to keep our copr build mechanism. As @mbukatov has mention already, first we need to start using fedora koji with epel7 build root for building the rpm. I will come up with a plan and update this issue.

[TimothyAsirJeyasing]

@r0h4n please assign to https://github.com/TimothyAsirJeyasing

[r0h4n]

@TimothyAsirJeyasing I have sent a request to your new github id to become member of "Tendrl" org. Please accept the invite so that I can assign this issue to your new id as requested.

Also, please provide a estimated date on this issue.

[TimothyAsirJeyasing]

We need to first have an account in centos sig and should joined to storage sig and any other applicable list of groups. Once its approved, we have to add our package into the group. After that we can start building the packages using koji and finally we can update our centos-ci repo with this changes. For approval and other build related tasks and update it will take around 2 to 2.5 weeks time.

[nthomas-redhat]

@TimothyAsirJeyasing , please get started on this

[mbukatov]

Note that this requires both release engineering and packaging to actually follow fedora packaging guidelines.