this morning I finished with installation of new koji - koji.theforeman.org. The biggest change is to move from EC2 to OS1
OpenStack cloud sponsored by Red Hat. Also we are able to have much more
strong hardware: 8 cores, 16 GB RAM and 800 GB block device.
There are two options how to do the migration. We can either migrate the
old koji keeping everything including all the history (and all the old
tags). But since we have been playing with koji quite a lot, there is
lots of old content which could be cleared out.
The second option would be to start from scratch.
I lean towards the latter, this could be opportunity to clear things and
start over with a clean plate. My thinking is:
We can even consider naming things differently, Dom was writing the
other day about changing our SCL prefix. How about to drop "nonscl"
infix and use "scl" where appropriate?
The transition should be smooth, we can keep running the old koji for
couple of months until all teams have builds.
> Hello,
>
> this morning I finished with installation of new koji -
> koji.theforeman.org. The biggest change is to move from EC2 to OS1
> OpenStack cloud sponsored by Red Hat. Also we are able to have much more
> strong hardware: 8 cores, 16 GB RAM and 800 GB block device.
>
> There are two options how to do the migration. We can either migrate the
> old koji keeping everything including all the history (and all the old
> tags). But since we have been playing with koji quite a lot, there is
> lots of old content which could be cleared out.
>
> The second option would be to start from scratch.
>
> I lean towards the latter, this could be opportunity to clear things and
> start over with a clean plate. My thinking is:
>
> - import external repos:
> - centos 6.5 (or rhel 6.5?)
> - centos scl 1.0
> - epel 6
> - fedora 19
> - create tags and rebuild:
>
> foreman-nightly-fedora19
> foreman-nightly-fedora19-build
> foreman-nightly-fedora19-override
> foreman-nightly-nonscl-rhel6
> foreman-nightly-nonscl-rhel6-build
> foreman-nightly-nonscl-rhel6-override
> foreman-nightly-rhel6
> foreman-nightly-rhel6-build
> foreman-nightly-rhel6-override
>
> The same for:
>
> foreman-plugins-*
> katello-* - question is to start building Katello into foreman-plugins-*
>
> I need to find out which of these are still in use:
>
> katello-sandbox-*
We no longer need this one ^
>
katello-thirdparty-*
>
This tag is used to build dependencies that Katello needed that are not
directly part of Katello (e.g. gem overrides, gems that don't exist
anywhere else and are required). We could re-think how this tag works.
> candlepin-*
pulp-*
>
These two are used by the Pulp and Candlepin teams directly to build their
upstream packages. We in turn build the version we are using for a release
(e.g. katello-pulp and katello-candlepin for nightly).
Eric
···
On Thu, Mar 27, 2014 at 7:48 AM, Lukas Zapletal wrote:
rdo-*
We can even consider naming things differently, Dom was writing the
other day about changing our SCL prefix. How about to drop “nonscl”
infix and use “scl” where appropriate?
The transition should be smooth, we can keep running the old koji for
couple of months until all teams have builds.
> Hello,
>
> this morning I finished with installation of new koji -
> koji.theforeman.org. The biggest change is to move from EC2 to OS1
> OpenStack cloud sponsored by Red Hat. Also we are able to have much more
> strong hardware: 8 cores, 16 GB RAM and 800 GB block device.
>
> There are two options how to do the migration. We can either migrate the
> old koji keeping everything including all the history (and all the old
> tags). But since we have been playing with koji quite a lot, there is
> lots of old content which could be cleared out.
>
> The second option would be to start from scratch.
>
> I lean towards the latter, this could be opportunity to clear things and
> start over with a clean plate. My thinking is:
>
> - import external repos:
> - centos 6.5 (or rhel 6.5?)
> - centos scl 1.0
> - epel 6
> - fedora 19
> - create tags and rebuild:
>
> foreman-nightly-fedora19
> foreman-nightly-fedora19-build
> foreman-nightly-fedora19-override
> foreman-nightly-nonscl-rhel6
> foreman-nightly-nonscl-rhel6-build
> foreman-nightly-nonscl-rhel6-override
> foreman-nightly-rhel6
> foreman-nightly-rhel6-build
> foreman-nightly-rhel6-override
>
> The same for:
>
> foreman-plugins-*
> katello-* - question is to start building Katello into foreman-plugins-*
Probably not, the stuff in foreman-plugins is fairly small and won't
have release cycles and major versions like Katello does.
> We can even consider naming things differently, Dom was writing the
> other day about changing our SCL prefix. How about to drop "nonscl"
> infix and use "scl" where appropriate?
Fine by me.
> The transition should be smooth, we can keep running the old koji for
> couple of months until all teams have builds.
>
> Opinions?
I don't mind which of the two we do, but if we set up a new instance
then I'd prefer to wait until after Foreman 1.5 and tackle a few things
at the same time. I'm working on a replacement for katello-thirdparty
for Foreman's dependencies and later core builds using tito v0.5, and as
you hinted, would like to fix the SCL prefix we build into (#4841).
If we're not rebuilding from scratch, then the crossover time shouldn't
be important, as I'd assuming you're not planning any mass-rebuilds.
