On Wed, Dec 7, 2016, at 01:08 AM, Frank Kloeker wrote: > ----- Original Nachricht ---- > Von: Clark Boylan <cboy...@sapwetik.org> > An: "Ian Y. Choi" <ianyrc...@gmail.com>, OpenStack Infra > <openstack-infra@lists.openstack.org> > Datum: 03.12.2016 00:37 > Betreff: Re: [OpenStack-Infra] [I18n] Regarding Zanata upgrade plan to > 3.9.6 > with Xenial: Help is needed > > > On Tue, Nov 22, 2016, at 03:56 PM, Clark Boylan wrote: > > > On Wed, Nov 9, 2016, at 09:49 AM, Ian Y. Choi wrote: > > > > Hello, > > > > > > > > I18n team currently uses Zanata in translate.openstack.org so frequently > > > > > > as an OpenStack translation platform. > > > > I really appreciate great help from all contributors, especially infra > > > > team members and Zanata development team > > > > : > > > > > > http://specs.openstack.org/openstack-infra/infra-specs/specs/migrate_to_zana > > ta.html > > > > . > > > > > > > > Thanks to [1], the current deployed Zanata version is 3.7.3. > > > > During about one year, there were some discussions for Zanata > > > > enhancements in many i18n IRC meetings, > > > > and especially Austin & Barcelona summits [2]. > > > > Zanata development team members kindly listen to such enhancements, and > > > > > > they are actively upgrading Zanata > > > > with fixing bugs and incorporating cool features, which are very helpful > > > > > > for translators. > > > > > > > > One main obstacle for upgrading Zanata (as far as I know) was that newer > > > > > > versions of Zanata requires Java 8, > > > > but it is not default on Trusty. To upgrade Zanata, upgrading from > > > > Trusty to Xenial for translate.openstack.org is needed > > > > since default-jre-headless on Trusty is Java 7 and Xenial is Java 8. > > > > > > > > Recently [3] has been merged, so I really hope that i18n team will see > > > > newer version of Zanata soon :) > > > > > > > > I18n team discussed Zanata upgrade with pleia2 and clarkb during i18n > > > > Barcelona meetup (See number 4 in [4]), > > > > and the following is my thoughts on appropriate procedures to support > > > > Zanata latest version > > > > (Currently 3.9.6 - [5]): > > > > > > > > 1. Xenial OS test for translate-dev.openstack.org > > > > : IMO after tests from infra team, [6] will be changed from "# Node-OS: > > > > > > trusty" to "# Node-OS: xenial" > > > > > > > > 2. Using openstackid instead of openstackid-dev for translators to test > > > > > > translate-dev.o.o > > > > : I uploaded a patch [7]. > > > > > > > > 3. Uploading a patch on openstack-infra/puppet-zanata for Zanata 3.9.6 > > > > : [8] is a reference for previous upgrade from Zanata 3.7.2 to 3.7.3 > > > > > > > > 4. translate-dev.o.o with Zanata 3.9.6 will be ready => I18n translators > > > > > > will test it :) > > > > > > > > 5. If there will be no error for Zanata 3.9,6, then node upgrade from > > > > Trusty to Xenial and Zanata upgrade to 3.9.6 > > > > is needed for translate.openstack.org > > > > : changing [9] line and also proposing a patch similar to [10] will be > > > > needed later. > > > > > > > > > > > > Since newer version of Zanata is what translators are expecting a lot > > :) > > > > , > > > > I would like to kindly ask infra team members for the help of reviewing > > > > > > and accomplishing such steps with higher priority. > > > > > > > > @clarkb, would the proposed procedures cover all the things regarding > > > > Zanata upgrade? > > > > If yes, would you share a sort of scheduled plans? > > > > IMO Zanata development team will kindly help following schedules if > > > > there will be some issues which are dependent to Zanata itself. > > > > > > > > > > > > [1] https://review.openstack.org/#/c/240383/ > > > > [2] https://etherpad.openstack.org/p/I18n-Zanata-enhancement > > > > [3] https://review.openstack.org/#/c/384239/ > > > > [4] https://etherpad.openstack.org/p/barcelona-i18n-meetup > > > > [5] https://github.com/zanata/zanata-platform/releases > > > > [6] > > > > > > http://git.openstack.org/cgit/openstack-infra/system-config/tree/manifests/s > > ite.pp#n1282 > > > > [7] https://review.openstack.org/#/c/393405/ > > > > [8] https://review.openstack.org/#/c/239617/1/manifests/init.pp > > > > [9] > > > > > > http://git.openstack.org/cgit/openstack-infra/system-config/tree/manifests/s > > ite.pp#n1257 > > > > [10] https://review.openstack.org/#/c/232313/ > > > > > > Just a quick status update on this. I have updated puppet things so that > > > we can deploy translate-dev01.openstack.org on Xenial then CNAME > > > translate-dev.openstack.org to it. (This is part of how we are trying to > > > deploy services in the future to avoid being tied to a single instance > > > in our puppetry). This includes running the noop puppet apply test > > > against Xenial for these nodes on puppet changes as well. > > > > > > All of that has gone relatively well and I just tried to deploy on > > > Xenial and have run into a few problems. The puppet output [11] shows > > > that the service isn't installed properly on Ubuntu Xenial. Looking at > > > the puppet-wildfly module [12] it doesn't appear to support systemd on > > > debuntu yet. Due to the upcoming thanksgiving holiday I doubt I will get > > > around to updating and testing that this week, so would be great if > > > someone else is able to work with the puppet-wildfly upstream to fix > > > this. > > > > > > One other thing that came up is do we need to copy any files from the > > > old server to the new server? Specifically it looks like portions of > > > `/home/wildfly/zanata` may need to be preserved. Or is everything > > > important in the database? > > > > > > In any case once the wildfly puppetry is working I think the next step > > > is to upgrade zanata to 3.9.6, change the openid server, and have the > > > team test it. Once that looks good its on to the production server. > > > > > > [11] http://paste.openstack.org/show/590149/ > > > [12] > > > > > https://github.com/biemond/biemond-wildfly/blob/master/manifests/service.pp# > > L35-L46 > > > > Time for an update, and this time it is good news. I managed to hack > > around the systemd issue by adding a puppet exec between installing the > > init script and starting the service that runs a systemctl daemon-reload > > [13]. This is necessary to make systemd see the init script allowing it > > to be used to start the service. > > > > With that sorted I have created a new server called > > translate-dev01.openstack.org and updated DNS to have > > translate-dev.openstack.org point to it. This server is running on > > Ubuntu Xenial with Java 8 and using the old version of Zanata (3.7.3). > > Now would be a good time to test that this works so that we don't have > > to do the entire upgrade migration in one go when we do production. Once > > we are happy with Zanata 3.7.3 on Ubuntu Xenial and Java 8 we can > > upgrade translate-dev.openstack.org to the version of Zanata we want, > > then test again. And once that is done we can redeploy and upgrade the > > production server on Xenial as well. > > > > Let me know how your testing goes and we can take it from there. > > > > [13] https://review.openstack.org/#/c/401363/ > > > Hi Clark, > > thanks for the work. Regarding the systemd issue just to ensure: you are > using Wildfly 10 with wildfly puppet module v1.0.0? It seems the systemd > stuff is already implemented there and to use with: > > class { '::wildfly': > ... > init_system => 'systemd', > }
This actually looks brand new. I will have to look at it more closely. I ended up hacking around it locally though. The shipped sys v init script works fine with systemd you just have to inject a daemon-reload since puppet doesn't know how to do that when dealing with systemd. Clark _______________________________________________ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
