[Users] oVirt Weekly Meeting Minutes -- 2012-06-06

[Dan Kenigsberg]

On Wed, Jun 06, 2012 at 11:45:17PM +0300, Itamar Heim wrote:
> On 06/06/2012 09:35 PM, Dan Kenigsberg wrote:
> >On Wed, Jun 06, 2012 at 10:59:35AM -0400, Ofer Schreiber wrote:
> >>Minutes:        http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-06-14.01.html
> >>Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-06-14.01.txt
> >>Log:            http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-06-14.01.log.html
> >>
> >>=========================
> >>#ovirt: oVirt Weekly Sync
> >>=========================
> >>
> >>
> >>Meeting started by oschreib at 14:01:34 UTC. The full logs are available
> >>at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-06-14.01.log.html
> >>
> >>Meeting summary
> >>---------------
> >>* agenda and roll call  (oschreib, 14:01:45)
> >>
> >>* Release status  (oschreib, 14:04:32)
> >>   * devel freeze June 7 (tomorrow)  (oschreib, 14:04:44)
> >>   * Beta shortly after  (oschreib, 14:04:50)
> >>   * GA June 27  (oschreib, 14:04:56)
> >>   * test day June 14  (oschreib, 14:05:07)
> >>   * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=824420
> >>     (oschreib, 14:06:51)
> >>   * AGREED: ovirt 3.1 feature freeze will be 07.06.2012 (tomorrow)
> >>     (oschreib, 14:09:04)
> >>   * node should be ready few days after  (oschreib, 14:09:17)
> >>   * vdsm is in feature freeze  (aglitke, 14:11:47)
> >>   * AGREED: mburns will be release manager next week  (oschreib,
> >>     14:13:31)
> >>   * ACTION: mburns to replace oschreib as release manager next week
> >>     (oschreib, 14:14:05)
> >>
> >>* sub project status -- vdsm  (oschreib, 14:14:29)
> >>   * AGREED: vdsm version should be bumped  (oschreib, 14:20:20)
> >>   * ACTION: danken to handle vdsm version until tomorrow  (oschreib,
> >>     14:20:35)
> >
> >We'd bump vdsm version to 4.10.0 tomorrow, hopefully with
> >Yair's http://gerrit.ovirt.org/#/c/5062/ included.
> >
> >>
> >>* sub project status -- engine  (oschreib, 14:21:15)
> >>   * things in good shape on the engine side  (oschreib, 14:23:00)
> >>
> >>* sub project status -- node  (oschreib, 14:23:31)
> >>   * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=824420
> >>     (oschreib, 14:25:39)
> >>   * node should support F17 in the next couple of days  (oschreib,
> >>     14:26:01)
> >>   * ACTION: fabiand to update BZ#824420  (oschreib, 14:26:50)
> >>
> >>* Workshops and Conferences  (oschreib, 14:27:17)
> >>   * bazulay and mburns are presenting ovirt in linux con Japan this week
> >>     (oschreib, 14:29:40)
> >>   * there will be an ovirt day in n linuxcon NA, then 2.5 co-hosted with
> >>     kvm forum in linuxcon europe  (oschreib, 14:31:43)
> >>
> >>* Other Topics  (oschreib, 14:31:48)
> >>   * LINK: http://www.ovirt.org/releases/beta/fedora/17/   (oschreib,
> >>     14:33:24)
> >>   * pre feature freeze F17 builds  (oschreib, 14:33:40)
> >>   * ACTION: oschreib to look for test day lead  (oschreib, 14:37:03)
> >>   * vdsms's setupNetwork is broken  (oschreib, 14:39:15)
> >>   * ACTION: aglitke to link setupNetwork bug on
> >>     https://bugzilla.redhat.com/show_bug.cgi?id=822145  (oschreib,
> >>     14:39:48)
> >>
> >>Meeting ended at 14:55:40 UTC.
> >>
> >>Action Items
> >>------------
> >>* mburns to replace oschreib as release manager next week
> >>* danken to handle vdsm version until tomorrow
> >>* fabiand to update BZ#824420
> >>* oschreib to look for test day lead
> >>* aglitke to link setupNetwork bug on
> >>   https://bugzilla.redhat.com/show_bug.cgi?id=822145
> >
> >After a casual review of http://www.ovirt.org/wiki/Second_Release I
> >understand that setupNetwork is not a strict citerion for this release.
> >
> >   MUST: Can define VLAN based networks, bond interfaces, and have VLANs over bonded interfaces
> >
> >Hence, I do not think that setupNetwork is a release blocker. However,
> >Avi/Adam, could you please see if this requirement is currently
> >satisfied, and if not open a blocking bug?
> 
> do you mean this works using setupNetworks, or the old api should be used?
> since i'm pretty sure engine needs to be changed to be told to use
> the old API for a 3.1 cluster.

We would try to make this work via setupNetworks.
If we fail to do this on time, we would do the necessary changes all
over the stack to make it happen via addNetwork.