<div dir="ltr">Okay done! I am "lionaneesh" on IRC and I'll be there on #sugar <a href="http://irc.freenode.net">irc.freenode.net</a>.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 5, 2013 at 6:14 PM, Roberto Rodriguez Alcala <span dir="ltr"><<a href="mailto:rralcala@gmail.com" target="_blank">rralcala@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Can we do it at 17:00 UTC?<div class="HOEnZb"><div class="h5"><br><br><div class="gmail_quote">On Fri, Jul 5, 2013 at 2:42 PM, Aneesh Dogra <span dir="ltr"><<a href="mailto:aneesh@sugarlabs.org" target="_blank">aneesh@sugarlabs.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Perfect. Let's setup an IRC meeting in 2 hours?</div><div><div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Fri, Jul 5, 2013 at 6:10 PM, Roberto Rodriguez Alcala <span dir="ltr"><<a href="mailto:rralcala@gmail.com" target="_blank">rralcala@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi<br><br>I'm still settling at my new place with scarce free time but please ping me if I can help in anything.<br>
<br>I'll normally make time for it within 2 to 4 hours.<br><br>bernie: I'll also keep an eye on munin.<br>
<br>Best,<br><br>Roberto<div><div><br><br><div class="gmail_quote">On Thu, Jul 4, 2013 at 3:05 AM, Bernie Innocenti <span dir="ltr"><<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Resending with the correct localization list address.<br>
<div><div><br>
On 07/03/2013 08:45 PM, Bernie Innocenti wrote:<br>
> +rralcala<br>
> +rgs<br>
><br>
> On 07/03/2013 04:11 PM, Aneesh Dogra wrote:<br>
>> Hey List,<br>
>><br>
>> I have finally ported our ancient pootle to pootle 2.5 (with all<br>
>> translation and database files) and it seems to be working. Check<br>
>> <a href="http://newpootle.sugarlabs.org/" target="_blank">http://newpootle.sugarlabs.org/</a><br>
>><br>
>> The next job is to start porting pootle-helpers and make them work on<br>
>> 2.5. If someone can give me a starting point it would be greatly<br>
>> helpful. Are there any scripts that might not be useful anymore?<br>
>><br>
>> Pootle 2.5 also includes some new inbuilt scripts like commit_to_vcs,<br>
>> which of course commits and pushes translation changed to the linked<br>
>> code repository [git/svn/vcs], so it probably supersedes our version in<br>
>> pootle-helpers.<br>
>><br>
>> Any inputs welcome.<br>
><br>
> I'm very happy to hear that you've (almost) succeeded in bringing us an<br>
> up-to-date Pootle instance! Many before you struggled with this<br>
> difficult migration.<br>
><br>
> Unfortunately, I won't be able to help you with the next phase because<br>
> I'll be on vacation from Jul 4 to Jul 10 (see my post to systems@).<br>
><br>
> Roberto might be able to help you, as he had expressed interest in<br>
> helping with Pootle. Aleksey also has lots of experience running<br>
> production services and integrating git with other things.<br>
><br>
> Checklist for you and whoever assists you:<br>
><br>
> - have you tried rebooting the service to see if it stays up?<br>
><br>
> - have you tried loading the service with some queries or crawling<br>
> it with wget -R to see if it has enough memory?<br>
><br>
> - what monitoring do you need? munin?<br>
><br>
> - are logs being rotated? any log spew?<br>
><br>
> - backups? never transition a VM to production before you have<br>
> good backups<br>
><br>
> - documentation? is the wiki up to date?<br>
><br>
> - try migrating all data from old pootle to new pootle once.<br>
> how long does it take? make sure nothing has been lost<br>
> or corrupted during the migration.<br>
><br>
> - announce the day and time of the cut-off on this list and<br>
> maybe cc sugar-devel@<br>
><br>
> - ensure the CNAME <a href="http://translate.sugarlabs.org" target="_blank">translate.sugarlabs.org</a> has a reasonably<br>
> short ttl<br>
><br>
> - on the announced time, put the production instance in read-only<br>
><br>
> - sync the data one last time, verify the result one last time<br>
><br>
> - switch the CNAME in the DNS<br>
><br>
> - wait until the change propagates<br>
><br>
> - announce the end of the outage<br>
><br>
> - wait for people to complain about the fallout<br>
><br>
> - after a few days, recycle the old VM<br>
><br>
> Of course, if anything goes wrong at any time, you must be able to go<br>
> back to the previous state. Sysadmin safely! :-)<br>
><br>
<br>
<br>
--<br>
</div></div><span><font color="#888888"> _ // Bernie Innocenti<br>
\X/ <a href="http://codewiz.org" target="_blank">http://codewiz.org</a><br>
</font></span></blockquote></div><br><br clear="all"><br></div></div><span><font color="#888888">-- <br>Roberto Rodríguez Alcalá<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear="all"><br></div></div><span class="HOEnZb"><font color="#888888">-- <br>Roberto Rodríguez Alcalá<br>
</font></span></blockquote></div><br></div>