- Board - oVirt List Archives

organizing oVirt workshops and meetups
by Carl Trieloff 14 Nov '11

14 Nov '11

I have created the following page to start coordination around. http://ovirt.org/wiki/Outreach If you add to the table or just mail the list with any event that you believe we should be present at. I'll build a master table and then we can work out the locations and venues to have the workshops, and setup a system to promote the meetups etc. Carl.

5 11

oVirt google+ page?
by Ryan Harper 11 Nov '11

11 Nov '11

Should we make a google+ ovirt page? http://www.google.com/+/business/ -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx ryanh(a)us.ibm.com

4 3

FOSDEM
by Chris Wright 11 Nov '11

11 Nov '11

FOSDEM has a 2 day Open Source virtualization and cloud track. OpenStack folks are planning to attend, might be a good opportunity to get some cross project collaboration as well as a chance to get oVirt folks together. ----- Forwarded message from Thierry Carrez <thierry(a)openstack.org> ----- Date: Fri, 11 Nov 2011 11:34:22 +0100 From: Thierry Carrez <thierry(a)openstack.org> To: "openstack(a)lists.launchpad.net" <openstack(a)lists.launchpad.net> Subject: [Openstack] OpenStack at FOSDEM Hi everyone, Our OpenStack devroom was accepted for FOSDEM, February 4-5, 2012 in Brussels. It was actually grouped with other "Open Source virtualization and cloud" projects in a giant devroom (550-seat auditorium) that lasts the full 2 days ! Expect a CFP in the coming weeks... See other devrooms at: http://fosdem.org/2012/devrooms_for_2012 -- Thierry Carrez (ttx) Release Manager, OpenStack

1 0

security@ovirt.org mailing list
by David Jorm 10 Nov '11

10 Nov '11

Hi All I would like to create a security(a)ovirt.org mailing list. The list would be used to capture reports of security flaws affecting projects under the oVirt umbrella, not for general security discussion. I would then like to create a security page on the wiki, mentioning this list and encouraging people to report flaws. The list should be private, with approval required to subscribe. I would like one of the initial subscribers to be secalert(a)redhat.com. All messages sent to this address result in an RT ticket in the Red Hat Security Response Team (SRT) queue. SRT looks at all of these tickets within one business day. What does everyone think of this idea? Thanks -- David Jorm / Red Hat Security Response Team

7 10

Need more mentors?
by Justin Clift 09 Nov '11

09 Nov '11

Hi guys, If you need further people to assist the project as a mentor, I'm up for it. ? Regards and best wishes, Justin Clift -- Aeolus Community Manager http://www.aeolusproject.org

2 1

oVirt launch
by Carl Trieloff 09 Nov '11

09 Nov '11

Thank you all for a very sucessfull launch last week of oVirt. From what I can tell is that we have had over 4800 unique people come to download oVirt since the project was hosted last week. Help get the word out, anyway you choose. regards Carl.

2 2

[VOTE] Include Nomad into the oVirt Incubator
by Carl Trieloff 29 Oct '11

29 Oct '11

This vote is to include Nomad into the oVirt incubtaor. Details about the project can be found at http://www.ovirt.org/wiki/Project_Proposal_-_Nomad More information about the incubator at oVirt can be found at http://www.ovirt.org/governance/adding-a-subproject/ In order to be accepted into the incubator, the project needs to be able to articulate its goals, scope and how it relates/integrates with the oVirt project. Nomad has done this. Entering the incubator is the low bar vote, which Nomad in my view clearly gets over. Note that the vote from incubator to full oVirt project (not this vote) is where we look for the demonstration of project criteria. The idea with the incubator is that any project that can articulate how it relates to oVirt should be able to enter the incubator and then work out details while in incubation. Vote open till the 27th. Here is my +1 Carl.

14 18

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

29 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 16

[VOTE RESULT] Nomad -- Please join in welcoming Nomad to the oVirt incubator.
by Carl Trieloff 27 Oct '11

27 Oct '11

Total of 13 votes, all +1 which includes 8 binding votes. Isaac, I can work with you in getting project setup and please feel free to prepare a talk on it for one of the break out slots at the workshop. A warm welcome, Carl.

1 0

[VOTE RESULT] Mom - Please join in welcoming Mom to the oVirt incubator.
by Carl Trieloff 27 Oct '11

27 Oct '11

Total of 8 votes, all +1 which includes 7 binding votes. Adam, I can work with you in getting project setup and please feel free to prepare a talk on it for one of the break out slots at the workshop. A warm welcome, Carl.

1 0