On Fri, May 8, 2015 at 1:45 PM, Loic Dachary <loic@xxxxxxxxxxx> wrote: > Hi, > > I was going through the checklist to retire a release, to verify nothing was left behind for Dumpling > > http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO_retire_a_stable_release > > and from the nightlies crontab that you published, I found > > http://tracker.ceph.com/projects/ceph-releases/wiki/Typica > > 10 18 * * 0,4 teuthology-suite -v -c giant -k distro -m typica -s upgrade/dumpling-firefly-x --filter ubuntu_ > > and > > http://tracker.ceph.com/projects/ceph-releases/wiki/Sepia > > 10 17 * * 2,4,7 teuthology-suite -v -c next -k distro -m plana,burnupi,mira -s upgrade/dumpling-firefly-x --filter ubuntu_ > > 13 19 * * 7 teuthology-suite -v -c firefly -k distro -m vps -s upgrade/dumpling-x ~/vps.yaml > > 15 18 * * 3,6 teuthology-suite -v -c giant -k distro -m vps -s upgrade/dumpling-firefly-x ~/vps.yaml You'll notice that these are all tests which upgrade from dumpling to something else. We want to keep testing that to make sure we aren't missing something in the upgrade paths — which would be bad, even though we're about ready to stop supporting dumpling. ;) -Greg > > > You can also remove from Sepia the lines commented out: > > #removed the line below b/c the suite 'upgrade/dumpling-firefly-x' on vps runs out of memory on hammer, YuriW 3/29/15 > #15 17 * * 1,3 teuthology-suite -v -c hammer -k distro -m vps -s upgrade/dumpling-firefly-x --suite-branch hammer ~/vps.yaml > > #removed the line below b/c the suite 'upgrade/dumpling-firefly-x' on vps runs out of memory on next, YuriW 3/29/15 > #15 17 * * 0,2,4,6 teuthology-suite -v -c next -k distro -m vps -s upgrade/dumpling-firefly-x --suite-branch hammer ~/vps.yaml > > Maybe there is a reason for scheduling them, even though Dumpling is retired. But in case it was just overlooked, maybe you can save some computing power in the labs :-0 > > Cheers > -- > Loïc Dachary, Artisan Logiciel Libre > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
