maria-developers team mailing list archive

[Arjen Lentz <arjen@xxxxxxxxxxxxx>]

Hi Peter

On 14/10/2009, at 8:44 AM, Peter Laursen wrote:
> The billion dollar question is: what options should a config wizard  
> (ideally) provide?
> .
> base configuration (memory requirements, #of_connections assumed):  
> use: mini, midi, medium. large, huge --template
> default storage engine: MyISAM, Maria, XtraDB, PBXT

InnoDB (XtraDB), that's the only mature transactional one from the  
above list.
Also set sql_mode=TRADITIONAL

both are actually what the original installer does for WIndows already.


> default charset: latin1, utf8, custom

I left latin1 in the baseline config, but with comments to easily go  
to utf8 when needed.

> enable slow log: yes|no

Yes, with a few extra options from the extensions, such as query_plan  
and the rate limiter.

> enable general log: yes|no

never.

> enable query cache: yes|no

yes but small.

> .. what else is important?

We made a sane baseline config that's in the debian/ubuntu package  
tests already.

Cheers,
Arjen.


> On Wed, Oct 14, 2009 at 00:10, Sergey Petrunya  
> <psergey@xxxxxxxxxxxx> wrote:
> Hi!
>
> It's time we've started to think of what we need of Windows  
> installer (at the
> moment we're close to having windows "noinstall" zip archive but  
> have nothing
> for installable package).
>
> I've filed some initial set of ideas and thoughts as MWL#55,
> http://askmonty.org/worklog/?tid=55. Any comments or input are  
> welcome.
>
>
> ----- Forwarded message from worklog-noreply@xxxxxxxxxxxx -----
>
> From: worklog-noreply@xxxxxxxxxxxx
> To: monty@xxxxxxxxxxxx
> Date: Wed, 14 Oct 2009 00:07:28 +0300 (EEST)
> Subject: [Maria-developers] Updated (by Psergey): Windows installer  
> for
>        MariaDB (55)
>
> -----------------------------------------------------------------------
>                              WORKLOG TASK
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 
> =-
> TASK...........: Windows installer for MariaDB
> CREATION DATE..: Wed, 14 Oct 2009, 00:07
> SUPERVISOR.....: Monty
> IMPLEMENTOR....:
> COPIES TO......:
> CATEGORY.......: Server-RawIdeaBin
> TASK ID........: 55 (http://askmonty.org/worklog/?tid=55)
> VERSION........: Server-9.x
> STATUS.........: Un-Assigned
> PRIORITY.......: 60
> WORKED HOURS...: 0
> ESTIMATE.......: 0 (hours remain)
> ORIG. ESTIMATE.: 0
>
> PROGRESS NOTES:
>
> -=-=(Psergey - Wed, 14 Oct 2009, 00:07)=-=-
> High-Level Specification modified.
> --- /tmp/wklog.55.old.28205     2009-10-14 00:07:28.000000000 +0300
> +++ /tmp/wklog.55.new.28205     2009-10-14 00:07:28.000000000 +0300
> @@ -1 +1,50 @@
> +Not a spec so far but a list of points to consider:
> +
> +1. Installer wishlist (user POV)
> +--------------------------------
> +From the user point of view:
> +
> +1.1 Step 1: simplest installer
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +An installer package that
> +- Copies files on installation
> +- Registers mysqld a service
> +- Checks if installation directory, MySQL's port, or named pipe are
> +  busy. If they are, it asks to remove the previous installation  
> first
> +  and aborts.
> +- Uninstall procedure (TODO: should that remove the datadir or  
> leave it?)
> +
> +1.2 Step 2: upgrades from MySQL
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +- Same as above but with handling of the case where MySQL has been  
> already
> +  installed:
> +  - offer to replace MySQL.
> +  - upgrade the data directory (todo we should sort out if anything/ 
> what is
> +    needed for this).
> +  - Uninstall MySQL
> +  - Install MariaDB.
> +
> +1.3 Step 3: Configuration wizard
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +- Installer should include configuration wizard that's similar to  
> what MySQL
> +  installer does.
> +
> +1.1 Step 1
> +~~~~~~~~~~
> +
> +2. Installer wishlist (developer POV)
> +-------------------------------------
> +* Some "installshield-like" tool that's easy to use (suggestion by  
> Webyog:
> +  NSIS)
> +* Installation procedure source should reside in MariaDB source  
> repository
> +* Installation procedure source file is better to be in human- 
> readable text
> +  format.
> +* It should be possible to automate creation of the installer  
> package, in a way
> +  that can be run from buildbot (e.g. the installer package build  
> process
> +  should print messages to its stdout)
> +
> +* Any suggestions on how can one automatically test the  
> installation package?
> +  (for example, we'll want to start the installer, install, check  
> that
> +  installation succeeded, then start the server, run some commands,  
> then
> +  uninstall. Any ways to achieve that?)
>
>
>
>
> DESCRIPTION:
>
> We need Windows Installer package for MariaDB.
>
>
> HIGH-LEVEL SPECIFICATION:
>
>
>
> Not a spec so far but a list of points to consider:
>
> 1. Installer wishlist (user POV)
> --------------------------------
> >From the user point of view:
>
> 1.1 Step 1: simplest installer
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> An installer package that
> - Copies files on installation
> - Registers mysqld a service
> - Checks if installation directory, MySQL's port, or named pipe are
>  busy. If they are, it asks to remove the previous installation first
>  and aborts.
> - Uninstall procedure (TODO: should that remove the datadir or leave  
> it?)
>
> 1.2 Step 2: upgrades from MySQL
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> - Same as above but with handling of the case where MySQL has been  
> already
>  installed:
>  - offer to replace MySQL.
>  - upgrade the data directory (todo we should sort out if anything/ 
> what is
>    needed for this).
>  - Uninstall MySQL
>  - Install MariaDB.
>
> 1.3 Step 3: Configuration wizard
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> - Installer should include configuration wizard that's similar to  
> what MySQL
>  installer does.
>
> 1.1 Step 1
> ~~~~~~~~~~
>
> 2. Installer wishlist (developer POV)
> -------------------------------------
> * Some "installshield-like" tool that's easy to use (suggestion by  
> Webyog:
>  NSIS)
> * Installation procedure source should reside in MariaDB source  
> repository
> * Installation procedure source file is better to be in human- 
> readable text
>  format.
> * It should be possible to automate creation of the installer  
> package, in a way
>  that can be run from buildbot (e.g. the installer package build  
> process
>  should print messages to its stdout)
>
> * Any suggestions on how can one automatically test the installation  
> package?
>  (for example, we'll want to start the installer, install, check that
>  installation succeeded, then start the server, run some commands,  
> then
>  uninstall. Any ways to achieve that?)
>
>
> ESTIMATED WORK TIME
>
> ESTIMATED COMPLETION DATE
> -----------------------------------------------------------------------
> WorkLog (v3.5.9)
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~maria-developers
> Post to     : maria-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~maria-developers
> More help   : https://help.launchpad.net/ListHelp
>
> ----- End forwarded message -----
>
> --
> BR
>  Sergey
> --
> Sergey Petrunia, Software Developer
> Monty Program AB, http://askmonty.org
> Blog: http://s.petrunia.net/blog

--
Arjen Lentz, Exec.Director @ Open Query (http://openquery.com)
Exceptional Services for MySQL at a fixed budget.

Follow our blog at http://openquery.com/blog/
OurDelta: enhanced builds for MySQL @ http://ourdelta.org