2:18 a.m.
--=-U8gayk2fbPhRpVTYJ0Oy
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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/=E2=80=A6).
Does that make sense?
- fabian
--=-U8gayk2fbPhRpVTYJ0Oy
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
iQIcBAABAgAGBQJTDaNUAAoJEC9+uOgSHVGUpPIP/0MTDzpmZEETIEvJS+mIybRC
fZSxKFOD4Y217WvV9JnzzKgKqzmt95931TUu6ba04+Vt/10H2bcfqQWTGaxQeLdn
9U94/43BBw1Ky3jvFw0l3ddq2tZr1bhDU8KpXVtjPaLbjaQoGlipdS/SESolMJTy
ZxevGUBg7JXstd0H8mIsUcLIOojoI9rk2hwtLoBL72L0lb4GGjXM5GxDZGsahjBq
fFH01RDqs9N6H31+088R6lGvHvshgyHd4vN4dI2lKQX1cUr1RH+D8hD4MWGqOU3A
Ipz5V+WxKrUwVstCj7eiwBP+y2m0IhXh/pwyaP4zTUSl+UJMkz0Thcy7Shux6atB
4M/6s48ffIjUg2G2PcUsxbDH7wUtHaX4t/x1+LkigrtGXoZL9rrVF0AHfK73uooc
ZzocyYvxyjqdkKL1LvWegzGPm/VqvuBd9lgDdu8HxiMA5VjDkNl8D2cde8kcenz0
cDNv1uwWu5TuXRFCHFlHQxuizVQTJbxO+XXAJxdu7UoIUg4Bu5bRMeYHD8cFaetQ
2F9g2hN/9WGjI+obQXleaLXlAfmZcky26iuY4w0MydqOQs91essE9IYTvUpgB+8A
T2z+6C9/9BNaMrPRnQmpQ069dEuoPtGxjGkyrT3/uBqHyVXSN61X+BOF+SBsFSBx
2PQuVPU1UCw/IHzh1CXf
=P41A
-----END PGP SIGNATURE-----
--=-U8gayk2fbPhRpVTYJ0Oy--
3:03 a.m.
We are moving to a new layout resources.ovirt.org/pub.
Please let us know where do you want to put your files.
- Kiril
----- Original Message -----
From: "Fabian Deutsch" <fabiand(a)redhat.com>
To: infra(a)ovirt.org
Cc: "node-devel" <node-devel(a)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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
3:17 a.m.
--=-6KaLOb7FZBe1c0B1o9dS
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Am Mittwoch, den 26.02.2014, 04:03 -0500 schrieb Kiril Nesenko:
We are moving to a new layout resources.ovirt.org/pub.
=20
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
=20
----- Original Message -----
> From: "Fabian Deutsch" <fabiand(a)redhat.com>
> To: infra(a)ovirt.org
> Cc: "node-devel" <node-devel(a)ovirt.org>
> Sent: Wednesday, February 26, 2014 10:18:27 AM
> Subject: oVirt Node filesystem layout on resources.ovirt.org
>=20
> Hey,
>=20
> 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.
>=20
> Currently the (Node related) layout is:
>=20
> releases
> + base
> + node-base
> + 3.0.0
> + iso
> + rpm
> + alpha
> + beta
> + nightly (symlink?)
> + stable (symlink to 3.0.0?)
>=20
> could we please change the tree to be more like:
>=20
> releases
> + node-base
> + 3.0
> + iso
> + rpm
> + stable (symlink to 3.0)
>=20
> 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
>=20
> Some more notes:
> 3.0 - Just this one dir for all updates
>=20
> 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).
>=20
> 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/=E2=80=A6).
>=20
> Does that make sense?
>=20
> - fabian
>=20
> _______________________________________________
> Infra mailing list
> Infra(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>=20
--=-6KaLOb7FZBe1c0B1o9dS
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
iQIcBAABAgAGBQJTDbEiAAoJEC9+uOgSHVGU+KsP/AzFSQzbKFU3XuLf5Ud+UTta
TwtPXiRiknIUoaiZhmsj+UlTyKI3joGkTDZPEk0dqqIbijiwLWx8w6brq2u51kYh
mSFTCgTv2kXRURFq3NNT8XApXqgJ+IupooTUTOBXMCQZIFNb46vQTTv4xFh76ZCn
FPP/NQHQjy6iMBIVrKiUwKOuWfCKWUAw9jfkM1N8wzUhHA91Yt6gJKsEK79FSlMB
sV756NmkUKCw1hkEULKWTzz2LSODniPDY33ftENU0GdC7Nk0d0QC9XFkQc6BKt5M
/I6aABLT4D0tJGQ6iWGegddYKxoLoum9kxc+LkGiIaGaMZrvkTxyYqHI1rlkvpNc
q511eiv6xBMtHMxiPWrgcHZWxzrybTYbCnlY6WLXZlDC8k9f1rNl7dxKFfaYiRbe
N/8HRMauRSUUHS+PypMxEsth2AhqUG80OSgjUwd2XlPm/9Za6DI2bN6CpDcjvSir
L3g0zCSBUsOGsjMBJ2QYuf98A7KOJGejdb3OoRJ+Ei1AIPgyo0Qreym/JHdh3vHA
dQVl+561L+vilV6lP3+2g5PXnzDfT67g/opAUlONn82jmoNPsrTb/z7oT8/NMRUP
VVg2KHrc44JMT9QKm26l/LVd+na2U1ya3UMEU5umh7ljlCOMpixzegm3EHkDrdJL
CwgR2qKyz7LAhaP1P76N
=hVm/
-----END PGP SIGNATURE-----
--=-6KaLOb7FZBe1c0B1o9dS--
12:18 a.m.
New subject: [node-devel] oVirt Node filesystem layout on resources.ovirt.org
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:
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" <fabiand(a)redhat.com>
>> To: infra(a)ovirt.org
>> Cc: "node-devel" <node-devel(a)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(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
_______________________________________________
node-devel mailing list
node-devel(a)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/noa...
<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://...
</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">ht...
</pre>
</blockquote>
<br>
</body>
</html>
--------------000008070201070809080008--
3699
days inactive
3705
days old
3 comments
3 participants
participants (3)
-
Fabian Deutsch -
Kiril Nesenko -
Lei Wang