--=-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--