How to write efficient and correct MySQL recipes for you configuration management system in 2019

5/24/2019 How to write efficient and correct MySQL recipes for you configuration management system in 2019
file:///home/fred/ownCloud/Presentations/ORACLE/LOADays 2019/How to write efficient and correct MySQL recipes for you configuration manageme… 1/51
1 / 51

2 / 512 / 51

Safe Harbor Statement
The following is intended to outline our general product
direction. It is intended for information purpose only, and may
not be incorporated into any contract. It is not a commitment to
deliver any material, code, or functionality, and should not be
relied up in making purchasing decisions. The development,
release and timing of any features or functionality described for
Oracle´s product remains at the sole discretion of Oracle.
Copyright @ 2019 Oracle and/or its affiliates. All rights reserved.
3 / 51

about me - http://about.me/lefred
Who am I ?
4 / 51

Frédéric
Descamps
@lefred
MySQL Evangelist
Hacking MySQL since 3.23
devops believer
living in Belgium 🇧🇪
http://lefred.be
5 / 51

MySQL 8.0
a major release devops friendly
6 / 51

New Key Features for a devops
World
MySQL 8.0 brought more than 250 features. Some are very
interesting to use with a configuration management system:
7 / 51

World
SET PERSISTS
8 / 51

World
SET PERSISTS
SQL RESTART statement
9 / 51

file:///home/fred/ownCloud/Presentations/ORACLE/LOADays 2019/How to write efficient and correct MySQL recipes for you configuration managem… 10/51
World
SET PERSISTS
integrated upgrade process
10 / 51

World
SET PERSISTS
dual passwords support
11 / 51

World
SET PERSISTS
dual passwords support
roles
12 / 51

World (2)
Partial Revokes from Database Objects
13 / 51

World (2)
ALTER INSTANCE for changing:
14 / 51

World (2)
InnoDB Encryption Key
15 / 51

World (2)
BINLOG Encryption Key
16 / 51

World (2)
TLS Context (SSL)
17 / 51

World (3)
MySQL Shell
18 / 51

World (3)
MySQL Shell
util object (check for upgrade)
19 / 51

World (3)
MySQL Shell
API
20 / 51

World (3)
MySQL Shell
API
adminAPI for HA
21 / 51

SET PERSIST
In MySQL 8.0, it's possible to use the SET statement syntax for
making configuration changes at runtime that also persist across
server restarts. This is a SQL statement.
22 / 51

SET PERSIST
In MySQL 8.0, it's possible to use the SET statement syntax for
making configuration changes at runtime that also persist across
server restarts. This is a SQL statement.
The configuration management recipe should not change any configuration
file. The config file should be the default or the most generic possible
according your systems. Then the recipe should verify and set the variables
defined for your system.
23 / 51

RESTART
Something very interesting, especially for Cloud environments,
is the new possibility to restart the mysqld process directly from
the SQL interface.
24 / 51

RESTART
Something very interesting, especially for Cloud environments,
is the new possibility to restart the mysqld process directly from
the SQL interface.
Of course it's possible to call the wrapper taking care of this operation,
service file or systemd service, but instead of subscribing or notifying the
service, when a variable change requires a restart (those are less and less),
it's possible to immediately restart the process directly from SQL
25 / 51

var
=
yxz
y n
y n
we
are
good
set
persist
we
are
good
set
persist_only
restart
Workflow Example
mysqlsh root@localhost --sql -e "select variable_value
from performance_schema.global_variables
where variable_name='innodb_ ush_method'" | tail -n1
mysqlsh root@localhost --sql
-e "set persist innodb_ ush_method=O_DIRECT"
ERROR: 1238 at line 1: Variable
'innodb_ ush_method' is a read only variable
if [[ $? ne 0 ]]
then
-e "set persist_only innodb_ ush_method=O_DIRECT"
-e "restart"
26 / 51

mysql_upgrade is gone
Previously, after installation of a new version of MySQL, the
server automatically upgraded the data dictionary tables at the
next startup, after which the DBA was expected to invoke
mysql_upgrade manually to upgrade the system tables in the
mysql schema, as well as objects in other schemas such as the
sys schema and user schemas (and restart mysqld again).
Since MySQL 8.0.16, the server (mysqld) does itself.
27 / 51

mysql_upgrade is gone
Previously, after installation of a new version of MySQL, the
server automatically upgraded the data dictionary tables at the
next startup, after which the DBA was expected to invoke
mysql_upgrade manually to upgrade the system tables in the
mysql schema, as well as objects in other schemas such as the
sys schema and user schemas (and restart mysqld again).
Since MySQL 8.0.16, the server (mysqld) does itself.
Because this operation was manual most systems are running without
updated system tables that can lead to errors. This is particularly true on
systems where the upgrade process is managed by configuration
management systems
28 / 51

mysql_upgrade is gone (2)
So, why did we do that?
Faster upgrade
Simpler process
Better security
Significant reduction in upgrade steps and more easily
automated
No restarts
Just plug and play
29 / 51

dual passwords
Since MySQL 8.0.14 it's possible for an account to have dual
password, designated as primary and secondary passwords.
This capability enables phased password changes to be
performed seamlessly in complex multiple-server systems,
without downtime.
SET PASSWORD [FOR user] = 'auth_string'
[REPLACE 'current_auth_string']
[RETAIN CURRENT PASSWORD]
ALTER ... DISCARD OLD PASSWORD can be used later.
30 / 51

dual passwords
Since MySQL 8.0.14 it's possible for an account to have dual
password, designated as primary and secondary passwords.
This capability enables phased password changes to be
performed seamlessly in complex multiple-server systems,
without downtime.
SET PASSWORD [FOR user] = 'auth_string'
[REPLACE 'current_auth_string']
[RETAIN CURRENT PASSWORD]
ALTER ... DISCARD OLD PASSWORD can be used later.
This will allow to change the MySQL password from your configuration
system management without having to plan a complicated orchestration
between involved services
31 / 51

roles
MySQL 8.0 supports roles, which are named collections of
privileges. Roles enable assignment of sets of privileges to
accounts and provide a convenient alternative to granting
individual privileges.
32 / 51

Partial Revokes from Database
Objects
Have you ever encountered situations where you want to grant
a user access to all databases except a few databases?
Starting from MySQL 8.0.16, you can partially revoke database
privileges from users, even if they are granted global privileges.
33 / 51

Partial Revokes from Database
Objects
Have you ever encountered situations where you want to grant
a user access to all databases except a few databases?
Starting from MySQL 8.0.16, you can partially revoke database
privileges from users, even if they are granted global privileges.
SQL> CREATE USER foo_admin;
SQL> GRANT SELECT ON *.* TO foo_admin;
SQL> SET GLOBAL partial_revokes=ON;
SQL> REVOKE SELECT ON payroll.* FROM foo_admin;
34 / 51

ALTER INSTANCE
ALTER INSTANCE defines actions applicable to a MySQL server
instance:
ALTER INSTANCE ROTATE INNODB MASTER KEY
This action rotates the master encryption key used for InnoDB
tablespace encryption.
More info: https://dev.mysql.com/doc/refman/8.0/en/innodb-
tablespace-encryption.html
35 / 51

ALTER INSTANCE (2)
ALTER INSTANCE ROTATE BINLOG MASTER KEY
This action rotates the binary log master key used for binary log
encryption.
It's also possible to call a RESTART to force the master key
rotation using
binlog_rotate_encryption_master_key_at_startup.
More info:
https://dev.mysql.com/doc/refman/8.0/en/replication-binlog-
encryption.html
36 / 51

ALTER INSTANCE (3)
TLS Context (SSL)
As of MySQL 8.0.16, the SSL context the server uses for new
connections is reconfigurable at runtime. This capability may be
useful, for example, to avoid restarting a MySQL server that has
been running so long that its SSL certificate has expired.
ALTER INSTANCE RELOAD TLS
This action reconfigures the SSL context from the current values
of the system variables that define the context. It also updates
the status variables that reflect the active context values.
37 / 51

MySQL Shell - util object
MySQL Shell includes utilities for working with MySQL. To access
the utilities from within MySQL Shell, use the util global object.
The util.checkForServerUpgrade() function is an upgrade
checker utility that enables you to verify whether MySQL server
instances are ready for upgrade.
38 / 51

MySQL Shell - util object
MySQL Shell includes utilities for working with MySQL. To access
the utilities from within MySQL Shell, use the util global object.
The util.checkForServerUpgrade() function is an upgrade
checker utility that enables you to verify whether MySQL server
instances are ready for upgrade.
This is very useful as you can check that the dataset and settings are
compatible with the newer version.
39 / 51

MySQL Shell - util object (2)
Let's consider the following
puppet recipe:
package {
'mysql-community-server':
ensure => latest,
}
40 / 51

Let's consider the following
puppet recipe:
package {
ensure => latest,
}
What if the current MySQL version is 5.7.26 and the latest
available is now 8.0.16 ?
41 / 51

package {
ensure => latest,
noop => true,
notify => Exec['upgrade_checker'],
}
exec {
'upgrade_checker':
command => "mysqlsh -- util check-for-upgrade
{ --user=root --host=localhost }",
refreshonly => true,
no tfy => Package['mysql-comunity-server-real'],
}
package {
'mysql-community-server-real':
name => 'mysql-community-server',
ensure => latest,
refreshonly => true,
}
42 / 51

MySQL Shell - adminAPI
The AdminAPI are commands you use to work with a cluster and
it's server instances modify the configuration of the instance.
Configuration changes can be persisted to the instance
automatically. Persisting changes is required after the following
operations:
dba.con gureInstance()
dba.createCluster()
Cluster.addInstance()
Cluster.removeInstance()
Cluster.rejoinInstance()
43 / 51

MySQL Shell - adminAPI
The AdminAPI are commands you use to work with a cluster and
it's server instances modify the configuration of the instance.
Configuration changes can be persisted to the instance
automatically. Persisting changes is required after the following
operations:
dba.con gureInstance()
dba.createCluster()
Cluster.addInstance()
Cluster.removeInstance()
Cluster.rejoinInstance()
All good commands to use in your recipe as they automate a lot
44 / 51

MySQL Shell - adminAPI (2)
The AdminAPI provides also functions that can be used for
checking if the configuration is suitable to join an InnoDB Cluster
or if the dataset is compatible with the cluster:
dba.checkInstanceCon guration()
Cluster.checkInstanceState()
45 / 51

MySQL Shell - API
All the Shell API is available via a Command Line Integration
Syntax.
Like the previous example with the util object, this new syntax
helps invoking built-on shell comamnds:
mysqlsh [OPTIONS] [URI] -- <object_name> <method_name> [ argument_list ]
https://mysqlserverteam.com/mysql-shell-api-command-line-
integration-for-devops/
46 / 51

MySQL Shell - API
All the Shell API is available via a Command Line Integration
Syntax.
Like the previous example with the util object, this new syntax
helps invoking built-on shell comamnds:
mysqlsh [OPTIONS] [URI] -- <object_name> <method_name> [ argument_list ]
https://mysqlserverteam.com/mysql-shell-api-command-line-
integration-for-devops/
This makes much easier call without single quotes, double quotes and
backslashed quotes in your recipes
47 / 51

in action
operations to manage MySQL
48 / 51

Let me show you some of these
improvements in action !
49 / 51

Conclusion
MySQL is evolving taking in consideration comments of those
who are operating MySQL at scale where not everything can be
done manually. We are working on facilitating more and more
the integration of many operations by writing easy APIs.
Now you know what are the best practices to re-write efficient
recipes for your configuration management system.
50 / 51

Thank you !
Any Questions ?
share your 💕 for MySQL on social media using @mysql
#MySQL8isGreat #MySQL
51 / 51

How to write efficient and correct MySQL recipes for you configuration management system in 2019

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to How to write efficient and correct MySQL recipes for you configuration management system in 2019

Similar to How to write efficient and correct MySQL recipes for you configuration management system in 2019 (20)

More from Frederic Descamps

More from Frederic Descamps (20)

Recently uploaded

Recently uploaded (20)

How to write efficient and correct MySQL recipes for you configuration management system in 2019