Re: [ovirt-devel] [oVirt 3.6 Localization Question #19] The selected proxy Host must be in the destination Storage Pool

2015-06-22 Thread Eli Mesika


- Original Message -
 From: Yuko Katabami ykata...@redhat.com
 To: devel@ovirt.org
 Sent: Monday, June 22, 2015 4:47:13 PM
 Subject: [ovirt-devel] [oVirt 3.6 Localization Question #19] The selected 
 proxy Host must be in the destination
 Storage Pool
 
 Hello again,
 
 Here is another question,
 
 File: AppErrors
 Resource ID: ACTION_TYPE_FAILED_VDS_NOT_IN_DEST_STORAGE_POOL
 String: Cannot ${action} ${type}. The selected proxy Host must be in the
 destination Storage Pool.
 Question: In my language, translation for the word destination may have to
 be changed depending on the action (i.e. migrate, move, import/export, copy,
 clone etc).
 What action is applicable in this case?

This error is raised when trying to import a VM from an external provider, so , 
the action is : import 

 
 Thank you,
 
 Yuko
 
 ___
 Devel mailing list
 Devel@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/devel
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel


[ovirt-devel] [oVirt 3.6 Localization Question #20] Add new Label to

2015-06-22 Thread Yuko Katabami
Hi,

I would like to ask you another question.
*
File:***UIConstants
*Resource ID:***newLabel
*String:***Add new Label to
*Question: *Could anyone tell me how / where this string appears in the
GUI? In Japanese translation, order of the words is different from
English, and I would like to make sure it works when it is shown on the
screen.

Kind regards,

Yuko* 
*
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [oVirt 3.6 Localization Question #20] Add new Label to

2015-06-22 Thread Yuko Katabami
I also found a similar string Add Label {0} to in UIMessages file.
Could anyone explain how/where this appears in the GUI as well?

Kind regards,

Yuko

On 06/23/2015 09:05 AM, Yuko Katabami wrote:
 Hi,

 I would like to ask you another question.
 *
 File:***UIConstants
 *Resource ID:***newLabel
 *String:***Add new Label to
 *Question: *Could anyone tell me how / where this string appears in
 the GUI? In Japanese translation, order of the words is different from
 English, and I would like to make sure it works when it is shown on
 the screen.

 Kind regards,

 Yuko* 
 *


 ___
 Devel mailing list
 Devel@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/devel


___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [oVirt 3.6 Localization Question #19] The selected proxy Host must be in the destination Storage Pool

2015-06-22 Thread Yuko Katabami
Hi Eli,

Thank you very much for your answer.
I will apply that to my translation.

Kind regards,

Yuko

On 06/23/2015 02:05 AM, Eli Mesika wrote:

 - Original Message -
 From: Yuko Katabami ykata...@redhat.com
 To: devel@ovirt.org
 Sent: Monday, June 22, 2015 4:47:13 PM
 Subject: [ovirt-devel] [oVirt 3.6 Localization Question #19] The selected 
 proxy Host must be in the destination
 Storage Pool

 Hello again,

 Here is another question,

 File: AppErrors
 Resource ID: ACTION_TYPE_FAILED_VDS_NOT_IN_DEST_STORAGE_POOL
 String: Cannot ${action} ${type}. The selected proxy Host must be in the
 destination Storage Pool.
 Question: In my language, translation for the word destination may have to
 be changed depending on the action (i.e. migrate, move, import/export, copy,
 clone etc).
 What action is applicable in this case?
 This error is raised when trying to import a VM from an external provider, so 
 , the action is : import 

 Thank you,

 Yuko

 ___
 Devel mailing list
 Devel@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/devel


___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] [oVirt 3.6 Localization Question #17] unified affinity group

2015-06-22 Thread Yuko Katabami
Hello all,

I am currently updating the oVirt 3.6 UI translations with other
translators and would like to ask you the following question:
*
File:*** ApplicationConstants
*Resource ID:***ACTION_TYPE_FAILED_AFFINITY_RULES_COLLISION
*String:*** Affinity Group collision detected in unified affinity group:
${UnifiedAffinityGroups}
and negative affinity group:
${negativeAR}
*Question: *Is unified affinity group referring to positive affinity
group? (the term is used in http://www.ovirt.org/Features/VM-Affinity
and a check box in the New/Edit Affinity Group window)
Is this error message is shown when there is a conflict between unified
(positive?) affinity group and negative affinity group is found?

Thanks in advance,

Yuko Katabami
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [oVirt 3.6 Localization Question #17] unified affinity group

2015-06-22 Thread Roy Golan

On 06/22/2015 01:56 PM, Yuko Katabami wrote:

Hello all,

I am currently updating the oVirt 3.6 UI translations with other 
translators and would like to ask you the following question:

*
File:*** ApplicationConstants
*Resource ID:***ACTION_TYPE_FAILED_AFFINITY_RULES_COLLISION
*String:*** Affinity Group collision detected in unified affinity group:
${UnifiedAffinityGroups}
and negative affinity group:
${negativeAR}
*Question: *Is unified affinity group referring to positive 
affinity group? (the term is used in 
http://www.ovirt.org/Features/VM-Affinity and a check box in the 
New/Edit Affinity Group window)
Is this error message is shown when there is a conflict between 
unified (positive?) affinity group and negative affinity group is found?


Yes. And unification is something we do behind the scene to help us 
validate that. So I don't think using 'unified' is adding value to the 
user.


Thanks in advance,

Yuko Katabami


___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel


___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [oVirt 3.6 Localization Question #17] unified affinity group

2015-06-22 Thread Yuko Katabami


On 06/22/2015 09:02 PM, Roy Golan wrote:
 On 06/22/2015 01:56 PM, Yuko Katabami wrote:
 Hello all,

 I am currently updating the oVirt 3.6 UI translations with other
 translators and would like to ask you the following question:
 *
 File:*** ApplicationConstants
 *Resource ID:***ACTION_TYPE_FAILED_AFFINITY_RULES_COLLISION
 *String:*** Affinity Group collision detected in unified affinity group:
 ${UnifiedAffinityGroups}
 and negative affinity group:
 ${negativeAR}
 *Question: *Is unified affinity group referring to positive
 affinity group? (the term is used in
 http://www.ovirt.org/Features/VM-Affinity and a check box in the
 New/Edit Affinity Group window)
 Is this error message is shown when there is a conflict between
 unified (positive?) affinity group and negative affinity group is found?

 Yes. And unification is something we do behind the scene to help us
 validate that. So I don't think using 'unified' is adding value to the
 user.
Hi Roy,

Thank you very much for your help.

Kind regards,

Yuko

 Thanks in advance,

 Yuko Katabami


 ___
 Devel mailing list
 Devel@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/devel



___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] Get involved in oVirt project! Summer edition

2015-06-22 Thread Sandro Bonazzola
Hi,
Summer is here and vacations are near! Have you got some free time and do 
you want to get involved in oVirt project?

Do you like the idea of having fresh disk images of recent distribution in 
oVirt Gluster repository?
You can help us by testing existing online images (like 
https://getfedora.org/en/cloud/download/) ensuring they works with cloud-init
or creating one yourself and report your success to devel@ovirt.org.
We'll be happy to upload the images once these are ready.


Do you like Debian and do you have some programming skill?
Help us getting VDSM running on it! Debian Jessie has been released a couple of 
weeks ago and it's a good time for giving it a try.
You can follow the progress here: http://www.ovirt.org/VDSM_on_Debian

Here are some bugs you can hopefully fix in less that one day or you can just 
try to reproduce providing info:

Bug ID  Status  Whiteboard  Summary
1065350 POSTintegration hosted-engine should prompt a question 
at the user when the host was already a host in the engine
1059952 NEW integration hosted-engine --deploy (additional 
host) will fail if the engine is not using the default self-signed CA
1083104 ASSIGNEDintegration engine-setup --offline does not update 
versionlock
1221176 NEW integration hosted-engine accepts FQDNs with 
underscore while the engine correctly fails on that
1200948 NEW integration hosted-engine-setup should validate the 
network interface name

Do you want something easier?

Bug ID  Whiteboard  Status  Summary
1174285 i18nNEW [de-DE] Live Snapshot Support reads Live 
Snapsnot Support
772931  infra   NEW [RFE] Reports should include the name of the 
oVirt engine
1143817 integration NEW [TEXT ONLY] - Hosted Engine - Instructions for 
FQDN are not clear enough
1156060 integration NEW [text] engine admin password prompt consistency
1115059 network NEW Incomplete error message when adding VNIC 
profile to running VM
734120  storage NEW [RFE] VDSM: use virt-sparsify/zerofree to 
reduce image size


Do you love DevOps?, you count stable builds in jenkins ci while trying to 
fall a sleep?
Then oVirt infra team is looking for you!, join the infra team and dive in to 
do the newest and coolest devops tools today!
Here are some of our open tasks you can help with: 
https://ovirt-jira.atlassian.net/secure/RapidBoard.jspa?rapidView=1projectKey=OVIRT


You don't have programming skills, not enough time for DevOps but you want 
still to contribute?
Here are some bugs you can take care of, also without writing a line of code:
https://bugzilla.redhat.com/buglist.cgi?quicksearch=product%3Aovirt%20whiteboard%3Adocs

Do you prefer to test things? We have some test cases[5] you can try using 
nightly snapshots[6].
You may also help testing: Bug 1234257 - Test upgrade path from EL6 with oVirt 
3.5.z to EL7


Do you want to contribute test cases? Most of the features[7] included in oVirt 
are missing a test case, you're welcome to contribute one!

Is this the first time you try to contribute to oVirt project?
You can start from here [1][2]!

You don't know gerrit very well? You can find some more docs here [3].

Any other question about development? Feel free to ask on devel@ovirt.org or on 
irc channel[4].

You don't really have time / skills for any development / documentation / 
testing related task?
Spread the word[8]!

Let us know you're getting involved, present yourself and tell us what you're 
going to do, you'll be welcome!

[1] http://www.ovirt.org/Develop
[2] http://www.ovirt.org/Working_with_oVirt_Gerrit
[3] https://gerrit-review.googlesource.com/Documentation
[4] http://www.ovirt.org/Community
[5] http://www.ovirt.org/Category:TestCase
[6] http://www.ovirt.org/Install_nightly_snapshot
[7] http://www.ovirt.org/Category:Feature
[8] 
http://www.zdnet.com/article/how-much-longer-can-red-hats-ovirt-remain-covert/

-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel


[ovirt-devel] Reminder: Fedora 20 end of life on 2015-06-23

2015-06-22 Thread Sandro Bonazzola
Hi,
just a reminder that Fedora 20 end of life tomorrow[1].
We're still building rpms targeted to Fedora 20 and we still have servers 
running on Fedora 20 which won't receive security updates anymore.
Infra please consider to upgrade / re-provision servers / slaves this week.

Since oVirt 3.5 supports Fedora only up to Fedora 20 I think we'll have to 
continue building packages for it until 3.6 will be out.
For 3.6 I suggest to keep Fedora 20 builds until Wildfly support will be in.

[1] https://lists.fedoraproject.org/pipermail/announce/2015-May/003267.html

-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel


[ovirt-devel] [IMPORTANT] Re: Move to Jboss Wildfly - planned for Monday, June 22nd

2015-06-22 Thread Oved Ourfali
top-posting:

Running more in-depth tests, we found out that there is an issue with matrix 
parameters in the REST-API (see [1] for more details).

We are now trying to understand the cause for these issue, and also check 
whether there is a workaround or not.
If we won't resolve it soon we'll have to postpone the move to Wildfly until 
this gets resolved.

I'll keep you all posted.

Regards,
Oved

[1] For example, asking for only 2 VMs can be done via using the following 
resource URL
   http://engine:port/ovirt-engine/api/vms;max=2

- Original Message -
 From: Oved Ourfali ov...@redhat.com
 To: Roy Golan rgo...@redhat.com
 Cc: devel devel@ovirt.org
 Sent: Sunday, June 21, 2015 4:24:38 PM
 Subject: Re: [ovirt-devel] Move to Jboss Wildfly - planned for Monday, June 
 22nd
 
 
 
 - Original Message -
  From: Roy Golan rgo...@redhat.com
  To: Oved Ourfali ov...@redhat.com
  Cc: devel devel@ovirt.org
  Sent: Sunday, June 21, 2015 4:05:13 PM
  Subject: Re: [ovirt-devel] Move to Jboss Wildfly - planned for Monday, June
  22nd
  
  On 06/21/2015 03:21 PM, Oved Ourfali wrote:
  
   - Original Message -
   From: Roy Golan rgo...@redhat.com
   To: Oved Ourfali ov...@redhat.com, devel devel@ovirt.org
   Sent: Sunday, June 21, 2015 3:19:28 PM
   Subject: Re: [ovirt-devel] Move to Jboss Wildfly - planned for Monday,
   June 22nd
  
   On 06/18/2015 09:13 AM, Oved Ourfali wrote:
   Hi all!
  
   On Monday, June 22nd, 11:00 CET, we plan to drop JBoss 7.1 support in
   oVirt
   3.6 and move to Jboss WildFly 8.2
   (we're still doing final verifications, but it looks promising).
  
   This will allow us to support Fedora 22 properly, and in future
   versions
   to
   leverage some new and cool features.
  
   In addition, Jboss WildFly 8.2 works with OpenJDK 1.8 so you can easily
   use
   it for
   development on newer distributions where OpenJDK 1.7 is not available
   (Fedora 21 and 22, for example).
   May need a separate thread for that, but we will be able to code using
   JDK 8. its about time. jdk 8 was out April 2014.
  
   We will still work with JDK7 for downstream.
  
  this should go on a separate thread :)
  
   When the patch [1] is merged, you will need WildFly 8.2 to be able to
   develop
   oVirt engine 3.6. Please use following guideline and update your
   development
   environment:
  
   I. Using WildFly 8.2 for oVirt 3.6 development
  
  1. Enable ovirt-master-snapshot-static repository on your
  development
  machine
   [ovirt-master-snapshot-static]
   name=Latest oVirt master additional nightly snapshot
   
   baseurl=http://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/@DIST@$releasever/
   enabled=1
   skip_if_unavailable=1
   gpgcheck=0
  
 Please replace @DIST@ with fc for Fedora or el for
 Centos/RHEL
  
  2. Install WildFly packages:
   yum install ovirt-engine-wildfly ovirt-engine-wildfly-overlay
  
  3. Rebase your patches and build oVirt engine (assuming
  ~/ovirt-engine
  as
 destination)
   make install-dev
  
  5. Setup WildFly overlay (assuming ~/ovirt-engine as destination)
   echo
   
   ENGINE_JAVA_MODULEPATH=\/usr/share/ovirt-engine-wildfly-overlay/modules:\${ENGINE_JAVA_MODULEPATH}\
   \

   ~/ovirt-engine/etc/ovirt-engine/engine.conf.d/20-setup-jboss-overlay.conf
  
  6. Execute setup
   cd ~/ovirt-engine
   ./bin/engine-setup
  
  7. Start engine service
   cd ~/ovirt-engine
   ./share/ovirt-engine/services/ovirt-engine/ovirt-engine.py
   start
  
  
   II. Using JBoss 7.1.1 for 3.5 environment
   why would anyone want to do that?
  
   Bugs!
  
  only for out (last?) z stream which will be 3.5.4. other then that, its
  really the end.
  
 
 We might also have 3.5.5.
 
  Using JBoss 7.1.1 on 3.5 is still possible, by doing the following:
  
   1. Install JBoss 7.1.1 RPM from ovirt-master-snapshot-static repo
   using
yum install ovirt-engine-jboss-as
  
   2. Build oVirt engine 3.5 with your backported feature (assuming
  ~/ovirt-engine as destination)
make install-dev
   
   3. Execute setup
cd ~/ovirt-engine
./bin/engine-setup--jboss-home=/usr/share/ovirt-engine-jboss-as
  
   4. Start engine service
cd ~/ovirt-engine
./share/ovirt-engine/services/ovirt-engine/ovirt-engine.py
start
 
   Once merged, we will send an E-mail to make sure you're all aware, and
   that
   you can do the steps described above.
  
   We're here for any issue you might have (specifically Martin who is
   responsible for this effort, and myself).
   Don't hesitate to contact us for any issue, either by mail or irc
   (mperina
   or oved).
  
   Regards,
   Oved
  
   [1] https://gerrit.ovirt.org/40152
   

[ovirt-devel] [oVirt 3.6 Localization Question #18] Snapshots scheduled on volume

2015-06-22 Thread Yuko Katabami
Hello all,

I have another question I would like to ask:

*File:***LocalizedEnums
*Resource ID:***AuditLogType___GLUSTER_VOLUME_SNAPSHOT_SCHEDULED
*String:***Snapshots scheduled on volume
*Question: *This string can be interpreted in a few different ways.
Could anyone tell me which one of the following is the correct
interpretation?
1) Snapshots that are scheduled on the volume
2) Snapshots are scheduled on the volume
3) Snapshots have just been scheduled on the volume

Kind regards,

Yuko Katabami


___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] [oVirt 3.6 Localization Question #19] The selected proxy Host must be in the destination Storage Pool

2015-06-22 Thread Yuko Katabami
Hello again,

Here is another question,
*
File:***AppErrors
*Resource ID:***ACTION_TYPE_FAILED_VDS_NOT_IN_DEST_STORAGE_POOL
*String:***Cannot ${action} ${type}. The selected proxy Host must be in
the destination Storage Pool.
*Question: *In my language, translation for the word destination may
have to be changed depending on the action (i.e. migrate, move,
import/export, copy, clone etc).
What action is applicable in this case?

Thank you,

Yuko
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel