smtp server for ovirt.org
by Eyal Edri
Do we have an SMTP server configured for oVirt?
I'm starting to configure the Jenkins CI server and it requires an SMTP
server for sending alerts via email.
Eyal.
13 years, 1 month
git for server config tracking
by Karsten 'quaid' Wade
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Today I setup local git repos on linode01.ovirt.org for tracking the
services' configurations: Mailman, Wordpress, Supybot, MediaWiki, and
/etc.
Hopefully my idea here is sane. If it's not, help me make it sane. :)
It's clearly not a solution equivalent to Puppet or Chef, but I'm not
trying to add a new service :) I'm trying to make sure we have a
handle on where we are right now in a lightweight, it's-just-done way.
In /root/git:
ls -l
total 4
lrwxrwxrwx 1 root root 4 Dec 14 18:37 ovirt-infra-etc -> /etc
lrwxrwxrwx 1 root root 25 Dec 14 18:21 ovirt-infra-mailman ->
/usr/lib/mailman/Mailman/
lrwxrwxrwx 1 root root 16 Dec 14 16:51 ovirt-infra-mediawiki ->
/var/www/html/w/
lrwxrwxrwx 1 root root 17 Dec 14 16:54 ovirt-infra-supybot ->
/var/lib/supybot/
lrwxrwxrwx 1 root root 21 Dec 14 16:52 ovirt-infra-wordpress ->
/usr/share/wordpress/
- -rw-r--r-- 1 root root 172 Dec 14 16:50 REPOS
Each of the symlinked directories now was initialized as a git repo.
Then I created this tree as the central origin:
ls -l /usr/local/git_root/
total 20
drwxr-xr-x 7 root root 4096 Dec 14 18:38 ovirt-infra-etc.git
drwxr-xr-x 7 root root 4096 Dec 14 18:23 ovirt-infra-mailman.git
drwxr-xr-x 7 root root 4096 Dec 14 18:30 ovirt-infra-mediawiki.git
drwxr-xr-x 7 root root 4096 Dec 14 18:33 ovirt-infra-supybot.git
drwxr-xr-x 7 root root 4096 Dec 14 17:09 ovirt-infra-wordpress.git
I'm working on the wiki page about how it's setup, but essentially I
did this for each repository:
mkdir foo-project.git
cd foo-project.git/
git --bare init
git config core.sharedrepository 1
git config receive.denyNonFastforwards true
find objects -type d -exec chmod 02770 {} \;
cd /root/git/foo-project.git
git remote add origin /usr/local/git_root/foo_project.git
git push origin master
git checkout origin/master
git branch -f master origin/master
git checkout master
All of this won't leave any of the servers and be without root:root
ownership because these git repositories contain actual passwords for
all these services.
- - 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/
iD8DBQFO6TWW2ZIOBq0ODEERAjgsAKDAbQrHDWl/hji0gSBIkGVwoyYLPgCdE8oI
7+5N9jHC2pzs45I2tsO+UHQ=
=Njkr
-----END PGP SIGNATURE-----
13 years, 1 month
Re: discussion tab (was [Engine-devel] API design and plan)
by Itamar Heim
moving discussion to infra list - is there a way to disable the
discussion tabs on the wikis if people prefer mailing lists to discuss
item to avoid confusing people?
On 12/13/2011 03:02 PM, Jon Choate wrote:
....
>>>> Is there a bias towards using the mailing list and against the
>>>> discussion tab on the wiki page when discussing wiki pages? Just
>>>> want to
>>>> know. I'm used to commenting on wikis on the discussion page.
>>>
>>> mailing list - shouldn't be.
>>> wiki - may be lost on the larger audience - I think discussing on
>>> the
>>> mailing list makes more sense since many don't subscribe to the
>>> wiki
>>> pages after their first review from when it was published.
>>
>> No offense, but the only thing which is more broken than email for
>> discussing such things is a wiki discussion (mailing list at least
>> pushes changes by default. has clients to manage replies by threads,
>> responses can be sent concurrently etc).
>>
> No offense taken, different tools work better for different groups of people. If we do not want to use the discussion tabs, is there a way to get rid of them so we don't have people posting comments there?
13 years, 1 month
Gerrit backup
by Karsten 'quaid' Wade
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I did a first pass at creating a backup process for gerrit.ovirt.org:
http://ovirt.org/wiki/Gerrit_backup
Right now it uses rsync on /usr/local/src/git to a remote directory at
ovirt.org:/home/gerrit-backup/gerrit.ovirt.org-src-backup/src/ .
So that's my hacky process and bash script to start. Very open to
other ideas.
One I'm not clear on is what we really need backed up from
gerrit.ovirt.org? I'd like us to get /etc in a private git repo, maybe
we just do that as a single repo that we distribute across all hosts'
/root directories? Should we also be using git for backing up the git
repo - so have gerrit-backup on the remote host pull changes instead
of pushing a directory structure via rsync?
Itamar mentions that we need to backup the Gerrit DB, which I'll work
on next. I reckon that's a combination of a dump of the database and
rsyncing the results to the remote host?
- - 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/
iD8DBQFO344x2ZIOBq0ODEERAu3TAKDDLtt5jr/a78mMLnW8T0eqSVx1fQCgi2c1
7lTFWA0VPPtuuIkokqk+JbI=
=xt+L
-----END PGP SIGNATURE-----
13 years, 1 month
