Am Mittwoch, den 26.02.2014, 04:03 -0500 schrieb Kiril Nesenko: > We are moving to a new layout resources.ovirt.org/pub. > > Please let us know where do you want to put your files.
For that case I'd suggest: pub + ovirt-node-base-3.0 + iso + rpm + src + ovirt-node-base-stable (symlink to ovirt-node-base-3.0) - fabian > - Kiril > > ----- Original Message ----- > > From: "Fabian Deutsch" <[email protected]> > > To: [email protected] > > Cc: "node-devel" <[email protected]> > > Sent: Wednesday, February 26, 2014 10:18:27 AM > > Subject: oVirt Node filesystem layout on resources.ovirt.org > > > > Hey, > > > > currently it is not easy to find oVirt Node (Base Image) releases on > > resources.o.o - I'd like to suggest a layout simplification to remove > > some clutter, improve the findability of isos and ease the maintenance. > > > > Currently the (Node related) layout is: > > > > releases > > + base > > + node-base > > + 3.0.0 > > + iso > > + rpm > > + alpha > > + beta > > + nightly (symlink?) > > + stable (symlink to 3.0.0?) > > > > could we please change the tree to be more like: > > > > releases > > + node-base > > + 3.0 > > + iso > > + rpm > > + stable (symlink to 3.0) > > > > Some notes on the removed paths: > > base - Was unused > > alpha - To reduce overhead I'd use jenkins builds for alpha > > beta - To reduce overhead I'd use jenkins builds for beta > > beta - To reduce overhead I'd use jenkins builds for nightlies > > > > Some more notes: > > 3.0 - Just this one dir for all updates > > > > This boils down to Node just offering stable images on resources.o.o. > > Everything else can be pulled from jenkins (once we get everything into > > shape again). > > > > This suggestion is just for the "base image". Once the base images are > > in place, jenkins can pick up the base images and generate "layered" > > images which include vdsm (to be used with Engine). > > The layered images can then be kept in the same place where the > > remaining oVirt (Engine, vdsm, ...) packages are kept (for 3.3.3 > > in /releases/3.3.3/…). > > > > Does that make sense? > > > > - fabian > > > > _______________________________________________ > > Infra mailing list > > [email protected] > > http://lists.ovirt.org/mailman/listinfo/infra > >
signature.asc
Description: This is a digitally signed message part
_______________________________________________ node-devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/node-devel
