View Issue Details

IDProjectCategoryView StatusLast Update
0008407Buildsyscommunity buildsyspublic2015-05-05 13:38
ReporterSandro Bonazzola 
PrioritynormalSeverityminorReproducibilityhave not tried
Status resolvedResolutionfixed 
Summary0008407: [Virt SIG] CBS tags hierarchy
DescriptionImplementation of the following proposal: http://lists.centos.org/pipermail/centos-virt/2015-March/004311.html

- virt${release}-common : packages not related to xen or kvm, used by at least 2 projects
- virt${release}-xen : xen hypervisor related packages
- virt${release}-kvm : kvm hypervisor related packages (like qemu-kvm-ev)
- virt${release}-ovirt : ovirt packages and dependencies, not required by other projects
- virt${release}-docker : docker packages and dependencies, not required by other projects
TagsNo tags attached.

Activities

alphacc

alphacc

2015-04-07 06:59

developer   ~0022684

Hi Sandro,

I am working with other sigs to have a common manageable hierarchy.

The schema is quite similar except we have one more variable


{signame}{major}-{project}-{release}
e.g : cloud6-openstack-juno

It allows to work on different release 33, 34 for ovirt for example :
e.g : virt6-ovirt-34

Should we follow the same idea ?
Sandro Bonazzola

Sandro Bonazzola

2015-04-07 13:08

reporter   ~0022688

it may make sense, 3.5 and 3.6 only for now.
gwd

gwd

2015-04-07 13:29

reporter   ~0022689

alphacc: What's the rationale behind adding {release} to the tags?
gwd

gwd

2015-04-07 14:08

reporter   ~0022690

For posterity: We discussed alphacc's proposed tag structure at the Virt SIG meeting on 7 April 2015, and all the maintainers (lsm5, gwd, sbonazzo) thought it was a good idea.
alphacc

alphacc

2015-04-08 13:28

developer   ~0022709

Last edited: 2015-04-08 13:29

View 2 revisions

So I have releases for ovirt

ovirt-35
ovirt-36

What should we use for

kvm
xen
docker

Let me know!

gwd

gwd

2015-04-08 14:56

reporter   ~0022711

Can the release have dots in it? Xen I think should be 4.4 and 4.6, but that can be 44 and 46 if necessary.
alphacc

alphacc

2015-04-08 14:58

developer   ~0022712

sorry no dot allowed.

ok for
xen-44
xen-46
alphacc

alphacc

2015-04-17 13:02

developer   ~0022799

I created ovirt and xen ; let me know what release to use for docker and kvm ?
alphacc

alphacc

2015-04-17 13:26

developer   ~0022802

Last edited: 2015-04-17 14:56

View 3 revisions

$ koji list-targets | grep virt7
virt7-common-el7 virt7-common-el7-build virt7-common-candidate
virt7-el7 virt7-el7-build virt7-testing
virt7-ovirt-35-el7 virt7-ovirt-35-el7-build virt7-ovirt-35-candidate
virt7-ovirt-36-el7 virt7-ovirt-36-el7-build virt7-ovirt-36-candidate
virt7-ovirt-common-el7 virt7-ovirt-common-el7-build virt7-ovirt-common-candidate
virt7-xen-44-el7 virt7-xen-44-el7-build virt7-xen-44-candidate
virt7-xen-46-el7 virt7-xen-46-el7-build virt7-xen-46-candidate
virt7-xen-common-el7 virt7-xen-common-el7-build virt7-xen-common-candidate


So just a little change in the workflow, pacakges end up in -candidate tags by default ; and be tagged testing and release then.

You have "virt7-common-el7" target for pkgs common to all projects

And "virt7-<project>-common-el7" target for pkgs common to all releases of a project.

It doesn't mean you *need* to use them ; but it is to align with other sigs and better to have more choices than less.

Sandro Bonazzola

Sandro Bonazzola

2015-04-20 08:02

reporter   ~0022824

Thanks alphacc, above targets looks good to me.
alphacc

alphacc

2015-04-20 08:34

developer   ~0022826

Ok great, let me know , when the SIG agreed on docker and kvm {release}.
dcaroest

dcaroest

2015-04-20 09:47

reporter   ~0022829

Looks ok to me too
gwd

gwd

2015-04-20 13:42

reporter   ~0022834

alphacc,

Would it make sense to also have a "stable" release tag, for a project, so that people can use whatever the latest "stable" version is, rather than having to manually change from (say) xen-44 to xen-46 (to xen-48, &c)?
alphacc

alphacc

2015-04-20 14:11

developer   ~0022835

Hi gwd,

Yes at the repository level we can have one repo with all releases.

Let's rediscussed that when we are ready to release.

We have now a way to build different release ; the upgrade path need to be tested by the SIG and we can then distribute the final release to users on the distribution server.

If we want to do it with a koji tag, fine but maybe a reposync with all -release tags is enough.

Thomas.
gwd

gwd

2015-04-20 14:12

reporter   ~0022836

Oh right, sorry, we discussed this already didn't we. :-/ Nevermind. Too many things going on...
alphacc

alphacc

2015-04-21 15:38

developer   ~0022852

$ koji list-targets | grep docker
virt7-docker-common-el7 virt7-docker-common-el7-build virt7-docker-common-candidate
virt7-docker-master-el7 virt7-docker-master-el7-build virt7-docker-master-candidate
virt7-docker-upstream-el7 virt7-docker-upstream-el7-build virt7-docker-upstream-candidate

So docker is done.
Let's see what we do with "kvm"
alphacc

alphacc

2015-05-05 13:38

developer   ~0022994

As agreed on the SIG meeting let's close this !

Issue History

Date Modified Username Field Change
2015-04-07 06:53 Sandro Bonazzola New Issue
2015-04-07 06:59 alphacc Note Added: 0022684
2015-04-07 13:08 Sandro Bonazzola Note Added: 0022688
2015-04-07 13:29 gwd Note Added: 0022689
2015-04-07 14:08 gwd Note Added: 0022690
2015-04-08 13:28 alphacc Note Added: 0022709
2015-04-08 13:29 alphacc Note Edited: 0022709 View Revisions
2015-04-08 14:56 gwd Note Added: 0022711
2015-04-08 14:58 alphacc Note Added: 0022712
2015-04-17 13:02 alphacc Note Added: 0022799
2015-04-17 13:26 alphacc Note Added: 0022802
2015-04-17 13:28 alphacc Note Edited: 0022802 View Revisions
2015-04-17 14:56 alphacc Note Edited: 0022802 View Revisions
2015-04-20 08:02 Sandro Bonazzola Note Added: 0022824
2015-04-20 08:34 alphacc Note Added: 0022826
2015-04-20 09:47 dcaroest Note Added: 0022829
2015-04-20 13:42 gwd Note Added: 0022834
2015-04-20 14:11 alphacc Note Added: 0022835
2015-04-20 14:12 gwd Note Added: 0022836
2015-04-21 15:38 alphacc Note Added: 0022852
2015-05-05 13:38 alphacc Note Added: 0022994
2015-05-05 13:38 alphacc Status new => resolved
2015-05-05 13:38 alphacc Resolution open => fixed