View Issue Details

IDProjectCategoryView StatusLast Update
0013762Buildsyscommunity buildsyspublic2017-09-13 22:25
Reporterapevec 
PriorityhighSeverityfeatureReproducibilityalways
Status assignedResolutionopen 
Summary0013762: CloudSIG: EOL releases
DescriptionSince this is the first time SIG archiving a release,
we'll use this to define and document EOL procedure in https://wiki.centos.org/SIGGuide

Please remove following CBS tags from the sync lists for buildlogs.c.o and mirror.c.o OpenStack releases which are EOLed upstream[1]

cloud6-openstack-juno-*
cloud7-openstack-juno-*
cloud7-openstack-kilo-*
cloud7-openstack-liberty-*
cloud7-openstack-mitaka-*

[1] https://releases.openstack.org/

TBD what to do with CBS tags and builds ?
TagsNo tags attached.

Activities

apevec

apevec

2017-09-01 14:50

reporter   ~0029975

This also includes archiving the last published content at vault.c.o
kbsingh@karan.org

kbsingh@karan.org

2017-09-13 13:16

administrator   ~0030047

done, pushed - Brian, please validate and close once you are happy and edit the content-control to match.
apevec

apevec

2017-09-13 20:18

reporter   ~0030049

What was the criteria under which 7.x.y/ subfolder will the archived content end up?
I see kilo and liberty under
http://vault.centos.org/centos/7.1.1503/cloud/x86_64/
kilo, liberty, mitaka and newton under
http://vault.centos.org/centos/7.2.1511/cloud/x86_64/
and nothing under
http://vault.centos.org/centos/7.3.1611/cloud/

Old content is also still available under
http://mirror.centos.org/centos/7.3.1611/cloud/x86_64/
apevec

apevec

2017-09-13 20:19

reporter   ~0030050

BTW Newton is _not_ EOLed yet and I see there is:
http://vault.centos.org/centos/7.2.1511/cloud/x86_64/openstack-newton/

Please note above request is for archiving EOLed juno to mitaka releases only!
apevec

apevec

2017-09-13 22:25

reporter   ~0030055

Capturing IRC discussion:
<kbsing> look at it this way
<kbsing> on the day 7.1511 came out, the repo that anyone running kilo would have been looking at is preserved in the same state
<kbsing> eg. in 7.1611 if a kernel update blew up someone's cloud, they use the last snapshot pre 1611, which would map to vault...
<apevec> hmm, ok, so it's snapshot whatever SIG repo had at that time
<hughesjr> yep
<kbsingh> the goal is to preserve the snapshot, to preserve the experience and keep it symetric
<kbsing> look at it differently... assume kilo straddles 2 releases, 1511 and 1611. the snapshot for 1511 in vault, would only contain kilo that was built against 1511, nothing that was built against newer content

Issue History

Date Modified Username Field Change
2017-09-01 14:48 apevec New Issue
2017-09-01 14:50 apevec Note Added: 0029975
2017-09-13 13:16 kbsingh@karan.org Status new => feedback
2017-09-13 13:16 kbsingh@karan.org Note Added: 0030047
2017-09-13 20:18 apevec Note Added: 0030049
2017-09-13 20:18 apevec Status feedback => assigned
2017-09-13 20:19 apevec Note Added: 0030050
2017-09-13 22:25 apevec Note Added: 0030055