- Board - oVirt List Archives

key points for next oVirt press release
by Jason Brooks 07 Feb '12

07 Feb '12

I'm putting together key points to include in the press release announcing the first release of oVirt and the oVirt Beijing workshop. What am I leaving out / what more ought we line up to include? * oVirt 3.0 1. What key elements/features of oVirt do we want to emphasize here? I'm referring to the release notes (http://www.ovirt.org/wiki/Release_Notes) for the main points of this release. * oVirt Beijing Workshop 1. March 21, 2012 2. IBM Campus, Beijing 3. RSVP address rsvp(a)ovirt.org 4. For more information: http://www.ovirt.org/news-and-events/workshop/ * Board member quotes 1. Will the release include quotes from participating companies / members? Thanks, Jason

1 0

oVirt's First Release go/no go meeting
by Ofer Schreiber 07 Feb '12

07 Feb '12

The following is a new meeting request: Subject: oVirt's First Release go/no go meeting Organizer: "Ofer Schreiber" <oschreib(a)redhat.com> Location: #ovirt on oftc Time: Tuesday, February 7, 2012, 5:00:00 PM - 6:00:00 PM GMT +02:00 Jerusalem Invitees: engine-devel(a)ovirt.org; node-devel(a)ovirt.org; board(a)ovirt.org *~*~*~*~*~*~*~*~*~* This is the official go/no go meeting for Ovirt's first release. Useful resources: 1. http://www.ovirt.org/wiki/Releases/First_Release_Blockers 2. http://www.ovirt.org/wiki/Releases/First_Release

1 0

oVirt Beijing - March 21st
by Carl Trieloff 03 Feb '12

03 Feb '12

Spread the word/ come join us! http://www.ovirt.org/news-and-events/workshop/ Carl.

1 0

Re-targeting oVirt's first release to Feb 9th
by Ofer Schreiber 02 Feb '12

02 Feb '12

We're re-targeting oVirt's first release to February 9th. An official go/no-go meeting will take place in #ovirt irc channel, at 15:00UTC, February 7th. Thanks, The oVirt team

2 2

Meeting minutes 2012-02-01
by Karsten (quaid) Wade 01 Feb '12

01 Feb '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Minutes: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-02-01-15.02.html Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-02-01-15.02.txt Log: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-02-01-15.02.log.html - --- ================================= #ovirt: oVirt weekly sync meeting ================================= Meeting started by rbergeron at 15:02:52 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-02-01-15.02.log.html . Meeting summary - --------------- * Agenda for today (rbergeron, 15:03:18) * Release Status (rbergeron, 15:04:24) * LINK: http://ovirt.org/wiki/Releases/First_Release_Blockers (mburns, 15:05:53) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=785728 (mburns, 15:09:59) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=782663 (mburns, 15:10:51) * AGREED: https://bugzilla.redhat.com/show_bug.cgi?id=782663 is a blocker (rbergeron, 15:14:09) * https://bugzilla.redhat.com/show_bug.cgi?id=782663 should be fixed and merged tomorrow (oschreib, 15:16:28) * ovirt-node is ready, waiting for last vdsm build. (oschreib, 15:18:26) * engine is ready for first release (oschreib, 15:20:25) * LINK: http://gerrit.ovirt.org/#change,1360 (danken, 15:22:59) * https://bugzilla.redhat.com/show_bug.cgi?id=786174 is a blocker for VDSM (oschreib, 15:35:37) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=786143 - logcollector is broken (mgoldboi, 15:37:28) * ACTION: oschreib to try fix https://bugzilla.redhat.com/show_bug.cgi?id=786143 (oschreib, 15:39:42) * retargeting oVirt's first release to Feb 9th (oschreib, 16:04:41) * go/no go meeting on Feb 7th (oschreib, 16:04:51) * AGREED: oVirt first release now 9 Feb (quaid, 16:06:38) * AGREED: go/no-go meeting for first release 7 Feb (quaid, 16:06:49) Meeting ended at 16:07:35 UTC. Action Items - ------------ * oschreib to try fix https://bugzilla.redhat.com/show_bug.cgi?id=786143 Action Items, by person - ----------------------- * oschreib * oschreib to try fix https://bugzilla.redhat.com/show_bug.cgi?id=786143 * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * oschreib (78) * danken (25) * quaid (22) * mburns (21) * mgoldboi (16) * rvaknin (14) * rbergeron (14) * ovirtbot (10) * sgordon (9) * lpeer (7) * acathrow (6) * cctrieloff (5) * rharper (5) * jimjag (1) * xTs_w (1) * Guest747 (1) * deepakcs (1) * jboggs (1) * rgolan (1) - -- Karsten Wade -- http://iquaid.org - --------------------------------- http://Fairy-TaleFarm.com - --------------------------------- gpg key : AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFPKWPF2ZIOBq0ODEERApCMAKCfGju3qluGjXRW7AiAjp9HxOcgsgCfZjBm XOf4lcxqXbFXzNKYNIId5CU= =lnpC -----END PGP SIGNATURE-----

1 0

FOSDEM sessions
by Itamar Heim 31 Jan '12

31 Jan '12

fyi we got the following sessions in the FOSDEM[1] Open Source Virtualization and Cloud devroom. if you are planning to be in FOSDEM drop us an email if you would want to meet, discuss, catch up, etc. 1. Virtualization Management the oVirt way - Introducing oVirt (Itamar Heim) 2. VDSM - The oVirt Node Management Agent (Federico Simoncelli) 3. Open Virtualization – Engine Core: Internals and Infrastructure (Omer Frenkel) apart of it there are also some kvm sessions in the hypervisor main track. Hope to meet you there, Itamar [1] http://fosdem.org/2012/

3 3

release process details
by Jon Choate 30 Jan '12

30 Jan '12

given that the release date is potentially in three working days, is there someone knowledgeable who can add detail to this page? http://www.ovirt.org/governance/releases-and-release-management I'm guessing with the go/no-go meeting coming up on Monday, there may be increased interest in the release management process. Jon

2 1

Re: package signing
by David Jaša 30 Jan '12

30 Jan '12

Doron Fediuck píše v Ne 29. 01. 2012 v 14:21 +0200: > On 26/01/12 18:20, David Jaša wrote: > > Doron Fediuck píše v Čt 26. 01. 2012 v 11:01 -0500: > >> +1 for the need. > >> I think we should give md5 or similar hashes, > > > > There is already file with md5 hashes in the repo but it has no meaning > > wrt attack prevention because it is not accessible via https, let alone > > HTTP Strict Transport Security so it can be mangled by attacker together > > with packages themselves. > > > Setting up https access is probably the way to go. > We can sign the hash file as well, but that's just for binaries. > > >> and let distro's do the signing. > >> > > > > Distros take care of it during their package build process, no need to > > worry about that. But if we offer packages on our site, they should be > > also signed. > > > Actually, I just got the diff between our views; > Indeed when you distribute binaries, I agree you should sign it. > The thing is, I do not think we should distribute binaries. Fedora > should distribute ovirt RPM's, and other distro's should do the same > using their own packaging mechanisms. For example, Gentoo will look > for the sources tarball, and during the installation will d/l it, > compile and deploy according to the relevant (signed) ebuild. > > This is why fundamental projects will give you such links: > http://www.x.org/releases/X11R7.6/src/ > http://www.kernel.org/pub/linux/kernel/v3.x/ > http://kde.mirrorcatalogs.com/stable/4.8.0/ > > You may also see rel-notes, change-log and doc's, but no binaries. > > I'm aware of the fact many projects (postgres and others) provide > binaries as well, but my view is that this is the distro's task > to package & sign the binaries, and the project's task to provide > a stable release tarball of sources. > I think we agree more than it seems. IMO we should provide binaries of just development versions of oVirt for widely-used stable distributions which do not have better ways to create custom repos (like OpenSuse Build Service or Ubuntu PPA) - we do this for Fedora, Debian would be a good candidate, too. David > > David > > -- David Jaša, RHCE SPICE QE based in Brno GPG Key: 22C33E24 Fingerprint: 513A 060B D1B4 2A72 7F0D 0278 B125 CD00 22C3 3E24

2 1

Minutes from Go/No-Go meeting 2012-01-30
by Mike Burns 30 Jan '12

30 Jan '12

Minutes: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-01-30-15.01.html Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-01-30-15.01.txt Log: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-01-30-15.01.log.html Quick summary: Issues across multiple packages will cause a delay in the release. Thanks Mike

1 0

oVirt First Release Delay
by Ofer Schreiber 30 Jan '12

30 Jan '12

Due to several issues raised in the release meeting today [1], we're postponing oVirt's first release. We will re-evaluate the release date on Wednesday, during the weekly irc meeting. Thanks, The oVirt team [1] Release meeting minutes can be found at: http://ovirt.org/meetings/ovirt/2012/ovirt.2012-01-30-15.01.html

1 0