- Infra - oVirt List Archives

how we do things
by Karsten 'quaid' Wade 16 Nov '11

16 Nov '11

-----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.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/ iD8DBQFOw0q92ZIOBq0ODEERAqryAJ0T0uu9SXo+h9hBHzzR3px6AqBV5wCfclli JhR9OnD6pVlAUd3fVsGE/SI= =TQ6c -----END PGP SIGNATURE-----

2 1

version controlling our configurations
by Karsten 'quaid' Wade 16 Nov '11

16 Nov '11

-----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.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/ iD8DBQFOw0Na2ZIOBq0ODEERArXNAJwK7l3yeV2HWwfDKyUNWIx4o1HlwQCg1vbN GONkwgIYlgBuCvx7aLr/oTg= =thSr -----END PGP SIGNATURE-----

2 1

Mailing list request
by Mike Burns 16 Nov '11

16 Nov '11

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

4 9

Request for documentation GIT repository.
by Steve Gordon 15 Nov '11

15 Nov '11

Hi, I would like to request creation of an ovirt-docs GIT repository for any and all documentation activity which is to occur outside of the wiki, particularly in formats that might initially be imported from other sources (DocBook XML). Thanks, Steve

4 12

Ovirt wiki account
by Asaf Shakarchi 10 Nov '11

10 Nov '11

Hey, Can anyone please open for me a wiki account named 'asaf' on Ovirt? Regards, Asaf

4 3

Use of nickserv for nick registration on irc.oftc.net
by Yair Zaslavsky 07 Nov '11

07 Nov '11

Hi all, I found out that irc.oftc.org has a nick services bot (named nickserv). This bot can be used to register our nicks on that server. As open source is project is open to the public issues of nick collisions may occur. I am wondering whether we should use nickserv for that. It is possible to get it's help by typing /msg nickserv help Regards, Yair

3 2

gerrit.ovirt.org now has gitweb
by Itamar Heim 07 Nov '11

07 Nov '11

gerrit will show a 'gitweb' link next to the patch set when reviewing a patch. you can use gitweb directly as well: http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git

2 2

ovirt-engine repo up in gerrit.ovirt.org!
by Itamar Heim 30 Oct '11

30 Oct '11

Here we go... - gerrit is up. - ovirt-engine git repo is there. - will upload the other repositories soon. below you can find the steps on how to get the code (yes, coming to you in wiki soon). a link to the wiki on how to build oVirt will be sent soon by Livnat. It's exciting to see everyone coming together to build a community, and I'm looking forward to working together on oVirt. Welcome everyone, Itamar How to use: 1. registering as a user: - you can use any OpenID provider for now[1] - login page shows google and yahoo - any fedora FAS account can login as well via https://admin.fedoraproject.org/accounts/openid/id/<username> 2. set ssh keys in gerrit settings - on your local machine, create a set of ssh keys if you don't have one via 'ssh-keygen -t rsa' - update via gerrit settings the ssh public key to allow ssh to gerrit 3. define gerrit in ~/.ssh/config Host gerrit.ovirt.org HostName gerrit.ovirt.org Port 29418 User <username> 4. check ssh works correctly, verify and ack the host fingerprint: ssh gerrit.ovirt.org if you get this, it is fine: *** Welcome to Gerrit Code Review **** 5. cloning the repo git clone gerrit.ovirt.org:ovirt-engine this can be done without registering to gerrit using: git clone git://gerrit.ovirt.org/ovirt-engine 6. install the change-Id hook - you must do this before you commit anything: scp -p gerrit.ovirt.org:hooks/commit-msg .git/hooks/ 7. do some work/commit/etc. wiki link on how to build/run ovirt will be sent by Livnat soon. 8. rebase: git fetch gerrit.ovirt.org:ovirt-engine master 9. push your patch for review: git push gerrit.ovirt.org:ovirt-engine HEAD:refs/for/master 10. track patch review process the review process is comprised of: - anyone can send a patch - anyone can code review and comment on the patch and +1/-1. This helps maintainers in reviewing the patches. - a maintainer can code review it with +2 it, which is required to commit (submit) it. - someone (anyone) needs to confirm they checked the patch works and flag it as verified +1 - a maintainer can submit (commit) the patch when it has: Code Review: +2 Verified: +1 - nacked (-1) patches should not be submitted - a submitted patch is merged to the git TODOs: - emails to mailing list on patches/commits[2] - upload repos of more projects - have gerrit add acked-by/verified-by based on the gerrit reviewes? - mirror to github [1] if anyone provides a reason to limit to specific OpenID providers that's an option as well. [2] basic emails until we merge the gerrit patches sending them inline - we are working on sending them to upstream gerrit.

6 14

Re: mail sever
by Karsten Wade 30 Oct '11

30 Oct '11

--O9T4zNOkGnr0n+A/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Including the infra@ list so others are aware we are setting up lists.ovirt.org as a relay server for gerrit.ovirt.org. On Sat, Oct 29, 2011 at 12:10:36PM +0200, Itamar Heim wrote: > I think it will be better to set one up. > it doesn't make sense to me we'll secure, deal with black listing, > etc. for each server separately (jenkins will also need to send > emails, and maybe more servers tomorrow). > > I think using lists.ovirt.org and either allowing relay from > specific hosts is better than yet another server to maintain. > or maybe require smtp authentication which is best i think. >=20 > but i really need one soon, since gerrit without email notification > is not very friendly... In my mind, it's arguable what is the right way to proceed as an infrastructure - one central SMTP or each host has it's own, we can debate that. For now, considering black/white listing etc., yes, I agree that using lists.ovirt.org is more efficient. I'm working on getting postfix to agree to my change. Go ahead and tell Gerrit to use lists.ovirt.org as an SMTP host, and I'll do some relay testing later when I can get 'postconf -d' to show me what I put in main.cf. - Karsten --=20 name: Karsten 'quaid' Wade, Sr. Community Gardener team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 --O9T4zNOkGnr0n+A/ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iD8DBQFOrcYf2ZIOBq0ODEERAtC7AJ0Rff/XHJWlHchHu3mfAlTCFNdcwQCgucmr PzNfLMG3h9NsTf5PqvxbRZ8= =WCxU -----END PGP SIGNATURE----- --O9T4zNOkGnr0n+A/--

1 0

Have your own website traffic generator
by Hit Booster 29 Oct '11

29 Oct '11

1 0