From kwade at redhat.com Thu Oct 4 16:32:02 2012 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Thu, 04 Oct 2012 09:32:02 -0700 Subject: Planned outage :: MediaWiki update for migration :: 2012-10-04 2200 UTC Message-ID: <506DBA02.6080209@redhat.com> We are upgrading our MediaWiki instance this evening. We may need to reboot the server if there are other updates that require it. To convert UTC to your local time, run: date -d '2012-10-04 22:00 UTC' == Affected services == wiki.ovirt.org == Unaffected services == These services are unaffected unless a reboot is required: www.ovirt.org (MediaWiki) lists.ovirt.org (Mailman) ovirt.org/releases These services are unaffected regardless of a reboot: gerrit.ovirt.org jenkins.ovirt.org Please join #ovirt on irc.oftc.net or respond to this email to track the status of this outage. == Reason for outage == I am upgrading our MediaWiki instance in preparation to migrating the service to use the new theme and run on OpenShift. Previously we discussed if this pre-migration was necessary, and since then we've found a MediaWiki page stating that an update to the target version is needed before moving to a new server. http://www.mediawiki.org/wiki/Manual:Moving_a_wiki#Versions_and_upgrading To do the update, I'll probably put the wiki in read-only mode for a short time. I'll announce this on IRC (irc.oftc.net #ovirt) a few minutes in advance. At the same time, I'll look to make sure other packages are updated. If there is anything risky, I'll hold off on an update. If a reboot is required, I will reboot during that time. If a reboot is required, I will send out a warning a few minutes in advance on IRC. I'll generally keep the channel updated during the maintenance window. - Karsten -- Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From dneary at redhat.com Tue Oct 9 18:09:22 2012 From: dneary at redhat.com (Dave Neary) Date: Tue, 09 Oct 2012 20:09:22 +0200 Subject: Is anyone proposing a main track FOSDEM talk? Message-ID: <50746852.5030907@redhat.com> Hi all, TL;DR The FOSDEM call for main track proposals closes soon, and I would like to see one or two oVirt proposals submitted. FOSDEM has a great crowd - very techie, very free software friendly, and very interested in new stuff. They have a main auditorium that holds 1000 people and they fill it for talks like "Tales from the Trenches of Kernel Development", "FreePlug - a Linux server in a Plug", "Amateur rocketry"... They also have a dazzling array of DevRooms, rooms with a capacity ranging from 30 people up to 300 or 400, on topics like embedded Linux platforms, the Free Desktop, legal topics in free software, telephony, etc. This year, I believe that Itamar proposed a Virtualisation DevRoom, and I hope that it gets accepted (notifications should be going out soon). DevRooms all organise their content independently - when they are announced, I'll let people know so that we can get some good submissions in for aligned topics, and if we're running a virt DevRoom, of course I'll help spread the word for that. But I would really like to see us run one or two introduction-level presentations on oVirt and virtualisation, aimed at this audience (that is, an audience of people who all own several computers!). Someone who can outline, in 45 minutes, the problems that oVirt solves, the basics of how it works, the community around the project... Who do we have who would be willing and able to give such a presentation? The deadline for main track submissions is November 1st: https://fosdem.org/2013/call_for_main_speakers.html Thanks! Dave. -- Dave Neary Community Action and Impact Open Source and Standards, Red Hat Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 From kanagaraj.rk at gmail.com Wed Oct 10 15:46:44 2012 From: kanagaraj.rk at gmail.com (R.Kanagaraj (RK)) Date: Wed, 10 Oct 2012 21:16:44 +0530 Subject: Is anyone proposing a main track FOSDEM talk? In-Reply-To: <50746852.5030907@redhat.com> References: <50746852.5030907@redhat.com> Message-ID: Hi Dave, I would like to give a presentation on Introduction to Virtualization and the role of oVirt in Virtualization. Please let me know whether it will meet the expectation of FOSDEM or not. On Tue, Oct 9, 2012 at 11:39 PM, Dave Neary wrote: > Hi all, > > TL;DR The FOSDEM call for main track proposals closes soon, and I would > like to see one or two oVirt proposals submitted. > > FOSDEM has a great crowd - very techie, very free software friendly, and > very interested in new stuff. They have a main auditorium that holds 1000 > people and they fill it for talks like "Tales from the Trenches of Kernel > Development", "FreePlug - a Linux server in a Plug", "Amateur rocketry"... > > They also have a dazzling array of DevRooms, rooms with a capacity ranging > from 30 people up to 300 or 400, on topics like embedded Linux platforms, > the Free Desktop, legal topics in free software, telephony, etc. This year, > I believe that Itamar proposed a Virtualisation DevRoom, and I hope that it > gets accepted (notifications should be going out soon). > > DevRooms all organise their content independently - when they are > announced, I'll let people know so that we can get some good submissions in > for aligned topics, and if we're running a virt DevRoom, of course I'll > help spread the word for that. > > But I would really like to see us run one or two introduction-level > presentations on oVirt and virtualisation, aimed at this audience (that is, > an audience of people who all own several computers!). Someone who can > outline, in 45 minutes, the problems that oVirt solves, the basics of how > it works, the community around the project... > > Who do we have who would be willing and able to give such a presentation? > The deadline for main track submissions is November 1st: > https://fosdem.org/2013/call_**for_main_speakers.html > > Thanks! > Dave. > > -- > Dave Neary > Community Action and Impact > Open Source and Standards, Red Hat > Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 > ______________________________**_________________ > Arch mailing list > Arch at ovirt.org > http://lists.ovirt.org/**mailman/listinfo/arch > -- With Regards, RK, +91 9840483044 -------------- next part -------------- An HTML attachment was scrubbed... URL: From eedri at redhat.com Wed Oct 10 16:02:09 2012 From: eedri at redhat.com (Eyal Edri) Date: Wed, 10 Oct 2012 12:02:09 -0400 (EDT) Subject: Is anyone proposing a main track FOSDEM talk? In-Reply-To: <50746852.5030907@redhat.com> Message-ID: <790883914.10088825.1349884929250.JavaMail.root@redhat.com> I'm waiting to see if there will be a room for jenkins/automation tests. if it will approved, i'd would like to give a lecture about the challenge of testing a Virtualization project like oVirt. and how it can be done using oVirt, jenkins, foreman and puppet. probably a similar or a follow up on my last lecture on Jenkins user conf [1] [1] http://www.slideshare.net/eyale30/the-challenge-testing-the-ovirt-project ----- Original Message ----- > From: "Dave Neary" > To: "oVirt Arch" > Sent: Tuesday, October 9, 2012 8:09:22 PM > Subject: Is anyone proposing a main track FOSDEM talk? > > Hi all, > > TL;DR The FOSDEM call for main track proposals closes soon, and I > would > like to see one or two oVirt proposals submitted. > > FOSDEM has a great crowd - very techie, very free software friendly, > and > very interested in new stuff. They have a main auditorium that holds > 1000 people and they fill it for talks like "Tales from the Trenches > of > Kernel Development", "FreePlug - a Linux server in a Plug", "Amateur > rocketry"... > > They also have a dazzling array of DevRooms, rooms with a capacity > ranging from 30 people up to 300 or 400, on topics like embedded > Linux > platforms, the Free Desktop, legal topics in free software, > telephony, > etc. This year, I believe that Itamar proposed a Virtualisation > DevRoom, > and I hope that it gets accepted (notifications should be going out > soon). > > DevRooms all organise their content independently - when they are > announced, I'll let people know so that we can get some good > submissions > in for aligned topics, and if we're running a virt DevRoom, of course > I'll help spread the word for that. > > But I would really like to see us run one or two introduction-level > presentations on oVirt and virtualisation, aimed at this audience > (that > is, an audience of people who all own several computers!). Someone > who > can outline, in 45 minutes, the problems that oVirt solves, the > basics > of how it works, the community around the project... > > Who do we have who would be willing and able to give such a > presentation? The deadline for main track submissions is November > 1st: > https://fosdem.org/2013/call_for_main_speakers.html > > Thanks! > Dave. > > -- > Dave Neary > Community Action and Impact > Open Source and Standards, Red Hat > Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 > _______________________________________________ > Arch mailing list > Arch at ovirt.org > http://lists.ovirt.org/mailman/listinfo/arch > From dneary at redhat.com Wed Oct 10 16:15:23 2012 From: dneary at redhat.com (Dave Neary) Date: Wed, 10 Oct 2012 18:15:23 +0200 Subject: Is anyone proposing a main track FOSDEM talk? In-Reply-To: References: <50746852.5030907@redhat.com> Message-ID: <50759F1B.4060103@redhat.com> Hi RK, For the main track, presentations are usually either "sexy" or are given by people who are well known. I think that the presentation you propose would not meet the standard. What could you change to "sexy" it up? Cheers, Dave. On 10/10/2012 05:46 PM, R.Kanagaraj (RK) wrote: > Hi Dave, > > I would like to give a presentation on Introduction to Virtualization > and the role of oVirt in Virtualization. Please let me know whether it > will meet the expectation of FOSDEM or not. > > On Tue, Oct 9, 2012 at 11:39 PM, Dave Neary > wrote: > > Hi all, > > TL;DR The FOSDEM call for main track proposals closes soon, and I > would like to see one or two oVirt proposals submitted. > > FOSDEM has a great crowd - very techie, very free software friendly, > and very interested in new stuff. They have a main auditorium that > holds 1000 people and they fill it for talks like "Tales from the > Trenches of Kernel Development", "FreePlug - a Linux server in a > Plug", "Amateur rocketry"... > > They also have a dazzling array of DevRooms, rooms with a capacity > ranging from 30 people up to 300 or 400, on topics like embedded > Linux platforms, the Free Desktop, legal topics in free software, > telephony, etc. This year, I believe that Itamar proposed a > Virtualisation DevRoom, and I hope that it gets accepted > (notifications should be going out soon). > > DevRooms all organise their content independently - when they are > announced, I'll let people know so that we can get some good > submissions in for aligned topics, and if we're running a virt > DevRoom, of course I'll help spread the word for that. > > But I would really like to see us run one or two introduction-level > presentations on oVirt and virtualisation, aimed at this audience > (that is, an audience of people who all own several computers!). > Someone who can outline, in 45 minutes, the problems that oVirt > solves, the basics of how it works, the community around the project... > > Who do we have who would be willing and able to give such a > presentation? The deadline for main track submissions is November > 1st: https://fosdem.org/2013/call___for_main_speakers.html > > > Thanks! > Dave. > > -- > Dave Neary > Community Action and Impact > Open Source and Standards, Red Hat > Ph: +33 9 50 71 55 62 / Cell: > +33 6 77 01 92 13 > _________________________________________________ > Arch mailing list > Arch at ovirt.org > http://lists.ovirt.org/__mailman/listinfo/arch > > > > > > -- > > With Regards, > RK, > +91 9840483044 > -- Dave Neary Community Action and Impact Open Source and Standards, Red Hat Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 From mburns at redhat.com Mon Oct 15 02:12:11 2012 From: mburns at redhat.com (Mike Burns) Date: Sun, 14 Oct 2012 22:12:11 -0400 Subject: Feature pages for 3.2 Message-ID: <1350267131.6975.15.camel@beelzebub.mburnsfire.net> The 3.2 Release page[1] has a list of features targeted for 3.2. The majority of the listed features either lack a feature page completely, or a link is missing. If you are responsible for the component the includes the feature, can you either create or have someone create a feature page? A template page is available[2]. Thanks Mike [1] http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features [2] http://wiki.ovirt.org/wiki/Feature_template From dneary at redhat.com Mon Oct 15 14:18:57 2012 From: dneary at redhat.com (Dave Neary) Date: Mon, 15 Oct 2012 16:18:57 +0200 Subject: Feature pages for 3.2 In-Reply-To: <1350267131.6975.15.camel@beelzebub.mburnsfire.net> References: <1350267131.6975.15.camel@beelzebub.mburnsfire.net> Message-ID: <507C1B51.10208@redhat.com> Hi, On 10/15/2012 04:12 AM, Mike Burns wrote: > The 3.2 Release page[1] has a list of features targeted for 3.2. The > majority of the listed features either lack a feature page completely, > or a link is missing. If you are responsible for the component the > includes the feature, can you either create or have someone create a > feature page? A template page is available[2]. > [1] http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features > [2] http://wiki.ovirt.org/wiki/Feature_template I just wanted to add that since this is a feature list I created based on the contents of an IRC meeting log, it's entirely possible that there are features ready for 3.2 which are not included in this list. If you're working on oVirt and have developed features recently, please check the page and ensure that it is listed there. And link to the corresponding feature page while you're at it, please! Thanks, Dave. -- Dave Neary Community Action and Impact Open Source and Standards, Red Hat Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 From lpeer at redhat.com Mon Oct 15 14:43:33 2012 From: lpeer at redhat.com (Livnat Peer) Date: Mon, 15 Oct 2012 16:43:33 +0200 Subject: Feature pages for 3.2 In-Reply-To: <1350267131.6975.15.camel@beelzebub.mburnsfire.net> References: <1350267131.6975.15.camel@beelzebub.mburnsfire.net> Message-ID: <507C2115.7050603@redhat.com> On 15/10/12 04:12, Mike Burns wrote: > The 3.2 Release page[1] has a list of features targeted for 3.2. The > majority of the listed features either lack a feature page completely, > or a link is missing. If you are responsible for the component the > includes the feature, can you either create or have someone create a > feature page? A template page is available[2]. > > Thanks > > Mike > > [1] http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features > [2] http://wiki.ovirt.org/wiki/Feature_template > All the network related features are covered. My only concern is that "Make network a main tab" won't make it on time to 3.2. If there is no objection I'll remove it from the list and if we'll be able to push it I'll add it again. Thanks, Livnat From dfediuck at redhat.com Mon Oct 15 15:54:38 2012 From: dfediuck at redhat.com (Doron Fediuck) Date: Mon, 15 Oct 2012 11:54:38 -0400 (EDT) Subject: Feature pages for 3.2 In-Reply-To: <507C1B51.10208@redhat.com> Message-ID: <304284832.12461053.1350316478851.JavaMail.root@redhat.com> ----- Original Message ----- > From: "Dave Neary" > To: "Mike Burns" > Cc: "Itamar Heim" , "Dan Kenigsberg" , "Ayal Baron" , "Livnat > Peer" , "Doron Fediuck" , "arch" > Sent: Monday, October 15, 2012 4:18:57 PM > Subject: Re: Feature pages for 3.2 > > Hi, > > On 10/15/2012 04:12 AM, Mike Burns wrote: > > The 3.2 Release page[1] has a list of features targeted for 3.2. > > The > > majority of the listed features either lack a feature page > > completely, > > or a link is missing. If you are responsible for the component the > > includes the feature, can you either create or have someone create > > a > > feature page? A template page is available[2]. > > [1] > > http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features > > [2] http://wiki.ovirt.org/wiki/Feature_template > > I just wanted to add that since this is a feature list I created > based > on the contents of an IRC meeting log, it's entirely possible that > there > are features ready for 3.2 which are not included in this list. If > you're working on oVirt and have developed features recently, please > check the page and ensure that it is listed there. And link to the > corresponding feature page while you're at it, please! > > Thanks, > Dave. > > -- > Dave Neary > Community Action and Impact > Open Source and Standards, Red Hat > Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 > Thanks. Created and updated the links to the MoM and Quota-3.2 pages. From ofrenkel at redhat.com Tue Oct 16 14:13:25 2012 From: ofrenkel at redhat.com (Omer Frenkel) Date: Tue, 16 Oct 2012 10:13:25 -0400 (EDT) Subject: Feature pages for 3.2 In-Reply-To: <507C2115.7050603@redhat.com> Message-ID: <1830068083.13015921.1350396805278.JavaMail.root@redhat.com> ----- Original Message ----- > From: "Livnat Peer" > To: "Mike Burns" > Cc: "arch" > Sent: Monday, October 15, 2012 4:43:33 PM > Subject: Re: Feature pages for 3.2 > > On 15/10/12 04:12, Mike Burns wrote: > > The 3.2 Release page[1] has a list of features targeted for 3.2. > > The > > majority of the listed features either lack a feature page > > completely, > > or a link is missing. If you are responsible for the component the > > includes the feature, can you either create or have someone create > > a > > feature page? A template page is available[2]. > > > > Thanks > > > > Mike > > > > [1] > > http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features > > [2] http://wiki.ovirt.org/wiki/Feature_template > > > > All the network related features are covered. > My only concern is that "Make network a main tab" won't make it on > time > to 3.2. > If there is no objection I'll remove it from the list and if we'll be > able to push it I'll add it again. > maybe just mark it as "nice-to-have" and not "must-have" (somehow)? so it is still documented it's planned and there is some work on it, and it's targeted to 3.2 with the possibility it would not be in. > Thanks, Livnat > _______________________________________________ > Arch mailing list > Arch at ovirt.org > http://lists.ovirt.org/mailman/listinfo/arch > From mburns at redhat.com Tue Oct 16 14:20:53 2012 From: mburns at redhat.com (Mike Burns) Date: Tue, 16 Oct 2012 10:20:53 -0400 Subject: Feature pages for 3.2 In-Reply-To: <1830068083.13015921.1350396805278.JavaMail.root@redhat.com> References: <1830068083.13015921.1350396805278.JavaMail.root@redhat.com> Message-ID: <1350397253.4491.23.camel@beelzebub.mburnsfire.net> On Tue, 2012-10-16 at 10:13 -0400, Omer Frenkel wrote: > > ----- Original Message ----- > > From: "Livnat Peer" > > To: "Mike Burns" > > Cc: "arch" > > Sent: Monday, October 15, 2012 4:43:33 PM > > Subject: Re: Feature pages for 3.2 > > > > On 15/10/12 04:12, Mike Burns wrote: > > > The 3.2 Release page[1] has a list of features targeted for 3.2. > > > The > > > majority of the listed features either lack a feature page > > > completely, > > > or a link is missing. If you are responsible for the component the > > > includes the feature, can you either create or have someone create > > > a > > > feature page? A template page is available[2]. > > > > > > Thanks > > > > > > Mike > > > > > > [1] > > > http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features > > > [2] http://wiki.ovirt.org/wiki/Feature_template > > > > > > > All the network related features are covered. > > My only concern is that "Make network a main tab" won't make it on > > time > > to 3.2. > > If there is no objection I'll remove it from the list and if we'll be > > able to push it I'll add it again. > > > > maybe just mark it as "nice-to-have" and not "must-have" (somehow)? > so it is still documented it's planned and there is some work on it, > and it's targeted to 3.2 with the possibility it would not be in. > I agree, we should keep it on the list. You can mark the status on the Feature page as a stretch or reach for 3.2. We should only drop it if we're sure that we're not going to be able to make it for 3.2 Mike > > Thanks, Livnat > > _______________________________________________ > > Arch mailing list > > Arch at ovirt.org > > http://lists.ovirt.org/mailman/listinfo/arch > > From lpeer at redhat.com Tue Oct 16 14:32:51 2012 From: lpeer at redhat.com (Livnat Peer) Date: Tue, 16 Oct 2012 16:32:51 +0200 Subject: Feature pages for 3.2 In-Reply-To: <1350397253.4491.23.camel@beelzebub.mburnsfire.net> References: <1830068083.13015921.1350396805278.JavaMail.root@redhat.com> <1350397253.4491.23.camel@beelzebub.mburnsfire.net> Message-ID: <507D7013.9080907@redhat.com> On 16/10/12 16:20, Mike Burns wrote: > On Tue, 2012-10-16 at 10:13 -0400, Omer Frenkel wrote: >> >> ----- Original Message ----- >>> From: "Livnat Peer" >>> To: "Mike Burns" >>> Cc: "arch" >>> Sent: Monday, October 15, 2012 4:43:33 PM >>> Subject: Re: Feature pages for 3.2 >>> >>> On 15/10/12 04:12, Mike Burns wrote: >>>> The 3.2 Release page[1] has a list of features targeted for 3.2. >>>> The >>>> majority of the listed features either lack a feature page >>>> completely, >>>> or a link is missing. If you are responsible for the component the >>>> includes the feature, can you either create or have someone create >>>> a >>>> feature page? A template page is available[2]. >>>> >>>> Thanks >>>> >>>> Mike >>>> >>>> [1] >>>> http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features >>>> [2] http://wiki.ovirt.org/wiki/Feature_template >>>> >>> >>> All the network related features are covered. >>> My only concern is that "Make network a main tab" won't make it on >>> time >>> to 3.2. >>> If there is no objection I'll remove it from the list and if we'll be >>> able to push it I'll add it again. >>> >> >> maybe just mark it as "nice-to-have" and not "must-have" (somehow)? >> so it is still documented it's planned and there is some work on it, >> and it's targeted to 3.2 with the possibility it would not be in. >> > > I agree, we should keep it on the list. You can mark the status on the > Feature page as a stretch or reach for 3.2. We should only drop it if > we're sure that we're not going to be able to make it for 3.2 > > Mike > Agree, updated the wiki. >>> Thanks, Livnat >>> _______________________________________________ >>> Arch mailing list >>> Arch at ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/arch >>> > > From iheim at redhat.com Wed Oct 17 12:58:25 2012 From: iheim at redhat.com (Itamar Heim) Date: Wed, 17 Oct 2012 14:58:25 +0200 Subject: Feature pages for 3.2 In-Reply-To: <1350267131.6975.15.camel@beelzebub.mburnsfire.net> References: <1350267131.6975.15.camel@beelzebub.mburnsfire.net> Message-ID: <507EAB71.1080109@redhat.com> On 10/15/2012 04:12 AM, Mike Burns wrote: > The 3.2 Release page[1] has a list of features targeted for 3.2. The > majority of the listed features either lack a feature page completely, > or a link is missing. If you are responsible for the component the > includes the feature, can you either create or have someone create a > feature page? A template page is available[2]. > > Thanks > > Mike > > [1] http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features > [2] http://wiki.ovirt.org/wiki/Feature_template > Adam, i see 'libvdsm preview' appears on the list. is this based on the current legacy api prototype or the new planned api? Thanks, Itamar From agl at us.ibm.com Wed Oct 17 14:41:36 2012 From: agl at us.ibm.com (Adam Litke) Date: Wed, 17 Oct 2012 09:41:36 -0500 Subject: Feature pages for 3.2 In-Reply-To: <507EAB71.1080109@redhat.com> References: <1350267131.6975.15.camel@beelzebub.mburnsfire.net> <507EAB71.1080109@redhat.com> Message-ID: <20121017144136.GG3672@aglitke> On Wed, Oct 17, 2012 at 02:58:25PM +0200, Itamar Heim wrote: > On 10/15/2012 04:12 AM, Mike Burns wrote: > >The 3.2 Release page[1] has a list of features targeted for 3.2. The > >majority of the listed features either lack a feature page completely, > >or a link is missing. If you are responsible for the component the > >includes the feature, can you either create or have someone create a > >feature page? A template page is available[2]. > > > >Thanks > > > >Mike > > > >[1] http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features > >[2] http://wiki.ovirt.org/wiki/Feature_template > > > > Adam, > > i see 'libvdsm preview' appears on the list. > is this based on the current legacy api prototype or the new planned api? I am not sure what you mean by "current legacy api prototype". I am working on a new JsonRPC based API that is driven by a schema. libvdsm is client-side C library with Python bindings that talks to vdsm using the the JsonRPC protocol according to the API schema. We do not currently have the Java client generated and that is still out of scope for 3.2 since no one is actively working on it. Hopefully this is enough information but if not please let me know. -- Adam Litke IBM Linux Technology Center From iheim at redhat.com Wed Oct 17 16:55:28 2012 From: iheim at redhat.com (Itamar Heim) Date: Wed, 17 Oct 2012 18:55:28 +0200 Subject: Feature pages for 3.2 In-Reply-To: <20121017144136.GG3672@aglitke> References: <1350267131.6975.15.camel@beelzebub.mburnsfire.net> <507EAB71.1080109@redhat.com> <20121017144136.GG3672@aglitke> Message-ID: <507EE300.4070505@redhat.com> On 10/17/2012 04:41 PM, Adam Litke wrote: > On Wed, Oct 17, 2012 at 02:58:25PM +0200, Itamar Heim wrote: >> On 10/15/2012 04:12 AM, Mike Burns wrote: >>> The 3.2 Release page[1] has a list of features targeted for 3.2. The >>> majority of the listed features either lack a feature page completely, >>> or a link is missing. If you are responsible for the component the >>> includes the feature, can you either create or have someone create a >>> feature page? A template page is available[2]. >>> >>> Thanks >>> >>> Mike >>> >>> [1] http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features >>> [2] http://wiki.ovirt.org/wiki/Feature_template >>> >> >> Adam, >> >> i see 'libvdsm preview' appears on the list. >> is this based on the current legacy api prototype or the new planned api? > > I am not sure what you mean by "current legacy api prototype". I am working on > a new JsonRPC based API that is driven by a schema. libvdsm is client-side C > library with Python bindings that talks to vdsm using the the JsonRPC protocol > according to the API schema. We do not currently have the Java client generated > and that is still out of scope for 3.2 since no one is actively working on it. > > Hopefully this is enough information but if not please let me know. > for some reason i though there was a phase which used a schema closer to the old xmlrpc api. my main concern with libvdsm is when it makes 'stable' api. i assume it closely tied to the jsonrpc based api/schema. so the question is when do we declare it as supported/stable/etc? From agl at us.ibm.com Wed Oct 17 17:27:40 2012 From: agl at us.ibm.com (Adam Litke) Date: Wed, 17 Oct 2012 12:27:40 -0500 Subject: Feature pages for 3.2 In-Reply-To: <507EE300.4070505@redhat.com> References: <1350267131.6975.15.camel@beelzebub.mburnsfire.net> <507EAB71.1080109@redhat.com> <20121017144136.GG3672@aglitke> <507EE300.4070505@redhat.com> Message-ID: <20121017172740.GK3672@aglitke> On Wed, Oct 17, 2012 at 06:55:28PM +0200, Itamar Heim wrote: > On 10/17/2012 04:41 PM, Adam Litke wrote: > >On Wed, Oct 17, 2012 at 02:58:25PM +0200, Itamar Heim wrote: > >>On 10/15/2012 04:12 AM, Mike Burns wrote: > >>>The 3.2 Release page[1] has a list of features targeted for 3.2. The > >>>majority of the listed features either lack a feature page completely, > >>>or a link is missing. If you are responsible for the component the > >>>includes the feature, can you either create or have someone create a > >>>feature page? A template page is available[2]. > >>> > >>>Thanks > >>> > >>>Mike > >>> > >>>[1] http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features > >>>[2] http://wiki.ovirt.org/wiki/Feature_template > >>> > >> > >>Adam, > >> > >>i see 'libvdsm preview' appears on the list. > >>is this based on the current legacy api prototype or the new planned api? > > > >I am not sure what you mean by "current legacy api prototype". I am working on > >a new JsonRPC based API that is driven by a schema. libvdsm is client-side C > >library with Python bindings that talks to vdsm using the the JsonRPC protocol > >according to the API schema. We do not currently have the Java client generated > >and that is still out of scope for 3.2 since no one is actively working on it. > > > >Hopefully this is enough information but if not please let me know. > > > > for some reason i though there was a phase which used a schema closer to the > old xmlrpc api. my main concern with libvdsm is when it makes 'stable' api. > i assume it closely tied to the jsonrpc based api/schema. so the question is > when do we declare it as supported/stable/etc? Well, the schema is currently very close to the xmlrpc API with some things fixed.. We decided that in order for this to become the new supported API eventually, it must start out working very similar to the old API. This will allow ovirt-engine to migrate to the new API without a complete rewrite. By preview, I am thinking we will deliver the API as something for people to try out but not make any API stability guarantees yet. I think we will be able to declare it stable once engine starts using it. My hope is we can move in that direction after the 3.2 release but it will take a concerted effort to get it done. -- Adam Litke IBM Linux Technology Center From iheim at redhat.com Wed Oct 17 17:44:10 2012 From: iheim at redhat.com (Itamar Heim) Date: Wed, 17 Oct 2012 19:44:10 +0200 Subject: Feature pages for 3.2 In-Reply-To: <20121017172740.GK3672@aglitke> References: <1350267131.6975.15.camel@beelzebub.mburnsfire.net> <507EAB71.1080109@redhat.com> <20121017144136.GG3672@aglitke> <507EE300.4070505@redhat.com> <20121017172740.GK3672@aglitke> Message-ID: <507EEE6A.6050807@redhat.com> On 10/17/2012 07:27 PM, Adam Litke wrote: > On Wed, Oct 17, 2012 at 06:55:28PM +0200, Itamar Heim wrote: >> On 10/17/2012 04:41 PM, Adam Litke wrote: >>> On Wed, Oct 17, 2012 at 02:58:25PM +0200, Itamar Heim wrote: >>>> On 10/15/2012 04:12 AM, Mike Burns wrote: >>>>> The 3.2 Release page[1] has a list of features targeted for 3.2. The >>>>> majority of the listed features either lack a feature page completely, >>>>> or a link is missing. If you are responsible for the component the >>>>> includes the feature, can you either create or have someone create a >>>>> feature page? A template page is available[2]. >>>>> >>>>> Thanks >>>>> >>>>> Mike >>>>> >>>>> [1] http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features >>>>> [2] http://wiki.ovirt.org/wiki/Feature_template >>>>> >>>> >>>> Adam, >>>> >>>> i see 'libvdsm preview' appears on the list. >>>> is this based on the current legacy api prototype or the new planned api? >>> >>> I am not sure what you mean by "current legacy api prototype". I am working on >>> a new JsonRPC based API that is driven by a schema. libvdsm is client-side C >>> library with Python bindings that talks to vdsm using the the JsonRPC protocol >>> according to the API schema. We do not currently have the Java client generated >>> and that is still out of scope for 3.2 since no one is actively working on it. >>> >>> Hopefully this is enough information but if not please let me know. >>> >> >> for some reason i though there was a phase which used a schema closer to the >> old xmlrpc api. my main concern with libvdsm is when it makes 'stable' api. >> i assume it closely tied to the jsonrpc based api/schema. so the question is >> when do we declare it as supported/stable/etc? > > Well, the schema is currently very close to the xmlrpc API with some things > fixed.. We decided that in order for this to become the new supported API > eventually, it must start out working very similar to the old API. This will > allow ovirt-engine to migrate to the new API without a complete rewrite. > > By preview, I am thinking we will deliver the API as something for people to try > out but not make any API stability guarantees yet. I think we will be able to > declare it stable once engine starts using it. My hope is we can move in that > direction after the 3.2 release but it will take a concerted effort to get it > done. > wouldn't we want two phases before declaring it stable? 1. move the engine to it. 2. refactor api to be cleaner than just resembling the xml/rpc one (iiuc, the planned api would be much lean/mean than the xml/rpc one?) thanks, Itamar From agl at us.ibm.com Wed Oct 17 18:27:47 2012 From: agl at us.ibm.com (Adam Litke) Date: Wed, 17 Oct 2012 13:27:47 -0500 Subject: Feature pages for 3.2 In-Reply-To: <507EEE6A.6050807@redhat.com> References: <1350267131.6975.15.camel@beelzebub.mburnsfire.net> <507EAB71.1080109@redhat.com> <20121017144136.GG3672@aglitke> <507EE300.4070505@redhat.com> <20121017172740.GK3672@aglitke> <507EEE6A.6050807@redhat.com> Message-ID: <20121017182747.GL3672@aglitke> On Wed, Oct 17, 2012 at 07:44:10PM +0200, Itamar Heim wrote: > On 10/17/2012 07:27 PM, Adam Litke wrote: > >On Wed, Oct 17, 2012 at 06:55:28PM +0200, Itamar Heim wrote: > >>On 10/17/2012 04:41 PM, Adam Litke wrote: > >>>On Wed, Oct 17, 2012 at 02:58:25PM +0200, Itamar Heim wrote: > >>>>On 10/15/2012 04:12 AM, Mike Burns wrote: > >>>>>The 3.2 Release page[1] has a list of features targeted for 3.2. The > >>>>>majority of the listed features either lack a feature page completely, > >>>>>or a link is missing. If you are responsible for the component the > >>>>>includes the feature, can you either create or have someone create a > >>>>>feature page? A template page is available[2]. > >>>>> > >>>>>Thanks > >>>>> > >>>>>Mike > >>>>> > >>>>>[1] http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features > >>>>>[2] http://wiki.ovirt.org/wiki/Feature_template > >>>>> > >>>> > >>>>Adam, > >>>> > >>>>i see 'libvdsm preview' appears on the list. > >>>>is this based on the current legacy api prototype or the new planned api? > >>> > >>>I am not sure what you mean by "current legacy api prototype". I am working on > >>>a new JsonRPC based API that is driven by a schema. libvdsm is client-side C > >>>library with Python bindings that talks to vdsm using the the JsonRPC protocol > >>>according to the API schema. We do not currently have the Java client generated > >>>and that is still out of scope for 3.2 since no one is actively working on it. > >>> > >>>Hopefully this is enough information but if not please let me know. > >>> > >> > >>for some reason i though there was a phase which used a schema closer to the > >>old xmlrpc api. my main concern with libvdsm is when it makes 'stable' api. > >>i assume it closely tied to the jsonrpc based api/schema. so the question is > >>when do we declare it as supported/stable/etc? > > > >Well, the schema is currently very close to the xmlrpc API with some things > >fixed.. We decided that in order for this to become the new supported API > >eventually, it must start out working very similar to the old API. This will > >allow ovirt-engine to migrate to the new API without a complete rewrite. > > > >By preview, I am thinking we will deliver the API as something for people to try > >out but not make any API stability guarantees yet. I think we will be able to > >declare it stable once engine starts using it. My hope is we can move in that > >direction after the 3.2 release but it will take a concerted effort to get it > >done. > > > > wouldn't we want two phases before declaring it stable? > 1. move the engine to it. > 2. refactor api to be cleaner than just resembling the xml/rpc one > (iiuc, the planned api would be much lean/mean than the xml/rpc one?) Yes, I would definitely be okay with cleaning it up. As a first pass we could remove all currently deprecated APIs, remove unneeded parameters, make parameters optional when possible, etc. I believe HSM is getting an API redesign and we could switch to that new API as well. Saggi and I also discussed how we can make VM representations a well organized collection of objects (eg. memSize=1024 => vm.append(VmMemoryStick(size=1024)) ). There are a lot of things we could do to reset the API at this stage. -- Adam Litke IBM Linux Technology Center From iheim at redhat.com Wed Oct 17 18:33:21 2012 From: iheim at redhat.com (Itamar Heim) Date: Wed, 17 Oct 2012 20:33:21 +0200 Subject: Feature pages for 3.2 In-Reply-To: <20121017182747.GL3672@aglitke> References: <1350267131.6975.15.camel@beelzebub.mburnsfire.net> <507EAB71.1080109@redhat.com> <20121017144136.GG3672@aglitke> <507EE300.4070505@redhat.com> <20121017172740.GK3672@aglitke> <507EEE6A.6050807@redhat.com> <20121017182747.GL3672@aglitke> Message-ID: <507EF9F1.8090903@redhat.com> On 10/17/2012 08:27 PM, Adam Litke wrote: > On Wed, Oct 17, 2012 at 07:44:10PM +0200, Itamar Heim wrote: >> On 10/17/2012 07:27 PM, Adam Litke wrote: >>> On Wed, Oct 17, 2012 at 06:55:28PM +0200, Itamar Heim wrote: >>>> On 10/17/2012 04:41 PM, Adam Litke wrote: >>>>> On Wed, Oct 17, 2012 at 02:58:25PM +0200, Itamar Heim wrote: >>>>>> On 10/15/2012 04:12 AM, Mike Burns wrote: >>>>>>> The 3.2 Release page[1] has a list of features targeted for 3.2. The >>>>>>> majority of the listed features either lack a feature page completely, >>>>>>> or a link is missing. If you are responsible for the component the >>>>>>> includes the feature, can you either create or have someone create a >>>>>>> feature page? A template page is available[2]. >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> Mike >>>>>>> >>>>>>> [1] http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features >>>>>>> [2] http://wiki.ovirt.org/wiki/Feature_template >>>>>>> >>>>>> >>>>>> Adam, >>>>>> >>>>>> i see 'libvdsm preview' appears on the list. >>>>>> is this based on the current legacy api prototype or the new planned api? >>>>> >>>>> I am not sure what you mean by "current legacy api prototype". I am working on >>>>> a new JsonRPC based API that is driven by a schema. libvdsm is client-side C >>>>> library with Python bindings that talks to vdsm using the the JsonRPC protocol >>>>> according to the API schema. We do not currently have the Java client generated >>>>> and that is still out of scope for 3.2 since no one is actively working on it. >>>>> >>>>> Hopefully this is enough information but if not please let me know. >>>>> >>>> >>>> for some reason i though there was a phase which used a schema closer to the >>>> old xmlrpc api. my main concern with libvdsm is when it makes 'stable' api. >>>> i assume it closely tied to the jsonrpc based api/schema. so the question is >>>> when do we declare it as supported/stable/etc? >>> >>> Well, the schema is currently very close to the xmlrpc API with some things >>> fixed.. We decided that in order for this to become the new supported API >>> eventually, it must start out working very similar to the old API. This will >>> allow ovirt-engine to migrate to the new API without a complete rewrite. >>> >>> By preview, I am thinking we will deliver the API as something for people to try >>> out but not make any API stability guarantees yet. I think we will be able to >>> declare it stable once engine starts using it. My hope is we can move in that >>> direction after the 3.2 release but it will take a concerted effort to get it >>> done. >>> >> >> wouldn't we want two phases before declaring it stable? >> 1. move the engine to it. >> 2. refactor api to be cleaner than just resembling the xml/rpc one >> (iiuc, the planned api would be much lean/mean than the xml/rpc one?) > > Yes, I would definitely be okay with cleaning it up. As a first pass we could > remove all currently deprecated APIs, remove unneeded parameters, make > parameters optional when possible, etc. I believe HSM is getting an API > redesign and we could switch to that new API as well. Saggi and I also > discussed how we can make VM representations a well organized collection of > objects (eg. memSize=1024 => vm.append(VmMemoryStick(size=1024)) ). There are a > lot of things we could do to reset the API at this stage. > but would make more sense to do after moving the engine to the current api or we'll never be able to make the migration and test for regressions, and then we could refactor both sides. post 3.2 we need to do some estimations on the effort of changing the engine and the post migration changes expected to the API to feel "better" about it to be claimed supported. From agl at us.ibm.com Wed Oct 17 18:56:40 2012 From: agl at us.ibm.com (Adam Litke) Date: Wed, 17 Oct 2012 13:56:40 -0500 Subject: Feature pages for 3.2 In-Reply-To: <507EF9F1.8090903@redhat.com> References: <1350267131.6975.15.camel@beelzebub.mburnsfire.net> <507EAB71.1080109@redhat.com> <20121017144136.GG3672@aglitke> <507EE300.4070505@redhat.com> <20121017172740.GK3672@aglitke> <507EEE6A.6050807@redhat.com> <20121017182747.GL3672@aglitke> <507EF9F1.8090903@redhat.com> Message-ID: <20121017185640.GM3672@aglitke> On Wed, Oct 17, 2012 at 08:33:21PM +0200, Itamar Heim wrote: > On 10/17/2012 08:27 PM, Adam Litke wrote: > >On Wed, Oct 17, 2012 at 07:44:10PM +0200, Itamar Heim wrote: > >>On 10/17/2012 07:27 PM, Adam Litke wrote: > >>>On Wed, Oct 17, 2012 at 06:55:28PM +0200, Itamar Heim wrote: > >>>>On 10/17/2012 04:41 PM, Adam Litke wrote: > >>>>>On Wed, Oct 17, 2012 at 02:58:25PM +0200, Itamar Heim wrote: > >>>>>>On 10/15/2012 04:12 AM, Mike Burns wrote: > >>>>>>>The 3.2 Release page[1] has a list of features targeted for 3.2. The > >>>>>>>majority of the listed features either lack a feature page completely, > >>>>>>>or a link is missing. If you are responsible for the component the > >>>>>>>includes the feature, can you either create or have someone create a > >>>>>>>feature page? A template page is available[2]. > >>>>>>> > >>>>>>>Thanks > >>>>>>> > >>>>>>>Mike > >>>>>>> > >>>>>>>[1] http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features > >>>>>>>[2] http://wiki.ovirt.org/wiki/Feature_template > >>>>>>> > >>>>>> > >>>>>>Adam, > >>>>>> > >>>>>>i see 'libvdsm preview' appears on the list. > >>>>>>is this based on the current legacy api prototype or the new planned api? > >>>>> > >>>>>I am not sure what you mean by "current legacy api prototype". I am working on > >>>>>a new JsonRPC based API that is driven by a schema. libvdsm is client-side C > >>>>>library with Python bindings that talks to vdsm using the the JsonRPC protocol > >>>>>according to the API schema. We do not currently have the Java client generated > >>>>>and that is still out of scope for 3.2 since no one is actively working on it. > >>>>> > >>>>>Hopefully this is enough information but if not please let me know. > >>>>> > >>>> > >>>>for some reason i though there was a phase which used a schema closer to the > >>>>old xmlrpc api. my main concern with libvdsm is when it makes 'stable' api. > >>>>i assume it closely tied to the jsonrpc based api/schema. so the question is > >>>>when do we declare it as supported/stable/etc? > >>> > >>>Well, the schema is currently very close to the xmlrpc API with some things > >>>fixed.. We decided that in order for this to become the new supported API > >>>eventually, it must start out working very similar to the old API. This will > >>>allow ovirt-engine to migrate to the new API without a complete rewrite. > >>> > >>>By preview, I am thinking we will deliver the API as something for people to try > >>>out but not make any API stability guarantees yet. I think we will be able to > >>>declare it stable once engine starts using it. My hope is we can move in that > >>>direction after the 3.2 release but it will take a concerted effort to get it > >>>done. > >>> > >> > >>wouldn't we want two phases before declaring it stable? > >>1. move the engine to it. > >>2. refactor api to be cleaner than just resembling the xml/rpc one > >>(iiuc, the planned api would be much lean/mean than the xml/rpc one?) > > > >Yes, I would definitely be okay with cleaning it up. As a first pass we could > >remove all currently deprecated APIs, remove unneeded parameters, make > >parameters optional when possible, etc. I believe HSM is getting an API > >redesign and we could switch to that new API as well. Saggi and I also > >discussed how we can make VM representations a well organized collection of > >objects (eg. memSize=1024 => vm.append(VmMemoryStick(size=1024)) ). There are a > >lot of things we could do to reset the API at this stage. > > > > but would make more sense to do after moving the engine to the > current api or we'll never be able to make the migration and test > for regressions, and then we could refactor both sides. > post 3.2 we need to do some estimations on the effort of changing > the engine and the post migration changes expected to the API to > feel "better" about it to be claimed supported. Agreed. One thing that may help is if we can generate a POC java binding (perhaps just for a single API) and we could see how easily that new API can be used from engine. Since engine has a vdsBroker, hopefully most of the affected engine code would be in one place. -- Adam Litke IBM Linux Technology Center From iheim at redhat.com Sun Oct 21 07:05:30 2012 From: iheim at redhat.com (Itamar Heim) Date: Sun, 21 Oct 2012 09:05:30 +0200 Subject: KVM on IBM POWER (PPC64) support in vdsm and ovirt In-Reply-To: <504CC616.60501@in.ibm.com> References: <504CC616.60501@in.ibm.com> Message-ID: <50839EBA.1080301@redhat.com> On 09/09/2012 07:38 PM, Pradipta Kumar Banerjee wrote: > Dear All, > Request your comments and suggestions on managing KVM on IBM POWER (PPC64) via > ovirt/vdsm > > Please find the feature page here - > http://wiki.ovirt.org/wiki/Features/Vdsm_for_PPC64 > > The vdsm changes are under discussion and can be found here > http://gerrit.ovirt.org/7072 > was in my queue for a while, finally got to it. thanks for the feature page. some comments on the text i copy/pasted from the wiki: > Managing KVM on IBM POWER processors requires changes to both vdsm and ovirt-engine. However the intent is to keep ovirt-engine changes to the minimum > > Following are the key changes that will be required > > Enhancing the bootstrapping mechanism in VDSM to handle IBM POWER processor and ppc64 specifics (like cpuid, cpu speed, cpu flags) > Adding a new CPU type (IBM POWER) to ovirt-engine so would this be something like intel/amd/ppc7 type of a thing? the current cpu types are indeed separated into intel and amd, but this only affects the cpu level compatibility feature at the cluster level. but they are both x86_64, so all other aspects of hardware are the same for them. i think you need a new 'arch' parameter for cluster. then you need the config to be both version and arch dependent, so you could specify things like disk/network/display/audio drives available per version, per arch. now i'm not sure i would call this 'arch', since it would make the change to the config too specific, but maybe a more general 'filter' column which allows to specify various filters on the config (arch would be one of them. maybe make filter notation a convention of "arch:x86_64" to specify what the filter is about. > Enhancing the VM templates based on guest device models (disk, network, video) supported by KVM on IBM POWER > > KVM on IBM POWER supports the following device models for guest > > virt-io, spapr-vscsi for disk > virt-io, e1000, rtl and spapr-vlan for network > vga device is supported for guest video > Only VNC backend is supported for guest console access. > > There is currently no support for SPICE protocol and USB support in guests. > > Both NFS and SAN storage is supported for the hosts. iSCSI support is currently work in progress > User Interface > > No new user interfaces are required to be added. However few of the existing interfaces needs to be updated to reflect KVM on IBM POWER related specifics. i think the arch field is needed at cluster, level, but that's indeed a small ui change. but you probably also need to add the arch to the VM/template entities, and to the OVF. all places using configs (that are relevant) would need to be fixed to use the filter. logic of moving VMs between clusters, creation of VMs from template, import/export, etc. would need to validate arch as well. > > At the minimum following user interfaces will be affected > > New Server/New Desktop Virtual Machine in userportal > New Server/New Desktop Virtual Machine in webadmin > Make Template in userportal and webadmin > Editing Virtual Disks and Editing Network Interfaces in webadmin > New Cluster in webadmin so actually, these would be affected in having more options, but these options would come from enum's. only change to look and feel of them would probably be the arch field (derived from template/cluster, not something user should be able to set, just view?) logic changes would be based on the filtering of relevant values as mentioned above. thanks, Itamar From fgranha at linux.vnet.ibm.com Mon Oct 22 12:59:21 2012 From: fgranha at linux.vnet.ibm.com (Fernando Granha Jeronimo) Date: Mon, 22 Oct 2012 10:59:21 -0200 Subject: KVM on IBM POWER (PPC64) support in vdsm and ovirt In-Reply-To: <50839EBA.1080301@redhat.com> References: <504CC616.60501@in.ibm.com> <50839EBA.1080301@redhat.com> Message-ID: <50854329.7020202@linux.vnet.ibm.com> On 10/21/2012 05:05 AM, Itamar Heim wrote: > On 09/09/2012 07:38 PM, Pradipta Kumar Banerjee wrote: >> Dear All, >> Request your comments and suggestions on managing KVM on IBM POWER >> (PPC64) via >> ovirt/vdsm >> >> Please find the feature page here - >> http://wiki.ovirt.org/wiki/Features/Vdsm_for_PPC64 >> >> The vdsm changes are under discussion and can be found here >> http://gerrit.ovirt.org/7072 >> > > was in my queue for a while, finally got to it. > thanks for the feature page. > some comments on the text i copy/pasted from the wiki: > >> Managing KVM on IBM POWER processors requires changes to both vdsm >> and ovirt-engine. However the intent is to keep ovirt-engine changes >> to the minimum >> >> Following are the key changes that will be required >> >> Enhancing the bootstrapping mechanism in VDSM to handle IBM POWER >> processor and ppc64 specifics (like cpuid, cpu speed, cpu flags) >> Adding a new CPU type (IBM POWER) to ovirt-engine > > so would this be something like intel/amd/ppc7 type of a thing? > the current cpu types are indeed separated into intel and amd, but > this only affects the cpu level compatibility feature at the cluster > level. > but they are both x86_64, so all other aspects of hardware are the > same for them. > i think you need a new 'arch' parameter for cluster. > then you need the config to be both version and arch dependent, so you > could specify things like disk/network/display/audio drives available > per version, per arch. > now i'm not sure i would call this 'arch', since it would make the > change to the config too specific, but maybe a more general 'filter' > column which allows to specify various filters on the config (arch > would be one of them. > maybe make filter notation a convention of "arch:x86_64" to specify > what the filter is about. > >> Enhancing the VM templates based on guest device models (disk, >> network, video) supported by KVM on IBM POWER >> >> KVM on IBM POWER supports the following device models for guest >> >> virt-io, spapr-vscsi for disk >> virt-io, e1000, rtl and spapr-vlan for network >> vga device is supported for guest video >> Only VNC backend is supported for guest console access. >> >> There is currently no support for SPICE protocol and USB support in >> guests. >> >> Both NFS and SAN storage is supported for the hosts. iSCSI support is >> currently work in progress >> User Interface >> >> No new user interfaces are required to be added. However few of the >> existing interfaces needs to be updated to reflect KVM on IBM POWER >> related specifics. > > i think the arch field is needed at cluster, level, but that's indeed > a small ui change. > but you probably also need to add the arch to the VM/template > entities, and to the OVF. > all places using configs (that are relevant) would need to be fixed to > use the filter. > logic of moving VMs between clusters, creation of VMs from template, > import/export, etc. would need to validate arch as well. > >> >> At the minimum following user interfaces will be affected >> >> New Server/New Desktop Virtual Machine in userportal >> New Server/New Desktop Virtual Machine in webadmin >> Make Template in userportal and webadmin >> Editing Virtual Disks and Editing Network Interfaces in webadmin >> New Cluster in webadmin > > so actually, these would be affected in having more options, but these > options would come from enum's. > only change to look and feel of them would probably be the arch field > (derived from template/cluster, not something user should be able to > set, just view?) > logic changes would be based on the filtering of relevant values as > mentioned above. > > thanks, > Itamar Hello Itamar, We are currently working on the engine-side changes for ppc support. In this first phase, we are analysing the code to carefully devise a solution and we agree that having the arch filter seems a good way to go, once it will allow a neat handling of arch specific details. Thanks, Fernando > _______________________________________________ > Arch mailing list > Arch at ovirt.org > http://lists.ovirt.org/mailman/listinfo/arch > From sgordon at redhat.com Tue Oct 23 15:11:06 2012 From: sgordon at redhat.com (Steve Gordon) Date: Tue, 23 Oct 2012 11:11:06 -0400 (EDT) Subject: Feature pages for 3.2 In-Reply-To: <1350267131.6975.15.camel@beelzebub.mburnsfire.net> Message-ID: <801812220.19194068.1351005066645.JavaMail.root@redhat.com> ----- Original Message ----- > From: "Mike Burns" > To: "Itamar Heim" , "Dan Kenigsberg" , "Ayal Baron" , "Livnat > Peer" , "Doron Fediuck" > Cc: "arch" > Sent: Sunday, October 14, 2012 10:12:11 PM > Subject: Feature pages for 3.2 > > The 3.2 Release page[1] has a list of features targeted for 3.2. The > majority of the listed features either lack a feature page > completely, > or a link is missing. If you are responsible for the component the > includes the feature, can you either create or have someone create a > feature page? A template page is available[2]. > > Thanks > > Mike > > [1] http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features > [2] http://wiki.ovirt.org/wiki/Feature_template I have been through the list of feature pages and just have a few comments to make: - Port mirroring was listed in the 3.1 release notes as supported, it is still in this list so does this mean it didn't actually make it or is this a further improvement to that functionality? - Some of the feature pages for gluster functionality are pretty light on detail. In particular: http://wiki.ovirt.org/wiki/Features/Gluster_Geo_Replication http://wiki.ovirt.org/wiki/Features/Gluster_Volume_Asynchronous_Tasks_Management http://wiki.ovirt.org/wiki/Features/Gluster_Volume_Performance_Statistics - Still missing pages for: * Bootstrap improvements * VM creation base on pre-defined profiles (instance types) * libvdsm preview * webadmin: allow column resizing & sorting in grid (bz 767924) * user level api * automatic storage domain upgrade * Japanese localization * full plugin support including example plugins (snmp, cim) Granted I already have a fair idea what some of these relate to, but let's make sure we have specific feature pages defining the desired scope for each of these. Thanks, Steve From alonbl at redhat.com Tue Oct 23 15:19:04 2012 From: alonbl at redhat.com (Alon Bar-Lev) Date: Tue, 23 Oct 2012 11:19:04 -0400 (EDT) Subject: Feature pages for 3.2 In-Reply-To: <801812220.19194068.1351005066645.JavaMail.root@redhat.com> Message-ID: <1247815022.5115715.1351005544577.JavaMail.root@redhat.com> ----- Original Message ----- > From: "Steve Gordon" > To: "arch" > Sent: Tuesday, October 23, 2012 5:11:06 PM > Subject: Re: Feature pages for 3.2 > > ----- Original Message ----- > > From: "Mike Burns" > > To: "Itamar Heim" , "Dan Kenigsberg" > > , "Ayal Baron" , "Livnat > > Peer" , "Doron Fediuck" > > Cc: "arch" > > Sent: Sunday, October 14, 2012 10:12:11 PM > > Subject: Feature pages for 3.2 > > > > The 3.2 Release page[1] has a list of features targeted for 3.2. > > The > > majority of the listed features either lack a feature page > > completely, > > or a link is missing. If you are responsible for the component the > > includes the feature, can you either create or have someone create > > a > > feature page? A template page is available[2]. > > > > Thanks > > > > Mike > > > > [1] > > http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features > > [2] http://wiki.ovirt.org/wiki/Feature_template > > I have been through the list of feature pages and just have a few > comments to make: > > - Port mirroring was listed in the 3.1 release notes as supported, it > is still in this list so does this mean it didn't actually make it > or is this a further improvement to that functionality? > > - Some of the feature pages for gluster functionality are pretty > light on detail. In particular: > http://wiki.ovirt.org/wiki/Features/Gluster_Geo_Replication > http://wiki.ovirt.org/wiki/Features/Gluster_Volume_Asynchronous_Tasks_Management > http://wiki.ovirt.org/wiki/Features/Gluster_Volume_Performance_Statistics > > - Still missing pages for: > * Bootstrap improvements I wrote this long ago... there was a problem in the link. > * VM creation base on pre-defined profiles (instance types) > * libvdsm preview > * webadmin: allow column resizing & sorting in grid (bz 767924) > * user level api > * automatic storage domain upgrade > * Japanese localization > * full plugin support including example plugins (snmp, cim) > Granted I already have a fair idea what some of these relate to, > but let's make sure we have specific feature pages defining the > desired scope for each of these. > > Thanks, > > Steve > _______________________________________________ > Arch mailing list > Arch at ovirt.org > http://lists.ovirt.org/mailman/listinfo/arch > From lpeer at redhat.com Tue Oct 23 15:56:32 2012 From: lpeer at redhat.com (Livnat Peer) Date: Tue, 23 Oct 2012 17:56:32 +0200 Subject: Feature pages for 3.2 In-Reply-To: <801812220.19194068.1351005066645.JavaMail.root@redhat.com> References: <801812220.19194068.1351005066645.JavaMail.root@redhat.com> Message-ID: <5086BE30.1040103@redhat.com> On 23/10/12 17:11, Steve Gordon wrote: > ----- Original Message ----- >> From: "Mike Burns" >> To: "Itamar Heim" , "Dan Kenigsberg" , "Ayal Baron" , "Livnat >> Peer" , "Doron Fediuck" >> Cc: "arch" >> Sent: Sunday, October 14, 2012 10:12:11 PM >> Subject: Feature pages for 3.2 >> >> The 3.2 Release page[1] has a list of features targeted for 3.2. The >> majority of the listed features either lack a feature page >> completely, >> or a link is missing. If you are responsible for the component the >> includes the feature, can you either create or have someone create a >> feature page? A template page is available[2]. >> >> Thanks >> >> Mike >> >> [1] http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features >> [2] http://wiki.ovirt.org/wiki/Feature_template > > I have been through the list of feature pages and just have a few comments to make: > > - Port mirroring was listed in the 3.1 release notes as supported, it is still in this list so does this mean it didn't actually make it or is this a further improvement to that functionality? Port mirroring did not actually work in 3.1. We fixed it and now it should be fine. > > - Some of the feature pages for gluster functionality are pretty light on detail. In particular: > http://wiki.ovirt.org/wiki/Features/Gluster_Geo_Replication > http://wiki.ovirt.org/wiki/Features/Gluster_Volume_Asynchronous_Tasks_Management > http://wiki.ovirt.org/wiki/Features/Gluster_Volume_Performance_Statistics > > - Still missing pages for: > * Bootstrap improvements > * VM creation base on pre-defined profiles (instance types) > * libvdsm preview > * webadmin: allow column resizing & sorting in grid (bz 767924) > * user level api > * automatic storage domain upgrade > * Japanese localization > * full plugin support including example plugins (snmp, cim) > Granted I already have a fair idea what some of these relate to, but let's make sure we have specific feature pages defining the desired scope for each of these. > > Thanks, > > Steve > From iheim at redhat.com Wed Oct 24 03:37:56 2012 From: iheim at redhat.com (Itamar Heim) Date: Wed, 24 Oct 2012 05:37:56 +0200 Subject: [Users] Call For Agenda Items -- oVirt Weekly Meeting 2012-10-24 In-Reply-To: <1350907677.4120.14.camel@beelzebub.mburnsfire.net> References: <1350907677.4120.14.camel@beelzebub.mburnsfire.net> Message-ID: <50876294.3050402@redhat.com> On 10/22/2012 02:07 PM, Mike Burns wrote: > Meeting Time and Place > oVirt Weekly Sync > * Wednesdays @ 15:00 UTC (may change during DST changes) - always > at 7:00am US Pacific, 10:00am US Eastern. > * To see in your timezone date -d 'WEDNESDAY 1000 EDT' > * On IRC: #ovirt on irc.oftc.net > > This is the agenda for the 2012-10-24 meeting: > > * Status of Next Release (Feature Status) (switching to arch) question for next release: i was under the impression we are targeting main underlying distro as fedora 18 for 3.2. fedora schedule seems to be RC build is only 28-nov? thanks, Itamar > * Sub-project reports (engine, vdsm, node, infra) > * Workshop Report > > If you have other topics, please reply to me and I will add them to the > agenda. If you propose a topic, please be prepared to lead the > discussion during the meeting. > > Thanks > > Mike > > _______________________________________________ > Users mailing list > Users at ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > From iheim at redhat.com Wed Oct 24 04:36:00 2012 From: iheim at redhat.com (Itamar Heim) Date: Wed, 24 Oct 2012 06:36:00 +0200 Subject: [Engine-devel] Feature page for GLUSTERFS_DOMAIN support is now available. In-Reply-To: <508527A6.2070109@linux.vnet.ibm.com> References: <508526A7.2050001@linux.vnet.ibm.com> <508527A6.2070109@linux.vnet.ibm.com> Message-ID: <50877030.6040203@redhat.com> On 10/22/2012 01:01 PM, Deepak C Shetty wrote: > Hi list, > I created a wiki page for GLUSTERFS_DOMAIN support. > Comments/Suggestions are welcome. > > http://wiki.ovirt.org/wiki/Features/GlusterFS_Storage_Domain (moving to @arch) several thoughts: 1. it almost sounds like a property of posixfs storage domain on how to attach the disk, since everything else is similar to posixfs, but i don't think we have a better way to notate this than a new type of storage domain today (actually, a new type of data center for now as well). 2. general question on the solution: this sounds somewhat like iscsi, which qemu doesn't handle. why not do the mapping of a remote gluster file to a block device at host level, by passing the fuse layer, in a general use case (not qemu specific)? this would be both useful to non qemu users of gluster and will not require any change to qemu/libvirt? now, just a thought, if we combine 1+2, maybe this can become an option of posixfs domain on "block mapper utility", with a predefined list of options in the engine vdsm supports (well, hooks maybe as well). such a block mapper utility would provide vdsm with the block device to mount for the posixfs mount/volume path it got. 3. wrt scope, iiuc: - all disk manipulations are still done like normal posixfs - running the VM is done directly via block device wouldn't using block device also improve other operations, like DD/qemu-img? (doesn't mean need to be in first phase) 4. nit: UI, i assume no need to specify vfsType, since it is always glusterfs? From sgordon at redhat.com Wed Oct 24 18:08:35 2012 From: sgordon at redhat.com (Steve Gordon) Date: Wed, 24 Oct 2012 14:08:35 -0400 (EDT) Subject: [Users] Call For Agenda Items -- oVirt Weekly Meeting 2012-10-24 In-Reply-To: <50876294.3050402@redhat.com> Message-ID: <1252731677.21657758.1351102115494.JavaMail.root@redhat.com> ----- Original Message ----- > From: "Itamar Heim" > To: "Mike Burns" > Cc: arch at ovirt.org > Sent: Tuesday, October 23, 2012 11:37:56 PM > Subject: Re: [Users] Call For Agenda Items -- oVirt Weekly Meeting 2012-10-24 > > On 10/22/2012 02:07 PM, Mike Burns wrote: > > Meeting Time and Place > > oVirt Weekly Sync > > * Wednesdays @ 15:00 UTC (may change during DST changes) - > > always > > at 7:00am US Pacific, 10:00am US Eastern. > > * To see in your timezone date -d 'WEDNESDAY 1000 > > EDT' > > * On IRC: #ovirt on irc.oftc.net > > > > This is the agenda for the 2012-10-24 meeting: > > > > * Status of Next Release (Feature Status) > > (switching to arch) > question for next release: > i was under the impression we are targeting main underlying distro as > fedora 18 for 3.2. > fedora schedule seems to be RC build is only 28-nov? > > thanks, > Itamar The Fedora 18 schedule has slipped a number of times, when we decided on this we were probably looking at the original schedule which had GA at November 6th [1]. Steve [1] http://fedoraproject.org/wiki/Releases/18/Schedule From kmayilsa at redhat.com Thu Oct 25 04:30:12 2012 From: kmayilsa at redhat.com (Kanagaraj) Date: Thu, 25 Oct 2012 10:00:12 +0530 Subject: Feature pages for 3.2 In-Reply-To: <801812220.19194068.1351005066645.JavaMail.root@redhat.com> References: <801812220.19194068.1351005066645.JavaMail.root@redhat.com> Message-ID: <5088C054.7050809@redhat.com> On Tuesday 23 October 2012 08:41 PM, Steve Gordon wrote: > ----- Original Message ----- >> From: "Mike Burns" >> To: "Itamar Heim" , "Dan Kenigsberg" , "Ayal Baron" , "Livnat >> Peer" , "Doron Fediuck" >> Cc: "arch" >> Sent: Sunday, October 14, 2012 10:12:11 PM >> Subject: Feature pages for 3.2 >> >> The 3.2 Release page[1] has a list of features targeted for 3.2. The >> majority of the listed features either lack a feature page >> completely, >> or a link is missing. If you are responsible for the component the >> includes the feature, can you either create or have someone create a >> feature page? A template page is available[2]. >> >> Thanks >> >> Mike >> >> [1] http://wiki.ovirt.org/wiki/OVirt_3.2_release-management#Features >> [2] http://wiki.ovirt.org/wiki/Feature_template > I have been through the list of feature pages and just have a few comments to make: > > - Port mirroring was listed in the 3.1 release notes as supported, it is still in this list so does this mean it didn't actually make it or is this a further improvement to that functionality? > > - Some of the feature pages for gluster functionality are pretty light on detail. In particular: > http://wiki.ovirt.org/wiki/Features/Gluster_Geo_Replication > http://wiki.ovirt.org/wiki/Features/Gluster_Volume_Asynchronous_Tasks_Management > http://wiki.ovirt.org/wiki/Features/Gluster_Volume_Performance_Statistics I am working on these items and will be available in couple of days. > > - Still missing pages for: > * Bootstrap improvements > * VM creation base on pre-defined profiles (instance types) > * libvdsm preview > * webadmin: allow column resizing & sorting in grid (bz 767924) > * user level api > * automatic storage domain upgrade > * Japanese localization > * full plugin support including example plugins (snmp, cim) > Granted I already have a fair idea what some of these relate to, but let's make sure we have specific feature pages defining the desired scope for each of these. > > Thanks, > > Steve > _______________________________________________ > Arch mailing list > Arch at ovirt.org > http://lists.ovirt.org/mailman/listinfo/arch From deepakcs at linux.vnet.ibm.com Mon Oct 29 06:57:14 2012 From: deepakcs at linux.vnet.ibm.com (Deepak C Shetty) Date: Mon, 29 Oct 2012 12:27:14 +0530 Subject: [Engine-devel] Feature page for GLUSTERFS_DOMAIN support is now available. In-Reply-To: <50877030.6040203@redhat.com> References: <508526A7.2050001@linux.vnet.ibm.com> <508527A6.2070109@linux.vnet.ibm.com> <50877030.6040203@redhat.com> Message-ID: <508E28CA.9080201@linux.vnet.ibm.com> On 10/24/2012 10:06 AM, Itamar Heim wrote: > On 10/22/2012 01:01 PM, Deepak C Shetty wrote: >> Hi list, >> I created a wiki page for GLUSTERFS_DOMAIN support. >> Comments/Suggestions are welcome. >> >> http://wiki.ovirt.org/wiki/Features/GlusterFS_Storage_Domain > > (moving to @arch) > > several thoughts: > 1. it almost sounds like a property of posixfs storage domain on how > to attach the disk, since everything else is similar to posixfs, but i > don't think we have a better way to notate this than a new type of > storage domain today (actually, a new type of data center for now as > well). I had tried doing somethign similar but that was rejected by Saggi ! Pls see https://lists.fedorahosted.org/pipermail/vdsm-devel/2012-July/001258.html > > 2. general question on the solution: this sounds somewhat like iscsi, > which qemu doesn't handle. why not do the mapping of a remote gluster > file to a block device at host level, by passing the fuse layer, in a > general use case (not qemu specific)? > this would be both useful to non qemu users of gluster and will not > require any change to qemu/libvirt? Goal here was to use GlusterFS as a filesystem layer for virt. stack, so that all virt. related ops can be done/achieved using simple FS cmds. We are not looking at doing (what looks like the opposite to me) things the other way. We are also looking at this purely from the virt. stack layer, hence haven't thought abt non-qemu use cases. I am still not clear on how what you are proposing works and helps ? Why add block->fs conversion when Gluster is designed as FS and any application ( qemu and non-qemu as well) can use libgfapi to talk to images stored in gluster bypassing the fuse layer, so that part is already covered. > > now, just a thought, if we combine 1+2, maybe this can become an > option of posixfs domain on "block mapper utility", with a predefined > list of options in the engine vdsm supports (well, hooks maybe as well). > such a block mapper utility would provide vdsm with the block device > to mount for the posixfs mount/volume path it got. Can you provide more details here, its not clear to us (Copying bharata as well who worked on native qemu-glusterfs integraiton). In case you are referring to the Gluster BD xlator, that does the reverse of this (block is seen as file). I am a bit confused here. > > 3. wrt scope, iiuc: > - all disk manipulations are still done like normal posixfs > - running the VM is done directly via block device To clarify, this wikipage *does not refer to the BD xlator work*. This wikipage refers to fitting QEMU-GlusterFS native integration with VDSM usign a new storage domain. VM is run using Gluster as a backend (QEMU's way of talking with FS), not as a block device. > > wouldn't using block device also improve other operations, like > DD/qemu-img? > (doesn't mean need to be in first phase) > > 4. nit: UI, i assume no need to specify vfsType, since it is always > glusterfs? Agree, showing vfsType will be good for FYI reasons tho :) > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kwade at redhat.com Mon Oct 29 23:53:14 2012 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Mon, 29 Oct 2012 16:53:14 -0700 Subject: Outage notice: Upgrading MediaWiki Message-ID: <508F16EA.3070608@redhat.com> I have things lined up right now to upgrade the MediaWiki instance. Reply here or join irc.oftc.net on #ovirt if you want to stop me for any reason. It's a one-way upgrade, as the database tables have to be updated. That means I need to take Apache offline, do the upgrade, then come back online. This affects the following services: * WordPress (www.ovirt.org) * MediaWiki (wiki.ovirt.org) * Apache (ovirt.org/*) * Mailman web interface (lists.ovirt.org/mailman/listinfo) ** Mailing lists should be unaffected If there are any problems, then things stay offline until I get a resolution. Once I begin the upgrade, I'm going to push forward until it's done - there is no fall-back-to-previous-version position. - Karsten -- Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From kwade at redhat.com Tue Oct 30 03:05:36 2012 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Mon, 29 Oct 2012 20:05:36 -0700 Subject: Outage notice: Upgrading MediaWiki In-Reply-To: <508F16EA.3070608@redhat.com> References: <508F16EA.3070608@redhat.com> Message-ID: <508F4400.5080102@redhat.com> This maintenance is ongoing. I'm having troubles getting the database to update or be recognized as updated. I'll send more updates when there is something to update. On 10/29/2012 04:53 PM, Karsten 'quaid' Wade wrote: > I have things lined up right now to upgrade the MediaWiki instance. > Reply here or join irc.oftc.net on #ovirt if you want to stop me for any > reason. > > It's a one-way upgrade, as the database tables have to be updated. That > means I need to take Apache offline, do the upgrade, then come back online. > > This affects the following services: > > * WordPress (www.ovirt.org) > * MediaWiki (wiki.ovirt.org) > * Apache (ovirt.org/*) > * Mailman web interface (lists.ovirt.org/mailman/listinfo) > ** Mailing lists should be unaffected > > If there are any problems, then things stay offline until I get a > resolution. Once I begin the upgrade, I'm going to push forward until > it's done - there is no fall-back-to-previous-version position. > > - Karsten > > > > _______________________________________________ > Arch mailing list > Arch at ovirt.org > http://lists.ovirt.org/mailman/listinfo/arch > -- Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From kwade at redhat.com Tue Oct 30 03:31:50 2012 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Mon, 29 Oct 2012 20:31:50 -0700 Subject: Outage notice: Upgrading MediaWiki In-Reply-To: <508F4400.5080102@redhat.com> References: <508F16EA.3070608@redhat.com> <508F4400.5080102@redhat.com> Message-ID: <508F4A26.4020409@redhat.com> The wiki upgrade is primarily working. At the moment we the wiki is not showing the site CSS, thus no skin/theme. I'm working on that, but the content is now available. (For the record, I forgot to set the database prefix in the config file, so it was looking for standard table names without the prefix our database uses: $wgDBprefix = "mw_"; ) On 10/29/2012 08:05 PM, Karsten 'quaid' Wade wrote: > This maintenance is ongoing. I'm having troubles getting the database to > update or be recognized as updated. I'll send more updates when there is > something to update. > > On 10/29/2012 04:53 PM, Karsten 'quaid' Wade wrote: >> I have things lined up right now to upgrade the MediaWiki instance. >> Reply here or join irc.oftc.net on #ovirt if you want to stop me for any >> reason. >> >> It's a one-way upgrade, as the database tables have to be updated. That >> means I need to take Apache offline, do the upgrade, then come back online. >> >> This affects the following services: >> >> * WordPress (www.ovirt.org) >> * MediaWiki (wiki.ovirt.org) >> * Apache (ovirt.org/*) >> * Mailman web interface (lists.ovirt.org/mailman/listinfo) >> ** Mailing lists should be unaffected >> >> If there are any problems, then things stay offline until I get a >> resolution. Once I begin the upgrade, I'm going to push forward until >> it's done - there is no fall-back-to-previous-version position. >> >> - Karsten >> >> >> >> _______________________________________________ >> 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 > -- Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From kwade at redhat.com Tue Oct 30 03:59:14 2012 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Mon, 29 Oct 2012 20:59:14 -0700 Subject: Outage notice: Upgrading MediaWiki In-Reply-To: <508F4A26.4020409@redhat.com> References: <508F16EA.3070608@redhat.com> <508F4400.5080102@redhat.com> <508F4A26.4020409@redhat.com> Message-ID: <508F5092.6000303@redhat.com> I'm declaring his maintenance outage to be over. There are a few clean-up items around extensions (getting ConfirmAccount working correctly, for example), but things are primarily working with the upgraded MediaWiki 1.19.2. I'd like to get us on to OpenShift fairly soon, rather than spending more time cleaning up the cruft on the current host. Expect more news on that front soon. - Karsten On 10/29/2012 08:31 PM, Karsten 'quaid' Wade wrote: > The wiki upgrade is primarily working. At the moment we the wiki is not > showing the site CSS, thus no skin/theme. I'm working on that, but the > content is now available. > > (For the record, I forgot to set the database prefix in the config file, > so it was looking for standard table names without the prefix our > database uses: > > $wgDBprefix = "mw_"; > ) > > On 10/29/2012 08:05 PM, Karsten 'quaid' Wade wrote: >> This maintenance is ongoing. I'm having troubles getting the database to >> update or be recognized as updated. I'll send more updates when there is >> something to update. >> >> On 10/29/2012 04:53 PM, Karsten 'quaid' Wade wrote: >>> I have things lined up right now to upgrade the MediaWiki instance. >>> Reply here or join irc.oftc.net on #ovirt if you want to stop me for any >>> reason. >>> >>> It's a one-way upgrade, as the database tables have to be updated. That >>> means I need to take Apache offline, do the upgrade, then come back online. >>> >>> This affects the following services: >>> >>> * WordPress (www.ovirt.org) >>> * MediaWiki (wiki.ovirt.org) >>> * Apache (ovirt.org/*) >>> * Mailman web interface (lists.ovirt.org/mailman/listinfo) >>> ** Mailing lists should be unaffected >>> >>> If there are any problems, then things stay offline until I get a >>> resolution. Once I begin the upgrade, I'm going to push forward until >>> it's done - there is no fall-back-to-previous-version position. >>> >>> - Karsten >>> >>> >>> >>> _______________________________________________ >>> 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 >> > > > > > _______________________________________________ > Arch mailing list > Arch at ovirt.org > http://lists.ovirt.org/mailman/listinfo/arch > -- Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From mburns at redhat.com Wed Oct 31 15:04:27 2012 From: mburns at redhat.com (Mike Burns) Date: Wed, 31 Oct 2012 11:04:27 -0400 Subject: oVirt Weekly Meeting 2012-11-07 -- Cancel or hold? Message-ID: <1351695867.4661.12.camel@beelzebub.mburnsfire.net> Should we consider canceling the weekly meeting next week since most of the major decision makers are all going to be tied up with KVM Forum/oVirt Workshop in Barcelona? Mike From dneary at redhat.com Wed Oct 31 15:19:09 2012 From: dneary at redhat.com (Dave Neary) Date: Wed, 31 Oct 2012 16:19:09 +0100 Subject: oVirt Weekly Meeting 2012-11-07 -- Cancel or hold? In-Reply-To: <1351695867.4661.12.camel@beelzebub.mburnsfire.net> References: <1351695867.4661.12.camel@beelzebub.mburnsfire.net> Message-ID: <5091416D.9040506@redhat.com> Hi, On 10/31/2012 04:04 PM, Mike Burns wrote: > Should we consider canceling the weekly meeting next week since most of > the major decision makers are all going to be tied up with KVM > Forum/oVirt Workshop in Barcelona? I think probably cancel. But to ask another way - what is the agenda for next week's meeting? And who needs to be there for it? Cheers, Dave. -- Dave Neary Community Action and Impact Open Source and Standards, Red Hat Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13 From iheim at redhat.com Wed Oct 31 17:02:33 2012 From: iheim at redhat.com (Itamar Heim) Date: Wed, 31 Oct 2012 19:02:33 +0200 Subject: oVirt Weekly Meeting 2012-11-07 -- Cancel or hold? In-Reply-To: <1351695867.4661.12.camel@beelzebub.mburnsfire.net> References: <1351695867.4661.12.camel@beelzebub.mburnsfire.net> Message-ID: <509159A9.1080808@redhat.com> On 10/31/2012 05:04 PM, Mike Burns wrote: > Should we consider canceling the weekly meeting next week since most of > the major decision makers are all going to be tied up with KVM > Forum/oVirt Workshop in Barcelona? +1 for canceling next week. From dneary at redhat.com Wed Oct 31 17:35:53 2012 From: dneary at redhat.com (Dave Neary) Date: Wed, 31 Oct 2012 18:35:53 +0100 Subject: Last-minute schedule changes to oVirt Workshop Message-ID: <50916179.7030609@redhat.com> Hi all, Because of the cancellation of a session on next Thursday the 8th of November in the oVirt Workshop in Barcelona, we have moved things around a bit in the schedule to make room for BOF sessions on Thursday at 5pm. As a result, the sessions of Pino de Candia, Viay Bellur and Deepak Shetty have moved a little earlier - Pino will now be presenting IaaS networking comparing virtual networking to openflow-controlled switch fabrics at 2:20pm, Vijay will present oVirt & Gluster integration after the break at 3:30pm, and Deepak will present the integration of GlusterFS as a storage domain in VDSM at 4:15pm. As a result of the reshuffle, we now have an hour (5pm-6pm) when we can schedule BOFs - I would love to see discussion here about potential BOF topics. The full schedule for the oVirt Workshop is now: Wednesday, Nov 7th - L'Aria Restaurant Time Title 9:00-11:00 oVirt Overview and Demo Andy Cathrow 11:00-12:00 oVirt Node ? Architecture, Design and Roadmap Mike Burns 12:00-13:00 Lunch 13:00-13:40 oVirt High Level Architecture and Roadmap Itamar Heim 13:40-14:20 Deep Dive Features: Network Simon Grinberg 14:20-15:00 Deep Dive Features: Storage Andy Cathrow 15:30 ? 18:00 Hands-on Lab ? Use and Install Thursday, Nov 8th - Rubi Time Title 9:00-10:00 Scripting and Integration: oVirt CLI and SDK Simon Grinberg 10:30-11:00 Using oVirt via EC2/CIMI with Deltacloud Oved Ourfali 11:00-11:30 Extending oVirt's Web Interface with UI Plugins Vojtech Szocs 11:30-12:00 Integrating oVirt into GNOME Boxes Christophe Fergeau 12:00-13:00 Lunch 13:00-13:40 Extending oVirt via Custom Hooks Andy Cathrow 13:40-14:20 SLA at oVirt Doron Fediuck 14:20-15:00 IaaS Networking: Overlay-Based Virtual Networking vs Openflow-Controlled Switch Fabrics Pino de Candia 15:30-16:15 oVirt/Gluster Integration Vijay Bellur 16:15-17:00 Integrating GlusterFS as a Storage Domain in VDSM Deepak C. Shetty 17:00-18:00 BOFs Friday, Nov 9th - Rubi Time Title 09:00-09:15 oVirt keynote in Ambar 09:15-09:35 oVirt Infrastructure Overview Mike Burns 09:35-10:00 Automated Testing of oVirt Node Fabian Deutsch 10:30-11:15 libvdsm: A Stable and Supportable Node-Level API Adam Litke 11:15-12:00 VDSM for Developers Federico Simoncelli 12:00-13:00 Lunch 13:00-13:40 Engine for Developers Juan Hernandez 13:40-14:20 Storage Live Migration: Under the Hood Federico Simoncelli 14:20-15:00 UI for Developers Vojtech Szocs 15:30-16:00 oVirt Node and OpenStack Fabian Deutsch 16:00-16:45 Drools Integration into oVirt Engine Laszlo Horyak 16:45-17-30 BOF: How can we improve oVirt Troubleshooting? Lee Yarwood In addition, as Jason said yesterday, there are several oVirt related sessions throuout the week in Barcelona: Itamar will present oVirt during the CloudOpen Summit on Tuesday 6th at 14:15 in Verdi, Andy Cathrow will give an overview of oVirt to KVM BOF attendees at 17:30 on Wednesday 8th in Ambar, and Vijay Bellur will present the integration of GlusterFS, oVirt and KVM at the Gluster workshop in Vivaldi on Thursday 8th. See you all there! And please do suggest BOF topics here (although, as usual with BOFs, those who turn up decide what to talk about). Cheers, Dave. -- Dave Neary Community Action and Impact Open Source and Standards, Red Hat Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13