From iheim at redhat.com  Fri Jun  1 16:02:51 2012
From: iheim at redhat.com (Itamar Heim)
Date: Fri, 01 Jun 2012 19:02:51 +0300
Subject: compile time (was Re: [Engine-devel] Maven 3 here we come!)
In-Reply-To: <4FBD42BC.3040808@redhat.com>
References: <4FBCB519.60606@redhat.com> <4FBD42BC.3040808@redhat.com>
Message-ID: <4FC8E7AB.5060802@redhat.com>

On 05/23/2012 11:04 PM, Yaniv Kaul wrote:
> 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'.

Saggi gave me his command line, which doesn't require any change of 
settings.xml

mvn clean install -Pgwtdev,gwt-admin -DskipTests 
-Dgwt.userAgent=gecko1_8 -Dgwt.draftCompile=true 
-Dgwt.compiler.optimizationLevel=0 -Dgwt.compiler.localWorkers=2 
-Dmaven.aspectj.incremental=true -Dmaven.aspectj.time=true

I wonder if we shouldn't make something similar to this as the default.
preferably, add ./configure script to tweak different options (which is 
very common in non java projects).


From smizrahi at redhat.com  Fri Jun  1 16:14:03 2012
From: smizrahi at redhat.com (Saggi Mizrahi)
Date: Fri, 01 Jun 2012 12:14:03 -0400 (EDT)
Subject: [Engine-devel] compile time (was Re:  Maven 3 here we come!)
In-Reply-To: <4FC8E7AB.5060802@redhat.com>
Message-ID: <b0bf52c8-34c7-426b-8f97-1803d2b01110@zmail16.collab.prod.int.phx2.redhat.com>



----- Original Message -----
> From: "Itamar Heim" <iheim at redhat.com>
> To: "Yaniv Kaul" <ykaul at redhat.com>
> Cc: engine-devel at ovirt.org, "<arch at ovirt.org>" <arch at ovirt.org>
> Sent: Friday, June 1, 2012 12:02:51 PM
> Subject: [Engine-devel] compile time (was Re:  Maven 3 here we come!)
> 
> On 05/23/2012 11:04 PM, Yaniv Kaul wrote:
> > 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'.
> 
> Saggi gave me his command line, which doesn't require any change of
> settings.xml
> 
> mvn clean install -Pgwtdev,gwt-admin -DskipTests
> -Dgwt.userAgent=gecko1_8 -Dgwt.draftCompile=true
> -Dgwt.compiler.optimizationLevel=0 -Dgwt.compiler.localWorkers=2
> -Dmaven.aspectj.incremental=true -Dmaven.aspectj.time=true
It will have to be optional with configure flags like --disable-optimization --disable-extra-user-agents --local-workers=2
So people know what they are doing and can choose what is best for them as I use 2 local workers because my host as 2 cores with HT which means by default it will start 4 local workers and have all my processing threads stuck on IO stopping the machine. Other, more powerful hosts, might be able to ramp the local workers.
Also you might want to turn on debug but still check other user agents.

> 
> I wonder if we shouldn't make something similar to this as the
> default.
> preferably, add ./configure script to tweak different options (which
> is
> very common in non java projects).
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
> 


From eedri at redhat.com  Sat Jun  2 09:00:34 2012
From: eedri at redhat.com (Eyal Edri)
Date: Sat, 02 Jun 2012 05:00:34 -0400 (EDT)
Subject: compile time (was Re: [Engine-devel] Maven 3 here we come!)
In-Reply-To: <4FC8E7AB.5060802@redhat.com>
Message-ID: <dc9224c6-6fe2-4db0-a720-e2185f78c63b@zmail17.collab.prod.int.phx2.redhat.com>



----- Original Message -----
> From: "Itamar Heim" <iheim at redhat.com>
> To: "Yaniv Kaul" <ykaul at redhat.com>
> Cc: engine-devel at ovirt.org, "<arch at ovirt.org>" <arch at ovirt.org>
> Sent: Friday, June 1, 2012 7:02:51 PM
> Subject: compile time (was Re: [Engine-devel] Maven 3 here we come!)
> 
> On 05/23/2012 11:04 PM, Yaniv Kaul wrote:
> > 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'.
> 
> Saggi gave me his command line, which doesn't require any change of
> settings.xml
> 
> mvn clean install -Pgwtdev,gwt-admin -DskipTests
> -Dgwt.userAgent=gecko1_8 -Dgwt.draftCompile=true
> -Dgwt.compiler.optimizationLevel=0 -Dgwt.compiler.localWorkers=2
> -Dmaven.aspectj.incremental=true -Dmaven.aspectj.time=true

how much time this command cuts from build time? 
shouldn't we use this in CI as well?

> 
> I wonder if we shouldn't make something similar to this as the
> default.
> preferably, add ./configure script to tweak different options (which
> is
> very common in non java projects).
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch
> 


From iheim at redhat.com  Sun Jun  3 08:30:13 2012
From: iheim at redhat.com (Itamar Heim)
Date: Sun, 03 Jun 2012 11:30:13 +0300
Subject: compile time (was Re: [Engine-devel] Maven 3 here we come!)
In-Reply-To: <dc9224c6-6fe2-4db0-a720-e2185f78c63b@zmail17.collab.prod.int.phx2.redhat.com>
References: <dc9224c6-6fe2-4db0-a720-e2185f78c63b@zmail17.collab.prod.int.phx2.redhat.com>
Message-ID: <4FCB2095.9060205@redhat.com>

On 06/02/2012 12:00 PM, Eyal Edri wrote:
>
>
> ----- Original Message -----
>> From: "Itamar Heim"<iheim at redhat.com>
>> To: "Yaniv Kaul"<ykaul at redhat.com>
>> Cc: engine-devel at ovirt.org, "<arch at ovirt.org>"<arch at ovirt.org>
>> Sent: Friday, June 1, 2012 7:02:51 PM
>> Subject: compile time (was Re: [Engine-devel] Maven 3 here we come!)
>>
>> On 05/23/2012 11:04 PM, Yaniv Kaul wrote:
>>> 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'.
>>
>> Saggi gave me his command line, which doesn't require any change of
>> settings.xml
>>
>> mvn clean install -Pgwtdev,gwt-admin -DskipTests
>> -Dgwt.userAgent=gecko1_8 -Dgwt.draftCompile=true
>> -Dgwt.compiler.optimizationLevel=0 -Dgwt.compiler.localWorkers=2
>> -Dmaven.aspectj.incremental=true -Dmaven.aspectj.time=true
>
> how much time this command cuts from build time?
> shouldn't we use this in CI as well?

i get a 3.5 minutes build with this.

with the exception of skipTests which in some jobs you want to run - 
yes. also -Pgwt-user is relevant to some jobs.
(and if this becomes more of the default compile mode, you would need to 
tweak it only when you need to)

>
>>
>> I wonder if we shouldn't make something similar to this as the
>> default.
>> preferably, add ./configure script to tweak different options (which
>> is
>> very common in non java projects).
>> _______________________________________________
>> Arch mailing list
>> Arch at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/arch
>>



From mburns at redhat.com  Mon Jun  4 08:50:01 2012
From: mburns at redhat.com (Mike Burns)
Date: Mon, 04 Jun 2012 17:50:01 +0900
Subject: Call For Agenda Items -- oVirt Weekly Sync Meeting 2012-06-06
Message-ID: <1338799801.5077.5.camel@mburns-laptop.usersys.redhat.com>

The current agenda is always listed on the wiki [1]

Please reply if you have other agenda items to bring up.

Also, as a reminder, If you propose a topic or are a maintainer of one
of the core sub-projects, either you or a delegate need to be in
attendance at the meeting to either drive your topic or give project
status.

Thanks

Mike

[1] http://www.ovirt.org/wiki/Meetings#Weekly_project_sync_meeting



From robert at middleswarth.net  Tue Jun  5 17:26:05 2012
From: robert at middleswarth.net (Robert Middleswarth)
Date: Tue, 05 Jun 2012 13:26:05 -0400
Subject: Adding redirect for http://wiki.ovirt.org to
	http://www.ovirt.org/wiki/Main_Page
Message-ID: <4FCE412D.1050304@middleswarth.net>

This change would take all of 5 min to make but would help for people
who just goto wiki.xxx assuming that is where the project wiki will sit.

Thanks
Robert


From oschreib at redhat.com  Wed Jun  6 14:59:35 2012
From: oschreib at redhat.com (Ofer Schreiber)
Date: Wed, 06 Jun 2012 10:59:35 -0400 (EDT)
Subject: oVirt Weekly Meeting Minutes -- 2012-06-06
In-Reply-To: <9a096fff-ad4f-4e86-b106-9b97223c0870@zmail14.collab.prod.int.phx2.redhat.com>
Message-ID: <90b1e05c-b95c-4df5-ab8a-d5ba2fadad9a@zmail14.collab.prod.int.phx2.redhat.com>

Minutes:        http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-06-14.01.html
Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-06-14.01.txt
Log:            http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-06-14.01.log.html

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


Meeting started by oschreib at 14:01:34 UTC. The full logs are available
at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-06-14.01.log.html

Meeting summary
---------------
* agenda and roll call  (oschreib, 14:01:45)

* Release status  (oschreib, 14:04:32)
  * devel freeze June 7 (tomorrow)  (oschreib, 14:04:44)
  * Beta shortly after  (oschreib, 14:04:50)
  * GA June 27  (oschreib, 14:04:56)
  * test day June 14  (oschreib, 14:05:07)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=824420
    (oschreib, 14:06:51)
  * AGREED: ovirt 3.1 feature freeze will be 07.06.2012 (tomorrow)
    (oschreib, 14:09:04)
  * node should be ready few days after  (oschreib, 14:09:17)
  * vdsm is in feature freeze  (aglitke, 14:11:47)
  * AGREED: mburns will be release manager next week  (oschreib,
    14:13:31)
  * ACTION: mburns to replace oschreib as release manager next week
    (oschreib, 14:14:05)

* sub project status -- vdsm  (oschreib, 14:14:29)
  * AGREED: vdsm version should be bumped  (oschreib, 14:20:20)
  * ACTION: danken to handle vdsm version until tomorrow  (oschreib,
    14:20:35)

* sub project status -- engine  (oschreib, 14:21:15)
  * things in good shape on the engine side  (oschreib, 14:23:00)

* sub project status -- node  (oschreib, 14:23:31)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=824420
    (oschreib, 14:25:39)
  * node should support F17 in the next couple of days  (oschreib,
    14:26:01)
  * ACTION: fabiand to update BZ#824420  (oschreib, 14:26:50)

* Workshops and Conferences  (oschreib, 14:27:17)
  * bazulay and mburns are presenting ovirt in linux con Japan this week
    (oschreib, 14:29:40)
  * there will be an ovirt day in n linuxcon NA, then 2.5 co-hosted with
    kvm forum in linuxcon europe  (oschreib, 14:31:43)

* Other Topics  (oschreib, 14:31:48)
  * LINK: http://www.ovirt.org/releases/beta/fedora/17/   (oschreib,
    14:33:24)
  * pre feature freeze F17 builds  (oschreib, 14:33:40)
  * ACTION: oschreib to look for test day lead  (oschreib, 14:37:03)
  * vdsms's setupNetwork is broken  (oschreib, 14:39:15)
  * ACTION: aglitke to link setupNetwork bug on
    https://bugzilla.redhat.com/show_bug.cgi?id=822145  (oschreib,
    14:39:48)

Meeting ended at 14:55:40 UTC.

Action Items
------------
* mburns to replace oschreib as release manager next week
* danken to handle vdsm version until tomorrow
* fabiand to update BZ#824420
* oschreib to look for test day lead
* aglitke to link setupNetwork bug on
  https://bugzilla.redhat.com/show_bug.cgi?id=822145

Action Items, by person
-----------------------
* aglitke
  * aglitke to link setupNetwork bug on
    https://bugzilla.redhat.com/show_bug.cgi?id=822145
* danken
  * danken to handle vdsm version until tomorrow
* fabiand
  * fabiand to update BZ#824420
* oschreib
  * mburns to replace oschreib as release manager next week
  * oschreib to look for test day lead

People Present (lines said)
---------------------------
* oschreib (99)
* aglitke (31)
* danken (24)
* itamar (14)
* ovirtbot (7)
* ykaul (6)
* doron (6)
* fabiand (6)
* dustins (3)
* mgoldboi (3)
* rickyh (2)
* eedri (2)
* yeylon_ (1)
* sgordon_ (1)
* mestery (1)
* ykaul1 (1)
* aaglitke (0)

Generated by `MeetBot`_ 0.1.4

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


From danken at redhat.com  Wed Jun  6 18:35:45 2012
From: danken at redhat.com (Dan Kenigsberg)
Date: Wed, 6 Jun 2012 21:35:45 +0300
Subject: oVirt Weekly Meeting Minutes -- 2012-06-06
In-Reply-To: <90b1e05c-b95c-4df5-ab8a-d5ba2fadad9a@zmail14.collab.prod.int.phx2.redhat.com>
References: <9a096fff-ad4f-4e86-b106-9b97223c0870@zmail14.collab.prod.int.phx2.redhat.com>
	<90b1e05c-b95c-4df5-ab8a-d5ba2fadad9a@zmail14.collab.prod.int.phx2.redhat.com>
Message-ID: <20120606183545.GE19844@redhat.com>

On Wed, Jun 06, 2012 at 10:59:35AM -0400, Ofer Schreiber wrote:
> Minutes:        http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-06-14.01.html
> Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-06-14.01.txt
> Log:            http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-06-14.01.log.html
> 
> =========================
> #ovirt: oVirt Weekly Sync
> =========================
> 
> 
> Meeting started by oschreib at 14:01:34 UTC. The full logs are available
> at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-06-14.01.log.html
> 
> Meeting summary
> ---------------
> * agenda and roll call  (oschreib, 14:01:45)
> 
> * Release status  (oschreib, 14:04:32)
>   * devel freeze June 7 (tomorrow)  (oschreib, 14:04:44)
>   * Beta shortly after  (oschreib, 14:04:50)
>   * GA June 27  (oschreib, 14:04:56)
>   * test day June 14  (oschreib, 14:05:07)
>   * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=824420
>     (oschreib, 14:06:51)
>   * AGREED: ovirt 3.1 feature freeze will be 07.06.2012 (tomorrow)
>     (oschreib, 14:09:04)
>   * node should be ready few days after  (oschreib, 14:09:17)
>   * vdsm is in feature freeze  (aglitke, 14:11:47)
>   * AGREED: mburns will be release manager next week  (oschreib,
>     14:13:31)
>   * ACTION: mburns to replace oschreib as release manager next week
>     (oschreib, 14:14:05)
> 
> * sub project status -- vdsm  (oschreib, 14:14:29)
>   * AGREED: vdsm version should be bumped  (oschreib, 14:20:20)
>   * ACTION: danken to handle vdsm version until tomorrow  (oschreib,
>     14:20:35)

We'd bump vdsm version to 4.10.0 tomorrow, hopefully with
Yair's http://gerrit.ovirt.org/#/c/5062/ included.

> 
> * sub project status -- engine  (oschreib, 14:21:15)
>   * things in good shape on the engine side  (oschreib, 14:23:00)
> 
> * sub project status -- node  (oschreib, 14:23:31)
>   * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=824420
>     (oschreib, 14:25:39)
>   * node should support F17 in the next couple of days  (oschreib,
>     14:26:01)
>   * ACTION: fabiand to update BZ#824420  (oschreib, 14:26:50)
> 
> * Workshops and Conferences  (oschreib, 14:27:17)
>   * bazulay and mburns are presenting ovirt in linux con Japan this week
>     (oschreib, 14:29:40)
>   * there will be an ovirt day in n linuxcon NA, then 2.5 co-hosted with
>     kvm forum in linuxcon europe  (oschreib, 14:31:43)
> 
> * Other Topics  (oschreib, 14:31:48)
>   * LINK: http://www.ovirt.org/releases/beta/fedora/17/   (oschreib,
>     14:33:24)
>   * pre feature freeze F17 builds  (oschreib, 14:33:40)
>   * ACTION: oschreib to look for test day lead  (oschreib, 14:37:03)
>   * vdsms's setupNetwork is broken  (oschreib, 14:39:15)
>   * ACTION: aglitke to link setupNetwork bug on
>     https://bugzilla.redhat.com/show_bug.cgi?id=822145  (oschreib,
>     14:39:48)
> 
> Meeting ended at 14:55:40 UTC.
> 
> Action Items
> ------------
> * mburns to replace oschreib as release manager next week
> * danken to handle vdsm version until tomorrow
> * fabiand to update BZ#824420
> * oschreib to look for test day lead
> * aglitke to link setupNetwork bug on
>   https://bugzilla.redhat.com/show_bug.cgi?id=822145

After a casual review of http://www.ovirt.org/wiki/Second_Release I
understand that setupNetwork is not a strict citerion for this release.

  MUST: Can define VLAN based networks, bond interfaces, and have VLANs over bonded interfaces

Hence, I do not think that setupNetwork is a release blocker. However,
Avi/Adam, could you please see if this requirement is currently
satisfied, and if not open a blocking bug?

Regards,
Dan.


From iheim at redhat.com  Wed Jun  6 20:45:17 2012
From: iheim at redhat.com (Itamar Heim)
Date: Wed, 06 Jun 2012 23:45:17 +0300
Subject: oVirt Weekly Meeting Minutes -- 2012-06-06
In-Reply-To: <20120606183545.GE19844@redhat.com>
References: <9a096fff-ad4f-4e86-b106-9b97223c0870@zmail14.collab.prod.int.phx2.redhat.com>
	<90b1e05c-b95c-4df5-ab8a-d5ba2fadad9a@zmail14.collab.prod.int.phx2.redhat.com>
	<20120606183545.GE19844@redhat.com>
Message-ID: <4FCFC15D.3070507@redhat.com>

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

do you mean this works using setupNetworks, or the old api should be used?
since i'm pretty sure engine needs to be changed to be told to use the 
old API for a 3.1 cluster.


From danken at redhat.com  Thu Jun  7 06:51:11 2012
From: danken at redhat.com (Dan Kenigsberg)
Date: Thu, 7 Jun 2012 09:51:11 +0300
Subject: oVirt Weekly Meeting Minutes -- 2012-06-06
In-Reply-To: <4FCFC15D.3070507@redhat.com>
References: <9a096fff-ad4f-4e86-b106-9b97223c0870@zmail14.collab.prod.int.phx2.redhat.com>
	<90b1e05c-b95c-4df5-ab8a-d5ba2fadad9a@zmail14.collab.prod.int.phx2.redhat.com>
	<20120606183545.GE19844@redhat.com> <4FCFC15D.3070507@redhat.com>
Message-ID: <20120607065109.GQ5797@redhat.com>

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

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


From danken at redhat.com  Thu Jun  7 10:42:55 2012
From: danken at redhat.com (Dan Kenigsberg)
Date: Thu, 7 Jun 2012 13:42:55 +0300
Subject: oVirt Weekly Meeting Minutes -- 2012-06-06
In-Reply-To: <20120606183545.GE19844@redhat.com>
References: <9a096fff-ad4f-4e86-b106-9b97223c0870@zmail14.collab.prod.int.phx2.redhat.com>
	<90b1e05c-b95c-4df5-ab8a-d5ba2fadad9a@zmail14.collab.prod.int.phx2.redhat.com>
	<20120606183545.GE19844@redhat.com>
Message-ID: <20120607104255.GU5797@redhat.com>

On Wed, Jun 06, 2012 at 09:35:45PM +0300, Dan Kenigsberg wrote:
> On Wed, Jun 06, 2012 at 10:59:35AM -0400, Ofer Schreiber wrote:
> > Minutes:        http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-06-14.01.html
> > Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-06-14.01.txt
> > Log:            http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-06-14.01.log.html
> > 
> > =========================
> > #ovirt: oVirt Weekly Sync
> > =========================
> > 
> > 
> > Meeting started by oschreib at 14:01:34 UTC. The full logs are available
> > at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-06-14.01.log.html
> > 
> > Meeting summary
> > ---------------
> > * agenda and roll call  (oschreib, 14:01:45)
> > 
> > * Release status  (oschreib, 14:04:32)
> >   * devel freeze June 7 (tomorrow)  (oschreib, 14:04:44)
> >   * Beta shortly after  (oschreib, 14:04:50)
> >   * GA June 27  (oschreib, 14:04:56)
> >   * test day June 14  (oschreib, 14:05:07)
> >   * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=824420
> >     (oschreib, 14:06:51)
> >   * AGREED: ovirt 3.1 feature freeze will be 07.06.2012 (tomorrow)
> >     (oschreib, 14:09:04)
> >   * node should be ready few days after  (oschreib, 14:09:17)
> >   * vdsm is in feature freeze  (aglitke, 14:11:47)
> >   * AGREED: mburns will be release manager next week  (oschreib,
> >     14:13:31)
> >   * ACTION: mburns to replace oschreib as release manager next week
> >     (oschreib, 14:14:05)
> > 
> > * sub project status -- vdsm  (oschreib, 14:14:29)
> >   * AGREED: vdsm version should be bumped  (oschreib, 14:20:20)
> >   * ACTION: danken to handle vdsm version until tomorrow  (oschreib,
> >     14:20:35)
> 
> We'd bump vdsm version to 4.10.0 tomorrow, hopefully with
> Yair's http://gerrit.ovirt.org/#/c/5062/ included.

Done. v4.10.0 it is.


From mburns at redhat.com  Mon Jun 11 13:46:19 2012
From: mburns at redhat.com (Mike Burns)
Date: Mon, 11 Jun 2012 09:46:19 -0400
Subject: Call For Agenda Items -- oVirt Weekly Sync 2012-06-13
Message-ID: <1339422379.13637.25.camel@beelzebub.mburnsfire.net>

This is the agenda for the 2012-06-13 meeting:

      * Status of Next Release
      * Sub-project reports (engine, vdsm, node)
      * Upcoming workshops

Any other topics to discuss?



From dneary at redhat.com  Mon Jun 11 14:30:43 2012
From: dneary at redhat.com (Dave Neary)
Date: Mon, 11 Jun 2012 16:30:43 +0200
Subject: Call For Agenda Items -- oVirt Weekly Sync 2012-06-13
In-Reply-To: <1339422379.13637.25.camel@beelzebub.mburnsfire.net>
References: <1339422379.13637.25.camel@beelzebub.mburnsfire.net>
Message-ID: <4FD60113.2060409@redhat.com>

Hi,

On 06/11/2012 03:46 PM, Mike Burns wrote:
> This is the agenda for the 2012-06-13 meeting:
>
>        * Status of Next Release
>        * Sub-project reports (engine, vdsm, node)
>        * Upcoming workshops
>
> Any other topics to discuss?

I'd like to attend and discuss how the OSAS team inside RedHat can help 
oVirt - I have been working with Itamar and others to put something 
together, and I think it would be great to get more input on what we 
have so far. Would that be appropriate for the meeting?

Thanks,
Dave.

-- 
Dave Neary
Community Action and Impact
Open Source and Standards Team, Red Hat
Phone: +33 9 50 71 55 62


From mburns at redhat.com  Mon Jun 11 14:36:33 2012
From: mburns at redhat.com (Mike Burns)
Date: Mon, 11 Jun 2012 10:36:33 -0400
Subject: Call For Agenda Items -- oVirt Weekly Sync 2012-06-13
In-Reply-To: <4FD60113.2060409@redhat.com>
References: <1339422379.13637.25.camel@beelzebub.mburnsfire.net>
	<4FD60113.2060409@redhat.com>
Message-ID: <1339425393.13637.33.camel@beelzebub.mburnsfire.net>

On Mon, 2012-06-11 at 16:30 +0200, Dave Neary wrote:
> Hi,
> 
> On 06/11/2012 03:46 PM, Mike Burns wrote:
> > This is the agenda for the 2012-06-13 meeting:
> >
> >        * Status of Next Release
> >        * Sub-project reports (engine, vdsm, node)
> >        * Upcoming workshops
> >
> > Any other topics to discuss?
> 
> I'd like to attend and discuss how the OSAS team inside RedHat can help 
> oVirt - I have been working with Itamar and others to put something 
> together, and I think it would be great to get more input on what we 
> have so far. Would that be appropriate for the meeting?
> 
> Thanks,
> Dave.
> 

Sure, I'll add it to the agenda.  Please be available on Wednesday at
14:00 UTC (10:00 EDT) to lead this discussion.

Thanks

Mike



From gkotton at redhat.com  Tue Jun 12 08:47:43 2012
From: gkotton at redhat.com (Gary Kotton)
Date: Tue, 12 Jun 2012 11:47:43 +0300
Subject: [oVirt][Quantum] question about quantum CLI
In-Reply-To: <CAAskrmH2rXN_nbnoBqkyWHj_mEWNNMhZm-AwcRauJ558nfnobw@mail.gmail.com>
References: <CAAskrmH2rXN_nbnoBqkyWHj_mEWNNMhZm-AwcRauJ558nfnobw@mail.gmail.com>
Message-ID: <4FD7022F.2040600@redhat.com>

Hi Kris,
Thanks for the questions. Please see my inline answers. I have also 
cc'ed the ovirt arch mailing list.
Thanks
Gary

On 06/12/2012 11:21 AM, Kris zhang wrote:
> Hi Gkotton,
>
> I have some questions:
>
> 1) In the file "ovirt.sh", i found the command quantum always use the 
> tenant "default", so if the ovirt don't support multi-tenant?
oVirt does not support multi tenancy at the moment. Maybe there are 
people on the list who can provide more details about this. The initial 
plan was to use the "default" tenant.
>
> 2) There is a parameter "Quantum plugin type (q_plugin)" will pass to 
> VDSM, so if vdsm will support some other plugin types, for example 
> Ryu, in the future?
Yes. The end goal is that Quantum supports all plugin types. In the POC 
I just implemented the LinuxBridge and OVS plugins. Please see the to #3 
to get more details.
>
> 3) I saw a information in archive mail list, the oVirt will run Linux 
> bridge and OVS side by side. It decided by user want to use which one 
> to manage their network, but i don't know how they can work together? 
> For example:  There are two hosts (Host A and Host B), and each host 
> run two VMs (vm1 vm2 in Host A, and vm3 vm4 in Host B), the vm1 and 
> vm3 belong to tenant A, and vm2 and vm4 belong to tenant B, then how 
> to setup the connectivity? Like this?
This is something that we have discussed quite a lot in the past and 
present. This has led to a large amount of confusion and debate.
I think that we should limit this to one quantum agent per host (please 
note that the Quantum service currently supports only one plugin). When 
VDSM is registered with oVirt in addition to providing the HOST details 
(IP, root password etc), the user should also provide the plugin agent 
that should be supported by VDSM. This will enable VDSM to install the 
agent. configure the agent settings, etc. This render the 'q_plugin' 
field redundant (this can still be used to ensure consistency between 
VDSM and oVirt).
>
>
> Inline image 1
>
>
> Thanks in advanced,
> Kris

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120612/b30d6f38/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 16105 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120612/b30d6f38/attachment.png>

From iheim at redhat.com  Tue Jun 12 09:36:36 2012
From: iheim at redhat.com (Itamar Heim)
Date: Tue, 12 Jun 2012 12:36:36 +0300
Subject: [oVirt][Quantum] question about quantum CLI
In-Reply-To: <4FD7022F.2040600@redhat.com>
References: <CAAskrmH2rXN_nbnoBqkyWHj_mEWNNMhZm-AwcRauJ558nfnobw@mail.gmail.com>
	<4FD7022F.2040600@redhat.com>
Message-ID: <4FD70DA4.5000602@redhat.com>

On 06/12/2012 11:47 AM, Gary Kotton wrote:
> Hi Kris,
> Thanks for the questions. Please see my inline answers. I have also
> cc'ed the ovirt arch mailing list.
> Thanks
> Gary
>
> On 06/12/2012 11:21 AM, Kris zhang wrote:
>> Hi Gkotton,
>>
>> I have some questions:
>>
>> 1) In the file "ovirt.sh", i found the command quantum always use the
>> tenant "default", so if the ovirt don't support multi-tenant?
> oVirt does not support multi tenancy at the moment. Maybe there are
> people on the list who can provide more details about this. The initial
> plan was to use the "default" tenant.

ovirt supports multiple users and an RBAC model for permissions between 
these users.
what exactly are you looking for?


From gkotton at redhat.com  Tue Jun 12 11:15:20 2012
From: gkotton at redhat.com (Gary Kotton)
Date: Tue, 12 Jun 2012 14:15:20 +0300
Subject: [oVirt][Quantum] question about quantum CLI
In-Reply-To: <4FD70DA4.5000602@redhat.com>
References: <CAAskrmH2rXN_nbnoBqkyWHj_mEWNNMhZm-AwcRauJ558nfnobw@mail.gmail.com>
	<4FD7022F.2040600@redhat.com> <4FD70DA4.5000602@redhat.com>
Message-ID: <4FD724C8.8060506@redhat.com>

On 06/12/2012 12:36 PM, Itamar Heim wrote:
> On 06/12/2012 11:47 AM, Gary Kotton wrote:
>> Hi Kris,
>> Thanks for the questions. Please see my inline answers. I have also
>> cc'ed the ovirt arch mailing list.
>> Thanks
>> Gary
>>
>> On 06/12/2012 11:21 AM, Kris zhang wrote:
>>> Hi Gkotton,
>>>
>>> I have some questions:
>>>
>>> 1) In the file "ovirt.sh", i found the command quantum always use the
>>> tenant "default", so if the ovirt don't support multi-tenant?
>> oVirt does not support multi tenancy at the moment. Maybe there are
>> people on the list who can provide more details about this. The initial
>> plan was to use the "default" tenant.
>
> ovirt supports multiple users and an RBAC model for permissions 
> between these users.
> what exactly are you looking for?
Quantum support multi tenancy. The integration with oVirt was done with 
the "default" tenant. This is a different model to that of oVirt.
Thanks
Gary


From robert at middleswarth.net  Tue Jun 12 20:53:47 2012
From: robert at middleswarth.net (Robert Middleswarth)
Date: Tue, 12 Jun 2012 16:53:47 -0400
Subject: Call For Agenda Items -- oVirt Weekly Sync 2012-06-13
In-Reply-To: <1339425393.13637.33.camel@beelzebub.mburnsfire.net>
References: <1339422379.13637.25.camel@beelzebub.mburnsfire.net>
	<4FD60113.2060409@redhat.com>
	<1339425393.13637.33.camel@beelzebub.mburnsfire.net>
Message-ID: <4FD7AC5B.1030908@middleswarth.net>

I added to the wiki and item about testing day.  According to someone on 
IRC it is Thursday.  From what I have seen there is a lot of stuff still 
up in the air for testing day.

Thanks
Robert

On 06/11/2012 10:36 AM, Mike Burns wrote:
> On Mon, 2012-06-11 at 16:30 +0200, Dave Neary wrote:
>> Hi,
>>
>> On 06/11/2012 03:46 PM, Mike Burns wrote:
>>> This is the agenda for the 2012-06-13 meeting:
>>>
>>>         * Status of Next Release
>>>         * Sub-project reports (engine, vdsm, node)
>>>         * Upcoming workshops
>>>
>>> Any other topics to discuss?
>> I'd like to attend and discuss how the OSAS team inside RedHat can help
>> oVirt - I have been working with Itamar and others to put something
>> together, and I think it would be great to get more input on what we
>> have so far. Would that be appropriate for the meeting?
>>
>> Thanks,
>> Dave.
>>
> Sure, I'll add it to the agenda.  Please be available on Wednesday at
> 14:00 UTC (10:00 EDT) to lead this discussion.
>
> Thanks
>
> Mike
>
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch



From gkotton at redhat.com  Wed Jun 13 06:02:15 2012
From: gkotton at redhat.com (Gary Kotton)
Date: Wed, 13 Jun 2012 09:02:15 +0300
Subject: [oVirt][Quantum] question about quantum CLI
In-Reply-To: <CAAskrmHB61c+X+P39za85nQndN3j6YZ8O7uqX=p5TeQiOUmWCQ@mail.gmail.com>
References: <CAAskrmH2rXN_nbnoBqkyWHj_mEWNNMhZm-AwcRauJ558nfnobw@mail.gmail.com>	<4FD7022F.2040600@redhat.com>	<4FD70DA4.5000602@redhat.com>	<4FD724C8.8060506@redhat.com>
	<CAAskrmHB61c+X+P39za85nQndN3j6YZ8O7uqX=p5TeQiOUmWCQ@mail.gmail.com>
Message-ID: <4FD82CE7.8090401@redhat.com>

Hi Kris,
Please see my answers and questions below.
Thanks
Gary

On 06/13/2012 07:31 AM, Kris zhang wrote:
> Hi Kotton,
>
> In the file ovirt.sh, there is a line:

A bit of background regarding the script. The purpose of the POC was to 
show that Quantum can be run in oVirt. It would have been ideal to write 
a REST client that could interface with the Quantum service. Due to the 
fact that I was not familiar with the oVirt code I felt that a quicker 
and more productive means was to invoke a bash script from the oVirt 
engine code. The script would invoke the quantum cli (this is a client 
that configures the quantum server). In addition to this I did not want 
to make any changes to the database schema. The result was a script that 
does the following:
1. Logical Network Management:
     Create:
         ovirt.sh network create <name>
             - the name is the name of the logical network (in the POC 
this is prefixed by "Q_"
             - this invokes the cli to create a network called <name>
             - the UUID returned by the quantum service will be save in 
/tmp/network.<name>
             - the above UUID is read when this logical network is used 
(this in the future will be save in the oVirt data base)
     Delete:
         ovirt.sh network remove <name>
             - the name is the name of the logical network (in the POC 
this is prefixed by "Q_"
             - this invokes the cli to delete a network called <name>
             - the file /tmp/network.<name> is deleted
2. VM Port management
     Create:
         ovirt.sh port create <net_name> <vmid>
             - the network name and the vm id are input (the VM id is a 
key to be able to delete it all :))
             - the script does the following:
                 - creates a port on the network. saves the port id in 
/tmp/network.<name>.<vmid>.port
                 - sets the state of the port to ACTIVE
                 - creates an attachment ID (this is the line that you 
had problems with). This is saved in /tmp/network.<name>.<vmid>.attachment
                 - saves the network name in a file /tmp/network.<vmid>
                 - the UUID's are read when the VM is started so that 
they can be passed to VDSM
     Delete:
         ovirt.sh port remove <vmid>
             - using the vmid the network name is read => enables us to 
get all of the ID's to delete port in quantum
             - cleans all of the files
The script is called from the ovirt engine. Sorry for the long winded 
explanation.

> quantum update_port default $NET_UUID $PORT_UUID state=ACTIVE
>                 uuidgen > /tmp/network.$3.$4.port.attach
> ATTACH_UUID=`cat /tmp/network.$3.$4.port.attach`

In Quantum the attachment ID is generated by the user. The code above 
generates the attachment ID for the port.
>
>
> But i run this command, i found there is no any uuid generated, so 
> what's the value of the ATTACH_UUID?
Do you run the script from the shell or is this run via oVirt?
There is a log of all of the script command - can you please look in 
/tmp/ovirt.txt - this may give us some clues.
You can run the script commands as described above. This may also help.
Thanks
Gary
> Best regards,
> Kris
>
>
> On Tue, Jun 12, 2012 at 7:15 PM, Gary Kotton <gkotton at redhat.com 
> <mailto:gkotton at redhat.com>> wrote:
>
>     On 06/12/2012 12:36 PM, Itamar Heim wrote:
>
>         On 06/12/2012 11:47 AM, Gary Kotton wrote:
>
>             Hi Kris,
>             Thanks for the questions. Please see my inline answers. I
>             have also
>             cc'ed the ovirt arch mailing list.
>             Thanks
>             Gary
>
>             On 06/12/2012 11:21 AM, Kris zhang wrote:
>
>                 Hi Gkotton,
>
>                 I have some questions:
>
>                 1) In the file "ovirt.sh", i found the command quantum
>                 always use the
>                 tenant "default", so if the ovirt don't support
>                 multi-tenant?
>
>             oVirt does not support multi tenancy at the moment. Maybe
>             there are
>             people on the list who can provide more details about
>             this. The initial
>             plan was to use the "default" tenant.
>
>
>         ovirt supports multiple users and an RBAC model for
>         permissions between these users.
>         what exactly are you looking for?
>
>     Quantum support multi tenancy. The integration with oVirt was done
>     with the "default" tenant. This is a different model to that of oVirt.
>     Thanks
>     Gary
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120613/b3f6f7da/attachment.html>

From gkotton at redhat.com  Wed Jun 13 09:48:00 2012
From: gkotton at redhat.com (Gary Kotton)
Date: Wed, 13 Jun 2012 12:48:00 +0300
Subject: [oVirt][Quantum] question about quantum CLI
In-Reply-To: <CAAskrmHHuc8E-sjddLM+sDkh2svszbNUa9L07ttNthjdzU3PJQ@mail.gmail.com>
References: <CAAskrmH2rXN_nbnoBqkyWHj_mEWNNMhZm-AwcRauJ558nfnobw@mail.gmail.com>	<4FD7022F.2040600@redhat.com>	<4FD70DA4.5000602@redhat.com>	<4FD724C8.8060506@redhat.com>	<CAAskrmHB61c+X+P39za85nQndN3j6YZ8O7uqX=p5TeQiOUmWCQ@mail.gmail.com>	<4FD82CE7.8090401@redhat.com>
	<CAAskrmHHuc8E-sjddLM+sDkh2svszbNUa9L07ttNthjdzU3PJQ@mail.gmail.com>
Message-ID: <4FD861D0.3010902@redhat.com>

On 06/13/2012 11:57 AM, Kris zhang wrote:
> Thanks for you detail answer, and please see the result of the command 
> quantum update_port,
The command "quantum update_port" sets the state of the port. In the 
case of the ovirt.sh script this sets the port in ACTIVE state.
The "user" is responsible for providing the attachment ID. In the case 
of the ovirt.sh script the ID is generated via uuidgen.
Once you have generated a UUID for the attachment you need to pass this 
to quantum via the "quantum plug_iface".
>
> Inline image 1
>
> I run this script from the shell, and you can see there is no an 
> attachment UUID created. Can you show me your testing result?

Please see below:

openstack at openstack:/tmp$ ./ovirt.sh network create Q_net
openstack at openstack:/tmp$ ./ovirt.sh port create Q_net 12345678
Updated Logical Port with ID: f9f203ab-dab6-4b9c-8dcf-561bcc698c76
on Virtual Network: 8c50db01-54ef-4688-a274-9ab3fcfafe7d
for tenant: default
Plugged interface 24bf26c4-f8eb-46cd-a168-b7a25e64d5b2
into Logical Port: f9f203ab-dab6-4b9c-8dcf-561bcc698c76
on Virtual Network: 8c50db01-54ef-4688-a274-9ab3fcfafe7d
for Tenant: default
openstack at openstack:/tmp$


openstack at openstack:/tmp$ ll
total 40
drwxrwxrwt  4 root      root      4096 2012-06-13 05:39 ./
drwxr-xr-x 23 root      root      4096 2012-05-26 06:39 ../
-rw-rw-r--  1 openstack openstack    6 2012-06-13 05:38 network.12345678
-rw-rw-r--  1 openstack openstack   37 2012-06-13 05:38 network.Q_net
-rw-rw-r--  1 openstack openstack   37 2012-06-13 05:38 
network.Q_net.12345678.port
-rw-rw-r--  1 openstack openstack   37 2012-06-13 05:38 
network.Q_net.12345678.port.attach
-rwxrwxrwx  1 openstack openstack 2097 2012-06-13 05:07 ovirt.sh*
-rw-rw-r--  1 openstack openstack 1797 2012-06-13 05:38 ovirt.txt

openstack at openstack:/tmp$ cat network.Q_net.12345678.port.attach
24bf26c4-f8eb-46cd-a168-b7a25e64d5b2
openstack at openstack:/tmp$

Thanks
Gary
>
> BR,
> Kris
>
>
> On Wed, Jun 13, 2012 at 2:02 PM, Gary Kotton <gkotton at redhat.com 
> <mailto:gkotton at redhat.com>> wrote:
>
>     Hi Kris,
>     Please see my answers and questions below.
>     Thanks
>     Gary
>
>
>     On 06/13/2012 07:31 AM, Kris zhang wrote:
>>     Hi Kotton,
>>
>>     In the file ovirt.sh, there is a line:
>
>     A bit of background regarding the script. The purpose of the POC
>     was to show that Quantum can be run in oVirt. It would have been
>     ideal to write a REST client that could interface with the Quantum
>     service. Due to the fact that I was not familiar with the oVirt
>     code I felt that a quicker and more productive means was to invoke
>     a bash script from the oVirt engine code. The script would invoke
>     the quantum cli (this is a client that configures the quantum
>     server). In addition to this I did not want to make any changes to
>     the database schema. The result was a script that does the following:
>     1. Logical Network Management:
>         Create:
>             ovirt.sh network create <name>
>                 - the name is the name of the logical network (in the
>     POC this is prefixed by "Q_"
>                 - this invokes the cli to create a network called <name>
>                 - the UUID returned by the quantum service will be
>     save in /tmp/network.<name>
>                 - the above UUID is read when this logical network is
>     used (this in the future will be save in the oVirt data base)
>         Delete:
>             ovirt.sh network remove <name>
>                 - the name is the name of the logical network (in the
>     POC this is prefixed by "Q_"
>                 - this invokes the cli to delete a network called <name>
>                 - the file /tmp/network.<name> is deleted
>     2. VM Port management
>         Create:
>             ovirt.sh port create <net_name> <vmid>
>                 - the network name and the vm id are input (the VM id
>     is a key to be able to delete it all :))
>                 - the script does the following:
>                     - creates a port on the network. saves the port id
>     in /tmp/network.<name>.<vmid>.port
>                     - sets the state of the port to ACTIVE
>                     - creates an attachment ID (this is the line that
>     you had problems with). This is saved in
>     /tmp/network.<name>.<vmid>.attachment
>                     - saves the network name in a file /tmp/network.<vmid>
>                     - the UUID's are read when the VM is started so
>     that they can be passed to VDSM
>         Delete:
>             ovirt.sh port remove <vmid>
>                 - using the vmid the network name is read => enables
>     us to get all of the ID's to delete port in quantum
>                 - cleans all of the files
>     The script is called from the ovirt engine. Sorry for the long
>     winded explanation.
>
>
>>     quantum update_port default $NET_UUID $PORT_UUID state=ACTIVE
>>                     uuidgen > /tmp/network.$3.$4.port.attach
>>     ATTACH_UUID=`cat /tmp/network.$3.$4.port.attach`
>
>     In Quantum the attachment ID is generated by the user. The code
>     above generates the attachment ID for the port.
>>
>>
>>     But i run this command, i found there is no any uuid generated,
>>     so what's the value of the ATTACH_UUID?
>     Do you run the script from the shell or is this run via oVirt?
>     There is a log of all of the script command - can you please look
>     in /tmp/ovirt.txt - this may give us some clues.
>     You can run the script commands as described above. This may also
>     help.
>     Thanks
>     Gary
>
>>     Best regards,
>>     Kris
>>
>>
>>     On Tue, Jun 12, 2012 at 7:15 PM, Gary Kotton <gkotton at redhat.com
>>     <mailto:gkotton at redhat.com>> wrote:
>>
>>         On 06/12/2012 12:36 PM, Itamar Heim wrote:
>>
>>             On 06/12/2012 11:47 AM, Gary Kotton wrote:
>>
>>                 Hi Kris,
>>                 Thanks for the questions. Please see my inline
>>                 answers. I have also
>>                 cc'ed the ovirt arch mailing list.
>>                 Thanks
>>                 Gary
>>
>>                 On 06/12/2012 11:21 AM, Kris zhang wrote:
>>
>>                     Hi Gkotton,
>>
>>                     I have some questions:
>>
>>                     1) In the file "ovirt.sh", i found the command
>>                     quantum always use the
>>                     tenant "default", so if the ovirt don't support
>>                     multi-tenant?
>>
>>                 oVirt does not support multi tenancy at the moment.
>>                 Maybe there are
>>                 people on the list who can provide more details about
>>                 this. The initial
>>                 plan was to use the "default" tenant.
>>
>>
>>             ovirt supports multiple users and an RBAC model for
>>             permissions between these users.
>>             what exactly are you looking for?
>>
>>         Quantum support multi tenancy. The integration with oVirt was
>>         done with the "default" tenant. This is a different model to
>>         that of oVirt.
>>         Thanks
>>         Gary
>>
>>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120613/382af09e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 53568 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120613/382af09e/attachment.png>

From dneary at redhat.com  Wed Jun 13 14:28:00 2012
From: dneary at redhat.com (Dave Neary)
Date: Wed, 13 Jun 2012 16:28:00 +0200
Subject: What are you looking for from oVirt?
Message-ID: <4FD8A370.3010904@redhat.com>

Hi everyone,

That is a grand subject for my first "proper" email to the Users list, 
and it definitely needs some context! So let me introduce myself.

My name is Dave Neary, and I recently started working for a group which 
is being formed inside Red Hat called OSAS (open source and standards). 
The role of my group is to help make any open source projects that Red 
Hat works in successful, and I would really like to help take oVirt to 
the next level in terms of adoption and contribution.

One of the things I'm still figuring out is what the natural audience 
for oVirt is, and what you all like about oVirt, and would like to see 
improved. Based on that, I would like to propose areas we as a community 
can concentrate on related to the product, the website, and our 
marketing and promotion, but the first step is still to get a better 
idea what the target audience for oVirt is, and should be.

So - how are you using oVirt? Why did you choose it over alternatives? 
What do you like about it? and what would you like to see change, 
whether that is in terms of technical, process, or marketing changes? 
I'm here to help, but to do so I need your help first!

Please feel free to reply to me on-list (if you'd like to start 
discussion) or off-list (if you'd like your feedback to be more 
discrete). Any feedback at all will be helpful.

Thank you very much - I look forward to hearing from as many of you as 
possible.

Regards,
Dave.

PS. I'm still figuring out proper mailing list etiquette for this 
project - I've added board@ and arch@ to CC since I expect our work to 
have project-wide consequences, but it's more to keep people informed at 
this point. Please let me know off-list if I'm doing something I shouldn't!

-- 
Dave Neary
Community Action and Impact
Open Source and Standards Team, Red Hat
Phone: +33 9 50 71 55 62


From kwade at redhat.com  Wed Jun 13 14:48:29 2012
From: kwade at redhat.com (Karsten 'quaid' Wade)
Date: Wed, 13 Jun 2012 07:48:29 -0700
Subject: What are you looking for from oVirt?
In-Reply-To: <4FD8A370.3010904@redhat.com>
References: <4FD8A370.3010904@redhat.com>
Message-ID: <4FD8A83D.8030109@redhat.com>

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

On 06/13/2012 07:28 AM, Dave Neary wrote:
> 
> My name is Dave Neary, and I recently started working for a group
> which is being formed inside Red Hat called OSAS (open source and
> standards). The role of my group is to help make any open source
> projects that Red Hat works in successful, and I would really like
> to help take oVirt to the next level in terms of adoption and
> contribution.

Just some context for folks - OSAS is the team that I work on with
other people you've seen around oVirt: Leslie Hawthorn, Carl Trieloff,
Jim Jagielski, and Jason Brooks. (You'll likely see others of us, such
as Garrett LeSage, as we all work on upstream projects together.)
Helping with the open sourcing and community growth of oVirt is really
the first project the OSAS team worked on together.

To quote Dave:

07:43 < dneary> We're basically the A-Team for community stuff
07:44 < dneary> Except our theme music isn't as cool

Cheers - Karsten
- --
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/

iD8DBQFP2Kg92ZIOBq0ODEERAkqZAKDC6RwtSiboq14hb1T7KrHm7YOFTwCglzzf
OvLipZfZGgfgNabGCW+zkEk=
=pY6R
-----END PGP SIGNATURE-----


From mburns at redhat.com  Wed Jun 13 15:17:48 2012
From: mburns at redhat.com (Mike Burns)
Date: Wed, 13 Jun 2012 11:17:48 -0400
Subject: oVirt Weekly Meeting Minutes -- 2012-06-13
Message-ID: <1339600668.3499.0.camel@beelzebub.mburnsfire.net>

Minutes:        http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-13-14.01.html
Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-13-14.01.txt
Log:            http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-13-14.01.log.html

=========================
#ovirt: ovirt weekly sync
=========================


Meeting started by mburns at 14:01:14 UTC. The full logs are available
at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-13-14.01.log.html
.



Meeting summary
---------------
* roll call and agenda  (mburns, 14:01:26)

* Status for next release  (mburns, 14:03:56)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=822145   (mburns,
    14:05:29)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=824397   (mburns,
    14:06:14)
  * status:  Modified  (mburns, 14:06:20)
  * in latest beta rpms  (mburns, 14:08:00)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=824420   (mburns,
    14:08:22)
  * very close to completion on this bug, one issue still remaining,
    then build and post  (mburns, 14:08:51)
  * engine will rebase to latest and rebuild  (mburns, 14:11:45)
  * new packages to mburns before EOD  (mburns, 14:11:55)
  * ovirt-node will try to post something for tomorrow  (mburns,
    14:12:25)
  * vdsm 4.10.0 built and will be posted today to beta area  (mburns,
    14:15:33)
  * ACTION: mburns to update when packages are posted to beta area
    (mburns, 14:16:32)
  * ACTION: mgoldboi to coordinate rpms for engine, clie, sdk, vdsm,
    guest-agent and send details of locations to mburns  (mburns,
    14:20:59)
  * ACTION: to post rpms to beta and send announcement  (mburns,
    14:21:12)

* test day  (mburns, 14:24:29)
  * community coordination for test day  (mburns, 14:35:38)
  * each sub-project will have someone helping  (mburns, 14:35:50)
  * ykaul will do cleanup of test day page  (mburns, 14:36:00)
  * all issues should be track on the test day wiki  (mburns, 14:36:12)
  * LINK: http://ovirt.org/wiki/Testing/OvirtTestDay   (mburns,
    14:36:57)

* Workshops  (mburns, 14:37:29)
  * LinuxCon Japan workshop help on Friday 8-June  (mburns, 14:39:15)
  * post-mortem to be done next week for LC Japan  (mburns, 14:39:43)
  * will need input from everyone on agenda for LC North America in
    August  (mburns, 14:40:08)

* How can OSAS team help?  (mburns, 14:42:17)
  * OSAS == Open Source and Standards  (mburns, 14:42:42)

* infra team as a sub-project  (mburns, 14:57:31)
  * LINK:
    http://blog.wikimedia.org/2011/09/19/ever-wondered-how-the-wikimedia-servers-are-configured/
    might be interesting in that regard  (ewoud, 15:14:02)

Meeting ended at 15:16:06 UTC.




Action Items
------------
* mburns to update when packages are posted to beta area
* mgoldboi to coordinate rpms for engine, clie, sdk, vdsm, guest-agent
  and send details of locations to mburns
* to post rpms to beta and send announcement




Action Items, by person
-----------------------
* mburns
  * mburns to update when packages are posted to beta area
  * mgoldboi to coordinate rpms for engine, clie, sdk, vdsm, guest-agent
    and send details of locations to mburns
* mgoldboi
  * mgoldboi to coordinate rpms for engine, clie, sdk, vdsm, guest-agent
    and send details of locations to mburns
* **UNASSIGNED**
  * to post rpms to beta and send announcement




People Present (lines said)
---------------------------
* mburns (146)
* dneary (51)
* RobertM (23)
* aglitke (22)
* mgoldboi (13)
* lh (9)
* itamar1 (9)
* ewoud (7)
* mpastern (7)
* ovirtbot (7)
* ykaul (6)
* rharper (5)
* sgordon (3)
* lpeer (3)
* garrett (3)
* quaid (2)
* danken (2)
* coredumb (2)
* rickyh (1)
* Guest3690 (1)
* ofrenkel (1)
* jb_netapp (1)




Generated by `MeetBot`_ 0.1.4

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



From acathrow at redhat.com  Wed Jun 13 15:33:30 2012
From: acathrow at redhat.com (Andrew Cathrow)
Date: Wed, 13 Jun 2012 11:33:30 -0400 (EDT)
Subject: [Users] What are you looking for from oVirt?
In-Reply-To: <alpine.LFD.2.02.1206131022360.14212@bart.robotics.net>
Message-ID: <4be4bce7-c983-4bbe-9841-1c0f2cf095b9@zmail07.collab.prod.int.phx2.redhat.com>



----- Original Message -----
> From: "Nathan Stratton" <nathan at robotics.net>
> To: "Dave Neary" <dneary at redhat.com>
> Cc: "arch" <arch at ovirt.org>, "Users" <users at ovirt.org>, "board" <board at ovirt.org>
> Sent: Wednesday, June 13, 2012 11:29:38 AM
> Subject: Re: [Users] What are you looking for from oVirt?
> 
> On Wed, 13 Jun 2012, Dave Neary wrote:
> 
> > So - how are you using oVirt? Why did you choose it over
> > alternatives? What
> > do you like about it? and what would you like to see change,
> > whether that is
> > in terms of technical, process, or marketing changes? I'm here to
> > help, but
> > to do so I need your help first!
> 
> Small private cloud deployments. We choose it because it was focused
> on
> KVM, RedHat driven, simple to manage, and libvirt based. Would love

What does your deployment look like - it's be great to understand how you're using it - eg. Linux guests only, Windows, size of deployment - do your users use poweruser portal etc.

> to see
> real glusterfs integration, quantum integration, and better API.

GlusterFS and Quantum are certainly in the works, but in a separate thread I'd love to hear feedback on the API what the issues/enhancements are.
Would you be able to post some initial comments on that?

thanks
Aic


> 
> ><>
> Nathan Stratton
> nathan at robotics.net
> http://www.robotics.net
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 


From acathrow at redhat.com  Wed Jun 13 18:27:02 2012
From: acathrow at redhat.com (Andrew Cathrow)
Date: Wed, 13 Jun 2012 14:27:02 -0400 (EDT)
Subject: [Users] What are you looking for from oVirt?
In-Reply-To: <alpine.LFD.2.02.1206131034060.18569@bart.robotics.net>
Message-ID: <ec58b1f7-8814-4c59-a686-9b309b59693c@zmail07.collab.prod.int.phx2.redhat.com>



----- Original Message -----
> From: "Nathan Stratton" <nathan at robotics.net>
> To: "Andrew Cathrow" <acathrow at redhat.com>
> Cc: "arch" <arch at ovirt.org>, "Users" <users at ovirt.org>, "board" <board at ovirt.org>, "Dave Neary" <dneary at redhat.com>
> Sent: Wednesday, June 13, 2012 11:57:35 AM
> Subject: Re: [Users] What are you looking for from oVirt?
> 
> On Wed, 13 Jun 2012, Andrew Cathrow wrote:
> 
> > What does your deployment look like - it's be great to understand
> > how you're using it - eg. Linux guests only, Windows, size of
> > deployment - do your users use poweruser portal etc.
> 
> I have 2 deployments I am working on with two different companies.
> 
> The first is two clusters (SJC and NYC) each with 20 boxes PXEBooted
> to
> a backend NetApp. All guests are Linux (Centos, RHEL, and Fedora).
> One of
> the unique things with the clusters is they use read only linux and
> NFS
> root.
> 
> The 2nd is still in design stage, but is starting out with 3 clusters
> (East / West US and Europe) each with 20 boxes. Each server is based
> on
> white label Xeon E5-2687W, 128GB RAM, 10GBase-T, and 12 SATA disks on
> a
> hardware RAID 6 controller. This is also going to use shared NFS read
> only
> root with PXEBoot from NetApps.
> 
> I have been running GlusterFS on and off for 5 years and are looking
> at
> running GlusterFS on all the raw 300TB RAID6 in each server. Each
> server
> will be a brick, two servers with distribute for redundancy, 10
> distribute pairs then will be unified. I have been trying to use this
> for
> raw image store for years, but its just not ready, so we will use
> NetApp
> for that, however GlusterFS will be very handy for tier 2 bulk
> storage.
> 
> > GlusterFS and Quantum are certainly in the works, but in a separate
> > thread I'd love to hear feedback on the API what the
> > issues/enhancements are.
> > Would you be able to post some initial comments on that?
> 
> APIs are great today on the backend, we are looking at the ability to
> modify the front end so we can tie it into our portal allowing users
> to
> manage their VMs seamless with the other services we offer.

So are you looking to extend the power user portal or something more?



> 
> ><>
> Nathan Stratton
> nathan at robotics.net
> http://www.robotics.net
> 


From mburns at redhat.com  Wed Jun 13 21:10:02 2012
From: mburns at redhat.com (Mike Burns)
Date: Wed, 13 Jun 2012 17:10:02 -0400
Subject: Test Day rpms uploaded (partially)
Message-ID: <1339621802.3499.11.camel@beelzebub.mburnsfire.net>

RPMs for vdsm and ovirt-engine have been uploaded to ovirt.org.  Some of
the various tools have not been updated yet, but are coming.

Ready:

ovirt-engine
vdsm

RPMs exist but will likely be updated:
log-collector
iso-uploader
image-uploader
ovirt-engine-cli
ovirt-engine-sdk

RPMs not posted yet:
ovirt-node
ovirt-guest-agent

As new RPMs get uploaded, I will send additional updates.

Thanks

Mike



From mburns at redhat.com  Wed Jun 13 21:11:59 2012
From: mburns at redhat.com (Mike Burns)
Date: Wed, 13 Jun 2012 17:11:59 -0400
Subject: Test Day rpms uploaded (partially)
In-Reply-To: <1339621802.3499.11.camel@beelzebub.mburnsfire.net>
References: <1339621802.3499.11.camel@beelzebub.mburnsfire.net>
Message-ID: <1339621919.3499.12.camel@beelzebub.mburnsfire.net>

Helps if I give the repo definition:

[ovirt-beta]
name=Nightly builds of the oVirt project
baseurl=http://ovirt.org/releases/beta/fedora/$releasever/
enabled=0
skip_if_unavailable=1
gpgcheck=0


On Wed, 2012-06-13 at 17:10 -0400, Mike Burns wrote:
> RPMs for vdsm and ovirt-engine have been uploaded to ovirt.org.  Some of
> the various tools have not been updated yet, but are coming.
> 
> Ready:
> 
> ovirt-engine
> vdsm
> 
> RPMs exist but will likely be updated:
> log-collector
> iso-uploader
> image-uploader
> ovirt-engine-cli
> ovirt-engine-sdk
> 
> RPMs not posted yet:
> ovirt-node
> ovirt-guest-agent
> 
> As new RPMs get uploaded, I will send additional updates.
> 
> Thanks
> 
> Mike
> 
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch




From mburns at redhat.com  Wed Jun 13 21:36:27 2012
From: mburns at redhat.com (Mike Burns)
Date: Wed, 13 Jun 2012 17:36:27 -0400
Subject: oVirt 3.1 Release Test Day
Message-ID: <1339623387.3499.23.camel@beelzebub.mburnsfire.net>

It's been pointed out to me that there has been a lack of communication
around the Test Day for the next oVirt Release.  I apologize for the
oversight that information hasn't been posted to these lists
previously.  

When is the test day?

Thursday 2012-06-14

Where can you find info on the test day?

http://ovirt.org/wiki/Testing/OvirtTestDay3.1

How can you help?

Download the bits (see separate mail for location and what's there).  
Install and play around in the environment.  
Report any issues seen to the IRC channel and/or mailing lists. 
Update the wiki page with results, info on your testing

What to do if you're unsure of something or stuck?

The main IRC channel (#ovirt on OFTC) should be staffed with people
paying extra attention.  If you're not getting a response, try pinging
someone there by name until you get a response.


If there are other questions, feel free to reply here or ask on IRC

Thanks

Mike



From lhawthor at redhat.com  Wed Jun 13 22:14:34 2012
From: lhawthor at redhat.com (Leslie Hawthorn)
Date: Wed, 13 Jun 2012 15:14:34 -0700
Subject: Following Up on LinuxCon Japan Workshop
Message-ID: <4FD910CA.1080808@redhat.com>

Hello everyone,

I'd like to collect feedback from everyone on last week's oVirt workshop 
at LinuxCon Japan. [0] Please reply back with comments by close of 
business this Friday, 15 June.

Once we have gathered feedback on list, I'll capture it on the oVirt 
wiki. We can then use what we've learned to help construct the agenda 
and other plans for other upcoming oVirt workshops at LinuxCons. [1]

If you know that you would like to volunteer as an instructor for future 
workshops or would like to suggest alternate content for the workshop, 
please include that in your feedback.

- Course Material
What sessions were most well received? Which ones require improvement? 
Any additional sessions we'd suggest?

- Audience Participation
How many attendees? How did the Q&A periods go? Would we like to prepare 
a post-event attendee survey? (I recommend we do the survey and can 
prepare some questions for the group if that's useful.)

- Developer/user traction resulting from engaging at workshop
Did this workshop help us to gain new developers or users? Reinforce 
relationships with existing community members?

- Promotion of the event, both before and after
What could be done to more effectively promote the event prior to the 
workshops? Videos and slides from the workshop should be posted on the 
LC Japan site tomorrow; what action would the community like to take to 
promote this content?

- A/V and Room Set up
Did the seating arrangements work well for the workshop format? Did the 
A/V work well, including the videotaping process?

- Food and beverage
Did the catered in lunch help to keep the flow of the workshop 
productive? Was the food of good quality and in keeping with the needs 
of attendee dietary constraints?

- Give aways
We did not produce attendee gifts for the oVirt workshop. Thoughts on 
whether this would be a welcome addition in the future? Suggestions for 
type of gift also welcome.

- Any other feedback

If it is preferable to discuss this feedback real-time, I will ask Mike 
Burns to give us more time for this topic during next week's oVirt IRC 
meeting.

[0] - 
https://events.linuxfoundation.org/events/linuxcon-japan/ovirt-gluster-workshops
[1] - http://www.ovirt.org/wiki/OVirt_Global_Workshops

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 Jun 13 23:41:29 2012
From: mburns at redhat.com (Mike Burns)
Date: Wed, 13 Jun 2012 19:41:29 -0400
Subject: [Users] Following Up on LinuxCon Japan Workshop
In-Reply-To: <4FD910CA.1080808@redhat.com>
References: <4FD910CA.1080808@redhat.com>
Message-ID: <1339630889.3499.47.camel@beelzebub.mburnsfire.net>

Hi Leslie,

On Wed, 2012-06-13 at 15:14 -0700, Leslie Hawthorn wrote:
> Hello everyone,
> 
> I'd like to collect feedback from everyone on last week's oVirt workshop 
> at LinuxCon Japan. [0] Please reply back with comments by close of 
> business this Friday, 15 June.
> 
> Once we have gathered feedback on list, I'll capture it on the oVirt 
> wiki. We can then use what we've learned to help construct the agenda 
> and other plans for other upcoming oVirt workshops at LinuxCons. [1]
> 
> If you know that you would like to volunteer as an instructor for future 
> workshops or would like to suggest alternate content for the workshop, 
> please include that in your feedback.
> 
> - Course Material
> What sessions were most well received? Which ones require improvement? 
> Any additional sessions we'd suggest?

All of the sessions seemed to be well received.  I don't know that any
need blatant improvement, though they could probably all take a bit of
slide updates.  The ovirt-node presentation was especially out of date
(my fault) with it's screenshots.  

> 
> - Audience Participation
> How many attendees? How did the Q&A periods go? Would we like to prepare 
> a post-event attendee survey? (I recommend we do the survey and can 
> prepare some questions for the group if that's useful.)

There were probably between 25-35 people through the course of the day
for all the presentations.  

There wasn't really a lot of time set aside for Q&A aside from a few
minutes at the end of each presentation and the breaks in between
presentations.  During those times, there generally were people asking
questions.

I think we should prepare the survey in advance of the next workshop and
ask people to fill it out during the workshop, rather than coming back a
couple weeks after the fact.  We didn't really collect names of the
people in attendance and I expect that a fair number of people
registered attended the Gluster Conference.

> 
> - Developer/user traction resulting from engaging at workshop
> Did this workshop help us to gain new developers or users? Reinforce 
> relationships with existing community members?

Only time will really tell here.  People definitely seemed interested
and there were a couple people already downloading and installing the
bits during the workshop.  I got the impression that most of the people
there were more corporate focused -- Hitachi and Fujitsu were both well
represented.  They're from companies that have previously expressed
interest in the project.  

> 
> - Promotion of the event, both before and after
> What could be done to more effectively promote the event prior to the 
> workshops? Videos and slides from the workshop should be posted on the 
> LC Japan site tomorrow; what action would the community like to take to 
> promote this content?

Not really my area of expertise -- promoting.  Probably better to get
information out there earlier that the workshop is happening.  It seemed
to be a bit of a fire drill getting things together for this workshop
since it was only about a month before that we decided to run it.
Future workshops shouldn't be as big a deal.

Probably an email announcement to users@ with a link to the
presentations/videos is the right next step.
> 
> - A/V and Room Set up
> Did the seating arrangements work well for the workshop format? Did the 
> A/V work well, including the videotaping process?

Our room was setup with 5 round tables seating 10 people each.  I'm not
sure that it was really the right layout.  I expected either rows of
chairs or long tables with chairs all facing the presentation screen.

A/V worked seamlessly.  It was all setup already when we arrived.  

> 
> - Food and beverage
> Did the catered in lunch help to keep the flow of the workshop 
> productive? Was the food of good quality and in keeping with the needs 
> of attendee dietary constraints?

I had no issues with the food.  People seemed to take the opportunity
more to step out and take a break, rather than sit and continue
discussing.  

> 
> - Give aways
> We did not produce attendee gifts for the oVirt workshop. Thoughts on 
> whether this would be a welcome addition in the future? Suggestions for 
> type of gift also welcome.

It would have been nice to have some sort of SWAG to give away, whether
just fancy handouts or stickers.  It would be even better if we could
have some sort of appliance with ovirt pre-installed and configured on a
usb stick as well, but that's probably a year or 2 down the road.

> 
> - Any other feedback

It's probably better if there are people from a wider range of the
sub-projects than we had in Japan.  I think that between Barak and I, we
managed to cover the majority of the project, but I think it would be
better to have someone from each major subproject there.  

I expect that either myself or someone from the Node team will be
attending at least LinuxCon NA, LinuxCon Europe and the NetApp
workshops.  We'll certainly handle the Node presentation for each of
these workshops.

Mike

> 
> If it is preferable to discuss this feedback real-time, I will ask Mike 
> Burns to give us more time for this topic during next week's oVirt IRC 
> meeting.
> 
> [0] - 
> https://events.linuxfoundation.org/events/linuxcon-japan/ovirt-gluster-workshops
> [1] - http://www.ovirt.org/wiki/OVirt_Global_Workshops
> 
> Cheers,
> LH
> 




From kwade at redhat.com  Thu Jun 14 00:17:14 2012
From: kwade at redhat.com (Karsten 'quaid' Wade)
Date: Wed, 13 Jun 2012 17:17:14 -0700
Subject: [Users] Following Up on LinuxCon Japan Workshop
In-Reply-To: <1339630889.3499.47.camel@beelzebub.mburnsfire.net>
References: <4FD910CA.1080808@redhat.com>
	<1339630889.3499.47.camel@beelzebub.mburnsfire.net>
Message-ID: <4FD92D8A.6040602@redhat.com>

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

On 06/13/2012 04:41 PM, Mike Burns wrote:

> Our room was setup with 5 round tables seating 10 people each.  I'm
> not sure that it was really the right layout.  I expected either
> rows of chairs or long tables with chairs all facing the
> presentation screen.

I'd like to hear more about what didn't work or could have improved
with this setup. It sounds similar to a setup Leslie, Jason, and I
looked at for a workshop at NetApp next year. At the time, it seemed
like a fairly ideal setup in some ways - everyone can view the
presenter but things are less classroom-like and more communal. (IIRC,
the setup there includes a few additional siderooms setup as long
tables and chairs facing one end of the room.)

- - Karsten
- -- 
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/

iD8DBQFP2S2K2ZIOBq0ODEERAl/pAJ9B6j4CT+EB0tm58/fNi/uaAJ1OMQCg5lNk
TnjBhI3N9Qz3sKt+33fQXkg=
=jfvY
-----END PGP SIGNATURE-----


From lhawthor at redhat.com  Thu Jun 14 06:59:57 2012
From: lhawthor at redhat.com (Leslie Hawthorn)
Date: Wed, 13 Jun 2012 23:59:57 -0700
Subject: [Users] Following Up on LinuxCon Japan Workshop
In-Reply-To: <1339630889.3499.47.camel@beelzebub.mburnsfire.net>
References: <4FD910CA.1080808@redhat.com>
	<1339630889.3499.47.camel@beelzebub.mburnsfire.net>
Message-ID: <4FD98BED.9090004@redhat.com>

Hi Mike,

Thanks for your detailed feedback.

On 06/13/2012 04:41 PM, Mike Burns wrote:
> - Audience Participation
> How many attendees? How did the Q&A periods go? Would we like to prepare
> a post-event attendee survey? (I recommend we do the survey and can
> prepare some questions for the group if that's useful.)
> I think we should prepare the survey in advance of the next workshop and
> ask people to fill it out during the workshop, rather than coming back a
> couple weeks after the fact.
I have an attendee list from the Linux Foundation for each workshop, so 
if we'd like to get the survey out this week it can happen. I believe I 
can also find a resource to translate the survey into Japanese, though 
that would mean a delay in sending it out.

Some suggested questions, I'd pare down to no more than 5.
- What was your favorite talk?
- What could we do to improve?
- Were the talks too long? Too short?
- Was the presentation material clear to you?
- Are you currently using or interested in using oVirt?
- Are you interested in contributing to the oVirt community?

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  Thu Jun 14 11:18:55 2012
From: mburns at redhat.com (Mike Burns)
Date: Thu, 14 Jun 2012 07:18:55 -0400
Subject: [Users] Following Up on LinuxCon Japan Workshop
In-Reply-To: <4FD98BED.9090004@redhat.com>
References: <4FD910CA.1080808@redhat.com>
	<1339630889.3499.47.camel@beelzebub.mburnsfire.net>
	<4FD98BED.9090004@redhat.com>
Message-ID: <1339672735.2175.0.camel@mburns-laptop.usersys.redhat.com>

On Wed, 2012-06-13 at 23:59 -0700, Leslie Hawthorn wrote:
> Hi Mike,
> 
> Thanks for your detailed feedback.
> 
> On 06/13/2012 04:41 PM, Mike Burns wrote:
> > - Audience Participation
> > How many attendees? How did the Q&A periods go? Would we like to prepare
> > a post-event attendee survey? (I recommend we do the survey and can
> > prepare some questions for the group if that's useful.)
> > I think we should prepare the survey in advance of the next workshop and
> > ask people to fill it out during the workshop, rather than coming back a
> > couple weeks after the fact.
> I have an attendee list from the Linux Foundation for each workshop, so 
> if we'd like to get the survey out this week it can happen. I believe I 
> can also find a resource to translate the survey into Japanese, though 
> that would mean a delay in sending it out.
> 
> Some suggested questions, I'd pare down to no more than 5.
> - What was your favorite talk?
> - What could we do to improve?
> - Were the talks too long? Too short?
> - Was the presentation material clear to you?
> - Are you currently using or interested in using oVirt?
> - Are you interested in contributing to the oVirt community?
> 
> Cheers,
> LH
> 
> 

If you think it's worth it, then go for it.  Feedback is always good.

Mike



From mburns at redhat.com  Thu Jun 14 11:29:23 2012
From: mburns at redhat.com (Mike Burns)
Date: Thu, 14 Jun 2012 07:29:23 -0400
Subject: [Users] Test Day rpms uploaded (partially)
In-Reply-To: <1339621919.3499.12.camel@beelzebub.mburnsfire.net>
References: <1339621802.3499.11.camel@beelzebub.mburnsfire.net>
	<1339621919.3499.12.camel@beelzebub.mburnsfire.net>
Message-ID: <1339673363.2175.1.camel@mburns-laptop.usersys.redhat.com>

On Wed, 2012-06-13 at 17:11 -0400, Mike Burns wrote:
> Helps if I give the repo definition:
> 
> [ovirt-beta]
> name=Nightly builds of the oVirt project
> baseurl=http://ovirt.org/releases/beta/fedora/$releasever/
> enabled=0
> skip_if_unavailable=1
> gpgcheck=0
> 
> 
> On Wed, 2012-06-13 at 17:10 -0400, Mike Burns wrote:
> > RPMs for vdsm and ovirt-engine have been uploaded to ovirt.org.  Some of
> > the various tools have not been updated yet, but are coming.
> > 
> > Ready:
> > 
> > ovirt-engine
> > vdsm
> > 
> > RPMs exist but will likely be updated:
> > log-collector
> > iso-uploader
> > image-uploader
> > ovirt-engine-cli
> > ovirt-engine-sdk

All of ^^ are updated

> > 
> > RPMs not posted yet:
> > ovirt-node

Not yet ^^

> > ovirt-guest-agent

Done^^

> > 
> > As new RPMs get uploaded, I will send additional updates.
> > 
> > Thanks
> > 
> > Mike
> > 
> > _______________________________________________
> > Arch mailing list
> > Arch at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/arch
> 
> 
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users




From mburns at redhat.com  Thu Jun 14 13:20:28 2012
From: mburns at redhat.com (Mike Burns)
Date: Thu, 14 Jun 2012 09:20:28 -0400
Subject: [Users] Test Day rpms uploaded (partially)
In-Reply-To: <1339673363.2175.1.camel@mburns-laptop.usersys.redhat.com>
References: <1339621802.3499.11.camel@beelzebub.mburnsfire.net>
	<1339621919.3499.12.camel@beelzebub.mburnsfire.net>
	<1339673363.2175.1.camel@mburns-laptop.usersys.redhat.com>
Message-ID: <1339680028.2175.2.camel@mburns-laptop.usersys.redhat.com>

On Thu, 2012-06-14 at 07:29 -0400, Mike Burns wrote:
> On Wed, 2012-06-13 at 17:11 -0400, Mike Burns wrote:
> > Helps if I give the repo definition:
> > 
> > [ovirt-beta]
> > name=Nightly builds of the oVirt project
> > baseurl=http://ovirt.org/releases/beta/fedora/$releasever/
> > enabled=0
> > skip_if_unavailable=1
> > gpgcheck=0
> > 
> > 
> > On Wed, 2012-06-13 at 17:10 -0400, Mike Burns wrote:
> > > RPMs for vdsm and ovirt-engine have been uploaded to ovirt.org.  Some of
> > > the various tools have not been updated yet, but are coming.
> > > 
> > > Ready:
> > > 
> > > ovirt-engine
> > > vdsm
> > > 
> > > RPMs exist but will likely be updated:
> > > log-collector
> > > iso-uploader
> > > image-uploader
> > > ovirt-engine-cli
> > > ovirt-engine-sdk
> 
> All of ^^ are updated
> 
> > > 
> > > RPMs not posted yet:
> > > ovirt-node
> 
> Not yet ^^

2.4.0 versions posted
> 
> > > ovirt-guest-agent
> 
> Done^^
> 
> > > 
> > > As new RPMs get uploaded, I will send additional updates.
> > > 
> > > Thanks
> > > 
> > > Mike
> > > 
> > > _______________________________________________
> > > Arch mailing list
> > > Arch at ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/arch
> > 
> > 
> > _______________________________________________
> > Users mailing list
> > Users at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> 




From bazulay at redhat.com  Thu Jun 14 15:02:46 2012
From: bazulay at redhat.com (Barak Azulay)
Date: Thu, 14 Jun 2012 18:02:46 +0300
Subject: [Users] Following Up on LinuxCon Japan Workshop
In-Reply-To: <1339630889.3499.47.camel@beelzebub.mburnsfire.net>
References: <4FD910CA.1080808@redhat.com>
	<1339630889.3499.47.camel@beelzebub.mburnsfire.net>
Message-ID: <4FD9FD16.20008@redhat.com>

On 06/14/2012 02:41 AM, Mike Burns wrote:
> Hi Leslie,
>
> On Wed, 2012-06-13 at 15:14 -0700, Leslie Hawthorn wrote:
>> Hello everyone,
>>
>> I'd like to collect feedback from everyone on last week's oVirt workshop
>> at LinuxCon Japan. [0] Please reply back with comments by close of
>> business this Friday, 15 June.
>>
>> Once we have gathered feedback on list, I'll capture it on the oVirt
>> wiki. We can then use what we've learned to help construct the agenda
>> and other plans for other upcoming oVirt workshops at LinuxCons. [1]
>>
>> If you know that you would like to volunteer as an instructor for future
>> workshops or would like to suggest alternate content for the workshop,
>> please include that in your feedback.
>>
>> - Course Material
>> What sessions were most well received? Which ones require improvement?
>> Any additional sessions we'd suggest?
>
> All of the sessions seemed to be well received.  I don't know that any
> need blatant improvement, though they could probably all take a bit of
> slide updates.  The ovirt-node presentation was especially out of date
> (my fault) with it's screenshots.
>


I would like to add:
- a demo is a must in a workshop, as it is the most effective and
   impressive way to attract people.
- I think the ovirt-engine presentation needs a bit more meat
- I would also add vertical presentations:
     * ovirt network
     * ovirt storage
     * ovirt vm life cycle
   Of course all the above should be presented after the arch & demo
   presentation





>>
>> - Audience Participation
>> How many attendees? How did the Q&A periods go? Would we like to prepare
>> a post-event attendee survey? (I recommend we do the survey and can
>> prepare some questions for the group if that's useful.)
>
> There were probably between 25-35 people through the course of the day
> for all the presentations.


I gave also an intro/arch talk also in the virt mini-summit, I actually 
gave 2.
I volunteered to cover for one of the presenters that surprisingly
didn't show up on time, because of the confusion this session was rather 
small (~40)
In the second one (in my scheduled slot), there were about ~80.



>
> There wasn't really a lot of time set aside for Q&A aside from a few
> minutes at the end of each presentation and the breaks in between
> presentations.  During those times, there generally were people asking
> questions.


Actually I wasn't expecting too many questions due to the different 
culture of the audience, but we did get questions and people showed 
interest.
Most of the interesting questions came during the breaks, and I had a 
few white-board sessions with those people.



>
> I think we should prepare the survey in advance of the next workshop and
> ask people to fill it out during the workshop, rather than coming back a
> couple weeks after the fact.  We didn't really collect names of the
> people in attendance and I expect that a fair number of people
> registered attended the Gluster Conference.
>

The linux foundation scanned all the participants tags, so I guess they 
can supply the names.


>>
>> - Developer/user traction resulting from engaging at workshop
>> Did this workshop help us to gain new developers or users? Reinforce
>> relationships with existing community members?
>
> Only time will really tell here.  People definitely seemed interested
> and there were a couple people already downloading and installing the
> bits during the workshop.  I got the impression that most of the people
> there were more corporate focused -- Hitachi and Fujitsu were both well
> represented.  They're from companies that have previously expressed
> interest in the project.
>


Hard to tell,
I had a feeling that there was also a none developers group that came 
also to learn about ovirt, more of the consultant type that actually 
considering ovirt as an option.


>>
>> - Promotion of the event, both before and after
>> What could be done to more effectively promote the event prior to the
>> workshops? Videos and slides from the workshop should be posted on the
>> LC Japan site tomorrow; what action would the community like to take to
>> promote this content?
>
> Not really my area of expertise -- promoting.  Probably better to get
> information out there earlier that the workshop is happening.  It seemed
> to be a bit of a fire drill getting things together for this workshop
> since it was only about a month before that we decided to run it.
> Future workshops shouldn't be as big a deal.
>


I would say we need a lot of promotion, I was actually accessed by a few 
people after the into presentation, saying they had no idea that ovirt 
is so mature and feature reach.
This message should be conveyed before the workshop.



> Probably an email announcement to users@ with a link to the
> presentations/videos is the right next step.
>>
>> - A/V and Room Set up
>> Did the seating arrangements work well for the workshop format? Did the
>> A/V work well, including the videotaping process?
>
> Our room was setup with 5 round tables seating 10 people each.  I'm not
> sure that it was really the right layout.  I expected either rows of
> chairs or long tables with chairs all facing the presentation screen.
>
> A/V worked seamlessly.  It was all setup already when we arrived.
>


I would agree with Mike on the room setup.
I would prefer facing the presentation rather than having to look aside.

In addition and related to the preparations for the workshop,
Since it was setup so late, the linux foundation thought that setting 
the workshop means canceling the mini-summit presentation slot.
So all the handouts & schedule boards hanged around the summit did no 
include this talk, anyway eventually they hanged a hand written schedule 
update, but I assume more people would have come if they knew.

The web schedule was updated.


>>
>> - Food and beverage
>> Did the catered in lunch help to keep the flow of the workshop
>> productive? Was the food of good quality and in keeping with the needs
>> of attendee dietary constraints?
>
> I had no issues with the food.  People seemed to take the opportunity
> more to step out and take a break, rather than sit and continue
> discussing.
>

I agree

>>
>> - Give aways
>> We did not produce attendee gifts for the oVirt workshop. Thoughts on
>> whether this would be a welcome addition in the future? Suggestions for
>> type of gift also welcome.
>
> It would have been nice to have some sort of SWAG to give away, whether
> just fancy handouts or stickers.  It would be even better if we could
> have some sort of appliance with ovirt pre-installed and configured on a
> usb stick as well, but that's probably a year or 2 down the road.
>
>>
>> - Any other feedback
>
> It's probably better if there are people from a wider range of the
> sub-projects than we had in Japan.  I think that between Barak and I, we
> managed to cover the majority of the project, but I think it would be
> better to have someone from each major subproject there.
>
> I expect that either myself or someone from the Node team will be
> attending at least LinuxCon NA, LinuxCon Europe and the NetApp
> workshops.  We'll certainly handle the Node presentation for each of
> these workshops.
>


It looks like ovirt & gluster workshops will happen side by side in the 
near future.
I don't know if this is possible but I would do the workshops in 
different days (of the summit) so people that want to participate in 
both workshops can do it.
I know for sure that in Japan many registered for both workshops



Barak

> Mike
>
>>
>> If it is preferable to discuss this feedback real-time, I will ask Mike
>> Burns to give us more time for this topic during next week's oVirt IRC
>> meeting.
>>
>> [0] -
>> https://events.linuxfoundation.org/events/linuxcon-japan/ovirt-gluster-workshops
>> [1] - http://www.ovirt.org/wiki/OVirt_Global_Workshops
>>
>> Cheers,
>> LH
>>
>
>
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch
>
>



From lhawthor at redhat.com  Thu Jun 14 19:11:43 2012
From: lhawthor at redhat.com (Leslie Hawthorn)
Date: Thu, 14 Jun 2012 12:11:43 -0700
Subject: [Users] Following Up on LinuxCon Japan Workshop
In-Reply-To: <1339672735.2175.0.camel@mburns-laptop.usersys.redhat.com>
References: <4FD910CA.1080808@redhat.com>
	<1339630889.3499.47.camel@beelzebub.mburnsfire.net>
	<4FD98BED.9090004@redhat.com>
	<1339672735.2175.0.camel@mburns-laptop.usersys.redhat.com>
Message-ID: <4FDA376F.4070608@redhat.com>

On 06/14/2012 04:18 AM, Mike Burns wrote:
> On Wed, 2012-06-13 at 23:59 -0700, Leslie Hawthorn wrote:
>> Hi Mike,
>>
>> Thanks for your detailed feedback.
>>
>> On 06/13/2012 04:41 PM, Mike Burns wrote:
>>> - Audience Participation
>>> How many attendees? How did the Q&A periods go? Would we like to prepare
>>> a post-event attendee survey? (I recommend we do the survey and can
>>> prepare some questions for the group if that's useful.)
>>> I think we should prepare the survey in advance of the next workshop and
>>> ask people to fill it out during the workshop, rather than coming back a
>>> couple weeks after the fact.
>> I have an attendee list from the Linux Foundation for each workshop, so
>> if we'd like to get the survey out this week it can happen. I believe I
>> can also find a resource to translate the survey into Japanese, though
>> that would mean a delay in sending it out.
>>
>> Some suggested questions, I'd pare down to no more than 5.
>> - What was your favorite talk?
>> - What could we do to improve?
>> - Were the talks too long? Too short?
>> - Was the presentation material clear to you?
>> - Are you currently using or interested in using oVirt?
>> - Are you interested in contributing to the oVirt community?
>>
>> Cheers,
>> LH
>>
>>
> If you think it's worth it, then go for it.  Feedback is always good.
>
>
I definitely think it's worth it and the Linux Foundation has graciously 
agreed to include our questions in their post-event attendee survey. 
Here are the questions we've asked, along with a request to the LF to 
help us word the text in such a way that it is clear to attendees who do 
not speak English as their first language:

oVirt:
Did you attend the oVirt workshop?
If yes:
1) What talk(s) were most useful to you?
2) What can we do to improve the workshop?
3) Was the presentation material clear to you?
4) Are you or your organization currently using or interested in using 
oVirt?
5) Would you like to contribute to the oVirt community?

I will collate the feedback from the survey and share it with everyone 
once it is collected.

Cheers,
LH

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

identi.ca/lh
twitter.com/lhawthorn



From gkotton at redhat.com  Fri Jun 15 06:11:39 2012
From: gkotton at redhat.com (Gary Kotton)
Date: Fri, 15 Jun 2012 09:11:39 +0300
Subject: [oVirt][Quantum] question about quantum CLI
In-Reply-To: <CAAskrmGFmdiQ1tmhgJx7Zdoat2p4Q50TYEE7zoLbmS5uK8mNPw@mail.gmail.com>
References: <CAAskrmH2rXN_nbnoBqkyWHj_mEWNNMhZm-AwcRauJ558nfnobw@mail.gmail.com>	<4FD7022F.2040600@redhat.com>	<4FD70DA4.5000602@redhat.com>	<4FD724C8.8060506@redhat.com>	<CAAskrmHB61c+X+P39za85nQndN3j6YZ8O7uqX=p5TeQiOUmWCQ@mail.gmail.com>	<4FD82CE7.8090401@redhat.com>	<CAAskrmHHuc8E-sjddLM+sDkh2svszbNUa9L07ttNthjdzU3PJQ@mail.gmail.com>	<4FD861D0.3010902@redhat.com>
	<CAAskrmGFmdiQ1tmhgJx7Zdoat2p4Q50TYEE7zoLbmS5uK8mNPw@mail.gmail.com>
Message-ID: <4FDAD21B.3030204@redhat.com>

Hi Kris,
You have asked a very interesting and good question. Please see the 
answers an explanations below. Both flow are used. The "a" flows (1a2a 
and 3a) are for the network management. The "b" flows (1b and 2b) are 
for the VM management.
Network management (1a):
     - user create a Quantum network
     - user will create a Quantum port and attachment
VM Management (1b):
     - users creates a VM
     - assigned VM to one or more logical networks. Each each assignment 
will receive the above quantum details
VM flow:
     - VDSM creates the libvirt XML file
         - (2b) if libvirt version is 0.9.10 or earlier then VDSM will 
have to create the tap device (via attachment ID) and will set it with 
type 'ethernet' in the libvirt file (this is what was done in the POC). 
In addition this it need to notify OVS of the VM ID on the port
         - in later versions of libvirt, libvirt will do the create via 
the attachment id
     - VDSM will start the VM
Network flow (2a and 3a):
     - The Quantum agent polls the Quantum plugin for network changes. 
If the agent detects a tap device that is part of a network then it will 
configure the characteristics of this tap device on the OVS. In the case 
of the POC it will be the VLAN tag of the network
Hope that I have answered your questions.
Thanks
Gary

On 06/14/2012 10:49 AM, Kris zhang wrote:
> Hi Kotton,
>
> Thank your very much, and i still have a question:
>
> There is a quantum.py file in the gkotton-vdsm_quantum-78427ca.zip. I 
> saw there are some methods (For example: vifAddOpenVswitch() ) to call 
> ovs-vsctl command, that means vdsm will control the ovs, not through 
> ovs quantum agent?
>
> The ovs quantum agent code is in the 
> http://bazaar.launchpad.net/~netstack-core/quantum/essex/view/head:/quantum/plugins/openvswitch/agent/ovs_quantum_agent.py 
> <http://bazaar.launchpad.net/%7Enetstack-core/quantum/essex/view/head:/quantum/plugins/openvswitch/agent/ovs_quantum_agent.py>
>
>
> Inline image 1
>
> Please see above the image, and there are two ways:
>
> First way: 1a, 2a, 3a.
> Second way: 1b, 2b
>
> which way is used in POC?
>
> Best regards,
> Kris
>
>
>
> On Wed, Jun 13, 2012 at 5:48 PM, Gary Kotton <gkotton at redhat.com 
> <mailto:gkotton at redhat.com>> wrote:
>
>     On 06/13/2012 11:57 AM, Kris zhang wrote:
>>     Thanks for you detail answer, and please see the result of the
>>     command quantum update_port,
>     The command "quantum update_port" sets the state of the port. In
>     the case of the ovirt.sh script this sets the port in ACTIVE state.
>     The "user" is responsible for providing the attachment ID. In the
>     case of the ovirt.sh script the ID is generated via uuidgen.
>     Once you have generated a UUID for the attachment you need to pass
>     this to quantum via the "quantum plug_iface".
>>
>>     Inline image 1
>>
>>     I run this script from the shell, and you can see there is no an
>>     attachment UUID created. Can you show me your testing result?
>
>     Please see below:
>
>     openstack at openstack:/tmp$ ./ovirt.sh network create Q_net
>     openstack at openstack:/tmp$ ./ovirt.sh port create Q_net 12345678
>     Updated Logical Port with ID: f9f203ab-dab6-4b9c-8dcf-561bcc698c76
>     on Virtual Network: 8c50db01-54ef-4688-a274-9ab3fcfafe7d
>     for tenant: default
>     Plugged interface 24bf26c4-f8eb-46cd-a168-b7a25e64d5b2
>     into Logical Port: f9f203ab-dab6-4b9c-8dcf-561bcc698c76
>     on Virtual Network: 8c50db01-54ef-4688-a274-9ab3fcfafe7d
>     for Tenant: default
>     openstack at openstack:/tmp$
>
>
>     openstack at openstack:/tmp$ ll
>     total 40
>     drwxrwxrwt  4 root      root      4096 2012-06-13 05:39 ./
>     drwxr-xr-x 23 root      root      4096 2012-05-26 06:39 ../
>     -rw-rw-r--  1 openstack openstack    6 2012-06-13 05:38
>     network.12345678
>     -rw-rw-r--  1 openstack openstack   37 2012-06-13 05:38 network.Q_net
>     -rw-rw-r--  1 openstack openstack   37 2012-06-13 05:38
>     network.Q_net.12345678.port
>     -rw-rw-r--  1 openstack openstack   37 2012-06-13 05:38
>     network.Q_net.12345678.port.attach
>     -rwxrwxrwx  1 openstack openstack 2097 2012-06-13 05:07 ovirt.sh*
>     -rw-rw-r--  1 openstack openstack 1797 2012-06-13 05:38 ovirt.txt
>
>     openstack at openstack:/tmp$ cat network.Q_net.12345678.port.attach
>     24bf26c4-f8eb-46cd-a168-b7a25e64d5b2
>     openstack at openstack:/tmp$
>
>     Thanks
>     Gary
>
>>
>>     BR,
>>     Kris
>>
>>
>>     On Wed, Jun 13, 2012 at 2:02 PM, Gary Kotton <gkotton at redhat.com
>>     <mailto:gkotton at redhat.com>> wrote:
>>
>>         Hi Kris,
>>         Please see my answers and questions below.
>>         Thanks
>>         Gary
>>
>>
>>         On 06/13/2012 07:31 AM, Kris zhang wrote:
>>>         Hi Kotton,
>>>
>>>         In the file ovirt.sh, there is a line:
>>
>>         A bit of background regarding the script. The purpose of the
>>         POC was to show that Quantum can be run in oVirt. It would
>>         have been ideal to write a REST client that could interface
>>         with the Quantum service. Due to the fact that I was not
>>         familiar with the oVirt code I felt that a quicker and more
>>         productive means was to invoke a bash script from the oVirt
>>         engine code. The script would invoke the quantum cli (this is
>>         a client that configures the quantum server). In addition to
>>         this I did not want to make any changes to the database
>>         schema. The result was a script that does the following:
>>         1. Logical Network Management:
>>             Create:
>>                 ovirt.sh network create <name>
>>                     - the name is the name of the logical network (in
>>         the POC this is prefixed by "Q_"
>>                     - this invokes the cli to create a network called
>>         <name>
>>                     - the UUID returned by the quantum service will
>>         be save in /tmp/network.<name>
>>                     - the above UUID is read when this logical
>>         network is used (this in the future will be save in the oVirt
>>         data base)
>>             Delete:
>>                 ovirt.sh network remove <name>
>>                     - the name is the name of the logical network (in
>>         the POC this is prefixed by "Q_"
>>                     - this invokes the cli to delete a network called
>>         <name>
>>                     - the file /tmp/network.<name> is deleted
>>         2. VM Port management
>>             Create:
>>                 ovirt.sh port create <net_name> <vmid>
>>                     - the network name and the vm id are input (the
>>         VM id is a key to be able to delete it all :))
>>                     - the script does the following:
>>                         - creates a port on the network. saves the
>>         port id in /tmp/network.<name>.<vmid>.port
>>                         - sets the state of the port to ACTIVE
>>                         - creates an attachment ID (this is the line
>>         that you had problems with). This is saved in
>>         /tmp/network.<name>.<vmid>.attachment
>>                         - saves the network name in a file
>>         /tmp/network.<vmid>
>>                         - the UUID's are read when the VM is started
>>         so that they can be passed to VDSM
>>             Delete:
>>                 ovirt.sh port remove <vmid>
>>                     - using the vmid the network name is read =>
>>         enables us to get all of the ID's to delete port in quantum
>>                     - cleans all of the files
>>         The script is called from the ovirt engine. Sorry for the
>>         long winded explanation.
>>
>>
>>>         quantum update_port default $NET_UUID $PORT_UUID state=ACTIVE
>>>                         uuidgen > /tmp/network.$3.$4.port.attach
>>>         ATTACH_UUID=`cat /tmp/network.$3.$4.port.attach`
>>
>>         In Quantum the attachment ID is generated by the user. The
>>         code above generates the attachment ID for the port.
>>>
>>>
>>>         But i run this command, i found there is no any uuid
>>>         generated, so what's the value of the ATTACH_UUID?
>>         Do you run the script from the shell or is this run via oVirt?
>>         There is a log of all of the script command - can you please
>>         look in /tmp/ovirt.txt - this may give us some clues.
>>         You can run the script commands as described above. This may
>>         also help.
>>         Thanks
>>         Gary
>>
>>>         Best regards,
>>>         Kris
>>>
>>>
>>>         On Tue, Jun 12, 2012 at 7:15 PM, Gary Kotton
>>>         <gkotton at redhat.com <mailto:gkotton at redhat.com>> wrote:
>>>
>>>             On 06/12/2012 12:36 PM, Itamar Heim wrote:
>>>
>>>                 On 06/12/2012 11:47 AM, Gary Kotton wrote:
>>>
>>>                     Hi Kris,
>>>                     Thanks for the questions. Please see my inline
>>>                     answers. I have also
>>>                     cc'ed the ovirt arch mailing list.
>>>                     Thanks
>>>                     Gary
>>>
>>>                     On 06/12/2012 11:21 AM, Kris zhang wrote:
>>>
>>>                         Hi Gkotton,
>>>
>>>                         I have some questions:
>>>
>>>                         1) In the file "ovirt.sh", i found the
>>>                         command quantum always use the
>>>                         tenant "default", so if the ovirt don't
>>>                         support multi-tenant?
>>>
>>>                     oVirt does not support multi tenancy at the
>>>                     moment. Maybe there are
>>>                     people on the list who can provide more details
>>>                     about this. The initial
>>>                     plan was to use the "default" tenant.
>>>
>>>
>>>                 ovirt supports multiple users and an RBAC model for
>>>                 permissions between these users.
>>>                 what exactly are you looking for?
>>>
>>>             Quantum support multi tenancy. The integration with
>>>             oVirt was done with the "default" tenant. This is a
>>>             different model to that of oVirt.
>>>             Thanks
>>>             Gary
>>>
>>>
>>
>>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120615/f2689600/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 172132 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120615/f2689600/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 53568 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120615/f2689600/attachment-0001.png>

From dneary at redhat.com  Fri Jun 15 10:23:31 2012
From: dneary at redhat.com (Dave Neary)
Date: Fri, 15 Jun 2012 12:23:31 +0200
Subject: What are you looking for from oVirt?
In-Reply-To: <4FD8A370.3010904@redhat.com>
References: <4FD8A370.3010904@redhat.com>
Message-ID: <4FDB0D23.1050603@redhat.com>

Hi,

On 06/13/2012 04:28 PM, Dave Neary wrote:
> So - how are you using oVirt? Why did you choose it over alternatives?
> What do you like about it? and what would you like to see change,
> whether that is in terms of technical, process, or marketing changes?
> I'm here to help, but to do so I need your help first!

Thank you to all those who have replied, on and off list, so far. For 
those of you who sent me private messages, I'll be (anonymously) 
collating your feedback and forwarding it on.

The range of users who have replied so far includes:
* Sysadmin at small web hosting business
* Cost-sensitive IT department of an unrelated industry
* Hosting provider specialising in HA
* Running a private cloud
* Test lab set-up considering for production deployment

And the top features you've cited are:
* Stateless hypervisor
* Ability to migrate VMs
* RHEL and KVM
* Cost
* The ability to have your preferred OS as both hypervisor and guest as 
a first class citizen
* Aimed for data center use-case rather than cloud

And the top gaps you've identified so far:
* Insufficient resources (docs) to help with production deployment on 
ovirt.org
* Difficulty of configuration and getting started
* You'd like to see a more diverse contributor community
* Stability (unfortunately, I don't have any concrete examples of this 
from the commenter)
* History on resource usage in hypervisors and guests
* Integration with Gluster
* Offer choices of guest agents with other distributions than RHEL

This is all giving me great insight into who's here - please keep it coming!

Cheers,
Dave.

-- 
Dave Neary
Community Action and Impact
Open Source and Standards Team, Red Hat
Phone: +33 9 50 71 55 62


From lhawthor at redhat.com  Fri Jun 15 16:44:40 2012
From: lhawthor at redhat.com (Leslie Hawthorn)
Date: Fri, 15 Jun 2012 09:44:40 -0700
Subject: [Users] Following Up on LinuxCon Japan Workshop
In-Reply-To: <4FD92D8A.6040602@redhat.com>
References: <4FD910CA.1080808@redhat.com>
	<1339630889.3499.47.camel@beelzebub.mburnsfire.net>
	<4FD92D8A.6040602@redhat.com>
Message-ID: <4FDB6678.9020705@redhat.com>

On 06/13/2012 05:17 PM, Karsten 'quaid' Wade wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 06/13/2012 04:41 PM, Mike Burns wrote:
>
>> Our room was setup with 5 round tables seating 10 people each.  I'm
>> not sure that it was really the right layout.  I expected either
>> rows of chairs or long tables with chairs all facing the
>> presentation screen.
> I'd like to hear more about what didn't work or could have improved
> with this setup. It sounds similar to a setup Leslie, Jason, and I
> looked at for a workshop at NetApp next year. At the time, it seemed
> like a fairly ideal setup in some ways - everyone can view the
> presenter but things are less classroom-like and more communal. (IIRC,
> the setup there includes a few additional siderooms setup as long
> tables and chairs facing one end of the room.)
>
+1

I have heard very good feedback about rounds for workshops in the past 
in terms of helping attendees hold better informal conversations and to 
help each other along when parts of the material were difficult for 
them. Whatever layout we choose, I want to ensure it's optimal for 
oVirt's needs.

Cheers,
LH

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

identi.ca/lh
twitter.com/lhawthorn



From ryanh at us.ibm.com  Fri Jun 15 19:53:52 2012
From: ryanh at us.ibm.com (Ryan Harper)
Date: Fri, 15 Jun 2012 14:53:52 -0500
Subject: ovirt f17 beta repo
Message-ID: <20120615195352.GN9959@frylock.austin.ibm.com>

I saw a discussion on #ovirt about how the build system is supposed to
increment the _XXXX past the version but that's not happening.  Well,
newer rpms are now posted to the repo, but because the
version is the same expect for the githash, it won't upgrade.  Can we
get this fixed[1]?


[root at ichigo-dom234 ~]# ls *.rpm
ovirt-engine-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
ovirt-engine-backend-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
ovirt-engine-config-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
ovirt-engine-dbscripts-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
ovirt-engine-genericapi-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
ovirt-engine-notification-service-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
ovirt-engine-restapi-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
ovirt-engine-setup-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
ovirt-engine-tools-common-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
ovirt-engine-userportal-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
ovirt-engine-webadmin-portal-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
[root at ichigo-dom234 ~]# rpm -Uvh --test *.rpm 
Preparing...                ########################################### [100%]
    package ovirt-engine-backend-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-backend-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
    package ovirt-engine-dbscripts-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-dbscripts-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
    package ovirt-engine-genericapi-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-genericapi-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
    package ovirt-engine-restapi-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-restapi-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
    package ovirt-engine-setup-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-setup-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
    package ovirt-engine-config-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-config-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
    package ovirt-engine-notification-service-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-notification-service-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
    package ovirt-engine-tools-common-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-tools-common-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
    package ovirt-engine-userportal-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-userportal-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
    package ovirt-engine-webadmin-portal-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-webadmin-portal-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
    package ovirt-engine-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed

         
1. I know I can --nodeps --force to get this to work.

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh at us.ibm.com



From juan.hernandez at redhat.com  Sat Jun 16 16:49:49 2012
From: juan.hernandez at redhat.com (Juan Hernandez)
Date: Sat, 16 Jun 2012 18:49:49 +0200
Subject: ovirt f17 beta repo
In-Reply-To: <20120615195352.GN9959@frylock.austin.ibm.com>
References: <20120615195352.GN9959@frylock.austin.ibm.com>
Message-ID: <4FDCB92D.6080809@redhat.com>

On 06/15/2012 09:53 PM, Ryan Harper wrote:
> I saw a discussion on #ovirt about how the build system is supposed to
> increment the _XXXX past the version but that's not happening.  Well,
> newer rpms are now posted to the repo, but because the
> version is the same expect for the githash, it won't upgrade.  Can we
> get this fixed[1]?

In my opinion the version number of the RPM should not include that 
_XXXX suffix. We should build packages using the numbering schema 
recommended for snapshot and pre-release packages here:

http://fedoraproject.org/wiki/Packaging:NamingGuidelines#Release_Tag

So the pre-release numbers should be something like this:

3.1.0-0.1.20120615git0a4333
3.1.0-0.2.20120618git94a365
...

That way the day we do the release we can change to this numbering:

3.1.0-1
3.1.0-2
...

And any release number will be greater than any pre-release number.

> [root at ichigo-dom234 ~]# ls *.rpm
> ovirt-engine-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-backend-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-config-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-dbscripts-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-genericapi-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-notification-service-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-restapi-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-setup-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-tools-common-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-userportal-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-webadmin-portal-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> [root at ichigo-dom234 ~]# rpm -Uvh --test *.rpm
> Preparing...                ########################################### [100%]
>      package ovirt-engine-backend-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-backend-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-dbscripts-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-dbscripts-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-genericapi-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-genericapi-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-restapi-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-restapi-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-setup-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-setup-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-config-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-config-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-notification-service-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-notification-service-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-tools-common-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-tools-common-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-userportal-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-userportal-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-webadmin-portal-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-webadmin-portal-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>
>
> 1. I know I can --nodeps --force to get this to work.
>



From jhernand at redhat.com  Sat Jun 16 16:47:32 2012
From: jhernand at redhat.com (Juan Hernandez)
Date: Sat, 16 Jun 2012 18:47:32 +0200
Subject: ovirt f17 beta repo
In-Reply-To: <20120615195352.GN9959@frylock.austin.ibm.com>
References: <20120615195352.GN9959@frylock.austin.ibm.com>
Message-ID: <4FDCB8A4.9040802@redhat.com>

On 06/15/2012 09:53 PM, Ryan Harper wrote:
> I saw a discussion on #ovirt about how the build system is supposed to
> increment the _XXXX past the version but that's not happening.  Well,
> newer rpms are now posted to the repo, but because the
> version is the same expect for the githash, it won't upgrade.  Can we
> get this fixed[1]?

In my opinion the version number of the RPM should not include that 
_XXXX suffix. We should build packages using the numbering schema 
recommended for snapshot and pre-release packages here:

http://fedoraproject.org/wiki/Packaging:NamingGuidelines#Release_Tag

So the pre-release numbers should be something like this:

3.1.0-0.1.20120615git0a4333
3.1.0-0.2.20120618git94a365
...

That way the day we do the release we can change to this numbering:

3.1.0-1
3.1.0-2
...

And any release number will be greater than any pre-release number.

> [root at ichigo-dom234 ~]# ls *.rpm
> ovirt-engine-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-backend-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-config-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-dbscripts-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-genericapi-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-notification-service-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-restapi-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-setup-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-tools-common-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-userportal-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-webadmin-portal-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> [root at ichigo-dom234 ~]# rpm -Uvh --test *.rpm
> Preparing...                ########################################### [100%]
>      package ovirt-engine-backend-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-backend-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-dbscripts-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-dbscripts-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-genericapi-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-genericapi-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-restapi-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-restapi-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-setup-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-setup-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-config-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-config-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-notification-service-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-notification-service-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-tools-common-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-tools-common-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-userportal-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-userportal-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-webadmin-portal-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-webadmin-portal-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>      package ovirt-engine-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
>
>
> 1. I know I can --nodeps --force to get this to work.
>


-- 
Direcci?n Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 
3?D, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid ? C.I.F. B82657941 - Red Hat S.L.


From oschreib at redhat.com  Sun Jun 17 11:46:27 2012
From: oschreib at redhat.com (Ofer Schreiber)
Date: Sun, 17 Jun 2012 07:46:27 -0400 (EDT)
Subject: ovirt f17 beta repo
In-Reply-To: <20120615195352.GN9959@frylock.austin.ibm.com>
Message-ID: <34731506-a819-4779-86b0-064d32e4d852@zmail14.collab.prod.int.phx2.redhat.com>



----- Original Message -----
> I saw a discussion on #ovirt about how the build system is supposed
> to
> increment the _XXXX past the version but that's not happening.  Well,
> newer rpms are now posted to the repo, but because the
> version is the same expect for the githash, it won't upgrade.  Can we
> get this fixed[1]?

I'll fix it first thing Tomorrow's morning.
please note that in order to upgrade ovirt-engine, you should use the "engine-upgrade" utility (which wouldn't work due to the versioning issue)


> 
> 
> [root at ichigo-dom234 ~]# ls *.rpm
> ovirt-engine-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-backend-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-config-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-dbscripts-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-genericapi-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-notification-service-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-restapi-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-setup-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-tools-common-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-userportal-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> ovirt-engine-webadmin-portal-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> [root at ichigo-dom234 ~]# rpm -Uvh --test *.rpm
> Preparing...
>                ########################################### [100%]
>     package ovirt-engine-backend-3.1.0_0001-0.gitf093e0.fc17.noarch
>     (which is newer than
>     ovirt-engine-backend-3.1.0_0001-0.gitdd65f3.fc17.noarch) is
>     already installed
>     package ovirt-engine-dbscripts-3.1.0_0001-0.gitf093e0.fc17.noarch
>     (which is newer than
>     ovirt-engine-dbscripts-3.1.0_0001-0.gitdd65f3.fc17.noarch) is
>     already installed
>     package
>     ovirt-engine-genericapi-3.1.0_0001-0.gitf093e0.fc17.noarch
>     (which is newer than
>     ovirt-engine-genericapi-3.1.0_0001-0.gitdd65f3.fc17.noarch) is
>     already installed
>     package ovirt-engine-restapi-3.1.0_0001-0.gitf093e0.fc17.noarch
>     (which is newer than
>     ovirt-engine-restapi-3.1.0_0001-0.gitdd65f3.fc17.noarch) is
>     already installed
>     package ovirt-engine-setup-3.1.0_0001-0.gitf093e0.fc17.noarch
>     (which is newer than
>     ovirt-engine-setup-3.1.0_0001-0.gitdd65f3.fc17.noarch) is
>     already installed
>     package ovirt-engine-config-3.1.0_0001-0.gitf093e0.fc17.noarch
>     (which is newer than
>     ovirt-engine-config-3.1.0_0001-0.gitdd65f3.fc17.noarch) is
>     already installed
>     package
>     ovirt-engine-notification-service-3.1.0_0001-0.gitf093e0.fc17.noarch
>     (which is newer than
>     ovirt-engine-notification-service-3.1.0_0001-0.gitdd65f3.fc17.noarch)
>     is already installed
>     package
>     ovirt-engine-tools-common-3.1.0_0001-0.gitf093e0.fc17.noarch
>     (which is newer than
>     ovirt-engine-tools-common-3.1.0_0001-0.gitdd65f3.fc17.noarch) is
>     already installed
>     package
>     ovirt-engine-userportal-3.1.0_0001-0.gitf093e0.fc17.noarch
>     (which is newer than
>     ovirt-engine-userportal-3.1.0_0001-0.gitdd65f3.fc17.noarch) is
>     already installed
>     package
>     ovirt-engine-webadmin-portal-3.1.0_0001-0.gitf093e0.fc17.noarch
>     (which is newer than
>     ovirt-engine-webadmin-portal-3.1.0_0001-0.gitdd65f3.fc17.noarch)
>     is already installed
>     package ovirt-engine-3.1.0_0001-0.gitf093e0.fc17.noarch (which is
>     newer than ovirt-engine-3.1.0_0001-0.gitdd65f3.fc17.noarch) is
>     already installed
> 
>          
> 1. I know I can --nodeps --force to get this to work.
> 
> --
> Ryan Harper
> Software Engineer; Linux Technology Center
> IBM Corp., Austin, Tx
> ryanh at us.ibm.com
> 
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch
> 


From oschreib at redhat.com  Sun Jun 17 11:47:26 2012
From: oschreib at redhat.com (Ofer Schreiber)
Date: Sun, 17 Jun 2012 07:47:26 -0400 (EDT)
Subject: ovirt f17 beta repo
In-Reply-To: <4FDCB8A4.9040802@redhat.com>
Message-ID: <a0a3dae1-5a74-42cf-b15a-53cf6c56a5e4@zmail14.collab.prod.int.phx2.redhat.com>



----- Original Message -----
> On 06/15/2012 09:53 PM, Ryan Harper wrote:
> > I saw a discussion on #ovirt about how the build system is supposed
> > to
> > increment the _XXXX past the version but that's not happening.
> >  Well,
> > newer rpms are now posted to the repo, but because the
> > version is the same expect for the githash, it won't upgrade.  Can
> > we
> > get this fixed[1]?
> 
> In my opinion the version number of the RPM should not include that
> _XXXX suffix. We should build packages using the numbering schema
> recommended for snapshot and pre-release packages here:
> 
> http://fedoraproject.org/wiki/Packaging:NamingGuidelines#Release_Tag
> 
> So the pre-release numbers should be something like this:
> 
> 3.1.0-0.1.20120615git0a4333
> 3.1.0-0.2.20120618git94a365
> ...
> 
> That way the day we do the release we can change to this numbering:
> 
> 3.1.0-1
> 3.1.0-2

Good suggestion, we will use that starting next beta drop.

> ...
> 
> And any release number will be greater than any pre-release number.
> 
> > [root at ichigo-dom234 ~]# ls *.rpm
> > ovirt-engine-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > ovirt-engine-backend-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > ovirt-engine-config-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > ovirt-engine-dbscripts-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > ovirt-engine-genericapi-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > ovirt-engine-notification-service-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > ovirt-engine-restapi-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > ovirt-engine-setup-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > ovirt-engine-tools-common-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > ovirt-engine-userportal-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > ovirt-engine-webadmin-portal-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > [root at ichigo-dom234 ~]# rpm -Uvh --test *.rpm
> > Preparing...
> >                ########################################### [100%]
> >      package
> >      ovirt-engine-backend-3.1.0_0001-0.gitf093e0.fc17.noarch
> >      (which is newer than
> >      ovirt-engine-backend-3.1.0_0001-0.gitdd65f3.fc17.noarch) is
> >      already installed
> >      package
> >      ovirt-engine-dbscripts-3.1.0_0001-0.gitf093e0.fc17.noarch
> >      (which is newer than
> >      ovirt-engine-dbscripts-3.1.0_0001-0.gitdd65f3.fc17.noarch) is
> >      already installed
> >      package
> >      ovirt-engine-genericapi-3.1.0_0001-0.gitf093e0.fc17.noarch
> >      (which is newer than
> >      ovirt-engine-genericapi-3.1.0_0001-0.gitdd65f3.fc17.noarch)
> >      is already installed
> >      package
> >      ovirt-engine-restapi-3.1.0_0001-0.gitf093e0.fc17.noarch
> >      (which is newer than
> >      ovirt-engine-restapi-3.1.0_0001-0.gitdd65f3.fc17.noarch) is
> >      already installed
> >      package ovirt-engine-setup-3.1.0_0001-0.gitf093e0.fc17.noarch
> >      (which is newer than
> >      ovirt-engine-setup-3.1.0_0001-0.gitdd65f3.fc17.noarch) is
> >      already installed
> >      package ovirt-engine-config-3.1.0_0001-0.gitf093e0.fc17.noarch
> >      (which is newer than
> >      ovirt-engine-config-3.1.0_0001-0.gitdd65f3.fc17.noarch) is
> >      already installed
> >      package
> >      ovirt-engine-notification-service-3.1.0_0001-0.gitf093e0.fc17.noarch
> >      (which is newer than
> >      ovirt-engine-notification-service-3.1.0_0001-0.gitdd65f3.fc17.noarch)
> >      is already installed
> >      package
> >      ovirt-engine-tools-common-3.1.0_0001-0.gitf093e0.fc17.noarch
> >      (which is newer than
> >      ovirt-engine-tools-common-3.1.0_0001-0.gitdd65f3.fc17.noarch)
> >      is already installed
> >      package
> >      ovirt-engine-userportal-3.1.0_0001-0.gitf093e0.fc17.noarch
> >      (which is newer than
> >      ovirt-engine-userportal-3.1.0_0001-0.gitdd65f3.fc17.noarch)
> >      is already installed
> >      package
> >      ovirt-engine-webadmin-portal-3.1.0_0001-0.gitf093e0.fc17.noarch
> >      (which is newer than
> >      ovirt-engine-webadmin-portal-3.1.0_0001-0.gitdd65f3.fc17.noarch)
> >      is already installed
> >      package ovirt-engine-3.1.0_0001-0.gitf093e0.fc17.noarch (which
> >      is newer than
> >      ovirt-engine-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already
> >      installed
> >
> >
> > 1. I know I can --nodeps --force to get this to work.
> >
> 
> 
> --
> Direcci?n Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
> 3?D, 28016 Madrid, Spain
> Inscrita en el Reg. Mercantil de Madrid ? C.I.F. B82657941 - Red Hat
> S.L.
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch
> 


From bazulay at redhat.com  Sun Jun 17 17:29:13 2012
From: bazulay at redhat.com (Barak Azulay)
Date: Sun, 17 Jun 2012 20:29:13 +0300
Subject: [Users] Following Up on LinuxCon Japan Workshop
In-Reply-To: <4FDD8093.1020108@redhat.com>
References: <4FD910CA.1080808@redhat.com>	<1339630889.3499.47.camel@beelzebub.mburnsfire.net>
	<4FD9FD16.20008@redhat.com> <4FDD8093.1020108@redhat.com>
Message-ID: <4FDE13E9.10203@redhat.com>

On 06/17/2012 10:00 AM, Yair Zaslavsky wrote:
> On 06/14/2012 06:02 PM, Barak Azulay wrote:
>> On 06/14/2012 02:41 AM, Mike Burns wrote:
>>> Hi Leslie,
>>>
>>> On Wed, 2012-06-13 at 15:14 -0700, Leslie Hawthorn wrote:
>>>> Hello everyone,
>>>>
>>>> I'd like to collect feedback from everyone on last week's oVirt workshop
>>>> at LinuxCon Japan. [0] Please reply back with comments by close of
>>>> business this Friday, 15 June.
>>>>
>>>> Once we have gathered feedback on list, I'll capture it on the oVirt
>>>> wiki. We can then use what we've learned to help construct the agenda
>>>> and other plans for other upcoming oVirt workshops at LinuxCons. [1]
>>>>
>>>> If you know that you would like to volunteer as an instructor for future
>>>> workshops or would like to suggest alternate content for the workshop,
>>>> please include that in your feedback.
>>>>
>>>> - Course Material
>>>> What sessions were most well received? Which ones require improvement?
>>>> Any additional sessions we'd suggest?
>>>
>>> All of the sessions seemed to be well received.  I don't know that any
>>> need blatant improvement, though they could probably all take a bit of
>>> slide updates.  The ovirt-node presentation was especially out of date
>>> (my fault) with it's screenshots.
>>>
>>
>>
>> I would like to add:
>> - a demo is a must in a workshop, as it is the most effective and
>>    impressive way to attract people.
>> - I think the ovirt-engine presentation needs a bit more meat
> What stuff do you think we need to add to this presentation?
> Can you be more specific?
> Thanks,
>
> Yair


- better diagrams
- code structure
- go over a simple example-command work  flow - from entry till DB ...

and many more



>
>> - I would also add vertical presentations:
>>      * ovirt network
>>      * ovirt storage
>>      * ovirt vm life cycle
>>    Of course all the above should be presented after the arch&  demo
>>    presentation
>>
>>
>>
>>
>>
>>>>
>>>> - Audience Participation
>>>> How many attendees? How did the Q&A periods go? Would we like to prepare
>>>> a post-event attendee survey? (I recommend we do the survey and can
>>>> prepare some questions for the group if that's useful.)
>>>
>>> There were probably between 25-35 people through the course of the day
>>> for all the presentations.
>>
>>
>> I gave also an intro/arch talk also in the virt mini-summit, I actually
>> gave 2.
>> I volunteered to cover for one of the presenters that surprisingly
>> didn't show up on time, because of the confusion this session was rather
>> small (~40)
>> In the second one (in my scheduled slot), there were about ~80.
>>
>>
>>
>>>
>>> There wasn't really a lot of time set aside for Q&A aside from a few
>>> minutes at the end of each presentation and the breaks in between
>>> presentations.  During those times, there generally were people asking
>>> questions.
>>
>>
>> Actually I wasn't expecting too many questions due to the different
>> culture of the audience, but we did get questions and people showed
>> interest.
>> Most of the interesting questions came during the breaks, and I had a
>> few white-board sessions with those people.
>>
>>
>>
>>>
>>> I think we should prepare the survey in advance of the next workshop and
>>> ask people to fill it out during the workshop, rather than coming back a
>>> couple weeks after the fact.  We didn't really collect names of the
>>> people in attendance and I expect that a fair number of people
>>> registered attended the Gluster Conference.
>>>
>>
>> The linux foundation scanned all the participants tags, so I guess they
>> can supply the names.
>>
>>
>>>>
>>>> - Developer/user traction resulting from engaging at workshop
>>>> Did this workshop help us to gain new developers or users? Reinforce
>>>> relationships with existing community members?
>>>
>>> Only time will really tell here.  People definitely seemed interested
>>> and there were a couple people already downloading and installing the
>>> bits during the workshop.  I got the impression that most of the people
>>> there were more corporate focused -- Hitachi and Fujitsu were both well
>>> represented.  They're from companies that have previously expressed
>>> interest in the project.
>>>
>>
>>
>> Hard to tell,
>> I had a feeling that there was also a none developers group that came
>> also to learn about ovirt, more of the consultant type that actually
>> considering ovirt as an option.
>>
>>
>>>>
>>>> - Promotion of the event, both before and after
>>>> What could be done to more effectively promote the event prior to the
>>>> workshops? Videos and slides from the workshop should be posted on the
>>>> LC Japan site tomorrow; what action would the community like to take to
>>>> promote this content?
>>>
>>> Not really my area of expertise -- promoting.  Probably better to get
>>> information out there earlier that the workshop is happening.  It seemed
>>> to be a bit of a fire drill getting things together for this workshop
>>> since it was only about a month before that we decided to run it.
>>> Future workshops shouldn't be as big a deal.
>>>
>>
>>
>> I would say we need a lot of promotion, I was actually accessed by a few
>> people after the into presentation, saying they had no idea that ovirt
>> is so mature and feature reach.
>> This message should be conveyed before the workshop.
>>
>>
>>
>>> Probably an email announcement to users@ with a link to the
>>> presentations/videos is the right next step.
>>>>
>>>> - A/V and Room Set up
>>>> Did the seating arrangements work well for the workshop format? Did the
>>>> A/V work well, including the videotaping process?
>>>
>>> Our room was setup with 5 round tables seating 10 people each.  I'm not
>>> sure that it was really the right layout.  I expected either rows of
>>> chairs or long tables with chairs all facing the presentation screen.
>>>
>>> A/V worked seamlessly.  It was all setup already when we arrived.
>>>
>>
>>
>> I would agree with Mike on the room setup.
>> I would prefer facing the presentation rather than having to look aside.
>>
>> In addition and related to the preparations for the workshop,
>> Since it was setup so late, the linux foundation thought that setting
>> the workshop means canceling the mini-summit presentation slot.
>> So all the handouts&  schedule boards hanged around the summit did no
>> include this talk, anyway eventually they hanged a hand written schedule
>> update, but I assume more people would have come if they knew.
>>
>> The web schedule was updated.
>>
>>
>>>>
>>>> - Food and beverage
>>>> Did the catered in lunch help to keep the flow of the workshop
>>>> productive? Was the food of good quality and in keeping with the needs
>>>> of attendee dietary constraints?
>>>
>>> I had no issues with the food.  People seemed to take the opportunity
>>> more to step out and take a break, rather than sit and continue
>>> discussing.
>>>
>>
>> I agree
>>
>>>>
>>>> - Give aways
>>>> We did not produce attendee gifts for the oVirt workshop. Thoughts on
>>>> whether this would be a welcome addition in the future? Suggestions for
>>>> type of gift also welcome.
>>>
>>> It would have been nice to have some sort of SWAG to give away, whether
>>> just fancy handouts or stickers.  It would be even better if we could
>>> have some sort of appliance with ovirt pre-installed and configured on a
>>> usb stick as well, but that's probably a year or 2 down the road.
>>>
>>>>
>>>> - Any other feedback
>>>
>>> It's probably better if there are people from a wider range of the
>>> sub-projects than we had in Japan.  I think that between Barak and I, we
>>> managed to cover the majority of the project, but I think it would be
>>> better to have someone from each major subproject there.
>>>
>>> I expect that either myself or someone from the Node team will be
>>> attending at least LinuxCon NA, LinuxCon Europe and the NetApp
>>> workshops.  We'll certainly handle the Node presentation for each of
>>> these workshops.
>>>
>>
>>
>> It looks like ovirt&  gluster workshops will happen side by side in the
>> near future.
>> I don't know if this is possible but I would do the workshops in
>> different days (of the summit) so people that want to participate in
>> both workshops can do it.
>> I know for sure that in Japan many registered for both workshops
>>
>>
>>
>> Barak
>>
>>> Mike
>>>
>>>>
>>>> If it is preferable to discuss this feedback real-time, I will ask Mike
>>>> Burns to give us more time for this topic during next week's oVirt IRC
>>>> meeting.
>>>>
>>>> [0] -
>>>> https://events.linuxfoundation.org/events/linuxcon-japan/ovirt-gluster-workshops
>>>>
>>>> [1] - http://www.ovirt.org/wiki/OVirt_Global_Workshops
>>>>
>>>> Cheers,
>>>> LH
>>>>
>>>
>>>
>>> _______________________________________________
>>> Arch mailing list
>>> Arch at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/arch
>>>
>>>
>>
>> _______________________________________________
>> Arch mailing list
>> Arch at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/arch
>



From gkotton at redhat.com  Mon Jun 18 05:52:23 2012
From: gkotton at redhat.com (Gary Kotton)
Date: Mon, 18 Jun 2012 08:52:23 +0300
Subject: [oVirt][Quantum] question about quantum CLI
In-Reply-To: <CAAskrmFS51Yq0dgGFsyh+MHfFsU93Opr1bDyDm8LWbBo8dYDTA@mail.gmail.com>
References: <CAAskrmH2rXN_nbnoBqkyWHj_mEWNNMhZm-AwcRauJ558nfnobw@mail.gmail.com>	<4FD7022F.2040600@redhat.com>	<4FD70DA4.5000602@redhat.com>	<4FD724C8.8060506@redhat.com>	<CAAskrmHB61c+X+P39za85nQndN3j6YZ8O7uqX=p5TeQiOUmWCQ@mail.gmail.com>	<4FD82CE7.8090401@redhat.com>	<CAAskrmHHuc8E-sjddLM+sDkh2svszbNUa9L07ttNthjdzU3PJQ@mail.gmail.com>	<4FD861D0.3010902@redhat.com>	<CAAskrmGFmdiQ1tmhgJx7Zdoat2p4Q50TYEE7zoLbmS5uK8mNPw@mail.gmail.com>	<4FDAD21B.3030204@redhat.com>
	<CAAskrmFS51Yq0dgGFsyh+MHfFsU93Opr1bDyDm8LWbBo8dYDTA@mail.gmail.com>
Message-ID: <4FDEC217.5050805@redhat.com>

Hi,
Please see inline.
Thanks
Gary

On 06/18/2012 04:11 AM, Kris zhang wrote:
> Hi Kotton,
>
> Thanks for your detailed answer, and it's very clear, and i still have 
> some other questions:
>
> 1) Where i can find the database changes? please correct me if no 
> change in db.

At the moment in oVirt there are no database changes. The code that you 
are looking at is a POC. We (the community) still need to address the 
database changes.I think that prior to adding the database changes we 
should first add a REST client that can communicate with the Quantum 
service (at the moment this is done via the Quantum CLI). I have a short 
list of items that need to be addressed for a a basic Quantum 
integration (this will at least give us the infrastructure to build on 
in the future). I think that for the first phase we should support the 
following:

     - oVirt Engine will support one Quantum service (the instance 
currently supports only 1 plugin)
         - oVirt installation will have Quantum service as a dependency
     - All hosts in a cluster must have the same networking support. 
This can be one of the following:
         - Legacy oVirt networking
         - Legacy oVirt networking for management and Quantum for VM 
networking
     - When a VDSM host is registered (IP, password etc), one of the 
above methods will registered. If this Quantum, then the relevant 
configuration data will be sent to VDSM. Agent packages will exist on VDSM
     - If a logical network is assigned to a Quantum cluster then this 
network must be registered with Quantum (to get the UUID)
     - All VM's running on this cluster will receive a port ID and pass 
an attachment ID to the Quantum
     - Limitations:
         - No network statistics for logical quantum networks

I think that small secluded changes can help the integration - for example:-
     - implement a REST client (used to communicate with Quantum service)
     - update database to store relevant quantum ID's
     - improve VDMS support for Quantum code (have a plugin architecture 
- so that different technologies can plug their code into VDSM)
     - address HOST management
     - packaging

> 2) If the engine server crashed, then how to rebuild the network 
> information which generated by ovirt.sh script in the /tmp dir?

Please note that this is a POC. All of the data generated by the script 
is persistent - that is, it is stored in the /tmp directory. I am not 
really sure that I understand your question. If oVirt engine crashes 
then the user will not be able to deploy VM's. If the Quantum service 
crashes then the user should not be able to configure Quantum networks 
or attach ports etc.
If the quantum service crashes or is unreachable by VDSM then a newly 
deployed VM may not be able to "attach" to the Quantum network. This can 
be averted by having the following - on oVirt engine there should be a 
process that monitors the status of the Quantum service. If this is down 
then it should restart it. This can and should be discussed in more detail.
>
> In addition, originally i think the quantum port create is no any 
> relationship with vm create, and only be linked when a VIF of a VM 
> attach into a port. But your design is different, so there is no port 
> creation in the web UI, right?

My thinking is that when a VNIC of a VM is linked to a Quantum network 
then the Quantum port should be created. After some discussion I 
understand that the oVirt VNIC has a UUID - this can now be used as the 
attachment ID. In my opinion the Quantum interface should be limited to 
the host management. The rest should be "hidden" from the user.
>
> Best regards,
> Kris
>
>
>
> On Fri, Jun 15, 2012 at 2:11 PM, Gary Kotton <gkotton at redhat.com 
> <mailto:gkotton at redhat.com>> wrote:
>
>     Hi Kris,
>     You have asked a very interesting and good question. Please see
>     the answers an explanations below. Both flow are used. The "a"
>     flows (1a2a and 3a) are for the network management. The "b" flows
>     (1b and 2b) are for the VM management.
>     Network management (1a):
>         - user create a Quantum network
>         - user will create a Quantum port and attachment
>     VM Management (1b):
>         - users creates a VM
>         - assigned VM to one or more logical networks. Each each
>     assignment will receive the above quantum details
>     VM flow:
>         - VDSM creates the libvirt XML file
>             - (2b) if libvirt version is 0.9.10 or earlier then VDSM
>     will have to create the tap device (via attachment ID) and will
>     set it with type 'ethernet' in the libvirt file (this is what was
>     done in the POC). In addition this it need to notify OVS of the VM
>     ID on the port
>             - in later versions of libvirt, libvirt will do the create
>     via the attachment id
>         - VDSM will start the VM
>     Network flow (2a and 3a):
>         - The Quantum agent polls the Quantum plugin for network
>     changes. If the agent detects a tap device that is part of a
>     network then it will configure the characteristics of this tap
>     device on the OVS. In the case of the POC it will be the VLAN tag
>     of the network
>     Hope that I have answered your questions.
>     Thanks
>     Gary
>
>
>     On 06/14/2012 10:49 AM, Kris zhang wrote:
>>     Hi Kotton,
>>
>>     Thank your very much, and i still have a question:
>>
>>     There is a quantum.py file in
>>     the gkotton-vdsm_quantum-78427ca.zip. I saw there are some
>>     methods (For example: vifAddOpenVswitch() ) to call ovs-vsctl
>>     command, that means vdsm will control the ovs, not through ovs
>>     quantum agent?
>>
>>     The ovs quantum agent code is in the
>>     http://bazaar.launchpad.net/~netstack-core/quantum/essex/view/head:/quantum/plugins/openvswitch/agent/ovs_quantum_agent.py
>>     <http://bazaar.launchpad.net/%7Enetstack-core/quantum/essex/view/head:/quantum/plugins/openvswitch/agent/ovs_quantum_agent.py>
>>
>>
>>     Inline image 1
>>
>>     Please see above the image, and there are two ways:
>>
>>     First way: 1a, 2a, 3a.
>>     Second way: 1b, 2b
>>
>>     which way is used in POC?
>>
>>     Best regards,
>>     Kris
>>
>>
>>
>>     On Wed, Jun 13, 2012 at 5:48 PM, Gary Kotton <gkotton at redhat.com
>>     <mailto:gkotton at redhat.com>> wrote:
>>
>>         On 06/13/2012 11:57 AM, Kris zhang wrote:
>>>         Thanks for you detail answer, and please see the result of
>>>         the command quantum update_port,
>>         The command "quantum update_port" sets the state of the port.
>>         In the case of the ovirt.sh script this sets the port in
>>         ACTIVE state.
>>         The "user" is responsible for providing the attachment ID. In
>>         the case of the ovirt.sh script the ID is generated via uuidgen.
>>         Once you have generated a UUID for the attachment you need to
>>         pass this to quantum via the "quantum plug_iface".
>>>
>>>         Inline image 1
>>>
>>>         I run this script from the shell, and you can see there is
>>>         no an attachment UUID created. Can you show me your testing
>>>         result?
>>
>>         Please see below:
>>
>>         openstack at openstack:/tmp$ ./ovirt.sh network create Q_net
>>         openstack at openstack:/tmp$ ./ovirt.sh port create Q_net 12345678
>>         Updated Logical Port with ID:
>>         f9f203ab-dab6-4b9c-8dcf-561bcc698c76
>>         on Virtual Network: 8c50db01-54ef-4688-a274-9ab3fcfafe7d
>>         for tenant: default
>>         Plugged interface 24bf26c4-f8eb-46cd-a168-b7a25e64d5b2
>>         into Logical Port: f9f203ab-dab6-4b9c-8dcf-561bcc698c76
>>         on Virtual Network: 8c50db01-54ef-4688-a274-9ab3fcfafe7d
>>         for Tenant: default
>>         openstack at openstack:/tmp$
>>
>>
>>         openstack at openstack:/tmp$ ll
>>         total 40
>>         drwxrwxrwt  4 root      root      4096 2012-06-13 05:39 ./
>>         drwxr-xr-x 23 root      root      4096 2012-05-26 06:39 ../
>>         -rw-rw-r--  1 openstack openstack    6 2012-06-13 05:38
>>         network.12345678
>>         -rw-rw-r--  1 openstack openstack   37 2012-06-13 05:38
>>         network.Q_net
>>         -rw-rw-r--  1 openstack openstack   37 2012-06-13 05:38
>>         network.Q_net.12345678.port
>>         -rw-rw-r--  1 openstack openstack   37 2012-06-13 05:38
>>         network.Q_net.12345678.port.attach
>>         -rwxrwxrwx  1 openstack openstack 2097 2012-06-13 05:07 ovirt.sh*
>>         -rw-rw-r--  1 openstack openstack 1797 2012-06-13 05:38 ovirt.txt
>>
>>         openstack at openstack:/tmp$ cat network.Q_net.12345678.port.attach
>>         24bf26c4-f8eb-46cd-a168-b7a25e64d5b2
>>         openstack at openstack:/tmp$
>>
>>         Thanks
>>         Gary
>>
>>>
>>>         BR,
>>>         Kris
>>>
>>>
>>>         On Wed, Jun 13, 2012 at 2:02 PM, Gary Kotton
>>>         <gkotton at redhat.com <mailto:gkotton at redhat.com>> wrote:
>>>
>>>             Hi Kris,
>>>             Please see my answers and questions below.
>>>             Thanks
>>>             Gary
>>>
>>>
>>>             On 06/13/2012 07:31 AM, Kris zhang wrote:
>>>>             Hi Kotton,
>>>>
>>>>             In the file ovirt.sh, there is a line:
>>>
>>>             A bit of background regarding the script. The purpose of
>>>             the POC was to show that Quantum can be run in oVirt. It
>>>             would have been ideal to write a REST client that could
>>>             interface with the Quantum service. Due to the fact that
>>>             I was not familiar with the oVirt code I felt that a
>>>             quicker and more productive means was to invoke a bash
>>>             script from the oVirt engine code. The script would
>>>             invoke the quantum cli (this is a client that configures
>>>             the quantum server). In addition to this I did not want
>>>             to make any changes to the database schema. The result
>>>             was a script that does the following:
>>>             1. Logical Network Management:
>>>                 Create:
>>>                     ovirt.sh network create <name>
>>>                         - the name is the name of the logical
>>>             network (in the POC this is prefixed by "Q_"
>>>                         - this invokes the cli to create a network
>>>             called <name>
>>>                         - the UUID returned by the quantum service
>>>             will be save in /tmp/network.<name>
>>>                         - the above UUID is read when this logical
>>>             network is used (this in the future will be save in the
>>>             oVirt data base)
>>>                 Delete:
>>>                     ovirt.sh network remove <name>
>>>                         - the name is the name of the logical
>>>             network (in the POC this is prefixed by "Q_"
>>>                         - this invokes the cli to delete a network
>>>             called <name>
>>>                         - the file /tmp/network.<name> is deleted
>>>             2. VM Port management
>>>                 Create:
>>>                     ovirt.sh port create <net_name> <vmid>
>>>                         - the network name and the vm id are input
>>>             (the VM id is a key to be able to delete it all :))
>>>                         - the script does the following:
>>>                             - creates a port on the network. saves
>>>             the port id in /tmp/network.<name>.<vmid>.port
>>>                             - sets the state of the port to ACTIVE
>>>                             - creates an attachment ID (this is the
>>>             line that you had problems with). This is saved in
>>>             /tmp/network.<name>.<vmid>.attachment
>>>                             - saves the network name in a file
>>>             /tmp/network.<vmid>
>>>                             - the UUID's are read when the VM is
>>>             started so that they can be passed to VDSM
>>>                 Delete:
>>>                     ovirt.sh port remove <vmid>
>>>                         - using the vmid the network name is read =>
>>>             enables us to get all of the ID's to delete port in quantum
>>>                         - cleans all of the files
>>>             The script is called from the ovirt engine. Sorry for
>>>             the long winded explanation.
>>>
>>>
>>>>             quantum update_port default $NET_UUID $PORT_UUID
>>>>             state=ACTIVE
>>>>                             uuidgen > /tmp/network.$3.$4.port.attach
>>>>
>>>>             ATTACH_UUID=`cat /tmp/network.$3.$4.port.attach`
>>>
>>>             In Quantum the attachment ID is generated by the user.
>>>             The code above generates the attachment ID for the port.
>>>>
>>>>
>>>>             But i run this command, i found there is no any uuid
>>>>             generated, so what's the value of the ATTACH_UUID?
>>>             Do you run the script from the shell or is this run via
>>>             oVirt?
>>>             There is a log of all of the script command - can you
>>>             please look in /tmp/ovirt.txt - this may give us some clues.
>>>             You can run the script commands as described above. This
>>>             may also help.
>>>             Thanks
>>>             Gary
>>>
>>>>             Best regards,
>>>>             Kris
>>>>
>>>>
>>>>             On Tue, Jun 12, 2012 at 7:15 PM, Gary Kotton
>>>>             <gkotton at redhat.com <mailto:gkotton at redhat.com>> wrote:
>>>>
>>>>                 On 06/12/2012 12:36 PM, Itamar Heim wrote:
>>>>
>>>>                     On 06/12/2012 11:47 AM, Gary Kotton wrote:
>>>>
>>>>                         Hi Kris,
>>>>                         Thanks for the questions. Please see my
>>>>                         inline answers. I have also
>>>>                         cc'ed the ovirt arch mailing list.
>>>>                         Thanks
>>>>                         Gary
>>>>
>>>>                         On 06/12/2012 11:21 AM, Kris zhang wrote:
>>>>
>>>>                             Hi Gkotton,
>>>>
>>>>                             I have some questions:
>>>>
>>>>                             1) In the file "ovirt.sh", i found the
>>>>                             command quantum always use the
>>>>                             tenant "default", so if the ovirt don't
>>>>                             support multi-tenant?
>>>>
>>>>                         oVirt does not support multi tenancy at the
>>>>                         moment. Maybe there are
>>>>                         people on the list who can provide more
>>>>                         details about this. The initial
>>>>                         plan was to use the "default" tenant.
>>>>
>>>>
>>>>                     ovirt supports multiple users and an RBAC model
>>>>                     for permissions between these users.
>>>>                     what exactly are you looking for?
>>>>
>>>>                 Quantum support multi tenancy. The integration with
>>>>                 oVirt was done with the "default" tenant. This is a
>>>>                 different model to that of oVirt.
>>>>                 Thanks
>>>>                 Gary
>>>>
>>>>
>>>
>>>
>>
>>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120618/2b022755/attachment.html>

From mburns at redhat.com  Mon Jun 18 11:59:09 2012
From: mburns at redhat.com (Mike Burns)
Date: Mon, 18 Jun 2012 07:59:09 -0400
Subject: Call For Agenda Items -- oVirt Weekly Meeting 2012-06-20
Message-ID: <1340020749.3734.33.camel@beelzebub.mburnsfire.net>

The next oVirt Weekly Meeting is scheduled for 2012-06-20 at 15:00 UTC
(10:00 AM EDT).

Current Agenda Items (as of this email)

* Status of Next Release
* Sub-project reports (engine, vdsm, node)
* Upcoming workshops
* Test Day Post-Mortem

Latest Agenda is listed here:
http://www.ovirt.org/wiki/Meetings#Weekly_project_sync_meeting

Reminder:  If you propose an additional agenda item, please be present
for the meeting to lead the discussion on it.

Thanks

Mike



From ryanh at us.ibm.com  Mon Jun 18 13:42:55 2012
From: ryanh at us.ibm.com (Ryan Harper)
Date: Mon, 18 Jun 2012 08:42:55 -0500
Subject: ovirt f17 beta repo
In-Reply-To: <4FDCB92D.6080809@redhat.com>
References: <20120615195352.GN9959@frylock.austin.ibm.com>
	<4FDCB92D.6080809@redhat.com>
Message-ID: <20120618134255.GP9959@frylock.austin.ibm.com>

* Juan Hernandez <juan.hernandez at redhat.com> [2012-06-16 12:08]:
> On 06/15/2012 09:53 PM, Ryan Harper wrote:
> >I saw a discussion on #ovirt about how the build system is supposed to
> >increment the _XXXX past the version but that's not happening.  Well,
> >newer rpms are now posted to the repo, but because the
> >version is the same expect for the githash, it won't upgrade.  Can we
> >get this fixed[1]?
> 
> In my opinion the version number of the RPM should not include that
> _XXXX suffix. We should build packages using the numbering schema
> recommended for snapshot and pre-release packages here:
> 
> http://fedoraproject.org/wiki/Packaging:NamingGuidelines#Release_Tag
> 
> So the pre-release numbers should be something like this:
> 
> 3.1.0-0.1.20120615git0a4333
> 3.1.0-0.2.20120618git94a365
> ...
> 
> That way the day we do the release we can change to this numbering:
> 
> 3.1.0-1
> 3.1.0-2
> ...
> 
> And any release number will be greater than any pre-release number.

+1 

So, how do we enact this change?


> 
> >[root at ichigo-dom234 ~]# ls *.rpm
> >ovirt-engine-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> >ovirt-engine-backend-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> >ovirt-engine-config-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> >ovirt-engine-dbscripts-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> >ovirt-engine-genericapi-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> >ovirt-engine-notification-service-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> >ovirt-engine-restapi-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> >ovirt-engine-setup-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> >ovirt-engine-tools-common-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> >ovirt-engine-userportal-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> >ovirt-engine-webadmin-portal-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> >[root at ichigo-dom234 ~]# rpm -Uvh --test *.rpm
> >Preparing...                ########################################### [100%]
> >     package ovirt-engine-backend-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-backend-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
> >     package ovirt-engine-dbscripts-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-dbscripts-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
> >     package ovirt-engine-genericapi-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-genericapi-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
> >     package ovirt-engine-restapi-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-restapi-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
> >     package ovirt-engine-setup-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-setup-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
> >     package ovirt-engine-config-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-config-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
> >     package ovirt-engine-notification-service-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-notification-service-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
> >     package ovirt-engine-tools-common-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-tools-common-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
> >     package ovirt-engine-userportal-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-userportal-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
> >     package ovirt-engine-webadmin-portal-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-webadmin-portal-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
> >     package ovirt-engine-3.1.0_0001-0.gitf093e0.fc17.noarch (which is newer than ovirt-engine-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already installed
> >
> >
> >1. I know I can --nodeps --force to get this to work.
> >
> 
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh at us.ibm.com



From danken at redhat.com  Mon Jun 18 14:28:49 2012
From: danken at redhat.com (Dan Kenigsberg)
Date: Mon, 18 Jun 2012 17:28:49 +0300
Subject: http://www.ovirt.org/wiki/Intercall issues
In-Reply-To: <4FDF304F.1090004@middleswarth.net>
References: <20120617180428.GA10904@redhat.com>
	<4FDF2D9D.1010700@linux.vnet.ibm.com>
	<4FDF304F.1090004@middleswarth.net>
Message-ID: <20120618142848.GB12442@redhat.com>

On Mon, Jun 18, 2012 at 09:42:39AM -0400, Robert Middleswarth wrote:
> From the US I am getting the conf number is invald?
> 

<snip>

> >>
> >Hello Dan,
> >     The India dial in ...
> >India Dial-In #: 000-800-650-1533
> >
> >never works.. so I am unable to connect to this call from home.
> >I cannot use the other India number as that is not supported for
> >my telecom carrier.
> >
> >Who can help in resolving this issue. The above number always
> >results in a 'engage' tone.
> >It never asks for conf. id.

I suppose arch at ovirt.org (CCed) could be more helpful in this regard.

Dan.


From zhang.kris at gmail.com  Wed Jun 13 04:31:26 2012
From: zhang.kris at gmail.com (Kris zhang)
Date: Wed, 13 Jun 2012 12:31:26 +0800
Subject: [oVirt][Quantum] question about quantum CLI
In-Reply-To: <4FD724C8.8060506@redhat.com>
References: <CAAskrmH2rXN_nbnoBqkyWHj_mEWNNMhZm-AwcRauJ558nfnobw@mail.gmail.com>
	<4FD7022F.2040600@redhat.com> <4FD70DA4.5000602@redhat.com>
	<4FD724C8.8060506@redhat.com>
Message-ID: <CAAskrmHB61c+X+P39za85nQndN3j6YZ8O7uqX=p5TeQiOUmWCQ@mail.gmail.com>

Hi Kotton,

In the file ovirt.sh, there is a line:

quantum update_port default $NET_UUID $PORT_UUID state=ACTIVE
                uuidgen > /tmp/network.$3.$4.port.attach
ATTACH_UUID=`cat /tmp/network.$3.$4.port.attach`


But i run this command, i found there is no any uuid generated, so what's
the value of the ATTACH_UUID?

Best regards,
Kris


On Tue, Jun 12, 2012 at 7:15 PM, Gary Kotton <gkotton at redhat.com> wrote:

> On 06/12/2012 12:36 PM, Itamar Heim wrote:
>
>> On 06/12/2012 11:47 AM, Gary Kotton wrote:
>>
>>> Hi Kris,
>>> Thanks for the questions. Please see my inline answers. I have also
>>> cc'ed the ovirt arch mailing list.
>>> Thanks
>>> Gary
>>>
>>> On 06/12/2012 11:21 AM, Kris zhang wrote:
>>>
>>>> Hi Gkotton,
>>>>
>>>> I have some questions:
>>>>
>>>> 1) In the file "ovirt.sh", i found the command quantum always use the
>>>> tenant "default", so if the ovirt don't support multi-tenant?
>>>>
>>> oVirt does not support multi tenancy at the moment. Maybe there are
>>> people on the list who can provide more details about this. The initial
>>> plan was to use the "default" tenant.
>>>
>>
>> ovirt supports multiple users and an RBAC model for permissions between
>> these users.
>> what exactly are you looking for?
>>
> Quantum support multi tenancy. The integration with oVirt was done with
> the "default" tenant. This is a different model to that of oVirt.
> Thanks
> Gary
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120613/3eaa5571/attachment.html>

From zhang.kris at gmail.com  Wed Jun 13 08:57:06 2012
From: zhang.kris at gmail.com (Kris zhang)
Date: Wed, 13 Jun 2012 16:57:06 +0800
Subject: [oVirt][Quantum] question about quantum CLI
In-Reply-To: <4FD82CE7.8090401@redhat.com>
References: <CAAskrmH2rXN_nbnoBqkyWHj_mEWNNMhZm-AwcRauJ558nfnobw@mail.gmail.com>
	<4FD7022F.2040600@redhat.com> <4FD70DA4.5000602@redhat.com>
	<4FD724C8.8060506@redhat.com>
	<CAAskrmHB61c+X+P39za85nQndN3j6YZ8O7uqX=p5TeQiOUmWCQ@mail.gmail.com>
	<4FD82CE7.8090401@redhat.com>
Message-ID: <CAAskrmHHuc8E-sjddLM+sDkh2svszbNUa9L07ttNthjdzU3PJQ@mail.gmail.com>

Thanks for you detail answer, and please see the result of the command
quantum update_port,

[image: Inline image 1]

I run this script from the shell, and you can see there is no an attachment
UUID created. Can you show me your testing result?

BR,
Kris


On Wed, Jun 13, 2012 at 2:02 PM, Gary Kotton <gkotton at redhat.com> wrote:

> **
> Hi Kris,
> Please see my answers and questions below.
> Thanks
> Gary
>
>
> On 06/13/2012 07:31 AM, Kris zhang wrote:
>
> Hi Kotton,
>
>  In the file ovirt.sh, there is a line:
>
>
> A bit of background regarding the script. The purpose of the POC was to
> show that Quantum can be run in oVirt. It would have been ideal to write a
> REST client that could interface with the Quantum service. Due to the fact
> that I was not familiar with the oVirt code I felt that a quicker and more
> productive means was to invoke a bash script from the oVirt engine code.
> The script would invoke the quantum cli (this is a client that configures
> the quantum server). In addition to this I did not want to make any changes
> to the database schema. The result was a script that does the following:
> 1. Logical Network Management:
>     Create:
>         ovirt.sh network create <name>
>             - the name is the name of the logical network (in the POC this
> is prefixed by "Q_"
>             - this invokes the cli to create a network called <name>
>             - the UUID returned by the quantum service will be save in
> /tmp/network.<name>
>             - the above UUID is read when this logical network is used
> (this in the future will be save in the oVirt data base)
>     Delete:
>         ovirt.sh network remove <name>
>             - the name is the name of the logical network (in the POC this
> is prefixed by "Q_"
>             - this invokes the cli to delete a network called <name>
>             - the file /tmp/network.<name> is deleted
> 2. VM Port management
>     Create:
>         ovirt.sh port create <net_name> <vmid>
>             - the network name and the vm id are input (the VM id is a key
> to be able to delete it all :))
>             - the script does the following:
>                 - creates a port on the network. saves the port id in
> /tmp/network.<name>.<vmid>.port
>                 - sets the state of the port to ACTIVE
>                 - creates an attachment ID (this is the line that you had
> problems with). This is saved in /tmp/network.<name>.<vmid>.attachment
>                 - saves the network name in a file /tmp/network.<vmid>
>                 - the UUID's are read when the VM is started so that they
> can be passed to VDSM
>     Delete:
>         ovirt.sh port remove <vmid>
>             - using the vmid the network name is read => enables us to get
> all of the ID's to delete port in quantum
>             - cleans all of the files
> The script is called from the ovirt engine. Sorry for the long winded
> explanation.
>
>
>  quantum update_port default $NET_UUID $PORT_UUID state=ACTIVE
>                 uuidgen > /tmp/network.$3.$4.port.attach
>  ATTACH_UUID=`cat /tmp/network.$3.$4.port.attach`
>
>
> In Quantum the attachment ID is generated by the user. The code above
> generates the attachment ID for the port.
>
>
>
>  But i run this command, i found there is no any uuid generated, so
> what's the value of the ATTACH_UUID?
>
> Do you run the script from the shell or is this run via oVirt?
> There is a log of all of the script command - can you please look in
> /tmp/ovirt.txt - this may give us some clues.
> You can run the script commands as described above. This may also help.
> Thanks
> Gary
>
>  Best regards,
> Kris
>
>
> On Tue, Jun 12, 2012 at 7:15 PM, Gary Kotton <gkotton at redhat.com> wrote:
>
>>  On 06/12/2012 12:36 PM, Itamar Heim wrote:
>>
>>> On 06/12/2012 11:47 AM, Gary Kotton wrote:
>>>
>>>> Hi Kris,
>>>> Thanks for the questions. Please see my inline answers. I have also
>>>> cc'ed the ovirt arch mailing list.
>>>> Thanks
>>>> Gary
>>>>
>>>> On 06/12/2012 11:21 AM, Kris zhang wrote:
>>>>
>>>>> Hi Gkotton,
>>>>>
>>>>> I have some questions:
>>>>>
>>>>> 1) In the file "ovirt.sh", i found the command quantum always use the
>>>>> tenant "default", so if the ovirt don't support multi-tenant?
>>>>>
>>>> oVirt does not support multi tenancy at the moment. Maybe there are
>>>> people on the list who can provide more details about this. The initial
>>>> plan was to use the "default" tenant.
>>>>
>>>
>>> ovirt supports multiple users and an RBAC model for permissions between
>>> these users.
>>> what exactly are you looking for?
>>>
>>  Quantum support multi tenancy. The integration with oVirt was done with
>> the "default" tenant. This is a different model to that of oVirt.
>> Thanks
>> Gary
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120613/7c6250a4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 53568 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120613/7c6250a4/attachment.png>

From nathan at robotics.net  Wed Jun 13 15:29:38 2012
From: nathan at robotics.net (Nathan Stratton)
Date: Wed, 13 Jun 2012 10:29:38 -0500 (CDT)
Subject: [Users] What are you looking for from oVirt?
In-Reply-To: <4FD8A370.3010904@redhat.com>
References: <4FD8A370.3010904@redhat.com>
Message-ID: <alpine.LFD.2.02.1206131022360.14212@bart.robotics.net>

On Wed, 13 Jun 2012, Dave Neary wrote:

> So - how are you using oVirt? Why did you choose it over alternatives? What 
> do you like about it? and what would you like to see change, whether that is 
> in terms of technical, process, or marketing changes? I'm here to help, but 
> to do so I need your help first!

Small private cloud deployments. We choose it because it was focused on 
KVM, RedHat driven, simple to manage, and libvirt based. Would love to see 
real glusterfs integration, quantum integration, and better API.

><>
Nathan Stratton
nathan at robotics.net
http://www.robotics.net


From nathan at robotics.net  Wed Jun 13 15:57:35 2012
From: nathan at robotics.net (Nathan Stratton)
Date: Wed, 13 Jun 2012 10:57:35 -0500 (CDT)
Subject: [Users] What are you looking for from oVirt?
In-Reply-To: <4be4bce7-c983-4bbe-9841-1c0f2cf095b9@zmail07.collab.prod.int.phx2.redhat.com>
References: <4be4bce7-c983-4bbe-9841-1c0f2cf095b9@zmail07.collab.prod.int.phx2.redhat.com>
Message-ID: <alpine.LFD.2.02.1206131034060.18569@bart.robotics.net>

On Wed, 13 Jun 2012, Andrew Cathrow wrote:

> What does your deployment look like - it's be great to understand how you're using it - eg. Linux guests only, Windows, size of deployment - do your users use poweruser portal etc.

I have 2 deployments I am working on with two different companies.

The first is two clusters (SJC and NYC) each with 20 boxes PXEBooted to 
a backend NetApp. All guests are Linux (Centos, RHEL, and Fedora). One of 
the unique things with the clusters is they use read only linux and NFS 
root.

The 2nd is still in design stage, but is starting out with 3 clusters 
(East / West US and Europe) each with 20 boxes. Each server is based on 
white label Xeon E5-2687W, 128GB RAM, 10GBase-T, and 12 SATA disks on a 
hardware RAID 6 controller. This is also going to use shared NFS read only 
root with PXEBoot from NetApps.

I have been running GlusterFS on and off for 5 years and are looking at 
running GlusterFS on all the raw 300TB RAID6 in each server. Each server 
will be a brick, two servers with distribute for redundancy, 10 
distribute pairs then will be unified. I have been trying to use this for 
raw image store for years, but its just not ready, so we will use NetApp 
for that, however GlusterFS will be very handy for tier 2 bulk storage.

> GlusterFS and Quantum are certainly in the works, but in a separate thread I'd love to hear feedback on the API what the issues/enhancements are.
> Would you be able to post some initial comments on that?

APIs are great today on the backend, we are looking at the ability to 
modify the front end so we can tie it into our portal allowing users to 
manage their VMs seamless with the other services we offer.

><>
Nathan Stratton
nathan at robotics.net
http://www.robotics.net


From zhang.kris at gmail.com  Thu Jun 14 07:49:49 2012
From: zhang.kris at gmail.com (Kris zhang)
Date: Thu, 14 Jun 2012 15:49:49 +0800
Subject: [oVirt][Quantum] question about quantum CLI
In-Reply-To: <4FD861D0.3010902@redhat.com>
References: <CAAskrmH2rXN_nbnoBqkyWHj_mEWNNMhZm-AwcRauJ558nfnobw@mail.gmail.com>
	<4FD7022F.2040600@redhat.com> <4FD70DA4.5000602@redhat.com>
	<4FD724C8.8060506@redhat.com>
	<CAAskrmHB61c+X+P39za85nQndN3j6YZ8O7uqX=p5TeQiOUmWCQ@mail.gmail.com>
	<4FD82CE7.8090401@redhat.com>
	<CAAskrmHHuc8E-sjddLM+sDkh2svszbNUa9L07ttNthjdzU3PJQ@mail.gmail.com>
	<4FD861D0.3010902@redhat.com>
Message-ID: <CAAskrmGFmdiQ1tmhgJx7Zdoat2p4Q50TYEE7zoLbmS5uK8mNPw@mail.gmail.com>

Hi Kotton,

Thank your very much, and i still have a question:

There is a quantum.py file in the gkotton-vdsm_quantum-78427ca.zip. I saw
there are some methods (For example: vifAddOpenVswitch() ) to call
ovs-vsctl command, that means vdsm will control the ovs, not through ovs
quantum agent?

The ovs quantum agent code is in the
http://bazaar.launchpad.net/~netstack-core/quantum/essex/view/head:/quantum/plugins/openvswitch/agent/ovs_quantum_agent.py


[image: Inline image 1]

Please see above the image, and there are two ways:

First way: 1a, 2a, 3a.
Second way: 1b, 2b

which way is used in POC?

Best regards,
Kris



On Wed, Jun 13, 2012 at 5:48 PM, Gary Kotton <gkotton at redhat.com> wrote:

> **
> On 06/13/2012 11:57 AM, Kris zhang wrote:
>
> Thanks for you detail answer, and please see the result of the command
> quantum update_port,
>
> The command "quantum update_port" sets the state of the port. In the case
> of the ovirt.sh script this sets the port in ACTIVE state.
> The "user" is responsible for providing the attachment ID. In the case of
> the ovirt.sh script the ID is generated via uuidgen.
> Once you have generated a UUID for the attachment you need to pass this to
> quantum via the "quantum plug_iface".
>
>
>  [image: Inline image 1]
>
>  I run this script from the shell, and you can see there is no an
> attachment UUID created. Can you show me your testing result?
>
>
> Please see below:
>
> openstack at openstack:/tmp$ ./ovirt.sh network create Q_net
> openstack at openstack:/tmp$ ./ovirt.sh port create Q_net 12345678
> Updated Logical Port with ID: f9f203ab-dab6-4b9c-8dcf-561bcc698c76
> on Virtual Network: 8c50db01-54ef-4688-a274-9ab3fcfafe7d
> for tenant: default
> Plugged interface 24bf26c4-f8eb-46cd-a168-b7a25e64d5b2
> into Logical Port: f9f203ab-dab6-4b9c-8dcf-561bcc698c76
> on Virtual Network: 8c50db01-54ef-4688-a274-9ab3fcfafe7d
> for Tenant: default
> openstack at openstack:/tmp$
>
>
> openstack at openstack:/tmp$ ll
> total 40
> drwxrwxrwt  4 root      root      4096 2012-06-13 05:39 ./
> drwxr-xr-x 23 root      root      4096 2012-05-26 06:39 ../
> -rw-rw-r--  1 openstack openstack    6 2012-06-13 05:38 network.12345678
> -rw-rw-r--  1 openstack openstack   37 2012-06-13 05:38 network.Q_net
> -rw-rw-r--  1 openstack openstack   37 2012-06-13 05:38
> network.Q_net.12345678.port
> -rw-rw-r--  1 openstack openstack   37 2012-06-13 05:38
> network.Q_net.12345678.port.attach
> -rwxrwxrwx  1 openstack openstack 2097 2012-06-13 05:07 ovirt.sh*
> -rw-rw-r--  1 openstack openstack 1797 2012-06-13 05:38 ovirt.txt
>
> openstack at openstack:/tmp$ cat network.Q_net.12345678.port.attach
> 24bf26c4-f8eb-46cd-a168-b7a25e64d5b2
> openstack at openstack:/tmp$
>
> Thanks
> Gary
>
>
>  BR,
> Kris
>
>
> On Wed, Jun 13, 2012 at 2:02 PM, Gary Kotton <gkotton at redhat.com> wrote:
>
>>  Hi Kris,
>> Please see my answers and questions below.
>> Thanks
>> Gary
>>
>>
>> On 06/13/2012 07:31 AM, Kris zhang wrote:
>>
>> Hi Kotton,
>>
>>  In the file ovirt.sh, there is a line:
>>
>>
>>  A bit of background regarding the script. The purpose of the POC was to
>> show that Quantum can be run in oVirt. It would have been ideal to write a
>> REST client that could interface with the Quantum service. Due to the fact
>> that I was not familiar with the oVirt code I felt that a quicker and more
>> productive means was to invoke a bash script from the oVirt engine code.
>> The script would invoke the quantum cli (this is a client that configures
>> the quantum server). In addition to this I did not want to make any changes
>> to the database schema. The result was a script that does the following:
>> 1. Logical Network Management:
>>     Create:
>>         ovirt.sh network create <name>
>>             - the name is the name of the logical network (in the POC
>> this is prefixed by "Q_"
>>             - this invokes the cli to create a network called <name>
>>             - the UUID returned by the quantum service will be save in
>> /tmp/network.<name>
>>             - the above UUID is read when this logical network is used
>> (this in the future will be save in the oVirt data base)
>>     Delete:
>>         ovirt.sh network remove <name>
>>             - the name is the name of the logical network (in the POC
>> this is prefixed by "Q_"
>>             - this invokes the cli to delete a network called <name>
>>             - the file /tmp/network.<name> is deleted
>> 2. VM Port management
>>     Create:
>>         ovirt.sh port create <net_name> <vmid>
>>             - the network name and the vm id are input (the VM id is a
>> key to be able to delete it all :))
>>             - the script does the following:
>>                 - creates a port on the network. saves the port id in
>> /tmp/network.<name>.<vmid>.port
>>                 - sets the state of the port to ACTIVE
>>                 - creates an attachment ID (this is the line that you had
>> problems with). This is saved in /tmp/network.<name>.<vmid>.attachment
>>                 - saves the network name in a file /tmp/network.<vmid>
>>                 - the UUID's are read when the VM is started so that they
>> can be passed to VDSM
>>     Delete:
>>         ovirt.sh port remove <vmid>
>>             - using the vmid the network name is read => enables us to
>> get all of the ID's to delete port in quantum
>>             - cleans all of the files
>> The script is called from the ovirt engine. Sorry for the long winded
>> explanation.
>>
>>
>>  quantum update_port default $NET_UUID $PORT_UUID state=ACTIVE
>>                 uuidgen > /tmp/network.$3.$4.port.attach
>>  ATTACH_UUID=`cat /tmp/network.$3.$4.port.attach`
>>
>>
>>  In Quantum the attachment ID is generated by the user. The code above
>> generates the attachment ID for the port.
>>
>>
>>
>>  But i run this command, i found there is no any uuid generated, so
>> what's the value of the ATTACH_UUID?
>>
>>  Do you run the script from the shell or is this run via oVirt?
>> There is a log of all of the script command - can you please look in
>> /tmp/ovirt.txt - this may give us some clues.
>> You can run the script commands as described above. This may also help.
>> Thanks
>> Gary
>>
>>  Best regards,
>> Kris
>>
>>
>> On Tue, Jun 12, 2012 at 7:15 PM, Gary Kotton <gkotton at redhat.com> wrote:
>>
>>>  On 06/12/2012 12:36 PM, Itamar Heim wrote:
>>>
>>>> On 06/12/2012 11:47 AM, Gary Kotton wrote:
>>>>
>>>>> Hi Kris,
>>>>> Thanks for the questions. Please see my inline answers. I have also
>>>>> cc'ed the ovirt arch mailing list.
>>>>> Thanks
>>>>> Gary
>>>>>
>>>>> On 06/12/2012 11:21 AM, Kris zhang wrote:
>>>>>
>>>>>> Hi Gkotton,
>>>>>>
>>>>>> I have some questions:
>>>>>>
>>>>>> 1) In the file "ovirt.sh", i found the command quantum always use the
>>>>>> tenant "default", so if the ovirt don't support multi-tenant?
>>>>>>
>>>>> oVirt does not support multi tenancy at the moment. Maybe there are
>>>>> people on the list who can provide more details about this. The initial
>>>>> plan was to use the "default" tenant.
>>>>>
>>>>
>>>> ovirt supports multiple users and an RBAC model for permissions between
>>>> these users.
>>>> what exactly are you looking for?
>>>>
>>>  Quantum support multi tenancy. The integration with oVirt was done
>>> with the "default" tenant. This is a different model to that of oVirt.
>>> Thanks
>>> Gary
>>>
>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120614/374d735b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 172132 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120614/374d735b/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 53568 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120614/374d735b/attachment-0001.png>

From richardsh at att.net  Thu Jun 14 14:13:07 2012
From: richardsh at att.net (richardsh at att.net)
Date: Thu, 14 Jun 2012 09:13:07 -0500
Subject: Returned mail: see transcript for details
Message-ID: <mailman.0.1481783056.32024.arch@ovirt.org>

The original message was received at Thu, 14 Jun 2012 09:13:07 -0500
from att.net [182.247.23.138]

----- The following addresses had permanent fatal errors -----
<arch at ovirt.org>



-------------- next part --------------
A non-text attachment was scrubbed...
Name: letter.zip
Type: application/octet-stream
Size: 28982 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120614/f3558ff5/attachment.obj>

From t.konishi at seirei.ne.jp  Fri Jun 15 07:13:10 2012
From: t.konishi at seirei.ne.jp (=?ISO-2022-JP?B?GyRCPi5APjknPSEbKEI=?=)
Date: Fri, 15 Jun 2012 16:13:10 +0900
Subject: What are you looking for from oVirt?
In-Reply-To: <4FD8A370.3010904@redhat.com>
References: <4FD8A370.3010904@redhat.com>
Message-ID: <CAGuFwMpaFpWmvH2r5TaXQA7EE3ou9ryioOb3hCrs83JY_Abhbg@mail.gmail.com>

Hi Dave, everyone

I have run a Web Hosting from 10 years ago.
I integrated the Web Hosting server with KVM 2 years ago.
I thought I tried to offer the VPS server which was rare in Japan,
using the remaining resources.

I am a server engineer, not a programmer.
Regrettably, VPS market has stabilized at a low price while I spent
much time in programming the "Administrator Portal" and "User Portal".

However, the VPS and the cloud have restrictions even now.
 * Can not use your favorite OS.(That can only be used a template)
 * Can not strengthen by focusing on specific performance.
I want to provide services which improve this issue

I do not have money to buy expensive software, such as RHEV.
When I started to give up the dream, I found a oVirt.
Now, I am studying the feasibility of a dream by oVirt.
I hope to be able to concentrate on infrastructure design without
programming by oVirt


However I feel that there is not enough stability yet if VPS is
provided with oVirt version for now.
oVirt community has companies such as RedHat.
I believe that the operation of the oVirt will be  stable in the
version of near future.

I was late in the VPS market.
I have "chagrin" in the VPS market.
I want to be a pioneer in Japan as that does  not  happen in oVirt.

Therefore, I forward preparing offers of VPS using oVirt in the fall.

I hope "the Japanese translation" and "stabilization" of oVirt than
new features.

thanks.

P.S.
I seek the formation of Japanese community in order to become one of
the pioneers.


---------------------------------------------------------------------
SeireiNetwork
 representative director : Takamune Konishi

19F HiltonPlazaWest 2-2-2 Umeda Kita-ku
Osaka Japan

Corp http://seirei.ne.jp/
Blog http://konishi.me/ <= oVirt Install Guide
ISP http://vpos.seirei.ne.jp/
WebHosting http://seirei.ath.cx/

tel +81-6-7494-6690
---------------------------------------------------------------------

2012/6/13 Dave Neary <dneary at redhat.com>:
> Hi everyone,
>
> That is a grand subject for my first "proper" email to the Users list, and
> it definitely needs some context! So let me introduce myself.
>
> My name is Dave Neary, and I recently started working for a group which is
> being formed inside Red Hat called OSAS (open source and standards). The
> role of my group is to help make any open source projects that Red Hat works
> in successful, and I would really like to help take oVirt to the next level
> in terms of adoption and contribution.
>
> One of the things I'm still figuring out is what the natural audience for
> oVirt is, and what you all like about oVirt, and would like to see improved.
> Based on that, I would like to propose areas we as a community can
> concentrate on related to the product, the website, and our marketing and
> promotion, but the first step is still to get a better idea what the target
> audience for oVirt is, and should be.
>
> So - how are you using oVirt? Why did you choose it over alternatives? What
> do you like about it? and what would you like to see change, whether that is
> in terms of technical, process, or marketing changes? I'm here to help, but
> to do so I need your help first!
>
> Please feel free to reply to me on-list (if you'd like to start discussion)
> or off-list (if you'd like your feedback to be more discrete). Any feedback
> at all will be helpful.
>
> Thank you very much - I look forward to hearing from as many of you as
> possible.
>
> Regards,
> Dave.
>
> PS. I'm still figuring out proper mailing list etiquette for this project -
> I've added board@ and arch@ to CC since I expect our work to have
> project-wide consequences, but it's more to keep people informed at this
> point. Please let me know off-list if I'm doing something I shouldn't!
>
> --
> Dave Neary
> Community Action and Impact
> Open Source and Standards Team, Red Hat
> Phone: +33 9 50 71 55 62
> _______________________________________________
> Board mailing list
> Board at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/board


From zhang.kris at gmail.com  Mon Jun 18 01:11:54 2012
From: zhang.kris at gmail.com (Kris zhang)
Date: Mon, 18 Jun 2012 09:11:54 +0800
Subject: [oVirt][Quantum] question about quantum CLI
In-Reply-To: <4FDAD21B.3030204@redhat.com>
References: <CAAskrmH2rXN_nbnoBqkyWHj_mEWNNMhZm-AwcRauJ558nfnobw@mail.gmail.com>
	<4FD7022F.2040600@redhat.com> <4FD70DA4.5000602@redhat.com>
	<4FD724C8.8060506@redhat.com>
	<CAAskrmHB61c+X+P39za85nQndN3j6YZ8O7uqX=p5TeQiOUmWCQ@mail.gmail.com>
	<4FD82CE7.8090401@redhat.com>
	<CAAskrmHHuc8E-sjddLM+sDkh2svszbNUa9L07ttNthjdzU3PJQ@mail.gmail.com>
	<4FD861D0.3010902@redhat.com>
	<CAAskrmGFmdiQ1tmhgJx7Zdoat2p4Q50TYEE7zoLbmS5uK8mNPw@mail.gmail.com>
	<4FDAD21B.3030204@redhat.com>
Message-ID: <CAAskrmFS51Yq0dgGFsyh+MHfFsU93Opr1bDyDm8LWbBo8dYDTA@mail.gmail.com>

Hi Kotton,

Thanks for your detailed answer, and it's very clear, and i still have some
other questions:

1) Where i can find the database changes? please correct me if no change in
db.

2) If the engine server crashed, then how to rebuild the network
information which generated by ovirt.sh script in the /tmp dir?

In addition, originally i think the quantum port create is no any
relationship with vm create, and only be linked when a VIF of a VM attach
into a port. But your design is different, so there is no port creation in
the web UI, right?

Best regards,
Kris



On Fri, Jun 15, 2012 at 2:11 PM, Gary Kotton <gkotton at redhat.com> wrote:

> **
> Hi Kris,
> You have asked a very interesting and good question. Please see the
> answers an explanations below. Both flow are used. The "a" flows (1a2a and
> 3a) are for the network management. The "b" flows (1b and 2b) are for the
> VM management.
> Network management (1a):
>     - user create a Quantum network
>     - user will create a Quantum port and attachment
> VM Management (1b):
>     - users creates a VM
>     - assigned VM to one or more logical networks. Each each assignment
> will receive the above quantum details
> VM flow:
>     - VDSM creates the libvirt XML file
>         - (2b) if libvirt version is 0.9.10 or earlier then VDSM will have
> to create the tap device (via attachment ID) and will set it with type
> 'ethernet' in the libvirt file (this is what was done in the POC). In
> addition this it need to notify OVS of the VM ID on the port
>         - in later versions of libvirt, libvirt will do the create via the
> attachment id
>     - VDSM will start the VM
> Network flow (2a and 3a):
>     - The Quantum agent polls the Quantum plugin for network changes. If
> the agent detects a tap device that is part of a network then it will
> configure the characteristics of this tap device on the OVS. In the case of
> the POC it will be the VLAN tag of the network
> Hope that I have answered your questions.
> Thanks
> Gary
>
>
> On 06/14/2012 10:49 AM, Kris zhang wrote:
>
> Hi Kotton,
>
>  Thank your very much, and i still have a question:
>
>  There is a quantum.py file in the gkotton-vdsm_quantum-78427ca.zip. I
> saw there are some methods (For example: vifAddOpenVswitch() ) to call
> ovs-vsctl command, that means vdsm will control the ovs, not through ovs
> quantum agent?
>
>  The ovs quantum agent code is in the
> http://bazaar.launchpad.net/~netstack-core/quantum/essex/view/head:/quantum/plugins/openvswitch/agent/ovs_quantum_agent.py
>
>
>  [image: Inline image 1]
>
>  Please see above the image, and there are two ways:
>
>  First way: 1a, 2a, 3a.
>  Second way: 1b, 2b
>
>  which way is used in POC?
>
>  Best regards,
> Kris
>
>
>
> On Wed, Jun 13, 2012 at 5:48 PM, Gary Kotton <gkotton at redhat.com> wrote:
>
>>  On 06/13/2012 11:57 AM, Kris zhang wrote:
>>
>> Thanks for you detail answer, and please see the result of the command
>> quantum update_port,
>>
>>  The command "quantum update_port" sets the state of the port. In the
>> case of the ovirt.sh script this sets the port in ACTIVE state.
>> The "user" is responsible for providing the attachment ID. In the case of
>> the ovirt.sh script the ID is generated via uuidgen.
>> Once you have generated a UUID for the attachment you need to pass this
>> to quantum via the "quantum plug_iface".
>>
>>
>>  [image: Inline image 1]
>>
>>  I run this script from the shell, and you can see there is no an
>> attachment UUID created. Can you show me your testing result?
>>
>>
>>  Please see below:
>>
>> openstack at openstack:/tmp$ ./ovirt.sh network create Q_net
>> openstack at openstack:/tmp$ ./ovirt.sh port create Q_net 12345678
>> Updated Logical Port with ID: f9f203ab-dab6-4b9c-8dcf-561bcc698c76
>> on Virtual Network: 8c50db01-54ef-4688-a274-9ab3fcfafe7d
>> for tenant: default
>> Plugged interface 24bf26c4-f8eb-46cd-a168-b7a25e64d5b2
>> into Logical Port: f9f203ab-dab6-4b9c-8dcf-561bcc698c76
>> on Virtual Network: 8c50db01-54ef-4688-a274-9ab3fcfafe7d
>> for Tenant: default
>> openstack at openstack:/tmp$
>>
>>
>> openstack at openstack:/tmp$ ll
>> total 40
>> drwxrwxrwt  4 root      root      4096 2012-06-13 05:39 ./
>> drwxr-xr-x 23 root      root      4096 2012-05-26 06:39 ../
>> -rw-rw-r--  1 openstack openstack    6 2012-06-13 05:38 network.12345678
>> -rw-rw-r--  1 openstack openstack   37 2012-06-13 05:38 network.Q_net
>> -rw-rw-r--  1 openstack openstack   37 2012-06-13 05:38
>> network.Q_net.12345678.port
>> -rw-rw-r--  1 openstack openstack   37 2012-06-13 05:38
>> network.Q_net.12345678.port.attach
>> -rwxrwxrwx  1 openstack openstack 2097 2012-06-13 05:07 ovirt.sh*
>> -rw-rw-r--  1 openstack openstack 1797 2012-06-13 05:38 ovirt.txt
>>
>> openstack at openstack:/tmp$ cat network.Q_net.12345678.port.attach
>> 24bf26c4-f8eb-46cd-a168-b7a25e64d5b2
>> openstack at openstack:/tmp$
>>
>> Thanks
>> Gary
>>
>>
>>  BR,
>> Kris
>>
>>
>> On Wed, Jun 13, 2012 at 2:02 PM, Gary Kotton <gkotton at redhat.com> wrote:
>>
>>>  Hi Kris,
>>> Please see my answers and questions below.
>>> Thanks
>>> Gary
>>>
>>>
>>> On 06/13/2012 07:31 AM, Kris zhang wrote:
>>>
>>> Hi Kotton,
>>>
>>>  In the file ovirt.sh, there is a line:
>>>
>>>
>>>  A bit of background regarding the script. The purpose of the POC was to
>>> show that Quantum can be run in oVirt. It would have been ideal to write a
>>> REST client that could interface with the Quantum service. Due to the fact
>>> that I was not familiar with the oVirt code I felt that a quicker and more
>>> productive means was to invoke a bash script from the oVirt engine code.
>>> The script would invoke the quantum cli (this is a client that configures
>>> the quantum server). In addition to this I did not want to make any changes
>>> to the database schema. The result was a script that does the following:
>>> 1. Logical Network Management:
>>>     Create:
>>>         ovirt.sh network create <name>
>>>             - the name is the name of the logical network (in the POC
>>> this is prefixed by "Q_"
>>>             - this invokes the cli to create a network called <name>
>>>             - the UUID returned by the quantum service will be save in
>>> /tmp/network.<name>
>>>             - the above UUID is read when this logical network is used
>>> (this in the future will be save in the oVirt data base)
>>>     Delete:
>>>         ovirt.sh network remove <name>
>>>             - the name is the name of the logical network (in the POC
>>> this is prefixed by "Q_"
>>>             - this invokes the cli to delete a network called <name>
>>>             - the file /tmp/network.<name> is deleted
>>> 2. VM Port management
>>>     Create:
>>>         ovirt.sh port create <net_name> <vmid>
>>>             - the network name and the vm id are input (the VM id is a
>>> key to be able to delete it all :))
>>>             - the script does the following:
>>>                 - creates a port on the network. saves the port id in
>>> /tmp/network.<name>.<vmid>.port
>>>                 - sets the state of the port to ACTIVE
>>>                 - creates an attachment ID (this is the line that you
>>> had problems with). This is saved in /tmp/network.<name>.<vmid>.attachment
>>>                 - saves the network name in a file /tmp/network.<vmid>
>>>                 - the UUID's are read when the VM is started so that
>>> they can be passed to VDSM
>>>     Delete:
>>>         ovirt.sh port remove <vmid>
>>>             - using the vmid the network name is read => enables us to
>>> get all of the ID's to delete port in quantum
>>>             - cleans all of the files
>>> The script is called from the ovirt engine. Sorry for the long winded
>>> explanation.
>>>
>>>
>>>  quantum update_port default $NET_UUID $PORT_UUID state=ACTIVE
>>>                 uuidgen > /tmp/network.$3.$4.port.attach
>>>  ATTACH_UUID=`cat /tmp/network.$3.$4.port.attach`
>>>
>>>
>>>  In Quantum the attachment ID is generated by the user. The code above
>>> generates the attachment ID for the port.
>>>
>>>
>>>
>>>  But i run this command, i found there is no any uuid generated, so
>>> what's the value of the ATTACH_UUID?
>>>
>>>  Do you run the script from the shell or is this run via oVirt?
>>> There is a log of all of the script command - can you please look in
>>> /tmp/ovirt.txt - this may give us some clues.
>>> You can run the script commands as described above. This may also help.
>>> Thanks
>>> Gary
>>>
>>>  Best regards,
>>> Kris
>>>
>>>
>>> On Tue, Jun 12, 2012 at 7:15 PM, Gary Kotton <gkotton at redhat.com> wrote:
>>>
>>>>  On 06/12/2012 12:36 PM, Itamar Heim wrote:
>>>>
>>>>> On 06/12/2012 11:47 AM, Gary Kotton wrote:
>>>>>
>>>>>> Hi Kris,
>>>>>> Thanks for the questions. Please see my inline answers. I have also
>>>>>> cc'ed the ovirt arch mailing list.
>>>>>> Thanks
>>>>>> Gary
>>>>>>
>>>>>> On 06/12/2012 11:21 AM, Kris zhang wrote:
>>>>>>
>>>>>>> Hi Gkotton,
>>>>>>>
>>>>>>> I have some questions:
>>>>>>>
>>>>>>> 1) In the file "ovirt.sh", i found the command quantum always use the
>>>>>>> tenant "default", so if the ovirt don't support multi-tenant?
>>>>>>>
>>>>>> oVirt does not support multi tenancy at the moment. Maybe there are
>>>>>> people on the list who can provide more details about this. The
>>>>>> initial
>>>>>> plan was to use the "default" tenant.
>>>>>>
>>>>>
>>>>> ovirt supports multiple users and an RBAC model for permissions
>>>>> between these users.
>>>>> what exactly are you looking for?
>>>>>
>>>>  Quantum support multi tenancy. The integration with oVirt was done
>>>> with the "default" tenant. This is a different model to that of oVirt.
>>>> Thanks
>>>> Gary
>>>>
>>>
>>>
>>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120618/6d233647/attachment.html>

From danken at redhat.com  Mon Jun 18 19:23:09 2012
From: danken at redhat.com (Dan Kenigsberg)
Date: Mon, 18 Jun 2012 22:23:09 +0300
Subject: Outage: www.ovirt. org planned server restart Tue 22 May 0100 UTC
In-Reply-To: <4FBA7DD7.5020106@iquaid.org>
References: <4FBA7DD7.5020106@iquaid.org>
Message-ID: <20120618192301.GA7538@redhat.com>

On Mon, May 21, 2012 at 10:39:35AM -0700, Karsten (quaid) Wade wrote:
> -----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.
this line says May
> 
> To convert UTC to your local time, run:
>   date -d '2012-04-13 22:00 UTC'
this says April

and you probably mean June!

(couldn't resist)


From danken at redhat.com  Mon Jun 18 19:38:47 2012
From: danken at redhat.com (Dan Kenigsberg)
Date: Mon, 18 Jun 2012 22:38:47 +0300
Subject: Outage: www.ovirt. org planned server restart Tue 22 May 0100 UTC
In-Reply-To: <20120618192301.GA7538@redhat.com>
References: <4FBA7DD7.5020106@iquaid.org>
 <20120618192301.GA7538@redhat.com>
Message-ID: <20120618193846.GB3883@redhat.com>

On Mon, Jun 18, 2012 at 10:23:08PM +0300, Dan Kenigsberg wrote:
> On Mon, May 21, 2012 at 10:39:35AM -0700, Karsten (quaid) Wade wrote:
> > -----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.
> this line says May
> > 
> > To convert UTC to your local time, run:
> >   date -d '2012-04-13 22:00 UTC'
> this says April
> 
> and you probably mean June!
> 
> (couldn't resist)

But I should have :-(
As I received this email one month too late due to some email client
hickup.

sorry for the noise.


From danken at redhat.com  Mon Jun 18 19:48:06 2012
From: danken at redhat.com (Dan Kenigsberg)
Date: Mon, 18 Jun 2012 22:48:06 +0300
Subject: Returned mail: see transcript for details
In-Reply-To: <20120618164936.6F35AC889@lists.ovirt.org>
References: <20120618164936.6F35AC889@lists.ovirt.org>
Message-ID: <20120618194805.GC3883@redhat.com>

On Thu, Jun 14, 2012 at 09:13:07AM -0500, richardsh at att.net wrote:
> The original message was received at Thu, 14 Jun 2012 09:13:07 -0500
> from att.net [182.247.23.138]
> 
> ----- The following addresses had permanent fatal errors -----
> <arch at ovirt.org>
>
>
>------=_NextPart_000_0010_C59D7370.54230D0F
>Content-Type: application/octet-stream;
>        name="letter.zip"
>Content-Transfer-Encoding: base64
>Content-Disposition: attachment;
>        filename="letter.zip"
> 

None of the recipients of this mailing list is going to run the attached
virus within windows screensaver, but I suppose we should not host it
http://lists.ovirt.org/pipermail/arch/attachments/20120614/some-hash/attachment.obj

Can it be deleted?


From lhawthor at redhat.com  Mon Jun 18 22:16:55 2012
From: lhawthor at redhat.com (Leslie Hawthorn)
Date: Mon, 18 Jun 2012 15:16:55 -0700
Subject: Post-Mortem Notes (was: Re: Following Up on LinuxCon Japan Workshop)
In-Reply-To: <4FD910CA.1080808@redhat.com>
References: <4FD910CA.1080808@redhat.com>
Message-ID: <4FDFA8D7.2010904@redhat.com>

Hello everyone,

Thank you for your detailed feedback. I have captured it on the oVirt 
wiki [0] for later reference. I have also shared these notes with the 
Linux Foundation Events Team.

I believe we have sufficiently detailed feedback to help us plan the 
next workshop. I'll address this item during this week's oVirt IRC meeting.

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

Cheers,
LH

On 06/13/2012 03:14 PM, Leslie Hawthorn wrote:
> Hello everyone,
>
> I'd like to collect feedback from everyone on last week's oVirt 
> workshop at LinuxCon Japan. [0] Please reply back with comments by 
> close of business this Friday, 15 June.
>
> Once we have gathered feedback on list, I'll capture it on the oVirt 
> wiki. We can then use what we've learned to help construct the agenda 
> and other plans for other upcoming oVirt workshops at LinuxCons. [1]
>
> If you know that you would like to volunteer as an instructor for 
> future workshops or would like to suggest alternate content for the 
> workshop, please include that in your feedback.
>
> - Course Material
> What sessions were most well received? Which ones require improvement? 
> Any additional sessions we'd suggest?
>
> - Audience Participation
> How many attendees? How did the Q&A periods go? Would we like to 
> prepare a post-event attendee survey? (I recommend we do the survey 
> and can prepare some questions for the group if that's useful.)
>
> - Developer/user traction resulting from engaging at workshop
> Did this workshop help us to gain new developers or users? Reinforce 
> relationships with existing community members?
>
> - Promotion of the event, both before and after
> What could be done to more effectively promote the event prior to the 
> workshops? Videos and slides from the workshop should be posted on the 
> LC Japan site tomorrow; what action would the community like to take 
> to promote this content?
>
> - A/V and Room Set up
> Did the seating arrangements work well for the workshop format? Did 
> the A/V work well, including the videotaping process?
>
> - Food and beverage
> Did the catered in lunch help to keep the flow of the workshop 
> productive? Was the food of good quality and in keeping with the needs 
> of attendee dietary constraints?
>
> - Give aways
> We did not produce attendee gifts for the oVirt workshop. Thoughts on 
> whether this would be a welcome addition in the future? Suggestions 
> for type of gift also welcome.
>
> - Any other feedback
>
> If it is preferable to discuss this feedback real-time, I will ask 
> Mike Burns to give us more time for this topic during next week's 
> oVirt IRC meeting.
>
> [0] - 
> https://events.linuxfoundation.org/events/linuxcon-japan/ovirt-gluster-workshops
> [1] - http://www.ovirt.org/wiki/OVirt_Global_Workshops
>
> Cheers,
> LH
>


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

identi.ca/lh
twitter.com/lhawthorn



From zhang.kris at gmail.com  Tue Jun 19 03:02:07 2012
From: zhang.kris at gmail.com (Kris zhang)
Date: Tue, 19 Jun 2012 11:02:07 +0800
Subject: [oVirt][Quantum] question about quantum CLI
In-Reply-To: <4FDEC217.5050805@redhat.com>
References: <CAAskrmH2rXN_nbnoBqkyWHj_mEWNNMhZm-AwcRauJ558nfnobw@mail.gmail.com>
	<4FD7022F.2040600@redhat.com> <4FD70DA4.5000602@redhat.com>
	<4FD724C8.8060506@redhat.com>
	<CAAskrmHB61c+X+P39za85nQndN3j6YZ8O7uqX=p5TeQiOUmWCQ@mail.gmail.com>
	<4FD82CE7.8090401@redhat.com>
	<CAAskrmHHuc8E-sjddLM+sDkh2svszbNUa9L07ttNthjdzU3PJQ@mail.gmail.com>
	<4FD861D0.3010902@redhat.com>
	<CAAskrmGFmdiQ1tmhgJx7Zdoat2p4Q50TYEE7zoLbmS5uK8mNPw@mail.gmail.com>
	<4FDAD21B.3030204@redhat.com>
	<CAAskrmFS51Yq0dgGFsyh+MHfFsU93Opr1bDyDm8LWbBo8dYDTA@mail.gmail.com>
	<4FDEC217.5050805@redhat.com>
Message-ID: <CAAskrmHYC2c9op+NeGvFZ3S8boNvhNBK76sXk8o7SMdJi1-4hw@mail.gmail.com>

Hi Kotton,

Thanks for these days help, currently i haven't any other questions.

Thanks again,
Kris


On Mon, Jun 18, 2012 at 1:52 PM, Gary Kotton <gkotton at redhat.com> wrote:

> **
> Hi,
> Please see inline.
> Thanks
> Gary
>
>
> On 06/18/2012 04:11 AM, Kris zhang wrote:
>
> Hi Kotton,
>
>  Thanks for your detailed answer, and it's very clear, and i still have
> some other questions:
>
>  1) Where i can find the database changes? please correct me if no change
> in db.
>
>
> At the moment in oVirt there are no database changes. The code that you
> are looking at is a POC. We (the community) still need to address the
> database changes.I think that prior to adding the database changes we
> should first add a REST client that can communicate with the Quantum
> service (at the moment this is done via the Quantum CLI). I have a short
> list of items that need to be addressed for a a basic Quantum integration
> (this will at least give us the infrastructure to build on in the future).
> I think that for the first phase we should support the following:
>
>     - oVirt Engine will support one Quantum service (the instance
> currently supports only 1 plugin)
>         - oVirt installation will have Quantum service as a dependency
>     - All hosts in a cluster must have the same networking support. This
> can be one of the following:
>         - Legacy oVirt networking
>         - Legacy oVirt networking for management and Quantum for VM
> networking
>     - When a VDSM host is registered (IP, password etc), one of the above
> methods will registered. If this Quantum, then the relevant configuration
> data will be sent to VDSM. Agent packages will exist on VDSM
>     - If a logical network is assigned to a Quantum cluster then this
> network must be registered with Quantum (to get the UUID)
>     - All VM's running on this cluster will receive a port ID and pass an
> attachment ID to the Quantum
>     - Limitations:
>         - No network statistics for logical quantum networks
>
> I think that small secluded changes can help the integration - for
> example:-
>     - implement a REST client (used to communicate with Quantum service)
>     - update database to store relevant quantum ID's
>     - improve VDMS support for Quantum code (have a plugin architecture -
> so that different technologies can plug their code into VDSM)
>     - address HOST management
>     - packaging
>
>
>
> 2) If the engine server crashed, then how to rebuild the network
> information which generated by ovirt.sh script in the /tmp dir?
>
>
> Please note that this is a POC. All of the data generated by the script is
> persistent - that is, it is stored in the /tmp directory. I am not really
> sure that I understand your question. If oVirt engine crashes then the user
> will not be able to deploy VM's. If the Quantum service crashes then the
> user should not be able to configure Quantum networks or attach ports etc.
> If the quantum service crashes or is unreachable by VDSM then a newly
> deployed VM may not be able to "attach" to the Quantum network. This can be
> averted by having the following - on oVirt engine there should be a process
> that monitors the status of the Quantum service. If this is down then it
> should restart it. This can and should be discussed in more detail.
>
>
>  In addition, originally i think the quantum port create is no any
> relationship with vm create, and only be linked when a VIF of a VM attach
> into a port. But your design is different, so there is no port creation in
> the web UI, right?
>
>
> My thinking is that when a VNIC of a VM is linked to a Quantum network
> then the Quantum port should be created. After some discussion I understand
> that the oVirt VNIC has a UUID - this can now be used as the attachment ID.
> In my opinion the Quantum interface should be limited to the host
> management. The rest should be "hidden" from the user.
>
>
>  Best regards,
> Kris
>
>
>
> On Fri, Jun 15, 2012 at 2:11 PM, Gary Kotton <gkotton at redhat.com> wrote:
>
>>  Hi Kris,
>> You have asked a very interesting and good question. Please see the
>> answers an explanations below. Both flow are used. The "a" flows (1a2a and
>> 3a) are for the network management. The "b" flows (1b and 2b) are for the
>> VM management.
>> Network management (1a):
>>     - user create a Quantum network
>>     - user will create a Quantum port and attachment
>> VM Management (1b):
>>     - users creates a VM
>>     - assigned VM to one or more logical networks. Each each assignment
>> will receive the above quantum details
>> VM flow:
>>     - VDSM creates the libvirt XML file
>>         - (2b) if libvirt version is 0.9.10 or earlier then VDSM will
>> have to create the tap device (via attachment ID) and will set it with type
>> 'ethernet' in the libvirt file (this is what was done in the POC). In
>> addition this it need to notify OVS of the VM ID on the port
>>         - in later versions of libvirt, libvirt will do the create via
>> the attachment id
>>     - VDSM will start the VM
>> Network flow (2a and 3a):
>>     - The Quantum agent polls the Quantum plugin for network changes. If
>> the agent detects a tap device that is part of a network then it will
>> configure the characteristics of this tap device on the OVS. In the case of
>> the POC it will be the VLAN tag of the network
>> Hope that I have answered your questions.
>> Thanks
>> Gary
>>
>>
>> On 06/14/2012 10:49 AM, Kris zhang wrote:
>>
>> Hi Kotton,
>>
>>  Thank your very much, and i still have a question:
>>
>>  There is a quantum.py file in the gkotton-vdsm_quantum-78427ca.zip. I
>> saw there are some methods (For example: vifAddOpenVswitch() ) to call
>> ovs-vsctl command, that means vdsm will control the ovs, not through ovs
>> quantum agent?
>>
>>  The ovs quantum agent code is in the
>> http://bazaar.launchpad.net/~netstack-core/quantum/essex/view/head:/quantum/plugins/openvswitch/agent/ovs_quantum_agent.py
>>
>>
>>  [image: Inline image 1]
>>
>>  Please see above the image, and there are two ways:
>>
>>  First way: 1a, 2a, 3a.
>>  Second way: 1b, 2b
>>
>>  which way is used in POC?
>>
>>  Best regards,
>> Kris
>>
>>
>>
>> On Wed, Jun 13, 2012 at 5:48 PM, Gary Kotton <gkotton at redhat.com> wrote:
>>
>>>  On 06/13/2012 11:57 AM, Kris zhang wrote:
>>>
>>> Thanks for you detail answer, and please see the result of the command
>>> quantum update_port,
>>>
>>>  The command "quantum update_port" sets the state of the port. In the
>>> case of the ovirt.sh script this sets the port in ACTIVE state.
>>> The "user" is responsible for providing the attachment ID. In the case
>>> of the ovirt.sh script the ID is generated via uuidgen.
>>> Once you have generated a UUID for the attachment you need to pass this
>>> to quantum via the "quantum plug_iface".
>>>
>>>
>>>  [image: Inline image 1]
>>>
>>>  I run this script from the shell, and you can see there is no an
>>> attachment UUID created. Can you show me your testing result?
>>>
>>>
>>>  Please see below:
>>>
>>> openstack at openstack:/tmp$ ./ovirt.sh network create Q_net
>>> openstack at openstack:/tmp$ ./ovirt.sh port create Q_net 12345678
>>> Updated Logical Port with ID: f9f203ab-dab6-4b9c-8dcf-561bcc698c76
>>> on Virtual Network: 8c50db01-54ef-4688-a274-9ab3fcfafe7d
>>> for tenant: default
>>> Plugged interface 24bf26c4-f8eb-46cd-a168-b7a25e64d5b2
>>> into Logical Port: f9f203ab-dab6-4b9c-8dcf-561bcc698c76
>>> on Virtual Network: 8c50db01-54ef-4688-a274-9ab3fcfafe7d
>>> for Tenant: default
>>> openstack at openstack:/tmp$
>>>
>>>
>>> openstack at openstack:/tmp$ ll
>>> total 40
>>> drwxrwxrwt  4 root      root      4096 2012-06-13 05:39 ./
>>> drwxr-xr-x 23 root      root      4096 2012-05-26 06:39 ../
>>> -rw-rw-r--  1 openstack openstack    6 2012-06-13 05:38 network.12345678
>>> -rw-rw-r--  1 openstack openstack   37 2012-06-13 05:38 network.Q_net
>>> -rw-rw-r--  1 openstack openstack   37 2012-06-13 05:38
>>> network.Q_net.12345678.port
>>> -rw-rw-r--  1 openstack openstack   37 2012-06-13 05:38
>>> network.Q_net.12345678.port.attach
>>> -rwxrwxrwx  1 openstack openstack 2097 2012-06-13 05:07 ovirt.sh*
>>> -rw-rw-r--  1 openstack openstack 1797 2012-06-13 05:38 ovirt.txt
>>>
>>> openstack at openstack:/tmp$ cat network.Q_net.12345678.port.attach
>>> 24bf26c4-f8eb-46cd-a168-b7a25e64d5b2
>>> openstack at openstack:/tmp$
>>>
>>> Thanks
>>> Gary
>>>
>>>
>>>  BR,
>>> Kris
>>>
>>>
>>> On Wed, Jun 13, 2012 at 2:02 PM, Gary Kotton <gkotton at redhat.com> wrote:
>>>
>>>>  Hi Kris,
>>>> Please see my answers and questions below.
>>>> Thanks
>>>> Gary
>>>>
>>>>
>>>> On 06/13/2012 07:31 AM, Kris zhang wrote:
>>>>
>>>> Hi Kotton,
>>>>
>>>>  In the file ovirt.sh, there is a line:
>>>>
>>>>
>>>>  A bit of background regarding the script. The purpose of the POC was
>>>> to show that Quantum can be run in oVirt. It would have been ideal to write
>>>> a REST client that could interface with the Quantum service. Due to the
>>>> fact that I was not familiar with the oVirt code I felt that a quicker and
>>>> more productive means was to invoke a bash script from the oVirt engine
>>>> code. The script would invoke the quantum cli (this is a client that
>>>> configures the quantum server). In addition to this I did not want to make
>>>> any changes to the database schema. The result was a script that does the
>>>> following:
>>>> 1. Logical Network Management:
>>>>     Create:
>>>>         ovirt.sh network create <name>
>>>>             - the name is the name of the logical network (in the POC
>>>> this is prefixed by "Q_"
>>>>             - this invokes the cli to create a network called <name>
>>>>             - the UUID returned by the quantum service will be save in
>>>> /tmp/network.<name>
>>>>             - the above UUID is read when this logical network is used
>>>> (this in the future will be save in the oVirt data base)
>>>>     Delete:
>>>>         ovirt.sh network remove <name>
>>>>             - the name is the name of the logical network (in the POC
>>>> this is prefixed by "Q_"
>>>>             - this invokes the cli to delete a network called <name>
>>>>             - the file /tmp/network.<name> is deleted
>>>> 2. VM Port management
>>>>     Create:
>>>>         ovirt.sh port create <net_name> <vmid>
>>>>             - the network name and the vm id are input (the VM id is a
>>>> key to be able to delete it all :))
>>>>             - the script does the following:
>>>>                 - creates a port on the network. saves the port id in
>>>> /tmp/network.<name>.<vmid>.port
>>>>                 - sets the state of the port to ACTIVE
>>>>                 - creates an attachment ID (this is the line that you
>>>> had problems with). This is saved in /tmp/network.<name>.<vmid>.attachment
>>>>                 - saves the network name in a file /tmp/network.<vmid>
>>>>                 - the UUID's are read when the VM is started so that
>>>> they can be passed to VDSM
>>>>     Delete:
>>>>         ovirt.sh port remove <vmid>
>>>>             - using the vmid the network name is read => enables us to
>>>> get all of the ID's to delete port in quantum
>>>>             - cleans all of the files
>>>> The script is called from the ovirt engine. Sorry for the long winded
>>>> explanation.
>>>>
>>>>
>>>>  quantum update_port default $NET_UUID $PORT_UUID state=ACTIVE
>>>>                 uuidgen > /tmp/network.$3.$4.port.attach
>>>>
>>>> ATTACH_UUID=`cat /tmp/network.$3.$4.port.attach`
>>>>
>>>>
>>>>  In Quantum the attachment ID is generated by the user. The code above
>>>> generates the attachment ID for the port.
>>>>
>>>>
>>>>
>>>>  But i run this command, i found there is no any uuid generated, so
>>>> what's the value of the ATTACH_UUID?
>>>>
>>>>  Do you run the script from the shell or is this run via oVirt?
>>>> There is a log of all of the script command - can you please look in
>>>> /tmp/ovirt.txt - this may give us some clues.
>>>> You can run the script commands as described above. This may also help.
>>>> Thanks
>>>> Gary
>>>>
>>>>  Best regards,
>>>> Kris
>>>>
>>>>
>>>> On Tue, Jun 12, 2012 at 7:15 PM, Gary Kotton <gkotton at redhat.com>wrote:
>>>>
>>>>>  On 06/12/2012 12:36 PM, Itamar Heim wrote:
>>>>>
>>>>>> On 06/12/2012 11:47 AM, Gary Kotton wrote:
>>>>>>
>>>>>>> Hi Kris,
>>>>>>> Thanks for the questions. Please see my inline answers. I have also
>>>>>>> cc'ed the ovirt arch mailing list.
>>>>>>> Thanks
>>>>>>> Gary
>>>>>>>
>>>>>>> On 06/12/2012 11:21 AM, Kris zhang wrote:
>>>>>>>
>>>>>>>> Hi Gkotton,
>>>>>>>>
>>>>>>>> I have some questions:
>>>>>>>>
>>>>>>>> 1) In the file "ovirt.sh", i found the command quantum always use
>>>>>>>> the
>>>>>>>> tenant "default", so if the ovirt don't support multi-tenant?
>>>>>>>>
>>>>>>> oVirt does not support multi tenancy at the moment. Maybe there are
>>>>>>> people on the list who can provide more details about this. The
>>>>>>> initial
>>>>>>> plan was to use the "default" tenant.
>>>>>>>
>>>>>>
>>>>>> ovirt supports multiple users and an RBAC model for permissions
>>>>>> between these users.
>>>>>> what exactly are you looking for?
>>>>>>
>>>>>  Quantum support multi tenancy. The integration with oVirt was done
>>>>> with the "default" tenant. This is a different model to that of oVirt.
>>>>> Thanks
>>>>> Gary
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120619/3219e7f9/attachment.html>

From kwade at redhat.com  Tue Jun 19 05:34:15 2012
From: kwade at redhat.com (Karsten 'quaid' Wade)
Date: Mon, 18 Jun 2012 22:34:15 -0700
Subject: http://www.ovirt.org/wiki/Intercall issues
In-Reply-To: <20120618142848.GB12442@redhat.com>
References: <20120617180428.GA10904@redhat.com>
	<4FDF2D9D.1010700@linux.vnet.ibm.com>
	<4FDF304F.1090004@middleswarth.net>
	<20120618142848.GB12442@redhat.com>
Message-ID: <4FE00F57.4000103@redhat.com>

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

On 06/18/2012 07:28 AM, Dan Kenigsberg wrote:
> On Mon, Jun 18, 2012 at 09:42:39AM -0400, Robert Middleswarth 
> wrote:
>> From the US I am getting the conf number is invald?
>> 
> 
> <snip>
> 
>>>> 
>>> Hello Dan, The India dial in ... India Dial-In #: 
>>> 000-800-650-1533
>>> 
>>> never works.. so I am unable to connect to this call from home.
>>> I cannot use the other India number as that is not supported
>>> for my telecom carrier.
>>> 
>>> Who can help in resolving this issue. The above number always 
>>> results in a 'engage' tone. It never asks for conf. id.
> 
> I suppose arch at ovirt.org (CCed) could be more helpful in this 
> regard.

This is a regular conference call?

Is it time to move this to IRC instead? It's the hip thing, all the
kids are doing it!

- - Karsten
- -- 
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/

iD8DBQFP4A9X2ZIOBq0ODEERAm2iAKDdksMcMayQwRxy9+/9WP+YsI9isQCghlow
aUezU//4gLTd1pm9mhgDpwk=
=m/mL
-----END PGP SIGNATURE-----


From danken at redhat.com  Tue Jun 19 07:33:20 2012
From: danken at redhat.com (Dan Kenigsberg)
Date: Tue, 19 Jun 2012 10:33:20 +0300
Subject: http://www.ovirt.org/wiki/Intercall issues
In-Reply-To: <4FE00F57.4000103@redhat.com>
References: <20120617180428.GA10904@redhat.com>
	<4FDF2D9D.1010700@linux.vnet.ibm.com>
	<4FDF304F.1090004@middleswarth.net>
	<20120618142848.GB12442@redhat.com> <4FE00F57.4000103@redhat.com>
Message-ID: <20120619073312.GA13734@redhat.com>

On Mon, Jun 18, 2012 at 10:34:15PM -0700, Karsten 'quaid' Wade wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 06/18/2012 07:28 AM, Dan Kenigsberg wrote:
> > On Mon, Jun 18, 2012 at 09:42:39AM -0400, Robert Middleswarth 
> > wrote:
> >> From the US I am getting the conf number is invald?
> >> 
> > 
> > <snip>
> > 
> >>>> 
> >>> Hello Dan, The India dial in ... India Dial-In #: 
> >>> 000-800-650-1533
> >>> 
> >>> never works.. so I am unable to connect to this call from home.
> >>> I cannot use the other India number as that is not supported
> >>> for my telecom carrier.
> >>> 
> >>> Who can help in resolving this issue. The above number always 
> >>> results in a 'engage' tone. It never asks for conf. id.
> > 
> > I suppose arch at ovirt.org (CCed) could be more helpful in this 
> > regard.
> 
> This is a regular conference call?

Yes. It's mentioned in
http://www.ovirt.org/wiki/Meetings#Meeting_Time_and_Place

> 
> Is it time to move this to IRC instead? It's the hip thing, all the
> kids are doing it!

I actually prefer Alexander Graham Bell's new invention.

Dan


From oschreib at redhat.com  Tue Jun 19 07:59:55 2012
From: oschreib at redhat.com (Ofer Schreiber)
Date: Tue, 19 Jun 2012 03:59:55 -0400 (EDT)
Subject: ovirt f17 beta repo
In-Reply-To: <20120618134255.GP9959@frylock.austin.ibm.com>
Message-ID: <34f790f5-d98b-4d5c-92f4-76d246c0ecaa@zmail14.collab.prod.int.phx2.redhat.com>



----- Original Message -----
> * Juan Hernandez <juan.hernandez at redhat.com> [2012-06-16 12:08]:
> > On 06/15/2012 09:53 PM, Ryan Harper wrote:
> > >I saw a discussion on #ovirt about how the build system is
> > >supposed to
> > >increment the _XXXX past the version but that's not happening.
> > > Well,
> > >newer rpms are now posted to the repo, but because the
> > >version is the same expect for the githash, it won't upgrade.  Can
> > >we
> > >get this fixed[1]?
> > 
> > In my opinion the version number of the RPM should not include that
> > _XXXX suffix. We should build packages using the numbering schema
> > recommended for snapshot and pre-release packages here:
> > 
> > http://fedoraproject.org/wiki/Packaging:NamingGuidelines#Release_Tag
> > 
> > So the pre-release numbers should be something like this:
> > 
> > 3.1.0-0.1.20120615git0a4333
> > 3.1.0-0.2.20120618git94a365
> > ...
> > 
> > That way the day we do the release we can change to this numbering:
> > 
> > 3.1.0-1
> > 3.1.0-2
> > ...
> > 
> > And any release number will be greater than any pre-release number.
> 
> +1
> 
> So, how do we enact this change?

I'll personally make sure next beta build will have this versioning schema

> 
> 
> > 
> > >[root at ichigo-dom234 ~]# ls *.rpm
> > >ovirt-engine-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > >ovirt-engine-backend-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > >ovirt-engine-config-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > >ovirt-engine-dbscripts-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > >ovirt-engine-genericapi-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > >ovirt-engine-notification-service-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > >ovirt-engine-restapi-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > >ovirt-engine-setup-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > >ovirt-engine-tools-common-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > >ovirt-engine-userportal-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > >ovirt-engine-webadmin-portal-3.1.0_0001-0.gitdd65f3.fc17.noarch.rpm
> > >[root at ichigo-dom234 ~]# rpm -Uvh --test *.rpm
> > >Preparing...
> > >               ########################################### [100%]
> > >     package
> > >     ovirt-engine-backend-3.1.0_0001-0.gitf093e0.fc17.noarch
> > >     (which is newer than
> > >     ovirt-engine-backend-3.1.0_0001-0.gitdd65f3.fc17.noarch) is
> > >     already installed
> > >     package
> > >     ovirt-engine-dbscripts-3.1.0_0001-0.gitf093e0.fc17.noarch
> > >     (which is newer than
> > >     ovirt-engine-dbscripts-3.1.0_0001-0.gitdd65f3.fc17.noarch)
> > >     is already installed
> > >     package
> > >     ovirt-engine-genericapi-3.1.0_0001-0.gitf093e0.fc17.noarch
> > >     (which is newer than
> > >     ovirt-engine-genericapi-3.1.0_0001-0.gitdd65f3.fc17.noarch)
> > >     is already installed
> > >     package
> > >     ovirt-engine-restapi-3.1.0_0001-0.gitf093e0.fc17.noarch
> > >     (which is newer than
> > >     ovirt-engine-restapi-3.1.0_0001-0.gitdd65f3.fc17.noarch) is
> > >     already installed
> > >     package ovirt-engine-setup-3.1.0_0001-0.gitf093e0.fc17.noarch
> > >     (which is newer than
> > >     ovirt-engine-setup-3.1.0_0001-0.gitdd65f3.fc17.noarch) is
> > >     already installed
> > >     package
> > >     ovirt-engine-config-3.1.0_0001-0.gitf093e0.fc17.noarch
> > >     (which is newer than
> > >     ovirt-engine-config-3.1.0_0001-0.gitdd65f3.fc17.noarch) is
> > >     already installed
> > >     package
> > >     ovirt-engine-notification-service-3.1.0_0001-0.gitf093e0.fc17.noarch
> > >     (which is newer than
> > >     ovirt-engine-notification-service-3.1.0_0001-0.gitdd65f3.fc17.noarch)
> > >     is already installed
> > >     package
> > >     ovirt-engine-tools-common-3.1.0_0001-0.gitf093e0.fc17.noarch
> > >     (which is newer than
> > >     ovirt-engine-tools-common-3.1.0_0001-0.gitdd65f3.fc17.noarch)
> > >     is already installed
> > >     package
> > >     ovirt-engine-userportal-3.1.0_0001-0.gitf093e0.fc17.noarch
> > >     (which is newer than
> > >     ovirt-engine-userportal-3.1.0_0001-0.gitdd65f3.fc17.noarch)
> > >     is already installed
> > >     package
> > >     ovirt-engine-webadmin-portal-3.1.0_0001-0.gitf093e0.fc17.noarch
> > >     (which is newer than
> > >     ovirt-engine-webadmin-portal-3.1.0_0001-0.gitdd65f3.fc17.noarch)
> > >     is already installed
> > >     package ovirt-engine-3.1.0_0001-0.gitf093e0.fc17.noarch
> > >     (which is newer than
> > >     ovirt-engine-3.1.0_0001-0.gitdd65f3.fc17.noarch) is already
> > >     installed
> > >
> > >
> > >1. I know I can --nodeps --force to get this to work.
> > >
> > 
> > _______________________________________________
> > Arch mailing list
> > Arch at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/arch
> 
> --
> Ryan Harper
> Software Engineer; Linux Technology Center
> IBM Corp., Austin, Tx
> ryanh at us.ibm.com
> 
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch
> 


From kwade at redhat.com  Tue Jun 19 16:23:48 2012
From: kwade at redhat.com (Karsten 'quaid' Wade)
Date: Tue, 19 Jun 2012 09:23:48 -0700
Subject: http://www.ovirt.org/wiki/Intercall issues
In-Reply-To: <20120619073312.GA13734@redhat.com>
References: <20120617180428.GA10904@redhat.com>
	<4FDF2D9D.1010700@linux.vnet.ibm.com>
	<4FDF304F.1090004@middleswarth.net>
	<20120618142848.GB12442@redhat.com> <4FE00F57.4000103@redhat.com>
	<20120619073312.GA13734@redhat.com>
Message-ID: <4FE0A794.3020909@redhat.com>

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

On 06/19/2012 12:33 AM, Dan Kenigsberg wrote:
> On Mon, Jun 18, 2012 at 10:34:15PM -0700, Karsten 'quaid' Wade
> wrote:

> 
>> 
>> Is it time to move this to IRC instead? It's the hip thing, all
>> the kids are doing it!
> 
> I actually prefer Alexander Graham Bell's new invention.

Sadly, Mr. Bell's invention is often a high barrier for participation
in open source projects. :(

- - Karsten
- -- 
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/

iD8DBQFP4KeU2ZIOBq0ODEERAoYoAKC4Zp9mhAZxDvfslwzxGIUxKLoyuQCg28sN
qXaLUgF5sAXZvFT06xS1QmA=
=WtFZ
-----END PGP SIGNATURE-----


From mburns at redhat.com  Wed Jun 20 15:17:35 2012
From: mburns at redhat.com (Mike Burns)
Date: Wed, 20 Jun 2012 11:17:35 -0400
Subject: oVirt Weekly Meeting Minutes -- 2012-06-20
Message-ID: <1340205455.3734.74.camel@beelzebub.mburnsfire.net>

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

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


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



Meeting summary
---------------
* agenda and roll call  (mburns, 14:01:16)

* Status of next release  (mburns, 14:04:16)
  * 9 bugs in 3.1 release tracker  (oschreib, 14:06:12)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=822145
    (oschreib, 14:06:16)
  * current targeted GA is 27-June  (mburns, 14:06:22)
  * LINK: http://www.ovirt.org/releases/beta/fedora/17/   (oschreib,
    14:10:03)
  * LINK: http://www.ovirt.org/releases/beta/fedora/17/   (mburns,
    14:10:34)
  * new beta build (3.1.0-0.1.20120620git6ef9f8.fc17) available
    (oschreib, 14:10:58)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=828633
    (oschreib, 14:11:36)
  * libvirt - Sanlock locking failed for readonly devices (MODIFIED)
    (oschreib, 14:11:57)
  * waiting on danpb  (oschreib, 14:25:17)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=828633   (mburns,
    14:25:34)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=831998
    (oschreib, 14:26:37)
  * VDSM - It's impossible to create bond with setupNetworks (ASSIGNED)
    (oschreib, 14:26:58)
  * WIP  (oschreib, 14:29:45)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=832199
    (oschreib, 14:31:02)
  * VDSM - vdsmd init script times out due to lengthy semanage operation
    (ASSIGNED)  (oschreib, 14:31:21)
  * WIP  (oschreib, 14:35:39)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=832517
    (oschreib, 14:36:43)
  * node - sshd daemon is not starting correctly after complete the
    installation of oVirt Node (NEW)  (oschreib, 14:36:58)
  * WIP, fix to be push in the next couple of days  (oschreib, 14:37:42)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=832539
    (oschreib, 14:37:55)
  * node - iptables blocking communication between node and engine
    (POST)  (oschreib, 14:38:06)
  * in review, should be in next build  (oschreib, 14:38:46)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=832577
    (oschreib, 14:38:56)
  * vdsm - ovirt-node can't be approved due to missing /rhev/data-center
    (POST)  (oschreib, 14:39:15)
  * pushed upstream, need to rebase to ovirt-3.1 branch  (oschreib,
    14:40:29)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=833201
    (oschreib, 14:40:39)
  * vdsm - Failed to add host - does not accept vdsm 4.10 (POST)
    (oschreib, 14:41:09)
  * pushed  (oschreib, 14:42:42)
  * ACTION: douglas please push http://gerrit.ovirt.org/#/c/5379/
    upstream and to ovirt-3.1  (danken, 14:46:12)
  * ACTION: douglas please push http://gerrit.ovirt.org/#/c/5379/
    upstream and to ovirt-3.1  (oschreib, 14:47:52)
  * AGREED: GA will be postponed to the 9th of July  (oschreib,
    14:53:58)

* upcoming workshops  (mburns, 14:56:11)
  * feedback from LC Japan  (mburns, 14:57:50)
  * LINK: http://www.ovirt.org/wiki/LC_Japan_Workshop_Post-Mortem
    (mburns, 14:57:56)
  * time to begin planning for LC North America (San Diego, Aug 29-31)
    (mburns, 14:58:34)
  * linux.conf.au has reached out requesting oVirt related presentations
    (mburns, 15:01:16)
  * LINK:
    https://events.linuxfoundation.org/events/linuxcon/co-located-events
    (dneary, 15:03:01)
  * lh to send agenda to LinuxCon North America  (mburns, 15:04:23)

* other topics  (mburns, 15:04:52)
  * ACTION: sgordon to send email about release notes  (mburns,
    15:05:50)
  * ACTION: dneary to ensure that discussion starts on infra@ on the
    creation of a community infrastructure team  (dneary, 15:12:46)
  * ACTION: dneary to ensure that discussion starts on infra@ on the
    creation of a community infrastructure team  (mburns, 15:13:09)

Meeting ended at 15:15:08 UTC.




Action Items
------------
* douglas please push http://gerrit.ovirt.org/#/c/5379/ upstream and to
  ovirt-3.1
* douglas please push http://gerrit.ovirt.org/#/c/5379/ upstream and to
  ovirt-3.1
* sgordon to send email about release notes
* dneary to ensure that discussion starts on infra@ on the creation of a
  community infrastructure team
* dneary to ensure that discussion starts on infra@ on the creation of a
  community infrastructure team




Action Items, by person
-----------------------
* dneary
  * dneary to ensure that discussion starts on infra@ on the creation of
    a community infrastructure team
  * dneary to ensure that discussion starts on infra@ on the creation of
    a community infrastructure team
* sgordon
  * sgordon to send email about release notes
* **UNASSIGNED**
  * douglas please push http://gerrit.ovirt.org/#/c/5379/ upstream and
    to ovirt-3.1
  * douglas please push http://gerrit.ovirt.org/#/c/5379/ upstream and
    to ovirt-3.1




People Present (lines said)
---------------------------
* oschreib (93)
* mburns (74)
* dneary (18)
* danken (15)
* lh (14)
* sgordon (8)
* fsimonce (8)
* quaid (7)
* ilvovsky (6)
* ykaul (4)
* itamar (3)
* RobertM (3)
* ovirtbot (3)
* rharper (3)
* yzaslavs (2)
* Guest571 (1)
* mkolesni (1)
* mkolesni_ (1)
* ofrenkel (1)
* READ10 (1)
* miki (1)
* masayag (1)
* mgoldboi (1)




Generated by `MeetBot`_ 0.1.4

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



From ykaul at redhat.com  Wed Jun 20 18:09:52 2012
From: ykaul at redhat.com (Yaniv Kaul)
Date: Wed, 20 Jun 2012 21:09:52 +0300
Subject: oVirt Weekly Meeting Minutes -- 2012-06-20
In-Reply-To: <1340205455.3734.74.camel@beelzebub.mburnsfire.net>
References: <1340205455.3734.74.camel@beelzebub.mburnsfire.net>
Message-ID: <4FE211F0.7030709@redhat.com>

Was test day post-mortem discussed? I had to leave before the meeting 
ended, but I don't see it here.
Y.


On 06/20/2012 06:17 PM, Mike Burns wrote:
> Minutes:        http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-20-14.00.html
> Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-20-14.00.txt
> Log:            http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-20-14.00.log.html
>
> =========================
> #ovirt: oVirt Weekly Sync
> =========================
>
>
> Meeting started by mburns at 14:00:42 UTC. The full logs are available
> at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-20-14.00.log.html
> .
>
>
>
> Meeting summary
> ---------------
> * agenda and roll call  (mburns, 14:01:16)
>
> * Status of next release  (mburns, 14:04:16)
>    * 9 bugs in 3.1 release tracker  (oschreib, 14:06:12)
>    * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=822145
>      (oschreib, 14:06:16)
>    * current targeted GA is 27-June  (mburns, 14:06:22)
>    * LINK: http://www.ovirt.org/releases/beta/fedora/17/   (oschreib,
>      14:10:03)
>    * LINK: http://www.ovirt.org/releases/beta/fedora/17/   (mburns,
>      14:10:34)
>    * new beta build (3.1.0-0.1.20120620git6ef9f8.fc17) available
>      (oschreib, 14:10:58)
>    * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=828633
>      (oschreib, 14:11:36)
>    * libvirt - Sanlock locking failed for readonly devices (MODIFIED)
>      (oschreib, 14:11:57)
>    * waiting on danpb  (oschreib, 14:25:17)
>    * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=828633   (mburns,
>      14:25:34)
>    * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=831998
>      (oschreib, 14:26:37)
>    * VDSM - It's impossible to create bond with setupNetworks (ASSIGNED)
>      (oschreib, 14:26:58)
>    * WIP  (oschreib, 14:29:45)
>    * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=832199
>      (oschreib, 14:31:02)
>    * VDSM - vdsmd init script times out due to lengthy semanage operation
>      (ASSIGNED)  (oschreib, 14:31:21)
>    * WIP  (oschreib, 14:35:39)
>    * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=832517
>      (oschreib, 14:36:43)
>    * node - sshd daemon is not starting correctly after complete the
>      installation of oVirt Node (NEW)  (oschreib, 14:36:58)
>    * WIP, fix to be push in the next couple of days  (oschreib, 14:37:42)
>    * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=832539
>      (oschreib, 14:37:55)
>    * node - iptables blocking communication between node and engine
>      (POST)  (oschreib, 14:38:06)
>    * in review, should be in next build  (oschreib, 14:38:46)
>    * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=832577
>      (oschreib, 14:38:56)
>    * vdsm - ovirt-node can't be approved due to missing /rhev/data-center
>      (POST)  (oschreib, 14:39:15)
>    * pushed upstream, need to rebase to ovirt-3.1 branch  (oschreib,
>      14:40:29)
>    * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=833201
>      (oschreib, 14:40:39)
>    * vdsm - Failed to add host - does not accept vdsm 4.10 (POST)
>      (oschreib, 14:41:09)
>    * pushed  (oschreib, 14:42:42)
>    * ACTION: douglas please push http://gerrit.ovirt.org/#/c/5379/
>      upstream and to ovirt-3.1  (danken, 14:46:12)
>    * ACTION: douglas please push http://gerrit.ovirt.org/#/c/5379/
>      upstream and to ovirt-3.1  (oschreib, 14:47:52)
>    * AGREED: GA will be postponed to the 9th of July  (oschreib,
>      14:53:58)
>
> * upcoming workshops  (mburns, 14:56:11)
>    * feedback from LC Japan  (mburns, 14:57:50)
>    * LINK: http://www.ovirt.org/wiki/LC_Japan_Workshop_Post-Mortem
>      (mburns, 14:57:56)
>    * time to begin planning for LC North America (San Diego, Aug 29-31)
>      (mburns, 14:58:34)
>    * linux.conf.au has reached out requesting oVirt related presentations
>      (mburns, 15:01:16)
>    * LINK:
>      https://events.linuxfoundation.org/events/linuxcon/co-located-events
>      (dneary, 15:03:01)
>    * lh to send agenda to LinuxCon North America  (mburns, 15:04:23)
>
> * other topics  (mburns, 15:04:52)
>    * ACTION: sgordon to send email about release notes  (mburns,
>      15:05:50)
>    * ACTION: dneary to ensure that discussion starts on infra@ on the
>      creation of a community infrastructure team  (dneary, 15:12:46)
>    * ACTION: dneary to ensure that discussion starts on infra@ on the
>      creation of a community infrastructure team  (mburns, 15:13:09)
>
> Meeting ended at 15:15:08 UTC.
>
>
>
>
> Action Items
> ------------
> * douglas please push http://gerrit.ovirt.org/#/c/5379/ upstream and to
>    ovirt-3.1
> * douglas please push http://gerrit.ovirt.org/#/c/5379/ upstream and to
>    ovirt-3.1
> * sgordon to send email about release notes
> * dneary to ensure that discussion starts on infra@ on the creation of a
>    community infrastructure team
> * dneary to ensure that discussion starts on infra@ on the creation of a
>    community infrastructure team
>
>
>
>
> Action Items, by person
> -----------------------
> * dneary
>    * dneary to ensure that discussion starts on infra@ on the creation of
>      a community infrastructure team
>    * dneary to ensure that discussion starts on infra@ on the creation of
>      a community infrastructure team
> * sgordon
>    * sgordon to send email about release notes
> * **UNASSIGNED**
>    * douglas please push http://gerrit.ovirt.org/#/c/5379/ upstream and
>      to ovirt-3.1
>    * douglas please push http://gerrit.ovirt.org/#/c/5379/ upstream and
>      to ovirt-3.1
>
>
>
>
> People Present (lines said)
> ---------------------------
> * oschreib (93)
> * mburns (74)
> * dneary (18)
> * danken (15)
> * lh (14)
> * sgordon (8)
> * fsimonce (8)
> * quaid (7)
> * ilvovsky (6)
> * ykaul (4)
> * itamar (3)
> * RobertM (3)
> * ovirtbot (3)
> * rharper (3)
> * yzaslavs (2)
> * Guest571 (1)
> * mkolesni (1)
> * mkolesni_ (1)
> * ofrenkel (1)
> * READ10 (1)
> * miki (1)
> * masayag (1)
> * mgoldboi (1)
>
>
>
>
> Generated by `MeetBot`_ 0.1.4
>
> .. _`MeetBot`: http://wiki.debian.org/MeetBot
>
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch




From mburns at redhat.com  Wed Jun 20 18:29:02 2012
From: mburns at redhat.com (Mike Burns)
Date: Wed, 20 Jun 2012 14:29:02 -0400
Subject: [Users] oVirt Weekly Meeting Minutes -- 2012-06-20
In-Reply-To: <4FE211F0.7030709@redhat.com>
References: <1340205455.3734.74.camel@beelzebub.mburnsfire.net>
	<4FE211F0.7030709@redhat.com>
Message-ID: <1340216942.16688.1.camel@mburns-laptop>

On Wed, 2012-06-20 at 21:09 +0300, Yaniv Kaul wrote:
> Was test day post-mortem discussed? I had to leave before the meeting 
> ended, but I don't see it here.
> Y.
> 

Not explicitly, but we essentially covered the results of the test day
in discussing the release status.

Mike

> 
> On 06/20/2012 06:17 PM, Mike Burns wrote:
> > Minutes:        http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-20-14.00.html
> > Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-20-14.00.txt
> > Log:            http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-20-14.00.log.html
> >
> > =========================
> > #ovirt: oVirt Weekly Sync
> > =========================
> >
> >
> > Meeting started by mburns at 14:00:42 UTC. The full logs are available
> > at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-20-14.00.log.html
> > .
> >
> >
> >
> > Meeting summary
> > ---------------
> > * agenda and roll call  (mburns, 14:01:16)
> >
> > * Status of next release  (mburns, 14:04:16)
> >    * 9 bugs in 3.1 release tracker  (oschreib, 14:06:12)
> >    * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=822145
> >      (oschreib, 14:06:16)
> >    * current targeted GA is 27-June  (mburns, 14:06:22)
> >    * LINK: http://www.ovirt.org/releases/beta/fedora/17/   (oschreib,
> >      14:10:03)
> >    * LINK: http://www.ovirt.org/releases/beta/fedora/17/   (mburns,
> >      14:10:34)
> >    * new beta build (3.1.0-0.1.20120620git6ef9f8.fc17) available
> >      (oschreib, 14:10:58)
> >    * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=828633
> >      (oschreib, 14:11:36)
> >    * libvirt - Sanlock locking failed for readonly devices (MODIFIED)
> >      (oschreib, 14:11:57)
> >    * waiting on danpb  (oschreib, 14:25:17)
> >    * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=828633   (mburns,
> >      14:25:34)
> >    * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=831998
> >      (oschreib, 14:26:37)
> >    * VDSM - It's impossible to create bond with setupNetworks (ASSIGNED)
> >      (oschreib, 14:26:58)
> >    * WIP  (oschreib, 14:29:45)
> >    * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=832199
> >      (oschreib, 14:31:02)
> >    * VDSM - vdsmd init script times out due to lengthy semanage operation
> >      (ASSIGNED)  (oschreib, 14:31:21)
> >    * WIP  (oschreib, 14:35:39)
> >    * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=832517
> >      (oschreib, 14:36:43)
> >    * node - sshd daemon is not starting correctly after complete the
> >      installation of oVirt Node (NEW)  (oschreib, 14:36:58)
> >    * WIP, fix to be push in the next couple of days  (oschreib, 14:37:42)
> >    * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=832539
> >      (oschreib, 14:37:55)
> >    * node - iptables blocking communication between node and engine
> >      (POST)  (oschreib, 14:38:06)
> >    * in review, should be in next build  (oschreib, 14:38:46)
> >    * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=832577
> >      (oschreib, 14:38:56)
> >    * vdsm - ovirt-node can't be approved due to missing /rhev/data-center
> >      (POST)  (oschreib, 14:39:15)
> >    * pushed upstream, need to rebase to ovirt-3.1 branch  (oschreib,
> >      14:40:29)
> >    * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=833201
> >      (oschreib, 14:40:39)
> >    * vdsm - Failed to add host - does not accept vdsm 4.10 (POST)
> >      (oschreib, 14:41:09)
> >    * pushed  (oschreib, 14:42:42)
> >    * ACTION: douglas please push http://gerrit.ovirt.org/#/c/5379/
> >      upstream and to ovirt-3.1  (danken, 14:46:12)
> >    * ACTION: douglas please push http://gerrit.ovirt.org/#/c/5379/
> >      upstream and to ovirt-3.1  (oschreib, 14:47:52)
> >    * AGREED: GA will be postponed to the 9th of July  (oschreib,
> >      14:53:58)
> >
> > * upcoming workshops  (mburns, 14:56:11)
> >    * feedback from LC Japan  (mburns, 14:57:50)
> >    * LINK: http://www.ovirt.org/wiki/LC_Japan_Workshop_Post-Mortem
> >      (mburns, 14:57:56)
> >    * time to begin planning for LC North America (San Diego, Aug 29-31)
> >      (mburns, 14:58:34)
> >    * linux.conf.au has reached out requesting oVirt related presentations
> >      (mburns, 15:01:16)
> >    * LINK:
> >      https://events.linuxfoundation.org/events/linuxcon/co-located-events
> >      (dneary, 15:03:01)
> >    * lh to send agenda to LinuxCon North America  (mburns, 15:04:23)
> >
> > * other topics  (mburns, 15:04:52)
> >    * ACTION: sgordon to send email about release notes  (mburns,
> >      15:05:50)
> >    * ACTION: dneary to ensure that discussion starts on infra@ on the
> >      creation of a community infrastructure team  (dneary, 15:12:46)
> >    * ACTION: dneary to ensure that discussion starts on infra@ on the
> >      creation of a community infrastructure team  (mburns, 15:13:09)
> >
> > Meeting ended at 15:15:08 UTC.
> >
> >
> >
> >
> > Action Items
> > ------------
> > * douglas please push http://gerrit.ovirt.org/#/c/5379/ upstream and to
> >    ovirt-3.1
> > * douglas please push http://gerrit.ovirt.org/#/c/5379/ upstream and to
> >    ovirt-3.1
> > * sgordon to send email about release notes
> > * dneary to ensure that discussion starts on infra@ on the creation of a
> >    community infrastructure team
> > * dneary to ensure that discussion starts on infra@ on the creation of a
> >    community infrastructure team
> >
> >
> >
> >
> > Action Items, by person
> > -----------------------
> > * dneary
> >    * dneary to ensure that discussion starts on infra@ on the creation of
> >      a community infrastructure team
> >    * dneary to ensure that discussion starts on infra@ on the creation of
> >      a community infrastructure team
> > * sgordon
> >    * sgordon to send email about release notes
> > * **UNASSIGNED**
> >    * douglas please push http://gerrit.ovirt.org/#/c/5379/ upstream and
> >      to ovirt-3.1
> >    * douglas please push http://gerrit.ovirt.org/#/c/5379/ upstream and
> >      to ovirt-3.1
> >
> >
> >
> >
> > People Present (lines said)
> > ---------------------------
> > * oschreib (93)
> > * mburns (74)
> > * dneary (18)
> > * danken (15)
> > * lh (14)
> > * sgordon (8)
> > * fsimonce (8)
> > * quaid (7)
> > * ilvovsky (6)
> > * ykaul (4)
> > * itamar (3)
> > * RobertM (3)
> > * ovirtbot (3)
> > * rharper (3)
> > * yzaslavs (2)
> > * Guest571 (1)
> > * mkolesni (1)
> > * mkolesni_ (1)
> > * ofrenkel (1)
> > * READ10 (1)
> > * miki (1)
> > * masayag (1)
> > * mgoldboi (1)
> >
> >
> >
> >
> > Generated by `MeetBot`_ 0.1.4
> >
> > .. _`MeetBot`: http://wiki.debian.org/MeetBot
> >
> > _______________________________________________
> > Arch mailing list
> > Arch at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/arch
> 
> 
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users




From oschreib at redhat.com  Thu Jun 21 08:28:03 2012
From: oschreib at redhat.com (Ofer Schreiber)
Date: Thu, 21 Jun 2012 04:28:03 -0400 (EDT)
Subject: Two updates from the oVirt team
In-Reply-To: <1d6ff4d8-9128-4545-a62a-92c1b2af6bf1@zmail14.collab.prod.int.phx2.redhat.com>
Message-ID: <5bb315fc-a5aa-47bd-a6e7-33301aff05ec@zmail14.collab.prod.int.phx2.redhat.com>

Hey everyone,

There are two updates I'd like to share with you:
1. oVirt 3.1 release date has been delayed to the 9th of July.
As you all know, We're in the middle of creating a new build of oVirt.
With your help, we found multiple issues which we consider as release blockers. Some of these issues require a few days to be solved properly, and as a result, we had to delay the general availability of oVirt.

2. New ovirt-engine rpms are available for download at http://ovirt.org/releases/beta/fedora/17
This build contain multiple bug fixes, as well as a new versioning schema, which will ensure future updates will be done correctly.
Please note, that due to the new versions, we don't support in-beta upgrade. please make sure you clean up you environment (using engine-cleanup, and yum remove) before installing the new rpms (version 3.1.0-0.1.20120620git6ef9f8.fc17)
New VDSM rpms should be available in the beginning of next week). 

Regards,
--
Ofer Schreiber
oVirt Release Manager


From bazulay at redhat.com  Thu Jun 21 16:11:13 2012
From: bazulay at redhat.com (Barak Azulay)
Date: Thu, 21 Jun 2012 19:11:13 +0300
Subject: Post-Mortem Notes
In-Reply-To: <4FDFA8D7.2010904@redhat.com>
References: <4FD910CA.1080808@redhat.com> <4FDFA8D7.2010904@redhat.com>
Message-ID: <4FE347A1.1060208@redhat.com>

On 06/19/2012 01:16 AM, Leslie Hawthorn wrote:
> Hello everyone,
>
> Thank you for your detailed feedback. I have captured it on the oVirt
> wiki [0] for later reference. I have also shared these notes with the
> Linux Foundation Events Team.
>
> I believe we have sufficiently detailed feedback to help us plan the
> next workshop. I'll address this item during this week's oVirt IRC meeting.
>
> [0] - http://www.ovirt.org/wiki/LC_Japan_Workshop_Post-Mortem
>
> Cheers,
> LH

Thanks for setting it up.

BTW the videos from the VDSM sessions were not uploaded (the VDSM 
session mentioned is another ovirt arch session that I gave in the mini 
summit).

Do you away to check with the Linux Foundation ?

Thanks
Barak Azulay


>
> On 06/13/2012 03:14 PM, Leslie Hawthorn wrote:
>> Hello everyone,
>>
>> I'd like to collect feedback from everyone on last week's oVirt
>> workshop at LinuxCon Japan. [0] Please reply back with comments by
>> close of business this Friday, 15 June.
>>
>> Once we have gathered feedback on list, I'll capture it on the oVirt
>> wiki. We can then use what we've learned to help construct the agenda
>> and other plans for other upcoming oVirt workshops at LinuxCons. [1]
>>
>> If you know that you would like to volunteer as an instructor for
>> future workshops or would like to suggest alternate content for the
>> workshop, please include that in your feedback.
>>
>> - Course Material
>> What sessions were most well received? Which ones require improvement?
>> Any additional sessions we'd suggest?
>>
>> - Audience Participation
>> How many attendees? How did the Q&A periods go? Would we like to
>> prepare a post-event attendee survey? (I recommend we do the survey
>> and can prepare some questions for the group if that's useful.)
>>
>> - Developer/user traction resulting from engaging at workshop
>> Did this workshop help us to gain new developers or users? Reinforce
>> relationships with existing community members?
>>
>> - Promotion of the event, both before and after
>> What could be done to more effectively promote the event prior to the
>> workshops? Videos and slides from the workshop should be posted on the
>> LC Japan site tomorrow; what action would the community like to take
>> to promote this content?
>>
>> - A/V and Room Set up
>> Did the seating arrangements work well for the workshop format? Did
>> the A/V work well, including the videotaping process?
>>
>> - Food and beverage
>> Did the catered in lunch help to keep the flow of the workshop
>> productive? Was the food of good quality and in keeping with the needs
>> of attendee dietary constraints?
>>
>> - Give aways
>> We did not produce attendee gifts for the oVirt workshop. Thoughts on
>> whether this would be a welcome addition in the future? Suggestions
>> for type of gift also welcome.
>>
>> - Any other feedback
>>
>> If it is preferable to discuss this feedback real-time, I will ask
>> Mike Burns to give us more time for this topic during next week's
>> oVirt IRC meeting.
>>
>> [0] -
>> https://events.linuxfoundation.org/events/linuxcon-japan/ovirt-gluster-workshops
>>
>> [1] - http://www.ovirt.org/wiki/OVirt_Global_Workshops
>>
>> Cheers,
>> LH
>>
>
>



From bazulay at redhat.com  Thu Jun 21 16:22:26 2012
From: bazulay at redhat.com (Barak Azulay)
Date: Thu, 21 Jun 2012 19:22:26 +0300
Subject: Post-Mortem Notes
In-Reply-To: <4FE347A1.1060208@redhat.com>
References: <4FD910CA.1080808@redhat.com> <4FDFA8D7.2010904@redhat.com>
	<4FE347A1.1060208@redhat.com>
Message-ID: <4FE34A42.5030906@redhat.com>

On 06/21/2012 07:11 PM, Barak Azulay wrote:
> On 06/19/2012 01:16 AM, Leslie Hawthorn wrote:
>> Hello everyone,
>>
>> Thank you for your detailed feedback. I have captured it on the oVirt
>> wiki [0] for later reference. I have also shared these notes with the
>> Linux Foundation Events Team.
>>
>> I believe we have sufficiently detailed feedback to help us plan the
>> next workshop. I'll address this item during this week's oVirt IRC
>> meeting.
>>
>> [0] - http://www.ovirt.org/wiki/LC_Japan_Workshop_Post-Mortem
>>
>> Cheers,
>> LH
>
> Thanks for setting it up.
>
> BTW the videos from the VDSM sessions were not uploaded (the VDSM
> session mentioned is another ovirt arch session that I gave in the mini
> summit).
>
> Do you away to check with the Linux Foundation ?

     == have ==

>
> Thanks
> Barak Azulay
>
>
>>
>> On 06/13/2012 03:14 PM, Leslie Hawthorn wrote:
>>> Hello everyone,
>>>
>>> I'd like to collect feedback from everyone on last week's oVirt
>>> workshop at LinuxCon Japan. [0] Please reply back with comments by
>>> close of business this Friday, 15 June.
>>>
>>> Once we have gathered feedback on list, I'll capture it on the oVirt
>>> wiki. We can then use what we've learned to help construct the agenda
>>> and other plans for other upcoming oVirt workshops at LinuxCons. [1]
>>>
>>> If you know that you would like to volunteer as an instructor for
>>> future workshops or would like to suggest alternate content for the
>>> workshop, please include that in your feedback.
>>>
>>> - Course Material
>>> What sessions were most well received? Which ones require improvement?
>>> Any additional sessions we'd suggest?
>>>
>>> - Audience Participation
>>> How many attendees? How did the Q&A periods go? Would we like to
>>> prepare a post-event attendee survey? (I recommend we do the survey
>>> and can prepare some questions for the group if that's useful.)
>>>
>>> - Developer/user traction resulting from engaging at workshop
>>> Did this workshop help us to gain new developers or users? Reinforce
>>> relationships with existing community members?
>>>
>>> - Promotion of the event, both before and after
>>> What could be done to more effectively promote the event prior to the
>>> workshops? Videos and slides from the workshop should be posted on the
>>> LC Japan site tomorrow; what action would the community like to take
>>> to promote this content?
>>>
>>> - A/V and Room Set up
>>> Did the seating arrangements work well for the workshop format? Did
>>> the A/V work well, including the videotaping process?
>>>
>>> - Food and beverage
>>> Did the catered in lunch help to keep the flow of the workshop
>>> productive? Was the food of good quality and in keeping with the needs
>>> of attendee dietary constraints?
>>>
>>> - Give aways
>>> We did not produce attendee gifts for the oVirt workshop. Thoughts on
>>> whether this would be a welcome addition in the future? Suggestions
>>> for type of gift also welcome.
>>>
>>> - Any other feedback
>>>
>>> If it is preferable to discuss this feedback real-time, I will ask
>>> Mike Burns to give us more time for this topic during next week's
>>> oVirt IRC meeting.
>>>
>>> [0] -
>>> https://events.linuxfoundation.org/events/linuxcon-japan/ovirt-gluster-workshops
>>>
>>>
>>> [1] - http://www.ovirt.org/wiki/OVirt_Global_Workshops
>>>
>>> Cheers,
>>> LH
>>>
>>
>>
>
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch
>
>



From lhawthor at redhat.com  Thu Jun 21 16:24:42 2012
From: lhawthor at redhat.com (Leslie Hawthorn)
Date: Thu, 21 Jun 2012 09:24:42 -0700
Subject: Post-Mortem Notes
In-Reply-To: <4FE347A1.1060208@redhat.com>
References: <4FD910CA.1080808@redhat.com> <4FDFA8D7.2010904@redhat.com>
	<4FE347A1.1060208@redhat.com>
Message-ID: <4FE34ACA.6060601@redhat.com>

On 06/21/2012 09:11 AM, Barak Azulay wrote:
> On 06/19/2012 01:16 AM, Leslie Hawthorn wrote:
>> Hello everyone,
>>
>> Thank you for your detailed feedback. I have captured it on the oVirt
>> wiki [0] for later reference. I have also shared these notes with the
>> Linux Foundation Events Team.
>>
>> I believe we have sufficiently detailed feedback to help us plan the
>> next workshop. I'll address this item during this week's oVirt IRC 
>> meeting.
>>
>> [0] - http://www.ovirt.org/wiki/LC_Japan_Workshop_Post-Mortem
>>
>> Cheers,
>> LH
>
> Thanks for setting it up.
>
> BTW the videos from the VDSM sessions were not uploaded (the VDSM 
> session mentioned is another ovirt arch session that I gave in the 
> mini summit).
>
> Do you away to check with the Linux Foundation ?
>
I'll check in with them.

Cheers,
LH


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

identi.ca/lh
twitter.com/lhawthorn



From lhawthor at redhat.com  Thu Jun 21 20:31:03 2012
From: lhawthor at redhat.com (Leslie Hawthorn)
Date: Thu, 21 Jun 2012 13:31:03 -0700
Subject: oVirt Workshop at LinuxCon North America
Message-ID: <4FE38487.7050004@redhat.com>

Hello everyone,

Following up from this week's IRC meeting, we've asked the Linux 
Foundation to replicate the agenda from LinuxCon Japan on the LC North 
America site. That's in process, but they'd like us to get the names and 
bios of our confirmed speakers to them no later than next Wednesday, 27 
June 2012.

I'll leave it to everyone to wrangle about who would like to speak and 
cover particular sessions. My goal with this workshop is to have a more 
diverse speaker line up, so please do volunteer if you're attending 
LinuxCon North America and would be willing to lead a session(s).

[0] - 
https://events.linuxfoundation.org/events/linuxcon-japan/ovirt-gluster-workshops

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  Thu Jun 21 20:44:57 2012
From: mburns at redhat.com (Mike Burns)
Date: Thu, 21 Jun 2012 16:44:57 -0400
Subject: oVirt Workshop at LinuxCon North America
In-Reply-To: <4FE38487.7050004@redhat.com>
References: <4FE38487.7050004@redhat.com>
Message-ID: <1340311497.17747.20.camel@mburns-laptop>

On Thu, 2012-06-21 at 13:31 -0700, Leslie Hawthorn wrote:
> Hello everyone,
> 
> Following up from this week's IRC meeting, we've asked the Linux 
> Foundation to replicate the agenda from LinuxCon Japan on the LC North 
> America site. That's in process, but they'd like us to get the names and 
> bios of our confirmed speakers to them no later than next Wednesday, 27 
> June 2012.
> 
> I'll leave it to everyone to wrangle about who would like to speak and 
> cover particular sessions. My goal with this workshop is to have a more 
> diverse speaker line up, so please do volunteer if you're attending 
> LinuxCon North America and would be willing to lead a session(s).
> 
> [0] - 
> https://events.linuxfoundation.org/events/linuxcon-japan/ovirt-gluster-workshops
> 
> Cheers,
> LH
> 

I will be there for the workshop to do the node presentation.  I can
also help with the overview and demo.  

Are there people from the engine team and vdsm teams planning to go?

Since it's not listed here, LinuxCon North America is August 29-31 in
San Diego.

Mike



From iheim at redhat.com  Thu Jun 21 21:07:39 2012
From: iheim at redhat.com (Itamar Heim)
Date: Fri, 22 Jun 2012 00:07:39 +0300
Subject: oVirt Workshop at LinuxCon North America
In-Reply-To: <1340311497.17747.20.camel@mburns-laptop>
References: <4FE38487.7050004@redhat.com>
	<1340311497.17747.20.camel@mburns-laptop>
Message-ID: <4FE38D1B.3050104@redhat.com>

On 06/21/2012 11:44 PM, Mike Burns wrote:
> On Thu, 2012-06-21 at 13:31 -0700, Leslie Hawthorn wrote:
>> Hello everyone,
>>
>> Following up from this week's IRC meeting, we've asked the Linux
>> Foundation to replicate the agenda from LinuxCon Japan on the LC North
>> America site. That's in process, but they'd like us to get the names and
>> bios of our confirmed speakers to them no later than next Wednesday, 27
>> June 2012.
>>
>> I'll leave it to everyone to wrangle about who would like to speak and
>> cover particular sessions. My goal with this workshop is to have a more
>> diverse speaker line up, so please do volunteer if you're attending
>> LinuxCon North America and would be willing to lead a session(s).
>>
>> [0] -
>> https://events.linuxfoundation.org/events/linuxcon-japan/ovirt-gluster-workshops
>>
>> Cheers,
>> LH
>>
>
> I will be there for the workshop to do the node presentation.  I can
> also help with the overview and demo.
>
> Are there people from the engine team and vdsm teams planning to go?

leslie - I suggest polling for other suggestions for sessions as well.
maybe someone working with ovirt, or extending it, or developing 
something interesting for a future use case would want to cover it in 
the workshop.

thanks,
    Itamar

>
> Since it's not listed here, LinuxCon North America is August 29-31 in
> San Diego.
>
> Mike
>
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch



From lhawthor at redhat.com  Thu Jun 21 22:25:26 2012
From: lhawthor at redhat.com (Leslie Hawthorn)
Date: Thu, 21 Jun 2012 15:25:26 -0700
Subject: oVirt Workshop at LinuxCon North America
In-Reply-To: <4FE38D1B.3050104@redhat.com>
References: <4FE38487.7050004@redhat.com>
	<1340311497.17747.20.camel@mburns-laptop>
	<4FE38D1B.3050104@redhat.com>
Message-ID: <4FE39F56.40202@redhat.com>

On 06/21/2012 02:07 PM, Itamar Heim wrote:
> On 06/21/2012 11:44 PM, Mike Burns wrote:
>> On Thu, 2012-06-21 at 13:31 -0700, Leslie Hawthorn wrote:
>>> Hello everyone,
>>>
>>> Following up from this week's IRC meeting, we've asked the Linux
>>> Foundation to replicate the agenda from LinuxCon Japan on the LC North
>>> America site. That's in process, but they'd like us to get the names 
>>> and
>>> bios of our confirmed speakers to them no later than next Wednesday, 27
>>> June 2012.
>>>
>>> I'll leave it to everyone to wrangle about who would like to speak and
>>> cover particular sessions. My goal with this workshop is to have a more
>>> diverse speaker line up, so please do volunteer if you're attending
>>> LinuxCon North America and would be willing to lead a session(s).
>>>
>>> [0] -
>>> https://events.linuxfoundation.org/events/linuxcon-japan/ovirt-gluster-workshops 
>>>
>>>
>>> Cheers,
>>> LH
>>>
>>
>> I will be there for the workshop to do the node presentation.  I can
>> also help with the overview and demo.
>>
>> Are there people from the engine team and vdsm teams planning to go?
>
> leslie - I suggest polling for other suggestions for sessions as well.
> maybe someone working with ovirt, or extending it, or developing 
> something interesting for a future use case would want to cover it in 
> the workshop.
>
Agreed that this would be most welcome - I sent off the agenda from LC 
Japan to the Linux Foundation so we had something to display on the 
conference site to encourage folks to register.

What are topics that the other list members would like to see us 
present? Present themselves?

As Mike stated earlier, LinuxCon North America takes place in San Diego, 
California, US on 29-31 August. The oVirt workshop takes place the day 
before the conference proper begins, on Tuesday, 28 August.

https://events.linuxfoundation.org/events/linuxcon

Cheers,
LH


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

identi.ca/lh
twitter.com/lhawthorn



From kwade at redhat.com  Mon Jun 25 05:19:24 2012
From: kwade at redhat.com (Karsten 'quaid' Wade)
Date: Sun, 24 Jun 2012 22:19:24 -0700
Subject: Outage :: www.ovirt.org :: 2012-06-25 0200 to 0300 UTC
In-Reply-To: <4FE757CB.3060708@redhat.com>
References: <4FE757CB.3060708@redhat.com>
Message-ID: <4FE7F4DC.3070601@redhat.com>

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

I am rescheduling this reboot - I forgot to warn arch@, and I got to
the hotel later than I'd hoped.

New time: 2012-06-25 2100 UTC.

To see this in your local time:

date -d "2012-06-25 2100 UTC"

If there is any problem with the new time, let me know.

On 06/24/2012 11:09 AM, Karsten 'quaid' Wade wrote:
> We're filling up the disk on www.ovirt.org, which is expected
> since it's only 10 GB. I'm going to double that, which requires a
> reboot.
> 
> Prior to the reboot I'll come on IRC and make sure everyone is 
> prepared, and hold-off the reboot if needed.
> 
> I know this window lands right in the morning for some of us, so
> if this is an issue, email me back. I could reschedule for 2100 UTC
> or so.
> 
> The restart should only take a few minutes. The hour window is to
> give me time to start and finish or rollback if there is a
> problem.
> 
> == When ==
> 
> 0200 to 0300 UTC
> 
> date -d "2012-06-25 0200 UTC" date -d "2012-06-25 0300 UTC"
> 
> == Affected services ==
> 
> lists.ovirt.org www.ovirt.org/wiki www.ovirt.org/.* ovirtbot (IRC
> bot)
> 
> _______________________________________________ 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/

iD8DBQFP5/Tb2ZIOBq0ODEERApDGAKDN5AT9UI91ZGmzYKADhzkcc6PCUACgnCfg
0At/7OIovSTeTSDfqD6Wibg=
=4eGk
-----END PGP SIGNATURE-----


From mburns at redhat.com  Mon Jun 25 12:27:18 2012
From: mburns at redhat.com (Mike Burns)
Date: Mon, 25 Jun 2012 08:27:18 -0400
Subject: Call For Agenda Items -- oVirt Weekly Meeting 2012-06-20
Message-ID: <1340627238.3656.14.camel@beelzebub.mburnsfire.net>

The next oVirt Weekly Meeting is scheduled for 2012-06-20 at 15:00 UTC
(10:00 AM EDT).

Current Agenda Items (as of this email)

* Status of Next Release
* Sub-project reports (engine, vdsm, node)
* Upcoming workshops


Latest Agenda is listed here:
http://www.ovirt.org/wiki/Meetings#Weekly_project_sync_meeting

Reminder:  If you propose an additional agenda item, please be present
for the meeting to lead the discussion on it.

Thanks

Mike



From mburns at redhat.com  Mon Jun 25 16:11:53 2012
From: mburns at redhat.com (Mike Burns)
Date: Mon, 25 Jun 2012 12:11:53 -0400
Subject: Call For Agenda Items -- oVirt Weekly Meeting 2012-06-20
In-Reply-To: <1340627238.3656.14.camel@beelzebub.mburnsfire.net>
References: <1340627238.3656.14.camel@beelzebub.mburnsfire.net>
Message-ID: <1340640713.3656.15.camel@beelzebub.mburnsfire.net>

So, the date is obviously 2012-06-27 and not 06-20...

On Mon, 2012-06-25 at 08:27 -0400, Mike Burns wrote:
> The next oVirt Weekly Meeting is scheduled for 2012-06-20 at 15:00 UTC
> (10:00 AM EDT).
> 
> Current Agenda Items (as of this email)
> 
> * Status of Next Release
> * Sub-project reports (engine, vdsm, node)
> * Upcoming workshops
> 
> 
> Latest Agenda is listed here:
> http://www.ovirt.org/wiki/Meetings#Weekly_project_sync_meeting
> 
> Reminder:  If you propose an additional agenda item, please be present
> for the meeting to lead the discussion on it.
> 
> Thanks
> 
> Mike
> 
> _______________________________________________
> Board mailing list
> Board at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/board




From lhawthor at redhat.com  Mon Jun 25 16:57:08 2012
From: lhawthor at redhat.com (Leslie Hawthorn)
Date: Mon, 25 Jun 2012 09:57:08 -0700
Subject: Post-Mortem Notes
In-Reply-To: <4FE34A42.5030906@redhat.com>
References: <4FD910CA.1080808@redhat.com> <4FDFA8D7.2010904@redhat.com>
	<4FE347A1.1060208@redhat.com> <4FE34A42.5030906@redhat.com>
Message-ID: <4FE89864.1020808@redhat.com>

On 06/21/2012 09:22 AM, Barak Azulay wrote:
>> Thanks for setting it up.
>>
>> BTW the videos from the VDSM sessions were not uploaded (the VDSM
>> session mentioned is another ovirt arch session that I gave in the mini
>> summit).
>>
>> Do you have a way to check with the Linux Foundation ?
>
>
I checked in with the Linux Foundation and it turns out that the audio 
from this VDSM session was very poor so the video was not usable. I have 
asked the LF to take down the incorrect video. Would you like to see the 
mini-summit session linked from the oVirt workshop page? I don't know if 
it's possible, but it cannot hurt to ask if this is a desired outcome.

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  Tue Jun 26 12:43:49 2012
From: oschreib at redhat.com (Ofer Schreiber)
Date: Tue, 26 Jun 2012 08:43:49 -0400 (EDT)
Subject: [Users] Two updates from the oVirt team
In-Reply-To: <5bb315fc-a5aa-47bd-a6e7-33301aff05ec@zmail14.collab.prod.int.phx2.redhat.com>
Message-ID: <fbf58aca-a7e5-47e7-8fd3-1ba148f109c0@zmail14.collab.prod.int.phx2.redhat.com>

As promised, A new vdsm build (vdsm-4.10.0-2) is available in the beta repo.


----- Original Message -----
> Hey everyone,
> 
> There are two updates I'd like to share with you:
> 1. oVirt 3.1 release date has been delayed to the 9th of July.
> As you all know, We're in the middle of creating a new build of
> oVirt.
> With your help, we found multiple issues which we consider as release
> blockers. Some of these issues require a few days to be solved
> properly, and as a result, we had to delay the general availability
> of oVirt.
> 
> 2. New ovirt-engine rpms are available for download at
> http://ovirt.org/releases/beta/fedora/17
> This build contain multiple bug fixes, as well as a new versioning
> schema, which will ensure future updates will be done correctly.
> Please note, that due to the new versions, we don't support in-beta
> upgrade. please make sure you clean up you environment (using
> engine-cleanup, and yum remove) before installing the new rpms
> (version 3.1.0-0.1.20120620git6ef9f8.fc17)
> New VDSM rpms should be available in the beginning of next week).
> 
> Regards,
> --
> Ofer Schreiber
> oVirt Release Manager
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 


From oschreib at redhat.com  Wed Jun 27 15:11:45 2012
From: oschreib at redhat.com (Ofer Schreiber)
Date: Wed, 27 Jun 2012 11:11:45 -0400 (EDT)
Subject: oVirt Weekly Meeting Minutes -- 2012-06-27
In-Reply-To: <0e3b308a-6829-4827-8116-ca7c2652f5df@zmail14.collab.prod.int.phx2.redhat.com>
Message-ID: <9653ccad-0611-4930-b489-890d3ba50531@zmail14.collab.prod.int.phx2.redhat.com>

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

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

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

Meeting summary
---------------
* agenda and roll call  (oschreib, 14:00:29)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=822145
    (oschreib, 14:12:20)

* Status of next release  (oschreib, 14:12:41)
  * GA date is July 9th  (oschreib, 14:12:53)
  * 11 blocker currently in the 3.1 tracker  (oschreib, 14:13:12)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=822145
    (oschreib, 14:13:32)
  * Sanlock locking failed for readonly devices  (component: libvirt,
    status: ASSIGNED)  (oschreib, 14:16:17)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=828633
    (oschreib, 14:16:32)
  * IDEA: the feature owner can put the wiki page in a different
    category  e.g. [[Category:Feature complete]]  (quaid, 14:16:56)
  * patch waiting for a review  (oschreib, 14:18:12)
  * It's impossible to create bond with setupNetworks (component: vdsm,
    status: ASSIGNED)  (oschreib, 14:19:13)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=831998
    (oschreib, 14:19:23)
  * merged upstream, waiting for the Fedora backport  (oschreib,
    14:23:01)
  * vdsmd init script times out due to lengthy semanage operation
    (component: vdsm, status: POST)  (oschreib, 14:23:48)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=832199
    (oschreib, 14:23:57)
  * patch in review  (oschreib, 14:26:55)
  * 3.1: sshd daemon is not starting correctly after complete the
    installation of oVirt Node (component: node, status: MODIFIED)
    (oschreib, 14:27:26)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=832517
    (oschreib, 14:27:35)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=832199   (danken,
    14:29:05)
  * bug fixed, new node build today if possible  (oschreib, 14:30:01)
  * ACTION: mburns to build and upload new node version  (oschreib,
    14:30:14)
  * 3.1: iptables blocking communication between node and engine
    (component: node, status: MODIFIED)  (oschreib, 14:31:30)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=832539
    (oschreib, 14:31:36)
  * should be in next build  (oschreib, 14:33:07)
  * ovirt-node can't be approved due to missing /rhev/data-center
    (component: vdsm, status: ON_QA)  (oschreib, 14:33:45)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=832577
    (oschreib, 14:33:51)
  * waiting for a verification  (oschreib, 14:35:29)
  * 3.1 Allow to create VLANed network on top of existing bond
    (component: vdsm, status: POST)  (oschreib, 14:36:05)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=833119
    (oschreib, 14:36:20)
  * pushed upstream, should be backported tomorrow to Fedora  (oschreib,
    14:40:56)
  * Failed to add host - does not accept vdsm 4.10 (component: vdsm,
    status: ON_QA)  (oschreib, 14:41:24)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=833201
    (oschreib, 14:41:33)
  * waiting for a verification  (oschreib, 14:43:51)
  *  [vdsm][bridgeless] BOOTPROTO/IPADDR/NETMASK options are not set on
    interface (component: vdsm, status: NEW)  (oschreib, 14:44:18)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=834281
    (oschreib, 14:44:26)
  * not a 3.1 blocker  (oschreib, 14:51:06)
  * Leak of keystore file descriptors in ovirt-engine (component:
    engine, status: MODIFIED)  (oschreib, 14:52:00)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=834399
    (oschreib, 14:52:08)
  * pushed and backported, waiting for a build  (oschreib, 14:52:22)

* Sub-project reports  (oschreib, 14:55:08)
  * status covered in BZ overview  (oschreib, 14:57:17)

* Upcoming workshops  (oschreib, 14:57:29)
  * no updates about upcoming workshops  (oschreib, 14:59:25)

* Release notes  (oschreib, 14:59:56)
  * 3.1 release notes should be given to sgordon by mail  (oschreib,
    15:04:51)
  * ACTION: oschreib to nag maintainers about RN  (oschreib, 15:06:04)

Meeting ended at 15:08:51 UTC.

Action Items
------------
* mburns to build and upload new node version
* oschreib to nag maintainers about RN

Action Items, by person
-----------------------
* mburns
  * mburns to build and upload new node version
* oschreib
  * oschreib to nag maintainers about RN
* **UNASSIGNED**
  * (none)

People Present (lines said)
---------------------------
* oschreib (119)
* sgordon (24)
* danken (18)
* RobertM (10)
* ilvovsky (8)
* quaid (6)
* fabiand (6)
* mburns (4)
* ofrenkel (3)
* READ10 (2)
* ovirtbot (2)
* Guest1297 (1)
* crobinso (1)
* dustins (1)


Generated by `MeetBot`_ 0.1.4

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


From robert at middleswarth.net  Thu Jun 28 06:57:32 2012
From: robert at middleswarth.net (Robert Middleswarth)
Date: Thu, 28 Jun 2012 02:57:32 -0400
Subject: [Users] What are you looking for from oVirt?
In-Reply-To: <4FDB0D23.1050603@redhat.com>
References: <4FD8A370.3010904@redhat.com> <4FDB0D23.1050603@redhat.com>
Message-ID: <4FEC005C.8010801@middleswarth.net>

On 06/15/2012 06:23 AM, Dave Neary wrote:
> Hi,
>
> On 06/13/2012 04:28 PM, Dave Neary wrote:
>> So - how are you using oVirt? Why did you choose it over alternatives?
>> What do you like about it? and what would you like to see change,
>> whether that is in terms of technical, process, or marketing changes?
>> I'm here to help, but to do so I need your help first!
>
> Thank you to all those who have replied, on and off list, so far. For 
> those of you who sent me private messages, I'll be (anonymously) 
> collating your feedback and forwarding it on.
>
> The range of users who have replied so far includes:
> * Sysadmin at small web hosting business
> * Cost-sensitive IT department of an unrelated industry
That would be me.
> * Hosting provider specialising in HA
> * Running a private cloud
> * Test lab set-up considering for production deployment
Well no one should be crazy enough to go live with a product they 
haven't at least ran inside a testing lab.
>
> And the top features you've cited are:
> * Stateless hypervisor
> * Ability to migrate VMs
Number one reason I am working with oVirt
> * RHEL and KVM
We are a debian based org so changing over to the RHEL based OS's is 
more a pain then a benefit.  KVM is still kinda young compared to both 
Xen / Vmware it seems to work well but there aren't as many os's covered 
by the vitro drivers and there seem to be more bugs / race conditions 
but that has been steadily changing as it has been getting more mature
> * Cost
> * The ability to have your preferred OS as both hypervisor and guest 
> as a first class citizen
> * Aimed for data center use-case rather than cloud
This would be number 2 in the list.

> And the top gaps you've identified so far:
> * Insufficient resources (docs) to help with production deployment on 
> ovirt.org
> * Difficulty of configuration and getting started
> * You'd like to see a more diverse contributor community
> * Stability (unfortunately, I don't have any concrete examples of this 
> from the commenter)
> * History on resource usage in hypervisors and guests
> * Integration with Gluster
> * Offer choices of guest agents with other distributions than RHEL
>
I could have created this list myself.  I have hit pretty much every one 
of these limits in the last few months working with the project.  3.1 
adds limited support for Gluster and ovirt seems to be more stable 
dispute F17 instability.

As for the question of stability the file storage system in 3.0 can be a 
bit unstable.  If your NFS share disappears for a few mins  the file 
system tends to go offline and wont reactivate.  Not sure about iscsi or 
FC since I don't have access to those file systems.
> This is all giving me great insight into who's here - please keep it 
> coming!
>
> Cheers,
> Dave.
>




From iheim at redhat.com  Thu Jun 28 19:19:18 2012
From: iheim at redhat.com (Itamar Heim)
Date: Thu, 28 Jun 2012 15:19:18 -0400
Subject: storage domain recovery (was [Users] What are you looking for
	from oVirt?)
In-Reply-To: <4FEC005C.8010801@middleswarth.net>
References: <4FD8A370.3010904@redhat.com> <4FDB0D23.1050603@redhat.com>
	<4FEC005C.8010801@middleswarth.net>
Message-ID: <4FECAE36.4040008@redhat.com>

On 06/28/2012 02:57 AM, Robert Middleswarth wrote:
>
> As for the question of stability the file storage system in 3.0 can be a
> bit unstable.  If your NFS share disappears for a few mins  the file
> system tends to go offline and wont reactivate.  Not sure about iscsi or
> FC since I don't have access to those file systems.

3.1 adds distinction between a storage domain going down due to an error 
or admin maintaining it.
in case of an error, there is a new recovery mechanism in 3.1 which 
should improve this.

Itamar



From robert at middleswarth.net  Thu Jun 28 20:07:32 2012
From: robert at middleswarth.net (Robert Middleswarth)
Date: Thu, 28 Jun 2012 16:07:32 -0400
Subject: storage domain recovery (was [Users] What are you looking for
	from oVirt?)
In-Reply-To: <4FECAE36.4040008@redhat.com>
References: <4FD8A370.3010904@redhat.com> <4FDB0D23.1050603@redhat.com>
	<4FEC005C.8010801@middleswarth.net> <4FECAE36.4040008@redhat.com>
Message-ID: <4FECB984.6050807@middleswarth.net>

On 06/28/2012 03:19 PM, Itamar Heim wrote:
> On 06/28/2012 02:57 AM, Robert Middleswarth wrote:
>>
>> As for the question of stability the file storage system in 3.0 can be a
>> bit unstable.  If your NFS share disappears for a few mins  the file
>> system tends to go offline and wont reactivate.  Not sure about iscsi or
>> FC since I don't have access to those file systems.
>
> 3.1 adds distinction between a storage domain going down due to an 
> error or admin maintaining it.
> in case of an error, there is a new recovery mechanism in 3.1 which 
> should improve this.
>
> Itamar
>
Very glad to her that.

Thanks
Robert



From nathan at robotics.net  Fri Jun 29 15:15:58 2012
From: nathan at robotics.net (Nathan Stratton)
Date: Fri, 29 Jun 2012 10:15:58 -0500 (CDT)
Subject: [Users] What are you looking for from oVirt?
In-Reply-To: <CAAJBOyY5wvNUbWH=4iRAUHdp=PvfQy_edRzm9PvTqop-vAuazQ@mail.gmail.com>
References: <4FD8A370.3010904@redhat.com> <4FDB0D23.1050603@redhat.com>
	<4FEC005C.8010801@middleswarth.net>
	<CAAJBOyY5wvNUbWH=4iRAUHdp=PvfQy_edRzm9PvTqop-vAuazQ@mail.gmail.com>
Message-ID: <alpine.LFD.2.02.1206291005580.29635@bart.robotics.net>

On Fri, 29 Jun 2012, Romain Vrignaud wrote:

> Hello,
>
> I don't run currently any oVirt deployement in production but I have a lab.
> I used to run in production the old oVirt product (in rails).
>
> My best wishes for the future release of oVirt are :
> * GluserFS support as many of us

I must admit the first part of managing GlusterFS with 3.3 works very 
well out of the box on oVirt 3.1.

Turn on GlusterFS in the cluster
Add your nodes
Manually add the peers in Gluster
Edit /etc/nfsmount.conf and set Defaultproto=tcp and Defaultvers=3 
Create your gluster volume
Start the volume
Mount it in on one of your nodes in say /mnt
chown 36.36 /mnt

The only problem now is that you have to now use the volume as a NFS 
server.

> * Nova (OpenStack Hypervisor) driver support (
> http://docs.openstack.org/trunk/openstack-compute/admin/content/selecting-a-hypervisor.html
> ).
> I choose oVirt because my first goal is to manage a virtualized datacenter
> with OSS. But we begin to look at private cloud deployement.
> I think Aeolus would work with oVirt virtualization backend but AFAIK it
> only support redhat based linux which is not possible for us as we run
> almost only debian server except for virtualisation layer. So we would like
> to deploy OpenStack but to rely on oVirt for KVM hypervisors.

Been looking at openstack, but it still looks like a cobbled together mess 
trying to serve all people right now to me.

> * Fully supported stateless ovirt-node

I have a lab cluster running pxeboot read-only nfsroot with a lot of luck.


><>
Nathan Stratton
nathan at robotics.net
http://www.robotics.net


From iheim at redhat.com  Fri Jun 29 19:15:26 2012
From: iheim at redhat.com (Itamar Heim)
Date: Fri, 29 Jun 2012 22:15:26 +0300
Subject: [Users] What are you looking for from oVirt?
In-Reply-To: <alpine.LFD.2.02.1206291005580.29635@bart.robotics.net>
References: <4FD8A370.3010904@redhat.com> <4FDB0D23.1050603@redhat.com>
	<4FEC005C.8010801@middleswarth.net>
	<CAAJBOyY5wvNUbWH=4iRAUHdp=PvfQy_edRzm9PvTqop-vAuazQ@mail.gmail.com>
	<alpine.LFD.2.02.1206291005580.29635@bart.robotics.net>
Message-ID: <4FEDFECE.3020409@redhat.com>

On 06/29/2012 06:15 PM, Nathan Stratton wrote:
> I must admit the first part of managing GlusterFS with 3.3 works very
> well out of the box on oVirt 3.1.
>
> Turn on GlusterFS in the cluster
> Add your nodes
> Manually add the peers in Gluster
> Edit /etc/nfsmount.conf and set Defaultproto=tcp and Defaultvers=3
> Create your gluster volume
> Start the volume
> Mount it in on one of your nodes in say /mnt
> chown 36.36 /mnt
>
> The only problem now is that you have to now use the volume as a NFS
> server.

why not as posixfs?


From rvrignaud at gmail.com  Fri Jun 29 08:13:32 2012
From: rvrignaud at gmail.com (Romain Vrignaud)
Date: Fri, 29 Jun 2012 10:13:32 +0200
Subject: [Users] What are you looking for from oVirt?
In-Reply-To: <4FEC005C.8010801@middleswarth.net>
References: <4FD8A370.3010904@redhat.com> <4FDB0D23.1050603@redhat.com>
	<4FEC005C.8010801@middleswarth.net>
Message-ID: <CAAJBOyY5wvNUbWH=4iRAUHdp=PvfQy_edRzm9PvTqop-vAuazQ@mail.gmail.com>

Hello,

I don't run currently any oVirt deployement in production but I have a lab.
I used to run in production the old oVirt product (in rails).

My best wishes for the future release of oVirt are :
* GluserFS support as many of us
* Nova (OpenStack Hypervisor) driver support (
http://docs.openstack.org/trunk/openstack-compute/admin/content/selecting-a-hypervisor.html
).
I choose oVirt because my first goal is to manage a virtualized datacenter
with OSS. But we begin to look at private cloud deployement.
I think Aeolus would work with oVirt virtualization backend but AFAIK it
only support redhat based linux which is not possible for us as we run
almost only debian server except for virtualisation layer. So we would like
to deploy OpenStack but to rely on oVirt for KVM hypervisors.
* Fully supported stateless ovirt-node

Regards,

Romain

2012/6/28 Robert Middleswarth <robert at middleswarth.net>

> On 06/15/2012 06:23 AM, Dave Neary wrote:
>
>> Hi,
>>
>> On 06/13/2012 04:28 PM, Dave Neary wrote:
>>
>>> So - how are you using oVirt? Why did you choose it over alternatives?
>>> What do you like about it? and what would you like to see change,
>>> whether that is in terms of technical, process, or marketing changes?
>>> I'm here to help, but to do so I need your help first!
>>>
>>
>> Thank you to all those who have replied, on and off list, so far. For
>> those of you who sent me private messages, I'll be (anonymously) collating
>> your feedback and forwarding it on.
>>
>> The range of users who have replied so far includes:
>> * Sysadmin at small web hosting business
>> * Cost-sensitive IT department of an unrelated industry
>>
> That would be me.
>
>  * Hosting provider specialising in HA
>> * Running a private cloud
>> * Test lab set-up considering for production deployment
>>
> Well no one should be crazy enough to go live with a product they haven't
> at least ran inside a testing lab.
>
>
>> And the top features you've cited are:
>> * Stateless hypervisor
>> * Ability to migrate VMs
>>
> Number one reason I am working with oVirt
>
>> * RHEL and KVM
>>
> We are a debian based org so changing over to the RHEL based OS's is more
> a pain then a benefit.  KVM is still kinda young compared to both Xen /
> Vmware it seems to work well but there aren't as many os's covered by the
> vitro drivers and there seem to be more bugs / race conditions but that has
> been steadily changing as it has been getting more mature
>
>  * Cost
>> * The ability to have your preferred OS as both hypervisor and guest as a
>> first class citizen
>> * Aimed for data center use-case rather than cloud
>>
> This would be number 2 in the list.
>
>
>  And the top gaps you've identified so far:
>> * Insufficient resources (docs) to help with production deployment on
>> ovirt.org
>> * Difficulty of configuration and getting started
>> * You'd like to see a more diverse contributor community
>> * Stability (unfortunately, I don't have any concrete examples of this
>> from the commenter)
>> * History on resource usage in hypervisors and guests
>> * Integration with Gluster
>> * Offer choices of guest agents with other distributions than RHEL
>>
>>  I could have created this list myself.  I have hit pretty much every one
> of these limits in the last few months working with the project.  3.1 adds
> limited support for Gluster and ovirt seems to be more stable dispute F17
> instability.
>
> As for the question of stability the file storage system in 3.0 can be a
> bit unstable.  If your NFS share disappears for a few mins  the file system
> tends to go offline and wont reactivate.  Not sure about iscsi or FC since
> I don't have access to those file systems.
>
>  This is all giving me great insight into who's here - please keep it
>> coming!
>>
>> Cheers,
>> Dave.
>>
>>
>
> ______________________________**_________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/**mailman/listinfo/users<http://lists.ovirt.org/mailman/listinfo/users>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120629/4ac5b108/attachment.html>