This is a multi-part message in MIME format. --------------000008070201070809080008 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit The new layout looks nice :-) http://resources.ovirt.org/pub/ovirt-node-base-3.0/rpm/el6/noarch/ Lei Wang On 02/26/2014 05:17 PM, Fabian Deutsch wrote:
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:
Am Mittwoch, den 26.02.2014, 04:03 -0500 schrieb Kiril Nesenko: 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" <fabiand@redhat.com> To: infra@ovirt.org Cc: "node-devel" <node-devel@ovirt.org> 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 Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ node-devel mailing list node-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/node-devel
--------------000008070201070809080008 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix"><br> The new layout looks nice :-)<br> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <a href="http://resources.ovirt.org/pub/ovirt-node-base-3.0/rpm/el6/noarch/">http://resources.ovirt.org/pub/ovirt-node-base-3.0/rpm/el6/noarch/</a><br> <br> Lei Wang<br> <br> On 02/26/2014 05:17 PM, Fabian Deutsch wrote:<br> </div> <blockquote cite="mid:1393406242.2969.19.camel@fdeutsch-laptop.local" type="cite"> <pre wrap="">Am Mittwoch, den 26.02.2014, 04:03 -0500 schrieb Kiril Nesenko: </pre> <blockquote type="cite"> <pre wrap="">We are moving to a new layout resources.ovirt.org/pub. Please let us know where do you want to put your files. </pre> </blockquote> <pre wrap=""> 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 </pre> <blockquote type="cite"> <pre wrap="">- Kiril ----- Original Message ----- </pre> <blockquote type="cite"> <pre wrap="">From: "Fabian Deutsch" <a class="moz-txt-link-rfc2396E" href="mailto:fabiand@redhat.com"><fabiand@redhat.com></a> To: <a class="moz-txt-link-abbreviated" href="mailto:infra@ovirt.org">infra@ovirt.org</a> Cc: "node-devel" <a class="moz-txt-link-rfc2396E" href="mailto:node-devel@ovirt.org"><node-devel@ovirt.org></a> 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 <a class="moz-txt-link-abbreviated" href="mailto:Infra@ovirt.org">Infra@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/infra">http://lists.ovirt.org/mailman/listinfo/infra</a> </pre> </blockquote> </blockquote> <pre wrap=""> </pre> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ node-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:node-devel@ovirt.org">node-devel@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/node-devel">http://lists.ovirt.org/mailman/listinfo/node-devel</a> </pre> </blockquote> <br> </body> </html> --------------000008070201070809080008--