From gkotton at redhat.com  Tue May  1 07:18:59 2012
From: gkotton at redhat.com (Gary Kotton)
Date: Tue, 01 May 2012 10:18:59 +0300
Subject: oVirt and Quantum
In-Reply-To: <444331bf-10b9-47a9-aa40-cf84bbfdbe84@zmail02.collab.prod.int.phx2.redhat.com>
References: <444331bf-10b9-47a9-aa40-cf84bbfdbe84@zmail02.collab.prod.int.phx2.redhat.com>
Message-ID: <4F9F8E63.6010704@redhat.com>

On 04/29/2012 02:50 PM, Oved Ourfalli wrote:
>
> ----- Original Message -----
>> From: "Gary Kotton"<gkotton at redhat.com>
>> To: arch at ovirt.org
>> Sent: Sunday, April 29, 2012 1:38:19 PM
>> Subject: oVirt and Quantum
>>
>> Hi,
>> As part of a POC we have integrated Quantum
>> (http://wiki.openstack.org/Quantum) into oVirt
>> (http://www.ovirt.org/).
>> This has been tested with the OVS and Linux Bridge plugins.
>> The details of the integration can be found at -
>> https://fedoraproject.org/wiki/Quantum_and_oVirt.
>> Any comments and suggestions would be greatly appreciated.
> Hey,
> I know it is only a POC, but if you can share the source code via gerrit that would be great.
I have added links to the POC code. An ex colleague of mine once said 
"Quick and dirty, remains dirty". The POC was quick and dirty. :). In 
essence it was actually very easy to do the hooking.



From gkotton at redhat.com  Tue May  1 15:26:00 2012
From: gkotton at redhat.com (Gary Kotton)
Date: Tue, 01 May 2012 11:26:00 -0400 (EDT)
Subject: oVirt/Quantum Integration ideas
In-Reply-To: <f40b0c11-56c6-4424-b405-303ce066672d@zmail18.collab.prod.int.phx2.redhat.com>
Message-ID: <8a612fbb-c186-4a11-9007-f8430e8fba99@zmail18.collab.prod.int.phx2.redhat.com>

Hi,
Any comments or input would be greatly appreciated.
ovirt.org/wiki/Quantum_and_oVirt
Thanks
Gary


From mburns at redhat.com  Wed May  2 11:22:11 2012
From: mburns at redhat.com (Mike Burns)
Date: Wed, 02 May 2012 07:22:11 -0400
Subject: Agenda for Weekly Sync - 2012-05-02
Message-ID: <1335957731.9282.49.camel@beelzebub.mburnsfire.net>

This is the agenda for the 2012-05-02 meeting:
      * Status of Next Release
      * Sub-project reports (engine, vdsm, node)
      * Review decision on Java 7 and Fedora jboss rpms in oVirt Engine
      * Upcoming workshops

I won't be around to run the meeting this week, so someone else will
need to do that.

For Node sub-project status:

* Starting work on F17 related stuff this week
* Should be ready for May 31 Freeze



From oschreib at redhat.com  Wed May  2 14:42:04 2012
From: oschreib at redhat.com (Ofer Schreiber)
Date: Wed, 02 May 2012 10:42:04 -0400 (EDT)
Subject: oVirt Weekly Sync Meeting - 2012-05-02
In-Reply-To: <a7bd9414-85e7-4238-8ab3-8ab023cd706e@zmail14.collab.prod.int.phx2.redhat.com>
Message-ID: <b016e172-fec9-4ecc-a292-147eb91c4f82@zmail14.collab.prod.int.phx2.redhat.com>


Minutes:        http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-02-14.00.html
Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-02-14.00.txt
Log:            http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-02-14.00.log.html

=========================
#ovirt: oVirt Weekly Sync
=========================

Meeting started by oschreib at 14:00:10 UTC. The full logs are available
at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-02-14.00.log.html
.

Meeting summary
---------------
* Agenda and Roll Call  (oschreib, 14:00:14)

* Next Release Status  (oschreib, 14:02:17)
  * Feature Freeze (Branching day) 2012-05-31.  (oschreib, 14:02:56)
  * LINK: http://www.ovirt.org/wiki/Second_Release   (oschreib,
    14:03:04)
  * ACTION: oschreib to review feature-freeze status next week
    (oschreib, 14:06:00)
  * LINK: http://www.ovirt.org/wiki/Release_Notes   (sgordon, 14:07:16)
  * ACTION: sgordon to handle Release Notes page in the wiki  (oschreib,
    14:09:13)

* Sub-project reports (engine, vdsm, node)  (oschreib, 14:10:47)
  * vdsm's network config might be a risk for next release  (oschreib,
    14:16:35)
  * ACTION: danken to review vdsm's network config in next meeting
    (oschreib, 14:17:24)

* Review decision on Java 7 and Fedora jboss rpms in oVirt Engine
  (oschreib, 14:18:58)
  * ACTION: eedri to add Java7 test to jenkins  (oschreib, 14:24:33)

* Upcoming workshops  (oschreib, 14:27:49)
  * LINK: http://lists.ovirt.org/pipermail/arch/2012-April/000546.html
    (lh, 14:27:57)
  * ACTION: lh to send follow up email to board re: lc japan workshop
    (lh, 14:33:50)

Meeting ended at 14:37:39 UTC.


Action Items
------------
* oschreib to review feature-freeze status next week
* sgordon to handle Release Notes page in the wiki
* danken to review vdsm's network config in next meeting
* eedri to add Java7 test to jenkins
* lh to send follow up email to board re: lc japan workshop


Action Items, by person
-----------------------
* danken
  * danken to review vdsm's network config in next meeting
* lh
  * lh to send follow up email to board re: lc japan workshop
* oschreib
  * oschreib to review feature-freeze status next week
* sgordon
  * sgordon to handle Release Notes page in the wiki
* **UNASSIGNED**
  * eedri to add Java7 test to jenkins

People Present (lines said)
---------------------------
* oschreib (49)
* lh (14)
* sgordon (10)
* lpeer (7)
* doron (5)
* danken (5)
* diederich (4)
* eedri_mtg (3)
* ovirtbot (2)
* ovedo (1)
* RobertM (1)
* jb_netapp (1)
* itamar1 (1)
* cctrieloff (1)
* masayag (1)
* doronf_ (1)
* ofrenkel (1)
* dustins (1)

Generated by `MeetBot`_ 0.1.4

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

Regards, 
--
Ofer Schreiber
oVirt Release Manage


From lhawthor at redhat.com  Wed May  2 14:48:06 2012
From: lhawthor at redhat.com (Leslie Hawthorn)
Date: Wed, 02 May 2012 07:48:06 -0700
Subject: Agenda for LinuxCon Japan Workshop
In-Reply-To: <1335805281.9282.8.camel@beelzebub.mburnsfire.net>
References: <4F9EC412.2080603@redhat.com>
	<1335805281.9282.8.camel@beelzebub.mburnsfire.net>
Message-ID: <4FA14926.9040203@redhat.com>

Hello everyone,

Please provide feedback as soon as possible - I'll be monitoring for 
requested agenda changes, speaker volunteers, etc. through close of 
business tomorrow, PDT.

More below.....

On 04/30/2012 10:01 AM, Mike Burns wrote:
> On Mon, 2012-04-30 at 09:55 -0700, Leslie Hawthorn wrote:
>> Hello everyone,
>>
>> As mentioned during last week's IRC meeting, we have an oVirt workshop
>> scheduled for LinuxCon Japan. [0] The Linux Foundation needs our
>> agenda, as well as speaker list and bios,  by this Thursday, 3 May, so
>> they can begin promoting.
>>
>> Here's the proposed agenda for the upcoming workshop:
>>
>> * 09:00 - 11:00 :: Welcome, introduction to oVirt architecture&  demo
>> (includes API/SDK/CLI)
>> * 11:00 - 12:00 :: Engine core
>> * 12:00 - 13:30 :: Lunch
>> * 13:30 - 14:30 :: VDSM
>> * 14:30 - 15:30 :: Node arch and details
> I can't get anyone there to discuss the Node.  If there are people
> attending that are willing to give a presentation, I'd be happy to work
> with you on the content.  But as of right now, there isn't anyone going
> who could give this talk.

Do we have any volunteers to take the Node session?

It would also be great to pull in more instructor volunteers overall. 
Red Hat can provide several instructors but it would be great to have a 
more diverse speaker roster.

Cheers,
LH

> Mike
>
>> * 15:30 - 16:00 :: Break
>> * 16:00 - 17:00 :: Linux virtualization panel (main conference)
>>
>> Open Questions:
>>
>> 1) Are there additional sessions that folks would like to propose for
>> this workshop?
>> 2) Would anyone like to volunteer as an instructor for any of the
>> above proposed sessions?
>>
>> As mentioned, we need to have all of this information in to the Linux
>> Foundation by this Thursday, so please send in your feedback as soon
>> as you are able.
>>
>> [0] - https://events.linuxfoundation.org/events/linuxcon-japan
>>
>> Thank you,
>> LH
>> -- 
>> Leslie Hawthorn
>> Community Action and Impact
>> Open Source and Standards @ Red Hat
>>
>> identi.ca/lh
>> twitter.com/lhawthorn
>> _______________________________________________
>> Board mailing list
>> Board at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/board
>


-- 
Leslie Hawthorn
Community Action and Impact
Open Source and Standards @ Red Hat

identi.ca/lh
twitter.com/lhawthorn



From deepakcs at linux.vnet.ibm.com  Thu May  3 15:24:25 2012
From: deepakcs at linux.vnet.ibm.com (Deepak C Shetty)
Date: Thu, 03 May 2012 20:54:25 +0530
Subject: [vdsm] Storage Device Management in VDSM and oVirt
In-Reply-To: <4F97DE7A.2040808@linux.vnet.ibm.com>
References: <a555ebae-952d-4d7a-82cc-6a9489da8e40@zmail13.collab.prod.int.phx2.redhat.com>
	<4F97DE7A.2040808@linux.vnet.ibm.com>
Message-ID: <4FA2A329.6060400@linux.vnet.ibm.com>

On 04/25/2012 04:52 PM, Deepak C Shetty wrote:
>
> This seems interesting.
>
> I am interested in pursuing this further and helping contribute to the 
> vdsm lsm integration. lsm is still in the early stages, but i feel its 
> the right time to start influencing it so that vdsm integration can be 
> smooth. My interest mainly lies in how external storage array can be 
> integrated into oVirt/VDSM and help oVirt exploit the array offload 
> features as part of the virtualization stack.
>
> I didn't find any oVirt wiki page on this topic, tho' there is a old 
> mailing list thread on vdsm lsm integration, which when read brings up 
> more issues to discuss :)
> How does storage repo engine and possible vdsm services framework ( i 
> learnt about these in my brief chat with Saggie some time back) play a 
> role here ?
>
> Can "Provisioning Storage" itself be like a high level service, with 
> gluster and lsm  exposing storage services, which vdsm can enumerate 
> and send to oVirt GUI, is that the idea ?
> Is there any wiki page on this topic which lists the todos on this 
> front, which I can start looking at ?
>

Hello Ayal,
     Looking for you opinion here.

thanx,
deepak



From abaron at redhat.com  Thu May  3 21:36:02 2012
From: abaron at redhat.com (Ayal Baron)
Date: Thu, 03 May 2012 17:36:02 -0400 (EDT)
Subject: [vdsm] Storage Device Management in VDSM and oVirt
In-Reply-To: <4F97DE7A.2040808@linux.vnet.ibm.com>
Message-ID: <d74a3e17-df27-4f1e-8261-9eb40c1f26bd@zmail13.collab.prod.int.phx2.redhat.com>



----- Original Message -----
> On 04/24/2012 07:37 PM, Ayal Baron wrote:
> >
> > ----- Original Message -----
> >> On 04/24/2012 02:07 AM, Ayal Baron wrote:
> >>> ----- Original Message -----
> >>>> On 04/22/2012 12:28 PM, Ayal Baron wrote:
> >>>>>>> This way we'd have a 2 stage process:
> >>>>>>> 1. setupStorage (generic)
> >>>>>> I was looking up on the VDSM archives and there are talks of
> >>>>>> using
> >>>>>> libstoragemgmt (lsm)
> >>>>> Funny, we started using that acronym for Live Storage Migration
> >>>>> :)
> >>>>>
> >>>>>> under VDSM. I was wondering if the setupStorage would be
> >>>>>> something
> >>>>>> where
> >>>>>> lsm would
> >>>>>> be used to do the work, it seems fit for purpose here.
> >>>>>>
> >>>>>>
> >>>>> I don't think this is the libstoragemgmt mandate.
> >>>>>
> >>>>> libstoragemgmt is:
> >>>>> "A library that will provide a vendor agnostic open source
> >>>>> storage
> >>>>> application programming interface (API) for storage arrays."
> >>>>>
> >>>>> i.e. it is there to abstract storage array specifics from the
> >>>>> user.
> >>>>> It will be used by things like LVM etc, not the other way
> >>>>> around.
> >>>>>
> >>>>> setupStorage would use libstoragemgmt wherever appropriate of
> >>>>> course.
> >>>>>
> >>>>> But as the libstoragemgmt maintainer, Tony (cc'd) can correct
> >>>>> me
> >>>>> if
> >>>>> I'm wrong here.
> >>>>>
> >>>>>
> >>>> I was looking at setupStorage as Provisioning + Setting up.
> >>>> I know one of the basic goals of lsm is provision the storage to
> >>>> the
> >>>> host
> >>>> and preparing the storage for consumption is higher layers work.
> >>>>
> >>>> With that, i think then its becomes a 3 stage process, from
> >>>> oVirt/VDSM
> >>>> pov...
> >>>> 1) Provision Storage (using lsm if applicable, based on whether
> >>>> external
> >>>> storage is connected)
> >>>> 2) Setup Storage (prepare the provisioned LUNs for usage)
> >>>> 3) createSD/createGlusterVolume/...  (plugin specific)
> >>>>
> >>>> Since we are talking about Storage management using VDSM, i was
> >>>> interested in understanding the plans, strategy of how VDSM +
> >>>> lsm
> >>>> will integrate ?
> >>> There are various ways of approaching this.
> >>> 1. Given proper storage you could just provision new LUNs
> >>> whenever
> >>> you need a new virtual disk and utilize storage side thin
> >>> provisioning and snapshots for most of your needs.
> >>> When you have such storage you don't really need steps 2 and 3
> >>> above.  Your storage is your virtual images repository.
> >>> Although quite simple and powerful, very few arrays are capable
> >>> of
> >>> growing to a very large number of objects (luns + snapshots +
> >>> whatever) today, so I don't see this being the most common use
> >>> case any time soon.
> >> This is not clear to me. This only talks about provisioning but
> >> not
> >> consuming.
> >> 2 and 3 above are required from a consumability perspective. The
> >> LUNs
> >> will have
> >> to prepared and used by LVM (pv, vg, lv, metadata) for VDSM to
> >> host a
> >> storage domain.
> > There are several ways of managing the repo in such a scenario,
> > just an example is to provision a LUN where vdsm would manage
> > metadata (listing of images, relations between snapshots, logical
> > sizes of images, etc) and every image is another LUN that we would
> > provision, so there would be no need for LVM in such a scenario.
> >
> 
> Sorry, but not clear to me. If vdsm is configured for file based
> storage
> domain, it would expect the LUN to have a fs, and vdsm would create
> the
> fs storage domain over it. If vdsm is configured for block based
> storage
> domain, it would end up using the LUN as a pv, over which the VG/LV
> would sit (hence the need for lvm) and form the block storage domain,
> unless you are talking of vdsm using raw LUNs which is not supported
> today ?

Today vdsm cannot provision LUNs, only consume there so the full scenario is of course not supported today.
However, we do support exposing LUNs directly to VMs so the only delta is that we do not manage the LUNs as a repository.

> 
> >>
> >>> 2. Provision LUNs (either statically or dynamically using lsm)
> >>> once, preferably thinly provisioned. Then setupStorage (storage
> >>> domain over VG / gLuster / other) and use lsm for creating
> >>> snapshots/clones on the fly
> >>> In my opinion this will be more prevalent to begin with.
> >>>
> >>> With lsm we will (hopefully) have a way of enumerating storage
> >>> side
> >>> capabilities so then when we create a repository (gluster / sd /
> >>> ...) we'd be able to determine on the fly what capabilities it
> >>> has
> >>> and determine if to use these or to use virtualized capabilities
> >>> (e.g. in the virt case when you need to create a snapshot use
> >>> qcowX).
> >>>
> >>> In oVirt, once you've defined a storage domain and it exposes a
> >>> set
> >>> of capabilities, user should be able to override (e.g. even
> >>> though
> >>> storage supports snapshots, I want to use qcow as this storage
> >>> can
> >>> only create 255 snapshots per volume and I need more than that).
> >>>
> >>> I'm assuming that we will not have any way of knowing the limits
> >>> per machine.
> >>>
> >>> Does that make sense?
> >>>
> >> Agree to #2. Thinking deeper....
> >>
> >> 1) Provisioning Storage
> >>
> >> Provisioning storage using lsm would require new VDSM verbs to be
> >> added,
> >> which can create / show the LUNs to the oVirt user and user can
> >> then
> >> select which LUN(s) to use for setupStorage.
> > create LUN doesn't exist today, but show LUNs does.
> >
> > Currently the (simplified) flow is:
> > 1. connect to storage (when relevant)
> > 2. get listing of devices
> > 3. create a storage domain on selected devices
> >
> >> Provisioning LUNs will probably exploit the lsm capabilities and
> >> provide
> >> the options to the user to create the LUNs using the available
> >> array
> >> features.
> >>
> >> With GlusterFS also providing some of the array capabilities
> >> (stripe,
> >> replicate etc), user might want to provision GlusterFS volume
> >> (with
> >> whatever capabilities gluster offers) to host storage upon,
> >> especially
> >> if the storage is coming from not-so-reliable commodity hw
> >> storage.
> >>
> >> I feel this also has to be considered as part of provisioning and
> >> should
> >> come before the setupStorage step.
> >>
> >> IMHO, there should be a "Storage Provisioning" tab in oVirt which
> >> will
> >> allow user to ...
> >>
> >>       1a) Carve LUNs from external Storage array.
> >>
> >>       1b) Provision storage as GlusterFS volume. User can select
> >>       the
> >>       LUNs
> >> carved (from #1a) as bricks for GlusterFS volume, if need be.
> >>
> >>       1c) Use local host free disk space.
> >>
> >> Somewhere here there should be option ( as applicable) for user to
> >> select whether to exploit storage array features or host virt
> >> capabilities for say snapshot, in cases where both are applicable.
> >>
> >> 2) Setup Storage
> >>
> >> Here the user would create VDSM file or block based storage
> >> domain,
> >> based on the storage provisioned from the "Storage Provisioning"
> >> tab.
> >> I believe this is where  VDSM will add its metadata to the
> >> provisioned
> >> storage to make it a storage domain.
> >>
> >> IMHO for image operations like snapshot/clone, VDSM will have to
> >> track&
> >> maintain whether the image is served by local host, external
> >> storage
> >> array or gluster volume and accordingly use the lvm, lsm or
> >> gluster
> >> apis
> >> to get the job done.
> > For sure.  That would be part of the domain metadata.
> >
> >> 3) Not sure if anymore steps needed ?
> > In general I agree with the above.  wrt the scope of setupStorage,
> > it's semantics.  Personally I think we should differentiate
> > between provisioning storage on the target side and provisioning
> > on the initiator side.
> >
> > The flow (from GUI) as I see it is (with lsm and an array that
> > supports dynamic provisioning):
> > 1. provide credentials and login into storage (out of band, using
> > lsm)
> > 2. enumerate capabilities
> > 3. based on 2, define required storage domain characteristics
> > (size, thin provisioning, etc)
> >    - but note that this is generic, so should apply to gluster as
> >    well
> > 4. create a storage domain - would implicitly create 1 or more LUNs
> > and anything else that is needed according to above
> > specifications.  API wise, this is probably 3 calls, 1. provision
> > LUNs, 2. setupStorage and 3.
> > createStorageDomain/createGlusterVolume/...
> >
> > Characteristics might include things like partitions, encryption?,
> > compression?, raid, file systems, etc.
> >
> 
> This seems interesting.
> 
> I am interested in pursuing this further and helping contribute to
> the
> vdsm lsm integration. lsm is still in the early stages, but i feel
> its
> the right time to start influencing it so that vdsm integration can
> be
> smooth. My interest mainly lies in how external storage array can be
> integrated into oVirt/VDSM and help oVirt exploit the array offload
> features as part of the virtualization stack.
> 
> I didn't find any oVirt wiki page on this topic, tho' there is a old
> mailing list thread on vdsm lsm integration, which when read brings
> up
> more issues to discuss :)
> How does storage repo engine and possible vdsm services framework ( i
> learnt about these in my brief chat with Saggie some time back) play
> a
> role here ?

Maybe Saggi could elaborate here.

> 
> Can "Provisioning Storage" itself be like a high level service, with
> gluster and lsm  exposing storage services, which vdsm can enumerate
> and
> send to oVirt GUI, is that the idea ?

I'm not sure "Provisioning Storage" is a clear enough definition, as it could cover a lot of possibly unrelated things, but I'd need to understand more what you mean to really be able to comment properly.

> Is there any wiki page on this topic which lists the todos on this
> front, which I can start looking at ?

Unfortunately there is not as we haven't sat down to plan it in depth, but you're more than welcome to start it.

Generally, the idea is as follows:
Currently vdsm has storage virtualization capabilites, i.e. we've implemented a form of thin-provisioning, we provide snapshots using qcow etc, without relying on the hardware.  Using lsm we could have feature negotiation and whenever we can offload, do it.
e.g. we could know if a storage array supports thin cloning, if it supports thick cloning, if a LUN supports thin provisioning etc.
In the last example (thin provisioning) when we create a VG on top of a thin-p LUN we should create all disk image (LVs) 'preallocated' and avoid vdsm's thin provisioning implementation (as it is not needed).

However, we'd need a mechanism at domain level to 'disable' some of the capabilities, so for example if we know that on a specific array snapshots are limited or provide poor performance (worse than qcow) or whatever, we'd be able to fall back to vdsm's software implementation.

Does this make sense?
> 
> thanx,
> deepak
> 
> 


From deepakcs at linux.vnet.ibm.com  Mon May  7 08:50:06 2012
From: deepakcs at linux.vnet.ibm.com (Deepak C Shetty)
Date: Mon, 07 May 2012 14:20:06 +0530
Subject: [vdsm] Storage Device Management in VDSM and oVirt
In-Reply-To: <d74a3e17-df27-4f1e-8261-9eb40c1f26bd@zmail13.collab.prod.int.phx2.redhat.com>
References: <d74a3e17-df27-4f1e-8261-9eb40c1f26bd@zmail13.collab.prod.int.phx2.redhat.com>
Message-ID: <4FA78CBE.4090300@linux.vnet.ibm.com>


>> This seems interesting.
>>
>> I am interested in pursuing this further and helping contribute to
>> the
>> vdsm lsm integration. lsm is still in the early stages, but i feel
>> its
>> the right time to start influencing it so that vdsm integration can
>> be
>> smooth. My interest mainly lies in how external storage array can be
>> integrated into oVirt/VDSM and help oVirt exploit the array offload
>> features as part of the virtualization stack.
>>
>> I didn't find any oVirt wiki page on this topic, tho' there is a old
>> mailing list thread on vdsm lsm integration, which when read brings
>> up
>> more issues to discuss :)
>> How does storage repo engine and possible vdsm services framework ( i
>> learnt about these in my brief chat with Saggie some time back) play
>> a
>> role here ?
> Maybe Saggi could elaborate here.
>
>> Can "Provisioning Storage" itself be like a high level service, with
>> gluster and lsm  exposing storage services, which vdsm can enumerate
>> and
>> send to oVirt GUI, is that the idea ?
> I'm not sure "Provisioning Storage" is a clear enough definition, as it could cover a lot of possibly unrelated things, but I'd need to understand more what you mean to really be able to comment properly.
>

Well, I was envisioning oVirt as being able to provision and consume 
storage, both, going ahead.
Provisioning thru' vdsm-libstoragemgmt (lsm) integration. oVirt user 
should be able to carve out LUNs,
be able to associate the LUNs visibility to host(s) of a oVirt cluster, 
all via libstoragemgmt interfaces.

With gluster being integrated into vdsm, oVirt user can provision and 
manage gluster volumes soon,
which also falls under "provisioning storage", hence I was wondering if 
there would be a new tab
in oVirt for "provisioning storage", where gluster ( in near future) and 
external array/LUNs  ( via
vdsm -lsm integration) can be provisioned.


>> Is there any wiki page on this topic which lists the todos on this
>> front, which I can start looking at ?
> Unfortunately there is not as we haven't sat down to plan it in depth, but you're more than welcome to start it.
>
> Generally, the idea is as follows:
> Currently vdsm has storage virtualization capabilites, i.e. we've implemented a form of thin-provisioning, we provide snapshots using qcow etc, without relying on the hardware.  Using lsm we could have feature negotiation and whenever we can offload, do it.
> e.g. we could know if a storage array supports thin cloning, if it supports thick cloning, if a LUN supports thin provisioning etc.
> In the last example (thin provisioning) when we create a VG on top of a thin-p LUN we should create all disk image (LVs) 'preallocated' and avoid vdsm's thin provisioning implementation (as it is not needed).
>

I was thinking libstoragemgmt 'query capability' or similar interface 
should help vdsm know the array capabilities.
I agree that if the backing LUN already is thinp'ed, then vdsm should 
not add its own over it. So such usecases & needs
from vdsm perspective need to be thought about and eventually it should 
influence the libstoragemgmt interfaces

> However, we'd need a mechanism at domain level to 'disable' some of the capabilities, so for example if we know that on a specific array snapshots are limited or provide poor performance (worse than qcow) or whatever, we'd be able to fall back to vdsm's software implementation.
>

I was thinking that its for the user to decide, not sure if we can 
auto-detect and automate this. But i feel this falls under the 'advanced 
usecase' category :)
We can always think about this later, rite ?



From mburns at redhat.com  Tue May  8 13:30:19 2012
From: mburns at redhat.com (Mike Burns)
Date: Tue, 08 May 2012 09:30:19 -0400
Subject: Call For Agenda Items 2012-05-09 meeting
Message-ID: <1336483819.27284.8.camel@beelzebub.mburnsfire.net>

Any agenda items for this week?

Current Agenda:

      * Status of Next Release
      * Sub-project reports (engine, vdsm, node)
      * Review decision on Java 7 and Fedora jboss rpms in oVirt Engine
      * Upcoming workshops

Thanks

Mike



From abaron at redhat.com  Wed May  9 12:18:31 2012
From: abaron at redhat.com (Ayal Baron)
Date: Wed, 09 May 2012 08:18:31 -0400 (EDT)
Subject: [vdsm] Storage Device Management in VDSM and oVirt
In-Reply-To: <4FA78CBE.4090300@linux.vnet.ibm.com>
Message-ID: <76e684fb-dcde-4ed3-8698-8e576327f09b@zmail13.collab.prod.int.phx2.redhat.com>



----- Original Message -----
> 
> >> This seems interesting.
> >>
> >> I am interested in pursuing this further and helping contribute to
> >> the
> >> vdsm lsm integration. lsm is still in the early stages, but i feel
> >> its
> >> the right time to start influencing it so that vdsm integration
> >> can
> >> be
> >> smooth. My interest mainly lies in how external storage array can
> >> be
> >> integrated into oVirt/VDSM and help oVirt exploit the array
> >> offload
> >> features as part of the virtualization stack.
> >>
> >> I didn't find any oVirt wiki page on this topic, tho' there is a
> >> old
> >> mailing list thread on vdsm lsm integration, which when read
> >> brings
> >> up
> >> more issues to discuss :)
> >> How does storage repo engine and possible vdsm services framework
> >> ( i
> >> learnt about these in my brief chat with Saggie some time back)
> >> play
> >> a
> >> role here ?
> > Maybe Saggi could elaborate here.
> >
> >> Can "Provisioning Storage" itself be like a high level service,
> >> with
> >> gluster and lsm  exposing storage services, which vdsm can
> >> enumerate
> >> and
> >> send to oVirt GUI, is that the idea ?
> > I'm not sure "Provisioning Storage" is a clear enough definition,
> > as it could cover a lot of possibly unrelated things, but I'd need
> > to understand more what you mean to really be able to comment
> > properly.
> >
> 
> Well, I was envisioning oVirt as being able to provision and consume
> storage, both, going ahead.
> Provisioning thru' vdsm-libstoragemgmt (lsm) integration. oVirt user
> should be able to carve out LUNs,
> be able to associate the LUNs visibility to host(s) of a oVirt
> cluster,
> all via libstoragemgmt interfaces.
> 
> With gluster being integrated into vdsm, oVirt user can provision and
> manage gluster volumes soon,
> which also falls under "provisioning storage", hence I was wondering
> if
> there would be a new tab
> in oVirt for "provisioning storage", where gluster ( in near future)
> and
> external array/LUNs  ( via
> vdsm -lsm integration) can be provisioned.


Ok, now I that I understand a little more, then in general I agree.
First upstream oVirt already has the ability to provision gLuster (albeit still in a limited way) and definitely we will need more provisioning capabilities including for example setting up LIO on a host and exposing LUNs that would be available to other hosts/VMs (for one, live storage migration without shared disks would need this).
Specifically wrt "Provisioning Storage" tab, that's more of a design question as there are going to be many services we will need to provision not all specifically around storage and I'm not sure that we'd want a new tab for every type.


> 
> 
> >> Is there any wiki page on this topic which lists the todos on this
> >> front, which I can start looking at ?
> > Unfortunately there is not as we haven't sat down to plan it in
> > depth, but you're more than welcome to start it.
> >
> > Generally, the idea is as follows:
> > Currently vdsm has storage virtualization capabilites, i.e. we've
> > implemented a form of thin-provisioning, we provide snapshots
> > using qcow etc, without relying on the hardware.  Using lsm we
> > could have feature negotiation and whenever we can offload, do it.
> > e.g. we could know if a storage array supports thin cloning, if it
> > supports thick cloning, if a LUN supports thin provisioning etc.
> > In the last example (thin provisioning) when we create a VG on top
> > of a thin-p LUN we should create all disk image (LVs)
> > 'preallocated' and avoid vdsm's thin provisioning implementation
> > (as it is not needed).
> >
> 
> I was thinking libstoragemgmt 'query capability' or similar interface
> should help vdsm know the array capabilities.

that is correct.

> I agree that if the backing LUN already is thinp'ed, then vdsm should
> not add its own over it. So such usecases & needs
> from vdsm perspective need to be thought about and eventually it
> should
> influence the libstoragemgmt interfaces

I don't see how it would influence the lsm interfaces.

> 
> > However, we'd need a mechanism at domain level to 'disable' some of
> > the capabilities, so for example if we know that on a specific
> > array snapshots are limited or provide poor performance (worse
> > than qcow) or whatever, we'd be able to fall back to vdsm's
> > software implementation.
> >
> 
> I was thinking that its for the user to decide, not sure if we can
> auto-detect and automate this. But i feel this falls under the
> 'advanced
> usecase' category :)
> We can always think about this later, rite ?

Correct, the mechanism is in order to allow the user to decide.

> 
> 


From lhawthor at redhat.com  Wed May  9 14:47:26 2012
From: lhawthor at redhat.com (Leslie Hawthorn)
Date: Wed, 09 May 2012 07:47:26 -0700
Subject: oVirt Workshop at LinuxCon Japan 2012
Message-ID: <4FAA837E.5050305@redhat.com>

Hello everyone,

As part of our efforts to raise awareness of and educate more developers 
about the oVirt project, we will be holding an oVirt workshop at 
LinuxCon Japan, taking place on June 8, 2012. You can find full details 
of the workshop agenda on the LinuxCon Japan site. [0]

Registration for the workshop is now open and is free of charge for the 
first 50 participants.  We will also look at adding additional 
participant slots to the workshop based on demand.

Attendees who register for LinuxCon Japan via the workshop registration 
link [1] will also be  eligible for a discount on their LinuxCon Japan 
registration.

Please spread the word to folks you think would find the workshop 
useful. If they have already registered for LinuxCon Japan, they can 
simply edit their existing registration to include the workshop.

[0] - 
https://events.linuxfoundation.org/events/linuxcon-japan/ovirt-gluster-workshops
[1] - http://www.regonline.com/Register/Checkin.aspx?EventID=1099949

Cheers,
LH

-- 
Leslie Hawthorn
Community Action and Impact
Open Source and Standards @ Red Hat

identi.ca/lh
twitter.com/lhawthorn



From mburns at redhat.com  Wed May  9 15:53:54 2012
From: mburns at redhat.com (Mike Burns)
Date: Wed, 09 May 2012 11:53:54 -0400
Subject: oVirt Weekly Meeting Minutes -- 2012-05-09
Message-ID: <1336578834.3397.13.camel@beelzebub.mburnsfire.net>

Minutes:        http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-09-14.00.html
Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-09-14.00.txt
Log:            http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-09-14.00.log.html

=========================
#ovirt: oVirt Weekly Sync
=========================


Meeting started by mburns at 14:00:55 UTC. The full logs are available
at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-09-14.00.log.html
.



Meeting summary
---------------
* agenda and roll call  (mburns, 14:01:10)
  * LINK: http://www.ovirt.org/wiki/Meetings#Weekly_project_sync_meeting
    (mburns, 14:01:31)

* Release status  (mburns, 14:04:03)
  * not much new with release status  (mburns, 14:07:09)
  * concerns with java 7 and jboss  (mburns, 14:07:22)
  * iso-uploader, log-collector, image-uploader are separate components
    and going into Fedora  (mburns, 14:08:12)
  * Devel Freeze and branching:  May 31  (mburns, 14:08:44)
  * Release date:  June 27  (mburns, 14:08:58)
  * ACTION: oschreib to follow up with maintainers to get builds done
    for alpha next week (hopefully)  (mburns, 14:11:01)
  * engine likely to have alpha on f16  (mburns, 14:11:14)
  * vdsm requirements will put node and other hosts on f17  (mburns,
    14:11:29)

* sub-project status -- Node  (mburns, 14:16:24)
  * we've started looking at f17 builds, but not a lot of progress there
    yet  (mburns, 14:17:06)
  * plan to get on this in the next week  (mburns, 14:17:15)

* sub-project status -- Engine  (mburns, 14:17:33)
  * patch sent to work with jdk 7, but that exposed issue with GWT
    (mburns, 14:20:01)

* sub-project status -- VDSM  (mburns, 14:20:12)
  * no vdsm representative here to give update  (mburns, 14:20:31)

* Java7 and distro versions of jboss  (mburns, 14:21:00)
  * we're deferring decision on whether java 7 and jboss from fedora are
    blockers, will keep on agenda for next week  (mburns, 14:23:58)

* upcoming workshops  (mburns, 14:24:20)
  * next workshop is LinuxCon Japan -- June 8  (mburns, 14:27:12)
  * LINK:
    https://events.linuxfoundation.org/events/linuxcon-japan/ovirt-gluster-workshops
    (mburns, 14:27:20)
  * LINK: http://www.regonline.com/Register/Checkin.aspx?EventID=1099949
    (mburns, 14:27:26)
  * please invite people who would benefit  (mburns, 14:27:37)
  * lh will work out details during visit to netapp next week  (mburns,
    14:30:37)
  * confirmed for linuxcon NA (August) and Europe (November),
    agendas/instructors/dates not finalized yet  (mburns, 14:31:10)

* maven/jenkins status  (mburns, 14:31:59)
  * clean mvn install using 3.0.x is failing  (mburns, 14:40:36)
  * ACTION: eedri to file bug to investigate issue  (mburns, 14:40:44)
  * builds failing due to too many open files  (mburns, 14:41:02)
  * try increasing limit and see if that helps, if not, bring up again
    in this meeting  (mburns, 14:41:36)
  * email alerts updated to include more info  (mburns, 14:42:07)
  * feedback on level of detail would be appreciated  (mburns, 14:42:22)
  * this affects only engine builds, node builds use a different email
    method  (mburns, 14:42:39)

* Other Topics  (mburns, 14:45:01)
  * discussion about forums vs. mailing lists on infra at ovirt.org --
    feedback welcome  (mburns, 14:47:10)

Meeting ended at 14:49:34 UTC.




Action Items
------------
* oschreib to follow up with maintainers to get builds done for alpha
  next week (hopefully)
* eedri to file bug to investigate issue




Action Items, by person
-----------------------
* eedri
  * eedri to file bug to investigate issue
* oschreib
  * oschreib to follow up with maintainers to get builds done for alpha
    next week (hopefully)
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* mburns (111)
* eedri (24)
* oschreib (22)
* lh (21)
* kroberts (8)
* ovirtbot (6)
* lpeer_ (5)
* ykaul (5)
* akio (3)
* sgordon (2)
* RobertM (1)
* jb_netapp (1)
* aglitke (1)
* doron (1)
* ofrenkel (1)
* dustins (1)




Generated by `MeetBot`_ 0.1.4

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



From lhawthor at redhat.com  Wed May  9 19:28:48 2012
From: lhawthor at redhat.com (Leslie Hawthorn)
Date: Wed, 09 May 2012 12:28:48 -0700
Subject: Upcoming oVirt Workshop Information
Message-ID: <4FAAC570.80902@redhat.com>

Hello everyone,

To give everyone the lay of the land on upcoming oVirt workshops, I've 
created this page on the oVirt wiki:

http://www.ovirt.org/wiki/OVirt_Global_Workshops

Jason Brooks is working on updating the content the oVirt website News 
and Events page to be in sync with the data on the wiki.

Cheers,
LH

-- 
Leslie Hawthorn
Community Action and Impact
Open Source and Standards @ Red Hat

identi.ca/lh
twitter.com/lhawthorn



From oschreib at redhat.com  Mon May 14 14:20:15 2012
From: oschreib at redhat.com (Ofer Schreiber)
Date: Mon, 14 May 2012 10:20:15 -0400 (EDT)
Subject: oVirt 3.1: Alpha packages needed
In-Reply-To: <b7f241f5-1bf1-4f66-8bab-bed0912b46ad@zmail14.collab.prod.int.phx2.redhat.com>
Message-ID: <22271640-94f2-46ec-b592-9562eb545b43@zmail14.collab.prod.int.phx2.redhat.com>

Dear package maintainers,

As we're getting closer to the feature freeze for next release, I'd like to create an alpha repository for oVirt 3.1
Please provide me a Fedora 17 based builds of your packages (preferably, with "alpha" in the release field), and I'll upload them into ovirt.org.

Thanks,
---
Ofer Schreiber
oVirt Release Manager


From mburns at redhat.com  Mon May 14 14:59:37 2012
From: mburns at redhat.com (Mike Burns)
Date: Mon, 14 May 2012 10:59:37 -0400
Subject: Call For Agenda Items -- 2012-05-16 Weekly Sync Meeting
Message-ID: <1337007577.4886.14.camel@mburns-laptop.usersys.redhat.com>

Any additional agenda items for next week?  

Current topics:
      * Status of Next Release
      * Sub-project reports (engine, vdsm, node)
      * Review decision on Java 7 and Fedora jboss rpms in oVirt Engine
      * Upcoming workshops



From gkotton at redhat.com  Mon May 14 15:14:49 2012
From: gkotton at redhat.com (Gary Kotton)
Date: Mon, 14 May 2012 18:14:49 +0300
Subject: Call For Agenda Items -- 2012-05-16 Weekly Sync Meeting
In-Reply-To: <1337007577.4886.14.camel@mburns-laptop.usersys.redhat.com>
References: <1337007577.4886.14.camel@mburns-laptop.usersys.redhat.com>
Message-ID: <4FB12169.1000306@redhat.com>

Hi,
Can we please discuss the integration ideas of Quantum into oVirt 
(http://www.ovirt.org/wiki/Quantum_and_oVirt)
Thanks
Gary

On 05/14/2012 05:59 PM, Mike Burns wrote:
> Any additional agenda items for next week?
>
> Current topics:
>        * Status of Next Release
>        * Sub-project reports (engine, vdsm, node)
>        * Review decision on Java 7 and Fedora jboss rpms in oVirt Engine
>        * Upcoming workshops
>
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch



From mburns at redhat.com  Wed May 16 14:52:29 2012
From: mburns at redhat.com (Mike Burns)
Date: Wed, 16 May 2012 10:52:29 -0400
Subject: oVirt Weekly Meeting Minutes -- 2012-05-16
Message-ID: <1337179949.11558.20.camel@mburns-laptop.usersys.redhat.com>

Minutes:        http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-16-14.00.html
Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-16-14.00.txt
Log:            http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-16-14.00.log.html

=========================
#ovirt: oVirt Weekly Sync
=========================


Meeting started by mburns at 14:00:28 UTC. The full logs are available
at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-16-14.00.log.html
.



Meeting summary
---------------
* agenda and roll call  (mburns, 14:00:38)

* Next release status  (mburns, 14:03:19)
  * GA target:  2012-06-27  (mburns, 14:03:35)
  * beta target: 2012-05-31  (mburns, 14:03:45)
  * alpha target:  ASAP  (mburns, 14:03:58)
  * new tracker BZ for 3.1  (oschreib, 14:04:49)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=822145
    (oschreib, 14:04:53)
  * BZ#821867 is a blocker for VDSM  (oschreib, 14:06:06)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=821867
    (oschreib, 14:06:10)
  * ACTION: oschreib to open bzs to track Java7 and Fedora17 issues
    (mburns, 14:07:58)
  * ACTION: oschreib to add ovirt.org/releases/beta  (oschreib,
    14:18:34)
  * AGREED: add new "beta" section to releases on ovirt.org  (mburns,
    14:18:47)

* sub-project status -- VDSM  (mburns, 14:19:01)
  * ACTION: ofrenkel open bug on Engine to handle real vdsm
    versions/release  (danken, 14:19:11)
  * 2 major blockers identified already  (mburns, 14:19:28)
  * bz821867 and one still to be filed  (mburns, 14:20:08)
  * basic networking is working in vdsm  (mburns, 14:22:23)

* sub-project status -- Engine  (mburns, 14:23:05)
  * engine rpms ready for alpha (on F16)  (mburns, 14:25:13)
  * no other feedback  (mburns, 14:25:28)

* sub-project status -- Node  (mburns, 14:25:34)
  * F17 based nodes are running and appear to work correctly  (mburns,
    14:25:48)
  * numerous patches still pending, working on getting those merged
    prior to alpha build  (mburns, 14:26:14)
  * only blocker known at the moment is lack of a vdsm build  (mburns,
    14:26:30)

* Java 7 and Fedora 17  (mburns, 14:27:03)
  * patches to move to F17 and java 7 are posted  (mburns, 14:27:59)
  * patches still in review  (mburns, 14:32:16)
  * LINK: http://gerrit.ovirt.org/#change,4315 - > Java7  (oschreib,
    14:32:18)
  * LINK: http://gerrit.ovirt.org/#change,4416 -> F17 support
    (oschreib, 14:32:37)
  * LINK: http://gerrit.ovirt.org/#change,4315   (mburns, 14:32:46)
  * LINK: http://gerrit.ovirt.org/#change,4316   (mburns, 14:32:52)

* Upcoming Workshops  (mburns, 14:37:52)
  * LINK: http://www.ovirt.org/wiki/OVirt_Global_Workshops   (lh,
    14:38:33)
  * not much more to report  (mburns, 14:38:41)
  * LINK: http://www.ovirt.org/wiki/OVirt_Global_Workshops   (mburns,
    14:38:47)
  * will get into planning for LinuxCon North America after LinuxCon
    Japan  (mburns, 14:40:12)
  * workshop planned at NetApp for January.  Can't book firm dates until
    we're within 3 months  (mburns, 14:42:12)
  * targeting late January (22-24)  (mburns, 14:42:24)

* oVirt / Quantum integration  (mburns, 14:43:22)
  * LINK: http://www.ovirt.org/wiki/Quantum_and_oVirt   (mburns,
    14:45:43)
  * requester is not available, deferring the topic  (mburns, 14:46:57)

* Other Topics  (mburns, 14:47:02)
  * No other topics to discuss  (mburns, 14:48:45)

Meeting ended at 14:48:53 UTC.




Action Items
------------
* oschreib to open bzs to track Java7 and Fedora17 issues
* oschreib to add ovirt.org/releases/beta
* ofrenkel open bug on Engine to handle real vdsm versions/release




Action Items, by person
-----------------------
* ofrenkel
  * ofrenkel open bug on Engine to handle real vdsm versions/release
* oschreib
  * oschreib to open bzs to track Java7 and Fedora17 issues
  * oschreib to add ovirt.org/releases/beta
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* mburns (96)
* oschreib (47)
* danken (25)
* lh (11)
* ofrenkel (9)
* ykaul (7)
* ovirtbot (3)
* yzaslavs (2)
* jb_netapp (1)
* lpeer_ (1)
* lpeer (1)
* cctrieloff (1)
* doronf (1)
* mestery_ (1)
* dustins (1)
* quaid (0)




Generated by `MeetBot`_ 0.1.4

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



From kwade at redhat.com  Mon May 21 18:19:40 2012
From: kwade at redhat.com (Karsten 'quaid' Wade)
Date: Mon, 21 May 2012 11:19:40 -0700
Subject: Outage: www.ovirt. org planned server restart Tue 22 May 0100 UTC
Message-ID: <4FBA873C.5070109@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

There will be a outage starting at 2100 EDT 21 May/0100 UTC 22 May
lasting up to three hours.

To convert UTC to your local time, run:
  date -d '2012-04-13 22:00 UTC'

Reason for outage:

The hosting provider for ovirt.org has a server reboot scheduled for
tonight. They intend to do a soft landing, upgrade software, and
restart the VMs.

Once the outage is completed, I will make sure that all services have
restarted properly.

Affected services:
 www.ovirt.org (WordPress and MediaWiki)
 lists.ovirt.org (Mailman)
 ovirt.org/releases

Unaffected services:
 gerrit.ovirt.org
 jenkins.ovirt.org

Please join #ovirt on irc.oftc.net or respond to this email to track
the status of this outage.

- -- 
Karsten 'quaid' Wade, Sr. Analyst - Community Growth
Red Hat Open Source and Standards (OSAS)
http://TheOpenSourceWay.org
@quaid (identi.ca/twitter/IRC) | gpg: AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFPuoc82ZIOBq0ODEERAvXDAJ44qH+hwpyGNKSl7dnHXGCp4AShlwCgodLj
/s3BsXTKdn/7HDn0surFRu0=
=UjaR
-----END PGP SIGNATURE-----


From kwade at redhat.com  Tue May 22 05:45:35 2012
From: kwade at redhat.com (Karsten 'quaid' Wade)
Date: Mon, 21 May 2012 22:45:35 -0700
Subject: Outage: www.ovirt. org planned server restart Tue 22 May 0100 UTC
In-Reply-To: <4FBA873C.5070109@redhat.com>
References: <4FBA873C.5070109@redhat.com>
Message-ID: <4FBB27FF.7090603@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This outage is complete and all services appear to be working correctly.

I did have to restart ovirtbot, which is expected, using this procedure:

http://ovirt.org/wiki/Running_ovirtbot

If you have any questions about this outage, please email
infra at ovirt.org to discuss.

- - Karsten

On 05/21/2012 11:19 AM, Karsten 'quaid' Wade wrote:
> There will be a outage starting at 2100 EDT 21 May/0100 UTC 22 May 
> lasting up to three hours.
> 
> To convert UTC to your local time, run: date -d '2012-04-13 22:00 
> UTC'
> 
> Reason for outage:
> 
> The hosting provider for ovirt.org has a server reboot scheduled 
> for tonight. They intend to do a soft landing, upgrade software, 
> and restart the VMs.
> 
> Once the outage is completed, I will make sure that all services 
> have restarted properly.
> 
> Affected services: www.ovirt.org (WordPress and MediaWiki) 
> lists.ovirt.org (Mailman) ovirt.org/releases
> 
> Unaffected services: gerrit.ovirt.org jenkins.ovirt.org
> 
> Please join #ovirt on irc.oftc.net or respond to this email to 
> track the status of this outage.
> 
> _______________________________________________ Infra mailing list 
> Infra at ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

- -- 
Karsten 'quaid' Wade, Sr. Analyst - Community Growth
Red Hat Open Source and Standards (OSAS)
http://TheOpenSourceWay.org
@quaid (identi.ca/twitter/IRC) | gpg: AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFPuyf/2ZIOBq0ODEERAoi8AKCfBYA2ucO3sXmJ1s1bfRgfXY2CLgCeLT68
u2T4ltASOXNc6Ac1KEkomYg=
=zPus
-----END PGP SIGNATURE-----


From mburns at redhat.com  Tue May 22 13:39:23 2012
From: mburns at redhat.com (Mike Burns)
Date: Tue, 22 May 2012 09:39:23 -0400
Subject: Call for Agenda Items -- Weekly oVirt Sync Meeting 2012-05-23
Message-ID: <1337693963.23619.38.camel@beelzebub.mburnsfire.net>

Any additional topics for this meeting?

Current Agenda:

* Status of Next Release
* Sub-project reports (engine, vdsm, node)
* Review decision on Java 7 and Fedora jboss rpms in oVirt Engine
* Upcoming workshops
* oVirt / Quantum Integration (gkotton)



From dfediuck at redhat.com  Wed May 23 09:59:53 2012
From: dfediuck at redhat.com (Doron Fediuck)
Date: Wed, 23 May 2012 12:59:53 +0300
Subject: Maven 3 here we come!
Message-ID: <4FBCB519.60606@redhat.com>

Hi all,
As discussed last month[1], we had to deal with some issues which turned out to be a Maven bug.
Thanks to Juan and Asaf's work, our current sources now build properly using Maven 3. 
So you're all invited to migrate into Maven 3. Other than upgrading your local maven package
no other action is needed.

For now, Maven 2 will also work for you, but I expect in the future we'd like to make use
of some advanced features, so migration to 3 is recommended.

Talking about advanced features, an interesting challenge is feedback on parallel builds [2].
So whoever wants to try it out and report if it improves run time without breaking anything,
will be appreciated. 

Happy migration!

[1]http://lists.ovirt.org/pipermail/arch/2012-April/000490.html
[2] https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html
-- 

/d

"Email returned to sender -- insufficient voltage."


From eedri at redhat.com  Wed May 23 10:26:31 2012
From: eedri at redhat.com (Eyal Edri)
Date: Wed, 23 May 2012 06:26:31 -0400 (EDT)
Subject: [Engine-devel] Maven 3 here we come!
In-Reply-To: <4FBCB519.60606@redhat.com>
Message-ID: <92d79202-3390-4994-ad8f-6bd99030a5d0@zmail17.collab.prod.int.phx2.redhat.com>



----- Original Message -----
> From: "Doron Fediuck" <dfediuck at redhat.com>
> To: engine-devel at ovirt.org
> Cc: "<arch at ovirt.org>" <arch at ovirt.org>
> Sent: Wednesday, May 23, 2012 12:59:53 PM
> Subject: [Engine-devel] Maven 3 here we come!
> 
> Hi all,
> As discussed last month[1], we had to deal with some issues which
> turned out to be a Maven bug.
> Thanks to Juan and Asaf's work, our current sources now build
> properly using Maven 3.
> So you're all invited to migrate into Maven 3. Other than upgrading
> your local maven package
> no other action is needed.
> 
> For now, Maven 2 will also work for you, but I expect in the future
> we'd like to make use
> of some advanced features, so migration to 3 is recommended.
> 
> Talking about advanced features, an interesting challenge is feedback
> on parallel builds [2].
> So whoever wants to try it out and report if it improves run time
> without breaking anything,
> will be appreciated.
> 
> Happy migration!
> 
> [1]http://lists.ovirt.org/pipermail/arch/2012-April/000490.html
> [2] https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html
> --

+1 on the move and testing out new features! 

> 
> /d
> 
> "Email returned to sender -- insufficient voltage."
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
> 


From gkotton at redhat.com  Wed May 23 10:42:14 2012
From: gkotton at redhat.com (Gary Kotton)
Date: Wed, 23 May 2012 13:42:14 +0300
Subject: Call for Agenda Items -- Weekly oVirt Sync Meeting 2012-05-23
In-Reply-To: <1337693963.23619.38.camel@beelzebub.mburnsfire.net>
References: <1337693963.23619.38.camel@beelzebub.mburnsfire.net>
Message-ID: <4FBCBF06.7090901@redhat.com>

Hi Mike,
There are a quite a few people who are unable to make the meeting today 
to speak about the Quantum integration. I was asked by Livnat if we 
could move this to next week when they will be able to attend. Livnat 
said that she will schedule a special oVirt Engine meeting next week to 
go over this.
Sorry for the inconvenience.
Thanks
Gary


On 05/22/2012 04:39 PM, Mike Burns wrote:
> oVirt / Quantum Integration



From mburns at redhat.com  Wed May 23 11:26:45 2012
From: mburns at redhat.com (Mike Burns)
Date: Wed, 23 May 2012 07:26:45 -0400
Subject: [Users] Call for Agenda Items -- Weekly oVirt Sync Meeting
	2012-05-23
In-Reply-To: <4FBCBF06.7090901@redhat.com>
References: <1337693963.23619.38.camel@beelzebub.mburnsfire.net>
	<4FBCBF06.7090901@redhat.com>
Message-ID: <1337772405.23619.41.camel@beelzebub.mburnsfire.net>

On Wed, 2012-05-23 at 13:42 +0300, Gary Kotton wrote:
> Hi Mike,
> There are a quite a few people who are unable to make the meeting today 
> to speak about the Quantum integration. I was asked by Livnat if we 
> could move this to next week when they will be able to attend. Livnat 
> said that she will schedule a special oVirt Engine meeting next week to 
> go over this.
> Sorry for the inconvenience.
> Thanks
> Gary
> 

Ok, dropped from agenda for today.

Mike

> 
> On 05/22/2012 04:39 PM, Mike Burns wrote:
> > oVirt / Quantum Integration
> 
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users




From oschreib at redhat.com  Wed May 23 12:09:14 2012
From: oschreib at redhat.com (Ofer Schreiber)
Date: Wed, 23 May 2012 08:09:14 -0400 (EDT)
Subject: Call for Agenda Items -- Weekly oVirt Sync Meeting 2012-05-23
In-Reply-To: <1337693963.23619.38.camel@beelzebub.mburnsfire.net>
Message-ID: <02da10ba-9555-4b1a-9e37-6438c7539657@zmail14.collab.prod.int.phx2.redhat.com>



----- Original Message -----
> Any additional topics for this meeting?
> 
> Current Agenda:
> 
> * Status of Next Release
> * Sub-project reports (engine, vdsm, node)
> * Review decision on Java 7 and Fedora jboss rpms in oVirt Engine

I'd like to raise the option to delay the Feature Freeze to 07.06. (one week slip)
We currently have three blockers (All blocks https://bugzilla.redhat.com/show_bug.cgi?id=822145 - oVirt 3.1):
1. https://bugzilla.redhat.com/show_bug.cgi?id=822158 - VDSM breaks libvirt configuration 
2. https://bugzilla.redhat.com/show_bug.cgi?id=822158 - engine-core - VDSM version is not supported. 
   - Currently on engine-core, still in NEW state
3. https://bugzilla.redhat.com/show_bug.cgi?id=824397 - Support official JBoss rpms 
   - This is NOT a must (as we can use the old rpms)
   - Patch is in review

Updates from VDSM and engine are needed.

> * Upcoming workshops
> * oVirt / Quantum Integration (gkotton)
> 

> _______________________________________________
> Board mailing list
> Board at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/board
> 


From oschreib at redhat.com  Wed May 23 14:54:04 2012
From: oschreib at redhat.com (Ofer Schreiber)
Date: Wed, 23 May 2012 10:54:04 -0400 (EDT)
Subject: oVirt 3.1 Feature Freeze delay
In-Reply-To: <9ecf4549-2ee2-4ec4-a822-84a946d00277@zmail14.collab.prod.int.phx2.redhat.com>
Message-ID: <54fcfd33-5092-47fc-b8de-c3ca8acdfb5f@zmail14.collab.prod.int.phx2.redhat.com>

oVirt 3.1 Feature Freeze date has been delayed by one week, to the 7th of June.
There's no impact on the GA date ATM, we will review it during the next weekly meeting.

We're delaying the FF due to 4 major blockers we currently have (across all the stack - VDSM, Engine and Node), all of them could be seen in https://bugzilla.redhat.com/show_bug.cgi?id=822158 (3.1 Tracker)

Regards,
Ofer Schreiber
oVirt Release Manager


From oschreib at redhat.com  Wed May 23 14:56:57 2012
From: oschreib at redhat.com (Ofer Schreiber)
Date: Wed, 23 May 2012 10:56:57 -0400 (EDT)
Subject: oVirt 3.1 Feature Freeze delay
In-Reply-To: <54fcfd33-5092-47fc-b8de-c3ca8acdfb5f@zmail14.collab.prod.int.phx2.redhat.com>
Message-ID: <c5ca0a53-bd17-45dc-8787-1225f1e750e0@zmail14.collab.prod.int.phx2.redhat.com>

The correct Bugzilla is:
https://bugzilla.redhat.com/show_bug.cgi?id=822145

Sorry for the confusion.
Ofer.

----- Original Message -----
> oVirt 3.1 Feature Freeze date has been delayed by one week, to the
> 7th of June.
> There's no impact on the GA date ATM, we will review it during the
> next weekly meeting.
> 
> We're delaying the FF due to 4 major blockers we currently have
> (across all the stack - VDSM, Engine and Node), all of them could be
> seen in https://bugzilla.redhat.com/show_bug.cgi?id=822158 (3.1
> Tracker)
> 
> Regards,
> Ofer Schreiber
> oVirt Release Manager
> _______________________________________________
> Board mailing list
> Board at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/board
> 


From mburns at redhat.com  Wed May 23 15:07:06 2012
From: mburns at redhat.com (Mike Burns)
Date: Wed, 23 May 2012 11:07:06 -0400
Subject: oVirt Weekly Sync Meeting Minutes -- 2012-05-23
Message-ID: <1337785626.3177.1.camel@mburns-laptop.usersys.redhat.com>

Minutes:        http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-23-14.00.html
Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-23-14.00.txt
Log:            http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-23-14.00.log.html

=========================
#ovirt: oVirt Weekly Sync
=========================


Meeting started by mburns at 14:00:23 UTC. The full logs are available
at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-23-14.00.log.html
.



Meeting summary
---------------
* agenda and roll call  (mburns, 14:00:41)

* Status of next release  (mburns, 14:05:17)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=822145   (mburns,
    14:05:29)
  * AGREED: freeze date and beta release delayed by 1 week to 2012-06-07
    (mburns, 14:12:33)
  * post freeze, release notes flag needs to be used where required
    (mburns, 14:14:21)
  * https://bugzilla.redhat.com/show_bug.cgi?id=821867 is a VDSM blocker
    for 3.1  (oschreib, 14:17:27)
  * ACTION: dougsland to fix upstream vdsm right now, and open a bug on
    libvirt augeas  (oschreib, 14:21:44)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=822158   (mburns,
    14:23:39)
  * assignee not available, update to come tomorrow  (mburns, 14:24:59)
  * ACTION: oschreib to make sure BZ#822158 is handled quickly
    (oschreib, 14:25:29)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=824397   (mburns,
    14:28:55)
  * 824397 expected to be merged prior next week's meeting  (mburns,
    14:29:45)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=824420   (mburns,
    14:30:15)
  * tracker for node based on F17  (mburns, 14:30:28)
  * blocked by util-linux bug currently  (mburns, 14:30:40)
  * new build expected from util-linux maintainer in next couple days
    (mburns, 14:30:55)

* sub-project status -- engine  (mburns, 14:32:49)
  * nothing to report outside of blockers discussed above  (mburns,
    14:34:00)

* sub-project status -- vdsm  (mburns, 14:34:09)
  * nothing outside of blockers above  (mburns, 14:35:36)

* sub-project status -- node  (mburns, 14:35:43)
  * working on f17 migration, but blocked by util-linux bug  (mburns,
    14:35:58)
  * should be ready for freeze deadline  (mburns, 14:36:23)

* Review decision on Java 7 and Fedora jboss rpms in oVirt Engine
  (mburns, 14:36:43)
  * Java7 basically working  (mburns, 14:37:19)
  * LINK: http://gerrit.ovirt.org/#change,4416   (oschreib, 14:39:35)
  * engine will make ack/nack statement next week  (mburns, 14:39:49)
  * fedora jboss rpms patch is in review, short tests passed  (mburns,
    14:40:04)
  * engine ack on fedora jboss rpms and java7 needed next week  (mburns,
    14:44:47)

* Upcoming Workshops  (mburns, 14:45:11)
  * NetApp workshop set for Jan 22-24 2013  (mburns, 14:47:16)
  * already at half capacity for Workshop at LinuxCon Japan  (mburns,
    14:47:37)
  * please continue to promote it  (mburns, 14:48:19)
  * proposal:  board meeting to be held at all major workshops  (mburns,
    14:48:43)
  * LINK: http://www.ovirt.org/wiki/OVirt_Global_Workshops   (mburns,
    14:49:30)

* Open Discussion  (mburns, 14:50:12)
  * oVirt/Quantum integration discussion will be held separately
    (mburns, 14:50:43)

Meeting ended at 14:52:47 UTC.




Action Items
------------
* dougsland to fix upstream vdsm right now, and open a bug on libvirt
  augeas
* oschreib to make sure BZ#822158 is handled quickly




Action Items, by person
-----------------------
* dougsland
  * dougsland to fix upstream vdsm right now, and open a bug on libvirt
    augeas
* oschreib
  * oschreib to make sure BZ#822158 is handled quickly
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* mburns (98)
* oschreib (55)
* doronf (12)
* lh (11)
* sgordon (8)
* dougsland (8)
* ovirtbot (6)
* ofrenkel (4)
* cestila (2)
* RobertMdroid (2)
* ydary (2)
* rickyh (1)
* yzaslavs (1)
* cctrieloff (1)
* mestery_ (1)
* dustins (1)




Generated by `MeetBot`_ 0.1.4

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



From kwade at redhat.com  Wed May 23 15:12:04 2012
From: kwade at redhat.com (Karsten 'quaid' Wade)
Date: Wed, 23 May 2012 08:12:04 -0700
Subject: Outage: www.ovirt. org planned server restart Thu 24 May 0400 UTC
Message-ID: <4FBCFE44.7030007@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

There will be a outage starting at 2100 EDT 21 May/0100 UTC 22 May
lasting up to ten minutes.

To convert UTC to your local time, run:
  date -d '2012-05-24 04:00 UTC'

Reason for outage:

Our hosted VM has an updated kernel that needs to be booted in to.

Other packages have been updated, too.

Outage should last less than ten minutes, as long as it remains a
simple reboot ...

Affected services:
 www.ovirt.org (WordPress and MediaWiki)
 lists.ovirt.org (Mailman)
 ovirt.org/releases

Unaffected services:
 gerrit.ovirt.org
 jenkins.ovirt.org

Please join #ovirt on irc.oftc.net or respond to this email to track
the status of this outage.

- -- 
- -- 
Karsten 'quaid' Wade, Sr. Analyst - Community Growth
Red Hat Open Source and Standards (OSAS)
http://TheOpenSourceWay.org
@quaid (identi.ca/twitter/IRC) | gpg: AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFPvP5E2ZIOBq0ODEERAqeEAKDcflKFg+if+L0moxmLb4Dcma2GCACghNGb
JVe3NbHXZYY6nqUarq/+gpo=
=htTi
-----END PGP SIGNATURE-----


From lhawthor at redhat.com  Wed May 23 16:57:42 2012
From: lhawthor at redhat.com (Leslie Hawthorn)
Date: Wed, 23 May 2012 09:57:42 -0700
Subject: oVirt Board Meetings at Workshops
Message-ID: <4FBD1706.2030504@redhat.com>

Hello everyone,

Given that many of our Board Members will be in attendance at some of 
our larger upcoming workshops [0], it would be useful to arrange Board 
meetings during these face to face gatherings. While there is not 
sufficient time to make arrangements for such a meeting at LinuxCon 
Japan, I would like to facilitate arrangements for Board Meetings at our 
other upcoming workshops.

I'd like to gather data on which workshops would work best for Board 
Meetings. Specifically, understanding if the oVirt Board would be 
interested in meeting at all of these workshops or only a subset of 
them. If we're aiming for a subset, which workshop dates/locations work 
best for all?

To collect this data, I've created a planning page [1] on the oVirt 
wiki. I'm asking that our Board Members review the page and add their 
preferences for Board Meeting locations. I'll then follow up on keeping 
the community updated on Board Meetings both on list and during our 
weekly IRC meetings.

[0] - http://www.ovirt.org/wiki/OVirt_Global_Workshops

[1] - http://www.ovirt.org/wiki/Workshop_Board_Meetings

Best,
LH

-- 
Leslie Hawthorn
Community Action and Impact
Open Source and Standards @ Red Hat

identi.ca/lh
twitter.com/lhawthorn



From snmishra at linux.vnet.ibm.com  Wed May 23 16:58:17 2012
From: snmishra at linux.vnet.ibm.com (snmishra at linux.vnet.ibm.com)
Date: Wed, 23 May 2012 12:58:17 -0400
Subject: [Engine-devel] Maven 3 here we come!
In-Reply-To: <92d79202-3390-4994-ad8f-6bd99030a5d0@zmail17.collab.prod.int.phx2.redhat.com>
References: <92d79202-3390-4994-ad8f-6bd99030a5d0@zmail17.collab.prod.int.phx2.redhat.com>
Message-ID: <20120523125817.Horde.WliYBpir309PvRcp7m2hSzA@imap.linux.ibm.com>


New to maven. Using rhel6.2, and installed maven 3.0.4. Changed path  
to pick this version instead of 2.2.1 I was using before.

when running "mvn clean install" I see -

Downloading:  
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.pom

It doesn't look right, shouldn't it be maven3 instead of maven2 ?

Do we need to update the "Maven personal settings" section on  
http://www.ovirt.org/wiki/Building_Ovirt_Engine

At least the part where it says "maven 3.x will not work". How about  
~/.m2/settings.xml ?

-Sharad

Quoting Eyal Edri <eedri at redhat.com>:

> ----- Original Message -----
>> From: "Doron Fediuck" <dfediuck at redhat.com>
>> To: engine-devel at ovirt.org
>> Cc: "<arch at ovirt.org>" <arch at ovirt.org>
>> Sent: Wednesday, May 23, 2012 12:59:53 PM
>> Subject: [Engine-devel] Maven 3 here we come!
>>
>> Hi all,
>> As discussed last month[1], we had to deal with some issues which
>> turned out to be a Maven bug.
>> Thanks to Juan and Asaf's work, our current sources now build
>> properly using Maven 3.
>> So you're all invited to migrate into Maven 3. Other than upgrading
>> your local maven package
>> no other action is needed.
>>
>> For now, Maven 2 will also work for you, but I expect in the future
>> we'd like to make use
>> of some advanced features, so migration to 3 is recommended.
>>
>> Talking about advanced features, an interesting challenge is feedback
>> on parallel builds [2].
>> So whoever wants to try it out and report if it improves run time
>> without breaking anything,
>> will be appreciated.
>>
>> Happy migration!
>>
>> [1]http://lists.ovirt.org/pipermail/arch/2012-April/000490.html
>> [2] https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html
>> --
>
> +1 on the move and testing out new features!
>
>>
>> /d
>>
>> "Email returned to sender -- insufficient voltage."
>> _______________________________________________
>> Engine-devel mailing list
>> Engine-devel at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>>
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel





From ykaul at redhat.com  Wed May 23 20:04:12 2012
From: ykaul at redhat.com (Yaniv Kaul)
Date: Wed, 23 May 2012 23:04:12 +0300
Subject: [Engine-devel] Maven 3 here we come!
In-Reply-To: <4FBCB519.60606@redhat.com>
References: <4FBCB519.60606@redhat.com>
Message-ID: <4FBD42BC.3040808@redhat.com>

On 05/23/2012 12:59 PM, Doron Fediuck wrote:
> Hi all,
> As discussed last month[1], we had to deal with some issues which turned out to be a Maven bug.
> Thanks to Juan and Asaf's work, our current sources now build properly using Maven 3.
> So you're all invited to migrate into Maven 3. Other than upgrading your local maven package
> no other action is needed.
>
> For now, Maven 2 will also work for you, but I expect in the future we'd like to make use
> of some advanced features, so migration to 3 is recommended.
>
> Talking about advanced features, an interesting challenge is feedback on parallel builds [2].

I'm not happy with parallel builds - it creates more java processes, 
each taking quite a bit of memory. This, in turn, causes them to swap, 
making everything crawl.
Took me 22 minutes to compile the webadmin and additional 21 minutes for 
the user portal, with -T 4. I've had 3.5GB of swap used (and 7GB 
resident memory with 'java' processes running around).
It usually takes me

The command line I've used was:
mvn -T 4 clean install -Pgwt-admin,gwt-user -DskipTests=true 
-Dmaven.test.skip=true


As opposed to 7+ 3 minutes without '-T 4'.

Y.

> So whoever wants to try it out and report if it improves run time without breaking anything,
> will be appreciated.
>
> Happy migration!
>
> [1]http://lists.ovirt.org/pipermail/arch/2012-April/000490.html
> [2]https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html




From eedri at redhat.com  Thu May 24 05:39:28 2012
From: eedri at redhat.com (Eyal Edri)
Date: Thu, 24 May 2012 01:39:28 -0400 (EDT)
Subject: [Engine-devel] Maven 3 here we come!
In-Reply-To: <4FBD42BC.3040808@redhat.com>
Message-ID: <8d85c9c0-3207-412e-8953-b317a3b43d50@zmail17.collab.prod.int.phx2.redhat.com>



----- Original Message -----
> From: "Yaniv Kaul" <ykaul at redhat.com>
> To: "Doron Fediuck" <dfediuck at redhat.com>
> Cc: engine-devel at ovirt.org, "<arch at ovirt.org>" <arch at ovirt.org>
> Sent: Wednesday, May 23, 2012 11:04:12 PM
> Subject: Re: [Engine-devel] Maven 3 here we come!
> 
> On 05/23/2012 12:59 PM, Doron Fediuck wrote:
> > Hi all,
> > As discussed last month[1], we had to deal with some issues which
> > turned out to be a Maven bug.
> > Thanks to Juan and Asaf's work, our current sources now build
> > properly using Maven 3.
> > So you're all invited to migrate into Maven 3. Other than upgrading
> > your local maven package
> > no other action is needed.
> >
> > For now, Maven 2 will also work for you, but I expect in the future
> > we'd like to make use
> > of some advanced features, so migration to 3 is recommended.
> >
> > Talking about advanced features, an interesting challenge is
> > feedback on parallel builds [2].
> 
> I'm not happy with parallel builds - it creates more java processes,
> each taking quite a bit of memory. This, in turn, causes them to
> swap,
> making everything crawl.
> Took me 22 minutes to compile the webadmin and additional 21 minutes
> for
> the user portal, with -T 4. I've had 3.5GB of swap used (and 7GB
> resident memory with 'java' processes running around).
> It usually takes me
> 
> The command line I've used was:
> mvn -T 4 clean install -Pgwt-admin,gwt-user -DskipTests=true
> -Dmaven.test.skip=true
> 

Have you tried using the mvn -T 1C option (to run one thread per core?)
On some builds it reduced my compilation time in a few min,
but it wasn't consistent.

also, maven says that some of the modules are not thread-safe 
and he will run then sequentially, so perhaps if the modules were re-factored
to fit parallel builds, only then we'll see real improvement. 

> 
> As opposed to 7+ 3 minutes without '-T 4'.
> 
> Y.
> 
> > So whoever wants to try it out and report if it improves run time
> > without breaking anything,
> > will be appreciated.
> >
> > Happy migration!
> >
> > [1]http://lists.ovirt.org/pipermail/arch/2012-April/000490.html
> > [2]https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html
> 
> 
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch
> 


From dfediuck at redhat.com  Thu May 24 06:50:32 2012
From: dfediuck at redhat.com (Doron Fediuck)
Date: Thu, 24 May 2012 09:50:32 +0300
Subject: [Engine-devel] Maven 3 here we come!
In-Reply-To: <20120523125817.Horde.WliYBpir309PvRcp7m2hSzA@imap.linux.ibm.com>
References: <92d79202-3390-4994-ad8f-6bd99030a5d0@zmail17.collab.prod.int.phx2.redhat.com>
	<20120523125817.Horde.WliYBpir309PvRcp7m2hSzA@imap.linux.ibm.com>
Message-ID: <4FBDDA38.4040200@redhat.com>

On 23/05/12 19:58, snmishra at linux.vnet.ibm.com wrote:
> 
> New to maven. Using rhel6.2, and installed maven 3.0.4. Changed path to pick this version instead of 2.2.1 I was using before.
> 
> when running "mvn clean install" I see -
> 
> Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.pom
> 
> It doesn't look right, shouldn't it be maven3 instead of maven2 ?

Sharad, Maven works with plugins for various tasks. Each plugin is a Maven artifact with its own version.
The install plugin handles installation tasks to local repository. You can read more about it here: http://maven.apache.org/plugins/maven-install-plugin/
So in this case, your Maven 3 is using a plugin called maven-install, and the /plugin's/ version is 2.3.1. 
That's perfectly fine.

> 
> Do we need to update the "Maven personal settings" section on http://www.ovirt.org/wiki/Building_Ovirt_Engine
> 
> At least the part where it says "maven 3.x will not work". How about ~/.m2/settings.xml ?

Thanks for the reminder- wiki updated. No change needed for the settings.xml file, or its location.

> 
> -Sharad
> 
> Quoting Eyal Edri <eedri at redhat.com>:
> 
>> ----- Original Message -----
>>> From: "Doron Fediuck" <dfediuck at redhat.com>
>>> To: engine-devel at ovirt.org
>>> Cc: "<arch at ovirt.org>" <arch at ovirt.org>
>>> Sent: Wednesday, May 23, 2012 12:59:53 PM
>>> Subject: [Engine-devel] Maven 3 here we come!
>>>
>>> Hi all,
>>> As discussed last month[1], we had to deal with some issues which
>>> turned out to be a Maven bug.
>>> Thanks to Juan and Asaf's work, our current sources now build
>>> properly using Maven 3.
>>> So you're all invited to migrate into Maven 3. Other than upgrading
>>> your local maven package
>>> no other action is needed.
>>>
>>> For now, Maven 2 will also work for you, but I expect in the future
>>> we'd like to make use
>>> of some advanced features, so migration to 3 is recommended.
>>>
>>> Talking about advanced features, an interesting challenge is feedback
>>> on parallel builds [2].
>>> So whoever wants to try it out and report if it improves run time
>>> without breaking anything,
>>> will be appreciated.
>>>
>>> Happy migration!
>>>
>>> [1]http://lists.ovirt.org/pipermail/arch/2012-April/000490.html
>>> [2] https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html
>>> -- 
>>
>> +1 on the move and testing out new features!
>>
>>>
>>> /d
>>>
>>> "Email returned to sender -- insufficient voltage."
>>> _______________________________________________
>>> Engine-devel mailing list
>>> Engine-devel at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>>>
>> _______________________________________________
>> Engine-devel mailing list
>> Engine-devel at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/engine-devel
> 
> 
> 


-- 

/d

"This message is made with 100% recycled electrons. No new atoms were destroyed in the making of this message."


From kwade at redhat.com  Thu May 24 08:08:39 2012
From: kwade at redhat.com (Karsten 'quaid' Wade)
Date: Thu, 24 May 2012 01:08:39 -0700
Subject: Outage: www.ovirt. org planned server restart Thu 24 May 0400 UTC
In-Reply-To: <4FBCFE44.7030007@redhat.com>
References: <4FBCFE44.7030007@redhat.com>
Message-ID: <4FBDEC87.6080308@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I was unable to make this window, so I am cancelling this outage. I am
rescheduling this for 2012-05-25 00:00 UTC, which is a better time for me.

To convert UTC to your local time, run:
  date -d '2012-05-25 00:00 UTC'

If you have any problems with this time, email me back.

Thanks - Karsten

On 05/23/2012 08:12 AM, Karsten 'quaid' Wade wrote:
> There will be a outage starting at 2100 EDT 21 May/0100 UTC 22 May 
> lasting up to ten minutes.
> 
> To convert UTC to your local time, run: date -d '2012-05-24 04:00
> UTC'
> 
> Reason for outage:
> 
> Our hosted VM has an updated kernel that needs to be booted in to.
> 
> Other packages have been updated, too.
> 
> Outage should last less than ten minutes, as long as it remains a 
> simple reboot ...
> 
> Affected services: www.ovirt.org (WordPress and MediaWiki) 
> lists.ovirt.org (Mailman) ovirt.org/releases
> 
> Unaffected services: gerrit.ovirt.org jenkins.ovirt.org
> 
> Please join #ovirt on irc.oftc.net or respond to this email to
> track the status of this outage.
> 
> _______________________________________________ Infra mailing list 
> Infra at ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

- -- 
Karsten 'quaid' Wade, Sr. Analyst - Community Growth
Red Hat Open Source and Standards (OSAS)
http://TheOpenSourceWay.org
@quaid (identi.ca/twitter/IRC) | gpg: AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFPveyH2ZIOBq0ODEERAre9AJ9AOqXzlR4mtfGzjOxU1pXjH6XlLgCgl1lY
ZhamvgeDAw3n/AMFSpL7dPg=
=uR3d
-----END PGP SIGNATURE-----


From robert at middleswarth.net  Thu May 24 16:36:38 2012
From: robert at middleswarth.net (Robert Middleswarth)
Date: Thu, 24 May 2012 12:36:38 -0400
Subject: Release guide lines not follow for the 1st release.
Message-ID: <4FBE6396.7070400@middleswarth.net>

I have started looking over the code as I plan to start to contribute to
the project.  Well reviewing I noticed there was no branches in vdsm
outside master.  I started asking around in irc and looking around in
the wiki.  I found http://www.ovirt.org/wiki/Release_Process and from
what I can tell these processes weren't followed on the 3.0 release. 
Under section 4 it calls for "All component owners must create a new
version branch" It looks like only the engine created a branch.  No
other projects have.  There are tags but no branches. 

Thanks
Robert
 


From agl at us.ibm.com  Thu May 24 20:28:05 2012
From: agl at us.ibm.com (Adam Litke)
Date: Thu, 24 May 2012 15:28:05 -0500
Subject: Screen sharing options for oVirt developer meetings
Message-ID: <20120524202805.GC10465@aglitke.ibm.com>

Hi all,

I am pushing a REST API into vdsm and some members on the team have requested
that we conduct a code-walkthrough where we can discuss some of the new
technology that is being used by the patch series.  In order to do this, I would
like to use a shared screen so the group can view the code together.  Within IBM
I would use a vnc session or LotusLive.  Here are my requirements:

 - Freely available to all community participants
 - Publicly accessible
 - Easy to set up
 - Scalable to at least 20 worldwide connections

I am wondering if we can set up some infrastructure on oVirt.org that can be
used for this purpose.  Perhaps we can just use a Linux VM with a preconfigured
VNC server.  Are there any other ideas on how we could accomplish such a feat?

Thanks for your input!

-- 
Adam Litke <agl at us.ibm.com>
IBM Linux Technology Center



From kwade at redhat.com  Fri May 25 00:21:13 2012
From: kwade at redhat.com (Karsten 'quaid' Wade)
Date: Thu, 24 May 2012 17:21:13 -0700
Subject: Outage: www.ovirt. org planned server restart Thu 24 May 00:00 UTC
In-Reply-To: <4FBDEC87.6080308@redhat.com>
References: <4FBCFE44.7030007@redhat.com> <4FBDEC87.6080308@redhat.com>
Message-ID: <4FBED079.7080903@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The server reboot was successful. In addition, I updated some
WordPress plugins.

My only concern with this outage was in planning. Because updating
WordPress and other server packages includes moving from versions with
potential security exploits, I wanted to take the cautious route of
not announcing the details of the update before doing it. I did
discuss things overall with Jason Brooks in private IRC, but we are
lacking in any way for me to easily discuss with the rest of the
Infrastructure team.

So, suggestions for improving that part of this process are most welcome.

- - Karsten, who finally fixed the Subject this time.

On 05/24/2012 01:08 AM, Karsten 'quaid' Wade wrote:
> I was unable to make this window, so I am cancelling this outage. I
> am rescheduling this for 2012-05-25 00:00 UTC, which is a better
> time for me.
> 
> To convert UTC to your local time, run: date -d '2012-05-25 00:00
> UTC'
> 
> If you have any problems with this time, email me back.
> 
> Thanks - Karsten
> 
> On 05/23/2012 08:12 AM, Karsten 'quaid' Wade wrote:
>> There will be a outage starting at 2100 EDT 21 May/0100 UTC 22
>> May lasting up to ten minutes.
> 
>> To convert UTC to your local time, run: date -d '2012-05-24
>> 04:00 UTC'
> 
>> Reason for outage:
> 
>> Our hosted VM has an updated kernel that needs to be booted in
>> to.
> 
>> Other packages have been updated, too.
> 
>> Outage should last less than ten minutes, as long as it remains a
>>  simple reboot ...
> 
>> Affected services: www.ovirt.org (WordPress and MediaWiki) 
>> lists.ovirt.org (Mailman) ovirt.org/releases
> 
>> Unaffected services: gerrit.ovirt.org jenkins.ovirt.org
> 
>> Please join #ovirt on irc.oftc.net or respond to this email to 
>> track the status of this outage.
> 
>> _______________________________________________ Infra mailing
>> list Infra at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
> 
> _______________________________________________ Arch mailing list 
> Arch at ovirt.org http://lists.ovirt.org/mailman/listinfo/arch

- -- 
Karsten 'quaid' Wade, Sr. Analyst - Community Growth
Red Hat Open Source and Standards (OSAS)
http://TheOpenSourceWay.org
@quaid (identi.ca/twitter/IRC) | gpg: AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFPvtB52ZIOBq0ODEERAmCXAJoCm/9Q6kVH/Hpq029K4b6fXXeCrQCg2JwX
jJv7qrT9fTsu7CtAi5jF8gw=
=mZ3h
-----END PGP SIGNATURE-----


From mburns at redhat.com  Fri May 25 01:07:32 2012
From: mburns at redhat.com (Mike Burns)
Date: Thu, 24 May 2012 21:07:32 -0400
Subject: Release guide lines not follow for the 1st release.
In-Reply-To: <4FBE6396.7070400@middleswarth.net>
References: <4FBE6396.7070400@middleswarth.net>
Message-ID: <1337908052.3606.47.camel@beelzebub.mburnsfire.net>

On Thu, 2012-05-24 at 12:36 -0400, Robert Middleswarth wrote:
> I have started looking over the code as I plan to start to contribute to
> the project.  Well reviewing I noticed there was no branches in vdsm
> outside master.  I started asking around in irc and looking around in
> the wiki.  I found http://www.ovirt.org/wiki/Release_Process and from
> what I can tell these processes weren't followed on the 3.0 release. 
> Under section 4 it calls for "All component owners must create a new
> version branch" It looks like only the engine created a branch.  No
> other projects have.  There are tags but no branches. 

While I understand the point of having branches like that, I don't know
that I agree with making it a requirement.  With git, having a tag for
the version is just as good as having a branch.  In the case that a
critical fix is needed, a branch can be created with minimal effort.
I'd propose that we adjust the Release Process to say that a tag is
created.  A separate versioned branch can be created if it's actually
needed.

Mike

> 
> Thanks
> Robert
>  
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch




From mburns at redhat.com  Wed May 30 14:46:08 2012
From: mburns at redhat.com (Mike Burns)
Date: Wed, 30 May 2012 10:46:08 -0400
Subject: oVirt Weekly Meeting Minutes -- 2012-05-30
Message-ID: <1338389168.3802.3.camel@mburns-laptop.usersys.redhat.com>

Minutes:        http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-30-14.00.html
Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-30-14.00.txt
Log:            http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-30-14.00.log.html

=========================
#ovirt: oVirt Weekly Sync
=========================


Meeting started by mburns at 14:00:20 UTC. The full logs are available
at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-05-30-14.00.log.html
.



Meeting summary
---------------
* agenda and roll call  (mburns, 14:00:53)
  * LINK: http://www.ovirt.org/wiki/Meetings#Weekly_project_sync_meeting
    (mburns, 14:01:16)

* Release status  (mburns, 14:03:59)
  * devel freeze June 7  (mburns, 14:04:11)
  * Beta shortly after  (mburns, 14:04:16)
  * GA June 27  (mburns, 14:04:22)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=822145
    (oschreib_1, 14:04:34)
  * good progress with Fedora JBoss rpms  (mburns, 14:05:45)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=824397
    (oschreib_1, 14:05:49)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=822158
    (oschreib_1, 14:06:55)
  * patch coming today -- testing in progress  (mburns, 14:08:43)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=824420   (mburns,
    14:09:12)
  * dependent blocking bug in util-linux is fixed and verified, but we
    hit an additional issue yesterday  (mburns, 14:09:48)
  * still digging into it to find the root cause  (mburns, 14:10:00)
  * ACTION: oschreib_1 to build alpha build and upload to ovirt.org once
    vdsm/engine issues are fixed/merged  (mburns, 14:13:05)
  * ACTION: mburns to do same with ovirt-node once its blockers fixed
    and vdsm generated  (mburns, 14:13:24)

* sub project status -- vdsm  (mburns, 14:13:42)
  * no update from vdsm team  (mburns, 14:15:37)

* sub project status -- engine  (mburns, 14:15:42)
  * things in good shape on the engine side  (mburns`, 14:18:03)
  * node is unclear at the moment, installs correctly, but blocked by
    login issues currently  (mburns`, 14:19:53)
  * should know more in next couple days  (mburns`, 14:20:00)

* java 7 and fedora jboss rpms  (mburns, 14:30:56)
  * AGREED: Fedora 17 jboss rpms and jboss 7 support will be included in
    3.1  (mburns, 14:32:36)

* Workshops and Conferences  (mburns, 14:33:11)
  * LINK: http://www.ovirt.org/wiki/Workshop_Board_Meetings   (mburns,
    14:34:15)
  * Board Members:  please commit to attending Board Meetings at ^^
    (mburns, 14:34:43)
  * next proposed board meeting is at LinuxCon North America in August
    (mburns, 14:35:10)

* Other Topics  (mburns, 14:37:15)
  * oschreib_1 to run next week's meeting since mburns won't be around
    (mburns, 14:38:56)

Meeting ended at 14:44:52 UTC.




Action Items
------------
* oschreib_1 to build alpha build and upload to ovirt.org once
  vdsm/engine issues are fixed/merged
* mburns to do same with ovirt-node once its blockers fixed and vdsm
  generated




Action Items, by person
-----------------------
* mburns
  * mburns to do same with ovirt-node once its blockers fixed and vdsm
    generated
* oschreib_1
  * oschreib_1 to build alpha build and upload to ovirt.org once
    vdsm/engine issues are fixed/merged
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* mburns (74)
* oschreib_1 (45)
* lh (8)
* itamar (8)
* mburns` (7)
* RobertM (6)
* ovirtbot (6)
* cctrieloff (4)
* mburns`` (2)
* jhernand (2)
* dougsland (1)
* rickyh (1)
* mgoldboi (1)




Generated by `MeetBot`_ 0.1.4

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



From quaid at iquaid.org  Mon May 21 17:39:39 2012
From: quaid at iquaid.org (Karsten (quaid) Wade)
Date: Mon, 21 May 2012 17:39:39 -0000
Subject: Outage: www.ovirt. org planned server restart Tue 22 May 0100 UTC
Message-ID: <4FBA7DD7.5020106@iquaid.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

There will be a outage starting at 2100 EDT 21 May/0100 UTC 22 May
lasting up to three hours.

To convert UTC to your local time, run:
  date -d '2012-04-13 22:00 UTC'

Reason for outage:

The hosting provider for ovirt.org has a server reboot scheduled for
tonight. They intend to do a soft landing, upgrade software, and
restart the VMs.

Once the outage is completed, I will make sure that all services have
restarted properly.

Affected services:
 www.ovirt.org (WordPress and MediaWiki)
 lists.ovirt.org (Mailman)
 ovirt.org/releases

Unaffected services:
 gerrit.ovirt.org
 jenkins.ovirt.org

Please join #ovirt on irc.oftc.net or respond to this email to track
the status of this outage.

- -- 
Karsten 'quaid' Wade ..... http://iquaid.org ..... gpg key: AD0E0C41
http://Fairy-TaleFarm.com .......................... Urban homestead
http://MicahForCouncil.org ................ Your advocate on council
http://SantaCruzPedicab.com .......... Sensible local transportation
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFPun3X2ZIOBq0ODEERAgQXAJ93cVbg2TgDTT5pT/MiENLqx/Q4nACgu/zB
ZiB7rR3Z5iuQU1XLBzzxVig=
=aYa2
-----END PGP SIGNATURE-----