CAcert Code Development list.

[Eva Stöwe <estoewe AT cacert.org>]

Hi Wytze, hi @ll,

from my point of view a20140322.1 is nearly finished. Yesterday I spend
some time on the final ruling. I do not think that you have to wait for
that as I regard the clean-up part of the case to be finished.

What remains is only some consideration on further consequences of the case.

If you do not observe anything odd in the logs I have no issue with you
conversing the DB as the software team asked you to do.

Thank you for your help.

Am 21.07.2014 17:10, schrieb Wytze van der Raay:
> Hi Eva,
> 
> On 06/10/2014 10:47 AM, Wytze van der Raay wrote:
>> On 06/07/2014 12:00 AM, Benny Baumann wrote:
>>> We have a fix for https://bugs.cacert.org/view.php?id=1172
>>> "Move the database engine from myISAM to InnoDB"
>>>
>>> The fix was reviewed by me (BenBE) and Michael Tänzer (NEOatNHNG).
>>> The fix was tested by Marcus Mängel (INOPIAE), Martin Gummi (magu), Eva
>>> Stöwe (katzazi) et. al.
>>>
>>> Find the patch attached to this mail. No update of the translations is
>>> required.
>>>
>>> This patch introduces a new script file for the database. Please
>>> coordinate with arbitration regarding a20140322.1 to ensure a sane
>>> environment before executing the script to convert the database to use
>>> InnoDB as database engine (instead of MyISAM). Please ensure proper
>>> backup AND restore procedures are in place AND working before this
>>> script is run.
> 
> Can you please let us know whether the current state of a20140322.1 is
> stable enough for proceeding with the conversion of the production database
> to InnoDB format?
> 
> Regards,
> -- wytze
> 
> 
>> The script has been installed on the production server on June 10, 2014.
>> See also the attached log message which was sent out to the 
>> cacert-systemlog
>> mailinglist.
>>
>> Note that the script has *not* yet been executed. This will take place at
>> some later convenient moment. The running arbitration is one issue, another
>> one is that our testserver test2.cacert.org has already partially been
>> upgraded to Debian Wheezy, ie. MySQL 5.5, so a test there would not be
>> conclusive for the production server unfortunately. One option would be to
>> postpone the migration until *after* the upgrade of the production server
>> to Debian Wheezy.
> 
> 

-- 
mit freundlichen Grüßen / best regards
Eva Stöwe
CAcert Assurer
CAcert Arbitrator & Case Manager
CAcert.org - Free Certificates
E-Mail: 
estoewe AT cacert.org

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature