From fdeutsch at redhat.com  Tue Feb  4 13:37:35 2014
From: fdeutsch at redhat.com (Fabian Deutsch)
Date: Tue, 4 Feb 2014 08:37:35 -0500 (EST)
Subject: [node-devel] Cancelled: oVirt Node weekly meeting
Message-ID: <1810621977.14722938.1391521055414.JavaMail.root@redhat.com>

A single instance of the following meeting has been cancelled:

Subject: oVirt Node weekly meeting 
Organiser: "Fabian Deutsch" <fdeutsch at redhat.com> 

Location: irc://irc.oftc.net#ovirt 
Time: Tuesday, 4 February, 2014, 3:00:00 PM - 3:30:00 PM GMT +01:00 Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna
 
Invitees: node-devel at ovirt.org 


*~*~*~*~*~*~*~*~*~*

-------------- next part --------------
A non-text attachment was scrubbed...
Name: meeting.ics
Type: text/calendar
Size: 1494 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20140204/c822fbb2/attachment.ics>

From fabiand at redhat.com  Tue Feb 11 14:32:34 2014
From: fabiand at redhat.com (Fabian Deutsch)
Date: Tue, 11 Feb 2014 15:32:34 +0100
Subject: [node-devel] oVirt Node Weekly Meeting Minutes -- 2014-02-11
Message-ID: <1392129154.15403.0.camel@fdeutsch-laptop.local>

Minutes:
http://ovirt.org/meetings/ovirt/2014/ovirt.2014-02-11-14.06.html
Minutes (text):
http://ovirt.org/meetings/ovirt/2014/ovirt.2014-02-11-14.06.txt
Log:
http://ovirt.org/meetings/ovirt/2014/ovirt.2014-02-11-14.06.log.html


=================================
#ovirt: oVirt Node Weekly Meeting
=================================


Meeting started by fabiand at 14:06:23 UTC. The full logs are available
at http://ovirt.org/meetings/ovirt/2014/ovirt.2014-02-11-14.06.log.html
.



Meeting summary
---------------
* Agenda  (fabiand, 14:06:37)
  * Build status  (fabiand, 14:06:42)
  * oVirt 3.3.3  (fabiand, 14:06:50)
  * oVirt 3.4  (fabiand, 14:06:54)
  * Other Items  (fabiand, 14:07:07)

* Build Status  (fabiand, 14:07:49)
  * Pending patches in gerrit  (fabiand, 14:08:43)
  * Many patches merged two weeks ago with the stable build for
    ovirt-node-iso-3.0.4  (fabiand, 14:08:57)

* oVirt 3.3.3  (fabiand, 14:09:51)
  * LINK:
    http://fedorapeople.org/~fabiand/node/3.0.4/ovirt-node-iso-3.0.4-1.0.201401291204.vdsm33.el6.iso
    (fabiand, 14:10:19)
  * ACTION: fabiand to ask vdsm people about node testing  (fabiand,
    14:12:09)

* oVirt 3.4  (fabiand, 14:12:20)
  * ovirt-node iso also available for oVirt 3.4 testing  (fabiand,
    14:12:45)
  * LINK:
    http://fedorapeople.org/~fabiand/node/3.0.4/ovirt-node-iso-3.0.4-1.0.201401291204.vdsm34.el6.iso
    (fabiand, 14:12:51)

* Other Items  (fabiand, 14:14:58)

* oVirt Node Nightly  (fabiand, 14:15:41)
  * LINK: http://jenkins.ovirt.org/view/All/job/ovirt-node-iso/
    (sbonazzo, 14:17:33)
  * Nightly Node builds are welcome - Several options
    StableNode+NightlyVdsm    NightlyNode+NightlyVdsm  (fabiand,
    14:22:28)
  * CI needs updates  (fabiand, 14:25:15)
  * Jobs should use edit-node (if not already)  (fabiand, 14:25:26)

* Review  (fabiand, 14:26:26)

Meeting ended at 14:31:21 UTC.




Action Items
------------
* fabiand to ask vdsm people about node testing




Action Items, by person
-----------------------
* fabiand
  * fabiand to ask vdsm people about node testing
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* fabiand (71)
* sbonazzo (12)
* ovirtbot (5)
* spiekey (3)
* jboggs (3)
* rbarry (2)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20140211/ec89d30b/attachment.sig>

From fabiand at redhat.com  Tue Feb 25 14:53:06 2014
From: fabiand at redhat.com (Fabian Deutsch)
Date: Tue, 25 Feb 2014 15:53:06 +0100
Subject: [node-devel] oVirt Node Weekly Meeting Minutes -- 2014-02-25
Message-ID: <1393339986.24340.11.camel@fdeutsch-laptop.local>

Minutes:
http://ovirt.org/meetings/ovirt/2014/ovirt.2014-02-25-14.03.html
Minutes (text):
http://ovirt.org/meetings/ovirt/2014/ovirt.2014-02-25-14.03.txt
Log:
http://ovirt.org/meetings/ovirt/2014/ovirt.2014-02-25-14.03.log.html


=================================
#ovirt: oVirt Node Weekly Meeting
=================================


Meeting started by fabiand at 14:03:20 UTC. The full logs are available
at http://ovirt.org/meetings/ovirt/2014/ovirt.2014-02-25-14.03.log.html
.



Meeting summary
---------------
* Agenda  (fabiand, 14:03:30)
  * Patch review  (fabiand, 14:03:49)
  * Release status  (fabiand, 14:04:02)
  * Build status  (fabiand, 14:04:05)
  * Other Items  (fabiand, 14:04:08)

* Patch review  (fabiand, 14:06:22)
  * patch queue down  (fabiand, 14:08:35)
  * small problem with syntax check due to problematic pep8 / doctests
    on Fedora 19 builders  (fabiand, 14:08:50)
  * Moved syntax checks to el6 builders  (fabiand, 14:09:01)

* Release status  (fabiand, 14:09:16)
  * 3.0.4 is out for a while, never officially announce nor published
    (fabiand, 14:11:24)
  * temporary space issues have been sorted out  (fabiand, 14:11:34)
  * ACTION: fabiand to finally reach out to infra to sort out location
    of rpms+isos and final image push  (fabiand, 14:11:52)
  * Build status  (fabiand, 14:12:00)
  * ACTION: rbarry to create a jenkins job which takes an base image iso
    and adds the vdsm-plugin to create a layered iso.  (fabiand,
    14:24:12)
  * There should be one or more jenkins jobs ot create isos for 3.2 -
    3.4  (fabiand, 14:24:30)

* Other Items  (fabiand, 14:27:19)

Meeting ended at 14:29:30 UTC.




Action Items
------------
* fabiand to finally reach out to infra to sort out location of
  rpms+isos and final image push
* rbarry to create a jenkins job which takes an base image iso and adds
  the vdsm-plugin to create a layered iso.




Action Items, by person
-----------------------
* fabiand
  * fabiand to finally reach out to infra to sort out location of
    rpms+isos and final image push
* rbarry
  * rbarry to create a jenkins job which takes an base image iso and
    adds the vdsm-plugin to create a layered iso.
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* fabiand (70)
* eedri (13)
* jboggs (5)
* rbarry (4)
* sbonazzo (4)
* ovirtbot (4)
* knesenko (3)
* Rydekull (2)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20140225/19dd203b/attachment.sig>

From fabiand at redhat.com  Wed Feb 26 08:18:27 2014
From: fabiand at redhat.com (Fabian Deutsch)
Date: Wed, 26 Feb 2014 09:18:27 +0100
Subject: [node-devel] oVirt Node filesystem layout on resources.ovirt.org
Message-ID: <1393402707.2969.13.camel@fdeutsch-laptop.local>

Hey,

currently it is not easy to find oVirt Node (Base Image) releases on
resources.o.o - I'd like to suggest a layout simplification to remove
some clutter, improve the findability of isos and ease the maintenance.

Currently the (Node related) layout is:

releases
+ base
+ node-base
  + 3.0.0
    + iso
    + rpm
  + alpha
  + beta
  + nightly (symlink?)
  + stable (symlink to 3.0.0?)

could we please change the tree to be more like:

releases
+ node-base
  + 3.0
    + iso
    + rpm
  + stable (symlink to 3.0)

Some notes on the removed paths:
 base - Was unused
 alpha - To reduce overhead I'd use jenkins builds for alpha
 beta - To reduce overhead I'd use jenkins builds for beta
 beta - To reduce overhead I'd use jenkins builds for nightlies

Some more notes:
 3.0 - Just this one dir for all updates

This boils down to Node just offering stable images on resources.o.o.
Everything else can be pulled from jenkins (once we get everything into
shape again).

This suggestion is just for the "base image". Once the base images are
in place, jenkins can pick up the base images and generate "layered"
images which include vdsm (to be used with Engine).
The layered images can then be kept in the same place where the
remaining oVirt (Engine, vdsm, ...) packages are kept (for 3.3.3
in /releases/3.3.3/?).

Does that make sense?

- fabian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20140226/1dd5c533/attachment.sig>

From knesenko at redhat.com  Wed Feb 26 09:03:20 2014
From: knesenko at redhat.com (Kiril Nesenko)
Date: Wed, 26 Feb 2014 04:03:20 -0500 (EST)
Subject: [node-devel] oVirt Node filesystem layout on resources.ovirt.org
In-Reply-To: <1393402707.2969.13.camel@fdeutsch-laptop.local>
References: <1393402707.2969.13.camel@fdeutsch-laptop.local>
Message-ID: <280111502.18113260.1393405400580.JavaMail.zimbra@redhat.com>

We are moving to a new layout resources.ovirt.org/pub.

Please let us know where do you want to put your files.

- Kiril

----- Original Message -----
> From: "Fabian Deutsch" <fabiand at redhat.com>
> To: infra at ovirt.org
> Cc: "node-devel" <node-devel at ovirt.org>
> Sent: Wednesday, February 26, 2014 10:18:27 AM
> Subject: oVirt Node filesystem layout on resources.ovirt.org
> 
> Hey,
> 
> currently it is not easy to find oVirt Node (Base Image) releases on
> resources.o.o - I'd like to suggest a layout simplification to remove
> some clutter, improve the findability of isos and ease the maintenance.
> 
> Currently the (Node related) layout is:
> 
> releases
> + base
> + node-base
>   + 3.0.0
>     + iso
>     + rpm
>   + alpha
>   + beta
>   + nightly (symlink?)
>   + stable (symlink to 3.0.0?)
> 
> could we please change the tree to be more like:
> 
> releases
> + node-base
>   + 3.0
>     + iso
>     + rpm
>   + stable (symlink to 3.0)
> 
> Some notes on the removed paths:
>  base - Was unused
>  alpha - To reduce overhead I'd use jenkins builds for alpha
>  beta - To reduce overhead I'd use jenkins builds for beta
>  beta - To reduce overhead I'd use jenkins builds for nightlies
> 
> Some more notes:
>  3.0 - Just this one dir for all updates
> 
> This boils down to Node just offering stable images on resources.o.o.
> Everything else can be pulled from jenkins (once we get everything into
> shape again).
> 
> This suggestion is just for the "base image". Once the base images are
> in place, jenkins can pick up the base images and generate "layered"
> images which include vdsm (to be used with Engine).
> The layered images can then be kept in the same place where the
> remaining oVirt (Engine, vdsm, ...) packages are kept (for 3.3.3
> in /releases/3.3.3/?).
> 
> Does that make sense?
> 
> - fabian
> 
> _______________________________________________
> Infra mailing list
> Infra at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
> 


From fabiand at redhat.com  Wed Feb 26 09:17:22 2014
From: fabiand at redhat.com (Fabian Deutsch)
Date: Wed, 26 Feb 2014 10:17:22 +0100
Subject: [node-devel] oVirt Node filesystem layout on resources.ovirt.org
In-Reply-To: <280111502.18113260.1393405400580.JavaMail.zimbra@redhat.com>
References: <1393402707.2969.13.camel@fdeutsch-laptop.local>
	<280111502.18113260.1393405400580.JavaMail.zimbra@redhat.com>
Message-ID: <1393406242.2969.19.camel@fdeutsch-laptop.local>

Am Mittwoch, den 26.02.2014, 04:03 -0500 schrieb Kiril Nesenko:
> We are moving to a new layout resources.ovirt.org/pub.
> 
> Please let us know where do you want to put your files.

For that case I'd suggest:
pub
+ ovirt-node-base-3.0
  + iso
  + rpm
  + src
+ ovirt-node-base-stable (symlink to ovirt-node-base-3.0)

- fabian

> - Kiril
> 
> ----- Original Message -----
> > From: "Fabian Deutsch" <fabiand at redhat.com>
> > To: infra at ovirt.org
> > Cc: "node-devel" <node-devel at ovirt.org>
> > Sent: Wednesday, February 26, 2014 10:18:27 AM
> > Subject: oVirt Node filesystem layout on resources.ovirt.org
> > 
> > Hey,
> > 
> > currently it is not easy to find oVirt Node (Base Image) releases on
> > resources.o.o - I'd like to suggest a layout simplification to remove
> > some clutter, improve the findability of isos and ease the maintenance.
> > 
> > Currently the (Node related) layout is:
> > 
> > releases
> > + base
> > + node-base
> >   + 3.0.0
> >     + iso
> >     + rpm
> >   + alpha
> >   + beta
> >   + nightly (symlink?)
> >   + stable (symlink to 3.0.0?)
> > 
> > could we please change the tree to be more like:
> > 
> > releases
> > + node-base
> >   + 3.0
> >     + iso
> >     + rpm
> >   + stable (symlink to 3.0)
> > 
> > Some notes on the removed paths:
> >  base - Was unused
> >  alpha - To reduce overhead I'd use jenkins builds for alpha
> >  beta - To reduce overhead I'd use jenkins builds for beta
> >  beta - To reduce overhead I'd use jenkins builds for nightlies
> > 
> > Some more notes:
> >  3.0 - Just this one dir for all updates
> > 
> > This boils down to Node just offering stable images on resources.o.o.
> > Everything else can be pulled from jenkins (once we get everything into
> > shape again).
> > 
> > This suggestion is just for the "base image". Once the base images are
> > in place, jenkins can pick up the base images and generate "layered"
> > images which include vdsm (to be used with Engine).
> > The layered images can then be kept in the same place where the
> > remaining oVirt (Engine, vdsm, ...) packages are kept (for 3.3.3
> > in /releases/3.3.3/?).
> > 
> > Does that make sense?
> > 
> > - fabian
> > 
> > _______________________________________________
> > Infra mailing list
> > Infra at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> > 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20140226/be91822d/attachment.sig>

From fabiand at redhat.com  Wed Feb 26 14:14:30 2014
From: fabiand at redhat.com (Fabian Deutsch)
Date: Wed, 26 Feb 2014 15:14:30 +0100
Subject: [node-devel] pyflakes and pep8 from pip?
Message-ID: <1393424070.9983.6.camel@fdeutsch-laptop.local>

Hey,

we are using pyflakes and pep8 to check oVirt Node patches.
One problem we have is that there are different pyflakes/pep8 version
son the different slaves.
E.g. this job fails because older pyflakes versions handle _()
diferently:
http://jenkins.ovirt.org/job/ovirt-node-devel-check/1893/console

Could we just use the pyflakes and pylint from pip to have the same
version on all slaves?

$ pip install --upgrade pyflakes pep8

We could have a job which runs the update regularly on all slaves.

Thoughts?

- fabian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20140226/6263ca46/attachment.sig>

From rbarry at redhat.com  Wed Feb 26 17:01:49 2014
From: rbarry at redhat.com (Ryan Barry)
Date: Wed, 26 Feb 2014 12:01:49 -0500
Subject: [node-devel] oVirt Node + VDSM Jenkins builder
Message-ID: <530E1DFD.40504@redhat.com>

Hey,

We on the Node team are planning on creating a Jenkins job to 
automatically add ovirt-node-plugin-vdsm to a base image in order to 
ease the burden of testing, and I'm looking for input from stakeholders 
on how we'd like to configure this.

Adding a single plugin to the image should be much less troublesome than 
the jobs we had which built an ISO on every commit, but I'd like to 
avoid overloading Jenkins as much as possible while still fulfilling the 
intended goal.

Looking at the build history of ovirt-node-plugin-vdsm, I don't think 
that it would be too invasive to trigger this new job on completion of 
ovirt-node-plugin-vdsm, but I'm open.

Thoughts?


From fabiand at redhat.com  Wed Feb 26 17:08:40 2014
From: fabiand at redhat.com (Fabian Deutsch)
Date: Wed, 26 Feb 2014 18:08:40 +0100
Subject: [node-devel] oVirt Node + VDSM Jenkins builder
In-Reply-To: <530E1DFD.40504@redhat.com>
References: <530E1DFD.40504@redhat.com>
Message-ID: <1393434520.22566.2.camel@fdeutsch-laptop.local>

Am Mittwoch, den 26.02.2014, 12:01 -0500 schrieb Ryan Barry:
> Adding a single plugin to the image should be much less troublesome
> than 
> the jobs we had which built an ISO on every commit, but I'd like to 
> avoid overloading Jenkins as much as possible while still fulfilling
> the 
> intended goal.

[Adding Douglas]

Hey,

yeah I think that is really the way to go, as edit-node is also our
recommended way to add plugins to an ISO.

> Looking at the build history of ovirt-node-plugin-vdsm, I don't think 
> that it would be too invasive to trigger this new job on completion
> of 
> ovirt-node-plugin-vdsm, but I'm open.

Yes, I agree on that. We should basically create a new iso once a new
ovirt-node-plugin-vdsm has been build.

Is there already a job which builds ovirt-node-plugin-vdsm?

Oh - And just to confirm - are we still planning to only add the plugin
to the last _stable_ base image?

- fabian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20140226/636a141d/attachment.sig>