Hi,
Is it possible to extend the list of supported files detailed on [1] to
include also the suffix of: txt, xml and dia (dia stands for Dia diagram
editor)?
[1] http://www.ovirt.org/wiki/Special:Upload
Thanks,
Moti

Hi,
As the result of the call for additional list moderators we would like to request that the following users be added as moderators:
abaron(a)redhat.com for arch(a)ovirt.org
ofrenkel(a)redhat.com for engine-devel(a)ovirt.org
sgordon(a)redhat.com for users(a)ovirt.org
This was discussed in the most recent oVirt sync meeting and this request is the outcome of this discussion:
http://ovirt.org/meetings/ovirt/2011/ovirt.2011-11-23-15.00.html
Thanks,
Steve

Since we all know that compiling oVirt on fedora for the first time downloads a very large amount of jars...
We need to think about mirroring the maven repositories we're using.
There are a few advantages for that:
* closer and faster servers
* better control over the servers, meaning if the original repos are down, ours can still be online.
* there is a chance we can be temporarily blocked if too many d/l are bring done. (or if some user d/l the entire repo using wget for e.g.)
here is info about mirroring from the maven site:
http://maven.apache.org/guides/mini/guide-mirror-settings.html
Eyal Edri.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm adding infra(a)ovirt.org to this discussion - nothing here need be
private (except for an internal machine name I trimmed.)
On 11/17/2011 09:12 AM, Ofer Schreiber wrote:
> Hey,
>
> Ronen finished creating the first rpms for ovirt [1] and vdsm
> [2].ovirt)
>
> I've uploaded all the 22 rpms (ovirt, vdsm and jboss) into
> /var/www/html/releases/0.0.1_0001-0/fc16 on ovirt.org. It seems
> that /releases is not mapped in apache to the right directory.
> Karsten - can you please add "Alias /releases
> /var/www/html/releases" to lists.ovirt.org.conf? I didn't want to
> do this by myself.
Hmm, I dropped a / one one side of the Alias, because it's there
somewhat and works somewhat. I'm going to do both /releases/ and
/releases (Wordpress tries to grab both, basically.)
Alias /releases/ /var/www/html/releases/
Alias /releases /var/www/html/releases
That seems to have solved the directory traversal problem.
Mike and I worked up some directory structure that he is sending to
the open thread.
>
> [1]ovirt rpms created from
> d28a4d368412a89d652d62db304f7976466aab34 [2] vdsm rpms created from
> 1895f39f62af9e751e513a07dda6a75a31cf5d4a
>
- - Karsten
- --
name: Karsten 'quaid' Wade, Sr. Community Architect
team: Red Hat Community Architecture & Leadership
uri: http://communityleadershipteam.orghttp://TheOpenSourceWay.org
gpg: AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFOxV1E2ZIOBq0ODEERAhxPAJwLzxBU3yvIqaEbSx6KVxqg/RH2ZgCgmyIe
KQZ1wB7e8f6AUoDeK0cuqm8=
=OTTW
-----END PGP SIGNATURE-----

-----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.orghttp://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-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ofer - I set up your sshkey and sudo access, as per this procedure:
http://ovirt.org/wiki/Adding_a_new_system_administrator_to_a_host
The real question is, how do we make sure that we are working in the
same direction?
Documenting everything we do is one way. Version controlling the
configuration files will help with rollback & learning we have done
each time.
Talking with Apache infra folk earlier, I learned about 'ckl':
https://www.apache.org/dev/ckl.html
It is a wrapper for your shell session; when you close the session,
the contents are written to a database with a user-written log message
of what and why the work was done. This in then queued for other
admins to review the work.
What is a good-enough way to get started that will take us somewhere sane?
- - Karsten
- --
name: Karsten 'quaid' Wade, Sr. Community Architect
team: Red Hat Community Architecture & Leadership
uri: http://communityleadershipteam.orghttp://TheOpenSourceWay.org
gpg: AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFOw0q92ZIOBq0ODEERAqryAJ0T0uu9SXo+h9hBHzzR3px6AqBV5wCfclli
JhR9OnD6pVlAUd3fVsGE/SI=
=TQ6c
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Just like I would be nervous without backup, I'm nervous that our
configuration files are not (yet) under version control.
I'd prefer that we use e.g. Puppet or Chef (I'd like to try Puppet
because of the knowledge around me, but am flexible if you are a Chef
du jour), but until we get to that, I had a quick-fix idea.
Because /etc contains a few passwords, I don't want to put this on any
open systems, and we don't have that many systems (yet) to have a
dedicated backup/config cluster (or whatever is the solution there.)
What if we use a local git repo on linode01.ovirt.org, then do a
checkout on each of the other hosts so root can locally update the
repository and push to the master on linode01? Trusted admins can have
a clone of the repository locally (on their encrypted partitions, natch.)
Good? Bad? Have a better solution for now?
- - Karsten
- --
name: Karsten 'quaid' Wade, Sr. Community Architect
team: Red Hat Community Architecture & Leadership
uri: http://communityleadershipteam.orghttp://TheOpenSourceWay.org
gpg: AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFOw0Na2ZIOBq0ODEERArXNAJwK7l3yeV2HWwfDKyUNWIx4o1HlwQCg1vbN
GONkwgIYlgBuCvx7aLr/oTg=
=thSr
-----END PGP SIGNATURE-----

I'm not sure this is the right place, but it seems like the logical
place to me.
I need a node-patches@ mailing list for the node project. Any
additional steps I need to take to get this done?
Thanks
Mike