[OpenStack-I18n] [OpenStack-Infra] [I18n] Regarding Zanata upgrade plan to 3.9.6 with Xenial: Help is needed

Ian Y. Choi ianyrchoi at gmail.com
Sat Jan 14 02:57:13 UTC 2017

Clark Boylan wrote on 1/14/2017 6:31 AM:
> On Thu, Jan 12, 2017, at 02:36 PM, Ian Y. Choi wrote:
>> - I18n team completed tests with current Zanata (3.7.3) with Xenial [1],
>> but found one error
>>     mentioned in [2]. It seems that more memory size allocation for
>> Zanata with Java 8 is needed.
>>     Could you upgrade the memory size for translate-dev server first to
>> test again?
> How much memory do we think will be necessary? The current instance is
> an 8GB RAM instance. As long as we have quota for it, there should not
> be a problem redeploying on a bigger instance.
Regarding this, I have recently seen another Zanata server: 
https://translate.zanata.org/ already uses Zanata 3.9.6.

Alex, could you share how much memory is being used for this server?
(server memory size, jvm heap size, and so on). I think the server will 
use Java 8 (OS will be Fedora, right?).
It might provide good estimation of how much memory is needed for 
translate-dev and also translate (in future) with us I think.

>> - I remember that newer version of openstackid needs to be tested with
>> translate-dev.
>>     So I have just uploaded this patch:
>> https://review.openstack.org/#/c/419667/ .
>>     I18n team needs more tests, but I think it is a good time to change
>> to openstackid-dev for such testing.
>>     Please ping me after openstackid-dev test with translate-dev is
>> completed with no error :)
>> - On last I18n team meeting, I18n team recognized that the backup would
>> be so important.
>>     Is there more disks for such backup on translate-dev and
>> translate.o.o server?
>>     And the approach implementing like [3] looks quite a good idea I
>> think. Thanks, Frank!
> I have commented on this change. I would prefer we not backup the dev
> server and only backup the production server. We don't treat our dev
> servers as permanent or reliable installs as they may need to be
> reloaded for various reasons to aid development and testing. Also we
> should set up backups similar to how we do the other services (I left a
> comment on this change with a link to an example).
Thanks for kind comments, Clark! I have just read and I agree with your 

>> - Can I have root access to translate-dev and translate server?
> This is something that can be discussed with the infra team, typically
> we would give access to someone assisting with implementation to the
> -dev server while keeping the production server as infra-root only. I
> will make sure fungi sees this.
I agree with your thoughts and also fungi's comments mentioned in 
another thread :)

One additional thought I just want add for the consideration of this is 
that at least it would be much better
if at least one active I18n team member who assists the implementation, 
on-going upgrade and operational issues
(e.g., Zanata login is not working)  has the access to dev and 
production servers
with providing good insights on Zanata infra side with I18n team members.
Also, I expect more aligned communication between I18n team and Infra team.
To accomplish this, I would at least one I18n team member will have good 
insight on such as
understanding how Zanata deployment has implemented previously and 
seeing & analyzing server logs.
This one I18n member to tho such role should not be me, but 
unfortunately, it is difficult for me to find another relevant I18n team 
member now.

Now I would like to think more on it and also discuss with I18n team 
members, and then ask again if my thoughts will come up
(Or I may need more discussion with infra team members during PTG).

With many thanks,


> Hope this helps,
> Clark

More information about the OpenStack-I18n mailing list