-Phil/Anil/Colin, probably not of interest to them; +Ryan, who raised something related in "[controller-dev] Question about opendaylight-karaf-empty" +Vratko
https://logs.opendaylight.org/disk-usage-by-file.txt.gz > > It also includes directories so we can walk around and figure out at a > higher level which projects use the most disk space too. > > Regards, > Thanh > > > On 12 July 2016 at 13:11, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES > at Cisco) <vrpo...@cisco.com> wrote: > bump this old thread... if I understood Vratko correctly, it seems we're just about to make this worse with https://git.opendaylight.org/gerrit/#/c/48934/ (which I'd like to get in to fix https://bugs.opendaylight.org/show_bug.cgi?id=6523, which we need for https://git.opendaylight.org/gerrit/#/c/48901/) On Thu, Jul 14, 2016 at 5:16 AM, Thanh Ha <thanh...@linuxfoundation.org> wrote: Hi Michael, I produced a log of all the files in opendaylight.snapshot sorted by size here: > > Do you think / agree it's worth to make controller/karaf a non-SNAPSHOT >> but fixed version project ASAP? >> >> >> >> I disagree. There are changes pending, >> >> and we are nowhere near having "fast" releases. >> >> >> >> What we could possibly do is to create two build profiles, >> >> and two merge jobs (with corresponding triggers) >> >> to build karaf and non-karaf parts of controller separately. >> >> >> >> The long term solution is to move the code into a separate (sub)project. >> >> How does odlparent/karaf.git sound like? >> > if I understand correctly, this (karaf that used to be in controller) is now in odlparent/karaf's opendaylight-karaf-empty, and opendaylight-karaf4-empty .. So how about we now, because this change comparatively relatively infrequently, make this a fixed instead of a daily SNAPSHOT release already? It would save a lot of people a lot of download time, wouldn't it? What would have to happen? > >> >> Vratko. >> >> >> >> *From:* odlparent-dev-boun...@lists.opendaylight.org [mailto: >> odlparent-dev-boun...@lists.opendaylight.org] *On Behalf Of *Michael >> Vorburger >> *Sent:* 12 July, 2016 18:51 >> *To:* controller-dev <controller-dev@lists.opendaylight.org>; Thanh Ha < >> thanh...@linuxfoundation.org>; odlparent-...@lists.opendaylight.org >> *Cc:* Anil Vishnoi <vishnoia...@gmail.com>; Dixon, Colin < >> co...@colindixon.com>; Philip Robb <pr...@linuxfoundation.org> >> *Subject:* [Odlparent-dev] Move opendaylight-karaf-empty (and >> opendaylight-karaf-resources) to fixed version >> >> >> >> Thanh, can you easily produce a sorted list of the biggest SNAPSHOT >> artefacts on nexus.opendaylight.org by file size? >> >> Hello Controllers, the "[OpenDaylight Discuss] Fast and/or Phased >> Planning for the Carbon Release" thread got me thinking about something: >> >> >> >> Every change to controller cause a new opendaylight-karaf-empty-1.7.0 >> SNAPSHOT (53 MB) and an opendaylight-karaf-resources (3 MB) to be >> downloaded by everyone. I do mean every change, any bit flipped in >> controller - not only Karaf related changes. And even if no change in >> controller whatsoever, then at least once a week, based on Thanh's >> explanation in the 'Fast and/or Phased' thread. >> >> So we're pushing around, and making people wait, for a lot of 50 MB >> downloads - completely unnecessarily in 99% of cases. This is probably not >> ideal? Do you think / agree it's worth to make controller/karaf a >> non-SNAPSHOT but fixed version project ASAP? Or am I exaggerating here? >> >> The 1% of cases where there really is a news in controller/karaf could be >> handled through a real fixed non-SNAPSHOT version increment. We just have >> to make this really easy to do for any contributor (i.e. ideally as >> automated as possible and ideally NOT requiring any sort of manual release >> management work by LF). >> >> How would we do this in practice? I'm not crystal about the release >> process stuff etc. Presumably this is a little bigger than just me putting >> in a Gerrit that changes the version in a few pom.xml under >> controller/karaf, or is it? How would we actually create and deploy once to >> Nexus a fixed non-SNAPSHOT versions (for phased) for an ODL artifact like >> controller/karaf/ ? Or does this need a new Git repo? I thought not, >> because there already are various Maven artefact versions mixed in some of >> our ODL Git repos, aren't there? >> >> >> >> Tx, >> >> M. >> >> -- >> >> Michael Vorburger <vorbur...@redhat.com> | IRC: vorburger @freenode | ~ >> = http://vorburger.ch >> > >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
