-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 So the requests I have received or heard so far around "providing package and tarball download locations" are: 1. ftp.ovirt.org as location with packages for various distros as well as binary and source tarballs. 2. Yum repository for the Fedora packages being worked on, until they get in to Fedora. 3. Location for different distros package management tools to find packages. 4. Centrally maintained details (examples) of the files used for different package management needs, e.g. files for /etc/yum.repos.do/ etc. Items 2 & 3 are essentially the same, but I wanted to call out the Yum repository since it's a top priority to happen this week. :) Here are my proposals for this: A. We have a neutral package repository URL base of ovirt.org/repo. B. The same directory tree can host .zip and tarballs. C. We setup ftp.ovirt.org to serve FTP and HTTP of the /repo directory as the DocumentRoot for ftp.ovirt.org. Any thoughts? - - Karsten http://ovirt.org/wiki/Yum_repo_file # Place this file in your /etc/yum.repos.d/ directory [ovirt] name=Builds of the oVirt project baseurl=http://ovirt.org/repo/fedora-$releasever/$basearch/ enabled=1 skip_if_unavailable=1 gpgcheck=0 [ovirt-source] name=Builds of the oVirt project - Source baseurl=http://ovirt.org/repo/fedora-$releasever/$basearch/SRPMS enabled=0 skip_if_unavailable=1 gpgcheck=0 - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFOwsyA2ZIOBq0ODEERAop6AKCH1+gtRh4P+d6xch59EH2eoQSVJgCdFUQC b3yLPRVNTM/FjScNHCSIxDs= =fa0q -----END PGP SIGNATURE-----
On Tue, 2011-11-15 at 12:33 -0800, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
So the requests I have received or heard so far around "providing package and tarball download locations" are:
1. ftp.ovirt.org as location with packages for various distros as well as binary and source tarballs.
2. Yum repository for the Fedora packages being worked on, until they get in to Fedora.
3. Location for different distros package management tools to find packages.
4. Centrally maintained details (examples) of the files used for different package management needs, e.g. files for /etc/yum.repos.do/ etc.
Items 2 & 3 are essentially the same, but I wanted to call out the Yum repository since it's a top priority to happen this week. :)
Here are my proposals for this:
A. We have a neutral package repository URL base of ovirt.org/repo.
I agree on most of this, but I'd call it releases instead of repo Mike
B. The same directory tree can host .zip and tarballs.
C. We setup ftp.ovirt.org to serve FTP and HTTP of the /repo directory as the DocumentRoot for ftp.ovirt.org.
Any thoughts?
- - Karsten
http://ovirt.org/wiki/Yum_repo_file
# Place this file in your /etc/yum.repos.d/ directory
[ovirt] name=Builds of the oVirt project baseurl=http://ovirt.org/repo/fedora-$releasever/$basearch/ enabled=1 skip_if_unavailable=1 gpgcheck=0
[ovirt-source] name=Builds of the oVirt project - Source baseurl=http://ovirt.org/repo/fedora-$releasever/$basearch/SRPMS enabled=0 skip_if_unavailable=1 gpgcheck=0
- -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFOwsyA2ZIOBq0ODEERAop6AKCH1+gtRh4P+d6xch59EH2eoQSVJgCdFUQC b3yLPRVNTM/FjScNHCSIxDs= =fa0q -----END PGP SIGNATURE----- _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On 11/15/2011 03:54 PM, Mike Burns wrote:
On Tue, 2011-11-15 at 12:33 -0800, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
So the requests I have received or heard so far around "providing package and tarball download locations" are:
1. ftp.ovirt.org as location with packages for various distros as well as binary and source tarballs.
2. Yum repository for the Fedora packages being worked on, until they get in to Fedora.
3. Location for different distros package management tools to find packages.
4. Centrally maintained details (examples) of the files used for different package management needs, e.g. files for /etc/yum.repos.do/ etc.
Items 2 & 3 are essentially the same, but I wanted to call out the Yum repository since it's a top priority to happen this week. :)
Here are my proposals for this:
A. We have a neutral package repository URL base of ovirt.org/repo. I agree on most of this, but I'd call it releases instead of repo
why not have releases as a subdir of repo? As we will most likely also have a subdir for nightly builds for example Carl.
On 11/16/2011 04:56 PM, Carl Trieloff wrote:
On 11/15/2011 03:54 PM, Mike Burns wrote:
On Tue, 2011-11-15 at 12:33 -0800, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
So the requests I have received or heard so far around "providing package and tarball download locations" are:
1. ftp.ovirt.org as location with packages for various distros as well as binary and source tarballs.
2. Yum repository for the Fedora packages being worked on, until they get in to Fedora.
3. Location for different distros package management tools to find packages.
4. Centrally maintained details (examples) of the files used for different package management needs, e.g. files for /etc/yum.repos.do/ etc.
Items 2& 3 are essentially the same, but I wanted to call out the Yum repository since it's a top priority to happen this week. :)
Here are my proposals for this:
A. We have a neutral package repository URL base of ovirt.org/repo. I agree on most of this, but I'd call it releases instead of repo
a more burning question (from my POV anyway) how can i get access to ovirt.org so i'll be able to upload the ovirt's rpm set once its done?
why not have releases as a subdir of repo? As we will most likely also have a subdir for nightly builds for example
Carl. _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/16/2011 07:01 AM, Ronen Angluster wrote:
a more burning question (from my POV anyway) how can i get access to ovirt.org so i'll be able to upload the ovirt's rpm set once its done?
How is that normally going to occur? Is it going to (eventually) be automated from a tool? I suppose it's only a matter of setting up shell accounts to have write access to /var/www/html/repo/. Is there another (standard) way to handle this? - - Karsten - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFOw9H62ZIOBq0ODEERAtEuAJ9NyT8wCXLgOeWI8LNVPuXvb7T2xwCg0km8 xH8UPeTG9qs01Wxe6hvkSNY= =IeuJ -----END PGP SIGNATURE-----
On Wed, 2011-11-16 at 07:08 -0800, Karsten 'quaid' Wade wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/16/2011 07:01 AM, Ronen Angluster wrote:
a more burning question (from my POV anyway) how can i get access to ovirt.org so i'll be able to upload the ovirt's rpm set once its done?
How is that normally going to occur? Is it going to (eventually) be automated from a tool?
I suppose it's only a matter of setting up shell accounts to have write access to /var/www/html/repo/. Is there another (standard) way to handle this?
I worked with Karsten and Steve on this a bit on IRC, and have a slightly better design and process to start from. This is obviously open for discussion, but here's what I'm thinking: Project release managers upload a tarball or zip with the appropriate packages and sources, etc. This tarball has a pre-defined layout. The upload is done to a generic location (not directly to /var/www/html/repo). A script running in a cron job unpacks and places files in the appropriate locations. The actual directory structure is here: http://ovirt.org/wiki/Releases I assume that we'll populate the nightlies directory directly from jenkins once it's up and running. Format for the tarball should be essentially the directory strcuture under the stable directory Mike
- - Karsten - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFOw9H62ZIOBq0ODEERAtEuAJ9NyT8wCXLgOeWI8LNVPuXvb7T2xwCg0km8 xH8UPeTG9qs01Wxe6hvkSNY= =IeuJ -----END PGP SIGNATURE----- _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
participants (4)
-
Carl Trieloff -
Karsten 'quaid' Wade -
Mike Burns -
Ronen Angluster