Re: [Engine-devel] Change in ovirt-engine[master]: core: enable to decrease DC compatibility...
- Original Message - > From: "Itamar Heim" > To: engine-devel@ovirt.org > Cc: "Eli Mesika" , "Federico Simoncelli" > , "Allon Mureinik" > , "Livnat Peer" > Sent: Wednesday, March 12, 2014 11:59:16 AM > Subject: Re: Change in ovirt-engine[master]: core: enable to decrease DC > compatibility... > > On 03/12/2014 12:26 AM, emes...@redhat.com wrote: > > Eli Mesika has submitted this change and it was merged. > > > > Change subject: core: enable to decrease DC compatibility... > > .. > > > > > > core: enable to decrease DC compatibility... > > > > enable to decrease DC compatibility version if DC has no clusters > > > > This patch enables to decrease the DC compatibility version if DC has no > > clusters. > > Eli - just saw this. I'm pretty sure it would be *bad* to downgrade a DC > version if it has storage domains as well. not sure if this is checked > already or not. > > may also be an issue with some logical network features. Downgrading a DC from storage perspective is problematic (domain version, storage pool metadata removal, etc). This should be blocked. -- Federico ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] oVirt - Glance Integration Deep Dive Session
- Original Message - > From: "Federico Simoncelli" > To: "oVirt Users" , "engine-devel" > Sent: Monday, July 29, 2013 11:44:21 AM > Subject: oVirt - Glance Integration Deep Dive Session > > Hi everyone, > on Tuesday at 3pm (CEST) I will be presenting the recent work done in > integrating OpenStack Glance into oVirt 3.3. > > The presentation will include both a high level overview (usage in webadmin) > and a deep dive about the low level implementation details. > > When: > Tue 30 Jul 2013 15:00 - 16:00 (CEST) > > Where: > https://sas.elluminate.com/m.jnlp?sid=819&password=M.9E565882E4EA0288E3479F3D2141BD > > Bridge: 8425973915# > Phone numbers: http://www.ovirt.org/Intercall Hi everyone, here you are the slides and the recordings: Slides: http://www.ovirt.org/File:Ovirt-2013-glance-integration-deep-dive.pdf Youtube video: http://www.youtube.com/watch?v=_Nyi1xyiQnY Elluminate recording: https://sas.elluminate.com/p.jnlp?psid=2013-07-30.0631.M.46676CB153495B16DF1807973906F0.vcr&sid=819 -- Federico ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] oVirt - Glance Integration Deep Dive Session
BEGIN:VCALENDAR PRODID:Zimbra-Calendar-Provider VERSION:2.0 METHOD:REQUEST BEGIN:VTIMEZONE TZID:Europe/Berlin BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETTO:+0100 TZOFFSETFROM:+0200 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=-1SU TZNAME:CET END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02 TZOFFSETTO:+0200 TZOFFSETFROM:+0100 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=-1SU TZNAME:CEST END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT UID:8ea8a413-e9de-46be-be2d-8f83ca22df3a SUMMARY:oVirt - Glance Integration Deep Dive Session ATTENDEE;CN=oVirt Users;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE :mailto:us...@ovirt.org ATTENDEE;CN=engine-devel;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRU E:mailto:engine-devel@ovirt.org ORGANIZER;CN=Federico Simoncelli:mailto:fsimo...@redhat.com DTSTART;TZID="Europe/Berlin":20130730T15 DTEND;TZID="Europe/Berlin":20130730T16 STATUS:CONFIRMED CLASS:PUBLIC X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY TRANSP:OPAQUE LAST-MODIFIED:20130729T094421Z DTSTAMP:20130729T094421Z SEQUENCE:0 DESCRIPTION:The following is a new meeting request:\n\nSubject: oVirt - Glan ce Integration Deep Dive Session \nOrganizer: "Federico Simoncelli" \n\nTime: Tuesday\, July 30\, 2013\, 3:00:00 PM - 4:00:00 PM G MT +01:00 Amsterdam\, Berlin\, Bern\, Rome\, Stockholm\, Vienna\n \nInvitees : us...@ovirt.org\; engine-devel@ovirt.org \n\n\n*~*~*~*~*~*~*~*~*~*\n\nHi e veryone\,\n on Tuesday at 3pm (CEST) I will be presenting the recent work do ne in\nintegrating OpenStack Glance into oVirt 3.3.\n\nThe presentation will include both a high level overview (usage in webadmin)\nand a deep dive abo ut the low level implementation details.\n\nWhen:\nTue 30 Jul 2013 15:00 - 1 6:00 (CEST)\n\nWhere:\nhttps://sas.elluminate.com/m.jnlp?sid=819&password=M. 9E565882E4EA0288E3479F3D2141BD\n\nBridge: 8425973915#\nPhone numbers: http:/ /www.ovirt.org/Intercall\n\n-- \nFederico\n BEGIN:VALARM ACTION:DISPLAY TRIGGER;RELATED=START:-PT5M DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] oVirt 3.3 feature freeze and delivery to testing repo
- Original Message - > From: "Itamar Heim" > To: "Moran Goldboim" , "Doron Fediuck" > , "Greg Padgett" > , "Omer Frenkel" , "Michal > Skrivanek" , "Mike > Kolesnik" , "Livnat Peer" , "Ayal > Baron" , "Federico > Simoncelli" > Cc: "engine-devel" > Sent: Tuesday, July 16, 2013 3:03:46 PM > Subject: Re: [Engine-devel] oVirt 3.3 feature freeze and delivery to testing > repo > > On 07/15/2013 05:45 PM, Moran Goldboim wrote: > > Maintainers and all, > > > > due to some misunderstanding regarding feature freeze for ovirt 3.3 > > release (suppose to be today, but marked as Jul 17th on release page), > > we are extending feature freeze till wendesday. > > > > feature owners: > > -please update 3.3 release page [1] with the feature status > > -please update testing page for your feature > > > > package owners- once your component is ready (should be done till > > wendesday) > > -tag your repo for 3.3 beta release > > -provide srpm to mike > > -provide fc19/el6 rpms builds using mock to mike > > > > mike if you would like to set a place people can upload it too please > > let us know. > > > > > > [1]http://www.ovirt.org/OVirt_3.3_release-management#Features_Status_Table > > > > what's the status of these which seem a shame to release without (and > all are supposed to be on their final step)? > - glance integration (federico) VDSM side is merged. Engine patches need some revisions, overall feedback is positive (+1/+2). -- Federico > - Neutron (quantum) integration (livnat/mike)? > - cloud-init (greg/omer)? > - plugable scheduling (doron)? ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] What type of DB inheritance to use?
- Original Message - > From: "Eli Mesika" > To: "Liran Zelkha" > Cc: "engine-devel" > Sent: Tuesday, May 14, 2013 3:21:11 AM > Subject: Re: [Engine-devel] What type of DB inheritance to use? > > > > - Original Message - > > From: "Liran Zelkha" > > To: "Yair Zaslavsky" > > Cc: "engine-devel" > > Sent: Sunday, May 12, 2013 1:19:07 PM > > Subject: Re: [Engine-devel] What type of DB inheritance to use? > > > > Hi > > > > From my experience, single table inheritance quickly grows into something > > unmanagable, as more and more (child related) fields are added, each line > > has a few relevant attributes, and a long list of NULL values. > > I would go with option 3. With materialized views, the costs of joins can > > be > > eliminated. > > +1 I'd prefer option 3 too. -- Federico ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] What type of DB inheritance to use?
- Original Message -
> From: "Itamar Heim"
> To: "Oved Ourfalli"
> Cc: "engine-devel"
> Sent: Monday, May 13, 2013 9:46:48 AM
> Subject: Re: [Engine-devel] What type of DB inheritance to use?
>
> On 05/13/2013 10:42 AM, Oved Ourfalli wrote:
> > IMO, the following fields will fit most providers, at least the ones we
> > plan to support in the near future:
> > * id
> > * name
> > * type
> > * URL
> > * requires_authentication (boolean) to support development/POC/testing...
> > mode
>
> redundant with empty username/password?
>
> > * username
> > * password
>
> do keystone based services allow to authenticate directly to them, or
> you need an additional authentication url (to get the ticket)?
You need the ticket, but we said that the keystone service (auth url, username
and password) are config values for the time being. Anyway in the future I
expect
these providers to be linked to their keystone service. E.g.:
id name username password url auth_provider tenant ...
1 keystone1 myusermypasshttp://keystone
2 glance1http://glance1 mytenant1
3 glance1http://glance1 mytenant2
4 quantum1 http://quantum 1 mytenant1
I expect quantum to be needing the tenant name too (as soon as it will be
integrated with keystone).
Given the username/password (created for the ovirt management), the user can
be added to the tenants (all the ones that the admin wants to consume) and
then ovirt will get the auth tokens with the relevant info, e.g. (pseudocode
with reference to the table above):
keystone = new Keystone("http://keystone";);
glance1_token = keystone.authenticate("myuser", "mypass", "mytenant1");
glance2_token = keystone.authenticate("myuser", "mypass", "mytenant2");
quantum1_token = glance1_token;
glance = new Glance("http://glance";, glance1_token);
glance.listImages();
--
Federico
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] unit tests failing
- Original Message - > From: "Federico Simoncelli" > To: "Ewoud Kohl van Wijngaarden" > Cc: "engine-devel" > Sent: Tuesday, January 29, 2013 4:45:43 PM > Subject: Re: [Engine-devel] unit tests failing > > - Original Message - > > From: "Ewoud Kohl van Wijngaarden" > > > > To: "Laszlo Hornyak" > > Cc: "Federico Simoncelli" , "engine-devel" > > > > Sent: Tuesday, January 29, 2013 4:36:35 PM > > Subject: Re: [Engine-devel] unit tests failing > > > > May I recommend git bisect? See http://lwn.net/Articles/317154/ or > > http://clock.co.uk/tech-blogs/git-bisect-simple-examples-and-automation > > as well. > > > > First you find a known BAD, for example master. Then you find a > > known > > GOOD (for example 100 commits ago in master: master~100). Then we > > can > > use a script to determine if it's good. I'm assuming mvn test will > > be > > sufficient, but maybe you can refine this to only test for a > > specific > > unit test. > > > > git bisect start BAD GOOD > > git bisect run mvn test > > > > Now it will do a binary search in your history trying to find the > > commit > > that broke mvn test. > > It's ff64900b7ae1b2d92e40bb290c61354d846d7d30 > I'm working on it as we speak. This is a quick fix: http://gerrit.ovirt.org/#/c/11510/ I'm sure there's a lot to improve, please review it so we can push it as fast as we can. Thanks. -- Federico ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] unit tests failing
- Original Message - > From: "Ewoud Kohl van Wijngaarden" > To: "Laszlo Hornyak" > Cc: "Federico Simoncelli" , "engine-devel" > > Sent: Tuesday, January 29, 2013 4:36:35 PM > Subject: Re: [Engine-devel] unit tests failing > > May I recommend git bisect? See http://lwn.net/Articles/317154/ or > http://clock.co.uk/tech-blogs/git-bisect-simple-examples-and-automation > as well. > > First you find a known BAD, for example master. Then you find a known > GOOD (for example 100 commits ago in master: master~100). Then we can > use a script to determine if it's good. I'm assuming mvn test will be > sufficient, but maybe you can refine this to only test for a specific > unit test. > > git bisect start BAD GOOD > git bisect run mvn test > > Now it will do a binary search in your history trying to find the > commit > that broke mvn test. It's ff64900b7ae1b2d92e40bb290c61354d846d7d30 I'm working on it as we speak. -- Federico ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] unit tests failing
I'll need to fix those tests, sorry. Working on it right now. -- Federico - Original Message - > From: "Alon Bar-Lev" > To: "engine-devel" , "Federico Simoncelli" > , "Ofri Masad" > > Sent: Tuesday, January 29, 2013 3:53:36 PM > Subject: unit tests failing > > Don't know what change exactly caused this: > > Tests in error: > canDoActionInvalidVmStatus(org.ovirt.engine.core.bll.MoveDisksCommandTest) > moveDisk(org.ovirt.engine.core.bll.MoveDisksCommandTest) > liveMigrateDisk(org.ovirt.engine.core.bll.MoveDisksCommandTest) > > liveMigrateDiskBasedOnTemplate(org.ovirt.engine.core.bll.MoveDisksCommandTest) > moveDiskAndLiveMigrateDisk(org.ovirt.engine.core.bll.MoveDisksCommandTest) > ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] 3.2 features for release notes
- Original Message - > From: "Itamar Heim" > To: "Cheryn Tan" > Cc: engine-devel@ovirt.org, "Federico Simoncelli" , > "Tomas Jelinek" , "Roy > Golan" , "Shahar Havivi" , "Frantisek > Kobzik" , "Arik > Hadas" , "Alona Kaplan" , "Igor > Lvovsky" , "Muli Salem" > , "Vojtech Szocs" , "Greg Padgett" > , "Doron Fediuck" > , oma...@redhat.com, "Moran Goldboim" > , "Daniel Erez" , > "Tal Nisan" , "Liron Aravot" , "Eli > Mesika" , "Yaniv > Bronheim" , "Juan Antonio Hernandez Fernandez" > , "Alon Bar-Lev" > , "Yair Zaslavsky" , a...@us.ibm.com, > "Shireesh Anjal" , > "Yaniv Dary" , "Michael Pasternak" > Sent: Thursday, January 24, 2013 4:30:07 PM > Subject: Re: [Engine-devel] 3.2 features for release notes > > On 23/01/2013 23:47, Cheryn Tan wrote: > > Hi all, > > > > I'm preparing the oVirt 3.2 release notes, starting with the > > features listed here: > > http://www.ovirt.org/OVirt_3.2_release-management#Features > > > > Can you please go through the list, and reply to this thread if: > > a) There are features being released for 3.2 which should be > > documented, but are not on the list; or > > b) Some of the planned features on this list are not being released > > for 3.2; or > > c) Some of the features on this list are being released for 3.2, > > but should not be documented. > > > > For features which aren't on the wiki, please send a short > > description or Bugzilla numbers of each feature. > > > > Please reply no later than Jan 28. > > > > Thank you very much for your help! > > Cheryn > > ___ > > Engine-devel mailing list > > Engine-devel@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/engine-devel > > > > I think most of these made it to 3.2, i'll point fingers at others to > give more details... (doesn't mean others weren't involved in them, > just > picked someone to give the details for release notes). > > SSIA: > Add support for Opteron G5 (Seoul) > Add Support for Intel Haswell CPU > windows 8/12 - add os type > windows 8/12 - default in user portal should be rdp > (till we have spice support...) > expand tree by default with list of DCs > > federico: > storage live migration I think that we should also advertise domain V3 (live upgrade) and live snapshots (I think they weren't present in ovirt-3.1 iirc) -- Federico ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] New Fedora VDSM Build?
- Original Message - > From: "Dan Kenigsberg" > To: "Ofer Schreiber" > Cc: "Federico Simoncelli" , engine-devel@ovirt.org, > "Saggi Mizrahi" > Sent: Tuesday, June 26, 2012 1:21:09 PM > Subject: Re: New Fedora VDSM Build? > > On Tue, Jun 26, 2012 at 06:57:45AM -0400, Ofer Schreiber wrote: > > - Original Message - > > > On Tue, Jun 26, 2012 at 05:53:56AM -0400, Ofer Schreiber wrote: > > > > Any updates about $topic? > > > > > > Federico is herding sheep in Scotland right now. > > > Saggi is his second-in-command. > > > > > > Currently, there ore nly 2 patches on top of Fedrico latest build > > > https://koji.fedoraproject.org/koji/buildinfo?buildID=327015 > > > > Did you fixed the bootstrap? > > If yes, I'd like to get a new build, so people will be able to > > install VDSM. > > bootstrap fixes are in the above-mentioned build -2. (But there > should be another one regarding kernel version. I could use some help > understanding why douglas cannot verify > http://gerrit.ovirt.org/#/c/5637/ ) FYI, for other reasons (related to koji) I had to make another build and since I was at it I added BZ#832577 and BZ#824298: http://koji.fedoraproject.org/koji/buildinfo?buildID=327730 * Tue Jun 26 2012 Federico Simoncelli 4.10.0-3.fc17 - BZ#832577: node can't be approved - BZ#824298 fix typo in keyword argument exc_info You can ignore it if it's not fixing anything that you care about. -- Federico ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
