[Engine-devel] oVirt 3.3 Release Go/No-Go meeting

2013-08-26 Thread Ofer Schreiber
BEGIN:VCALENDAR
PRODID:Zimbra-Calendar-Provider
VERSION:2.0
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:Asia/Jerusalem
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETTO:+0200
TZOFFSETFROM:+0300
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=1SU
TZNAME:IST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETTO:+0300
TZOFFSETFROM:+0200
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=-1FR
TZNAME:IDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:6765afcb-6f9d-4f37-af8f-df9f64b7e3f7
SUMMARY:oVirt 3.3 Release Go/No-Go meeting
LOCATION:#ovirt IRC channel @oftc
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:engine-
 de...@ovirt.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:users@o
 virt.org
ORGANIZER;CN=Ofer Schreiber:mailto:oschr...@redhat.com
DTSTART;TZID=Asia/Jerusalem:20130827T16
DTEND;TZID=Asia/Jerusalem:20130827T163000
STATUS:CONFIRMED
CLASS:PUBLIC
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
TRANSP:OPAQUE
LAST-MODIFIED:20130826T073344Z
DTSTAMP:20130826T073344Z
SEQUENCE:0
DESCRIPTION:The following is a new meeting request:\n\nSubject: oVirt 3.3 Re
 lease Go/No-Go meeting \nOrganizer: Ofer Schreiber oschr...@redhat.com \
 n\nLocation: #ovirt IRC channel @oftc \nTime: Tuesday\, August 27\, 2013\, 4
 :00:00 PM - 4:30:00 PM GMT +02:00 Jerusalem\n \nInvitees: engine-devel@ovirt
 .org\; us...@ovirt.org \n\n\n*~*~*~*~*~*~*~*~*~*\n\noVirt 3.3 Release Go/No-
 Go meeting
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


[Engine-devel] [oVirt/RHEV 3.3 Localization Question #16] Cannot change/edit item in tree context

2013-08-26 Thread Yuko Katabami

  
  
Hello all,


I would like to ask your help again with those strings:

File: uicompat.UIConstants
Resource IDs: 

cannotChangeClusterInTreeContext
cannotChangeDCInTreeContext
cannotChangeHostInTreeContext
cannotEditNameInTreeContext
Strings:

Cannot change Cluster in tree context
Cannot change Data Center in tree context
Cannot change Host in tree context
Cannot edit name in tree context

I have found this information (at
http://gerrit.ovirt.org/#/c/17886/): When a specific item (for
example, an actual host -- not "Hosts") is selected in the left-pane
tree, we need to disable editing the name of that item. 

Is this relevant to all of those strings?

If so, is my following interpretation correct?

Cannot change Cluster in tree context = Cannot change name of
the Cluster which is selected in the tree context

Cannot change Data Center in tree context= Cannot change the
name of the Data Center which is selected in the tree context

Cannot change Host in tree context= Cannot change the name of
the Host which is selected in the tree context

Cannot edit name in tree context= Cannot edit the name of an
item which is selected in the tree context


The current strings can be interpreted in several different ways and
we would like to have the above points clarified so that we can
translate them accurately.

Thank you,

Yuko
-- 
   Regards,


Yuko Katabami () 
Technical Translator II 
NAATI Accredited Professional Translator (English into Japanese)
#28138 
RHCSA #111-119-244 
Mobile: +61 415 847 352 
Email: ykata...@redhat.com 

 

Red Hat, Asia-Pacific Pty Ltd 
Level 1, 193 North Quay 
Brisbane 4000 
Office: +61 7 3514 8100 
Fax: +61 7 3514 8199 
Website: www.redhat.com


Facebook: Red Hat APAC | Red
  Hat Japan | Red Hat Korea | JBoss
  APAC 
Twitter: Red Hat APAC | Red
  Hat ANZ 
LinkedIn: Red Hat APAC | JBoss APAC
  

  

___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel


[Engine-devel] Opimizing Postgres Stored Procedures

2013-08-26 Thread Eli Mesika
Hi

I had merged the following patch 
http://gerrit.ovirt.org/#/c/17962/

This patch introduce usage of the IMMUTABLE, STABLE and STRICT keywords in 
order to boost performance of the Postgres SPs.

Please make sure that your current/and future DB scripts applied that.


Volatility
--
* A function should be marked as IMMUTABLE if it doesn't change the database, 
and if it doesn't perform any lookups (even for database configuration values) 
during its operation.
* A function should be marked STABLE if it doesn't change the database, but 
might perform lookups (IMMUTABLE is preferable if function meets the 
requirements).
* A function doesn't need to be marked VOLATILE, because that's the default.

STRICTNESS
--
A function should be marked STRICT if it should return NULL when it is passed a 
NULL argument, and then the function won't even be called if it is indeed 
passed a NULL argument.


I am available for any questions.

Thanks 

Eli
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel


Re: [Engine-devel] UI by-products of Neutron integration

2013-08-26 Thread Malini Rao

- Original Message -
 From: Lior Vernia lver...@redhat.com
 To: engine-devel engine-devel@ovirt.org
 Sent: Sunday, August 25, 2013 4:12:36 AM
 Subject: [Engine-devel] UI by-products of Neutron integration
 
 Hello everyone and specifically UI peeps,
 
 Just wanted to turn your attention to a couple of reusable UI components
 that have been introduced along with the 3.3 Neutron integration
 feature, and that might be of interest elsewhere.
 
 The most interesting of them are link columns to be used within
 EntityModelCellTable instances, that upon clicking enable one to jump
 to a different UI context by selecting a different entity in the system
 tree. I've attached a couple of screenshots that show how we've used it
 to quickly navigate from the context of a network provider to that of
 one of its imported networks.
 
 This could be useful wherever one might want to move quickly to a main
 tab context of an entity that is secondary in the current context. For
 example, say I just moved a storage domain to maintenance and now I
 would like to edit its properties - the domain name might be a good
 candidate to link to that storage domain item in the system tree.

Lior, this is a good interaction paradigm but it is good only if it is a 
consistent interaction paradigm. Based on my conversations with various users 
so far, I see some emerging issues on the way the system tree is perceived and 
also some of the confusions it is causing in people. Because of the way it is 
positioned prominently and permanently on the left, it looks like it drives the 
content on the left but that is not 'always' the case. Based on which main tab 
you are on and based on the level of granularity on the tree, the changes on 
the right change or sometimes only the search box updates. At some point, we 
should definitely look into trying to make the expectation between the tree and 
content more obvious and consistent and your approach seems to be pointing in 
the right direction - i.e, the tree should always reflect your current context 
on the right.

Having said that, I am not sure we should plug this interaction in as an 
additional variant in some places as the users will totally be lost as to what 
behavior will occur anytime they click a link or node.

If you guys are ready to look into this in a more holistic manner, Eldan and I 
will be more than willing to spend some time coming up with a proposal to share 
with you all and/or we will be open to ideas from all.


 
 The usage is pretty straightforward, the recipe is as follows:
 1. Add tree items that are potential targets to the map member in
 SystemTreeModel (map works by ID).
 2. Add LinkColumnWithTooltip to required table.
 3. Set the column's FieldUpdater to set the selected item of
 SystemTreeModelProvider according to the ID of the clicked EntityModel.
 
 Examples can be found in the following patches:
 http://gerrit.ovirt.org/#/c/15523/
 http://gerrit.ovirt.org/#/c/15524/
 
 A couple more components which might be useful:
 * HorizontalSplitTable comprises two tables separated horizontally, to
 be used in import/export situations.
 * ListModelListBoxColumn to be used with EntityModelCellTable, contains
 a list box that's linked to a ListModel.
 * EditTextColumnWithTooltip to be used with EntityModelCellTable,
 contains text that can be edited upon clicking.
 
 All three can be observed by navigating to the Networks main tab and
 clicking Import, examples for usage may be found in
 ImportNetworksModel and ImportNetworksPopupView.
 
 Lior.
 
 ___
 Engine-devel mailing list
 Engine-devel@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/engine-devel
 
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel


Re: [Engine-devel] DataIntegrityViolationException when creating a new template

2013-08-26 Thread Einav Cohen
indeed, http://gerrit.ovirt.org/#/c/18453/ did the trick.
[I still cannot create the template, but that's due to a slow and 
problematic storage - I no longer see the exception that I originally 
reported]

Many thanks for your help!


Regards,
Einav

- Original Message -
 From: Daniel Erez de...@redhat.com
 To: Einav Cohen eco...@redhat.com
 Cc: engine-devel engine-devel@ovirt.org
 Sent: Sunday, August 25, 2013 5:10:21 AM
 Subject: Re: [Engine-devel] DataIntegrityViolationException when creating a 
 new   template
 
 
 
 - Original Message -
  From: Liron Aravot lara...@redhat.com
  To: Omer Frenkel ofren...@redhat.com
  Cc: engine-devel engine-devel@ovirt.org
  Sent: Sunday, August 25, 2013 11:37:49 AM
  Subject: Re: [Engine-devel] DataIntegrityViolationException when creating a
  new template
  
  
  
  - Original Message -
   From: Omer Frenkel ofren...@redhat.com
   To: Einav Cohen eco...@redhat.com
   Cc: engine-devel engine-devel@ovirt.org
   Sent: Sunday, August 25, 2013 11:23:55 AM
   Subject: Re: [Engine-devel] DataIntegrityViolationException when creating
   a
   new   template
   
   
   
   - Original Message -
From: Einav Cohen eco...@redhat.com
To: engine-devel engine-devel@ovirt.org
Sent: Friday, August 23, 2013 10:54:07 PM
Subject: [Engine-devel] DataIntegrityViolationException when creating a
new
template

latest upstream, using development environment.
attempting to 'Make Template' results in an internal engine error
(see
attached screen-shot).

in engine.log, I see the following error:
org.springframework.dao.DataIntegrityViolationException:
CallableStatementCallback; SQL [{call insertvmdevice(?, ?, ?, ?, ?, ?,
?,
?,
?, ?, ?, ?)}]; ERROR: null value in column device_id violates
not-null
constraint
[see attached engine.log, look for the 2013-08-23 15:40:04 time-stamp
to
see
the initial invocation of AddVmTemplateCommand, error above appears in
2013-08-23 15:40:27]

ideas?
  
  Seems like there's already a bug for that -
  https://bugzilla.redhat.com/51
 
 As a quick workaround, detach the DirectLUN disks or apply:
 http://gerrit.ovirt.org/#/c/18453/
 

   
   did you remember to run setup in order to update your db?
   i just tried creating few templates and all worked ok
   
Thanks in advance.
  


Regards,
Einav Cohen Baum
RHEV-M Engineering - UX Team Manager
Red Hat, Inc.
314 Littleton Road
Westford, MA 01886
T [internal]: (81) 31046
T [external]: (+1) 978 589 1046
IRC: ecohen @
 - RHAT [internal]: #rhev-dev #boston #westford #tlv
 - OFTC [external]: #ovirt

___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel

   ___
   Engine-devel mailing list
   Engine-devel@ovirt.org
   http://lists.ovirt.org/mailman/listinfo/engine-devel
   
  ___
  Engine-devel mailing list
  Engine-devel@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/engine-devel
  
 ___
 Engine-devel mailing list
 Engine-devel@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/engine-devel
 
 
 
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel