<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Alex Eng wrote on 11/23/2016 5:12 PM:<br>
</div>
<blockquote
cite="mid:CANY9q5Bf_H-ENLA3t75fpuR5R1Y81mwT7hYWJjX5Xe10NpD4zg@mail.gmail.com"
type="cite">
<div dir="ltr">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span
style="font-size:12.8px">One other thing that came up is do
we need to copy any files from the<br>
</span><span style="font-size:12.8px">old server to the new
server? Specifically it looks like portions of<br>
</span><span style="font-size:12.8px">`/home/wildfly/zanata`
may need to be preserved. Or is everything<br>
</span><span style="font-size:12.8px">important in the
database?</span></blockquote>
<div><br>
</div>
<div>The directory /home/wildfly/zanata will need to migrate
over to new server too. :) <br>
</div>
</div>
</blockquote>
More on Alex's comment from my asking:<br>
<br>
Zanata uses mysql database. <br>
There should be mysql configuration in standalone.xml to tell
you which DB it is using.<br>
<br>
<br>
With many thanks,<br>
<br>
/Ian<br>
<blockquote
cite="mid:CANY9q5Bf_H-ENLA3t75fpuR5R1Y81mwT7hYWJjX5Xe10NpD4zg@mail.gmail.com"
type="cite">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Nov 23, 2016 at 9:56 AM, Clark
Boylan <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:cboylan@sapwetik.org" target="_blank">cboylan@sapwetik.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed,
Nov 9, 2016, at 09:49 AM, Ian Y. Choi wrote:<br>
> Hello,<br>
><br>
> I18n team currently uses Zanata in <a
moz-do-not-send="true"
href="http://translate.openstack.org" rel="noreferrer"
target="_blank">translate.openstack.org</a> so frequently<br>
> as an OpenStack translation platform.<br>
> I really appreciate great help from all contributors,
especially infra<br>
> team members and Zanata development team<br>
> :<br>
> <a moz-do-not-send="true"
href="http://specs.openstack.org/openstack-infra/infra-specs/specs/migrate_to_zanata.html"
rel="noreferrer" target="_blank">http://specs.openstack.org/<wbr>openstack-infra/infra-specs/<wbr>specs/migrate_to_zanata.html</a><br>
> .<br>
><br>
> Thanks to [1], the current deployed Zanata version is
3.7.3.<br>
> During about one year, there were some discussions for
Zanata<br>
> enhancements in many i18n IRC meetings,<br>
> and especially Austin & Barcelona summits [2].<br>
> Zanata development team members kindly listen to such
enhancements, and<br>
> they are actively upgrading Zanata<br>
> with fixing bugs and incorporating cool features, which
are very helpful<br>
> for translators.<br>
><br>
> One main obstacle for upgrading Zanata (as far as I
know) was that newer<br>
> versions of Zanata requires Java 8,<br>
> but it is not default on Trusty. To upgrade Zanata,
upgrading from<br>
> Trusty to Xenial for <a moz-do-not-send="true"
href="http://translate.openstack.org" rel="noreferrer"
target="_blank">translate.openstack.org</a> is needed<br>
> since default-jre-headless on Trusty is Java 7 and
Xenial is Java 8.<br>
><br>
> Recently [3] has been merged, so I really hope that
i18n team will see<br>
> newer version of Zanata soon :)<br>
><br>
> I18n team discussed Zanata upgrade with pleia2 and
clarkb during i18n<br>
> Barcelona meetup (See number 4 in [4]),<br>
> and the following is my thoughts on appropriate
procedures to support<br>
> Zanata latest version<br>
> (Currently 3.9.6 - [5]):<br>
><br>
> 1. Xenial OS test for <a moz-do-not-send="true"
href="http://translate-dev.openstack.org" rel="noreferrer"
target="_blank">translate-dev.openstack.org</a><br>
> : IMO after tests from infra team, [6] will be changed
from "# Node-OS:<br>
> trusty" to "# Node-OS: xenial"<br>
><br>
> 2. Using openstackid instead of openstackid-dev for
translators to test<br>
> translate-dev.o.o<br>
> : I uploaded a patch [7].<br>
><br>
> 3. Uploading a patch on openstack-infra/puppet-zanata
for Zanata 3.9.6<br>
> : [8] is a reference for previous upgrade from Zanata
3.7.2 to 3.7.3<br>
><br>
> 4. translate-dev.o.o with Zanata 3.9.6 will be ready
=> I18n translators<br>
> will test it :)<br>
><br>
> 5. If there will be no error for Zanata 3.9,6, then
node upgrade from<br>
> Trusty to Xenial and Zanata upgrade to 3.9.6<br>
> is needed for <a moz-do-not-send="true"
href="http://translate.openstack.org" rel="noreferrer"
target="_blank">translate.openstack.org</a><br>
> : changing [9] line and also proposing a patch similar
to [10] will be<br>
> needed later.<br>
><br>
><br>
> Since newer version of Zanata is what translators are
expecting a lot :)<br>
> ,<br>
> I would like to kindly ask infra team members for the
help of reviewing<br>
> and accomplishing such steps with higher priority.<br>
><br>
> @clarkb, would the proposed procedures cover all the
things regarding<br>
> Zanata upgrade?<br>
> If yes, would you share a sort of scheduled plans?<br>
> IMO Zanata development team will kindly help following
schedules if<br>
> there will be some issues which are dependent to Zanata
itself.<br>
><br>
><br>
> [1] <a moz-do-not-send="true"
href="https://review.openstack.org/#/c/240383/"
rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/240383/</a><br>
> [2] <a moz-do-not-send="true"
href="https://etherpad.openstack.org/p/I18n-Zanata-enhancement"
rel="noreferrer" target="_blank">https://etherpad.openstack.<wbr>org/p/I18n-Zanata-enhancement</a><br>
> [3] <a moz-do-not-send="true"
href="https://review.openstack.org/#/c/384239/"
rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/384239/</a><br>
> [4] <a moz-do-not-send="true"
href="https://etherpad.openstack.org/p/barcelona-i18n-meetup"
rel="noreferrer" target="_blank">https://etherpad.openstack.<wbr>org/p/barcelona-i18n-meetup</a><br>
> [5] <a moz-do-not-send="true"
href="https://github.com/zanata/zanata-platform/releases"
rel="noreferrer" target="_blank">https://github.com/zanata/<wbr>zanata-platform/releases</a><br>
> [6]<br>
> <a moz-do-not-send="true"
href="http://git.openstack.org/cgit/openstack-infra/system-config/tree/manifests/site.pp#n1282"
rel="noreferrer" target="_blank">http://git.openstack.org/cgit/<wbr>openstack-infra/system-config/<wbr>tree/manifests/site.pp#n1282</a><br>
> [7] <a moz-do-not-send="true"
href="https://review.openstack.org/#/c/393405/"
rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/393405/</a><br>
> [8] <a moz-do-not-send="true"
href="https://review.openstack.org/#/c/239617/1/manifests/init.pp"
rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/239617/1/manifests/init.pp</a><br>
> [9]<br>
> <a moz-do-not-send="true"
href="http://git.openstack.org/cgit/openstack-infra/system-config/tree/manifests/site.pp#n1257"
rel="noreferrer" target="_blank">http://git.openstack.org/cgit/<wbr>openstack-infra/system-config/<wbr>tree/manifests/site.pp#n1257</a><br>
> [10] <a moz-do-not-send="true"
href="https://review.openstack.org/#/c/232313/"
rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/232313/</a><br>
<br>
Just a quick status update on this. I have updated puppet
things so that<br>
we can deploy <a moz-do-not-send="true"
href="http://translate-dev01.openstack.org"
rel="noreferrer" target="_blank">translate-dev01.openstack.org</a>
on Xenial then CNAME<br>
<a moz-do-not-send="true"
href="http://translate-dev.openstack.org" rel="noreferrer"
target="_blank">translate-dev.openstack.org</a> to it.
(This is part of how we are trying to<br>
deploy services in the future to avoid being tied to a
single instance<br>
in our puppetry). This includes running the noop puppet
apply test<br>
against Xenial for these nodes on puppet changes as well.<br>
<br>
All of that has gone relatively well and I just tried to
deploy on<br>
Xenial and have run into a few problems. The puppet output
[11] shows<br>
that the service isn't installed properly on Ubuntu Xenial.
Looking at<br>
the puppet-wildfly module [12] it doesn't appear to support
systemd on<br>
debuntu yet. Due to the upcoming thanksgiving holiday I
doubt I will get<br>
around to updating and testing that this week, so would be
great if<br>
someone else is able to work with the puppet-wildfly
upstream to fix<br>
this.<br>
<br>
One other thing that came up is do we need to copy any files
from the<br>
old server to the new server? Specifically it looks like
portions of<br>
`/home/wildfly/zanata` may need to be preserved. Or is
everything<br>
important in the database?<br>
<br>
In any case once the wildfly puppetry is working I think the
next step<br>
is to upgrade zanata to 3.9.6, change the openid server, and
have the<br>
team test it. Once that looks good its on to the production
server.<br>
<br>
[11] <a moz-do-not-send="true"
href="http://paste.openstack.org/show/590149/"
rel="noreferrer" target="_blank">http://paste.openstack.org/<wbr>show/590149/</a><br>
[12]<br>
<a moz-do-not-send="true"
href="https://github.com/biemond/biemond-wildfly/blob/master/manifests/service.pp#L35-L46"
rel="noreferrer" target="_blank">https://github.com/biemond/<wbr>biemond-wildfly/blob/master/<wbr>manifests/service.pp#L35-L46</a><br>
<br>
Thanks,<br>
Clark<br>
<br>
______________________________<wbr>_________________<br>
OpenStack-Infra mailing list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-Infra@lists.openstack.org">OpenStack-Infra@lists.<wbr>openstack.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra"
rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-infra</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">Alex
Eng<br>
<br>
</div>
</div>
</blockquote>
<p><br>
</p>
</body>
</html>