[chef] Design of cookbook breaks systems

[Tobias Unsleber < >]

Hi,

I'm using the mysql-cookbook to manage mysql at our servers.

What cause trouble is that this cookbook breaks the system in
terms of two aspects:

- Since the service is named mysql-<instance> and the default
instance "mysql" is no longer existing. So at every update the
update is failling because the scripts try to use a service called
"mysql" which is failing

- Since the Sockets are named according like the configured instance
the default sockets are no longer available and many software
does no longer work by default.

-----

Furthermore the mysql-cookbook is in general quite fine. Good to manage the
server in general, users, privileges and databases. I probably won't
ever need
the multiple-instance feature. It's OK if it does not get in my way.

At the moment I try workarounds to fix the issues. For the Sockets I
modify the
startup scripts in the cookbook to have created links to the
instance-socket for
the different operating systems to the expected default location.

For the startup script issue, I working on some fix right now.

Does anybody have an advice for this issue?

Regards,
Tobias

-- 
Tobias Unsleber
Inline Online Internet Dienste GmbH
Kaiserstr. 80
D-76133 Karlsruhe
Tel: +49-721-96682-45, Fax: +49-721-96682-11

HRB 7454, Sitz Karlsruhe, Registergericht: Karlsruhe
Geschäftsführer: Dr. Andreas Werner, Dr. Armin Zundel