Can you add spruce to the survey as an option please? We've used it
instead of spiff for a very long time. I'd like to think lots of people
prefer it to spiff.

Nic







On Sat, Feb 11, 2017 at 12:35 PM +1000, "Marco Nicosia" <
mnicosia(a)pivotal.io> wrote:



















Hi all!


On behalf of the Core Services engineering team, I’m happy to announce
that we’ve recently published cf-mysql-release v34
<https://github.com/cloudfoundry/cf-mysql-release/releases/tag/v34>. I
wanted to call attention to a couple of important changes, and take a
moment to ask for some feedback.


First, we’re thinking of dropping spiff manifest templates in favor of
using BOSH’s native features. To learn more, take a peek at our work in
progress, cf-mysql-deployment
<https://github.com/cloudfoundry/cf-mysql-deployment>.





- Is this OK? Click: 💚
<http://clickpoint.cfapps.io/click/mysql-manifest-gen?lose-spiff>

- Is disaster? Click: 💔
<http://clickpoint.cfapps.io/click/mysql-manifest-gen?keep-spiff>




Both links lead to a brief survey where you can tell us more about how you
use and deploy cf-mysql. I’d love to hear from you.


Important Changes




-

*Retroactively remove lock permissions* from existing
service-broker-created users [#132881499
<https://www.pivotaltracker.com/story/show/132881499>]


One major limitation of Galera is that table-level locks are not
replicated. We’ve found that many applications that rely on table locking
never notice this limitation when moving onto cf-mysql. In order to “fail
fast,” starting in v32
<https://github.com/cloudfoundry/cf-mysql-release/releases/tag/v32>,
new service instances are explicitly disallowed from locking tables. With
release v34 forward, all existing Service Instances will no longer have the
ability to lock tables. Apps that attempt to lock tables will now see an
error of the form:


MariaDB [cf_eedd5768_9c6c_4388_ae0b_dc64f4022bf4]> LOCK TABLES fruit WRITE;

ERROR 1044 (42000): Access denied for user 'uoY64cqdw6qyMtNl'@'%' to database 'cf_eedd5768_9c6c_4388_ae0b_dc64f4022bf4'



-

Rename broker-deregistrar to *deregister-and-purge-instances* [
#138006305 <https://www.pivotaltracker.com/story/show/138006305>]


Too often, Operators have been burned trying out an innocuously-named
errand. Renaming the errand, deregister-and-purge-instances makes it
clear that this is an errand that should only be run just before bosh
delete-deployment.







Release Notes

v34 has a ton more inside, I hope you check out the release notes
<https://github.com/cloudfoundry/cf-mysql-release/releases/tag/v34>!


Thanks, and have a great weekend!


—


Marco Nicosia
Product Manager
Pivotal Software, Inc.
mnicosia(a)pivotal.io


​