[Engine-devel] oVirt 3.3 Release Go/No-Go meeting
by Ofer Schreiber
------=_Part_4569047_2100528860.1377502424350
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
The following is a new meeting request:
Subject: oVirt 3.3 Release Go/No-Go meeting
Organizer: "Ofer Schreiber" <oschreib(a)redhat.com>
Location: #ovirt IRC channel @oftc
Time: Tuesday, August 27, 2013, 4:00:00 PM - 4:30:00 PM GMT +02:00 Jerusalem
Invitees: engine-devel(a)ovirt.org; users(a)ovirt.org
*~*~*~*~*~*~*~*~*~*
oVirt 3.3 Release Go/No-Go meeting
------=_Part_4569047_2100528860.1377502424350
Content-Type: text/calendar; charset=utf-8; method=REQUEST; name=meeting.ics
Content-Transfer-Encoding: 7bit
BEGIN:VCALENDAR
PRODID:Zimbra-Calendar-Provider
VERSION:2.0
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:Asia/Jerusalem
BEGIN:STANDARD
DTSTART:16010101T020000
TZOFFSETTO:+0200
TZOFFSETFROM:+0300
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=1SU
TZNAME:IST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T020000
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-
devel(a)ovirt.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:users@o
virt.org
ORGANIZER;CN=Ofer Schreiber:mailto:oschreib@redhat.com
DTSTART;TZID="Asia/Jerusalem":20130827T160000
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" <oschreib(a)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\; users(a)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
------=_Part_4569047_2100528860.1377502424350--
11 years, 3 months
[Engine-devel] repository closure status
by Sandro Bonazzola
Hi,
3.3.0 general availability is scheduled for: 2013-08-28
I've just checked repositories closure, here is the result:
nightly Fedora 18:
# repoclosure -l fedora -l updates -l updates-testing -r ovirt-nightly
Reading in repository metadata - please wait....
Checking Dependencies
Repos looked at: 4
fedora
ovirt-nightly
updates
updates-testing
Num Packages in Repos: 61537
package: ovirt-hosted-engine-setup-0.0.0-0.0.master.fc18.noarch from ovirt-nightly
unresolved deps:
sanlock-python >= 0:2.8
sanlock >= 0:2.8
package: vdsm-4.12.0-63.gitc7fc753.fc18.x86_64 from ovirt-nightly
unresolved deps:
libvirt-daemon >= 0:1.0.2-1
package: vdsm-4.12.0-67.git978b0a4.fc18.x86_64 from ovirt-nightly
unresolved deps:
libvirt-daemon >= 0:1.0.2-1
package: vdsm-4.12.0-72.git8d05744.fc18.x86_64 from ovirt-nightly
unresolved deps:
libvirt-daemon >= 0:1.0.2-1
3.3 (RC) Fedora 18:
# repoclosure -l fedora -l updates -l updates-testing -r ovirt-3.3
Reading in repository metadata - please wait....
Checking Dependencies
Repos looked at: 4
fedora
ovirt-3.3
updates
updates-testing
Num Packages in Repos: 61421
package: vdsm-4.12.0-0.1.rc3.fc18.i686 from ovirt-3.3
unresolved deps:
python-ethtool >= 0:0.8-1
libvirt-daemon >= 0:1.0.2-1
package: vdsm-4.12.0-0.1.rc3.fc18.x86_64 from ovirt-3.3
unresolved deps:
python-ethtool >= 0:0.8-1
libvirt-daemon >= 0:1.0.2-1
nightly Fedora 19:
# repoclosure -l fedora -l updates -l updates-testing -r ovirt-nightly
Reading in repository metadata - please wait....
Checking Dependencies
Repos looked at: 4
fedora
ovirt-nightly
updates
updates-testing
Num Packages in Repos: 50256
package: ovirt-engine-reports-3.3.0-0.2.master.20130803235659.fc19.noarch from ovirt-nightly
unresolved deps:
jasperreports-server >= 0:4.7.0
3.3 (RC) Fedora 19 is ok.
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
11 years, 3 months
[Engine-devel] Proposal for new commit msg design for engine commits
by Eyal Edri
Hi,
You all probably know and familiar with 'ovirt-engine' git hook for commit msg template [1].
this helps understand the general area of the patch in the project but it lacks additional info that might
be valuable for scaling automatic tests in Jenkins CI.
Let me explain:
Infra team is working hard on expanding oVirt CI infrastructure and adding more tests in jenkins (per commit/patch).
Adding important meta-data per patch can significatly improve the ability to run specific tests for each patch/commit,
and not waste valuable resources on Jenkins jobs that are not relevant to the code in the patch.
So the idea is to add/expand current metadata per patch, in the form of: (either)
1. expanding current header template to include more data like 'network' , 'setup', 'tools', 'virt'
2. adding a new label with relevant tags for the patch, called e.g 'METADATA: network, rest, virt'
Jenkins jobs will then be able to parse that data and trigger only relevant jobs for it.
this can also allow us to add more jobs per patch, an option that is very problematic today considering the amount of
patches coming in to engine.
Once agreed on a format, we'll be able to add a git hook to verify the validity of the commit msg. (similar to bug-url).
if we're not 100% sure that the tags will cover all corner cases and we feel like we need to run the code on all jobs,
we can a nightly job to run all the remaining jobs (but at least it won't run on every patch/commit).
[1] <core | restapi | tools | history | engine | userportal | webadmin>:
thoughts?
Eyal Edri.
11 years, 3 months
[Engine-devel] Feedback/ input needed on Host power management
by Malini Rao
Hello all,
In taking a look at the current implementation of Hosts> Power management, we have come up with a couple of approaches on improving this from a UX perspective -http://www.ovirt.org/Talk:Community#UXD_Proposals_for_Host_Power_management. We want your thoughts and input on what approach makes more sense from a user's perspective before fine tuning the UI.
Thanks
Malini
User Experience designer
11 years, 3 months
[Engine-devel] Issues with IBM POWER support in oVirt engine
by Vitor de Lima
--_000_B2CAFC4D5E2D574A883EF61ACD5ADE330180A712SERV070corpeldo_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi everyone,
I wrote some code to run a VM on a IBM POWER host, but I stumbled in some i=
ssues that will need a little bit of refactoring in the current code and I =
would like some feedback.
The first issue is that KVM on POWER requires a special SCSI interface (cal=
led SPAPR), which is not available in x86-64. Currently I'm solving this pr=
oblem by using (in the VmInfoBuilder class):
if (vm.getArchitecture().equals(ArchitectureType.ppc64)) {
Map<String, Object> struct =3D new HashMap<String, Object>();
struct.put(VdsProperties.Type, VmDeviceType.CONTROLLER.getName(=
));
struct.put(VdsProperties.Device, VdsProperties.Scsi);
// Create a controller in the index 1, the VirtIO_SCSI interface=
is in index 0
struct.put(VdsProperties.Index, "1");
Map<String, String> spaprAddress =3D new HashMap<String, String=
>();
spaprAddress.put("type", "spapr-vio");
struct.put(VdsProperties.Address, spaprAddress);
devices.add(struct);
}
But this is a poor solution, because this class would be polluted by archit=
ectural differences. Another thing to notice is that since in IBM POWER the=
re are two SCSI controllers, all the SCSI devices must have their SCSI addr=
ess explicitly defined (it was not needed before, since there was just one =
controller before). It was proposed that a "strategy" class could solve the=
problem, but I would like to have some feedback on which package it should=
be, since it will also be used in the bll package to validate other stuff.
The second issue is that the CD-ROM interface is SCSI on POWER guests (and =
must be attached to the SPAPR interface) and IDE on the x86_64, this inform=
ation could be retrieved from the osinfo (by creating a property there) or =
It could be hard-coded in the strategy class.
Which would be the best way to handle this difference?
The third and final issue is that when the VNC protocol is used in a VM, by=
default a Cirrus Logic VGA device is created. This device is not supported=
on POWER guests, but the standard VGA device is. I made a workaround, but =
the issue is where to put this association between the device type and the =
display protocol.
Should it also be a property in the osinfo? Or it should be handled in the =
strategy class?
--_000_B2CAFC4D5E2D574A883EF61ACD5ADE330180A712SERV070corpeldo_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"PT-BR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi everyone,<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I wrote some code to run a VM o=
n a IBM POWER host, but I stumbled in some issues that will need a little b=
it of refactoring in the current code and I would like some feedback.<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The first issue is that KVM on =
POWER requires a special SCSI interface (called SPAPR), which is not availa=
ble in x86-64. Currently I’m solving this problem by using (in the Vm=
InfoBuilder class):<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">if (vm.getArchitecture().equals=
(ArchitectureType.ppc64)) {<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"> &=
nbsp; Map<String, Object> struct =3D new=
HashMap<String, Object>();<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"> &=
nbsp; struct.put(VdsProperties.Type, VmDevice=
Type.CONTROLLER.getName());<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"> &=
nbsp; struct.put(VdsProperties.Device, VdsPro=
perties.Scsi);<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"> &=
nbsp; // Create a controller in the index 1, the Vi=
rtIO_SCSI interface is in index 0<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"> &=
nbsp; struct.put(VdsProperties.Index, "1=
");<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"> &=
nbsp; Map<String, String> spaprAddress =
=3D new HashMap<String, String>();<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"> &=
nbsp; spaprAddress.put("type", &quo=
t;spapr-vio");<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"> &=
nbsp; struct.put(VdsProperties.Address, spapr=
Address);<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"> &=
nbsp; devices.add(struct);<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">}<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">But this is a poor solution, be=
cause this class would be polluted by architectural differences. Another th=
ing to notice is that since in IBM POWER there are two SCSI controllers, al=
l the SCSI devices must have their SCSI
address explicitly defined (it was not needed before, since there was just=
one controller before). It was proposed that a “strategy” clas=
s could solve the problem, but I would like to have some feedback on which =
package it should be, since it will also be
used in the bll package to validate other stuff.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The second issue is that the CD=
-ROM interface is SCSI on POWER guests (and must be attached to the SPAPR i=
nterface) and IDE on the x86_64, this information could be retrieved from t=
he osinfo (by creating a property there)
or It could be hard-coded in the strategy class.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Which would be the best way to =
handle this difference?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The third and final issue is th=
at when the VNC protocol is used in a VM, by default a Cirrus Logic VGA dev=
ice is created. This device is not supported on POWER guests, but the stand=
ard VGA device is. I made a workaround,
but the issue is where to put this association between the device type and=
the display protocol.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Should it also be a property in=
the osinfo? Or it should be handled in the strategy class?<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p> </o:p></span></p>
</div>
</body>
</html>
--_000_B2CAFC4D5E2D574A883EF61ACD5ADE330180A712SERV070corpeldo_--
11 years, 3 months
Re: [Engine-devel] Jenkins job to run networking functional tests
by Eyal Edri
[adding devel lists]
Usually to get power user privileges you need get +1 community (mostly relevant people in your team/project).
saying you're familiar with jenkins and the project and is cabaple of adding jobs to the project.
I personally give +1 since i know you're contribution and experience.
Eyal.
----- Original Message -----
> From: "Giuseppe Vallarelli" <gvallare(a)redhat.com>
> To: "infra" <infra(a)ovirt.org>
> Sent: Monday, August 19, 2013 10:19:46 AM
> Subject: Jenkins job to run networking functional tests
>
> Hello everybody, following the previous discussion with Eyal,
> I need to get rights in order to create a jenkins job to
> achieve what stated in the subject.
>
> Is it the right place for such request?
>
> Cheers, Giuseppe
>
> ----- Forwarded Message -----
> | From: "Eyal Edri" <eedri(a)redhat.com>
> | To: "Giuseppe Vallarelli" <gvallare(a)redhat.com>
> | Cc: "infra" <infra(a)ovirt.org>
> | Sent: Sunday, August 18, 2013 2:06:22 PM
> | Subject: Re: running network functional tests
> |
> | Hi,
> |
> | Usually in these cases when a new job is requested to a specific
> | project/component,
> | A 'power user' for the relevant team (in your case network), is given
> | privileges on the Jenkins machine
> | to add any job required.
> |
> | I would propose the following:
> | 1. request power user access to jenkins.ovirt.org (if you don't already
> | have)
> | 2. add a new job with your functional test per commit (not per patch for
> | starts)
> | any infra member can assist you with the labels for slaves / os /etc...
> | 3. once that job is running properly, you can contact infra to assist in
> | converting it to a per-patch job
> | with the topic / field verification logic done.
> | 4. not sure if this is relevant to your tests, but all existing jenkins
> | slaves are VMs and not bare-metal.
> |
> | i hope this helps.
> |
> | Eyal.
> |
> | ----- Original Message -----
> | > From: "Giuseppe Vallarelli" <gvallare(a)redhat.com>
> | > To: "infra" <infra(a)ovirt.org>
> | > Sent: Friday, August 16, 2013 12:28:43 PM
> | > Subject: Fwd: running network functional tests
> | >
> | > ----- Forwarded Message -----
> | > | From: "Giuseppe Vallarelli" <gvallare(a)redhat.com>
> | > | To: "infra" <infra(a)ovirt.org>
> | > | Cc: "David Caro Estevez" <dcaroest(a)redhat.com>
> | > | Sent: Monday, August 12, 2013 10:58:04 AM
> | > | Subject: running network functional tests
> | > |
> | > | Hello everbody!
> | > | Just recently we added networking functional tests and we would like
> | > | to have them running when we submit patches network related, i.e.
> | > | going to affect network modules. Displaying success or failure
> | > | as it happens with the current unittests.
> | > |
> | > | Requirements/ideas:
> | > |
> | > | - OS Fedora 19/RHEL6.4 should not matter.
> | > |
> | > | - Kernel module used: bonding, dummy.
> | > |
> | > | - No more than one 'instance' of networkTests should run
> | > | on a specific host, simply because we use some global
> | > | constants to identify network name vlan id and so on.
> | > |
> | > | - Ideally we can use a previously proposed idea of commit tag
> | > | where for example @networking is provided in the commit msg
> | > | title to identify the need of running also the network
> | > | functional tests.
> | > |
> | > | - We should be able to run at the same time functional networking
> | > | tests and unit tests - I don't expect any conflicts.
> | > |
> | > | Would be cool to have a test run before -1s all networking patches
> | > | in case of problems :-)
> | > |
> | > | Let me know if more information are needed.
> | > |
> | > |
> | > | Cheers, Giuseppe
> | >
> | > Is there any update on the subject?
> | >
> | > Any estimate to have functional network tests running?
> | > I mind that we can run network functional tests upstream
> | > that will speed up our workflow and possibly decrease the
> | > regressions.
> | >
> | > Thanks Giuseppe
> | > _______________________________________________
> | > Infra mailing list
> | > Infra(a)ovirt.org
> | > http://lists.ovirt.org/mailman/listinfo/infra
> | >
> |
> _______________________________________________
> Infra mailing list
> Infra(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
11 years, 3 months
[Engine-devel] oVirt UI technology stack upgrade complete
by Vojtech Szocs
Hello everyone,
last week, we merged a patch that upgrades oVirt UI technology stack to use the latest version of Google Web Toolkit SDK and related modules [1]. This patch includes all "essential" upgrade changes as described in [2].
After merging the above mentioned patch, we faced some issues related to GWT RPC serialization, involving classes shared between frontend and backend. Please read on to learn more about these issues and ways to fix them.
--
(A) NullPointerException at server-side (GWT RPC servlet) when serializing backend business entity into RPC response payload
Symptoms
* exception in server.log -> Exception while dispatching incoming RPC call: java.lang.NullPointerException
* error dialog in web UI with status code 500 (internal server error)
Root cause
* fields such as "private X field = Y;" of the given entity are not included in GWT RPC serialization policy
* this happens when entity constructor isn't referenced in UI code -> GWT compiler marks the constructor and instance initializer as dead code
* since instance initializer takes care of adding such fields to given type (entity) in generated JavaScript, such fields won't be added at all
Workaround
* for each field such as "private X field = Y;"
1, change field declaration to "private X field;"
2, add "field = Y;" statement to constructor
Consequence
* even though constructor and instance initializer are marked as dead code, fields such as "private X field;" are still added to given type (entity) in generated JavaScript
* this is due to how generated JavaScript works, i.e. fields without initialization statement such as "private X field;" are always added, whereas fields with initialization statement such as "private X field = Y;" are added via instance initializer (which might be removed if it's marked as dead code)
References
* patch [http://gerrit.ovirt.org/#/c/17352/] for RepoImage entity
--
(B) Instance field(s) with null values at server-side after deserializing RPC request payload
Symptoms
* object passed from client contains field(s) with null values, despite client initializing fields before making RPC call
Root cause
* client uses RPC method signature that works with type A, i.e. VdcActionParametersBase
* type A meets GWT RPC serialization rules, as defined in [3] section "Serializable User-defined Classes"
* client uses type B (extends A) when calling given RPC method at runtime, i.e. MyCustomParameters
* type B does NOT meet GWT RPC serialization rules, i.e. missing no-arg constructor
* back at server-side, GWT RPC servlet fails to deserialize type B properly
Workaround
* ensure all types participating in GWT RPC communication meet GWT RPC serialization rules
1, assignable to IsSerializable or Serializable interface
2, all non-final & non-transient instance fields meet GWT RPC serialization rules
3, contains no-arg constructor (in order to create instance during deserialization)
References
* patch [http://gerrit.ovirt.org/#/c/17368/] for Gluster Parameter classes
--
Regards,
Vojtech
[1] http://gerrit.ovirt.org/#/c/16739/
[2] http://www.ovirt.org/Features/GWT_Platform_Upgrade
[3] http://www.gwtproject.org/doc/latest/DevGuideServerCommunication.html#Dev...
11 years, 3 months
[Engine-devel] Rebuild ovirt 3.2.1 success, but lost i18n support
by An Yang
--=-idC09TPR8Ct/GVyk0dLv
Content-Type: multipart/alternative; boundary="=-umgPw/+YnaaGimIE+IJT"
--=-umgPw/+YnaaGimIE+IJT
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hi all,
I just rebuild ovirt-engine 3.2.1 aaccording to
http://www.ovirt.org/Building_oVirt_engine , it work fine, but I could
not choose the language, it always display U.S. English UI.
Could you give me a hand, how can I enable GWT's i18n support, or
something is wrong in my building ENV?=20
Thanks in advance.
An Yang
--=-umgPw/+YnaaGimIE+IJT
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; CHARSET=3DUTF-8">
<META NAME=3D"GENERATOR" CONTENT=3D"GtkHTML/4.2.2">
</HEAD>
<BODY>
Hi all,<BR>
<BR>
I just rebuild ovirt-engine 3.2.1 aaccording to <A HREF=3D"http://www.ovirt=
.org/Building_oVirt_engine">http://www.ovirt.org/Building_oVirt_engine</A> =
, it work fine, but I could not choose the language, it always display U.S.=
English UI.<BR>
Could you give me a hand, how can I enable GWT's i18n support, or something=
is wrong in my building ENV? <BR>
<BR>
Thanks in advance.<BR>
An Yang
</BODY>
</HTML>
--=-umgPw/+YnaaGimIE+IJT--
--=-idC09TPR8Ct/GVyk0dLv
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAABAgAGBQJSEs0tAAoJEIzlWTTXdxmtmnYIAKlGCEvwHxNNYGeUSH/zPz6C
2CdDyDTzKtTY/L0+Di1Z1z/hwpxNdna18W/OCr9cFlcBwSXM9e9dC3F2FdvIOxFU
SL77W81PSJgsbaoYB7vfjA7mwDFxpzpp7n0mMgDPStoJZ5PSxWuRUl0ow5RGDBpk
ev7NAhEdpbNLlOrgIIkeYgBEfUZWyZXqodKUELqJ5rrF6Yy5W1M/sBWu4P42XCNc
ndwtkXwSnOEaWzoV4FOqtcf2x8oA69DG4Vor64YV030MsFlD2e902FbVwsEQ7BCq
pPpHmuGRmQlVt6hksZA4Pjus3J1LX040WmZAynfnx66jVUe5jS96+rj5wl6GB4I=
=4yAp
-----END PGP SIGNATURE-----
--=-idC09TPR8Ct/GVyk0dLv--
11 years, 3 months